AADL Requirements Annex Review
|
|
- Morgan Dennis
- 5 years ago
- Views:
Transcription
1 Dominique Blouin Lab-STICC Université de Bretagne-Occidentale Université de Bretagne-Sud Bretagne, France 1 AADL Standards Meeting, April 23 th, 2013
2 Agenda Comments from Annex Document Review Motivations for a Requirements Annex Requirements Annex Overview Remaining Work Future Plans 2
3 Agenda Comments from Annex Document Review Motivations for a Requirements Annex Requirements Annex Overview Remaining Work Future Plans 3
4 Motivations for a Requirements Annex RDAL RDAL + AADL + SAVI Benefits of early fault discovering (Feiler 2009) 4
5 Why a New RE Language? Existing languages: URN (ITU Z.151) GRL UCM 5
6 Problems with Existing RE Languages Include constructs for both the problem (requirements) and solution (design) domains. Implies duplication of information. Model transformation used to derive an initial AADL design. Need for model synchronization. Difficult to trace requirements to AADL design elements. Not always adapted to support RE bests practices of embedded systems development. 6
7 FAA REMH David Lempia and Steven Miller Rockwell Collins Set of best practices to enable successful management of requirements. Based on a study of the literature and industry practices. David Lempia and Steven Miller Rockwell Collins Methods and tools from research not adopted because of the difficulty to change existing practices and tools. REMH proposes a set of 11 practices that can be adopted incrementally. 7
8 Objectives for Requirements Annex Separate the concerns: Problem (requirements) / solution (design) Easy to use with AADL (and potentially other ADLs). Emphasis on semantics: Analysis Partially automated validation of requirements specifications. Automated verification of formally expressed requirements. Documentation generation Requirements spec. generated from the model (not the reverse). Fitted for the embedded systems domain. 8
9 Objectives for Requirements Annex Extensible with respect to: Expression languages (natural, OCL, Lute, PSL, BLESS, etc.). Traceability (traceability links to models from other languages for different concerns can be defined) Incorporate good ideas from other languages and methods: SysML KAOS URN FAA Requirements Engineering Management Handbook Do not restrict the use of the language to a specific process. 9
10 Agenda Comments from Annex Document Review Motivations for a Requirements Annex Requirements Annex Overview Remaining Work Future Plans 10
11 How the Annex is Presented Introduce the concepts with class diagrams. Show usage examples with parts of the FAA isolette thermostat example modeled with RDAL and AADL. 11
12 Class Diagram Conventions Reference (blue) Inheritance (black) Language Color Legend 12
13 FAA Isolette Thermostat Example Two functions introduced for safety reasons: Maintain constant current temperature. Monitor current temperature. 13
14 Modeling of the Example RDAL Meta- Model AADL Meta- Model <<conforms to>> URN Meta- Model <<conforms to>> <<conforms to>> <<conforms to>> <<traced to>> RDAL RDAL Model RDAL Model Model URN URN Model URN Model Model <<traced to>> AADL AADL Model AADL Model Model Settings Model Settings Meta-Model 15
15 Core RDAL Language 16
16 Contractual Element Realizations 17
17 Organizational Elements 18
18 Refinement Elements Inspired from KAOS refinement mechanism. Used to model: Decomposition into sub-requirements providing more details. Design alternatives. Example KAOS diagram. 19
19 Refinement Elements A section was added to SAE document on refinements. Additional weight property on decomposition. Reviewed so that refined elements are independent of their refining elements. Allows sending a high level requirements specification without the need to send all its refinements. 20
20 Allocation of System Requirements to Subsystems 21
21 System Overview Definition The system interacts with its environment through variables (monitored / controlled). System requirements define a precise relationship between monitored and controlled variables for all contexts of operation of the system. System Boundary == Environment Variables. Getting the system boundary correct is 90 % of the problem! Stuart Faulk to Steven Miller 22
22 System Overview Definition 23
23 System Overview Definition Combined RDAL and AADL to formalize the system overview. Profiled AADL for defining the system overview. RDAL to represent system overview concepts and trace AADL elements. 24
24 System Context Definition Normal context of operation. 25
25 AADL System Overview Specification 26
26 Requirements Capture 27
27 Graphical Tool Support Graphical and Textual (to be defined) syntaxes. 28
28 Requirements Expressions Libraries Choice of constraint languages Expression Extensible Choice of Constraint Languages 29
29 Scope of Expressions The expressions attached to requirements, assumptions and goals are evaluated in the context of the associated design elements. A scope must be provided for constructs such as: Lute: predefined sets such as Processor_Set, etc. OCL: allinstance The scope is taken as the elements contained in the design elements of the requirements specification. Includes elements from the with clauses. 30
30 Example Pacemaker Scope 31
31 Traceability to Use Case Steps 32
32 Environmental Assumptions Environmental assumptions constrain the entities of the environment. Having a formalized system boundary allow to distinguish between assumptions and requirements. Allows checking that an assumption on an entity has a corresponding requirement in the requirements specification of the entity. 33
33 Environmental Assumptions 34
34 Image Requirements in Isolette Specification 35
35 Goal Capture The definition of requirements and goals greatly varies in languages. Often there is a distinction between: Functional Non-functional. RDAL: Requirements: Verifiable (binary). Goals: Satisfiable to a level (quantitative). 36
36 Goals Capture 37
37 Like requirements, goals can be: Refined. Bridged to design elements. Goal Capture Expressed formally (returning a value of the satisfaction level). Linked to non-functional properties and sensitivity points for design optimization. Ongoing work with Etienne Borde, Greg Loniewsky and Emilio Insfran. 38
38 Traceability to Use Cases 39
39 Bridge to Design Elements 40
40 Hard / Soft Bridges to Design Elements A soft bridge provides a view of the design for assigning requirements and goals to design elements. The bridged elements must be part of the scope of the specification. Hard (Direct Reference) Soft (Query Expression) 41
41 Constraints Languages ML Declare constraints languages in an opaque manner. Extensible (can easily add new languages). Used by other tools (Open-PEOPLE quantitative analysis framework). 42
42 Settings Declares typing rules for RDAL generic traceability points per target language. Declares user-defined hierarchical categories for various RDAL elements: Requirements, Assumptions, Goals and Verification Activities. 43
43 Revised Settings Meta-Model Traceability Typing Rules Userdefined Categories
44 Semantics (Quality Assurance of Requirements Specification) A requirements specification allows to differentiate an acceptable from a not acceptable system. Acceptable: All requirements of the specification are verified by the system. Not acceptable: At least one requirement of the specification is not verified. Precondition: The requirements specification is itself acceptable. 45
45 Semantics (Quality Assurance of Requirements Specification) Characteristics of a good requirements specification (IEEE Std ) Correct Unambiguous Complete Consistent Ranked for importance and/or stability Verifiable Modifiable Traceable No intent to proof correct requirements specification, but several simple analyses can help finding errors. 46
46 Semantics (Requirements Specification Alone) Correct: Every requirement is one that the software shall meet. RDAL Analysis: Verify that contracts represent a stakeholder need. Every requirement and goal must be linked to a Stakeholder, considering refinements and derivations. Verify that there is rationale for contracts. Every requirement, goal and assumption are linked to a Rationale element. Every rationale is linked to a stakeholder of the contract. 47
47 Semantics (RDAL + AADL Specification) Requirements visibility: Following AADL property visibility mechanism: *From SAE AS5506 AADL Specification 48
48 Semantics (RDAL + AADL Specification) Automated verification of requirements. Automated satisfaction evaluation of goals. Support for goal-driven design optimization. 49
49 Semantics (RDAL + AADL Specifications) Validation of integration of multi-team (subcontractors) design models: Verification of environmental assumptions on the global system overview model (thanks to formal identification of the system boundary). Verification of image requirements and assumptions. 50
50 Agenda Comments from Annex Document Review Motivations for a Requirements Annex Requirements Annex Overview Remaining Work Future Plans 51
51 Remaining Work on Language Define a textual syntax. Would KSU be working on it? Complete the definition of the graphical syntax. Add means to define user properties (like in ReqIF). Rename Contractual Element to Agreed Element? Specialize Requirement class into functional / non-functional like for goals?
52 Remaining Work on Language Are system function goals really needed? Used to model preliminary system goals of the isolette example. Could be represented as high level requirements expressed in natural language. Or allow refining system function goals into requirements? Review traceability mechanism between requirements and design? Right now, traceability goes from requirements models to design models. Usually it is the reverse so that several designs can tentatively meet the same requirements specification. However, alternatives are represented in the requirements specification through refinements. Besides, we need a scope for evaluating the requirements expressions. Currently provided by the design elements of the specification.
53 Remaining Work on RDALTE1 Fix the reference to AADL models elements problem. OSATE instance model has the same problem Study this problem and RDAL traceability issues in the context of Global Model Management (GMM). GMM introduced in the next presentation.
54 Remaining Work on RDALTE2 Implement textual syntax (Xtext based). Update the graphical editor for latest RDAL. Implement meta-model constraints. Implement analyses. Quality assurance of requirements specification. Implement requirements visibility mechanism. Improve implementation of automated verification of requirements. Adapt advanced editor view to define requirement condition.
55 Remaining Work on RDALTE2 Experiment with a behavioral constraint language. Integration of BLESS? System overview editor: Option 1: Finish developing the Graphiti editor. Option 2: Implement a profiling mechanism in the Adele editor. Option 2 could allow implementing other editors such as data flow diagrams to represent system functions with AADL.
56 Agenda Comments from Annex Document Review Motivations for a Requirements Annex Requirements Annex Overview Remaining Work Future Plans 57
57 Future Plans The funding for this work (Open-PEOPLE project) ended in December I will not have much time to work on the project until the end of the Adele joint project. Expected to finish end of October How could we continue this project in the longer term? Any ideas for funding?
Update on AADL Requirements Annex
Open-PEOPLE Open Power and Energy Optimization PLatform and Estimator Update on AADL Requirements Annex Dominique BLOUIN* *Lab-STICC, Université de Bretagne Sud, Lorient, FRANCE AADL Standards Meeting,
More informationComplexity-Reducing Design Patterns for Cyber-Physical Systems. DARPA META Project. AADL Standards Meeting January 2011 Steven P.
Complexity-Reducing Design Patterns for Cyber-Physical Systems DARPA META Project AADL Standards Meeting 24-27 January 2011 Steven P. Miller Delivered to the Government in Accordance with Contract FA8650-10-C-7081
More informationAn Information Model for High-Integrity Real Time Systems
An Information Model for High-Integrity Real Time Systems Alek Radjenovic, Richard Paige, Philippa Conmy, Malcolm Wallace, and John McDermid High-Integrity Systems Group, Department of Computer Science,
More informationQuery Language for AADLv2, Jérôme Hugues, ISAE Serban Gheorghe, Edgewater
Query Language for AADLv2, Jérôme Hugues, ISAE Serban Gheorghe, Edgewater Outline 1. Discussion from previous meetings 2. Defining elements for a DSL, inputs from the meta model 3. Defining elements for
More informationModelling & Simulation of Complex Socio-Cyber- Physical Systems and Large Scale Systems of Systems
Modelling & Simulation of Complex Socio-Cyber- Physical Systems and Large Scale Systems of Systems Along their Lifetime, a System Owner Standpoint CSDM 2016 December 13-14, 2016 N. Thuy - EDF R&D General
More informationSAE Architecture Analysis and Design Language. AS-2C AADL Subcommittee Meeting Feb 3-6, 2014 Toulouse, France
SAE Architecture Analysis and Design Language AS-2C AADL Subcommittee Meeting Feb 3-6, 2014 Toulouse, France Upcoming SAE/AADL Meetings Next Meeting: September 2013 Montreal Spring 2014 Santa Barbara,
More informationBUILDING GOOD-QUALITY FUNCTIONAL SPECIFICATION MODEL
BUILDING GOOD-QUALITY FUNCTIONAL SPECIFICATION MODEL A few words on Samares Engineering Research and Consultancy on Systems Engineering Requirement engineering Model-Based Systems Engineering Co-simulation
More informationTest and Evaluation of Autonomous Systems in a Model Based Engineering Context
Test and Evaluation of Autonomous Systems in a Model Based Engineering Context Raytheon Michael Nolan USAF AFRL Aaron Fifarek Jonathan Hoffman 3 March 2016 Copyright 2016. Unpublished Work. Raytheon Company.
More informationCIS 890: High-Assurance Systems
CIS 890: High-Assurance Systems Hazard Analysis Lecture: Error Modeling Annex Version 2 - Introduction Copyright 2016, John Hatcliff, Hariharan Thiagarajan. The syllabus and all lectures for this course
More informationMike Whalen Program Director, UMSEC University of Minnesota
Formal Analysis for Communicating Medical Devices Mike Whalen Program Director, UMSEC University of Minnesota Research Topics Multi-Domain Analysis of System Architecture Models Compositional Assume-Guarantee
More informationSAE Architecture Analysis and Design Language. AS-2C AADL Subcommittee Meeting Sept 29-Oct 2, 2014 Valencia, Spain
SAE Architecture Analysis and Design Language AS-2C AADL Subcommittee Meeting Sept 29-Oct 2, 2014 Valencia, Spain Upcoming SAE/AADL Meetings Fall 2014 - Valencia, Workshop is the Monday, Sept 29 th, Meeting
More informationLecture 5: Requirements Specifications
Lecture 5: Requirements Specifications Why we need to write specifications Purpose and audience Choosing an appropriate size and formality Desiderata for Specifications Properties of good specifications
More informationAADL Graphical Editor Design
AADL Graphical Editor Design Peter Feiler Software Engineering Institute phf@sei.cmu.edu Introduction An AADL specification is a set of component type and implementation declarations. They are organized
More informationIntroduction to AADL analysis and modeling with FACE Units of Conformance
Introduction to AADL analysis and modeling with FACE Units of Conformance AMRDEC Aviation Applied Technology Directorate Contract Number W911W6-17- D-0003 Delivery Order 3 This material is based upon work
More informationPresented by Greg Pollari (Rockwell Collins) and Nigel Shaw (Eurostep)
System Architecture Virtual Integration (SAVI) Project : Intermodel Error Checking and Consistency Review and Demonstration An Aerospace Vehicle Systems Institute Project (AVSI) Presented by Greg Pollari
More informationSAE Architecture Analysis and Design Language. AS-2C AADL Subcommittee Meeting Feb 2-5, 2015 San Diego, USA
SAE Architecture Analysis and Design Language AS-2C AADL Subcommittee Meeting Feb 2-5, 2015 San Diego, USA Upcoming SAE/AADL Meetings Fall 2014 - Valencia, Workshop is the Monday, Sept 29 th Winter 2015
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 informationAutomatic Generation of the AADL ALISA Verification Plan with ATL
Available online at www.ijpe-online.com Vol. 13, No. 7, November 2017, pp. 1111-1122 DOI: 10.23940/ijpe.17.07.p14.11111122 Automatic Generation of the AADL ALISA Verification Plan with ATL Tianyi Wu a,
More informationSoftware Requirements Specification. <Project> for. Version 1.0 approved. Prepared by <author(s)> <Organization> <Date created>
Software Requirements Specification for Version 1.0 approved Prepared by Software Requirements Specification for Page 2 Table of Contents Revision
More informationRecommended Practice for Software Requirements Specifications (IEEE)
Recommended Practice for Software Requirements Specifications (IEEE) Author: John Doe Revision: 29/Dec/11 Abstract: The content and qualities of a good software requirements specification (SRS) are described
More informationModeling Issues Modeling Enterprises. Modeling
Modeling Issues Modeling Enterprises SE502: Software Requirements Engineering Modeling Modeling can guide elicitation: It can help you figure out what questions to ask It can help to surface hidden requirements
More informationSynchronization of Models of Rich Languages with Triple Graph Grammars: an Experience Report *
Synchronization of Models of Rich Languages with Triple Graph Grammars: an Experience Report * Dominique Blouin 1, Alain Plantec 2, Pierre Dissaux 3, Frank Singhoff 2 and Jean- Philippe Diguet 1 1 Lab-STICC,
More informationFundamentals to Creating Architectures using ISO/IEC/IEEE Standards
Fundamentals to Creating Architectures using ISO/IEC/IEEE Standards What to Architect? How to Architect? IEEE Goals and Objectives Chartered by IEEE Software Engineering Standards Committee to: Define
More informationTools for Formally Reasoning about Systems. June Prepared by Lucas Wagner
Tools for Formally Reasoning about Systems June 9 2015 Prepared by Lucas Wagner 2015 Rockwell 2015 Collins. Rockwell All Collins. rights reserved. All rights reserved. Complex systems are getting more
More informationRAMSES. Refinement of AADL Models for the Synthesis of Embedded Systems. Etienne Borde
Refinement of AADL Models for the Synthesis of Embedded Systems Etienne Borde etienne.borde@telecom-paristech.fr AADL: Architecture Analysis and Design Language We use AADL to model SCES architectures:
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 informationInvestigation of System Timing Concerns in Embedded Systems: Tool-based Analysis of AADL Models
Investigation of System Timing Concerns in Embedded Systems: Tool-based Analysis of AADL Models Peter Feiler Software Engineering Institute phf@sei.cmu.edu 412-268-7790 2004 by Carnegie Mellon University
More informationThe Analysis and Proposed Modifications to ISO/IEC Software Engineering Software Quality Requirements and Evaluation Quality Requirements
Journal of Software Engineering and Applications, 2016, 9, 112-127 Published Online April 2016 in SciRes. http://www.scirp.org/journal/jsea http://dx.doi.org/10.4236/jsea.2016.94010 The Analysis and Proposed
More informationChapter 4 Objectives
Chapter 4 Objectives Eliciting requirements from the customers Modeling requirements Reviewing requirements to ensure their quality Documenting requirements for use by the design and test teams 4.1 The
More informationNumber: DI-SESS Approval Date:
DATA ITEM DESCRIPTION Title: SOFTWARE PRODUCT DESIGN (SPD) Number: Approval Date: 20160322 AMSC Number: N9644 Limitation: DTIC Applicable: GIDEP Applicable: Preparing Activity: AS Project Number: SESS-2016-006
More informationFlight Systems are Cyber-Physical Systems
Flight Systems are Cyber-Physical Systems Dr. Christopher Landauer Software Systems Analysis Department The Aerospace Corporation Computer Science Division / Software Engineering Subdivision 08 November
More informationEvidence-based Development coupling structured argumentation with requirements development.
Evidence-based Development coupling structured argumentation with requirements development Jeremy.Dick@integrate.biz integrate 2012 based on paper Paper: EVIDENCE-BASED DEVELOPMENT COUPLING STRUCTURED
More informationSysML Past, Present, and Future. J.D. Baker Sparx Systems Ambassador Sparx Systems Pty Ltd
SysML Past, Present, and Future J.D. Baker Sparx Systems Ambassador Sparx Systems Pty Ltd A Specification Produced by the OMG Process SysML 1.0 SysML 1.1 Etc. RFI optional Issued by Task Forces RFI responses
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 informationRequirements Validation and Negotiation
REQUIREMENTS ENGINEERING LECTURE 2017/2018 Joerg Doerr Requirements Validation and Negotiation AGENDA Fundamentals of Requirements Validation Fundamentals of Requirements Negotiation Quality Aspects of
More informationPlatform modeling and allocation
Platform modeling and allocation Systems Engineering BSc Course Budapest University of Technology and Economics Department of Measurement and Information Systems Traceability Platform-based systems design
More informationSystem Architecture Virtual Integration (SAVI) Presentation to PDT Europe 2016
System Architecture Virtual Integration (SAVI) to PDT Europe 2016 Greg Pollari, Rockwell Collins Nigel Shaw, Eurostep Limited Agenda SAVI The problem SAVI The constium Two examples Conclusions Looking
More informationSoftware architecture in ASPICE and Even-André Karlsson
Software architecture in ASPICE and 26262 Even-André Karlsson Agenda Overall comparison (3 min) Why is the architecture documentation difficult? (2 min) ASPICE requirements (8 min) 26262 requirements (12
More informationDominique Blouin Etienne Borde
Dominique Blouin Etienne Borde dominique.blouin@telecom-paristech.fr etienne.borde@telecom-paristech.fr Institut Mines-Télécom Content Domain specific Languages in a Nutshell Overview of Eclipse Modeling
More informationREQUIREMENTS ENGINEERING LECTURE 2017/2018. Dr. Jörg Dörr. Conceptual Modelling. Fraunhofer IESE
REQUIREMENTS ENGINEERING LECTURE 2017/2018 Dr. Jörg Dörr Conceptual Modelling AGENDA Analysis & Specification with Conceptual Models 2 Requirements Specification ANALYSIS & SPECIFICATION WITH CONCEPTUAL
More informationThe software lifecycle and its documents
The software lifecycle and its documents Supplementary material for Software Architecture course B. Meyer, May 2006 Lifecycle models Origin: Royce, 1970, Waterfall model Scope: describe the set of processes
More informationWhat is Software Architecture
What is Software Architecture Is this diagram an architecture? (ATM Software) Control Card Interface Cash Dispenser Keyboard Interface What are ambiguities in the previous diagram? Nature of the elements
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 informationTO: FROM: DATE: SUBJECT: Revisions General 2.1 The Mismatch does
TO: FROM: T10 Membership Paul A Suhler, Quantum Corporation David Black, EMC DATE: 22 October 2008 SUBJECT: T10/08-46r1, SPC-4: Correction to IKEv2-SCSI Certificate Request Payload 1 Revisions 0 Initial
More informationModel-Driven Engineering Approach for Simulating Virtual Devices in the OSATE 2 Environment
Model-Driven Engineering Approach for Simulating Virtual Devices in the OSATE 2 Environment Fáber D. Giraldo and Mónica M. Villegas Abstract Simulating devices while developing software for embedded systems
More informationSE 1: Software Requirements Specification and Analysis
SE 1: Software Requirements Specification and Analysis Lecture 4: Basic Notations Nancy Day, Davor Svetinović http://www.student.cs.uwaterloo.ca/ cs445/winter2006 uw.cs.cs445 U Waterloo SE1 (Winter 2006)
More informationDelimited. Interfaced. Readable. Modifiable. Verifiable. Prioritized* Endorsed
15 quality goals for requirements Justified Correct Complete Consistent Unambiguous Feasible Abstract Traceable Delimited Interfaced Readable Modifiable Verifiable Prioritized* Endorsed Marked attributes
More informationSCADE. SCADE Architect System Requirements Analysis EMBEDDED SOFTWARE
EMBEDDED SOFTWARE SCADE SCADE Architect 19.2 SCADE Architect is part of the ANSYS Embedded Software family of products and solutions, which gives you a design environment for systems with high dependability
More informationSAE Architecture Analysis and Design Language. AS-2C ADL Subcommittee Meeting June 6-9, 2011 Paris, France
SAE Architecture Analysis and Design Language AS-2C ADL Subcommittee Meeting June 6-9, 2011 Paris, France Election of AS2 Chair Greg Newman elected Replaces Mike Pakucko Covers AS2C (AADL) AS2D (time triggered)
More informationCertification of Model Transformations
Certification of Transformations Dániel Varró 1st Workshop on the Analysis of Transformations (AMT 2012) Sharing some challenges of the CERTIMOT project Budapest University of Technology and Economics
More informationSummary of Changes in ISO 9001:2008
s in ISO 9001:2008 Clause 0.1 Introduction General Added the phrase its organizational environment, changes in that environment, or risks associated with that environment, to the first paragraph Created
More informationSoftware Verification and Validation (VIMMD052) Introduction. Istvan Majzik Budapest University of Technology and Economics
Software Verification and Validation (VIMMD052) Introduction Istvan Majzik majzik@mit.bme.hu Budapest University of Technology and Economics Dept. of Measurement and Information s Budapest University of
More informationRaising the Level of Development: Models, Architectures, Programs
IBM Software Group Raising the Level of Development: Models, Architectures, Programs Dr. James Rumbaugh IBM Distinguished Engineer Why Is Software Difficult? Business domain and computer have different
More informationAnalysis and Design Language (AADL) for Quantitative System Reliability and Availability Modeling
Application of the Architectural Analysis and Design Language (AADL) for Quantitative System Reliability and Availability Modeling Chris Vogl, Myron Hecht, and Alex Lam Presented to System and Software
More informationOn the link between Architectural Description Models and Modelica Analyses Models
On the link between Architectural Description Models and Modelica Analyses Models Damien Chapon Guillaume Bouchez Airbus France 316 Route de Bayonne 31060 Toulouse {damien.chapon,guillaume.bouchez}@airbus.com
More informationETSI TS V6.1.0 ( )
TS 102 224 V6.1.0 (2004-12) Technical Specification Smart cards; Security mechanisms for UICC based Applications - Functional requirements (Release 6) 2 TS 102 224 V6.1.0 (2004-12) Reference RTS/SCP-R0282r1
More informationFuture Directions for SysML v2 INCOSE IW MBSE Workshop January 28, 2017
Future Directions for SysML v2 INCOSE IW MBSE Workshop January 28, 2017 Sanford Friedenthal safriedenthal@gmail.com 1/30/2017 Agenda Background System Modeling Environment (SME) SysML v2 Requirements Approach
More informationChapter 6 Architectural Design
Chapter 6 Architectural Design Chapter 6 Architectural Design Slide 1 Topics covered The WHAT and WHY of architectural design Architectural design decisions Architectural views/perspectives Architectural
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 information5/9/2014. Recall the design process. Lecture 1. Establishing the overall structureof a software system. Topics covered
Topics covered Chapter 6 Architectural Design Architectural design decisions Architectural views Architectural patterns Application architectures Lecture 1 1 2 Software architecture The design process
More informationIncQuery for MagicDraw Quick Start Guide
IncQuery for MagicDraw Quick Start Guide v1.6.2, June 17, 2018 Table of Contents 1. Installation Guide............................................................. 1 2. Custom Query Evaluation......................................................
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 informationArchitectural Blueprint
IMPORTANT NOTICE TO STUDENTS These slides are NOT to be used as a replacement for student notes. These slides are sometimes vague and incomplete on purpose to spark a class discussion Architectural Blueprint
More informationNOTES ON OBJECT-ORIENTED MODELING AND DESIGN
NOTES ON OBJECT-ORIENTED MODELING AND DESIGN Stephen W. Clyde Brigham Young University Provo, UT 86402 Abstract: A review of the Object Modeling Technique (OMT) is presented. OMT is an object-oriented
More informationModeling Requirements
Modeling Requirements Critical Embedded Systems Dr. Balázs Polgár Prepared by Budapest University of Technology and Economics Faculty of Electrical Engineering and Informatics Dept. of Measurement and
More informationSESE Tour 2018 Toulouse May 22
SESE Tour 2018 Toulouse May 22 Optimal function modelling with SysML Authors: Regis Casteran, Xavier Dorel, Raphaël Faudou, David Gouyon, Frederic Risy Presented by Xavier Dorel (Schneider-Electric) And
More informationSoftware Quality Starts with the Modelling of Goal-Oriented Requirements
Software Quality Starts with the Modelling of Goal-Oriented Requirements Emmanuelle Delor, Robert Darimont CEDITI Avenue Georges Lemaître, 21 B-6041 Charleroi Belgium Phone : +32 (0) 71 25 94 04 Fax :
More informationArchitecture Modeling in embedded systems
Architecture Modeling in embedded systems Ákos Horváth Model Driven Software Development Lecture 11 Budapest University of Technology and Economics Department of Measurement and Information Systems Abstract
More informationMinsoo Ryu. College of Information and Communications Hanyang University.
Software Reuse and Component-Based Software Engineering Minsoo Ryu College of Information and Communications Hanyang University msryu@hanyang.ac.kr Software Reuse Contents Components CBSE (Component-Based
More informationNatural Language Requirements
Natural Language Requirements Software Verification and Validation Laboratory Requirement Elaboration Heuristic Domain Model» Requirement Relationship Natural Language is elaborated via Requirement application
More informationSoftware Reuse and Component-Based Software Engineering
Software Reuse and Component-Based Software Engineering Minsoo Ryu Hanyang University msryu@hanyang.ac.kr Contents Software Reuse Components CBSE (Component-Based Software Engineering) Domain Engineering
More informationCIS 890: Safety Critical Systems
CIS 890: Safety Critical Systems Lecture: Requirements Introduction Copyright 2011, John Hatcliff. The syllabus and all lectures for this course are copyrighted materials and may not be used in other course
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 informationModel-based System Engineering for Fault Tree Generation and Analysis
Model-based System Engineering for Fault Tree Generation and Analysis Nataliya Yakymets, Hadi Jaber, Agnes Lanusse CEA Saclay Nano-INNOV, Institut CARNOT CEA LIST, DILS, 91 191 Gif sur Yvette CEDEX, Saclay,
More informationSoftware Architectures
Software Architectures Richard N. Taylor Information and Computer Science University of California, Irvine Irvine, California 92697-3425 taylor@ics.uci.edu http://www.ics.uci.edu/~taylor +1-949-824-6429
More informationDependability Modeling Based on AADL Description (Architecture Analysis and Design Language)
Dependability Modeling Based on AADL Description (Architecture Analysis and Design Language) Ana Rugina, Karama Kanoun and Mohamed Kaâniche {rugina, kanoun, kaaniche}@laas.fr European Integrated Project
More informationCC and CEM addenda. Modular PP. March Version 1.0 CCDB
CC and CEM addenda Modular PP March 2014 Version 1.0 CCDB-2014-03-001 Foreword This is addenda to the the Common Criteria version 3 and the associated Common Evaluation Methodology for Information Technology
More informationSofware Requirements Engineeing
Sofware Requirements Engineeing Three main tasks in RE: 1 Elicit find out what the customers really want. Identify stakeholders, their goals and viewpoints. 2 Document write it down (Requirements Specification).
More informationHITSP Standards Harmonization Process -- A report on progress
Document Number: HITSP 06 N 75 Date: May 4, 2006 HITSP Standards Harmonization Process -- A report on progress Arlington, VA May 4 th, 2006 0 What Was Done Reviewed obligations from federal contract Observed
More informationHarmonization of usability measurements in ISO9126 software engineering standards
Harmonization of usability measurements in ISO9126 software engineering standards Laila Cheikhi, Alain Abran and Witold Suryn École de Technologie Supérieure, 1100 Notre-Dame Ouest, Montréal, Canada laila.cheikhi.1@ens.etsmtl.ca,
More informationFramework for building information modelling (BIM) guidance
TECHNICAL SPECIFICATION ISO/TS 12911 First edition 2012-09-01 Framework for building information modelling (BIM) guidance Cadre pour les directives de modélisation des données du bâtiment Reference number
More information8/22/2003. Proposal for VPI model PSL assertion extensions
8/22/2003 Proposal for VPI model PSL assertion extensions Cadence Design Systems, Inc. 8/22/2003 This proposal has been prepared by Cadence Design Systems, Inc. for consideration by the IEEE 1364 working
More informationComponent Design. Systems Engineering BSc Course. Budapest University of Technology and Economics Department of Measurement and Information Systems
Component Design Systems Engineering BSc Course Budapest University of Technology and Economics Department of Measurement and Information Systems Traceability Platform-based systems design Verification
More informationModel Verification: Return of experience
Model Verification: Return of experience P. Dissaux 1, P. Farail 2 1: Ellidiss Technologies, 24, quai de la douane, 29200 Brest, France 2: Airbus Operations SAS, 316 route de Bayonne, 31060 Toulouse, France
More informationISO/IEC/ IEEE INTERNATIONAL STANDARD. Systems and software engineering Architecture description
INTERNATIONAL STANDARD ISO/IEC/ IEEE 42010 First edition 2011-12-01 Systems and software engineering Architecture description Ingénierie des systèmes et des logiciels Description de l'architecture Reference
More informationArchitectural Design. Topics covered. Architectural Design. Software architecture. Recall the design process
Architectural Design Objectives To introduce architectural design and to discuss its importance To explain the architectural design decisions that have to be made To introduce three complementary architectural
More informationOCL Support in MOF Repositories
OCL Support in MOF Repositories Joachim Hoessler, Michael Soden Department of Computer Science Technical University Berlin hoessler@cs.tu-berlin.de, soden@cs.tu-berlin.de Abstract From metamodels that
More informationEnterprise Architect Training Courses
On-site training from as little as 135 per delegate per day! Enterprise Architect Training Courses Tassc trainers are expert practitioners in Enterprise Architect with over 10 years experience in object
More informationQuality Software Requirements By J. Chris Gibson
Quality Software Requirements By J. Chris Gibson The information contained within this document has been gathered from a variety of sources and practices observed by the development team at Protera Software
More informationPresentation of the AADL: Architecture Analysis and Design Language
Presentation of the AADL: Architecture Analysis and Design Language Outline 1. AADL a quick overview 2. AADL key modeling constructs 1. AADL components 2. Properties 3. Component connection 3. AADL: tool
More informationModeling Requirements, Architectures, Behaviour...
Modeling Requirements, Architectures, Behaviour... The System Modeling Language (SysML) and the SYSMOD modeling approach Budapest University of Technology and Economics Department of Measurement and Information
More informationETSI TR V1.1.1 ( )
TR 101 303 V1.1.1 (2001-06) Technical Report Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON); Service and Network Management Framework; Overview and Introduction 2 TR 101
More informationSoftware Architecture in Action. Flavio Oquendo, Jair C Leite, Thais Batista
Software Architecture in Action Flavio Oquendo, Jair C Leite, Thais Batista Motivation 2 n In this book you can learn the main software architecture concepts and practices. n We use an architecture description
More informationUML Profile for MARTE: Time Model and CCSL
UML Profile for MARTE: Time Model and CCSL Frédéric Mallet 1 Université Nice Sophia Antipolis, Aoste team INRIA/I3S, Sophia Antipolis, France Frederic.Mallet@unice.fr Abstract. This 90 minutes tutorial
More informationMonday Jan 30. Tuesday Jan 31. AADL Standards Meeting Jan 30 Feb 1, 2012 Toulouse, France with ERTS Conference N7 INPT University de Toulouse
AADL Standards Meeting Jan 30 Feb 1, 2012 Toulouse, France with ERTS Conference N7 INPT University de Toulouse http://maps.google.com/maps?q=rue+charles+camichel,+31000+toulouse,+france&z=16 Teleconference
More informationDeriving safety requirements according to ISO for complex systems: How to avoid getting lost?
Deriving safety requirements according to ISO 26262 for complex systems: How to avoid getting lost? Thomas Frese, Ford-Werke GmbH, Köln; Denis Hatebur, ITESYS GmbH, Dortmund; Hans-Jörg Aryus, SystemA GmbH,
More informationISO/IEC INTERNATIONAL STANDARD. Information technology Multimedia framework (MPEG-21) Part 21: Media Contract Ontology
INTERNATIONAL STANDARD ISO/IEC 21000-21 First edition 2013-07-01 Information technology Multimedia framework (MPEG-21) Part 21: Media Contract Ontology Technologies de l'information Cadre multimédia (MPEG-21)
More informationINTERNATIONAL TELECOMMUNICATION UNION
INTERNATIONAL TELECOMMUNICATION UNION )454 ) TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU ).4%'2!4%$ 3%26)#%3 $)')4!,.%47/2+ )3$. '%.%2!, 3425#452% -%4(/$ &/2 4(% #(!2!#4%2):!4)/. /& 4%,%#/--5.)#!4)/.
More informationIllustrating the AADL Error Modeling Annex (v. 2) Using a Simple Safety-Critical Medical Device
Illustrating the AADL Error Modeling Annex (v. 2) Using a Simple Safety-Critical Medical Device Brian Larson, John Hatcliff, Kim Fowler Kansas State University {brl,hatcliff,kimrfowler}@ksu.edu Julien
More informationOscar Slotosch, Validas AG. Proposal for a Roadmap towards Development of Qualifyable Eclipse Tools
Oscar Slotosch, Proposal for a Roadmap towards Development of Qualifyable Eclipse Tools, 2012 Seite 1 Content Roadmap Requirements for Tool Qualification (Standards) Proposals for Goals for Eclipse Proposals
More information