September 2007
M T W T F S S
« Aug   Oct »
 12
3456789
10111213141516
17181920212223
24252627282930

Basic objective of a High Level Design Document




High level software design, also called software architecture is the first step to analyze and consider all requirements for a software and attempt to define a structure which is able to fulfill them. For this also the non-functional requirements have to be considered, such as scalability, portability and maintainability. This first design step has to [...]



Software Design Document Outline and Template




For a design document to be comprehensive, and to actually meet the needs of the project rather than just being a piece of paper written to meet a statutory process need such as ISO and CMM, the design document needs to have a correct format, and be well understood by the team members who are [...]



Basics of software design documentation




Designing software is an exercise in managing complexity. The complexity exits within the software design itself, within the software organization of the company, and within the industry as a whole. Software design is a difficult and error prone process. For many projects, software is so complex that there are plenty of different design aspects and [...]



Terms used in the Rational Unified Process




There are a whole host of terms that are employed in the Rational Unified Process, and the attempt below is to explain some of them. If you find terms missing, please let me know.

Iterations: Each phase in the Rational Unified Process can be further broken down into iterations. An iteration is a complete development [...]