Home arrow Practices arrow Page 4 - The Art Of Software Development (part 2): Designing For Simplicity

Drawing Class - Practices

In the first part of this article, you got a crash course inrequirements analysis. Now that you've figured out what your customerneeds, it's time to design it - easily the most challenging and creativephase of the project cycle. Find out more, inside.

TABLE OF CONTENTS:
  1. The Art Of Software Development (part 2): Designing For Simplicity
  2. The Best Laid Plans...
  3. Building Blocks
  4. Drawing Class
  5. All Used Up
  6. Testing Times
  7. Different Strokes, Different Folks
By: Vikram Vaswani, (c) Melonfire
Rating: starstarstarstarstar / 4
September 03, 2002

print this article
SEARCH DEV SHED

TOOLS YOU CAN USE

advertisement
Typically, a software design document contains the following sections,each of which is designed to address different components of thesoftwarearchitecture:
  1. Introduction: This section provides an introduction to the softwarebeing developed, together with background, scope, definitions andreferences.
  2. Application overview: This discusses the application to be developedin general, together with a broad description of software concepts andfunctions.
  3. Constraints, considerations and goals: This section describes theconstraints and guidelines to be kept in mind when designing theapplication. It includes details about the hardware and softwareavailable, the development and execution environment, user profiles,performance and security considerations, data storage and formatconstraints, together with a list of important rules to be kept in mindwhile designing the software (and the basis of each).
  4. Design strategy: This section provides information on the programmingparadigms used when designing the software. It includes information onthe IDE or programming language used, the techniques used for datastorage, interprocess communication, flow control, exception handling,resource management, garbage collection and traffic management.
  5. System architecture: This contains high-level architectural diagramsof the system design, together with descriptions of the components usedand their relationships via a modeling language. A description of thevarious modules that make up the system is also included.
  6. Component architecture: Each of the modules that makes up the systemneeds to be described in greater detail. This section may therefore befurther split into sub-sections, each one containing a detaileddescription of the internals of the various modules that make up theoverall system. These details include information on the purpose of eachcomponent, its functions, its data input and output formats, its inputand output interfaces, its internal business logic, and its interactionwith other components. You can include pseudo-code wherever needed toensure that the details are clearly communicated.
This document serves as the basis for the developer or developmentteam's efforts, and should be reviewed at least once to identify andcorrect design flaws, if any exist, before beginning work.

 
 
>>> More Practices Articles          >>> More By Vikram Vaswani, (c) Melonfire
 

blog comments powered by Disqus
escort Bursa Bursa escort Antalya eskort
   

PRACTICES ARTICLES

- Calculating Development Project Costs
- More Techniques for Finding Things
- Finding Things
- Finishing the System`s Outlines
- The System in So Many Words
- Basic Data Types and Calculations
- What`s the Address? Pointers
- Design with ArgoUML
- Pragmatic Guidelines: Diagrams That Work
- Five-Step UML: OOAD for Short Attention Span...
- Five-Step UML: OOAD for Short Attention Span...
- Introducing UML: Object-Oriented Analysis an...
- Class and Object Diagrams
- Class Relationships
- Classes

Developer Shed Affiliates

 


Dev Shed Tutorial Topics: