Model-Driven User Requirements Specification using SysML Authors: Michel dos Santos Soares, Jos Vrancken Source: Journal of Software(JSW), Vol. 3, No.

Slides:



Advertisements
Similar presentations
Andrea Maurino Web Service Design Methodology Batini, De Paoli, Maurino, Grega, Comerio WP2-WP3 Roma 24/11/2005.
Advertisements

Integration of MBSE and Virtual Engineering for Detailed Design
IT Requirements Capture Process. Motivation for this seminar Discovering system requirements is hard. Formally testing use case conformance is hard. We.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 8 Slide 1 System models.
The Unified Software Development Process - Workflows Ivar Jacobson, Grady Booch, James Rumbaugh Addison Wesley, 1999.
Computer Engineering 203 R Smith Requirements Management 6/ Requirements IEEE Standard Glossary A condition or capability needed by a user to solve.
Documenting Requirements using Use Case Diagrams
©Ian Sommerville 2000Software Engineering, 6/e, Chapter 71 System models l Abstract descriptions of systems whose requirements are being analysed.
Software Requirements
Software Engineering CSE470: Requirements Analysis 1 Requirements Analysis Defining the WHAT.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
SE 555 – Software Requirements & Specifications Introduction
SE 555 Software Requirements & Specification Requirements Analysis.
Course Instructor: Aisha Azeem
Requirements Engineering
Basic Concepts The Unified Modeling Language (UML) SYSC System Analysis and Design.
Architectural Design.
System Analysis & Design
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 1 Introduction to Software Engineering CEN 4010.
Software Engineering CS B Prof. George Heineman.
1 BTEC HNC Systems Support Castle College 2007/8 Systems Analysis Lecture 9 Introduction to Design.
Chapter 4 System Models A description of the various models that can be used to specify software systems.
System models Abstract descriptions of systems whose requirements are being analysed Abstract descriptions of systems whose requirements are being analysed.
المحاضرة الثالثة. Software Requirements Topics covered Functional and non-functional requirements User requirements System requirements Interface specification.
An Introduction to Software Architecture
Instructor: Peter Clarke
Dr. Tom WayCSC Software Requirements CSC 4700 Software Engineering Lecture 2 Based on Sommerville, Chapter 6.
UML Diagrams: Class Diagrams The Static Analysis Model Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
SOFTWARE DESIGN (SWD) Instructor: Dr. Hany H. Ammar
Programming in Java Unit 3. Learning outcome:  LO2:Be able to design Java solutions  LO3:Be able to implement Java solutions Assessment criteria: 
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?
© 2012 xtUML.org Bill Chown – Mentor Graphics Model Driven Engineering.
Requirements Capture. Four Steps of requirements capture List candidate requirements Understand system context Capture functional requirements Capture.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 11 Slide 1 Design.
1 Advanced Software Architecture Muhammad Bilal Bashir PhD Scholar (Computer Science) Mohammad Ali Jinnah University.
Requirement Handling
Requirements Specification. Welcome to Software Engineering: “Requirements Specification” “Requirements Specification”  Verb?  Noun?  “Specification”
1 CMPT 275 High Level Design Phase Modularization.
Requirements Engineering-Based Conceptual Modelling From: Requirements Engineering E. Insfran, O. Pastor and R. Wieringa Presented by Chin-Yi Tsai.
Requirements and Use Cases
Data Structures Using C++ 2E
Copyright ©2004 Virtusa Corporation | CONFIDENTIAL Requirement Engineering Virtusa Training Group 2004 Trainer: Ojitha Kumanayaka Duration : 1 hour.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
1 Unified Modeling Language, Version 2.0 Chapter 2.
UML Course Instructor: Rizwana Noor. Overview  Modeling  What is UML?  Why UML?  UML Diagrams  Use Case  Components  Relationships  Notations.
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
4+1 View Model of Software Architecture
Software Engineering, COMP201 Slide 1 Software Requirements BY M D ACHARYA Dept of Computer Science.
Software Engineering Lecture 10: System Engineering.
Using UML, Patterns, and Java Object-Oriented Software Engineering Chapter 2, Modeling with UML: UML 2 Metamodel Note to Instructor: The material in this.
1 SWE Introduction to Software Engineering Lecture 14 – System Modeling.
Lecture 5 Introduction to Use Case Analysis and the Analysis Model Introduction to the UML.
Requirement Elicitation Review – Class 8 Functional Requirements Nonfunctional Requirements Software Requirements document Requirements Validation and.
Introduction to Software Engineering 1. Software Engineering Failures – Complexity – Change 2. What is Software Engineering? – Using engineering approaches.
Dillon: CSE470: ANALYSIS1 Requirements l Specify functionality »model objects and resources »model behavior l Specify data interfaces »type, quantity,
1 Software Requirements Descriptions and specifications of a system.
1 Team Skill 3 Defining the System Part 1: Use Case Modeling Noureddine Abbadeni Al-Ain University of Science and Technology College of Engineering and.
Interface Concepts Modeling Core Team
Classifications of Software Requirements
Chapter 4 – Requirements Engineering
Chapter 5 Designing the Architecture Shari L. Pfleeger Joanne M. Atlee
Requirements Analysis
IMPORTANT NOTICE TO STUDENTS:
Software Requirements Specification Document
UML profiles.
An Introduction to Software Architecture
Software Engineering System Modeling Chapter 5 (Part 1) Dr.Doaa Sami
Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.
Software Development Process Using UML Recap
Presentation transcript:

