Product Line Engineering Lecture PL Architectures I
|
|
- Everett Kelly
- 6 years ago
- Views:
Transcription
1 Product Line Engineering Lecture PL Architectures I Dr. Martin Becker martin.becker@iese.fraunhofer.de 0
2 Schedule - Lectures 1
3 Schedule - Exercises 2
4 Product Line Scoping --- Requirements Engineering --- How to identify, analyze, model, and instantiate common and variable requirements?
5 RE Phases The RE Activities can be divided into five phases, which are more or less standard for the requirements process: Requirements elicitation Requirements analysis Requirements specification/documentation Requirements verification and validation Requirements management 4
6 RE in Product Line Life Cycle Product Requirements Product Application Engineering Evaluation Identification Adaptation Integration Product Requirements A Requirements B Requirements C Scoping Domain Domain Classification Product Line Artifact Base Documentation Coordination Evolution Family Engineering Feedback Product Line Infrastructure 5
7 Usage of RE Documents for variability specification High level Variability (Feature, Decision) Models can be managed in RM-Tools Req. Doc Structuring Traceability Management Use abstract requirements, i.e. Features, to specify variability Vertical traceability can be used to represent constraints 6
8 Text based representation Customisation of textual requirements Environment: Textual requirements with Word template (basic use cases) Specific mapping: Introduction of new text elements <<opt expr1 / text >>. <<alt expr2 / value-1 / text1 / value-2 / text2 >>. expr: logical expressions with decision variables <<mult decision-variable / value-1 / text1 / value-2 / text2...>> <<value decision-variable>> 7
9 Extending UML Many approaches to UML extensions exist Example: Stereotypes Advantage: - stereotypes are supported by most UML-tools Disadvantages: - there is no instantiation/ application engineering support - stereotypes are meant for domain specific extensions Diesel Engine «variability» Engine Car Driver «variability» Start Car Gasoline Engine «uses» «uses» Preheat Engine Start Engine 8
10 Conclusion RE is of key relevance of Single Systems Engineering and PLE Traceability support is helpful esp. for constistency in case of changes RE approach is different in different PLE approaches Variability models can be represented as requirements as well Several mechanisms can be applied to handle variation points on the artefact level 9
11 Product Line Scoping --- Intro --- What is architecture? Who needs it? Single System Architecture vs. Product Line Architecture?
12 The Need for Software Architecture The rise of software architecture has resulted from two trends[1] : Large and complex systems The importance of quality attributes (increasingly time to market is critical) 11
13 Software Complexity Components and interdependencies Just one subsystem out of 20! 12
14 High Quality Quality is NOT only about correctness of functionality Successful software systems have to assure additional properties: Performance Security Availability Maintainability Customizability Flexibility Run-time maintainability or configurability These properties are the so-called Quality Attributes 13
15 Architecture as a Tool Conceptual tool to cope with complexity in Software Engineering needed Architecture Architecture is a set of concepts allowing to control complexity 14
16 Structure or structures of the system, which comprise software elements, the externally visible properties of those elements, and the relationships among them. [Bass et al., Software Architecture in Practice] 15
17 A software system s architecture is the set of principal design decisions made about the system [Taylor et al.] 16
18 Architecture Architecture is the first artefact that translates the problem into in the solution space Provides an overview on the system Enables early discussion and assessment of design alternatives Architecture is an output of the software design process Requirements Engineering Design Implementation Requirements Architecture Code Legend: process work product control flow product flow 17
19 (Single-System) Architecture as an Artifact The architecture of a software system covers the most important design decisions ensures that the quality attributes can be achieved decomposes the system into manageable pieces allows parallelization of work in teams allows communication to and among stakeholders 18
20 Single-System Architecture as a Mediator Business Level Early Decisions Prediction Separate analysis of system characteristics Stakeholderspecific Notations Architecture Late Realization Testing Integrated System Programming Language Technology (-specific)( Level 19
21 Mission of (Single-System) Architecture Reasoning and prediction (predictive) Will the system properties meet the requirements? Vehicle for communication (descriptive) Why are the things as they are? What is the role of a architecture element? Constrain and guide implementation (prescriptive) What is allowed/forbidden? How do the components interface each other? 20
22 Architectural Drivers Business goals Customer organization Developing organization Quality attributes System in use System under development Key functional requirements Unique properties Make system viable Constraints Organizational and technical Cost and time cause complexity might be competing Product Line Context: Customizability is a major driver 21
23 Where Architectural Drivers Originate Stakeholders Customer Management Project Manager End User Product Manager Software Architect Tester Maintainer Developer Developer Management 22
24 Architecture Usage Scenarios Communication Quality prediction Evolution planning Integration planning Reuse decisions Development Development planning Architecture Technical prototyping Change impact analysis Risk detection Test planning 23
25 Types of Architectures Ultra Large Scale System Architectures Ecosystem Architectures Enterprise Architectures System-of-System Architectures System Architectures Software Architectures Product Line Architectures Reference Architectures Platform Architectures Business Architectures 24
26 A Product Line Architecture goes a step further The architecture of a whole family of systems covers the most important common design decisions ensures that the quality attributes can be achieved in all members of the product line decomposes a family of systems into manageable pieces allows parallelization of work in family and application engineering allows communication to and among stakeholders enables customers to see customization possibilities 25
27 Product Line System Architecture as a Mediator Product Line Scope and Requirements Early Decisions Prediction Separate analysis Stakeholderspecific of system characteristics Notations Product Line Architecture Late Realization Testing Integrated System Programming Language Product Line Implementation 26
28 Mission of Product Line Architecture (1/2) Reasoning and prediction (predictive) Will all members of the product line meet the common requirements? Vehicle for communication (descriptive) Why should I reuse this component? What is the reason behind a variation point? What is the role of a reusable architecture element? Constrain and guide implementation (prescriptive) What is allowed/forbidden when I customize for a customer? What different interface implementations and combinations are available 27
29 Mission of Product Line Architecture (2/2) Reasoning and prediction (predictive) How does Product A differ from Product B? What must be changed to get Product C? What are the constraints and dependencies on Component D? Vehicle for communication (descriptive) What are the advantages of Product B? Which team develops when the Variant Feature F? Constrain and guide implementation (prescriptive) What parameters are supported by Component D? How to adapt and integrate the components How to manage the variant components? 28
30 Some major additional stakeholders in a product line Production Manager Configuration Manager Product Line Manager Product Line Adoption Manager Product Line Architect 29
31 Example System Structures Subystem Mechanic Component Electronic Component Software Component 30
32 Architecture as the Key-Enabler for Reuse-in-the-Large Reuse-in-the-Small Reuse-in-the-Large vs Avoid identification, evaluation, integration, coordination efforts Order of magnitude efficiency improvement 31
33 Common confusion Product Line Reference architecture architecture = = Platform architecture explicit variation points and dependencies no final implementation included (only reference) Low level of detail / close to technology e.g. Standard Template Library (although low-level) e.g. Java Platform Enterprise Edition e.g. Microsoft s Platform Architecture for SOA 32
34 What can Differ in a Product Line Architecture? 33
35 Excerpts of Product Line Architectures ID Decision Question VP Resol. S1 Presence Is there a presence sensor? presence {Y,n} S2 Position Is there a position sensor? position {N,y} S3 Actuator Is there an actuator? Actuator, triggeract. {N,y} 34
36 Excerpts of Product Line Architectures [3] Data flow in an automotive system Independent Port Mandatory Component Dependent Port Optional Port Optional Component 35
37 Excerpts of Product Line Architectures [4] 36
38 Excerpts of Product Line Architectures [4] EAST-ADL 37
39 A Product Line Architecture is a description of the structural properties for building a group of related systems, typically the components and their interrelationships. The inherent guidelines about the use of components must capture the means for handling required variability among the systems. [2] 38
40 What offers a product line architecture Enables making considerations about variability early on Product Line Architecture enables encapsulating the variability In so doing the impact of variability across the software is reduced 39
41 Who needs a product line architecture? Application designers: PLAs as common assets customized to yield individual product architectures. customizations happen at predefined VPs. Family designers: PLAs help to make assumptions about the architectural context in which core assets will be reused highlighting the essential product line concepts. suppressing non-essential product line concepts (i.e., product-specific ones). Both: PLAs facilitate sharing assets and provide feedback opportunities. 40
42 References 1. Paul Clements, Software Engineering Institute, Carnegie Mellon University, RiSE summer school P. Clements, L.M. Northrop: Software Product Lines: Practices and Patterns. Addison-Wesley, Mann, S. & Rock, G. (2009), Dealing with Variability in Architecture Descriptions to Support Automotive Product Lines, in 'VaMoS', Universitat Duisburg-Essen, ICB Research Report, Third International Workshop on Variability Modelling of Software-Intensive Systems, Seville, Spain, January 28-30, Proceedings,, pp ATTEST2 project, overview of variability concepts in EAST-ADL2, retrieved from 5. Schmid, K. (2004), A Quantitative Model of the Value of Architecture in Product Line Adoption, in Frank van der Linden, ed.,'software Product-Family Engineering', Springer Berlin / Heidelberg,, pp
43 References 6. Henkel, J. & Diwan, A. (2005), CatchUp!: capturing and replaying refactorings to support API evolution, in 'ICSE '05: Proceedings of the 27th international conference on Software engineering', ACM, New York, NY, USA, pp Raine Kauppinen, Juha Taina and Antti Tevanlinna, Hook and Template Coverage Criteria for Testing, Framework-based Software Product Families, Proceedings of SPLIT 2004 International Workshop on Software Product Line Testing 8. Jan Bosch: Design and Use of Software Architectures. Addison-Wesley, Caroline Nyholm: Product Line Development an Overview. Extended Report for I. Crnkovic and M. Larsson (editors), Building Reliable Component-Based Systems, Artech House, July 2002, ISBN F. van der Linden, K. Schmid, E. Rommes: Software Product Lines in Action. Springer-Verlag,
44 References 11. Nick Rozanski and Eoin Woods: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives. Addison-Wesley Professional, Maarit Harsu : A survey of product-line architectures, Technical report 23, Institute of Software Systems, Tampere University of Technology, D. Perry,. E Generic Architecture Descriptions for Product Lines. In Proceedings of the Second international ESPRIT ARES Workshop on Development and Evolution of Software Architectures For Product Families (February 26-27, 1998). F. v. Linden, Ed. Lecture Notes In Computer Science, vol Springer- Verlag, London, Jaejoon Lee, Dirk Muthig, Feature-oriented Analysis and Design, in Applied Software Product Line Engineering, CRC Press, Etxeberria, L.; Sagardui,G.;, Product line architecture: new issues for evaluation, in: Proceedings of the 9th International Conference on Software Product Lines, 2005, pp
Product Line Engineering Lecture PLE Principles & Experiences (2)
Product Line Engineering Lecture PLE Principles & Experiences (2) Dr. Martin Becker martin.becker@iese.fraunhofer.de 2 Copyright 2011 Product Line Scoping --- Recap --- Introduction Reuse Approaches Typical
More informationArchitecture. By Glib Kutepov Fraunhofer IESE
Architecture By Glib Kutepov Glib.kutepov@iese.fraunhofer.de Outline 1. Why Architecture? 2. What is Architecture? 3. How to create an Architecture? Alignment Modeling and Structuring Architectural Views
More informationModel Driven Architecture as Approach to Manage Variability in Software Product Families
Model Driven Architecture as Approach to Manage Variability in Software Product Families Sybren Deelstra, Marco Sinnema, Jilles van Gurp, Jan Bosch Department of Mathematics and Computer Science, University
More informationinitiating software product lines Modeling and Using Product Line Variability in Automotive Systems
focus initiating software product lines Modeling and Using Product Line Variability in Automotive Systems Steffen Thiel and Andreas Hein, Robert Bosch Corporation Automotive systems provide a broad spectrum
More informationIngegneria del Software II academic year: Course Web-site: [www.di.univaq.it/ingegneria2/]
Course: Ingegneria del Software II academic year: 2004-2005 Course Web-site: [www.di.univaq.it/ingegneria2/] Software Product Lines and Product Line Architectures Lecturer: Henry Muccini and Vittorio Cortellessa
More informationThe Systems and Software Product Line Engineering Lifecycle Framework
Revised January 27, 2013 Contact Information: info@biglever.com www.biglever.com 512-426-2227 The Systems and Software Product Line Engineering Lifecycle Framework Report ##200805071r4 Mainstream forces
More informationDesigning Software Ecosystems. How Can Modeling Techniques Help? Mahsa H. Sadi, Eric Yu. 1 Introduction. 2 Modeling Requirements.
Introduction Ecosystems Mahsa H. Sadi, Department of Computer Science University of Toronto E mail: mhsadi@cs.toronto.edu Exploring Modeling Methods for Systems Analysis and Design (EMMSAD) Working Conference
More informationFunctional Hazard Assessment in Product-Lines A Model-Based Approach
Functional Hazard Assessment in Product-Lines A Model-Based Approach Ibrahim Habli, Tim Kelly, Richard Paige Department of Computer Science, University of York, York, United Kingdom {Ibrahim.Habli, Tim.Kelly,
More informationSoftware Product Line Engineering L5:Organisations and SPL
Software Product Line Engineering L5:Organisations and SPL L5:Processes and SPL and Organizations Economics Planning Strategy Business People Organisati on Structures Techn. L5 Architect ure Process L5
More informationProduct Line Potential Analysis
Product Line Potential Analysis Claudia Fritsch and Ralf Hahn Robert Bosch GmbH Corporate Research and Development P.O. Box 94 03 50, D-60461 Frankfurt, Germany {Claudia.Fritsch Ralf.Hahn}@de.bosch.com
More informationPractical Evaluation of Software Product Family Architectures 1
Practical Evaluation of Software Product Family Architectures 1 Eila Niemelä, Mari Matinlassi, Anne Taulavuori VTT Technical Research Centre of Finland P.O. Box 1100, FIN-90571 Oulu, Finland {Eila.Niemela,
More informationModel Driven Development with Non-Functional Aspects
Model Driven Development with Non-Functional Aspects Liming Zhu, Yan Liu NICTA, Australian Technology Park, Eveleigh, Australia School of Computer Science and Engineering, University of New South Wales,
More informationTDT4252 Modelling of Information Systems Advanced Course
1 TDT4252 Modelling of Information Systems Advanced Course Sobah Abbas Petersen Adjunct Associate Professor sap@idi.ntnu.no 2 Today s Lecture AKM in Industry: an example A15: K.Sandkuhl and F. Lillehagen,
More informationJOURNAL OF OBJECT TECHNOLOGY
JOURNAL OF OBJECT TECHNOLOGY Online at www.jot.fm. Published by ETH Zurich, Chair of Software Engineering JOT, 2009 Vol. 8, No. 5, July-August 2009 Goal-driven Product Derivation John D. McGregor, Clemson
More informationUsing intentional actor modeling. enterprise software architectures
Using intentional actor modeling to support the evolution of enterprise software architectures in organizations istar 10 workshop @ CAiSE 2010 Hammamet, Tunisia June 2010 Daniel Gross & Eric Yu Daniel
More informationA Reuse-Oriented Product-Line Method for Enterprise Web Applications
A Reuse-Oriented Product-Line Method for Enterprise Web Applications Neil Mather and Samia Oussena School of Computing and Technology University of West London, London, UK, W5 5RF Abstract. Software product
More informationSEI Architecture Techniques complementary to the RUP Stuart Kerrigan, Richard van Schelven Principal Engineers Data Networks
SEI Architecture Techniques complementary to the RUP Principal Engineers Data Networks SATURN 14 th -16 th May 2007 Agenda Setting the scene SEI & the RUP Summary Future Work Q&A SATURN 14 th -16 th May
More informationTDT4252 Modelling of Information Systems Advanced Course
1 TDT4252 Modelling of Information Systems Advanced Course Sobah Abbas Petersen Adjunct Associate Professor sap@idi.ntnu.no 2 Today s Lecture AKM in Industry: an example Purpose: To describe an approach
More informationGeneration-Based Software Product-Line Evolution: A Case Study
Generation-Based Software Product-Line Evolution: A Case Study Konstantin Romanovsky 1 Saint-Petersburg State University, Mathematics And Mechanics Faculty, School of Software Engineering Abstract Product-line
More informationExtending Software Architecting Processes with Decision-Making Activities
Extending Software Architecting Processes with Decision-Making Activities Rafael Capilla and Francisco Nava Department of Computer Science, Universidad Rey Juan Carlos, c/ Tulipán s/n, 28933, Madrid, Spain
More informationSOMF at a Glance. Methodologies Corporation:
SOMF at a Glance Service-Oriented Modeling Framework (SOMF) - A modeling platform for Enterprise Architecture, Business Architecture, Application Architecture, service-oriented architecture (SOA), and
More informationProbabilistic Macro-Architectural Decision Framework
Probabilistic Macro-Architectural Decision Framework Plamen Petrov, University of Robert L. Nord, Carnegie Mellon University Ugo Buy, University of Presented at the 2 nd International Workshop on Software
More informationCapability Patterns as the Enablers for Model-based Development of Business Context-aware Applications
Capability Patterns as the Enablers for Model-based Development of Business Context-aware Applications Janis Stirna 1, Jelena Zdravkovic 1, Martin Henkel 1, Janis Kampars 2 1 Department of Computer and
More informationLecture 1. In practice, most large systems are developed using a. A software process model is an abstract representation
Chapter 2 Software Processes Lecture 1 Software process descriptions When we describe and discuss processes, we usually talk about the activities in these processes such as specifying a data model, designing
More informationReusing Platform-specific Models in Model-Driven Architecture for Software Product Lines
Reusing Platform-specific Models in Model-Driven Architecture for Software Product Lines Frédéric Verdier 1,2, Abdelhak-Djamel Seriai 1 and Raoul Taffo Tiam 2 1 LIRMM, University of Montpellier / CNRS,
More informationSWE 211 Software Processes
SWE 211 Software Processes These slides are designed and adapted from slides provided by Software Engineering 9 /e Addison Wesley 2011 by Ian Sommerville 1 Outlines Software process models Process activities
More informationQuantifying Product Line Benefits
Quantifying Product Line Benefits Peter Knauber, Fraunhofer IESE, Germany, peter.knauber@iese.fhg.de Jesus Bermejo, Telvent, Spain, jesus.bermejo@telvent.abengoa.com Günter Böckle, Siemens AG, Corporate
More informationChallenges of Capturing Design Rationales in Enterprise Architecture: A case study
Challenges of Capturing Design Rationales in Enterprise Architecture: A case study Georgios Plataniotis 1,2,4, Sybren de Kinderen 3,4, and Henderik A. Proper 1,2,4 1 Public Research Centre Henri Tudor,
More informationExtending the SPES Modeling Framework for Supporting Role-specific Variant Management in the Engineering Process of Embedded Software
Extending the SPES Modeling Framework for Supporting Role-specific ariant Management in the Engineering Process of Embedded Software Tobias Kaufmann 1, Christian Manz 2, Thorsten Weyer 1 1 University of
More informationMethods for the specification and verification of business processes MPB (6 cfu, 295AA)
Methods for the specification and verification of business processes MPB (6 cfu, 295AA) Roberto Bruni http://www.di.unipi.it/~bruni 04 - Methodology 1 Objective Coarse-grained methodology for developing
More informationinitiating software product lines Feature-Oriented Product Line Engineering
focus initiating software product lines -Oriented Product Line Engineering Kyo C. Kang and Jaejoon Lee, Pohang University of Science and Technology Patrick Donohoe, Software Engineering Institute, Carnegie
More informationArchitecting High Quality Software: The Role of Software Architecture in System Development and Evolution
Architecting High Quality Software: The Role of Software Architecture in System Development and Evolution Linda Northrop Director, Product Line Systems Program SEI 2007Carnegie Mellon University Software
More informationInterface Management in a Large Enterprise
Eclipse Finance Day 2012 Public Interface Management in a Large Enterprise Eclipse Finance Day 2012 Robert Blust October 16, 2012 Tooling Context Enterprise Project Components Interfaces Data Types Workforce
More informationLecture 5: Requirements Engineering II. COSI 120b, Principles of Software Engineering
Lecture 5: Requirements Engineering II COSI 120b, Principles of Software Engineering Your Requirements Customer UI Designer Tester Sales End User Your Requirements What did they look like? How specific
More informationSoftware Product Lines. Dennis Wagelaar Viviane Jonckers Software Languages Lab
Dennis Wagelaar Viviane Jonckers Software Languages Lab (SPL) SPL origins, goals SPL concepts Core assets, features Product decisions, output SPL process SCV analysis, feature modelling Configuration,
More informationEnterprise Architecture: an ideal discipline for use in Supply Chain Management
Enterprise Architecture: an ideal discipline for use in Supply Chain Management Richard Freggi Senior Supply Chain Architect (TOGAF 9.1 certified level 2) HP Inc. Content Understanding Supply Chain Management
More informationExpand application range with respect to consider the whole system. Consider state of the art and adapt actual regulations and standards
V-Model 97 is not state of the art in all fields No further development since that time 07/1997: update and release of V-Model 97 Increasingly applied in business, partially in SMBs, too Generally binding
More informationDesign of an Integrated Model for Development of Business and Enterprise Systems
International Journal of Research Studies in Computer Science and Engineering (IJRSCSE) Volume 2, Issue 5, May 2015, PP 50-57 ISSN 2349-4840 (Print) & ISSN 2349-4859 (Online) www.arcjournals.org Design
More informationQuality Management of Software and Systems
Quality Management of Software and Systems Processes and QM Prof. Dr. Liggesmeyer, 1 Contents Rational Unified Process (RUP) Extreme Programming (XP) Processes Prof. Dr. Liggesmeyer, 2 Starting point:
More informationProf. Dr. Liggesmeyer, 1. Quality Management of Software and. Processes and QM. Systems. QMSS Processes and QM
Quality Management of Software and Systems Processes and QM Prof. Dr. Liggesmeyer, 1 Contents V-Model XT Rational Unified Process (RUP) Extreme Programming (XP) Processes Prof. Dr. Liggesmeyer, 2 V-Model
More informationCMMI SM Model Measurement and Analysis
Carnegie Mellon University Software Engineering Institute CMMI SM Model CMMI SM is a Service Mark of Carnegie Mellon University Carnegie Mellon University Software Engineering Institute CMMI Staged Representation
More informationProduct Line Challenges and Organization Structuring Critical Success Factors
Product Line Challenges and Organization Structuring Critical Success Factors Agnes Owuato Odongo Kenya Electricity Generating Company aodongo@kengen.co.ke Abstract: Several methods have been published
More informationSoftware Development Methodologies
Software Development Methodologies Lecturer: Raman Ramsin Lecture 4 Integrated Object-Oriented Methodologies: OPM and RUP 1 Object Process Methodology (OPM) Introduced by Dori in 1995. Primarily intended
More informationEstablishing an SOA composite applications development process for work- based learning and competency progression management
Int. J., Vol. x, No. x, xxxx 1 Establishing an SOA composite applications development process for work- based learning and competency progression management Hilary Dexter, Jim Petch and Dan Powley 186
More informationImplementing Enterprise Architecture with MDA
Implementing Enterprise with MDA Mike Rosen CTO, M²VP Mrosen@m2vp.com Copyright M 2 VP Inc. 2003, All rights reserved Agenda What is Enterprise? What does it mean to implement it? How does MDA help? Enterprise
More informationMDA and Stakeholders in an MDA Process
MDA and Stakeholders in an MDA Process and the support for their roles www.bournemouth.ac.uk Model Driven Architecture (MDA) An approach: to system development, which increases the rigour of models. It
More informationSupport for Hardware Devices in Component Models for Embedded Systems
Support for Hardware Devices in Component Models for Embedded Systems Luka Lednicki School of Innovation, Design and Engineering Mälerdalen University October, 2009 Contents 1.Research topic...2 2.Research
More informationModel-based Management of Software Platforms
Model-based Management of Software Platforms Vector Congress, 20th of November 2018, Stuttgart V1.3 2018-11-19 Agenda Project and Platform Driven Development Reasons for Variants Platform Process Summary
More informationWhy Document the Architecture? EEC 421/521: Software Engineering. Design Process. Thinking About Design. Stakeholder Communication.
Why Document the Architecture? EEC 421/521: Software Engineering Architectural Design Stakeholder Communication High-level presentation of system System Analysis Big effect on performance, reliability,
More informationThe Strengths and Weaknesses of Software Architecture Design in the RUP, MSF, MBASE and RUP-SOA Methodologies: A Conceptual Review
Reyes-Delgado, P. Mora, M., Duran-Limon H., Rodriguez-Martnez, L., O'Connor, R.V. and Mendoza-Gonzalez, R., The Strengths and Weaknesses of Software Architecture Design in the RUP, MSF, MBASE and RUP-SOA
More informationGOAL-BASED MODELING FOR REQUIREMENT TRACEABILITY OF SOFTWARE PRODUCT LINE
GOAL-BASED MODELING FOR REQUIREMENT TRACEABILITY OF SOFTWARE PRODUCT LINE 1 ASAD ABBAS, 2 ISMA FARAH SIDDIQUI, 3* SCOTT UK-JIN LEE 1,2,3 Department of Computer Science and Engineering, Hanyang University
More informationIEEE and Agile Process- Create Architecture Description through Agile Architecture Framework
Int'l Conf. Software Eng. Research and Practice SERP'17 149 IEEE 42010 and Agile Process- Create Architecture Description through Agile Architecture Framework Shun Chi Lo and Ning Chen Department of Computer
More informationA Process Model for Project Members Conforming to Enterprise Architecture
A Process Model for Project Members Conforming to Enterprise Architecture Ralph Foorthuis Sjaak Brinkkemper Frank Hofman Technical Report UU-CS-2008-023 September 2008 Department of Information and Computing
More informationGoal Model Integration for Tailoring Product Line Development Processes
Goal Model Integration for Tailoring Product Line Development Processes Arfan Mansoor Software Architectures and Product Line Group Ilmenau University of Technology Ilmenau, 98693, Germany Detlef Streitferdt
More informationFormalizing Enterprise Architecture Decision Models using Integrity Constraints
Formalizing Enterprise Architecture Decision Models using Integrity Constraints Marc van Zee, Dirk van der Linden, Diana Marosin and Georgios Plataniotis University of Luxembourg, Luxembourg Public Research
More informationversion NDIA CMMI Conf 3.5 SE Tutorial RE - 1
Requirements Engineering SE Tutorial RE - 1 What Are Requirements? Customer s needs, expectations, and measures of effectiveness Items that are necessary, needed, or demanded Implicit or explicit criteria
More informationthe state of the practice Product Line Engineering: The State of the Practice
focus the state of the practice Product Line Engineering: The State of the Practice Andreas Birk, sd&m Gerald Heller, Hewlett-Packard Isabel John and Klaus Schmid, Fraunhofer Institute for Experimental
More informationIssues and Models in Software Product Lines
Issues and Models in Software Product Lines Jorge L. Díaz-Herrera Department of Computer Science, Southern Polytechnic State University (SPSU) Peter Knauber Fraunhofer Institute for Experimental Software
More informationArchitecture-led Incremental System Assurance (ALISA) Demonstration
Architecture-led Incremental System Assurance (ALISA) Demonstration Peter Feiler Software Engineering Institute Carnegie Mellon University Pittsburgh, PA 15213 [DISTRIBUTION STATEMENT A] This material
More informationFOUNDATIONAL CONCEPTS FOR MODEL DRIVEN SYSTEM DESIGN
FOUNDATIONAL CONCEPTS FOR MODEL DRIVEN SYSTEM DESIGN Loyd Baker, Paul Clemente, Bob Cohen, Larry Permenter, Byron Purves, and Pete Salmon INCOSE Model Driven System Interest Group Abstract. This paper
More informationOrganising Requirements
Requirements Organisation, Analysis and Evolution Software Requirements and Design CITS 4401 Lecture 20 CITS4401 Software Requirements and Design 2 Viewpoints Organising Requirements Interactor viewpoints:
More informationSE curriculum in CC2001 made by IEEE and ACM: What is Software Engineering?
SE curriculum in CC2001 made by IEEE and ACM: Overview and Ideas for Our Work Katerina Zdravkova Institute of Informatics E-mail: Keti@ii.edu.mk What is Software Engineering? SE is the discipline concerned
More informationComputer Science Technical Report. Modeling Approach Comparison Criteria for MODELS 2011 CMA Workshop
Computer Science Technical Report Modeling Approach Comparison Criteria for MODELS 2011 CMA Workshop Geri Georg, Colorado State University, USA Gunter Mussbacher, Carleton University, Canada Betty Cheng,
More informationSolution Architecture Training: Enterprise Integration Patterns and Solutions for Architects
www.peaklearningllc.com Solution Architecture Training: Enterprise Integration Patterns and Solutions for Architects (3 Days) Overview This training course covers a wide range of integration solutions
More informationSoftware Processes 1
Software Processes 1 Topics covered Software process models Process activities Coping with change 2 The software process A structured set of activities required to develop a software system. Many different
More informationRequirements Validation and Negotiation
REQUIREMENTS ENGINEERING LECTURE 2014/2015 Dr. Sebastian Adam Requirements Validation and Negotiation AGENDA Fundamentals of Requirements Validation Fundamentals of Requirements Negotiation Quality Aspects
More informationObjectives. The software process. Topics covered. Waterfall model. Generic software process models. Software Processes
Objectives Software Processes To introduce software process models To describe three generic process models and when they may be used To describe outline process models for requirements engineering, software
More informationIntroduction to Software Engineering
Introduction to Software Engineering 2. Requirements Collection Mircea F. Lungu Based on a lecture by Oscar Nierstrasz. Roadmap > The Requirements Engineering Process > Functional and non-functional requirements
More informationISO/IEC INTERNATIONAL STANDARD. Software and systems engineering Tools and methods for product line technical management
INTERNATIONAL STANDARD ISO/IEC 26555 First edition 2013-03-01 Software and systems engineering Tools and methods for product line technical management Ingénierie du logiciel et des systèmes Outils et méthodes
More informationRequirements Elicitation
Requirements Elicitation Software Engineering I Lecture 4 14. November 2006 Bernd Bruegge Applied Software Engineering Technische Universitaet Muenchen 1 Outline Motivation Requirements elicitation challenges
More informationOrchestration of automated vehicle functions
Orchestration of automated vehicle functions Automotive Electronics Systems Conference 2016 Overview Orchestration of automated vehicle functions Automation of vehicle functions Use of service oriented
More informationEngineering Practices and Patterns for Rapid BIT Evolution
Pursuant to ITAR 120.10, this document contains no technical data NDIA Systems Engineering Conference Engineering Practices and Patterns for Rapid BIT Evolution James Brewer Principal Systems Engineer
More informationTest Workflow. Michael Fourman Cs2 Software Engineering
Test Workflow Michael Fourman Introduction Verify the result from implementation by testing each build Plan the tests in each iteration Integration tests for every build within the iteration System tests
More informationAn Overview of Software Process
An Overview of Software Process Objectives To introduce the general phases of the software development life cycle (SDLC) To describe various generic software process models and discuss their pros and cons
More informationPTC INTEGRITY ASSET LIBRARY INTRODUCTION
PTC INTEGRITY ASSET LIBRARY INTRODUCTION Hedley Apperly VP Solution Management October 2015 AGENDA Asset Reuse & Modular Design Challenges Introducing PTC Integrity Asset Library Summary & Benefits Next
More informationINCOSE (MBSE) Model Based System Engineering (SoS) System of Systems Activity Introduction
INCOSE (MBSE) Model Based System Engineering (SoS) System of Systems Activity Introduction Ron Williamson, Ph.D. Raytheon ron.williamson@incose.org Jan 30-31, 2011 INCOSE IW11 MBSE Workshop MBSE Wiki page:
More informationSimon Fraser University, 2 Athabasca University
Requirements Engineering In Feature Oriented Software Product Lines: An Initial Analytical Study Mohsen Asadi 1, Bardia Mohabbati 1, Ebrahim Bagheri 2, Dragan Gašević 1,2, 1 Simon Fraser University, 2
More informationAssessing Merge Potential of Existing Engine Control Systems into a Product Line
Assessing Merge Potential of Existing Engine Control Systems into a Product Line Kentaro Yoshimura Hitachi Europe Automotive Research and Development Laboratory Dharmalingam Ganesan Dirk Muthig Fraunhofer
More informationVICCI. Feature-based Software Product Lines. and their Application. Exercise Academic Skills for Software Engineers
VICCI Visual and Interactive Cyber-Physical Systems Control and Integration Exercise Academic Skills for Software Engineers Feature-based Software Product Lines and their Application Christoph Seidl Georg
More informationAutomotive Systems Engineering und Functional Safety: The Way Forward
Automotive Systems Engineering und Functional Safety: The Way Forward Dr. Simon Burton Albert Habermann Vector Informatik GmbH Ingersheimer Strasse 24 70499 Stuttgart, Germany +49 711 80670 1529 albert.habermann@vector.com
More informationWorkshop Summary. Process Support of Software Product Lines
Workshop Summary 10 th International Software Process Workshop (ISPW 10): Process Support of Software Product Lines Barry Boehm, USC ISPW Program Chair (To appear in ISPW 10 Proceedings, IEEE, 1997) 1.
More informationMicrosoft Dynamics NAV Reference Model
Microsoft Dynamics NAV Reference Model Dejan Pajk, University of Ljubljana, Faculty of Economics, Kardeljeva pl. 17, 1000 Ljubljana, Slovenia, dejan.pajk@ef.uni-lj.si Abstract: The past decade has seen
More informationTowards Systematic Software Reuse in Certifiable Safety-Critical Systems
Towards Systematic Software Reuse in Certifiable Safety-Critical Systems Mikael Åkerholm 1,2, Rikard Land 1,2 1 Mälardalen University, School of Innovation, Design and Engineering, Västerås, Sweden 2 CC
More informationIntroduction of RUP - The Rational Unified Process
Introduction of RUP - The Rational Unified Process Jong-Hoon Lee Dependable Software Laboratory Konkuk University References Textbook: The Rational Unified Process Made Easy A Practitioner s Guide to the
More informationObject-Oriented Software Engineering Using UML, Patterns, and Java. Chapter 1: Introduction
Object-Oriented Software Engineering Using UML, Patterns, and Java Chapter 1: Introduction Object-Oriented Software Engineering Using UML, Patterns, and Java Ingegneria del software: scenario di riferimento
More informationTowards a Systematic Requirement-Based Test Generation Framework: Industrial Challenges and Needs
Towards a Systematic Requirement-Based Test Generation Framework: Industrial Challenges and Needs Shokoofeh Hesari Certus V&V Centre, Simula Research Laboratory University of Oslo Oslo, Norway Abstract
More informationArcade Game Maker Product Line Concept of Operations
Arcade Game Maker Product Line Concept of Operations ArcadeGame Team July 2003 Table of Contents 1 Overview 1 1.1 Identification 2 1.2 Document Map 2 1.3 Concepts 3 1.4 Readership 3 2 Approach 4 3 Background
More informationSoftware Processes. Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 1
Software Processes Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 1 Objectives To introduce software process models To describe three generic process models and when they may be
More informationARCADE Example. An example of application of the Open Architectural Description Framework ARCADE. Erlend Stav, Ståle Walderhaug, and Babak Farshchian
An example of application of the Open Architectural Description Framework ARCADE Erlend Stav, Ståle Walderhaug, and Babak Farshchian Developed by SINTEF ICT Copyright 2013 by SINTEF This work is licensed
More informationRepresenting Variability in Software Product Lines: A Case Study
Representing Variability in Software Product Lines: A Case Study Michel Jaring and Jan Bosch University of Groningen Department of Mathematics and Computing Science PO Box 800, 9700 AV Groningen The Netherlands
More informationOrganizational Knowledge Patterns: Foundations and Application Examples
ORADM, Cancun, March 2012 Organizational Knowledge Patterns: Foundations and Application Examples Kurt Sandkuhl The University of Rostock, Germany Where is Rostock? Hamburg Rostock Berlin The University
More informationTowards a requirements reuse method using Product Line in distributed environments
Towards a requirements reuse method using Product Line in distributed environments Thais Ebling, Jorge Luis Nicolas Audy, Rafael Prikladnicki Pontifical Catholic University of Rio Grande do Sul (PUCRS),
More informationThinking about Agile-Approach to PhD - Research
National Technical University Kharkiv Polytechnic Institute (http://www/kpi.kharkov.ua) Department of Software Engineering and Management Information Technologies V.N. Karazin National University of Kharkiv
More informationRequirements Analysis and Design Definition. Chapter Study Group Learning Materials
Requirements Analysis and Design Definition Chapter Study Group Learning Materials 2015, International Institute of Business Analysis (IIBA ). Permission is granted to IIBA Chapters to use and modify this
More informationThe Three Dimensions of Requirements Engineering: 20 Years Later
The Three Dimensions of Requirements Engineering: 20 Years Later Klaus Pohl and Nelufar Ulfat-Bunyadi Abstract Requirements engineering is the process of eliciting stakeholder needs and desires and developing
More informationMDA Overview Applied MDA
IBM Software Group MDA Overview Applied MDA Jim Amsden Senior Software Engineer IBM Rational Software jamsden@us.ibm,com Tutorial: MDA, UML, and applicability to SOA (C) IBM Corporation March 2006 Agenda!
More informationProduct Line Architectures for SOA
Product Line Architectures for SOA Mercy N. Njima 1, Maurice H. ter Beek 2, and Stefania Gnesi 2 1 IMT Institute for Advanced Studies, Lucca, Italy 2 Istituto di Scienza e Tecnologie dell Informazione,
More informationComponent-based Development Process and Component Lifecycle
-based Process and Lifecycle Ivica Crnkovic 1, Michel Chaudron 2, Stig Larsson 3 1 Mälardalen University, Department of Computer Science and Electronics, Sweden 2 Eindhoven University of Technology, Dept.
More informationComparative Study of Different Models in Component Based Software Engineering
e t International Journal on Emerging Technologies (Special Issue NCETST-2017) 8(1): 441-445(2017) (Published by Research Trend, Website: www.researchtrend.net) ISSN No. (Print) : 0975-8364 ISSN No. (Online)
More informationAn Iterative Model for Agile Product Line Engineering
An Iterative Model for Agile Product Line Engineering Yaser Ghanam University of Calgary yghanam@ucalgary.ca Abstract Agile software development (ASD) and software product line engineering (SPLE) seem
More information