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 …

PJHyett asks

Why is it that selling points of newer langauges are features that Lisp had decades ago? Java has garbage collection, Ruby has closures, Perl is dynamically typed, etc. What the hell have we been doing this whole time besides reinventing the wheel?

Call me lazy, but I want …

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 …

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 …

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 …

Sometimes a column is not the atomic piece of data you thought it was. See Essay 10.1 for the first part of this rant, which address multi-dimensionality.

A second example of a column not being an atomic piece of data is when we have to support navigation through a …

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 …

There are two layers of use case authoring and minimal consensus on which level is "right" for any particular purpose.

1. Business Level use cases - ignore the presence or absence of a GUI, and pursue the business problem. This leaves designers free to create any GUI, perhaps one that is not …

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 …