Structure Charts.

Slides:



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

Systems Analysis and Design in a Changing World, Fifth Edition
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
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.
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.
ITEC113 Algorithms and Programming Techniques
Chapter 2- Visual Basic Schneider
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall Process Specifications and Structured Decisions Systems Analysis and Design, 8e Kendall.
© 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,
1 STRUCTURE CHARTS Elements and Definitions. 2 Software System Design translates SRS into a ===> software system architecture: –system’s static structure.
Chapter 9 Describing Process Specifications and Structured Decisions
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.
Kendall & KendallCopyright © 2014 Pearson Education, Inc. Publishing as Prentice Hall 9 Kendall & Kendall Systems Analysis and Design, 9e Process Specifications.
Chapter 3 Planning Your Solution
The Program Design Phases
PRE-PROGRAMMING PHASE
Algorithm & Flowchart.
Structure Charts Agenda: Use of Structure Charts Symbols How to create.
Systems Analysis and Design
Kendall & KendallCopyright © 2014 Pearson Education, Inc. Publishing as Prentice Hall 9 Kendall & Kendall Systems Analysis and Design, 9e Process Specifications.
System Implementation System Implementation - Mr. Ahmad Al-Ghoul System Analysis and Design.
Chapter 9 Describing Process Specifications and Structured Decisions
Design the program Create a detailed description of program –Use charts or ordinary language (pseudocode) Identify algorithms needed –Algorithm: a step-by-step.
Describing Process Specifications and Structured Decisions Systems Analysis and Design, 7e Kendall & Kendall 9 © 2008 Pearson Prentice Hall.
10 ITK261 The traditional approach to design Reading: Chapter 10 Oct 9, 11.
10 The traditional approach to design Hisham Alkhawar.
Programming Concepts Chapter 3.
© 2011 Pearson Addison-Wesley. All rights reserved. Addison Wesley is an imprint of Stewart Venit ~ Elizabeth Drake Developing a Program.
설계(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.
Dale Roberts 1 Program Control - Algorithms Department of Computer and Information Science, School of Science, IUPUI CSCI N305.
1 DATA FLOW DIAGRAM. 2 Outline Process decomposition diagrams Data flow diagram (DFD)
First Steps in Modularization. Simple Program Design, Fourth Edition Chapter 8 2 Objectives In this chapter you will be able to: Introduce modularization.
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.
Introduction to Flow Chart It is pictorial representation of process of a system or processes. Types of Flow charts –Program Flow Chart –System Flow chart.
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.
ICS124 Session 9 Flowcharting 1. By the end of this section the student will be able to:  Name the three structures of the Structure Theorem  Identify.
Copyright © 2011 Pearson Education Process Specifications and Structured Decisions Systems Analysis and Design, 8e Kendall & Kendall Global Edition 9.
CSE 110: Programming Language I Matin Saad Abdullah UB 404.
 Problem Analysis  Coding  Debugging  Testing.
Systems Analysis and Design in a Changing World, Fourth Edition
Diagramming Techniques
System Design and Modeling
Diagramming Techniques
Systems Analysis and Design
Structure Charts Agenda: Use of Structure Charts Symbols How to create.
2.0 Problem Solving PROGRAM DESIGN
Designing and Debugging Batch and Interactive COBOL Programs
Unit# 9: Computer Program Development
Algorithms & Pseudocode
Structure Charts Agenda: What are Structure Charts
Chapter 11 Describing Process Specifications and Structured Decisions
WJEC GCSE Computer Science
Presentation transcript:

Structure Charts

Structure Chart is an important tool for showing relationship between the modules of a computer program in SSAD (Structured Systems Analysis and Design) [Page-Jones, 1988].

Structure Charts 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) In contrast to flow chart, Structure Charts does not represent sequence of execution. However, this problem can be solved by following the rule of “reading from left to right”

Structure Chart Use 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 Symbols Module Control Modules Library Modules Modules is a program or subroutine containing sequential logic: a form of binary circuit design that employs one or more inputs and one or more outputs, whose states are related by defined rules.

Structure Chart - Module 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 Symbols Module Invocation Arrow (only from main to sub) Data Flow Arrow / data couple Control Flow Arrow/ control couple

Structure Chart Module Invocation Arrow

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 Symbols Conditions (decision logic) A line with a diamond Indicates that a control module determines which subordinate module will be invoked

Structure Chart - Condition One of these three subordinate module will be executed based on the output from the control module (sort inventory parts)

Structure Chart Symbols Loops(iterative logic) Can only be drawn in module invocation arrow. Indicating that the control module actions will be repeated until a certain flag or user input.

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

Structure Chart for Calculate Pay Amount Routine

Structure Chart for Entire Calculate Payroll Program

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

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

Sampai jumpa minggu depan Terima kasih Sampai jumpa minggu depan