Software Requirements Engineering Elaboration Process Lecture-14.

Slides:



Advertisements
Similar presentations
Requirements Diagrams With UML Models
Advertisements

Object-Oriented Software Engineering Visual OO Analysis and Design
Chapter : Analysis Modeling
© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 9 Slide 1 Appendix 3 Object-Oriented Analysis and Design.
Chapter 8 Analysis Engineering Software Engineering: A Practitioner’s Approach by Roger S. Pressman.
Software Requirements Engineering Elaboration Process Lecture-13.
1 SWE Introduction to Software Engineering Lecture 16 – System Modeling An Example.
Chapter 8 Analysis Modeling
Analysis Modeling Dynamic Modeling. Requirements analysis Results in static and dynamic models – Scenario models: use cases (static), swimlane diagrams.
Object-Oriented Analysis
Slide 1 Chapter 8 Behavioral Modeling. Slide 2 Key Ideas Behavioral models describe the internal dynamic aspects of an information system that supports.
Chapter 8 Analysis Modeling
Unified Modeling Language
Building The Analysis Model. Object-Oriented Analysis The object oriented analysis define all classes, the relationships and behavior associated with.
Analysis Modeling (cont’d) CpSc 372: Introduction to Software Engineering Jason O. Hallstrom Authorship Disclaimer. These slides.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 8: Modelling Interactions and Behaviour.
CS 325: Software Engineering March 3, 2015 Activity Modeling for Transformational Systems Trtansformational Systems UML Activity Diagrams.
Data Flow Diagrams.
Chapter 8 Analysis Engineering (分析工程) Software Engineering: A Practitioner’s Approach by Roger S. Pressman Software Engineering: A Practitioner’s Approach.
Requirements Engineering CSE-305 Requirements Engineering Process Tasks Lecture-5.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 25. Review Design Level Class Diagram Identifying classes/Operations/Attributes Associations – Simple associations.
Requirement Engineering. Review of Last Lecture Problems with requirement Requirement Engineering –Inception (Set of Questions) –Elicitation (Collaborative.
Chapter 4 – Requirements Engineering Lecture 3 1Chapter 4 Requirements engineering.
1 Chapter 7 Requirement Modeling flow, behavior, patterns and Webapps.
Software Engineering Object Oriented Analysis. Objectives 1.To outline an Object Oriented Analysis process and modelling language 2.To study the process.
Slide 1 Systems Analysis and Design with UML Version 2.0, Second Edition Alan Dennis, Barbara Wixom, and David Tegarden Chapter 8: Behavioral Modeling.
Analysis Modeling. Function Modeling & Information Flow  Information is transformed as it flows through a computer-based system. The system accepts input.
Behavioral Modeling Chapter 8.
Intro to Software System Modeling
CS /31 Illinois Institute of Technology CS487 Software Engineering OOA with UML David Lash.
Developed by Reneta Barneva, SUNY Fredonia for CSIT 425 Requirements Modeling.
1 Software Engineering: A Practitioner’s Approach, 6/e Chapter 8: Analysis Modeling Software Engineering: A Practitioner’s Approach, 6/e Chapter.
1.  A customer walks into your office, sits down, looks you straight in the eye and says, “I know you think you understand what I said, but what you.
Course Instructor: Kashif Ihsan 1. Chapter # 3 2.
Object-Oriented Analysis and Design CHAPTER 10: SYSTEM SEQUENCE DIAGRAMS 1.
Drawing System Sequence Diagrams
Use Case Diagram The purpose is to communicate the system’s functionality and behaviour to the customer or end user. Mainly used for capturing user requirements.
Interaction Diagrams Interaction Diagrams allow the designer to show how groups of objects collaborate in some behavior. –Interaction Diagrams will show.
Software Engineering OO Analysis (Object-Behaviour Models)
Behavioral Modeling Chapter 8
CSCI-383 Object-Oriented Programming & Design Lecture 12.
7. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Detailed Object-Oriented Requirements Definitions  System Processes—A Use.
UML Examples PRESETED BY: MEHRAN NAJAFI SHIMA AGHTAR.
System Sequence Diagram Chandan Rupakheti & Steve Chenoweth Week 5-3a.
Requirement Engineering. Recap Flow Based Modeling DFDs CFDs Processing narratives Class-based Model How to select classes? How to find attributes and.
Interaction Diagram An interaction diagram is a graphical representation of interactions between objects. Sequence diagram: shows the sequence in which.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 26. Review UML behavioral Diagrams – Sequence diagram.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Building analysis model  Analysis modeling uses a combination of text and diagrammatic forms to depict requirements for data function and behavior in.
Requirements Engineering Determining and Defining the Requirements for the Project.
OBJECT-ORIENTED TESTING. TESTING OOA AND OOD MODELS Analysis and design models cannot be tested in the conventional sense. However, formal technical reviews.
Unit II: Requirements Engineering
Software Engineering Unit II : Requirement Engineering Requirement Engineering : Initiating the Process, Eliciting Requirements, Building the Requirements.
1 8.1 Requirements Analysis Rules of Thumb Rules of Thumb Models should focus on requirements that are visible within the problem or business domain. The.
1 Systems Analysis and Design Behavioral Modeling Chapter 8 (Last one before the Midterm!)
CompSci 280 S Introduction to Software Development
Chapter 8 Analysis Engineering
Elaboration Process Lecture-16.
Ch 7: using Data Flow Diagrams
Elaboration & Negotiation Process
State Transition Diagram for A System
Data Dictionaries ER Diagram.
Analysis Modeling Dynamic Modeling.
Business System Development
Software Engineering Chapter 5 (Part 3) System Modeling Dr.Doaa Sami.
Analysis Modeling Requirements analysis Flow-oriented modeling
Unit-3 Analysis Modeling
Requirement Analysis using
Software design and architecture
Presentation transcript:

Software Requirements Engineering Elaboration Process Lecture-14

Recap  Object Oriented Analysis  Class Modeling

Class Diagram Class diagram for the system class

Today’s lecture  Object Oriented analysis  Object oriented modeling  Behavioral modeling  Structure analysis  Flow oriented modeling

CRC Modeling

A CRC model index card for FloorPlan class

Behavioral Modeling

Creating a Behavioral Model 1) Identify events found within the use cases and implied by the attributes in the class diagrams 2) Build a state diagram for each class, and if useful, for the whole software system

Identifying Events in Use Cases  An event occurs whenever an actor and the system exchange information  An event is NOT the information that is exchanged, but rather the fact that information has been exchanged  Some events have an explicit impact on the flow of control, while others do not  An example is the reading of a data item from the user versus comparing the data item to some possible value

Building a State Diagram  A state is represented by a rounded rectangle  A transition (i.e., event) is represented by a labeled arrow leading from one state to another  Syntax: trigger-signature [guard]/activity  The active state of an object indicates the current overall status of the object as is goes through transformation or processing  A state name represents one of the possible active states of an object  The passive state of an object is the current value of all of an object's attributes  A guard in a transition may contain the checking of the passive state of an object

Identifying Events  A use-case is examined for points of information exchange.  The homeowner uses the keypad to key in a four-digit password. The password is compared with the valid password stored in the system. If the password in incorrect, the control panel will beep once and reset itself for additional input. If the password is correct, the control panel awaits further action.

State Diagram State diagram for the ControlPanel class

Sequence Diagram Sequence diagram (partial) for the SafeHome security function

Summary Class Modeling CRC Behavioral modeling State diagrams Sequence diagrams