Please enable JavaScript.
Coggle requires JavaScript to display documents.
Chapter 2 - Coggle Diagram
Chapter 2
-
2.1.2.Software Development Lifecycle Models in Context:
- Software development lifecycle models must be selected and adapted to the context of project and product characteristic. They are:
-
- The type of product being developed
-
- Identified product and project risks
2.2.Test Levels
- Objective:
focus on component that are separately testable
- Special:
Done in isolation from the rest of the system...
- Functionality
- Non-functionality
- Structural properties
- Test basis:
Code, data model, component specification, test object
- Components, unit or modules
- Code and data structures
- Classes
- Objective:
Focus on interactions and interfaces between components or system
- Software and system design
- Sequence diagrams
- Interface and communication protocol specifications
- Use cases
- Architecture at component or system level
- Workflows
- External interface definitions
- Functional
- Non-functional
- Special: There are 2 different levels of integration testing
- Component integration testing
- System integration testing
- Subsystem database
- Infrastructure Interfaces APIs
- Objective:
Focus on the behavior and capabilities of a whole system or product
- Special:
Uncompleted or undocumented specification
- Functional
- Non-functional
- Data quality characteristic
- Risk analysis reports
- Use cases
- Epics and user stories
- Models of system behavior
- State diagrams
- System and user manuals
- Applications
- Hardware / Software system
- Establish confidence
- Validating that system works as expected
- Verify functional / non-functional behaviors
Common types
User Acceptance Testing (UAT)
- End-user perform
- Validating the fitness for use of the system
Operational acceptance testing
- By operations or system administration staff
- Focus on operational aspect
-
-
-
-
-