Softw are Engineering for Em bedded System s Software Engineering - - PowerPoint PPT Presentation

▶
softw are engineering for em bedded system s software
SMART_READER_LITE
LIVE PREVIEW

Softw are Engineering for Em bedded System s Software Engineering - - PowerPoint PPT Presentation

Oct 09, 2023 202 likes •717 views

Softw are Engineering for Em bedded System s Software Engineering for Embedded Systems Mohammad. Abdullah Al Faruque Talal Bonny CES - C hair for E mbedded S ystems (Prof. Dr. Jrg Henkel) Department of Computer Science University of Karlsruhe

slide-1
SLIDE 1

Universität Karlsruhe ( TH)

Softw are Engineering for Em bedded System s

Mohammad Abdullah Al Faruque

Chair for Em bedded System s

WS 2005-06

Software Engineering for Embedded Systems

  • Mohammad. Abdullah Al Faruque

Talal Bonny

CES - Chair for Embedded Systems (Prof. Dr. Jörg Henkel) Department of Computer Science University of Karlsruhe

slide-2
SLIDE 2

Universität Karlsruhe ( TH)

Softw are Engineering for Em bedded System s

Mohammad Abdullah Al Faruque

Chair for Em bedded System s

WS 2005-06

Lectures Plan

Date Lecture Lecturer

25.10.2005 Introduction Bonny 08.11.2005 SW for ES Al Faruque 22.11.2005 Process Models Al Faruque 06.12.2005 Process Models Al Faruque 20.12.2005 SystemC Bonny 10.01.2006 SystemC Bonny 24.01.2006 MDA Bonny 07.02.2006 UML Al Faruque

slide-3
SLIDE 3

Universität Karlsruhe ( TH)

Softw are Engineering for Em bedded System s

Mohammad Abdullah Al Faruque

Chair for Em bedded System s

WS 2005-06

Definition of Software Engineering Embedded Systems at a Glance Embedded Software and Different Issues Related to Software Engineering Process Models Detail Description of V Model

Requirement Analysis

  • Example: Adaptive Cruise Control (ACC)

Requirement Engineering How to Do Requirement Analysis

  • Analysis of Functional Requirements
  • Quality Analysis

Architecture Design

Waterfall Model Spiral Model Rational Unified Process (RUP) Extreme Programming (XP) Lecture Contents ( Big Picture)

slide-4
SLIDE 4

Universität Karlsruhe ( TH)

Softw are Engineering for Em bedded System s

Mohammad Abdullah Al Faruque

Chair for Em bedded System s

WS 2005-06

V Model

Source: Prof. Dr.-Ing. Stefan Kowalewshi, RWTH

Architecture Architecture Design Design

slide-5
SLIDE 5

Universität Karlsruhe ( TH)

Softw are Engineering for Em bedded System s

Mohammad Abdullah Al Faruque

Chair for Em bedded System s

WS 2005-06

Architecture Architecture Design Design

Source: Prof. Dr.-Ing. Stefan Kowalewshi, RWTH

Tw o Analysis Paths

slide-6
SLIDE 6

Universität Karlsruhe ( TH)

Softw are Engineering for Em bedded System s

Mohammad Abdullah Al Faruque

Chair for Em bedded System s

WS 2005-06

Bass, Clements, Kazman, 2003 (modified): The architecture of a system is the structure or the structures of the system , w hich com prise elem ents, the externally visible properties of those elem ents, and the relationship am ong them

The architecture defines elements of the system

  • Architecture design is the first phase in which the system is no

longer a black box

  • The designer begins to structure the system into parts
  • Architecture manifests the earliest design decisions
  • Architecture is the blueprint for system integration

W hat is Architecture?

slide-7
SLIDE 7

Universität Karlsruhe ( TH)

Softw are Engineering for Em bedded System s

Mohammad Abdullah Al Faruque

Chair for Em bedded System s

WS 2005-06

Bass, Clements, Kazman, 2003 (modified): The architecture of a system is the structure or the structures of the system , w hich com prise elem ents, the externally visible properties of those elem ents, and the relationship am ong them

The architecture is only one step further in refinement

  • Now the elements are black boxes
  • The architecture specifies what the elements do and how they

interact from an outside ( system ‘s) perspective (often regarded as the element‘s responsibilities)

  • Central concept of architectures: I nterfaces

W hat is Architecture ( contd) ?

