1 CS362 High Level Program Design Tool Structure Chart © 2011, Regis University.

Slides:



Advertisements
Similar presentations
10 Software Engineering Foundations of Computer Science ã Cengage Learning.
Advertisements

1 Software Design Introduction  The chapter will address the following questions:  How do you factor a program into manageable program modules that can.
Object-Oriented Application Development Using VB.NET 1 Chapter 5 Object-Oriented Analysis and Design.
Lecture Set 3E Introduction Basic Software Development Issues 1. Notes on Software Development 2. Intro to Software Development Tools 7/31/2008 2:43PM.
Creating a Document with a Table, Chart, and Watermark
Chapter 2- Visual Basic Schneider
Design Patterns in Java Appendix D UML at a Glance Summary prepared by Kirk Scott 1.
QUALITY TOOLS Tree Diagram. WHAT IS ? The tree diagram is used to break-up complex problems into smaller subproblems. Helps understand the complexity,
Chapter 1 Program Design
Object-oriented design Part 4: More UML. Interfaces An interface is a language construct specific to Java Java does not support multiple inheritance Interfaces.
Structure Charts Agenda: Use of Structure Charts Symbols How to create.
DCT 1123 PROBLEM SOLVING & ALGORITHMS INTRODUCTION TO PROGRAMMING.
System Implementation System Implementation - Mr. Ahmad Al-Ghoul System Analysis and Design.
“The Chemist’s Toolkit”
LESSON 8 Booklet Sections: 12 & 13 Systems Analysis.
© 2008 The McGraw-Hill Companies, Inc. All rights reserved. M I C R O S O F T ® Creating Diagrams with SmartArt Graphics Lesson 7.
Structured Programming Defn: This is an approach to program development that produces programs of high quality that are easy to test, debug, modify and.
The Pythagorean Theorem in 3D
Chapter 12 Describing Information Systems.
Interaction diagrams Sequence and collaboration diagrams.
CSC 221: Computer Programming I Fall 2001  top-down design  approach to problem solving, program design  focus on tasks, subtasks, …  reference parameters.
Copyright © 2009 Pearson Education, Inc. Publishing as Pearson Addison-Wesley STARTING OUT WITH Python Python First Edition by Tony Gaddis Chapter 3 Simple.
Copyright © 2008 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Starting Out with Programming Logic & Design First Edition by Tony Gaddis.
First Steps in Modularization Simple Program Design Third Edition A Step-by-Step Approach 8.
1 Introduction to Flowcharting. 2 Writing a program Defining the problem –Write down what the program will do Planning –Write down the steps, draw a flowchart.
1 Introduction to Flowcharting. 2 Writing a program Defining the problem –Write down what the program will do Planning –Write down the steps, draw a flowchart.
WS8.1-1 ANSYS, Inc. Proprietary © 2009 ANSYS, Inc. All rights reserved. April 28, 2009 Inventory # Workshop 8.1 Line and Surface Bodies DesignModeler.
ENGR-25_Programming-1.ppt 1 Bruce Mayer, PE Engineering/Math/Physics 25: Computational Methods Bruce Mayer, PE Registered Electrical.
I Power Higher Computing Software Development The Software Development Process.
Chapter 7 Software Engineering Introduction to CS 1 st Semester, 2015 Sanghyun Park.
Flowcharts and Algorithms. Review of Terms  A computer is a machine that can represent and manipulate data –Ultimately the data and the instructions.
Describing Information Systems.  A system is a group of connected operations.  Systems can be described in several different ways including:  Structure.
First Steps in Modularization. Simple Program Design, Fourth Edition Chapter 8 2 Objectives In this chapter you will be able to: Introduce modularization.
Chapter 8 Scheduling.
Chapter 8 First steps in modularisation. Objectives To introduce modularisation as a means of dividing a problem into subtasks To present hierarchy charts.
First Steps in Modularization. Simple Program Design, Fourth Edition Chapter 8 2 Objectives In this chapter you will be able to: Introduce modularization.
PROGRAM DEVELOPMENT CYCLE. Problem Statement: Problem Statement help diagnose the situation so that your focus is on the problem, helpful tools at this.
First Steps in Modularization. Simple Program Design, Fourth Edition Chapter 8 2 Objectives In this chapter you will be able to: Introduce modularization.
BTS430 Dialogue Charts Please run this as a presentation. It uses hyperlinks.
Use Flowchart modeling to design and create an interactive quiz to be run on Powerpoint. Start Question Click to start the quiz Correct Incorrect, try.
Chapter Topics 2.1 Designing a Program 2.2 Output, Input, and Variables 2.3 Variable Assignment and Calculations 2.4 Variable Declarations and Data Types.
Systems Design.  Application Design  User Interface Design  Database Design.
GE 121 – Engineering Design Engineering Design GE121 Managing The Design Process Part II Lecture 11B.
Diagram Editor Use Case Analysis Assumption: simple stand-alone, single user application. Three basic kinds of interaction of the user with the diagram.
Guide to Functional Decomposition
Designing User Experience (UX) This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License.Creative Commons.
An Introduction to Programming with C++1 Beginning the Problem- Solving Process Tutorial 2.
CSE 110: Programming Language I Matin Saad Abdullah UB 404.
Presentation On Critical Path Analysis Project Management Series – 1 Powered by: Jazz PresentationJazz Presentation.
Systems Analysis and Design in a Changing World, Fourth Edition
Structured Programming
Objectives The student will be able to:
16.5 Electrical Circuits.
Structure Charts Agenda: Use of Structure Charts Symbols How to create.
Starting Out with Programming Logic & Design
Unit# 9: Computer Program Development
Chapter 3 Simple Functions
Structured Programming
Reducing Fractions.
Problem Solving: Structure Charts
Designing User Experience (UX)
Structure Charts Agenda: What are Structure Charts
Project Planning By Phaik San Liew.
Starting Out with Programming Logic & Design
Area of Irregular Shapes
IPC144 Introduction to Programming Using C Week 4 – Lesson 2
Top-Down Design & JSP Skill Area Part D
Lesson 1-5 Chemistry Problem Solving Metric and Unit Conversions
Information System Design
Structure Charts.
Presentation transcript:

1 CS362 High Level Program Design Tool Structure Chart © 2011, Regis University

2 Structure Charts A structure chart purpose: Shows only WHAT tasks your program will do (not HOW it will complete them)

3 Structure Charts Structure charts are hierarchical diagrams They diagram the overall program structure They show the relationship between all the tasks (functions) in the program They indicate which data is shared by the tasks (functions)

4 Creating a Structure Chart A large program design is first broken into tasks Tasks are repeatedly divided into even smaller subtasks Rectangles are used to represent tasks/subtasks within the program Lines are used to hierarchically connect the tasks/sutasks Subtasks are diagrammed below the task that they are part of Task SubTask1SubTask2

5 Creating a Structure Chart An upward arrow indicates that the data value has been set inside the task and is being passed out for use by other tasks. A downward arrow indicates a data value previously set in some other task is now being passed into this task. Data may also be passed both into a task (downward arrow), modified, and passed back out again (upward arrow). Task SubTask1SubTask2 Data1 The passing of data between tasks is shown by arrows going up from or down to the task’s rectangle

6 Sample Structure Chart main getInputprocessDatadisplayResults data result data result Given a generic program that reads some data from the user, runs some calculations using that data, and displays results to the user, the structure chart could look like this:

7 Expanded Example If the processData task is complicated, it may be broken down into further sub-tasks. The structure chart could look like this: main getInputprocessDatadisplayResults data result data result convertDataanalyzeData result data

8 In Summary Put starting function in a rectangle root of an upside-down tree. Determine the main subtasks that must be performed by the program to solve the problem. Put main subtasks in rectangles below the root, and draw a connecting line from the root to each subtask. Examine each subtask individually, and break them down into even smaller tasks. Put subtasks in rectangles below the task that they are part of, and draw a connecting line from task to subtask. Repeat until the bottom tasks of the tree are very simple tasks to complete