Design
In systems design the design functions and operations are described in detail, including screen layouts, business rules, process diagrams and other documentation. The output of this stage will describe the new system as a collection of modules or subsystems.
The design stage takes as its initial input the requirements identified in the approved requirements document. For each requirement, a set of one or more design elements will be produced as a result of interviews, workshops, and/or prototype efforts.
Design elements describe the desired software features in detail, and generally include functional hierarchy diagrams, screen layout diagrams, tables of business rules, business process diagrams, pseudocode, and a complete entity-relationship diagram with a full data dictionary. These design elements are intended to describe the software in sufficient detail that skilled programmers may develop the software with minimal additional input design.
The design stage takes as its initial input the requirements identified in the approved requirements document. For each requirement, a set of one or more design elements will be produced as a result of interviews, workshops, and/or prototype efforts.
Design elements describe the desired software features in detail, and generally include functional hierarchy diagrams, screen layout diagrams, tables of business rules, business process diagrams, pseudocode, and a complete entity-relationship diagram with a full data dictionary. These design elements are intended to describe the software in sufficient detail that skilled programmers may develop the software with minimal additional input design.
There are several tools and techniques used for designing. These tools and techniques are:
1-Flowchart
2-Data flow diagram (DFDs)
3-Data dictionary
4-Structured English
5-Decision table
6-Decision tree
Benefits:
1-Improved system performance; individually tailored configuration advice demonstrates where improvement is necessary, and how to improve the system to regain lost performance.
2-Customers gain a detailed understanding of how their users use their system. This Usage Profile can be leveraged to develop future architecture changes.
3-Potential to learn of future concerns, allowing customers to take proactive measures to avoid problems.
4-A baseline performance level is established against which benefits can be compared and changes to the system predicted or foreseen.
1-Flowchart
2-Data flow diagram (DFDs)
3-Data dictionary
4-Structured English
5-Decision table
6-Decision tree
Benefits:
1-Improved system performance; individually tailored configuration advice demonstrates where improvement is necessary, and how to improve the system to regain lost performance.
2-Customers gain a detailed understanding of how their users use their system. This Usage Profile can be leveraged to develop future architecture changes.
3-Potential to learn of future concerns, allowing customers to take proactive measures to avoid problems.
4-A baseline performance level is established against which benefits can be compared and changes to the system predicted or foreseen.