Source: Prof. Dr.-Ing. Stefan Kowalewshi, RWTH

slide-8
SLIDE 8

Universität Karlsruhe ( TH)

Softw are Engineering for Em bedded System s

Mohammad Abdullah Al Faruque

Chair for Em bedded System s

WS 2005-06

Bass, Clements, Kazman, 2003 (modified): The architecture of a system is the structure or the structures of the system , w hich com prise elem ents, the externally visible properties of those elem ents, and the relationship am ong them A system can have and usually has more than one structure.

Examples:

  • Design time elements (files, components, modules)
  • Run-time elements (processes, tasks, threads)
  • Behavioral elements (states, messages, queues)

The designer must consider different architectural view s

Source: Prof. Dr.-Ing. Stefan Kowalewshi, RWTH

W hat is Architecture ( contd) ?

slide-9
SLIDE 9

Universität Karlsruhe ( TH)

Softw are Engineering for Em bedded System s

Mohammad Abdullah Al Faruque

Chair for Em bedded System s

WS 2005-06

Bass, Clements, Kazman, 2003 (again):

Architecture represents earliest design decisions They are the most difficult to get correct and the hardest to change later in the design process They have the most far-reaching effects

W hy?

Architecture defines constraints on implementation Architecture dictates organizational structure Architecture inhibits or enables a system‘s quality ⇒ It is possible to predict system qualities by studying the architecture

I m portance of Architecture

Source: Prof. Dr.-Ing. Stefan Kowalewshi, RWTH

slide-10
SLIDE 10

Universität Karlsruhe ( TH)

Softw are Engineering for Em bedded System s

Mohammad Abdullah Al Faruque

Chair for Em bedded System s

WS 2005-06

Take most important qualities (SEI: ”architectural drivers“) Apply structuring principles which support these qualities Find a compromise, if qualities require contradicting structuring principles Architecture Design

Source: Prof. Dr.-Ing. Stefan Kowalewshi, RWTH

slide-11
SLIDE 11

Universität Karlsruhe ( TH)

Softw are Engineering for Em bedded System s

Mohammad Abdullah Al Faruque

Chair for Em bedded System s

WS 2005-06

Quality Attribute Scenarios ( Bass, Clem ents, Kazm an)

system

Stim ulus Environm ent Response Response m easure Source of stim ulus

Source: Prof. Dr.-Ing. Stefan Kowalewshi, RWTH

slide-12
SLIDE 12

Universität Karlsruhe ( TH)

Softw are Engineering for Em bedded System s

Mohammad Abdullah Al Faruque

Chair for Em bedded System s

WS 2005-06

Maintainability is the property of a system which describes how well faults can be removed General Scenario: Stimulus:

  • 1. A fault is detected
  • 2. Requirements change such that previous (implemented) design

decisions become wrong

Response:

  • 1. Change is made such that fault is removed without introducing new

faults

Response measure:

  • 1. Effort for removing fault
  • 2. Probability of introducing new faults

Exam ple: Maintainability

Source: Prof. Dr.-Ing. Stefan Kowalewshi, RWTH

slide-13
SLIDE 13

Universität Karlsruhe ( TH)

Softw are Engineering for Em bedded System s

Mohammad Abdullah Al Faruque

Chair for Em bedded System s

WS 2005-06

General principle ( SEI: “Tactics“) to achieve maintainability:

Keep changes local

  • Where the change is done
  • Which other parts are effected by the change.

Concrete structuring principle:

Information Hiding

Achieving Maintainability

slide-14
SLIDE 14

Universität Karlsruhe ( TH)

Softw are Engineering for Em bedded System s

Mohammad Abdullah Al Faruque

Chair for Em bedded System s

WS 2005-06

Definition of Software Engineering Embedded Systems at a Glance Embedded Software and Different Issues Related to Software Engineering Process Models Detail Description of V Model

Requirement Analysis

  • Example: Adaptive Cruise Control (ACC)

Requirement Engineering How to Do Requirement Analysis

  • Analysis of Functional Requirements
  • Quality Analysis

Architecture Design

Waterfall Model Spiral Model Rational Unified Process (RUP) Extreme Programming (XP) Lecture Contents ( Big Picture)

slide-15
SLIDE 15

Universität Karlsruhe ( TH)

Softw are Engineering for Em bedded System s

Mohammad Abdullah Al Faruque

Chair for Em bedded System s

WS 2005-06

Requirements Design Implementation Integration Validation Deployment

