Structure Charts Agenda: Use of Structure Charts Symbols How to create.

Slides:



Advertisements
Similar presentations
Chapter 10: The Traditional Approach to Design
Advertisements

Systems Analysis and Design in a Changing World, Fifth Edition
Structured Design. 2 Design Quality – Simplicity “There are two ways of constructing a software design: One is to make it so simple that there are obviously.
Chapter 3: Modularization
Chapter 2: Modularization
Describing Process Specifications and Structured Decisions Systems Analysis and Design, 7e Kendall & Kendall 9 © 2008 Pearson Prentice Hall.
1 Software Design Introduction  The chapter will address the following questions:  How do you factor a program into manageable program modules that can.
Traditional Approach to Design
UNIT 2. Introduction to Computer Programming
Programming Logic and Design Fourth Edition, Introductory
ALGORITHMS THIRD YEAR BANHA UNIVERSITY FACULTY OF COMPUTERS AND INFORMATIC Lecture two Dr. Hamdy M. Mousa.
Chapter 10 The Traditional Approach to Design
©2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart 6-1 Systems Development and Documentation Techniques.
Chapter 9: The Traditional Approach to Design Chapter 10 Systems Analysis and Design in a Changing World, 3 rd Edition.
Flow Chart.
What is Software Design?  Introduction  Software design consists of two components, modular design and packaging.  Modular design is the decomposition.
Copyright Irwin/McGraw-Hill Software Design Prepared by Kevin C. Dittman for Systems Analysis & Design Methods 4ed by J. L. Whitten & L. D. Bentley.
Software Design Deriving a solution which satisfies software requirements.
Chapter 2- Visual Basic Schneider
© Copyright 2011 John Wiley & Sons, Inc.
Summary Class responsibility cards can be used to help allocate responsibilities between different classes. The use of stereotype classes, such as entity,
Software Architecture Design Instructor: Dr. Jerry Gao.
Jump to first page 1 System Design (Finalizing Design Specifications) Chapter 3d.
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design Copyright 2000 © John Wiley & Sons, Inc. All rights reserved. Slide 1 Key.
SE-565 Software System Requirements More UML Diagrams.
Algorithm & Flowchart.
Structure Charts Agenda: Use of Structure Charts Symbols How to create.
Systems Analysis and Design
System Implementation System Implementation - Mr. Ahmad Al-Ghoul System Analysis and Design.
Chapter 9 Moving to Design. The Structured Approach To Designing The Application Architecture Module-an identifiable component of a computer program that.
INTRODUCTION TO PROGRAMMING STRUCTURE Chapter 4 1.
Describing Process Specifications and Structured Decisions Systems Analysis and Design, 7e Kendall & Kendall 9 © 2008 Pearson Prentice Hall.
Chapter 9 Moving to Design
10 ITK261 The traditional approach to design Reading: Chapter 10 Oct 9, 11.
10 The traditional approach to design Hisham Alkhawar.
1 IPC144 Session 4 Flowcharts. 2 Objectives: By the end of this session, the student will be able to: List the three elements of the Structure Theorem.
설계(Design) 구조도 허준영.
Systems analysis and design, 6th edition Dennis, wixom, and roth
System Implementation
Chapter 12: Design Phase n 12.1 Design and Abstraction n 12.2 Action-Oriented Design n 12.3 Data Flow Analysis n Data Flow Analysis Example n
1 ITEC 2010 Chapter 9 – Design The Structure Chart Structure chart –A hierarchical diagram showing the relationships between the modules of a.
Chapter 10 Software Engineering. Understand the software life cycle. Describe the development process models. Understand the concept of modularity in.
1 DATA FLOW DIAGRAM. 2 Outline Process decomposition diagrams Data flow diagram (DFD)
CCSB223/SAD/CHAPTER131 Chapter 13 Designing the System Internals.
SOFTWARE DESIGN. INTRODUCTION There are 3 distinct types of activities in design 1.External design 2.Architectural design 3.Detailed design Architectural.
First Steps in Modularization. Simple Program Design, Fourth Edition Chapter 8 2 Objectives In this chapter you will be able to: Introduce modularization.
Chapter 16 Quality Assurance Through Software Engineering Systems Analysis and Design Kendall & Kendall Sixth Edition.
Systems Design.  Application Design  User Interface Design  Database Design.
IPC144 Session 4 Flowcharts 1. Objectives: By the end of this session, the student will be able to: List the three elements of the Structure Theorem Identify.
System Development And Analysis. MOVING FROM LOGICAL TO PHYSICAL PROCESS MODELS Analysis phase – focus on logical processes and data flows Design phase.
SYSTEM ANALYSIS AND DESIGN SAFAA S.Y. DALLOUL. DESIGN THE PROGRAM.
IPC144 Session 4 Flowcharts 1. Objectives: By the end of this session, the student will be able to: List the three elements of the Structure Theorem Identify.
Copyright © 2011 Pearson Education Process Specifications and Structured Decisions Systems Analysis and Design, 8e Kendall & Kendall Global Edition 9.
Structure Charts. Graphical representation of the logic of the program, the decisions made, where they are made, the alternative paths, the data stores,
CSE 110: Programming Language I Matin Saad Abdullah UB 404.
Systems Analysis and Design in a Changing World, Fourth Edition
Chapter 1: Quick Revision of System/Software Analysis and Design Tools
Diagramming Techniques
System Design and Modeling
Diagramming Techniques
Programming Flowcharts
Computer Programming Flowchart.
Systems Analysis and Design
2.0 Problem Solving PROGRAM DESIGN
Programming Fundamentals
Activity Diagrams Activity diagrams describe the workflow behavior of a system.  The diagrams describe the state of activities by showing the sequence.
Designing and Debugging Batch and Interactive COBOL Programs
Software Design Designing the overall structure (architecture) of a software system Designing small pieces of computation Designing non-automated processes.
Structure Charts Agenda: What are Structure Charts
Structure Charts.
Presentation transcript:

