SWR Use Case Modeling Francis Bordeleau (Mercury Computer Systems/Carleton University) Francois-Xavier Lebas (Thales)

Slides:



Advertisements
Similar presentations
Requirements Elicitation and Use Case Diagrams
Advertisements

Kellan Hilscher. Definition Different perspectives on the components, behavioral specifications, and interactions that make up a software system Importance.
Use Case Modeling SJTU. Unified Modeling Language (UML) l Standardized notation for object-oriented development l Needs to be used with an analysis and.
Object-Oriented Analysis and Design
Use-case Modeling.
Chapter 18 Object-Oriented Systems Analysis and Design Using UML
Systems Analysis and Design in a Changing World, Fourth Edition
L4-1-S1 UML Overview © M.E. Fayad SJSU -- CmpE Software Architectures Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I.
1 UML Component and Deployment Diagrams. Models, Views, and Diagrams Use Case Diagrams Use Case Diagrams Use Case Diagrams Scenario Diagrams Scenario.
IELM 511: Information System design
7. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Detailed Object-Oriented Requirements Definitions  System Processes—A Use.
Objectives Explain the purpose and objectives of object- oriented design Develop design class diagrams Develop interaction diagrams based on the principles.
Use Case Modeling.
Use Case Modeling. Kendall & Kendall© 2005 Pearson Prentice Hall18-2 Commonly Used UML Diagrams The most commonly used UML diagrams are: – Use case diagram,
Object-Oriented Analysis and Design
Chapter 7: The Object-Oriented Approach to Requirements
2005/05/25 Unified Modeling Lanauage 1 Introduction to Unified Modeling Language (UML) – Part One Ku-Yaw Chang Assistant Professor.
Programming in Java Unit 3. Learning outcome:  LO2:Be able to design Java solutions  LO3:Be able to implement Java solutions Assessment criteria: 
Chapter 7 Appendix A Object-Oriented Analysis and Design: Use Cases Modern Systems Analysis and Design Seventh Edition Jeffrey A. Hoffer Joey F. George.
Unified Modeling Language* Keng Siau University of Nebraska-Lincoln *Adapted from “Software Architecture and the UML” by Grady Booch.
L6-S1 UML Overview 2003 SJSU -- CmpE Advanced Object-Oriented Analysis & Design Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College.
ARTIFACT UML Actor A Use Case 1 Use Case 2 Actor B Document FileManager GraphicFile File Repository DocumentList FileList Customer name addr withdraw()
Requirements Engineering for Web Applications. SR: System Vision Document Written by key stakeholders Written by key stakeholders An executive summary.
Chapter 7 The Object-Oriented Approach to Requirements.
1 Version /05/2004 © 2004 Robert Oshana Requirements Engineering Use cases.
Logical view –show classes and objects Process view –models the executables Implementation view –Files, configuration and versions Deployment view –Physical.
Requirements Engineering for Web Applications. SR: System Vision Document Written by key stakeholders Written by key stakeholders An executive summary.
Systems Analysis and Design in a Changing World, Fourth Edition
Lecture 9-1 : Intro. to UML (Unified Modeling Language)
22 August, 2007Information System Design IT60105, Autumn 2007 Information System Design IT60105 Lecture 8 Use Case Diagrams.
UML (Unified Modeling Language)
CONNECTING COMPONENT Pertemuan Matakuliah: M Analisis dan Perancangan Sistem Informasi Lanjut Tahun:
1 5/18/2007ã 2007, Spencer Rugaber Architectural Documentation Graphical (views) and textual Kruchten's 4+1 Views –Philippe B. Kruchten. "The 4+1 View.
1 Architectural Blueprints—The “4+1” View Model of Software Architecture (
Object Oriented Programming and Data Abstraction Earl Huff Rowan University.
Use Case, Component and Deployment Diagrams University of Sunderland.
Appendix Object-Oriented Analysis and Design: Use Cases and Sequence Diagrams Modern Systems Analysis and Design Fifth Edition Jeffrey A. Hoffer Joey F.
7 Systems Analysis – ITEC 3155 The Object Oriented Approach – Use Cases.
1 Systems Analysis and Design Behavioral Modeling Chapter 8 (Last one before the Midterm!)
 Sequence Diagrams Introduction.  Sequence Diagrams  Review Schedule Sheridan.
Chapter 5 – System Modeling
CompSci 280 S Introduction to Software Development
Systems Analysis and Design in a Changing World, Fourth Edition
Chapter 7 Appendix A Object-Oriented Analysis and Design: Use Cases
UML(Unified Modeling Language)
Global Science and Technology, Inc., Greenbelt, MD, USA
Chapter 5 – System Modeling
Group Y Presenters: (indicate roles)
Object-oriented software testing
BTS430 Systems Analysis and Design using UML
Use Case Model.
Unified Modeling Language
Component and Deployment Diagrams
University of Central Florida COP 3330 Object Oriented Programming
System Modeling Chapter 4
Online Shopping APP.
UML: Unified modeling language
Princess Nourah bint Abdulrahman University
IELM 511: Information System design
אפיון ועיצוב מערכות מוכוון עצמים
Unified Modeling Language
Object Oriented Analysis and Design
Static Testing Static testing refers to testing that takes place without Execution - examining and reviewing it. Dynamic Testing Dynamic testing is what.
CS 8532: Advanced Software Engineering
Design Yaodong Bi.
Chapter 22 Object-Oriented Systems Analysis and Design and UML
CIS 375 Bruce R. Maxim UM-Dearborn
Uml diagrams In ooad.
<Your Team # > Your Team Name Here
Software Development Process Using UML Recap
Presentation transcript:

SWR Use Case Modeling Francis Bordeleau (Mercury Computer Systems/Carleton University) Francois-Xavier Lebas (Thales)

Usage of Statecharts and Sequence Diagram at the Use Case level Use statecharts at the use case level to give a high-level global overview of system behavior Use sequence diagrams to give an user-system interaction-based view of a use case Relationships between use case and statechart is many-to-one Relationship between use case and sequence diagram is one-to-many (potentially one sequence diagram for each possible scenario in a use case) Refinement between system level statechart and component statechart must be consistent Refinement between use case (black-box) level SD and white-box SD must be consistent, and must be consistent with class definitions

Top level Use Case Packages Current SWRadio spec includes Radio System Functionality Radio Set Functionality HF4285 Military Waveform Example In the new version of the SWRadio specification, they will constitute three different packages Relationships between the three packages will be explicit Radio System Package describes the global use cases/scenarios of a SWRadio system Radio Set Package describes the main use cases/scenarios of a radio set. This is the main focus of the current specification HF4285 Military Waveform is used as an example to illustrate and validate the general SWRadio use cases and scenarios described in the Radio Set and Radio System Packages We propose to promote the first two packages (Radio System Package and Radio Set Package) to the main part of the document and put the HF4285 Military Waveform in an appendix.

Main Radio System Main Use Cases Purpose Clarify end-users needs Delineates what is addressed at lower levels Proposed Use Cases Operational Use System Management Configure Deploy Diagnose

Radio Set Main Actors Give an overall actor diagram that describes the relationships between the main system actors Define the main actors using a template that provides Actor description List of system functionalities (use cases) in which the actor is involved For each functionality, the role of the actor in the system execution of that functionality

Radio Set Sub-Packages Operational Control Startup Shutdown Configure Replace Unit Maintenance Log related use cases Support Security? Security and Manage Security?

Main Radio Set Operational Use Cases Reception (Rx) Transmission (Tx) Configure Configure Software Configure Radio Set Download Different types of download?

RX Use Case Description

TX Use Case Description

Channel Configuration