SSA(D) vs OOAD M. Pickard CSC 513.

Slides:



Advertisements
Similar presentations
Chapter 2 Approaches to System Development
Advertisements

Irwin/McGraw-Hill Copyright © 2004 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS6th Edition.
Chapter 4 Enterprise Modeling.
Software Requirements Engineering
Design. Overview Design and abstraction Action-oriented design Data flow analysis Transaction analysis Data-oriented design Object-oriented design Challenges.
Lecture 13 Revision IMS Systems Analysis and Design.
Systems Development Life Cycle
Systems Analysis and Design in a Changing World, Fifth Edition
Data Modeling Introduction. Learning Objectives Define key data modeling terms –Entity type –Attribute –Multivalued attribute –Relationship –Degree –Cardinality.
6 Systems Analysis and Design in a Changing World, Fourth Edition.
Traditional Approach to Requirements Data Flow Diagram (DFD)
Chapter 6: The Traditional Approach to Requirements
Systems Analysis and Design in a Changing World, Fifth Edition
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
Chapter 2: Approaches to System Development
INFO415 Approaches to System Development: Part 2
Systems Analysis and Design in a Changing World, Fifth Edition
Lesson 7 Guide for Software Design Description (SDD)
INFORMATION SYSTEM APPLICATIONS System Development Life Cycle.
Systems Analysis & Design Methods Traditional Techniques: Data Flow Diagrams (see also handouts !)
Phase 2: Systems Analysis
Two Approaches to System Development
Requirements Definition and Specification. Outline Definition and specification Natural language Semi-formal techniques –Program description languages.
Unified Modeling Language, Version 2.0
SOFTWARE DESIGN (SWD) Instructor: Dr. Hany H. Ammar
Chapter 9 Moving to Design
1 Systems Analysis and Design in a Changing World, Thursday, January 18, 2007.
1 ISA&D7‏/8‏/ ISA&D7‏/8‏/2013 Methodologies of the SDLC Traditional Approach to SDLC Object-Oriented Approach to SDLC CASE Tools.
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 COMP 350: Object Oriented Analysis and Design Lecture 1Introduction References: Craig Larman Chapter 1.
UHD::3320::CH121 DESIGN PHASE Chapter 12. UHD::3320::CH122 Design Phase Two Aspects –Actions which operate on data –Data on which actions operate Two.
CS 4850: Senior Project Fall 2014 Object-Oriented Design.
2 Systems Analysis and Design in a Changing World, Fifth Edition.
Computing and SE II Chapter 9: Design Methods and Design Models Er-Yu Ding Software Institute, NJU.
© 2006 Pearson Addison-Wesley. All rights reserved 2-1 Chapter 2 Principles of Programming & Software Engineering.
1 Introduction to Design. 2 Outline Basics of design Design approaches.
6 Systems Analysis and Design in a Changing World, Fourth Edition.
CSIS 4850: CS Senior Project – Spring 2009 CSIS 4850: Senior Project Spring 2009 Object-Oriented Design.
Chapter 2 Principles of Programming and Software Engineering.
Object Oriented Programming and Data Abstraction Earl Huff Rowan University.
Basic Characteristics of Object-Oriented Systems
CS 8532: Adv. Software Eng. – Spring 2007 Dr. Hisham Haddad Discussion of Course Syllabus Class will start momentarily. Please Stand By … CS 8532: Advanced.
CS 8532: Adv. Software Eng. – Spring 2009 Dr. Hisham Haddad , Monday Class will start momentarily. Please Stand By … CS 8532: Advanced Software.
Introduction to OOAD and UML
From requirements to specification Specification is a refinement of requirements Can be included together as Software Requirements Specifications (SRS)
Slide 1 Unified Modeling Language, Version 2.0 Object-Oriented SAD.
Systems Development Life Cycle
Software Design.
UML Diagrams By Daniel Damaris Novarianto S..
Systems Analysis and Design in a Changing World, Fourth Edition
Chapter 6 The Traditional Approach to Requirements.
Main issues: • What do we want to build • How do we write this down
Architecture Concept Documents
Systems Analysis and Design With UML 2
Software Engineering Design
Software Design Mr. Manoj Kumar Kar.
UML Diagrams Jung Woo.
The Object Oriented Approach to Design
Object-Oriented Design
تحلیل سیستم‌ها مدل‌سازی پردازشی.
Unified Modeling Language
Software Design CMSC 345, Version 1/11.
Object oriented analysis and design
Dynamic Modeling Lecture # 37.
John D. McGregor Module 6 Session 1 More Design
Systems Architecture & Design Lecture 3 Architecture Frameworks
Software Design Methodologies and Testing
Systems Development Life Cycle
Presentation transcript:

SSA(D) vs OOAD M. Pickard CSC 513

Different Perspectives . . . SSA (and design) Data and actions considered separately. Emphasis on data structures, procedures. OOAD Data and actions considered together. Emphasis on classes, objects.

Steps in OOA Use-case modeling Class Modeling Dynamic Modeling

OOD Create interaction diagrams sequence diagrams, collaboration diagrams Build a detailed class diagram, or object model packages of classes relationships owned by the package hierarchy of packages Design the product using objects Proceed to detailed design

Structured Systems Analysis (SSA) Analysis, resulting in Specifications 9 Step Approach (Gane and Sarsen) Draw DFD Define scope of product & operational approach Refine/define data flows Define logic of processes Define data stores Define physical resources Determine I/O specifications Perform sizing (volumes, frequencies) Determine hardwire requirementss Other variations

SSA - Specifications Semiformal techniques Data Flow Diagram (DFD) Entity Relationship Diagram (ERD) Decision (Logic) Table (DLT) Decision Tree

SSA - Specifications Formal techniques Finite State Machines Petri Nets Z Formal specification language pronounced “zed” Other

Structured Methods - Design Architectural design Structure charts Map DFDs to structure chart Global data structures Proceed to detailed design

SSA(D) vs OOAD The differences become very apparent in the activities that take place after requirements gathering and before detailed design. SSAD does not preclude use of OOPL. OOAD does not preclude use of procedural language.

Architectural Design - Important Principles Minimize coupling Maximize cohesion Use information hiding Documentation design decisions design architecture

Detailed Design Identification of modules, i.e, program unit purpose, preconditions, postconditions Description of interfaces between program units Module specifications narrative or structured English semiformal or formal methods to describe module functionality DLT, FSM, other linked closely to implementation environment programming language, operating system, etc definition of local data structures

Implementation Using the detailed design, construction begins . . .