Requirements Engineering Process

Improvement: An Industrial Case Study

Ali Hajou3903958

1

2

Presentation contentO Author introductionO Paper outlineO Related literatureO PDD O ExampleO Conclusion

3

Author information (1)

Georgi A. MarkovO Req. Engineer at Siemens Corp. Tech.O University of FreiburgO European University of ViadrinaO Furtwangen University of Applied Sciences

4

Author information (2)

O Anne HoffmannO Req. Engineer and Project manager at

Siemens AG.O Active in the field of Req. Engineering

5

Author information (3)

O Oliver CreightonO Req. Engineer at Siemens Corp. Tech.O Guest researcher at Tech. Universität

München

6

Paper outline (1)

Case study

Improving

Requirements Engineering Process

7

Paper outline (2)O Problems

1. Communication gap2. Limited amount of ‘monolithic’ reqs3. Req. Overload4. Insufficient Traceability5. …6. ..

8

Paper outline (3)O Requirements Engineering Reference

Model O Goal-Oriented Requirements EngineeringO The Requirements PyramidO Feature-Driven DevelopmentO ScrumO Feature ModelingO Component Family ModelingO Model-Based Requirements Engineering

O Predefined a couple of methods O Requirements meta modelO Feature and family modelO Requirement Engineering Process

9

Paper outline (4)

10

Related literatureO Origin of problems is missing

O Can partially answer the research question (Lauesen & Vinter, 2001; Sawyer, Sommerville and Viller, 1997)

O Req. metamodel is not complete (according to other literature. O Missing “requirement maturity” (Sommerville &

Sawyer, 1997; Beecham, Hall & Rainer, 2005)O Missing details of req. traceability (Gotel &

Finkelstein, 1994; Damian, Zowghi, Viadyanathasamy and Pal, 2004; Ramesh & Yarke, 2001)

11

PDD

Prepare yourself

12

Example (1)O BG1: Register ClientsO PG1: Client registrationO UC1: Use Case “client registration overview”O F1: Feature “New client registration page”O FM1: Feature Model “Client registration”

O F2: (Child) Feature “Register new client using face recognition”O F3: (Child) Feature “Register new client by entering first and last name”

O SRH1: Stakeholder“Shop owner”O UR1: User Requirement “The person behind the desk must be able

to register new clients using face recognition or by entering its first and last name”

O C1: Component “Webpage”O C2: Component “Button for taking a picture using the

webcam”O C3: Component “Manual entry of first and last name”O C4: Component “Automatically create face pattern”O C5: Component “Save and register new client”O SCM1: Solution Component Mode “Client registration”O CONF1: Configuration“Method of registering clients”O P1: Product “Client registration Software”

O FDM1: Function Domain Model “Small Grocery Stores”

13

Example (2)

Meta element

Project

Business goal

Product goal

Stakeholder request

Use Case

User requirement

Feature

Parent feature

Feature model

Function domain model

Component

Parent component

Solution Component mode

Configuration

Product

Acronym PROJ BG PG SHR UC UR F F FM FDM C C SCM CONF P

1 1 1 1 1 1 1 - 1 1 1 - 1 1 1

1 1 1 1 1 1 2 1 1 1 2 1 1 1 1

1 1 1 1 1 1 2 1 1 1 4 1 1 1 1

  1 1 1 1 1 1 3 1 1 1 3 1 1 1 1

  1 1 1 1 1 1 1 - 1 1 5 1 1 1 1

14

ConclusionO Paper contains the case study

execution

O My focus was to the Requirements Engineering Metamodel

O Metamodel is missing some partsO Test cases + Test reportsO Requirement versioning O Product build or release ID

15

Questions?