Design

Content

The Design model generally consists of UML diagrams plus narratives where necessary. The model describes the static structure and dynamic behavior of each class. Additional non-behavioral requirements must also be included in the design document.

In the 4+1 view, the design is the details of how to implement …

more ...

Architecture

An architecture document not only describes the solution, it must trace back to individual functional requirements, and also should satisfy the non-functional requirements. In most cases, the requirements must be prioritized, and there will be tradeoffs for meeting absolutely all of the requirements.

In some cases, an architecture exists, and …

more ...

Requirements

Requirements describe the problem, and provide a direction for composing a solution. The remaining deliverables, leading up to the creation of software, are created from the requirements. These includes the architecture, design, implementation and deployment documents.

By defining the problem, the requirements document also serves to bracket the scope of …

more ...

Deliverables, Process and Standards

Software development evolves through four phases:

  1. Identification of a problem and inception of a project to implement a solution.
  2. Elaboration (analysis) of that problem to determine the most effective solution.
  3. Design of software to implement that solution.
  4. Implementation of the solution; installing and configuring software, training, and everything that goes …
more ...