Introduction Concepts Workflow Activities Artifacts Guidelines
- Relation to Other Disciplines
- Related Book Content
The purpose of implementation is:
- to define the organization of the code, in terms of implementation subsystems organized in layers
- to implement classes and objects in terms of components (source files, binaries, executables, and others)
- to test the developed components as units
- to integrate the results produced by individual implementers (or teams), into an executable system
The Implementation discipline limits its scope to how individual classes are to be unit tested. System tests and integration tests are described in the Test discipline.
Relation to Other Disciplines
The implementation is related to other disciplines:
- The Requirements discipline describes how to, in a use-case model, capture requirements that the implementation should fulfill.
- The Analysis & Design discipline describes how to develop a design model. The design model represents the intent of the implementation, and is the primary input to the Implementation discipline.
- The Test discipline describes how to integration test each build during the integration of the system. It also describes how to test the system to verify that all requirements have been met, as well as how defects are detected and submitted.
- The Project Management discipline describes how to best plan the project. Important aspects of the planning process are the iteration plan, change management and defect tracking systems.
Related Book Content
For exercices, Cyber-Readings or further readings about the Implementation Discipline, refer the the following book Chapter: Software Engineering Process – with the UPEDU, Chapter VI: The Implementation Discipline