|
STRUCTURE CHARTS AND ROBUST PROCESS DESIGN |
|
|
|
Process Design is a structured approach that has proven to be effective, economical, and enjoyable in creating robust software design. Without robust design, resulting systems may have: - Poor reliability - not meeting functional specs;
- Poor efficiency - not meeting performance specs;
- Poor maintainability - expensive to change; and
- Poor flexibility – not able to keep up with business and technology changes.
Application design occurs in three main stages:- Conceptual Design
- Process (Module) Design
- Detailed Logic (Algorithm) Design
Advanced Strategies offers courses covering all three stages. This course focuses on the second stage, process design, with emphasis on the effective use of functional decomposition and structure charts.
Course Outcomes:
Students of this course will return to work:
- Articulating the value of formal, robust system design to the success of the organization.
- With an easy, intuitive approach to speed up development.
- Prepared to break down the complexity and chaos of the design specification into something that can be more readily taken forward into development.
- With a framework for how structured design feeds both procedural detailed design and Object-oriented detailed design.
Course Outline:
Foundations
- What is Design?
- A Birdseye View
- Facts about Design
- Goals of Design
- Structured Process Design and Quality
|
Structured Process Design
- Product Characteristics: Modular, Hierarchical and Functional
- Process Characteristics: Iteration, Verification, Teamwork
|
Develop a Structured Design
- Functional Decomposition
- Intuitive Decomposition
- Tips
- Transform Analysis
- Transaction Analysis
- Data Driven Design
|
Evaluating a Design
- Quality Factors
- Feasibility
- Workability
- Robustness
- Correctness
|
Completing the Design Spec.
- Packaging Highlights
- Test Specifications
- Performance Goals
- Local Standards
- Design Tips
|
Taking it Forward
- Logic Design
- Procedural Design Strategies
- OO Design Strategies
- SOA Implications
- Coding and Testing
|
Who Should Attend:
The primary audience is Systems Analysts.
Course Duration:
Three Days
Class Availability:
Request It Now!
|