The W aterfall Model of the Softw are Life Cycle

slide-16
SLIDE 16

Universität Karlsruhe ( TH)

Softw are Engineering for Em bedded System s

Mohammad Abdullah Al Faruque

Chair for Em bedded System s

WS 2005-06

Requirements analysis and definition System and software design Implementation and unit testing Integration and system testing Operation and maintenance The main drawback of the waterfall model is the difficulty of accommodating change after the process is underway. One phase has to be complete before moving onto the next phase W aterfall Model Phases

slide-17
SLIDE 17

Universität Karlsruhe ( TH)

Softw are Engineering for Em bedded System s

Mohammad Abdullah Al Faruque

Chair for Em bedded System s

WS 2005-06

Inflexible partitioning of the project into distinct stages makes it difficult to respond to changing customer requirements Therefore, this model is only appropriate when the requirements are well-understood and changes will be fairly limited during the design process Few business systems have stable requirements The waterfall model is mostly used for large systems engineering projects where a system is developed at several sites W aterfall Model Problem s

slide-18
SLIDE 18

Universität Karlsruhe ( TH)

Softw are Engineering for Em bedded System s

Mohammad Abdullah Al Faruque

Chair for Em bedded System s

WS 2005-06

Definition of Software Engineering Embedded Systems at a Glance Embedded Software and Different Issues Related to Software Engineering Process Models Detail Description of V Model

Requirement Analysis

  • Example: Adaptive Cruise Control (ACC)

Requirement Engineering How to Do Requirement Analysis

  • Analysis of Functional Requirements
  • Quality Analysis

Architecture Design

Waterfall Model Spiral Model Rational Unified Process (RUP) Extreme Programming (XP) Lecture Contents ( Big Picture)

slide-19
SLIDE 19

Universität Karlsruhe ( TH)

Softw are Engineering for Em bedded System s

Mohammad Abdullah Al Faruque

Chair for Em bedded System s

WS 2005-06

Developed by Barry Boehm in the middle of the 80's Metamodell that includes other procedural models (i.e. waterfall model) Describes as one of the first procedural models, the iterative-incremental development process of software Spiral Model

Source: Dr.-I ng. M. Syrjakow

slide-20
SLIDE 20

Universität Karlsruhe ( TH)

Softw are Engineering for Em bedded System s

Mohammad Abdullah Al Faruque

Chair for Em bedded System s

WS 2005-06

Development follows a spiral from the inside towards

  • utward

Each turn of the spiral (phase) is an iterative evolutionary cycle with the same steps The goals of one cycle and risk analysis inferred from the previous cycle Separate spiral cycles for independent program sections possible Spiral should be kept as close as possible for cost minimization Spiral Model

Source: Dr.-I ng. M. Syrjakow

slide-21
SLIDE 21

Universität Karlsruhe ( TH)

Softw are Engineering for Em bedded System s

Mohammad Abdullah Al Faruque

Chair for Em bedded System s

WS 2005-06

Evaluate alternatives, identify, resolve risks, develop prototypes

Develop, verify next-level product Plan next phases

Determine objectives alternatives, constraints

Softw are Developm ent Lifecycle Spiral Model

slide-22
SLIDE 22

Universität Karlsruhe ( TH)

Softw are Engineering for Em bedded System s

Mohammad Abdullah Al Faruque

Chair for Em bedded System s

WS 2005-06

Spiral Model of the Softw are Process

slide-23
SLIDE 23

Universität Karlsruhe ( TH)

Softw are Engineering for Em bedded System s

Mohammad Abdullah Al Faruque

Chair for Em bedded System s

WS 2005-06

Identification of the goals of the partial product (achievement, functionality, etc..) Identification of alternative realization possibilities (draft A, draft B, re-use, purchase) Identification of the boundary conditions to consider those with the different alternatives (costs, time, interfaces, etc..) First Quadrant ( Goals)

Source: Dr.-I ng. M. Syrjakow

slide-24
SLIDE 24

Universität Karlsruhe ( TH)

Softw are Engineering for Em bedded System s

Mohammad Abdullah Al Faruque

Chair for Em bedded System s

WS 2005-06

Evaluation of the alternatives with consideration of the goals and boundary conditions If the evaluation shows the fact that it is risky, then a cost effective strategy has to be developed in order to overcome the risks This can be done e.g. by means of prototypes, Simulationen or user questionings Second Quadrant ( Risk Analysis)

