Traditional Approach to Design

Slides:



Advertisements
Similar presentations
1 9 Moving to Design Lecture Analysis Objectives to Design Objectives Figure 9-2.
Advertisements

Chapter 10: The Traditional Approach to Design
Systems Analysis and Design in a Changing World, Fifth Edition
Systems Development Environment
CSC 123 Systems Analysis & Design
Design Concepts and Principles
Using Dataflow Diagrams
1 Software Design Introduction  The chapter will address the following questions:  How do you factor a program into manageable program modules that can.
Chapter 10 The Traditional Approach to Design
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.
Software Design Deriving a solution which satisfies software requirements.
8.
© Copyright 2011 John Wiley & Sons, Inc.
Chapter 9 Using Data Flow Diagrams
Systems Analysis and Design in a Changing World, 6th Edition
L ECTURE 9 – PROCESS MODELLING PART 1 Data Flow Diagrams for Process Modelling Multi-level Data Flow Diagrams Logical Vs Physical DFDs Steps to Construct.
Software Design Description (SDD) Diagram Samples
6 Systems Analysis and Design in a Changing World, Fourth Edition.
Chapter 7: The Object-Oriented Approach to Requirements
Traditional Approach to Requirements Data Flow Diagram (DFD)
Chapter 6: The Traditional Approach to Requirements
System Analysis Overview Document functional requirements by creating models Two concepts help identify functional requirements in the traditional approach.
Systems Analysis and Design in a Changing World, Fifth Edition
PROCESS MODELING Chapter 8 - Process Modeling
2 Approaches to Requierements Engineering Reference: Systems Analysis and Design in a Changing World, 3 rd Edition, chapter 2 and chapter 6.
Chapter 6 The Traditional Approach to Requirements
System Implementation System Implementation - Mr. Ahmad Al-Ghoul System Analysis and Design.
The Design Discipline.
Systems Analysis and Design in a Changing World, Fifth Edition
INFO415 Approaches to System Development: Part 2
Traditional Approach to Requirements
Systems Analysis and Design in a Changing World, Fifth Edition
Irwin/McGraw-Hill Copyright © 2004 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS6th Edition.
Chapter 9 Moving to Design. The Structured Approach To Designing The Application Architecture Module-an identifiable component of a computer program that.
PHASE 4 SYSTEMS IMPLEMENTATION Application Development SYSTEMS ANALYSIS & DESIGN.
Chapter 7 Structuring System Process Requirements
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 10Slide 1 Architectural Design l Establishing the overall structure of a software system.
 2004 by SEC Chapter 4 Software Design. 2  2004 by SEC Chapter 4 Software Design 4.1 Design Fundamentals 4.2 Design Method 4.3 Architecture Design
Software Design Designing the overall structure (architecture) of a software system Designing small pieces of computation Designing non-automated processes.
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 Systems Analysis and Design in a Changing World, Thursday, January 18, 2007.
Systems Analysis and Design in a Changing World, 3rd Edition
6 Systems Analysis and Design in a Changing World, Fifth Edition.
Systems analysis and design, 6th edition Dennis, wixom, and roth
1 6 Systems Analysis and Design in a Changing World, 2 nd Edition, Satzinger, Jackson, & Burd Chapter 6 The Traditional Approach to Requirements.
1 ITEC 2010 Chapter 9 – Design The Structure Chart Structure chart –A hierarchical diagram showing the relationships between the modules of a.
9 Systems Analysis and Design in a Changing World, Fourth Edition.
Computing and SE II Chapter 9: Design Methods and Design Models Er-Yu Ding Software Institute, NJU.
CCSB223/SAD/CHAPTER131 Chapter 13 Designing the System Internals.
Design Methods Instructor: Dr. Jerry Gao. Software Design Methods Design --> as a multistep process in which we design: a) data structureb) program structure.
Systems Design.  Application Design  User Interface Design  Database Design.
6 Systems Analysis and Design in a Changing World, Fourth Edition.
System Development And Analysis. MOVING FROM LOGICAL TO PHYSICAL PROCESS MODELS Analysis phase – focus on logical processes and data flows Design phase.
Systems Development Lifecycle
1 7 Systems Analysis and Design in a Changing World, 2 nd Edition, Satzinger, Jackson, & Burd Chapter 7 The Object-Oriented Approach to Requirements.
Structure Charts. Graphical representation of the logic of the program, the decisions made, where they are made, the alternative paths, the data stores,
SOFTWARE DESIGN & SOFTWARE ENGINEERING Software design is a process in which data, program structure, interface and their details are represented by well.
11 Systems Analysis and Design in a Changing World, Fifth Edition.
 Problem Analysis  Coding  Debugging  Testing.
