The OOA OBJECT DICTIONARY

Slides:

Advertisements

Similar presentations

Use Case: Use case title Submitter(s) Submitting Company #1 – Submitter 1, Submitter 2 Supporters(s) Supporting Company #1 – Submitter 1, Submitter 2 Use.

Advertisements

//HDL Example 8-2 // //RTL description of design example (Fig.8-9) module Example_RTL (S,CLK,Clr,E,F,A);

Lecture 8- Analysis Modeling The Elements of Anaylsis Model The Elements of Anaylsis Model Data Modeling, Functional Modeling and Information Flow Data.

Modeling Main issues: What do we want to build How do we write this down ©2008 John Wiley & Sons Ltd. vliet.

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.

1 STRUCTURE CHARTS Elements and Definitions. 2 Software System Design translates SRS into a ===> software system architecture: –system’s static structure.

Chapter 10 System Sequence Diagrams. What is a System Sequence Diagram? A way of modeling input and output events related to systems It is a picture that.

Analysis Modeling Instructor: Dr. Jerry Gao. Analysis Modeling Jerry Gao, Ph.D. Jan Elements of the analysis model - Data modeling - Functional.

The OOA Process - I Steps and Rules Objects and Structures.

© 2005 Prentice Hall4-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.

Object Oriented Design OOD. OOD characteristics - I conceptual compatibility with OOA notational consistency with OOA clean traceability of OOA results.

1 SWE Introduction to Software Engineering Lecture 15 – System Modeling Using UML.

Object Oriented Analysis OOA. OOA Deliverables Static Object model –one single diagram Scenarios –set of diagrams Object Dictionary –one set of comprehensive.

Software Engineering CSE470: Requirements Analysis 1 Requirements Analysis Defining the WHAT.

T T07-01 Sample Size Effect – Normal Distribution Purpose Allows the analyst to analyze the effect that sample size has on a sampling distribution.

The OOD Process Design as a Logical Continuation of Analysis.

CS /47 Illinois Institute of Technology CS487 Software Engineering Requirements II- part B Instructor David Lash.

The OOA Process - I Steps and Rules Objects and Structures.

The OOA Process - II Scenarios. The Steps of OOA - Part 1 identify objects (classes) identify structures –generalization - specialization (“ISA”) –whole.

Cardinality and Modality (ERD)

2 Approaches to Requierements Engineering Reference: Systems Analysis and Design in a Changing World, 3 rd Edition, chapter 2 and chapter 6.

Data flow diagrams.

Chapter 4 User Experience Model. User experience model (Ux) Visual specification of the user interface Visual specification of the user interface Both.

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.

程建群博士(Dr. Jason Cheng) 年03月

Phase 2: Systems Analysis

1 Ref: Prof Sarda Process Modeling…… Lecture Outline Data flow diagram (DFD)

Information Systems. Features of Information Systems Read Page P88 Then use your research to complete the following slides.

Dynamic Modeling Chapter 11 Part of Analysis Modeling Designing Concurrent, Distributed, and Real-Time Applications with UML Hassan Gomaa (2001)

CSC 395 – Software Engineering Lecture 13: Object-Oriented Analysis –or– Let the Pain Begin (At Least I’m Honest!)

1 UML Basic Training. UML Basic training2 Agenda  Definitions: requirements, design  Basics of Unified Modeling Language 1.4  SysML.

Approaching a Problem Where do we start? How do we proceed?

Conceptual Modelling – Behaviour

Modeling Shari L. Pfleeger and Joanne M. Atlee, Software Engineering: Theory and Practice, 4 th edition, Prentice Hall, Hans Van Vliet, Software.

Analysis Modeling. Function Modeling & Information Flow  Information is transformed as it flows through a computer-based system. The system accepts input.

Procedures for managing workflow components Workflow components: A workflow can usually be described using formal or informal flow diagramming techniques,

System sequence diagrams

7. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Detailed Object-Oriented Requirements Definitions  System Processes—A Use.

Introduction to OOAD and the UML

UML’s StateChart FSM, EFSM in UML Concurrent states Tool support.

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.

Information Systems Architecture (ISA) Conceptual blueprint for organization’s desired information systems structure Consists of:  Data (e.g. Enterprise.

Information Systems Architecture (ISA)

QUALITY MANAGEMENT PRINCIPLES. Objectives 4 Understand usefulness of CASE tools 4 Types of CASE tools 4 Data flow diagrams (DFD)

Unit-3 Identifying use cases Object Analysis Classification

Events to Data Flows to Data Dictionaries System Analysis & Design.

Course Instructor: Kashif I hsan 1. Chapter # 6 2.

Dillon: CSE470: ANALYSIS1 Requirements l Specify functionality »model objects and resources »model behavior l Specify data interfaces »type, quantity,

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.

Engineering Quality Software Week02 J.N.Kotuba1 SYST Engineering Quality Software.

WHAT IS A Context Diagram?

Cmpe 589 Spring 2006.

System sequence diagrams

Rumbaugh’s Objectmodeling Technique

Data Dictionaries ER Diagram.

UML’s StateChart FSM, EFSM in UML Concurrent states Tool support.

Object-Oriented Analysis

تحلیل سیستم‌ها مدل‌سازی پردازشی.

Unified Modeling Language

University of Houston-Clear Lake

Section 4.7 Forming Functions from Verbal Descriptions

Software Design CMSC 345, Version 1/11.

Ship Harbor Model Department of Computer Science University of Karachi

System Design By Kustanto.

Requirement Analysis using

Georg Umgiesser and Natalja Čerkasova

No Yes START Do you live in Scotland? Take umbrella See last Flowchart

IT323 Project Phase#2.

Introduction to OOAD and the UML

Requirements “Content Guide”

Presentation transcript:

The OOA OBJECT DICTIONARY OBJECT SPECIFICATION object-name STRUCTURES ... EXTERNAL INPUTS / OUTPUTS ... ATTRIBUTES ... STATE-DIAGRAM ... SERVICES ... END SPECIFICATION.

OBJECT SPECIFICATION object-name STRUCTURES ..... END SPECIFICATION. verbal description label cardinality three types of structures placeholders for design solutions (not ISA) check with static model and scenarios!

OBJECT SPECIFICATION object-name EXTERNAL INPUTS / OUTPUTS ..... END SPECIFICATION. verbal description name parameters placeholders for design objects check with scenarios!

OBJECT SPECIFICATION object-name ATTRIBUTES ..... END SPECIFICATION. verbal (and graphical) description e.g. BNF, ER data attributes from OOA will be extended in design check with static model and scenarios!

OBJECT SPECIFICATION object-name STATE DIAGRAM ..... END SPECIFICATION. verbal and graphic description states permissible transitions NO events or outputs placeholders for design solutions check with static model and scenarios!

OBJECT SPECIFICATION object-name SERVICES ..... END SPECIFICATION. verbal or graphical description e.g. PDL, Flow Diag., Block Diag. will be refined and extended in design check with scenarios!