Source: Dr.-I ng. M. Syrjakow

slide-25
SLIDE 25

Universität Karlsruhe ( TH)

Softw are Engineering for Em bedded System s

Mohammad Abdullah Al Faruque

Chair for Em bedded System s

WS 2005-06

Depending on the remaining risks the procedural model is specified for this step, e.g. evolutionary model, prototype model or waterfall model Also a combination of different models can be selected to minimize the risk Third Quadrant ( Developm ent/ Test)

Source: Dr.-I ng. M. Syrjakow

slide-26
SLIDE 26

Universität Karlsruhe ( TH)

Softw are Engineering for Em bedded System s

Mohammad Abdullah Al Faruque

Chair for Em bedded System s

WS 2005-06

Examination (Review) of the three preceding steps as well as planning of the next cycle by the person's groups or

  • rganizations concerned

Planning contains also a possible allocation of the SW product in components, which are then developed further independently Agreement (Commitment) over the next cycle Fourth Quadrant ( Planning)

Source: Dr.-I ng. M. Syrjakow

slide-27
SLIDE 27

Universität Karlsruhe ( TH)

Softw are Engineering for Em bedded System s

Mohammad Abdullah Al Faruque

Chair for Em bedded System s

WS 2005-06

Advantages

Flexible model (on changing requirements can be reacted) In periodic intervals one can examine and one has the chance to define again the procedure depending on the risk Integration of other procedural models Disadvantages High management expenditure, there are often new decisions Knowledge about identifying and managing of risks not yet popular Suitable for larger projects

Evaluation of the Spiral Model

Source: Dr.-I ng. M. Syrjakow

slide-28
SLIDE 28

Universität Karlsruhe ( TH)

Softw are Engineering for Em bedded System s

Mohammad Abdullah Al Faruque

Chair for Em bedded System s

WS 2005-06

Definition of Software Engineering Embedded Systems at a Glance Embedded Software and Different Issues Related to Software Engineering Process Models Detail Description of V Model

Requirement Analysis

  • Example: Adaptive Cruise Control (ACC)

Requirement Engineering How to Do Requirement Analysis

  • Analysis of Functional Requirements
  • Quality Analysis

Architecture Design

Waterfall Model Spiral Model Rational Unified Process (RUP) Extreme Programming (XP) Lecture Contents ( Big Picture)

slide-29
SLIDE 29

Universität Karlsruhe ( TH)

Softw are Engineering for Em bedded System s

Mohammad Abdullah Al Faruque

Chair for Em bedded System s

WS 2005-06

Develop in 1998 The RUP is based on two fundamental dimensions

Phases permit the management view, in order to judge the progress of the overall project Workflows permit the shared view on the individual activities

Rational Unified Process ( RUP)

Source: Dr.-I ng. M. Syrjakow

slide-30
SLIDE 30

Universität Karlsruhe ( TH)

Softw are Engineering for Em bedded System s

Mohammad Abdullah Al Faruque

Chair for Em bedded System s

WS 2005-06

Rational Unified Process ( RUP)

Source: Dr.-I ng. M. Syrjakow

slide-31
SLIDE 31

Universität Karlsruhe ( TH)

Softw are Engineering for Em bedded System s

Mohammad Abdullah Al Faruque

Chair for Em bedded System s

WS 2005-06

Who

Worker; define roles for persons who handles activities (sequences of working steps that leads to a meaningful result)

When

Workflow; indicates the sequence, in which certain activities follow one another

How

Activities; Part of the activity of the Workers, consist of the steps thinking, performing, reviewing and are terminated, if new artifact developed

What

Artifacts; Information units, are developed and used during the project (both input and output of activities)

W ho w hen How W hat?

Source: Dr.-I ng. M. Syrjakow

slide-32
SLIDE 32

Universität Karlsruhe ( TH)

Softw are Engineering for Em bedded System s

Mohammad Abdullah Al Faruque

Chair for Em bedded System s

WS 2005-06

Tool Mentor should support the developer using the project tool Guidelines specify proceeding, processes and rules for the work on the project Templates are used for the uniformity of documents and models in the project Further Elem ents of the RUP

Source: Dr.-I ng. M. Syrjakow

slide-33
SLIDE 33

Universität Karlsruhe ( TH)

Softw are Engineering for Em bedded System s

Mohammad Abdullah Al Faruque

Chair for Em bedded System s

