Enhancing validation with Prototypes out of Requirements Model
|
|
- Dale Phelps
- 5 years ago
- Views:
Transcription
1 Enhancing validation with Prototypes out of Requirements Model Michael Deynet, Sabine Niebuhr, Björn Schindler Software Systems Engineering, Clausthal University of Technology, Clausthal-Zellerfeld, Germany {michael.deynet, sabine.niebuhr, ABSTRACT In large IT projects it is important that the supplier understands the needs (requirements) of the user on the acquirer s side correctly. The presented Requirements Engineering methodology picks up this problem and improves the communication between acquirer (including the user) and supplier. Our approach uses a requirements model based on UML to communicate the acquirers requirements to the supplier. We use this Requirements Model to generate an early prototype of the developed IT-system. This can be used to illustrate the main functionality of the IT system to get early feedback from the user. Keywords Requirements Engineering, Screen-Mockup Prototype, UML, Validation 1. Introduction In industry large IT projects are subdivided into two parts: the acquirers part and the suppliers part. At the beginning, the overall IT lifecycle process contains two processes: The Acquisition Process and the Supply Process (e.g. ISO 12207). The Acquisition Process contains the activities of the acquirer who acquires an IT product. The acquirer captures the users needs (requirements) of the IT system and represents them. On the other side the Supply Process contains the activities of the vendor who has closed a contract with the acquirer to develop an IT product. The following development process on the supplier s side defines the system requirements among other things on the basis of the requirements of the acquirer. The acquirer s requirements should meet the following properties: The requirements should be understandable, clearly described, minimal, verifiable, and realizable (all this for the user and for the supplier). Through this, the IT product will be more verifiable regarding costs, quality, time, maintainability and functionality. Currently there are existing two language types for specifying IT systems: Natural language and specialized (formal or semi-formal) languages like UML-based languages or domain specific languages. The natural language is often used in early steps in IT
2 projects mainly on acquires side to describe the System Requirements. Specialized languages are often used in later steps of IT projects (e.g. for code generation). The use of natural language causes some problems: Natural language is unclear and interpretable. Furthermore, it is not possible to provide tool support for natural language (e.g. for testing). By the use of specialized languages a lot of these problems can be eliminated. Generally the acquirer uses natural language to specify the requirements of a system. He handovers these requirements to the supplier who refines them and uses them for designing and implementing the system. Through this, the problems concerning natural language get worse because the requirements in natural language are going over organization boundaries. Thereby it is crucial that the supplier understands the requirements of the acquirer early in the right way because the success of the IT project depends on this. Thus, we improved the interface between acquirer and supplier. The acquirer collects the requirements in a more formal language (than natural language), so that the supplier understands it in a better way. To define the requirements on the acquirers side we mostly use UML. Hereby, the supplier understands the requirements early in the right way. Furthermore, we use the formally described requirements to generate an early prototype of the IT system. This has got a basic benefit: The later user of the IT system (who is not an IT professional) can understand the prototype (which represents the requirement) and validate the requirements of the IT system. 2. The New Requirements Engineering Approach To improve communication our focus was to change the crucial situation between acquirer and supplier. What we had to do was to change the partially existing process for Requirements Engineering and to change the syntax for the requirements specification. In most cases the requirements specification documents are written in plain text with some illustrating figures. Plain text holds the risk of misinterpretation (on the suppliers and acquirers side) and inconsistency. Our approach is supplementing the typical textual specification with an extended Requirements Model. We use this Requirements Model to generate an early prototype of the developed IT system. This can be used to illustrate the core functionality of the IT-system to get early feedback from the user. We handover the Requirements Model (including the prototype) to the supplier, so that he can use this to understand the requirements. By using a more precise language, like UML and the same understandable semantics we can reduce the communication gap between the supplier and the acquirer.
3 2.1. Requirements Engineering Model The aim of the Requirements Engineering methodology is an extended object oriented Requirements Model described in UML notation (Object Management Group, 2009). Our Requirements Model consists of 4 partial models: 1. Use Case Model: It describes the external view of the future system, using UML Use Case Diagrams and Use Case Tables. 2. Domain Model: It describes the domain entities using UML Class Diagrams. 3. Activity Model: It describes the sequences of the functions described in the Use Case Model. 4. Screen Mock-up Model: It sketches the future actor interface. Use Case Model, Domain Model and Activity Model are described in UML and therefore have a defined language as syntax, namely the UML profile. This means a well defined semantics for especially the UML activity diagrams, which are the core of the requirements model. Due to the execution semantics, the model can be interpreted by a machine and the modeling can be supported by a tool. 2.2 Requirements Engineering Methodology Our approach combines Requirements Engineering and Software Architecture Design in modeling the Requirements Engineering Model. The central activity of the Requirements Engineering methodology is designing this model. To fulfill the demands of Requirements Engineering regarding Architecture Design aspects we combine the Requirements Analysis with Object Oriented Analysis (e.g. Booch, 2007) and Model Based Design (e.g. Kleppe, 2003). Since we changed the language of the specification from natural language to the more formal language UML, we moved further communication and media gap between supplier and acquirer to a new communication gap between the supplier s requirements analyst and the user. For involving the users for requirements validation, the UML Requirements Model is enhanced with Screen-Mockups. Executing the Requirements Engineering methodology, this enhanced Requirements Model is used to generate a prototype out of the model to communicate with users. In the further processing of Requirements Engineering the user and the requirements analysts communicate through the prototype. As a benefit of prototyping the modeled requirements, we bridge this new gap, and the user is able to understand the specification again. The risk of an incomplete or false validation is minimized and the specification is closer to the users needs. The semantics of the Requirements Model, as well as the methodology to design the model are described in well defined syntax and semantics. Well defined syntax and semantics enable machines to interpret the methodology s description.
4 3. Requirements Model Our Requirements Model consists of 4 parts: The Use Case Model, the Domain Model, the Activity Model, and the Screen-Mockup Model. The Use Case Model describes the external view of the system. The Domain Model describes the Domain Entities of the system. Each Use Case (in the Use Case Model) is detailed with an Activity in the Activity Model. In these Activities the Domain Entities (of the Domain Model) are used to describe the information flow among themselves. The interfaces between the Activities and external Actors (e.g. other systems) are described with Screen-Mockups. These model parts and their relationships are pictured in Figure 1 (left). Please have a closer look on the model parts in the following. 3.1 Use Case Model The Use Cases in the Use Case Model are describing the system requirements on the highest level. For each Use Case a Use Case Table is used to describe the requirement. In Figure 1 (right) a Use Case Table for a Use Case is pictured. Activity Model Domain Model Screen-Mockup Model Use Case Model Name Brief description ID Description Actors Category Trigger Precondition Incoming Data Outgoing Data Postcondition Standard sequence Alternative sequence Miscellaneous Figure 1: Left: Overview Requirements Model; Right: Use Cases and Use Case Table 3.2 Activity Model For each Use Case an Activity is created to decompose the high level requirement into a sequence of (more detailed) requirements (called Actions). To permit a later prototype
5 generation we had to define extensions to the UML Activities in terms of UML profiles. These extensions are described below Interface Action To describe the interface between the system and external actors we defined a special type of Action, the Interface Action. The Interface Action refers to a Screen-Mockup which defines the data (elements from the domain model) exchanged through the described interface. The Interface Action can have Input or Output Pins (both with the stereotype «InterfacePin»). With these Pins it is possible to get or set objects which are transported over the interface from/to the Actors. For example in Figure 2 (left) the system gets the called party from the inter-phone system. This party (variable cp ) can be used for further processing in the Activity. ActivityModel Use Case Model ActivityModel Figure 2: Left: Interface action to describe the interaction between Actors and the system; Right: Service Actions to describe functions the system processes on its own Service Action Service Actions are used to describe functions that the system executes on its own. They can also have Input and Output Pins (stereotype «VariablePin»). Input Pins are parameters on which the service action executes its output. This output is described as Output Pins of the Service Action. The output of a Service Action can for example be used for further decisions of the control flow, shown in Figure 2 (right). Here route is the variable which has a reference to the object which is the output of the Service Action Calculate route Variables To enable an automatic prototype generation we elaborated a variable concept for UML Activities: We distinguish between variable declaration and variable use in UML
6 Activities. We use the Object Nodes with the stereotype «Variable» for variable declaration. In Figure 2 (left) for example the variable with the name cp and from the type party is declared. Variables can be used as input or output of Actions. This is provided by Input and Output Pins with the stereotype «VariablePin» Call Behavior Action The presented methodology was elaborated to specify an embedded communication system. There was a need to handle the creation of multiple instances of Activities. This instantiation is provided by the Call Behavior Action (see Figure 3 (left)). Multiple instances can be created by executing the Call Behavior Action several times (seefigure 3 (right)). ActivityProviding LAN communication Figure 3: Left: Call Behavior Action to create an instance of an Activity; Right: Multiple instances of one Activity Signals The communication between Activities is provided by signals. A signal has a name ( Send Voice Message, Figure 4 (left)), a reference to the object which is transferred (InputPin voice message with stereotype «VariablePin») and a target (InputPin wi with stereotype «MessageTargetPin»). wi is a variable of the type Providing wireless communication (this is an Activity). So, the voice message is sent to the Activity which is referenced by the variable wi. The variable wi is previously set by the Service Action Get Wireless Instance. 3.3 Domain Model We use UML class diagrams to describe the domain entities of the system. In the Activity Model these Entities can be used to declare variables (see Figure 4 (right)) and to use these variables with Input and OutputPins. In the Activity Model in Figure 2 (left) the variable cp is declared. This variable has the type party which is defined in the
7 Domain Model. cp is used in the Activity Model as OutputPin of the Interface Action Get called party. ActivityModel ActivityModel Domain Model Figure 4: Left: Signals for inter-activity communication; Right: Use of Domain Entities in the Activity Model 3.4 Screen-Mockup Model The interface between external actors and the system is described with Screen- Mockups. This can be a User Interface (if the actor is a user) or any other interface where data is transmitted (if the actor is another system). Figure 5 (left) shows the Screen-Mockup Create NPC. This Mockup contains a Label (element Name with stereotype «MockupLabel»), a button (element Create with stereotype «MockupButton») and a textfield (element NameTextfield with stereotype «MockupTextfield») where the user can enter a text. An Interface Action in the Activity Model refers to a Screen-Mockup in the Screen- Mockup Model (see Figure 5 (right)). The Interface Action Create NPC refers to the Mockup Create NPC. The Textfield NameTextfield of the Mockup is mapped to the OutputPin of the Interface Action ( mockupelement=nametextfield in the specification of the OutputPin). If the Interface Action is active the user can enter the input in the Textfield NameTextfield of the Screen-Mockup. In the further processing of the Activity this input is copied to the variable newpc.name over the OutputPin. 4. Prototype Generation Through the previous sketched extensions to the UML Activities in terms of UML profiles the requirements model has a precise semantics with a well defined syntax. With this well defined execution semantics, the model is interpretable by a tool. In the following we present how the requirements model is used to generate a prototype of the system.
8 If the generated prototype is started the execution begins with an overview of the system functionality (see Figure 6 (left)). Thereby, for each Use Case in the Use Case Model a button is created. Screen-Mockup Model Activity Model Figure 5: Left: Screen-Mockup Model; Right: Mapping InterfaceAction with Screen-Mockup and InterfacePin with a Mockup-Element There exists an underlying Activity (in the Activity Model) for each Use Case in the Use Case Model. This underlying Activity is executed by clicking on the corresponding button on the overview page in the prototype. 4.1 Activity execution We enrich elements (e.g. actions, pins, object nodes) used in the UML activities with stereotypes. This allows us to classify these elements into several groups, depending on their functionality. In the following, the most important stereotypes are explained: An «Interface Action» describes actions which deal with user interactions. If an Interface Action is executed, the prototype will show the associated Screen-Mockup and the user of the prototype can simulate the Actor who communicates with the system in this Action. Figure 7 shows the Interface Action Create NPC which references to the analogous Screen-Mockup. A «Service Action» describes an action the system executes on its own. If a Service Action is active the user of the prototype has to simulate the processing of the Service
9 Action on the basis of the data which are copied to the Input Pins the Service Action owns. Use Case Model Prototype Figure 6: Left: Each Use Case is represented by a button in the prototype; Right: Decision nodes In the prototype, decision nodes have to be simulated by the user (e.g. if the user is logged in, see Figure 6 (right)). If a decision node is executed, a dialogue with a list of all possible decisions appears in the prototype. The possible decisions result from the outgoing edges and their guards. 5. Preliminary lessons learned The presented RE Methodology is applied in a real project in the field of public administration on the acquirer s side. We are currently finalizing the requirements model and are validating this with the user using generated prototypes. Activity Model Active Screen-Mockup Model B A C A D E Prototype B D E C Figure 7: Screen-Mockup and corresponding windows of the Prototype
10 Using the generated prototypes enhances the communication with the user, especially in early steps of IT projects. The user gets able to understand the specified core functionality of the IT system and can validate this with his needs. We defined a very clear syntax and execution semantics for the requirements model to generate these prototypes. The maintenance of the requirements model is very complex and the requirements engineer has to fulfill a high level of expertise to maintain the requirements model. To pickup this disadvantage we are elaborating a finder-grained tool support for specifying the requirements in the requirements model. 6. Conclusions In this paper a Requirements Engineering methodology is presented which improves the communication between user, acquirer and supplier. This methodology uses a requirements model based on UML. It consists of 4 parts: Use Case Model, Activity Model, Domain Model and Screen-Mockup Model. The Use Cases are used to describe the external view of the system. Each Use Case is refined with an Activity. This Activity describes the sequences of the functions described in the Use Case Model. The Domain Model describes the domain entities using UML Class Diagrams. The Screen-Mockup Model sketches the interface between external Actors and the system. The paper details the modeling approach and the syntax of the requirements model and shows the relations between the particular model elements. Furthermore, the execution semantics of the requirements model which is used to generate early prototypes of the system is shown. 7. References Booch, G. et.al (2007). Object-Oriented Analysis and Design with Applications. 3rd ed. Boston ISO (1995). Systems and software engineering -- Software life cycle processes Object Management Group (2009, 1th July). Kleppe, A. (2003). MDA Explained: The Model Driven Architecture. Boston. Acknowledgements Thanks to Andreas Rausch who takes a leading part in elaborating the presented Requirements Engineering Methodology. Copyright Copyright 2010 Michael Deynet, Sabine Niebuhr, Björn Schindler. The author(s) assign to NACCQ and educational non-profit institutions a non-exclusive licence to use this document for personal use and in courses of instruction provided that the article is used in full and this copyright statement is reproduced. The author(s) also grant a non-exclusive licence to NACCQ to publish this document in full on the World Wide Web (prime sites and mirrors) and in printed form within the Bulletin of Applied Computing and Information Technology. Any other usage is prohibited without the express permission of the author(s).
Refinement and Formalization of Semi-Formal Use Case Descriptions
Refinement and Formalization of Semi-Formal Use Case Descriptions Matthias Riebisch, Michael Hübner Ilmenau Technical University Max-Planck-Ring 14; 98684 Ilmenau; Germany {matthias.riebisch michael.huebner}@tu-ilmenau.de
More informationOpen Work of Two-Hemisphere Model Transformation Definition into UML Class Diagram in the Context of MDA
Open Work of Two-Hemisphere Model Transformation Definition into UML Class Diagram in the Context of MDA Oksana Nikiforova and Natalja Pavlova Department of Applied Computer Science, Riga Technical University,
More informationAn Agent Modeling Language Implementing Protocols through Capabilities
An Agent Modeling Language Implementing Protocols through Capabilities Nikolaos Spanoudakis 1,2 1 Technical University of Crete, Greece nikos@science.tuc.gr Pavlos Moraitis 2 2 Paris Descartes University,
More informationRequirements Modelling and Software Systems Implementation Using Formal Languages
Requirements Modelling and Software Systems Implementation Using Formal Languages Radek Kočí Brno University of Technology, Faculty of Information Technology Czech Republic koci@fit.vutbr.cz ICSEA 2018,
More informationDesigning a System Engineering Environment in a structured way
Designing a System Engineering Environment in a structured way Anna Todino Ivo Viglietti Bruno Tranchero Leonardo-Finmeccanica Aircraft Division Torino, Italy Copyright held by the authors. Rubén de Juan
More informationSoftware Engineering from a
Software Engineering from a modeling perspective Robert B. France Dept. of Computer Science Colorado State University USA france@cs.colostate.edu Softwaredevelopment problems Little or no prior planning
More informationIngegneria del Software Corso di Laurea in Informatica per il Management. Introduction to UML
Ingegneria del Software Corso di Laurea in Informatica per il Management Introduction to UML Davide Rossi Dipartimento di Informatica Università di Bologna Modeling A model is an (abstract) representation
More informationISO Compliant Automatic Requirements-Based Testing for TargetLink
ISO 26262 Compliant Automatic Requirements-Based Testing for TargetLink Dr. Udo Brockmeyer CEO BTC Embedded Systems AG An der Schmiede 4, 26135 Oldenburg, Germany udo.brockmeyer@btc-es.de Adrian Valea
More informationUNIT-4 Behavioral Diagrams
UNIT-4 Behavioral Diagrams P. P. Mahale Behavioral Diagrams Use Case Diagram high-level behaviors of the system, user goals, external entities: actors Sequence Diagram focus on time ordering of messages
More informationObjectives Pre-Test Questions Introduction Collaboration Diagrams Flow of Events and Special Requirements...
10 Analysis Modeling M MAJOR A J O R T TOPICSO P I C S Objectives... 144 Pre-Test Questions...144 Introduction... 145 Collaboration Diagrams... 145 Flow of Events and Special Requirements... 151 Class-Responsibility-Collaboration
More informationSUMMARY: MODEL DRIVEN SECURITY
SUMMARY: MODEL DRIVEN SECURITY JAN-FILIP ZAGALAK, JZAGALAK@STUDENT.ETHZ.CH Model Driven Security: From UML Models to Access Control Infrastructres David Basin, Juergen Doser, ETH Zuerich Torsten lodderstedt,
More informationISO compliant verification of functional requirements in the model-based software development process
requirements in the model-based software development process Hans J. Holberg SVP Marketing & Sales, BTC Embedded Systems AG An der Schmiede 4, 26135 Oldenburg, Germany hans.j.holberg@btc-es.de Dr. Udo
More informationUML for Real-Time Overview
Abstract UML for Real-Time Overview Andrew Lyons April 1998 This paper explains how the Unified Modeling Language (UML), and powerful modeling constructs originally developed for the modeling of complex
More informationA Model-Based Development Method for Device Drivers
A Model-Based Development Method for Device Drivers Michael Kersten Siemens AG Otto-Hahn-Ring 6 D-81739 München Ulrich Margull 1 mal 1 Software GmbH Maxstr. 31 D-90762 Fürth Nikolaus Regnat Siemens AG
More informationBusiness Object Type Library Draft Technical Specification
Draft Technical Specification Page 1 Object Type Library Draft Technical Specification Object Type Library... 1 Draft Technical Specification... 1 Version Information... 2 Executive Summary... 2 ebtwg
More informationA UML 2 Profile for Variability Models and their Dependency to Business Processes
A UML 2 Profile for Variability Models and their Dependency to Business Processes Birgit Korherr and Beate List Women s Postgraduate College for Internet Technologies Institute of Software Technology and
More informationOO Analysis and Design with UML 2 and UP
OO Analysis and Design with UML 2 and UP Dr. Jim Arlow, Zuhlke Engineering Limited Clear View Training 2008 v2.5 1 UML principles Clear View Training 2008 v2.5 2 1.2 What is UML? Unified Modelling Language
More informationCHAPTER 1. Topic: UML Overview. CHAPTER 1: Topic 1. Topic: UML Overview
CHAPTER 1 Topic: UML Overview After studying this Chapter, students should be able to: Describe the goals of UML. Analyze the History of UML. Evaluate the use of UML in an area of interest. CHAPTER 1:
More informationAn Evaluation of a Use Case Driven Requirements Analysis Using Web UI Prototype Generation Tool
An Evaluation of a Use Case Driven Requirements Analysis Using Web UI Prototype Generation Tool SHINPEI OGATA Function Control System, Graduate School of Engineering Shibaura Institute of Technology 307
More informationSCOOP A contract-based concurrent object-oriented programming model
SCOOP A contract-based concurrent object-oriented programming model Benjamin Morandi 1, Sebastian S. Bauer 2, and Bertrand Meyer 1 1 Chair of Software Engineering, Swiss Federal Institute of Technology
More informationINTRODUCING A MULTIVIEW SOFTWARE ARCHITECTURE PROCESS BY EXAMPLE Ahmad K heir 1, Hala Naja 1 and Mourad Oussalah 2
INTRODUCING A MULTIVIEW SOFTWARE ARCHITECTURE PROCESS BY EXAMPLE Ahmad K heir 1, Hala Naja 1 and Mourad Oussalah 2 1 Faculty of Sciences, Lebanese University 2 LINA Laboratory, University of Nantes ABSTRACT:
More informationSelection of UML Models for Test Case Generation: A Discussion on Techniques to Generate Test Cases
St. Cloud State University therepository at St. Cloud State Culminating Projects in Computer Science and Information Technology Department of Computer Science and Information Technology 6-2018 Selection
More informationGeneralized Document Data Model for Integrating Autonomous Applications
6 th International Conference on Applied Informatics Eger, Hungary, January 27 31, 2004. Generalized Document Data Model for Integrating Autonomous Applications Zsolt Hernáth, Zoltán Vincellér Abstract
More informationTest requirements in networked systems
Test requirements in networked systems Jürgen Klüser, Vector Informatik GmbH The use of CAN with J1939 or CANopen based higher layers leads to cost efficient and flexible solutions, but together with a
More informationSCOS-2000 Technical Note
SCOS-2000 Technical Note MDA Study Prototyping Technical Note Document Reference: Document Status: Issue 1.0 Prepared By: Eugenio Zanatta MDA Study Prototyping Page: 2 Action Name Date Signature Prepared
More informationUML part I. UML part I 1/41
UML part I UML part I 1/41 UML part I 2/41 UML - Unified Modeling Language unified it can be shared among workers modeling it can be used for description of software model language it has defined structure
More informationJOURNAL OF OBJECT TECHNOLOGY
JOURNAL OF OBJECT TECHNOLOGY Online at http://www.jot.fm. Published by ETH Zurich, Chair of Software Engineering JOT, 2004 Vol. 3, No. 7, July-August 2004 UML 2 Activity and Action Models Part 5: Partitions
More informationPattern for Structuring UML-Compatible Software Project Repositories
Pattern for Structuring UML-Compatible Software Project Repositories Pavel Hruby Navision Software a/s Frydenlunds Allé 6 2950 Vedbaek, Denmark E-mail: ph@navision.com Web site: www.navision.com/services/methodology/default.asp
More informationIndex. business modeling syntax 181 business process modeling 57 business rule 40
OCL.book Page 203 Tuesday, July 22, 2003 9:48 PM Index Symbols OclAny, of 167 = OclAny, of 167 @pre 34, 86, 155 ^ 34, 156 ^^ 157 A abstract syntax 93 accumulator 153 action in statechart 56 activity
More informationCSCU9T4: Managing Information
CSCU9T4: Managing Information CSCU9T4 Spring 2016 1 The Module Module co-ordinator: Dr Gabriela Ochoa Lectures by: Prof Leslie Smith (l.s.smith@cs.stir.ac.uk) and Dr Nadarajen Veerapen (nve@cs.stir.ac.uk)
More informationObjectives. Explain the purpose and objectives of objectoriented. Develop design class diagrams
Objectives Explain the purpose and objectives of objectoriented design Develop design class diagrams Develop interaction diagrams based on the principles of object responsibility and use case controllers
More informationEvaluating OO-CASE tools: OO research meets practice
Evaluating OO-CASE tools: OO research meets practice Danny Greefhorst, Matthijs Maat, Rob Maijers {greefhorst, maat, maijers}@serc.nl Software Engineering Research Centre - SERC PO Box 424 3500 AK Utrecht
More informationBusiness Modelling. PRACTICAL OBJECT-ORIENTED DESIGN WITH UML 2e. Early phase of development Inputs: Activities: informal specification
PRACTICAL OBJECT-ORIENTED DESIGN WITH UML 2e Chapter 4: Restaurant System: Business Modelling Slide 1/1 Business Modelling Early phase of development Inputs: informal specification Activities: create use
More informationConstruction of BPMN-based Business Process Model Base
Construction of BPMN-based Business Process Model Base Yanjie Lu Hongming Cai Lihong Jiang Shanghai Jiaotong University hmcai@sjtu.edu.cn doi:10.4156/ijiip.vol1. issue2.3 Shanghai Jiaotong University lvyanjie@sjtu.edu.cn
More informationModel Driven Development of Component Centric Applications
Model Driven Development of Component Centric Applications Andreas Heberle (entory AG), Rainer Neumann (PTV AG) Abstract. The development of applications has to be as efficient as possible. The Model Driven
More informationExercise Unit 2: Modeling Paradigms - RT-UML. UML: The Unified Modeling Language. Statecharts. RT-UML in AnyLogic
Exercise Unit 2: Modeling Paradigms - RT-UML UML: The Unified Modeling Language Statecharts RT-UML in AnyLogic Simulation and Modeling I Modeling with RT-UML 1 RT-UML: UML Unified Modeling Language a mix
More informationTopic : Object Oriented Design Principles
Topic : Object Oriented Design Principles Software Engineering Faculty of Computing Universiti Teknologi Malaysia Objectives Describe the differences between requirements activities and design activities
More informationFormal Foundations of Software Engineering
Formal Foundations of Software Engineering http://d3s.mff.cuni.cz Martin Nečaský Pavel Parízek CHARLES UNIVERSITY IN PRAGUE faculty of mathematics and physics Goals of the course Show methods and tools
More informationPerspectives on User Story Based Visual Transformations
Perspectives on User Story Based Visual Transformations Yves Wautelet 1, Samedi Heng 2, and Manuel Kolp 2 1 KU Leuven, Belgium yves.wautelet@kuleuven.be, 2 LouRIM, Université catholique de Louvain, Belgium
More informationThe etrice Eclipse Project Proposal
The etrice Eclipse Project Proposal Dipl.-Ing. Thomas Schütz, Protos Software GmbH Eclipse Embedded Day 2010, Stuttgart Agenda Motivation Scope of etrice ROOM Language Codegenerators Middleware Realization
More informationMethods for requirements engineering
Methods for requirements engineering Objectives To explain the role of methods and techniques in requirements engineering To introduce data-flow modelling To introduce semantic data modelling To introduce
More informationIntroduction to Software Engineering. ECSE-321 Unit 9 Architectural Design Approaches
Introduction to Software Engineering ECSE-321 Unit 9 Architectural Design Approaches Requirement Elicitation Analysis (Software Product Design) Architectural Design Detailed Design Architectural Design
More information12 Tutorial on UML. TIMe TIMe Electronic Textbook
TIMe TIMe Electronic Textbook 12 Tutorial on UML Introduction......................................................2.................................................3 Diagrams in UML..................................................3
More informationModeling Crisis Management System With the Restricted Use Case Modeling Approach
Modeling Crisis Management System With the Restricted Use Case Modeling Approach Gong Zhang 1, Tao Yue 2, and Shaukat Ali 3 1 School of Computer Science and Engineering, Beihang University, Beijing, China
More informationMEMOCenterNG A full-featured modeling environment for organization modeling and model-driven software development
MEMOCenterNG A full-featured modeling environment for organization modeling and model-driven software development Jens Gulden and Prof. Dr. Ulrich Frank University Duisburg-Essen, Universitaetsstr. 9,
More informationDefinition of Information Systems
Information Systems Modeling To provide a foundation for the discussions throughout this book, this chapter begins by defining what is actually meant by the term information system. The focus is on model-driven
More informationASSURING DATA INTEROPERABILITY THROUGH THE USE OF FORMAL MODELS OF VISA PAYMENT MESSAGES (Category: Practice-Oriented Paper)
ASSURING DATA INTEROPERABILITY THROUGH THE USE OF FORMAL MODELS OF VISA PAYMENT MESSAGES (Category: Practice-Oriented Paper) Joseph Bugajski Visa International JBugajsk@visa.com Philippe De Smedt Visa
More informationUML REFERENCE SHEETS. 2013, 2014 Michael Marking; all rights reserved, including moral rights. Web site:
UML Reference Sheets 2013, 2014 Michael Marking; all rights reserved, including moral rights. Web site: http://www.tatanka.com/ Revision Information This document was last revised 2014.03.02. The current
More informationFormal Verification for safety critical requirements From Unit-Test to HIL
Formal Verification for safety critical requirements From Unit-Test to HIL Markus Gros Director Product Sales Europe & North America BTC Embedded Systems AG Berlin, Germany markus.gros@btc-es.de Hans Jürgen
More informationA PROPOSAL FOR MODELING THE CONTROL SYSTEM FOR THE SPANISH LIGHT SOURCE IN UML
A PROPOSAL FOR MODELING THE CONTROL SYSTEM FOR THE SPANISH LIGHT SOURCE IN UML D. Beltran*, LLS, Barcelona, Spain M. Gonzalez, CERN, Geneva, Switzerlan Abstract CELLS (Consorcio para la construcción, equipamiento
More informationProblems and Solutions by Using the Integrated Domain Modeling Toolset
Problems and Solutions by Using the Integrated Domain Modeling Toolset Kelly Verónica Fernández Céspedes, Riga Technical University, Latvia doi: 10.1515/acss-2015-0011 Abstract To contribute to the analysis
More informationUSE CASE BASED REQUIREMENTS VERIFICATION
USE CASE BASED REQUIREMENTS VERIFICATION Verifying the consistency between use cases and assertions Stéphane S. Somé, Divya K. Nair School of Information Technology and Engineering (SITE), University of
More informationDimensions for the Separation of Concerns in Describing Software Development Processes
Dimensions for the Separation of Concerns in Describing Software Development Processes Pavel Hruby Navision Software Frydenlunds Allé 6 DK-2950 Vedbæk, Denmark ph@navision.com http://www.navision.com,
More informationBPMN Working Draft. 1. Introduction
1. Introduction The Business Process Management Initiative (BPMI) has developed a standard Business Process Modeling Notation (BPMN). The primary goal of BPMN is to provide a notation that is readily understandable
More informationObject Oriented Modeling
Overview UML Unified Modeling Language What is Modeling? What is UML? A brief history of UML Understanding the basics of UML UML diagrams UML Modeling tools 2 Modeling Object Oriented Modeling Describing
More informationETSI ETR 346 TECHNICAL December 1996 REPORT
ETSI ETR 346 TECHNICAL December 1996 REPORT Source: ETSI TC-RES Reference: DTR/RES-06013-1 ICS: 33.020 Key words: Testing, TTCN, abstract test suite, validation Radio Equipment and Systems (RES); Trans-European
More informationUNIT I. 3. Write a short notes on process view of 4+1 architecture. 4. Why is object-oriented approach superior to procedural approach?
Department: Information Technology Questions Bank Class: B.E. (I.T) Prof. Bhujbal Dnyaneshwar K. Subject: Object Oriented Modeling & Design dnyanesh.bhujbal11@gmail.com ------------------------------------------------------------------------------------------------------------
More informationJOURNAL OF OBJECT TECHNOLOGY
JOURNAL OF OBJECT TECHNOLOGY Online at http://www.jot.fm. Published by ETH Zurich, Chair of Software Engineering JOT, 2003 Vol. 2, No. 6, November-December 2003 UML 2 Activity and Action Models Part 3:
More informationAgent-Oriented Software Engineering
Agent-Oriented Software Engineering Lin Zuoquan Information Science Department Peking University lz@is.pku.edu.cn http://www.is.pku.edu.cn/~lz/teaching/stm/saswws.html Outline Introduction AOSE Agent-oriented
More informationFormal specification of semantics of UML 2.0 activity diagrams by using Graph Transformation Systems
Formal specification of semantics of UML 2.0 activity diagrams by using Graph Transformation Systems Somayeh Azizi 1, Vahid Panahi 2 Computer science department, Sama Technical and vocational, Training
More informationCOAP 3110 INTERACTIVE SITE DEVELOPMENT
COAP 3110 INTERACTIVE SITE DEVELOPMENT http://wwwai.wu-wien.ac.at/~hahsler/webster/coap3110/ Instructor Michael Hahsler Tel. 31336/6081 0699 100 00 598 E-mail: hahsler@ai.wu-wien.ac.at 1 Course description
More informationCHAPTER 5 CO:-Sketch component diagram using basic notations 5.1 Component Diagram (4M) Sample Component Diagram 5.2 Deployment Diagram (8M)
CHAPTER 5 CO:-Sketch component diagram using basic notations 5.1 Component Diagram (4M) Sample Component Diagram 5.2 Deployment Diagram (8M) Sample Deployment diagram Component diagrams are different in
More informationChapter 3 Research Method
Chapter 3 Research Method 3.1 A Ontology-Based Method As we mention in section 2.3.6, we need a common approach to build up our ontologies for different B2B standards. In this chapter, we present a ontology-based
More informationlnteroperability of Standards to Support Application Integration
lnteroperability of Standards to Support Application Integration Em delahostria Rockwell Automation, USA, em.delahostria@ra.rockwell.com Abstract: One of the key challenges in the design, implementation,
More informationSmart Driver Assistant Software Requirements Specifications
2016 Software Requirements Specifications SEYMUR MAMMADLI SHKELQIM MEMOLLA NAIL IBRAHIMLI MEHMET KURHAN MIDDLE EAST TECHNICAL UNIVERSITY Department Of Computer Engineering Preface This document contains
More informationModeling automatic train regulation systems
Modeling automatic train regulation systems J.K. Tobin Alcatel Canada Inc., Transport Automation Systems, Canada Abstract The increasing complexity of automatic train supervision and regulation systems
More informationRich Hilliard 20 February 2011
Metamodels in 42010 Executive summary: The purpose of this note is to investigate the use of metamodels in IEEE 1471 ISO/IEC 42010. In the present draft, metamodels serve two roles: (1) to describe the
More informationOBJECT ORIENTED DESIGN with the Unified Process. Use Case Realization
OBJECT ORIENTED DESIGN with the Unified Process Use Case Realization Objectives Explain the purpose and objectives of objectoriented design Develop design class diagrams Develop detailed sequence diagrams
More informationRequirement Analysis
Requirement Analysis Requirements Analysis & Specification Objective: determine what the system must do to solve the problem (without describing how) Done by Analyst (also called Requirements Analyst)
More informationCover Page. The handle holds various files of this Leiden University dissertation
Cover Page The handle http://hdl.handle.net/1887/22891 holds various files of this Leiden University dissertation Author: Gouw, Stijn de Title: Combining monitoring with run-time assertion checking Issue
More informationSemantics-Based Integration of Embedded Systems Models
Semantics-Based Integration of Embedded Systems Models Project András Balogh, OptixWare Research & Development Ltd. n 100021 Outline Embedded systems overview Overview of the GENESYS-INDEXYS approach Current
More informationAGH University of Science and Technology Computer Science Laboratory Department of Automatics Al. Mickiewicza Kraków, POLAND
AGH University of Science and Technology Computer Science Laboratory Department of Automatics Al. Mickiewicza 30 30-059 Kraków, POLAND Analysis of UML Representation for XTT and ARD Rule Design Methods
More informationSoftware Development Methodologies
Software Development Methodologies Lecturer: Raman Ramsin Lecture 3 Seminal Object-Oriented Methodologies: A Feature-Focused Review 1 Responsibility-Driven Design (RDD) Introduced in 1990; a UML-based
More informationUML 2.0 UML 2.0. Scott Uk-Jin Lee. Division of Computer Science, College of Computing Hanyang University ERICA Campus
UML 2.0 Division of Computer Science, College of Computing Hanyang University ERICA Campus Introduction to UML 2.0 UML Unified Modeling Language Visual language for specifying, constructing and documenting
More informationLab Manual. Object Oriented Analysis And Design. TE(Computer) VI semester
Lab Manual Object Oriented Analysis And Design TE(Computer) VI semester Index Sr. No. Title of Programming Assignment Page No. 1 2 3 4 5 6 7 8 9 10 Study of Use Case Diagram Study of Activity Diagram Study
More informationIBM Rational Rhapsody
IBM Rational Rhapsody IBM Rational Rhapsody TestConductor Add On Qualification Kit for DO-178B/C Overview Version 1.9 License Agreement No part of this publication may be reproduced, transmitted, stored
More informationHITSP/T16. October 15, 2007 Version 1.1. Healthcare Information Technology Standards Panel. Security and Privacy Technical Committee.
October 15, 2007 Version 1.1 HITSP/T16 Submitted to: Healthcare Information Technology Standards Panel Submitted by: Security and Privacy Technical Committee 20071015 V1.1 D O C U M E N T C H A N G E H
More informationUML Fundamental. OutLine. NetFusion Tech. Co., Ltd. Jack Lee. Use-case diagram Class diagram Sequence diagram
UML Fundamental NetFusion Tech. Co., Ltd. Jack Lee 2008/4/7 1 Use-case diagram Class diagram Sequence diagram OutLine Communication diagram State machine Activity diagram 2 1 What is UML? Unified Modeling
More informationINTRODUCTION TO UNIFIED MODELING MODEL (UML) & DFD. Slides by: Shree Jaswal
INTRODUCTION TO UNIFIED MODELING MODEL (UML) & DFD Slides by: Shree Jaswal What is UML? 2 It is a standard graphical language for modeling object oriented software. It was developed in mid 90 s by collaborative
More informationchallenges in domain-specific modeling raphaël mannadiar august 27, 2009
challenges in domain-specific modeling raphaël mannadiar august 27, 2009 raphaël mannadiar challenges in domain-specific modeling 1/59 outline 1 introduction 2 approaches 3 debugging and simulation 4 differencing
More information7 The proposed domain specific language: operational level
7 The proposed domain specific language: operational level In our methodology, a scenario corresponds to the specification of concrete activities in the pervasive mobile game, including interactions among
More informationK-Model Structured Design of Configuration Models
K-Model Structured Design of Configuration Models Dr. Axel Brinkop 1 and Dr. Thorsten Krebs 2 and Hartmut Schlee 3 Abstract. 3 The purpose of this paper is to introduce the novel knowledge acquisition
More informationETSI TS V1.2.1 ( )
TS 101 871-2 V1.2.1 (2003-04) Technical Specification Digital Enhanced Cordless Telecommunications (DECT); Application Specific Access Profile (ASAP); DECT Multimedia Access Profile (DMAP); Profile requirement
More informationBusiness-Driven Software Engineering Lecture 5 Business Process Model and Notation
Business-Driven Software Engineering Lecture 5 Business Process Model and Notation Jochen Küster jku@zurich.ibm.com Agenda BPMN Introduction BPMN Overview BPMN Advanced Concepts Introduction to Syntax
More informationUML 2.0 State Machines
UML 2.0 State Machines Frederic.Mallet@unice.fr Université Nice Sophia Antipolis M1 Formalisms for the functional and temporal analysis With R. de Simone Objectives UML, OMG and MDA Main diagrams in UML
More informationETSI EG V1.2.1 ( )
EG 201 872 V1.2.1 (2001-08) Guide Methods for Testing and Specification (MTS); Methodological approach to the use of object-orientation in the standards making process 2 EG 201 872 V1.2.1 (2001-08) Reference
More informationDesign and Evolution of an Agent-Based CASE System for OOAD
Proceedings of ATS 2003 206 Design and Evolution of an -Based CASE System for OOAD Dong Liu, Kalaivani Subramaniam, Behrouz H. Far, and Armin Eberlein Department of Electrical and Computer Engineering
More informationRequirements Validation and Negotiation
REQUIREMENTS ENGINEERING LECTURE 2015/2016 Eddy Groen Requirements Validation and Negotiation AGENDA Fundamentals of Requirements Validation Fundamentals of Requirements Negotiation Quality Aspects of
More information1: Specifying Requirements with Use Case Diagrams
Outline UML Design Supplement 1: Specifying Requirements with Use Case Diagrams Introduction Use Case Diagrams Writing Use Cases Guidelines for Effective Use Cases Slide adapted from Eran Toch s lecture
More informationSEMANTIC WEB POWERED PORTAL INFRASTRUCTURE
SEMANTIC WEB POWERED PORTAL INFRASTRUCTURE YING DING 1 Digital Enterprise Research Institute Leopold-Franzens Universität Innsbruck Austria DIETER FENSEL Digital Enterprise Research Institute National
More informationEnterprise Architect. User Guide Series. Domain Models
Enterprise Architect User Guide Series Domain Models What support for modeling domains? Sparx Systems Enterprise Architect supports a range of modeling languages, technologies and methods that can be used
More informationRestricted Use Case Modeling Approach
RUCM TAO YUE tao@simula.no Simula Research Laboratory Restricted Use Case Modeling Approach User Manual April 2010 Preface Use case modeling is commonly applied to document requirements. Restricted Use
More informationModeling Standard 300D&C
Modeling Standard 300D&C Table of contents Introduction Assumptions License The Base Model Identification and description of the elements of the model The Requirement Model Types of relationships between
More informationIntroduction to Software Engineering. 5. Modeling Objects and Classes
Introduction to Software Engineering 5. Modeling Objects and Classes Roadmap > UML Overview > Classes, attributes and operations > UML Lines and Arrows > Parameterized Classes, Interfaces and Utilities
More information3. Agent-Oriented Methodologies Part 2: The PROMETHEUS methodology.
Multiagent Syste ems Design (MASD D) Part 2: The PROMETHEUS methodology. https://kemlg.upc.edu Javier Vázquez-Salceda MASD Methodological Extensions to Object-Oriented Approaches A means for agent technologies
More informationResearch Paper on Implementation of OCL Constraints in JAVA
ISSN No. 0976-5697 Volume 8, No. 5, May June 2017 International Journal of Advanced Research in Computer Science RESEARCH PAPER Available Online at www.ijarcs.info Research Paper on Implementation of OCL
More informationModeling Systems Using Design Patterns
Modeling Systems Using Design Patterns Jaroslav JAKUBÍK Slovak University of Technology Faculty of Informatics and Information Technologies Ilkovičova 3, 842 16 Bratislava, Slovakia jakubik@fiit.stuba.sk
More informationiserver Free Archimate ArchiMate 1.0 Template Stencil: Getting from Started Orbus Guide Software Thanks for Downloading the Free ArchiMate Template! Orbus Software have created a set of Visio ArchiMate
More informationChapter 4 Requirements Elicitation
Object-Oriented Software Engineering Using UML, Patterns, and Java Chapter 4 Requirements Elicitation Outline Today: Motivation: Software Lifecycle Requirements elicitation challenges Problem statement
More informationA UML-based Process Meta-Model Integrating a Rigorous Process Patterns Definition
A UML-based Process Meta-Model Integrating a Rigorous Process Patterns Definition Hanh Nhi Tran, Bernard Coulette, Bich Thuy Dong 2 University of Toulouse 2 -GRIMM 5 allées A. Machado F-3058 Toulouse,
More information