Product Line Engineering Lecture – Introduction (1)

2y ago
18 Views
2 Downloads
406.65 KB
26 Pages
Last View : 2d ago
Last Download : 2m ago
Upload by : Kaden Thurman
Transcription

Product Line Engineering Lecture –Introduction (1)Dr. Martin Beckermartin.becker@iese.fraunhofer.de2Copyright Fraunhofer IESE 2011

ContactDr. Martin BeckerFraunhofer IESEEmail: martin.becker@iese.fraunhofer.dePhone: 0631 / 6800 – 2246Questions before and after the lecture,via email/phone, and by appointment.1 Fraunhofer IESE

Organisational Issueslecture (2h) exercises (1h)Î 4 ECTS creditsLecture: Friday, 15:30-17:00 in IESEExercises: separate time slot, once every two weeks?Examinations: Oral Written2 Fraunhofer IESE

ExercisesExercises When: Friday, 17:15 - 18:45 Where: Fraunhofer IESE (Z04.06 –J. Nehmer)Contact Adeline SilvaFraunhofer IESEE-mail: adeline.silva@iese.fraunhofer.de3 Fraunhofer IESE

Lectures - 11 15:30 - 17:0028-Oct-11 15:30 - 17:004-Nov-11 15:30 - 17:0011-Nov-11 15:30 - 17:0018-Nov-11 15:30 - 17:0025-Nov-11 15:30 - 17:002-Dec-11 15:30 - 17:009-Dec-11 15:30 - 17:0016-Dec-11 15:30 - 17:006-Jan-12 15:30 - 17:0013-Jan-12 15:30 - 17:0020-Jan-12 15:30 - 17:0027-Jan-12 15:30 - 17:003-Feb-12 15:30 - v-11 17:15 - 18:4518-Nov-11 17:15 - 18:452-Dec-11 17:15 - 18:4516-Dec-11 17:15 - 18:456-Jan-12 17:15 - 18:4520-Jan-12 17:15 - 18:453-Feb-12 17:15 - 18:4610-Feb-12 15:30 - 17:00LocationIESEIESEIESEIESEIESEIESEIESEIESENoNo4 Fraunhofer IESE

Class InfrastructureRegister via email to adeline.silva@iese.fraunhofer.de Î access to Google groupSubject: Register – LectureContent Name: your name Course of studies and Semester Email Experience in Software Engineering University (lectures, classes) Industry OtherGet slides via AGSE Web-Site5 Fraunhofer IESE

Contents of the LectureEngineeringof variant-richsoftware / system families6 Fraunhofer IESE

Our GoalsAfter this course you will have learned a what challenges development organizations are facing due to variants why opportunistic reuse does not work how to systematically reuse software methods, techniques, and tools forsystematic variation management7 Fraunhofer IESE

Your Expectations?8 Fraunhofer IESE

Literature1. Software Product Line Engineering: Foundations, Principles andTechniques by Klaus Pohl, Günter Böckle and Frank J. Linden2. Software Product Lines: Practices and Patterns by Paul Clements andLinda Northrop3. Component-Based Product Line Engineering with UML by Colin Atkinson,Joachim Bayer, Christian Bunse and Erik Kamsties and some more research papers Fraunhofer IESE9

--- Motivation ---10 Fraunhofer IESE

The Beginning Most organizations usually do not develop a single system (product),but a set of products in a certain business area Many similar products arise over timet1t2Product ARelease 1Product ARelease 2t4t3tmtimeProduct ARelease N Product BRelease 1tn Product CRelease 1Product BRelease N Developing similar products always from scratch is unproductive it costs effort, time and money it leads to redundant effort in maintenance and quality assurance11 Fraunhofer IESE

In the Meantimepropagate changeswithin productsVersionVersion propagate changeswithin productspropagate changesacross productsVersionVersionVersion Versionpropagate changesacross productsVersionVersion Versionbug fix12 Fraunhofer IESE

Developers versus Maintainers (No Reuse!)10080Resources (%)604020developersmaintainers0# delivered systems (to be maintained)13 Fraunhofer IESE

Some more Challenges Increasing complexity of systems Need for reducing cost, effort,and time-to-market Increasing request for quality solutions Increasing demand for customized products Increasing inter projects/systems dependencies14 Fraunhofer IESE

Problem is well known is SE-Community:Î Software Crisis (1968)ÎYou can expect solutionsProblem is not limited to SE-Community15 Fraunhofer IESE

Approach I: Mature single system engineering Improvements of 5-10% per year possibleEffort perproduct Of course you must applythe state-of-the-practice You must adopt new approachesfrom time to timeoptimummaturity[schematicillustration]16 Fraunhofer IESE

Approach II: Reuse Inherent to human nature Î natural approach1. Use of existing solution2. Adapt similar solutions3. Develop anew Reusing existing solutions saves time and effort brings quality avoids complexity due to replicaCan be applied to any kind of system17 Fraunhofer IESE

Size of Code Base to be Maintained# LoC (to be maintained)Software Reuse# delivered systems (to be maintained)18 Fraunhofer IESE

Reuse approaches: Ad-hocProductRequirementsApplication EngineeringProductRequirementsProductApplication (Archive)ProductRequirementsProductApplication EngineeringProductReuseRepository(Archive)19 Fraunhofer IESE

