1 PROCESS SPECIFICATIONS for DFDs Concepts and Examples.

Slides:



Advertisements
Similar presentations
Data Flow Diagram (DFD) Overview
Advertisements

Chapter 10: The Traditional Approach to Design
Systems Analysis and Design in a Changing World, Fifth Edition
Systems Analysis Requirements structuring Process Modeling
Describing Process Specifications and Structured Decisions Systems Analysis and Design, 7e Kendall & Kendall 9 © 2008 Pearson Prentice Hall.
Repetition control structures
Irwin/McGraw-Hill Copyright © 2004 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS6th Edition.
Traditional Approach to Design
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.
Systems Analysis and Design 9th Edition
© Copyright 2011 John Wiley & Sons, Inc.
1 STRUCTURE CHARTS Elements and Definitions. 2 Software System Design translates SRS into a ===> software system architecture: –system’s static structure.
1 SWE Introduction to Software Engineering Lecture 21 – Architectural Design (Chapter 13)
1 The DATA DICTIONARY (for DFDs) Concepts and Examples.
Data Flow Diagramming. Data Flow Diagrams Data Flow Diagrams are a means to represent data transformation processes within an information system.
Structuring System Requirements: Process Modeling
Application architectures
CS189A/172 - Winter 2008 Lecture 7: Software Specification, Architecture Specification.
1 PROCESS SPECIFICATIONS for DFDs Concepts and Examples.
1 Chapter 16 Component-Level Design. 2 Component-Level Design  the closest design activity to coding  the approach:  review the design description.
Lecture Notes 1/21/04 Program Design & Intro to Algorithms.
Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 3. Defining the System 4. Managing Scope 5.
© Copyright 2011 John Wiley & Sons, Inc.
Systems Analysis and Design in a Changing World, 6th Edition
Modeling the Processes and Logic
Lesson-21Process Modeling Define systems modeling and differentiate between logical and physical system models. Define process modeling and explain its.
System analysis and design
Application architectures
System Analysis Overview Document functional requirements by creating models Two concepts help identify functional requirements in the traditional approach.
PROCESS MODELING Chapter 8 - Process Modeling
Functional Modeling Joseph Valacich, Joey George and Jeff Hoffer, Essentials of System Analysis and Design, 4 th edition, Prentice Hall, 2009.
Chapter 9 Describing Process Specifications and Structured Decisions
Lecture 6 Data Flow Modeling
Data-Flow Diagrams Week 10 Lecture 1. Data Flow Diagrams (DFDs) One of most important modelling tools used by system analysts In use since late 1970’s.
Describing Process Specifications and Structured Decisions Systems Analysis and Design, 7e Kendall & Kendall 9 © 2008 Pearson Prentice Hall.
Chapter 9 Moving to Design
The Software Development Life Cycle. Software Development SDLC The Software Development Life-Cycle Sometimes called the program development lifecycle.
10 ITK261 The traditional approach to design Reading: Chapter 10 Oct 9, 11.
10 The traditional approach to design Hisham Alkhawar.
Dr. Andy Seddon Staffordshire UNIVERSITY School of Computing Code Design (The use of pseudo code for Elementary Process Descriptions)
© 2011 Pearson Addison-Wesley. All rights reserved. Addison Wesley is an imprint of Stewart Venit ~ Elizabeth Drake Developing a Program.
Elements of Software Analysis and Design - Structured Approaches - Structured Analysis - Functional Oriented Design 10/24/2015ICS 413 – Software Engineering1.
Repetition Control Structures Simple Program Design Third Edition A Step-by-Step Approach 5.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
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.
Information Systems Architecture (ISA) Conceptual blueprint for organization’s desired information systems structure Consists of:  Data (e.g. Enterprise.
Information Systems Architecture (ISA)
Technical Methods for Specifying Requirements 1. When to Use Technical Methods  If the description of the requirement is too complex for natural language.
Systems Analysis and Design 8th Edition
1 Software Engineering: A Practitioner’s Approach, 6/e Chapter 11b: Component-Level Design Software Engineering: A Practitioner’s Approach, 6/e Chapter.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
McGraw-Hill/Irwin Copyright © 2006 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter 5 Modeling the Processes and Logic.
Application architectures Advisor : Dr. Moneer Al_Mekhlafi By : Ahmed AbdAllah Al_Homaidi.
Systems Analysis and Design in a Changing World, Fourth Edition
Business Process Modeling What is a process model? – A formal way of representing how a business system operates. – Illustrates the activities that are.
Application architectures. Objectives l To explain the organisation of two fundamental models of business systems - batch processing and transaction processing.
Business System Development
Technical Methods for Specifying Requirements
IT316 Software Requirement Engineering
Introduction to Programming and Visual Basic
Chapter 2 : Data Flow Diagram
Problem Solving Techniques
Chapter 16 Component-Level Design
Component-Level Design
Process Description Tools
Chapter 7: Data Flow Diagram Structuring System Process Requirements
WRITING AN ALGORITHM, PSEUDOCODE, AND FLOWCHART LESSON 2.
Information system analysis and design
Presentation transcript:

1 PROCESS SPECIFICATIONS for DFDs Concepts and Examples

2 Process Specification part of the specifications for a complete –Dataflow Analysis (DFD) –OOAD model –SADT –etc.

3 Process Specification for a DFD specifies process “bubbles” in a DFD –NOT sources and sinks must be consistent with DFD –specification compatible with diagram must be complete with regard to the DFD consists of –process decomposition (diagrams) –process description

4 Process Description (see also IEEE ) name (and aliases) informal description inputs (see DFD & data dictionary) outputs (see DFD & data dictionary) processing (semi-formal) related processes, sources and sinks

5

6 Read & Check Query name: read & check query (RCQ) description: Reads query statements from the physician’s terminal interface, brings them into internal format, checks correctness and completeness, and handles error situations. Transaction oriented. Communicates with user interface.

7 Read & Check Query inputs: –Query from: physician terminal (external source)

8 Read & Check Query outputs: –Query + to: process request (system internal process) –Query - to: physician terminal (external source) comment: needs further elaboration

9 Read & Check Query related processes, sources and sinks: –depends on: user interface design for physician terminal –is-part-of (super-ordinate process): Patient Information System

10 Read & Check Query related processes, sources and sinks: –is-decomposed-into (sub-ordinate proc.): read query check query error handling for query

11 (Semi-) Formal Specification? PDL - Program Design Language –see Caine, Farber, and Gordon –“pseudo-code”, structured English –English embedded within programming language syntax –close to flowcharts

12 Specifying Processes in DFDs Structured English Decision Trees Decision Tables => see the example SRS on the course webpage/library => see the information about structured decisions in course folder in the library => read A.Davis’ book (see syllabus)

13 STOP HERE We will come back at design level!

14 (Semi-) Formal Specification? PDL - Program Design Language –see Caine, Farber, and Gordon –“pseudo-code”, structured English –English embedded within programming language syntax –close to flowcharts

15 PDL modelling basic control - a block: BEGIN block-name statements END block-name PROCESS process-name process description END process-name

16 PDL modelling basic control - a condition: IF condition THEN block ELSE block ENDIF Remark: There is a CASE construct.

17 PDL modelling basic control - a iteration: DO-WHILE condition block ENDDO Remark: There are REPEAT and DO-FOR constructs.

18 Read & Check Query - PDL PROCESS read&check_query event: query window is activated; initialise interface (query window); DO WHILE user keeps interface active => query call read_query => query-i; call check_query => query_error_info or query+; IF query_error_info THEN call error_handling_for_query => query- ENDIF ENDDO END.

19 End of Section 2f coming up: software design