{[ promptMessage ]}

Bookmark it

{[ promptMessage ]}

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

Info icon This 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
Image of page 1

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

View Full Document Right 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
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
Image of page 3

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

View Full Document Right 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
Image of page 4
10 5 Structured Design Models Figure 10-1
Image of page 5

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

View Full Document Right 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
Image of page 6
10 7 DFD with Automation System Boundary Figure 10-2
Image of page 7

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

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

{[ snackBarMessage ]}

What students are saying

  • Left Quote Icon

    As a current student on this bumpy collegiate pathway, I stumbled upon Course Hero, where I can find study resources for nearly all my courses, get online help from tutors 24/7, and even share my old projects, papers, and lecture notes with other students.

    Student Picture

    Kiran Temple University Fox School of Business ‘17, Course Hero Intern

  • Left Quote Icon

    I cannot even describe how much Course Hero helped me this summer. It’s truly become something I can always rely on and help me. In the end, I was not only able to survive summer classes, but I was able to thrive thanks to Course Hero.

    Student Picture

    Dana University of Pennsylvania ‘17, Course Hero Intern

  • Left Quote Icon

    The ability to access any university’s resources through Course Hero proved invaluable in my case. I was behind on Tulane coursework and actually used UCLA’s materials to help me move forward and get everything together on time.

    Student Picture

    Jill Tulane University ‘16, Course Hero Intern