Model-Driven User Requirements Specification using SysML Authors: Michel dos Santos Soares, Jos Vrancken Source: Journal of Software(JSW), Vol. 3, No. 6, 57-68, Jun 2008 ISSN X Presenter: Ming-Chih Li ESL, Dept. of CSIE, CCU 2011/03/11

Outline  Introduction  A Proposed User Requirements Classification  User Requirements Specification Using SysML Diagrams  SysML Requirements Diagram Extensions  Case Study  Discussion  Conclusion 2011/3/112

Introduction  Requirements engineering(RE) is an important phase in a system’s life cycle. When poorly performed failures, cost overrun and delays  RE can be divided into two main groups of activities Requirements development  Documenting and analyzing Requirements management 2011/3/113

Introduction (cont.)  Well-written user requirements documentation is fundamental as it facilitates later phases, not only during RE, but during the whole system life cycle. 2011/3/114

Introduction (cont.)  The increasing complexity of systems makes requirements engineering activities both more important and more difficult. large number of elements and reliability factors  must be decomposed into several smaller components increase the level of abstraction Model-driven approaches 2011/3/115

Introduction (cont.)  UML and its profiles(e.g. SysML, MARTE) are the current dominant graphical languages used in model- driven approaches  This paper is about applying a Model-Driven Requirements Engineering approach based on SysML  Requirements diagrams  Use Case diagrams 2011/3/116

Introduction (cont.)  First, a classification for each atomic requirement is proposed  the SysML Requirements diagram is used to represent graphically single user requirements and their relationships 2011/3/117

Introduction (cont.)  Then, User requirements are also represented in a tabular format, which may facilitate requirements tracing during the system life cycle.  Finally, SysML Use Case diagrams are applied to represent the actors involved and the use cases, giving a context diagram delimiting the system 2011/3/118

Introduction (cont.)  After being structured and graphically represented, user requirements may be detailed into systems requirements 2011/3/119

A Proposed User Requirements Classification  A common classification proposed for requirements is based on the level of abstraction functional  describes what the system should do non-functional  are related to emergent system properties, such as reliability and performance external  a detailed description of all inputs into and outputs from the software system 2011/3/1110

User Requirements Specification Using SysML Diagrams  The SysML Requirements Diagram is a stereotype of the UML Class diagram 2011/3/1111

User Requirements Specification Using SysML Diagrams (cont.)  Requirements relationships hierarchy derive satisfy  dependency relationship between a requirement and a model element verify  how a test case can verify a requirement refine trace 2011/3/1112

User Requirements Specification Using SysML Diagrams (cont.)  Requirements Table This allows an agile way to identify, prioritize and trace requirements 2011/3/1113

User Requirements Specification Using SysML Diagrams (cont.)  The SysML Use Case Diagram The SysML Use Case diagram is derived without important extensions from the UML 2.0 Use Case diagram The Use Case diagram shows system functionalities that are performed through the interaction of the system with its actors. 2011/3/1114

SysML Requirements Diagram Extensions 2011/3/1115 Type: tagged values e.g. Performance, Security and Efficiency for non-functional req. User, Hardware, Software and Communication for External Interface req.

SysML Requirements Diagram Extensions (cont.)  Grouping Requirements Requirements may be decomposed into atomic requirements, and may later even be related in the sense that together they are capable of delivering a whole feature 2011/3/1116

Case Study  The case study is based on a document with 79 atomic requirements for a road traffic management system.  We have selected in this paper to model the requirements of the Traffic Manager(TM, 10) and the Traffic Management Center(TMC, 8). 2011/3/1117

Case Study (cont.) 2011/3/1118

Case Study (cont.) 2011/3/1119

2011/3/1120

2011/3/1121

2011/3/1122

Discussion  natural language is the only description of requirements ambiguity, lack of easy visualization and impossibility to analyze and simulate.  SysML is a language is highly customizable and can be extended into families of languages Profiles may specialize language semantics, provide new graphical icons and domain-specific model libraries 2011/3/1123

Conclusion (cont.)  It is essential to have properly- structured and controlled requirements specifications  requirements tables are useful to represent decomposition in a tabular form and improve traceability  Using a specific diagram for requirements is a SysML advantage over UML 2011/3/1124

Conclusion  An extension to the basic SysML Requirements diagram is proposed, based on a classification for user requirements  It is also shown that related requirements can be grouped, which can be seen as an initial system decomposition into subsystems 2011/3/1125

 Thanks for your listening 2011/3/1126