Software Product Lines Krishna Anusha, Eturi. Introduction: A software product line is a set of software systems developed by a company that share a common.

Slides:



Advertisements
Similar presentations
Technology Management Activities and Tools
Advertisements

Component Based Software Engineering Ravi Kumar Mylavarapu.
2009 – E. Félix Security DSL Toward model-based security engineering: developing a security analysis DSML Véronique Normand, Edith Félix, Thales Research.
Lecture # 2 : Process Models
Chapter 22 Product Line Engineering Week 1 CIS 673.
Sponsored by the U.S. Department of Defense © 2004 by Carnegie Mellon University page 1 Pittsburgh, PA Integrating Domain Specific Modeling.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
Software Quality Metrics
Software Factory Assembling Applications with Models, Patterns, Frameworks and Tools Anna Liu Senior Architect Advisor Microsoft Australia.
Software Product Lines
Iterative development and The Unified process
Pertemuan Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
1.
1 Objective of today’s lesson S oftware engineering occurs as a consequence of a process called system engineering. Instead of concentrating solely on.
System Engineering Instructor: Dr. Jerry Gao. System Engineering Jerry Gao, Ph.D. Jan System Engineering Hierarchy - System Modeling - Information.
University of Jyväskylä – Department of Mathematical Information Technology Computer Science Teacher Education ICNEE 2004 Topic Case Driven Approach for.
Reuse Basic concepts. Rationale for reuse  Save calendar time  Save person hours  Reduce process risk  Increased quality  Standards compliance.
Course Instructor: Aisha Azeem
Software Product Line Engineering Andrew Burmester SE 4110 Section 2 4/14/11.
Autonomic Software Product Lines (ASPL) Nadeem Abbas, Jesper Andersson, Welf Löwe Linnaeus University, Sweden Monday, August 23, st International.
Software Product Line Architectures (SPLA) Nipun Shah
Computer Systems & Architecture Lesson Software Product Lines.
© 1998 Concept Five Technologies Enterprise Application Integration Capability Maturity Model.
MANAGING STRATEGY INTRODUCTION TO STRATEGIC MANAGEMENT.
SEI´S Software Product Line Tenets Linda M. Northrop Software Engineering Institute IEEE Software July/August 2002.
Software Product Line Testing Part I : Introduction
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
Developing an IS/IT Strategy
Chapter 2 The process Process, Methods, and Tools
Engineering, Operations & Technology | Information TechnologyAPEX | 1 Copyright © 2009 Boeing. All rights reserved. Architecture Concept UG D- DOC UG D-
Software System Engineering: A tutorial
T. Dawson, TASC 9/11/13 Use of a Technical Reference in NASA IV&V.
E MBEDDED S YSTEMS S OFTWARE T RAINING C ENTER S OFTWARE D ESIGN C OPYRIGHT © 2011 DSR C ORPORATION.
BMAN Integrative Team Project Week 2 Professor Linda A Macaulay.
1.  Project: temporary endeavor to achieve some specific objectives in a defined time  Project management ◦ Dynamic process ◦ Controlled and structured.
Code Reuse as a Practice within Extreme Programming Gerald DeHondt Kent State University Vijayan Sugumaran Oakland University.
SOFTWARE REUSABILITY AJAYINDER SINGH CSC What is Software Reuse Software reuse is the process of implementing or updating software systems using.
Rapid Application Development. What is RAD……..?  Rapid Application Development (RAD) is a software development process.  first developed during the.
In this topic we will look at: Issues With Information Technology And Management Information Systems Planning A Conceptual Model for Information Systems.
University of Southern California Center for Systems and Software Engineering Model-Based Software Engineering Supannika Koolmanojwong Spring 2013.
PREPARED BY: Hadeel El-Genedy SOFTWARE ARCHITECTURE COURSE PRE-MASTERS STUDIES COMPUTER SCIENCE DEPARTMENT CAIRO UNIVERSITY Software Product Line.
Introducing Software Product Lines (SPL) Silvio Romero de Lemos Meira Eduardo Santana de Almeida
Information Systems Engineering. Lecture Outline Information Systems Architecture Information System Architecture components Information Engineering Phases.
Software Product Line Material based on slides and chapter by Linda M. Northrop, SEI.
Systems Analysis and Design in a Changing World, Fourth Edition
Software Acquisition and Project Management Lesson I: Introduction.
A Goal Based Methodology for Developing Domain-Specific Ontological Frameworks Faezeh Ensan, Weichang Du Faculty of Computer Science, University of New.
APPLY FUNCTIONAL MODELING TO CONSEQUENCE ANALYSIS IN SUPERVISION SYSTEMS Present by Xinxin Zhang 1 Morten Lind 1, Giulio Gola 2,
A Metrics Program. Advantages of Collecting Software Quality Metrics Objective assessments as to whether quality requirements are being met can be made.
MODEL-BASED SOFTWARE ARCHITECTURES.  Models of software are used in an increasing number of projects to handle the complexity of application domains.
Foundations of Information Systems in Business. System ® System  A system is an interrelated set of business procedures used within one business unit.
Banaras Hindu University. A Course on Software Reuse by Design Patterns and Frameworks.
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
Applying Adaptive Software Development (ASD) Agile Modeling on Predictive Data Mining Applications: ASD-DM Methodology M. Alnoukari 1 Z.Alzoabi 2 S.Hanna.
Software Engineering Process - II 7.1 Unit 7: Quality Management Software Engineering Process - II.
Paula Serdeira Azevedo (1) Carlos Azevedo (2) Mário Romão (3)
Managing Enterprise Architecture
C_ITIP211 LECTURER: E.DONDO. Unit 1 : The Systems Development Environment.
Product Line Architecture. Systems Systems often come in families: basic, regular, professional, enterprise,… Can we share components? Is architecture.
Software Engineering cosc 4359 Spring 2017.
Presented by Munezero Immaculee Joselyne PhD in Software Engineering
Rapid Application Development Model
Object oriented system development life cycle
Software Product Lines
Advanced Management Control and Sustainable Development
Object-Oriented Systems Development Life Cycle (CH-3)
Introduction to Systems Analysis and Design Stefano Moshi Memorial University College System Analysis & Design BIT
Open API and Open Architecture Working Group (OA2-WG) *DRAFT*
Presentation transcript:

Software Product Lines Krishna Anusha, Eturi

Introduction: A software product line is a set of software systems developed by a company that share a common set of core requirements necessary for the developing a product with some known or allowable variations.

What is SPL? It is the process of developing related systems from common assets or common assets [2]. Core assets : The core assets include the architecture, reusable components, documentations, process descriptions etc [1].

Activities in the SPL: Core Asset Development, Product Development, Management.

Fig.1 Three activities of SPL

Core Asset Development: It includes the development of production capability by taking inputs and resulting outputs accordingly. The inputs and outputs are affected by each other as this process is iterative.

Fig 2. Core Asset Development

The inputs of the core assets development are: Product constraints, Styles, patterns, frameworks, Production constraints, Production strategy, Inventory of preexisting assets. The outputs of core assets development are: Core assets, Product line scope, Production plan.

Product Development: In the product development, the inputs include the requirements, product line scope and the core assets [5]. The output is the product itself.

Fig 3. Production Development

Management: The management includes two levels. They are: The organizational level and The technical level.

Fig 4.Management

Software Product Line practice areas: A practice area is the body of work or set of activities. Some of the practice areas defined for the product line concepts such as: Software engineering practices area, Organizational or Technical management.

Software engineering practice areas include the following: Architecture definition, Requirements engineering, Testing, Understanding relevant domains etc.

Technical management practice areas includes the following: Process definition, Technical risk management, Tool support etc.

The Organizational management practice areas include: Funding, Market analysis, Organizational planning, Training etc.

What are Product Line patterns: The patterns include ways to define similar contexts and problem/solution pairs. The practice areas are put into practices using the product line patterns [1].

Advantages of Software Product Line: Achieve productivity gains, Improve time to market, Exploit economies of scope through reuse of common assets [4], Enhance the predictability of software development processes, Improve software quality.

Conclusion: Future directions of Software Product Line are: The future directions of the Software Product Line is heading towards development of more strategic methods. Minimizing the short comes of the first generation methodologies, which used manual application engineering. This way, the dynamic software product lines are being developed [6]. The software mass customization is one of the development methodologies which focus on domain engineering of reusable assets [3].

References: [1] L. M. Northrop,” SEI’s Software Product Line Tenets”, IEEE Software, Vol. 19, I. 4, P , [2] P. Donohoe, "Introduction to Software Product Lines", 12th International Software Product Line Conference, P , [3] C. W. K. Krueger, “New methods in Software Product Line Development”, 10 th International Software Product Line conference, [4] C.W.Krueger,"Software product line reuse in practice",3rd IEEE Symposium on Application-Specific Systems and Software Engineering Technology, Proceedings, P , [5] J. Zhang, X. Cai, G. Liu, "The Role of Aspects in Software Product Lines", International Conference on Computer Science and Information Technology, P , 2008.

References contd.. [6] M. Kim, S. Park, “Goal and Scenario Driven Product Line Development”, IEEE Computer Society, 2004.

Questions ? Questions ?

Thank you