WS 2005-06

Cooperate the Elem ents

Source: Dr.-I ng. M. Syrjakow

slide-34
SLIDE 34

Universität Karlsruhe ( TH)

Softw are Engineering for Em bedded System s

Mohammad Abdullah Al Faruque

Chair for Em bedded System s

WS 2005-06

At the Inception Stage the project extents and the relationship between contractor and customer is defined (life cycle objective) At the Elaboration Stage the system‘s structure is defined (life cycle architecture) At the Construction Stage the software is developed towards a running system (initial operational capability) At the Transition Stage the finished system is transferred from the development to the application area (product release) The Phases of the RUP

Source: Dr.-I ng. M. Syrjakow

slide-35
SLIDE 35

Universität Karlsruhe ( TH)

Softw are Engineering for Em bedded System s

Mohammad Abdullah Al Faruque

Chair for Em bedded System s

WS 2005-06

At each stage there are iterations whose workflows are processed similarly to the waterfall model At any time the RUP offers help with planning, guidelines, check lists and best practices The Phases of the RUP ( contd)

Source: Dr.-I ng. M. Syrjakow

slide-36
SLIDE 36

Universität Karlsruhe ( TH)

Softw are Engineering for Em bedded System s

Mohammad Abdullah Al Faruque

Chair for Em bedded System s

WS 2005-06

Business Modeling Business Processes and Task Domains are defined Requirement Management The demanded capacity of the system is specified Analysis and Design The requirements are transferred in an architecture Core W orkflow s of the RUP ( I )

Source: Dr.-I ng. M. Syrjakow

slide-37
SLIDE 37

Universität Karlsruhe ( TH)

Softw are Engineering for Em bedded System s

Mohammad Abdullah Al Faruque

Chair for Em bedded System s

WS 2005-06

Implementation On the basis of the technical models an executable system is developed Test Deployment The system must be arranged in such a way that it can be handed over to the user Core W orkflow s of the RUP ( I I )

Source: Dr.-I ng. M. Syrjakow

slide-38
SLIDE 38

Universität Karlsruhe ( TH)

Softw are Engineering for Em bedded System s

Mohammad Abdullah Al Faruque

Chair for Em bedded System s

WS 2005-06

Configuration & Change Management

During the whole development process results have to be planned and managed

Project Management

Planning and Supervision of the activities need to reach the envisaged milestones

Environment

The used tools are part of the development surroundings. The planning and supervision of these surroundings require their own workflow as the project‘s scope increases

Supporting W orkflow s of the RUP

Source: Dr.-I ng. M. Syrjakow

slide-39
SLIDE 39

Universität Karlsruhe ( TH)

Softw are Engineering for Em bedded System s

Mohammad Abdullah Al Faruque

Chair for Em bedded System s

WS 2005-06

Heavy weight Many formal definitions Very structured Iterative increment

Iterations are steps in the Workflow Increments are additions and improvements of the product

Application Driven Architecture-centered Main Features of the RUP

Source: Dr.-I ng. M. Syrjakow

slide-40
SLIDE 40

Universität Karlsruhe ( TH)

Softw are Engineering for Em bedded System s

Mohammad Abdullah Al Faruque

Chair for Em bedded System s

WS 2005-06

The user receives a total view of the architecture, which is divided into the following five views:

Logical view (view of the final user) Implementation view (view of the programmer) Process view (view of the system integrator) Distribution view (view of system engineer) Use Case view (view of the Analyst/ Testers)

Architecture-centered Process

Source: Dr.-I ng. M. Syrjakow

slide-41
SLIDE 41

Universität Karlsruhe ( TH)

Softw are Engineering for Em bedded System s

Mohammad Abdullah Al Faruque

Chair for Em bedded System s

WS 2005-06

The consistent and complete use of RUP only make sense for teams over 10 persons. Over 30 roles must be assigned and over 100 different artifact types (result of working types) needs to be documented and administered. Further See http: / / www.rational.com/ products/ rup W hen Does RUP Make Sense?

Source: Dr.-I ng. M. Syrjakow

slide-42
SLIDE 42

Universität Karlsruhe ( TH)

Softw are Engineering for Em bedded System s

Mohammad Abdullah Al Faruque

Chair for Em bedded System s

WS 2005-06

Definition of Software Engineering Embedded Systems at a Glance Embedded Software and Different Issues Related to Software Engineering Process Models Detail Description of V Model

