Software Design Article Index for
Software 		Website Links For
Software Design 		 

Information About

Software Design
  CATEGORIES ABOUT SOFTWARE DESIGN
   
software development
   
project management
   
architecture and engineering occupations
   
design
   
APPAREL
BABY
BEAUTY
BOOKS
CAR TOYS
CELL PHONES
DVD'S
ELECTRONICS
GOURMET FOOD
GROCERIES
HEALTH & PERSONAL
HOME & GARDEN
JEWELRY
MUSIC
MUSIC INSTRUMENTS
OFFICE PRODUCTS
SOFTWARE
SPORTING GOODS
TOOLS & HARDWARE
TOYS
VIDEO GAMES
SHOPPING HOME
MORE SHOPPING...



The Software Requirements Analysis (SRA) step of a Software Development Process yields Specifications that are used in Software Engineering . If the software is "semiautomated" or User Centered , software design may involve User Experience Design yielding a Story Board to help determine those specifications. If the software is completely Automated (meaning no User or User Interface ), a software design may be as simple as a Flow Chart or text describing a planned sequence of events. There are also Semi-formal methods like Unified Modeling Language and Fundamental Modeling Concepts . In either case some Documentation of the plan is usually the product of the design.

A software design may be Platform-independent or Platform-specific , depending on the availability of the technology called for by the design.


DESIGN CONSIDERATIONS

There are many aspects to consider in the design of a piece of software. The importance of each should reflect the goals the software is trying to achieve. Some of these aspects are:

  • Extensibility - New capabilities can be added to the software without major changes to the underlying architecture.

  • Robustness - The software is able to operate under stress or tolerate unpredictable or invalid input. For example, it can be designed with a resilience to low memory conditions.

  • Reliability - The software is able to perform a required function under stated conditions for a specified period of time.

  • Fault-tolerance - The software is resistant to and able to recover from component failure.

  • Security - The software is able to withstand hostile acts and influences.

  • Maintainability - The software can be restored to a specified condition withing a specified period of time. For example, virus software may include the ability to periodically receive virus definition updates in order to maintain the software's effectiveness.

  • Compatibility - The software is able to operate with other products that are designed for interoperability with another product. For example, a piece of software may be backward-compatible with an older version of itself.




DESIGN PATTERNS

A software designer or architect may identify a design problem which has been solved by others before. A template or pattern describing a solution to a common problem is known as a design pattern. ( Design Pattern (computer Science) ). The reuse of such patterns can speed up the software development process, having been tested and proved in the past.


USAGE

Software Design Document ation may be reviewed or presented to allow constraints, specifications and even requirements to be adjusted prior to Programming . Redesign may occur after review of a programmed Simulation or Prototype . It is possible to design software in the process of programming, without a plan or requirement analysis, but for more complex projects this would not be considered a professional approach. A separate design prior to programming allows for Multidisciplinary designers and Subject Matter Expert s (SMEs) to collaborate with highly-skilled programmers for software that is both useful and technically sound.


SEE ALSO