Systems Analysis and Design in a Changing World, Fourth Edition
Chapter 6 The Traditional Approach to Requirements.
System Design.
Lecture 9- Design Concepts and Principles
Unit# 9: Computer Program Development
Software Design Designing the overall structure (architecture) of a software system Designing small pieces of computation Designing non-automated processes.
Lecture 9- Design Concepts and Principles
SYSTEMS ANALYSIS & DESIGN
Presentation transcript:

Traditional Approach to Design Chapter 10 Traditional Approach to Design

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

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

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

Structured Design Models

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

DFD with Automation System Boundary (Figure 10-2)

The System Flowchart Representation of various computer programs, files, databases, and associated manual processes that make up complete system Frequently constructed during analysis activities Graphically describes organization of subsystems into automated and manual components Can show type of transaction processing system Batch Real-time

Common System Flowchart Symbols

Sample System Flowchart for Payroll System (Figure 10-4)

The Structure Chart Describes functions and sub-functions of each part of system Shows relationships between modules of a computer program Simple and direct organization Each module performs a specific function Each layer in a program performs specific activities Chart is tree-like with root module and branches

A Simple Structure Chart for the Calculate Pay Amounts Module

Structure Chart Symbols

Structure Chart for Entire Payroll Program

Developing a Structure Chart Transaction analysis Uses system flow chart and event table inputs Upper-level modules developed first Identifies each transaction supported by program Transform analysis Uses DFD fragments for inputs Computer program “transforms” inputs into outputs Charts have input, calculate, and output sub-trees

High-Level Structure Chart for the Order-Entry Subsystem After Transaction Analysis

Steps to Create a Structure Chart from a DFD Fragment Determine primary information flow Main stream of data transformed from some input form to output form Find process that represents most fundamental change from input to output Redraw DFD with inputs to left and outputs to right – central transform process goes in middle Generate first draft of structure chart based on redrawn data flow

The Create New Order DFD Fragment

Decomposed DFD for Create New Order

Rearranged Create New Order DFD

First Draft of the Structure Chart for Create New Order (Figure 10-14)

Steps to Create a Structure Chart from a DFD Fragment (continued) Add other modules Get input data via user-interface screens Read from and write to data storage Write output data or reports Add logic from structured English or decision tables Make final refinements to structure chart based on quality control concepts

The Structure Chart for the Create New Order Program (Figure 10-15)

Combination of Structure Charts: Transaction and Transform Analysis

Evaluating the Quality of a Structure Chart Module coupling Measure of how module is connected to other modules in program Goal is to be loosely coupled (independent) Module cohesion Measure of internal strength of module Module performs one defined task Goal is to be highly cohesive

Module Algorithm Design—Pseudocode Describes internal logic of software modules Variation of structured English that is closer to programming code Syntax should mirror development language Three types of control statements used in structured programming Sequence – sequence of executable statements Decision – if-then-else logic Iteration – do-until or do-while

Integrating Structured Application Design with Other Design Tasks Structure chart must be modified or enhanced to integrate design of user interface and database Are additional modules needed? Does pseudocode in modules need modification? Are additional data couples needed to pass data? Structure charts and system flowcharts must correspond to planned network architecture Required protocols, capacity, and security

Three-Layer Design Three-layer architecture View layer, business logic layer, and data layer Structure charts and system flowcharts describe design decisions and software structuring Employs multiple programs for user interface, business logic, and data access modules Modules in different layers communicate over real- time links using well-defined protocols

System Flowchart Showing Three-Layer Architecture for Customer Order

Structure Chart Showing Three-Layer Architecture for Create New Order (Figure 10-20)