Requirement Analysis

  • Example: Adaptive Cruise Control (ACC)

Requirement Engineering How to Do Requirement Analysis

  • Analysis of Functional Requirements
  • Quality Analysis

Architecture Design

Waterfall Model Spiral Model Rational Unified Process (RUP) Extreme Programming (XP) Lecture Contents ( Big Picture)

slide-43
SLIDE 43

Universität Karlsruhe ( TH)

Softw are Engineering for Em bedded System s

Mohammad Abdullah Al Faruque

Chair for Em bedded System s

WS 2005-06

In 1999 by Kent Beck developed as- "an easy, efficient, low-risk, flexible, calculable, accurate and pleasurable way of the software development" Extrem e Program m ing ( XP)

Source: Dr.-I ng. M. Syrjakow

slide-44
SLIDE 44

Universität Karlsruhe ( TH)

Softw are Engineering for Em bedded System s

Mohammad Abdullah Al Faruque

Chair for Em bedded System s

WS 2005-06

Agiler software development process for small teams Made possible to react itself to vague and rapidly changing requirements It can go on without a strict requirement catalog But also customer's requests are considered, which requests appear during the software development The XP development process goes through again and again in short cycles in all disciplines of the classical software development process (requirement analysis, Design, implementation, integration, test) Extrem e Program m ing

Source: Dr.-I ng. M. Syrjakow

slide-45
SLIDE 45

Universität Karlsruhe ( TH)

Softw are Engineering for Em bedded System s

Mohammad Abdullah Al Faruque

Chair for Em bedded System s

WS 2005-06

User Stories: The requirements of the software is collected not like the RUP in Use Cases, but in user

  • Stories. User Stories describe GUIs, functionalities and

test scenarios On-site Customer: A competent representative of the customer is present during the entire development time with the developers (might be only rarely realizable). Pair Program m ing: At the development computers two developers sit and develop together. Main Features of XP

Source: Dr.-I ng. M. Syrjakow

slide-46
SLIDE 46

Universität Karlsruhe ( TH)

Softw are Engineering for Em bedded System s

Mohammad Abdullah Al Faruque

Chair for Em bedded System s

WS 2005-06

Testing: Before the development of a module, customizable test cases are programmed. Simple Design: No unnecessary features are implemented Small Releases: Frequent iterations accomplished with executable programs as result, which the customer examines. Refactoring: The source code is rather early re- structured (if necessarily). Main Features of XP ( contd)

Source: Dr.-I ng. M. Syrjakow

slide-47
SLIDE 47

Universität Karlsruhe ( TH)

Softw are Engineering for Em bedded System s

Mohammad Abdullah Al Faruque

Chair for Em bedded System s

WS 2005-06

Continuous integration:

By different team members produced code is very frequently united.

Collective Ownership:

The developed source code belongs to the entire team. Everyone is responsible for each code. The teams rotate cyclically.

Coding standard:

Conventions are provided for the structure of the code, in order to facilitate legibility/ readability. Further see http: / / www.extremeprogramming.org and http: / / www.xprogramming.com.

Main Features of XP ( contd)

Source: Dr.-I ng. M. Syrjakow

slide-48
SLIDE 48

Universität Karlsruhe ( TH)

Softw are Engineering for Em bedded System s

Mohammad Abdullah Al Faruque

Chair for Em bedded System s

WS 2005-06

Two programmers working side-by-side, collaborating

  • n the same design, algorithm, code or test. One

programmer, the driver, has control of the keyboard/ mouse and actively implements the

  • program. The other programmer, the observer,

continuously observes the work of the driver to identify tactical (syntactic, spelling, etc.) defects and also thinks strategically about the direction of the

  • work. On demand, the two programmers can

brainstorm any challenging problem. Because the two programmers periodically switch roles, they work together as equals to develop software.

  • - Laurie W illiam s

North Carolina State University Computer Science

W hat is Pair Program m ing?

Source: Dr.-I ng. M. Syrjakow

slide-49
SLIDE 49

Universität Karlsruhe ( TH)

Softw are Engineering for Em bedded System s

Mohammad Abdullah Al Faruque

Chair for Em bedded System s

WS 2005-06

End Of the Lecture 3

slide-50
SLIDE 50

Universität Karlsruhe ( TH)

Softw are Engineering for Em bedded System s

Mohammad Abdullah Al Faruque

Chair for Em bedded System s

WS 2005-06