Implementation

An implementation document is prepared along with the software to present the packaging and component structure, including visible interfaces of components. This shows the structure of the final deliverables, and describes the files, databases and other persitent features of the system. This document will also identify all third-party components used …

more ...

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 ...

Good Design and Pragmatic Design

Kenny YoungBuck approaches the Master and asks, "What is good design?"

The Master replies, "Kenny, you innocent little monkey, it's a wonder you haven't joined a cult. Good design maximizes business value while minimizing costs including development, maintenance, adaptation and operation."

"Master, are there circumstances where this is not true …

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 ...


Essay 18 - What Is Your Problem?

We know something is wrong or can be improved, but we lack the will to drill into details and write a problem statement. It isn't a lack of ability, it is purely a lack of will.

A common source of serious issues with software comes from proposing a solution without …

more ...

Essay 23 - Jumping the Technology Ship

We're told, repeatedly, to avoid changing horses in mid-stream. We're told not to follow the crowd blindly.

Once upon a time, we made a technology decision that -- at the time -- was right. But things have shifted around a bit, and what was once prudence is now folly. When do you …

more ...