1 TRANSFORM ANALYSIS Heuristics and Rules. 2 DFD with Transform Flow Characteristics input-driven output-driven center of transformation.

Slides:



Advertisements
Similar presentations
Ch-11 Project Execution and Termination. System Testing This involves two different phases with two different outputs First phase is system test planning.
Advertisements

MAPPING DATA FLOW DIAGRAMS INTO STRUCTURE CHARTS
Design Concepts and Principles
1 Software Design Introduction  The chapter will address the following questions:  How do you factor a program into manageable program modules that can.
Analysis Modeling.
1 SOFTWARE DESIGN QUALITY COHESION and COUPLING (Part II)
Design Phase What’s design?
Copyright Irwin/McGraw-Hill Software Design Prepared by Kevin C. Dittman for Systems Analysis & Design Methods 4ed by J. L. Whitten & L. D. Bentley.
Data-Flow Oriented Design
1 © University of Sunderland IMSE Lecture 4 u so far all our structure charts have been produced from an English description, e.g. - night on the town.
1 STRUCTURE CHARTS Elements and Definitions. 2 Software System Design translates SRS into a ===> software system architecture: –system’s static structure.
1 STRUCTURE CHARTS An Example: The Registration System.
1 SOFTWARE DESIGN QUALITY COHESION and COUPLING (Part I)
1 SYSTEM and MODULE DESIGN Elements and Definitions.
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.
IMSE Lecture Week 6 - Low Level Design Summary of last week: u Transform Analysis - 4 steps: 1 annotate the DFD (without redrawing it) 2 draw the intermediate.
1 PROCESS SPECIFICATIONS for DFDs Concepts and Examples.
Software Engineering CSE470: Systems Engineering 35 Computer System Engineering Computer System Engineering is a problem-solving activity. Itemize desired.
1 PROCESS SPECIFICATIONS for DFDs Concepts and Examples.
Data Flow Diagrams "Business process flow" not a Flow Chart.
Chapter 10: Architectural Design
Data Flow Diagrams BCA Sem IV K.I.R.A.S.
Systems Analysis and Design
Modeling the system the data flow diagram the context diagram level decomposition the cornucopia case portfolio project Systems Analysis and Design for.
Software Engineering Data flow diagrams.
INTRO TO INFORMATION SYSTEMS DEVELOPMENT IS 340 BY CHANDRA S. AMARAVADI 1.
System Implementation System Implementation - Mr. Ahmad Al-Ghoul System Analysis and Design.
สาขาวิชาเทคโนโลยี สารสนเทศ คณะเทคโนโลยีสารสนเทศ และการสื่อสาร.
1 Ref: Prof Sarda Process Modeling…… Lecture Outline Data flow diagram (DFD)
1 Chapter 14 Architectural Design 2 Why Architecture? The architecture is not the operational software. Rather, it is a representation that enables a.
Two Approaches to System Development
Software Design Designing the overall structure (architecture) of a software system Designing small pieces of computation Designing non-automated processes.
Systems analysis and design, 6th edition Dennis, wixom, and roth
TCS2411 Software Engineering1 Data-Flow Oriented Design “From DFD to Structure Chart”
Intro to Software System Modeling
SIM3302 SOFTWARE DESIGN & TESTING
PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.
1 DATA FLOW DIAGRAM. 2 Outline Process decomposition diagrams Data flow diagram (DFD)
ARCHITECTURAL DESIGN. Why is Architecture Important? Representations of software architecture are an enabler for communication between all parties (stakeholders)
CCSB223/SAD/CHAPTER131 Chapter 13 Designing the System Internals.
1 CMPT 275 High Level Design Phase Modularization.
Functional Modeling Joseph Valacich, Joey George and Jeff Hoffer, Essentials of System Analysis and Design, 4 th edition, Prentice Hall, 2009.
Design Methods Instructor: Dr. Jerry Gao. Software Design Methods Design --> as a multistep process in which we design: a) data structureb) program structure.
Flexible Registration for Community Education Dottie Marron Delivery Center Manager Student Administrative Services Consulting Center.
1 DATA FLOW DIAGRAMS An Example. 2 registration P1 Read & check reg. P2 Prepare invoice P3 Accept reg. P4 Print invoice P5 Write conf. user printer registration.
Architectural Design Introduction Design has been described as a multistep process in which representations of data and program structure,
section II Analysis Systems Analysis and Design
Systems Design.  Application Design  User Interface Design  Database Design.
CS223: Software Engineering
Systems Development Lifecycle
CMSC 104, Section 301, Fall Lecture 18, 11/11/02 Functions, Part 1 of 3 Topics Using Predefined Functions Programmer-Defined Functions Using Input.
DATA FLOW DIAGRAMS.
Application architectures Advisor : Dr. Moneer Al_Mekhlafi By : Ahmed AbdAllah Al_Homaidi.
Architectural Complexity  A useful technique for assessing the overall complexity of a proposed architecture is to consider dependencies between components.
Dillon: CSE470: ANALYSIS1 Requirements l Specify functionality »model objects and resources »model behavior l Specify data interfaces »type, quantity,
SOFTWARE DESIGN & SOFTWARE ENGINEERING Software design is a process in which data, program structure, interface and their details are represented by well.
Data Flow Diagram : Developed By Larry Constantine as a way of expressing system requirements in graphical Form: Data Flow Models (DFMs) are easy to understand.
System Design and Modeling
Lecture 9- Design Concepts and Principles
SDC – SDLC integration.
Systems Analysis and Design
تحلیل سیستم‌ها مدل‌سازی پردازشی.
Software Design Designing the overall structure (architecture) of a software system Designing small pieces of computation Designing non-automated processes.
Software Design CMSC 345, Version 1/11.
Design Model Like a Pyramid Component Level Design i n t e r f a c d s
Lecture 9- Design Concepts and Principles
SOFTWARE DESIGN (SWD) Instructor: Dr. Hany H. Ammar
System Design By Kustanto.
IT323 Project Phase#2.
Presentation transcript:

1 TRANSFORM ANALYSIS Heuristics and Rules

2 DFD with Transform Flow Characteristics input-driven output-driven center of transformation

3 Structured Analysis and Design Information Flow Analysis 1 - specify the flow of information in your system => DFD 2 - identify typical structural patterns in the DFD => analysed & annotated DFD 3 - use a proven heuristic to map DFD into SC => first SC 4 - refine and check your Structure Chart => final SC

4 Structured Analysis and Design Transform Analysis 1 - specify the flow of information in your system 2 - a) confirm transform flow characteristics b) identify the center of transformation ===> annotated DFD 3 - transform your DFD into a first Structure Chart using IPO structure as design heuristic 4 - refine and check your Structure Chart ===> complete SC

5 Transform Analysis - Step 1 the DFD should exist as a result of systems requirements engineering and systems analysis check completeness of the DFD, data dictionary, and process dictionary refine the DFD (decompose, etc.) if that is necessary

6 registration read & check reg. prepare invoice accept reg. print invoice write conf. user printer registration db reg+ reg_info conf. invoice reg- profile prices invoice_prt conf_msg error_msg

7 read registration check registration error-handler registration reg+ error_reason error_msg reg_i

8 Transform Analysis - Step 2 Step 2a: –check the list of properties for transform flow characteristics –be aware that this is a guideline only Step 2b: –find and mark the center of transformation in the DFD

9 Transform Analysis - Step 2b locate the center of transformation –follow input-driven flows into the center until the data is in an internal format, correct and complete ===> mark position –trace back output-driven flows to the center until the data is complete and ready for presentation, but not yet in external format ===> mark position connect all markings: center of transformation

10 registration read & check reg. prepare invoice accept reg. print invoice write conf. user printer registration db reg+ reg_info conf. invoice reg- profile prices invoice_prt conf_msg error_msg center of transformation

11 read registration check registration error-handler registration reg+ error_reason error_msg reg_i

12 Transform Analysis - Step 3 IPO mapping heuristic i1 i2 ct1 ct2 o1o2 o3 sys I-ctrlP-crtlO-ctrl i1i2ct1ct2o1o2o3

13 The IPO Mapping & Design Heuristic establish a top level main controller (system) always introduce: –Input-driven flow controller –transform flow controller (Processing) –Output-driven flow controller translate DFD processes into SC modules and hang them from the correct controller allocate subprocesses => submodules

14 reg. sys. read & check comp reg. prod. output read reg. check reg. error hdlg. reg. prep. inv. acc. reg. print inv. write conf. crtdbprtcrt

15 Transform Analysis - Step 4 add data (and control) flows further decompose (factor) were necessary –user interface handling modules –error-handling modules –add initialisation & termination modules check quality of design: –cohesion –coupling reconfirm mapping with DFD

16 See our Structure Chart Example (Section 3c) for a complete specification of data and control flows.

17 End of Section 3e coming up: software design quality