Structure Charts Agenda: Use of Structure Charts Symbols How to create

Structure Chart Use Describe functions and sub-functions of each part of system (in more detail than a DFD) Show relationships between common and unique modules of a computer program Hierarchical, Modular structure Each layer in a program performs specific activities Each module performs a specific function

Structure Chart Symbols Structure Chart symbols represent Modules (sequential logic) Conditions (decision logic) Loops (iterative logic) Data couples Control couples

Structure Chart - Module Rectangle represents a module (program or subroutine) Control Modules (mainline) branch to sub-modules Library modules are reusable and can be invoked from more than one Control Module elsewhere in the system

Structure Chart - Data Couple Arrow with an empty circle Shows the data one module passes to another

Structure Chart - Control Couple Arrow with filled circle Shows a message (flag) which one module sends to another Module uses a flag to signal a specific condition or action to another module

Structure Chart - Condition A line with a diamond Indicates that a control module determines which subordinate module will be invoked

Structure Chart - Loop A curved arrow representing a loop One or more modules are repeated

Structure Chart for Calculate Pay Amount Routine Figure 9-9

Structure Chart for Entire Calculate Payroll Program Figure 9-11

Steps in drawing a structure chart Review the DFDs and object models Identify modules and relationships Add couples, loops, and conditions Analyze the structure chart, the DFDs, and the data dictionary Example: Order System DFD Order System Structure Chart

Summary - Structure Charts Show the relationships among program modules Structure Chart consists of: Modules - Related program code organized into small units that are easy to understand and maintain Data couples - Data passed between modules Control couples - Data passed between modules that indicates a condition or action to another module (e.g. End of File) Conditions - determines what subordinate module a control module will run Loops - Indicates one or more subordinate modules are repeated Structure Charts are based on the DFD and Data Dictionary