Problems with Ad-hoc reuseExperiences Applied widely: Clone and Own Does not scale within an organization and across time due to Lacking means for organizing and managing reusable artifactsÎ Search effortsÎ Evaluation effortsÎ Adaptation efforts (80:20 rule holds here)Î Integration effortsIn most cases a no go!20 Fraunhofer IESE

Reuse Approaches: Domain EngineeringDomain edbackDomainApplication EngineeringProductIdea: Proactively develop for reuse21 Fraunhofer IESE

Problems of Domain EngineeringDomain Engineering: Development for reuse Understand domain concepts, entities, and relationships Set up, maintain, evolve reuse infrastructureApplication Engineering: Development with reuse Product development based on large-scale reuse Reuse is driven by domain concepts No searching for reusable artifacts requiredEmphasis is on Domain Engineering No clear termination criteria It takes forever Unclear domain boundaries Reusable artifacts become more general or generic then required And thus much harder to reuse and maintain Application engineering assumed as requiring no effort (ideal vision) Fraunhofer IESE22

Domain Engineering – Successes Cases GUI LibrariesHorizontal, well-understood domainswith limited variability Databases Middleware Operating Systems High risk that effort spentin variability supportdoes not pay of23 Fraunhofer IESE

Optimizing Reuse – Product Line EngineeringProduct Product Product1232 Considering the different products an organization or organizationalsector delivers as Product Family or Product Line Taking advantage of commonality Clear understanding about variability Strategic planning of software reuse Efficient productionProactively plan the reuse:Just the right variability support Fraunhofer IESE24

More about PLEProduct Line Concepts Success Stories in the next lecture see you there again25 Fraunhofer IESE

7 2-Dec-11 15:30 - 17:00 IESE 8 9-Dec-11 15:30 - 17:00 IESE 9 16-Dec-11 15:30 - 17:00 IESE 10 6-Jan-12 15:30 - 17:00 IESE 11 13-Jan-12 15:30 - 17:00 IESE 12 20-Jan-12 15:30 - 17:00 IESE 13 27-Jan-12 15:30 - 17:00 IESE 14 3-Feb-12 15:30 - 17:00 IESE No Date Time Location 1 4-Nov-11 17:15 - 18:45 IESE 2 18-Nov-11 17

Related Documents:

Introduction of Chemical Reaction Engineering Introduction about Chemical Engineering 0:31:15 0:31:09. Lecture 14 Lecture 15 Lecture 16 Lecture 17 Lecture 18 Lecture 19 Lecture 20 Lecture 21 Lecture 22 Lecture 23 Lecture 24 Lecture 25 Lecture 26 Lecture 27 Lecture 28 Lecture

Lecture 1: A Beginner's Guide Lecture 2: Introduction to Programming Lecture 3: Introduction to C, structure of C programming Lecture 4: Elements of C Lecture 5: Variables, Statements, Expressions Lecture 6: Input-Output in C Lecture 7: Formatted Input-Output Lecture 8: Operators Lecture 9: Operators continued

Lecture 1: Introduction and Orientation. Lecture 2: Overview of Electronic Materials . Lecture 3: Free electron Fermi gas . Lecture 4: Energy bands . Lecture 5: Carrier Concentration in Semiconductors . Lecture 6: Shallow dopants and Deep -level traps . Lecture 7: Silicon Materials . Lecture 8: Oxidation. Lecture

TOEFL Listening Lecture 35 184 TOEFL Listening Lecture 36 189 TOEFL Listening Lecture 37 194 TOEFL Listening Lecture 38 199 TOEFL Listening Lecture 39 204 TOEFL Listening Lecture 40 209 TOEFL Listening Lecture 41 214 TOEFL Listening Lecture 42 219 TOEFL Listening Lecture 43 225 COPYRIGHT 2016

Partial Di erential Equations MSO-203-B T. Muthukumar tmk@iitk.ac.in November 14, 2019 T. Muthukumar tmk@iitk.ac.in Partial Di erential EquationsMSO-203-B November 14, 2019 1/193 1 First Week Lecture One Lecture Two Lecture Three Lecture Four 2 Second Week Lecture Five Lecture Six 3 Third Week Lecture Seven Lecture Eight 4 Fourth Week Lecture .

5 What Are Lines And Stanzas? Line A line is pretty self-explanatory. Line A line of a poem is when it jumps Line To a new, well, line, Line Like this! Line Sometimes a line is a complete sentence. Line But it doesn’t Line Have to be! Line A stanza is kind of like a paragraph. Line Stanzas are made up of lines. Line This “stanza” has five lines.

Introduction to Quantum Field Theory for Mathematicians Lecture notes for Math 273, Stanford, Fall 2018 Sourav Chatterjee (Based on a forthcoming textbook by Michel Talagrand) Contents Lecture 1. Introduction 1 Lecture 2. The postulates of quantum mechanics 5 Lecture 3. Position and momentum operators 9 Lecture 4. Time evolution 13 Lecture 5. Many particle states 19 Lecture 6. Bosonic Fock .

MEDICAL RENAL PHYSIOLOGY (2 credit hours) Lecture 1: Introduction to Renal Physiology Lecture 2: General Functions of the Kidney, Renal Anatomy Lecture 3: Clearance I Lecture 4: Clearance II Problem Set 1: Clearance Lecture 5: Renal Hemodynamics I Lecture 6: Renal Hemodynamics II Lecture 7: Renal Hemodynam