Software
<2>
** c______r p, p, and p.a.d/d ________ **
Computer programs, procedures, and possibly associated documentation/data pertaining to the operation of a computer system.
- Application Software
- System Software
Application Software
<2>
** P.I.P.T for ___ _____. **
* G.P.A.P and A.S.P*
Performs Information Processing Tasks for end users.
- General Purpose Application Programs (email, web browsers, etc)
- Application Specific Programs (business-accounting, STEM software, etc)
System Software
<2>
- ** MSO ____ ***
- ** S_P and S_P ***
- ** examples for each ***
Manages and Supports Operations of computer systems and networks.
- System Management Programs (OSs, DBMS, app servers, etc)
- System Development Programs (programming (language translators, editors, tools ,etc)
Software Quality (SQ)
** think temperature to which a s___, c___, or p___ …… (2 things)***
The degree to which a system, component, or process
- meets specified requirements
- meets customer or user needs or expectations
[SQ] Characteristics
<7>
** F.R.$.(GASS).D.D.C **
- Good design
- Good functionality
- Reliable
- Consistency
- Durable
- Good after-sale service
- Value for $
[SQ] Assurance (SQA)
A systematic pattern of all necessary actions to ensure that an item/product conforms to technical requirements.
[SQA] Objectives
Ensure confidence that software will conform to:
- Functional and tech requirements
- Scheduling and budget requirements
[SQA] Challenges
<4>
** L.I.N.C **
- Limited opportunities to detect defects (“bugs”)
- Invisibility of the product
- Diverse/potentially varying # of users
- High complexity
[SQA] Components and Practices (SQA C and P)
<7>
** C.C.D. P.T.R.S. **
- Configuration Management
- Checklists and Templates
- Documentation control
- Procedures and Work Instructions
- Software Testing
- Reviews
- Staff (re)training certification
Software Bugs
term coined by Grace Hopper when a moth was found in the relay of the Mark II
[SQA C and P] Reviews
Design Reviews
Peer Reviews
[SQA C and P Reviews] Design Reviews
A systematic and documented analysis of a design which determines its ability to meet requirements. Serves to identify present and potential problems.
[SQA C and P Reviews] Peer Reviews
- Inspections: Manually examining the developing product, by small groups of peers to validate conformity to specs and requirements.
- Walkthroughs: Developer leads dev members and other parties through a product - participants are involved in giving feedback.
[SQA C and P Reviews] Objectives
<5>
- detect analysis and design errors
- identify new risks
- locate deviations from templates, style procedures, and conventions
- approve the analysis or design of a product
- provide an informal meeting place
[SQA C and P] Verification and Validation
- verification: “did we build the software right?”
- validation: “did we build the right software?”
[SQA C and P] Testing Definition 1
an empirical, technical investigation conducted to provide stakeholders with info about quality of product under test
[SQA C and P Testing] Objectives
- find defects from development of item
- prevent defects
- increase confidence about level of quality
- ensure end result meets biz/user requirements
[SQA C and P] Testing Definition 2
Software evaluation through exploration and experimentation.
- Evaluating: making judgement (good? bad? etc)
- Exploration: testing is inherently exploratory
- Experimentation: interaction with a subject and observation of its operating
[SQA] V Model (SQA V Model)
V Model: Verification and Validation Model
- An extension of the waterfall model, based on associating the testing phase of each corresponding development stage
- Every single development cycle phase has a directly associated testing phase
- The corresponding testing phase of the development phase is planned in parallel.
- One side of the V is the Verification phases, and the other side are the Validation phases. The Coding phase is in the middle.
{SQA V Model] Verification Phases (Development)
<4>
(1) User/Business Requirement: communication with customer to understand expectations and needs
(2) Software Application/System Design: complete hardware and communication setup for product
(3) High Level Design/Architectural Design: data transfer and comms between internal modules and external/outside systems
(4) Low Level Design/Detailed Design: detailed internal design for all system modules
[SQA V Model] Validation Phases (Testing)
<4>
(1) User Acceptance Testing: system’s compliance with business requirements
(2) System Testing: completely integrated system’s functionality w/ external systems (uncovers most hardware and software issues)
(3) Integration Testing: verifies interfaces between integrated components (modules)
(4) Unit Testing: written by developers as they work on code
[SQA Testing] Methods (SQA Testing Methods)
<4>
- Static
- Dynamic
- White Box
- Black Box
[SQA Testing Methods] Static
- Involves verification
- Item under test is NOT being executed
[SQA Testing Methods] Dynamic
- Involves validation
- Item under test IS being executed
