Mississippi State University Page 1 2/21/2016 The Eureka Story.

Slides:



Advertisements
Similar presentations
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 14 Slide 1 Object-oriented Design 1.
Advertisements

Analysis Modeling.
Chapter 22 Object-Oriented Systems Analysis and Design and UML Systems Analysis and Design Kendall and Kendall Fifth Edition.
Practical Object-Oriented Design with UML 2e Slide 1/1 ©The McGraw-Hill Companies, 2004 PRACTICAL OBJECT-ORIENTED DESIGN WITH UML 2e Chapter 5: Restaurant.
7M701 1 Software Engineering Object-oriented Design Sommerville, Ian (2001) Software Engineering, 6 th edition: Chapter 12 )
Capturing the requirements
Analysis Modeling Over view of today’s lesson T he analysis model is the first technical representation of a system. Analysis modeling uses a combination.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
Lecture 4 Class Responsibility Collaboration Cards
7M701 1 Software Engineering Software Requirements Sommerville, Ian (2001) Software Engineering, 6 th edition: Chapter 5
Chapter 8 Analysis Modeling
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.
©Ian Sommerville 2006Software Engineering, 7th edition. Chapter 14 Slide 1 Object-oriented Design.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
Overview of Software Requirements
Software Requirements and the Requirements Engineering Process Chapters 5 and 6.
Objects What are Objects Observations
Design Patterns Discussion of pages: xi-11 Sections: Preface, Forward, Chapter
The Software Development Life Cycle: An Overview
Object-oriented methodology object models use case modeling unified modeling language the data dictionary the cornucopia case portfolio project Systems.
1/19 Component Design On-demand Learning Series Software Engineering of Web Application - Principles of Good Component Design Hunan University, Software.
System models Abstract descriptions of systems whose requirements are being analysed Abstract descriptions of systems whose requirements are being analysed.
111 Subsystems CS 4311 Wirfs Brock et al., Designing Object-Oriented Software, Prentice Hall, (Chapter 7)
Database Systems: Design, Implementation, and Management Ninth Edition
Unified Modeling Language, Version 2.0
PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 4th Edition Copyright © 2012 John Wiley & Sons, Inc. All rights.
Requirement Engineering. Review of Last Lecture Problems with requirement Requirement Engineering –Inception (Set of Questions) –Elicitation (Collaborative.
Object-Oriented Analysis and Design An Introduction.
1 Object-Oriented Analysis Use Case Driven. 2 The outline method for OOA 1.Identify object classes within the problem domain 2.Define the behaviour of.
Using UML, Patterns, and Java Object-Oriented Software Engineering Chapter 4, Requirements Elicitation.
Chapter 9 요구사항 모델링: 시나리오 기반 방법론 Requirements Modeling: Scenario-Based Methods 임현승 강원대학교 Revised from the slides by Roger S. Pressman and Bruce R. Maxim.
MCS 270 Spring 2014 Object-Oriented Software Development.
Using UML, Patterns, and Java Object-Oriented Software Engineering Chapter 2, Modeling with UML: Review Session (Optional)
Using UML, Patterns, and Java Object-Oriented Software Engineering Chapter 2, Modeling with UML: Review Session (Optional)
Sommerville 2004,Mejia-Alvarez 2009Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
Developed by Reneta Barneva, SUNY Fredonia for CSIT 425 Requirements Modeling.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 14 Slide 1 Object-oriented Design.
Chapter 8 Analysis & Modeling. Data Modeling examines data objects independently of processing focuses attention on the data domain creates a model at.
Fall 2010 CS4310 Requirements Engineering A Brief Review of UML & OO Dr. Guoqiang Hu Department of Computer Science UTEP 1.
CS 4850: Senior Project Fall 2014 Object-Oriented Design.
Lecture 6: Structural Modeling
INTRODUCTION TO SOFTWARE ENGINEERING Authors: William M. Buchanan Joseph Picone Contact Information: ECE 4512 / 4522 Box 9571 Mississippi State University.
Lecture 1: Introduction to Software Engineering WXGE6103 Software Engineering Process and Practice Object-oriented Design.
Use Case Driven Analysis Requirements Use Case Use Case Description System Sequence Diagram Chapter 5.
Capturing the requirements  Requirement: a feature of the system or a description of something the system is capable of doing in order to fulfill the.
Object-Oriented Modeling: Static Models. Object-Oriented Modeling Model the system as interacting objects Model the system as interacting objects Match.
Object-Oriented Analysis and Design ธนวัฒน์ แซ่ เอียบ.
Analysis Modeling CpSc 372: Introduction to Software Engineering
Requirements Engineering for Web Applications. SR: System Vision Document Written by key stakeholders Written by key stakeholders An executive summary.
OBJECT ORIENTED AND FUNCTION ORIENTED DESIGN 1 Chapter 6.
UML Examples PRESETED BY: MEHRAN NAJAFI SHIMA AGHTAR.
Requirements Engineering-Based Conceptual Modelling From: Requirements Engineering E. Insfran, O. Pastor and R. Wieringa Presented by Chin-Yi Tsai.
Domain Classes – Part 1.  Analyze Requirements as per Use Case Model  Domain Model (Conceptual Class Diagram)  Interaction (Sequence) Diagrams  System.
Object-Oriented Programming © 2013 Goodrich, Tamassia, Goldwasser1Object-Oriented Programming.
111 Subsystems CS 4311 Wirfs Brock et al., Designing Object-Oriented Software, Prentice Hall, (Chapter 7)
1 Unified Modeling Language, Version 2.0 Chapter 2.
Domain Model A representation of real-world conceptual classes in a problem domain. The core of object-oriented analysis They are NOT software objects.
Unit-3 Identifying use cases Object Analysis Classification
Evaluating Requirements
UML - Development Process 1 Software Development Process Using UML.
CSIS 4850: CS Senior Project – Spring 2009 CSIS 4850: Senior Project Spring 2009 Object-Oriented Design.
Object-Oriented Software Engineering Practical Software Development using UML and Java Modelling with Classes.
Requirement Elicitation Review – Class 8 Functional Requirements Nonfunctional Requirements Software Requirements document Requirements Validation and.
1 © 2013 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the.
1 Use Cases Object-Oriented Modeling and Design with UML (Second Edition) Blaha & Rumbaugh Sections 7.1, 8.1.
DOMAIN CLASSES – PART 1 BTS430 Systems Analysis and Design using UML.
SYS466 Domain Classes – Part 1.
Motivation: Concise System Behavior Communication plus Code Generation
Chapter 22 Object-Oriented Systems Analysis and Design and UML
Presentation transcript:

Mississippi State University Page 1 2/21/2016 The Eureka Story

Mississippi State University Page 2 2/21/2016 Senior Design Software Engineering Deliverables Demonstrate Evidence of Software Engineering through: Use Cases Models

Mississippi State University Page 3 2/21/2016 Senior Design Software Engineering Deliverables Product Drawings (showing externally visible objects) List of Use Cases Two Use Cases (often traveled sunny and rainy day) Information Model (externally visible objects) One State Model (behavior of your most interesting object) One Process Model (describing activity in every state) Object Communication Model Revised Information Model (externally visible plus internal objects)

Mississippi State University Page 4 2/21/2016 Externally Visible Vending Machine Objects

Mississippi State University Page 5 2/21/2016 Vending Machine Use Case Scenarios

Mississippi State University Page 6 2/21/2016 Correct Change Vending Machine Use Case

Mississippi State University Page 7 2/21/2016 Vending Machine Information Model

Mississippi State University Page 8 2/21/2016 Vending Machine State and Process Model

Mississippi State University Page 9 2/21/2016 Vending Machine Object Communication Model

Mississippi State University Page 10 2/21/2016 Introducing the Use Case Describes User Interaction with your system in terms of externally visible objects

Mississippi State University Page 11 2/21/2016 Externally Visible Vending Machine Objects

Mississippi State University Page 12 2/21/2016 Vending Machine Use Case Scenarios

Mississippi State University Page 13 2/21/2016 Correct Change Vending Machine Use Case

Mississippi State University Page 14 2/21/2016 Externally Visible Objects Are Explicitly Included in Use Cases

Mississippi State University Page 15 2/21/2016 Introducing the Information Model Relationships, Objects, and Attributes

Mississippi State University Page 16 2/21/2016 Vending Machine Information Model

Mississippi State University Page 17 2/21/2016 Vending Machine Information Model

Mississippi State University Page 18 2/21/2016 Information Model Consists of: Objects Attributes Relationships One-to-one One-to-many Many-to-many Unconditional Conditional

Mississippi State University Page 19 2/21/2016 Object Definition Set of real-world things with common characteristics All instances of an object behave the same

Mississippi State University Page 20 2/21/2016 Identifying Objects Tangible things that make up the problem Roles played by people or organizations Incidents, e.g. accidents, system crashes, service calls Interactions with a transaction or contract quality, e.g. purchase related to buyer, seller, and thing purchased Table Specifications, e.g. definition of a things attributes

Mississippi State University Page 21 2/21/2016 Identifying Objects Object identification is: an art refined by experience an iterative process

Mississippi State University Page 22 2/21/2016 Keys To the IM Imagine you’re a specific instance of an object when evaluating relationships; e.g. one-to-one, one-to-many, etc. Answer questions about relationships from the mindset of an object instance Understand that relationships represent information exchange agreements between objects Don’t create an object unless you’re absolutely convinced you’ve got to have it Objects are work - more often than not, a lot of work

Mississippi State University Page 23 2/21/2016 Senior Design Software Engineering Focus Object-Oriented Analysis

Mississippi State University Page 24 2/21/2016 Object-Oriented Analysis  A different way to see, discover, and describe the same old problems  Describe the solution in terms of the problem  OOA Models represent a higher layer of abstraction  When used in product development, the goal is to maintain the models, not the code Object-oriented Analysis describes the problem using coupled graphical equations: information, state, and process models Object-oriented Development produces the code

Mississippi State University Page 25 2/21/2016 Models Are Coupled Graphical Equations If you change one model, you change them all The Information Model is coupled to its State and Process Models PM is coupled to IM and SM SM is coupled to IM and PM OCM is derived from IM, SM, and PM

Mississippi State University Page 26 2/21/2016 Object-Oriented Systems Analysis What is Object-Oriented Analysis? Behavior specification using models Models reflect the things in the problem (objects) Behavior simulation by walking through (or executing) the models

Mississippi State University Page 27 2/21/2016 FYI: Object-Oriented Development What is Object-Oriented Development? Performance specification Template creation Code generation

Mississippi State University Page 28 2/21/2016 Senior Design Focus On the Models Behavior specification (required): Types of models: IM, SM, PM, plus OCM Behavior simulation (model walk-through is required): (Compiling and executing models is not required)

Mississippi State University Page 29 2/21/2016 Behavior Specification Behavior specification using three types of models: Information State Process (An Object Communication Model results from Information, State, and Process models)

Mississippi State University Page 30 2/21/2016 OOA Motivation: Concise Behavior Communication and Code Generation

Mississippi State University Page 31 2/21/2016 Backup Story: A Tale of More Models

Mississippi State University Page 32 2/21/2016 Information Model

Mississippi State University Page 33 2/21/2016 State And Process Model - Room

Mississippi State University Page 34 2/21/2016 State and Process Model - Person

Mississippi State University Page 35 2/21/2016 Object Communication Model OOA Signaling Diagram

Mississippi State University Page 36 2/21/2016 Object Communication Model - OCM

Mississippi State University Page 37 2/21/2016 Where Most People Find Themselves On The OOA Learning Curve The Bottom Of The Paraboloid