Satzinger_Ch10

Satzinger_Ch10 - 10 Chapter 10 The Traditional Approach to...

Info iconThis preview shows pages 1–8. Sign up to view the full content.

View Full Document Right Arrow Icon
10 Chapter 10 The Traditional Approach to Design Systems Analysis and Design in a Changing World, 5th Edition
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
10 2 Learning Objectives Describe the steps involved in the traditional approach to designing the application architecture Develop a system flowchart Develop a structure chart using transaction analysis and transform analysis Write pseudocode for structured modules Explain how to use three-layer design with the traditional approach
Background image of page 2
10 3 Overview Traditional approach to designing software Overview of structured models, model development process, related terminology How data flow diagrams are annotated with automation boundary information How analysis phase models are transformed into design models using system flowcharts, structure charts, and module pseudocode Integration into other design phase activities Applying approach to a three-layer architecture
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
10 4 The Structured Approach to Designing the Application Architecture Application software programs Designed in conjunction with database and user interface Hierarchy of modules Design internal logic of individual modules Top-down approach DFDs with automation boundaries System flowcharts, structure charts, pseudocode
Background image of page 4
10 5 Structured Design Models Figure 10-1
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
10 6 The Automation System Boundary Partitions data flow diagram processes into manual processes and automated systems Processes can be inside or outside boundary Data flows can be inside and outside of boundary Data flows that cross system boundary represent inputs and outputs of system Data flows that cross boundaries between programs represent program-to-program communication
Background image of page 6
10 7 DFD with Automation System Boundary Figure 10-2
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 8
This is the end of the preview. Sign up to access the rest of the document.

This document was uploaded on 02/22/2010.

Page1 / 36

Satzinger_Ch10 - 10 Chapter 10 The Traditional Approach to...

This preview shows document pages 1 - 8. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online