requirements engineering - uc homepages

13
1 University of Cincinnati Department of Electrical Eng. and Computer Science © 2019, Nan Niu Requirements Engineering (Summer 2019) Prof. Nan Niu ([email protected] ) http://homepages.uc.edu/~niunn/courses

Upload: others

Post on 19-May-2022

4 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Requirements Engineering - UC Homepages

1

University of Cincinnati Department of Electrical Eng. and Computer Science

© 2019, Nan Niu

Requirements Engineering

(Summer 2019)

Prof. Nan Niu ([email protected])

http://homepages.uc.edu/~niunn/courses

Page 2: Requirements Engineering - UC Homepages

2

University of Cincinnati Department of Electrical Eng. and Computer Science

© 2019, Nan Niu

Today’s Menu

Next Seminar: Visual Modeling

Notations

This Seminar: Goal Modeling Assignment 1

Last Seminar: Req.s Elicitation

Page 3: Requirements Engineering - UC Homepages

3

University of Cincinnati Department of Electrical Eng. and Computer Science

© 2019, Nan Niu

Assignment 1 ➜ Dataset available on the course website

Ä http://homepages.uc.edu/~niunn/courses/

➜ Objectives

Ä Use the given set of functional requirements (FRs) to build an i* model

Ä Use your i* model to make the FRs more complete by following softgoal-based tradeoff analysis

➜ Due: before 8:30am on Friday (July 12)

Page 4: Requirements Engineering - UC Homepages

4

University of Cincinnati Department of Electrical Eng. and Computer Science

© 2019, Nan Niu

Assignment 1 (Cont’d) ➜ Schedule of Wednesday (July 10)

Ä 9:20-10:00: i* lecturing Ä 10:00-10:30: students working on their ASN1 (i*

modeling part) and the instructor doing Q&A Ä 10:30-11:00: softgoal analysis lecturing Ä 11:00-11:30: students working on their ASN1 (i*

modeling and softgoal-based tradeoff analysis) and the instructor doing Q&A

➜ Thursday (July 11) Ä 8:30-9:50: ASN1 Q&A Ä 10:00-10:40: Visual modeling notations (class

participation ) Ä 10:40-11:30:ASN1 Q&A

Page 5: Requirements Engineering - UC Homepages

5

University of Cincinnati Department of Electrical Eng. and Computer Science

© 2019, Nan Niu

i* Two views (SD & SR) Five nodes (actors, goals, softgoals, tasks,

resources) Three edges (dependency, decomposition,

softgoal contribution)

Page 6: Requirements Engineering - UC Homepages

6

University of Cincinnati Department of Electrical Eng. and Computer Science

© 2019, Nan Niu

Practical Impacts of i*➜ International standard

Ä User Requirements Notation (URN) Ø Goal Requirements Language (GRL) www.itu.int/rec/T-REC-Z.151/en

Ä Initiated from the telecom industry Ä ITU-T Recommendation Z.151

➜ Real-world applications Ä Air traffic control

Ø  N. Maiden et al. “Model-Driven Requirements Engineering: Synchronising Models in an Air Traffic Management Case Stud”, CAiSE, 2004.

Ä Food safety Ø  A. Perini and A. Susi. “Designing a Decision Support System for Integrated

Production in Agriculture: An Agent-Oriented Approach”, Environmental Modelling and Software Journal, 19(9), September 2004.

Ä Hospital wards Ø  S. Kethers et al. “Modelling Trust Relationships In A Healthcare Network:

Experiences With The TCD Framework”, ECIS 2005.

Page 7: Requirements Engineering - UC Homepages

7

University of Cincinnati Department of Electrical Eng. and Computer Science

© 2019, Nan Niu

Air Traffic Control

Page 8: Requirements Engineering - UC Homepages

8

University of Cincinnati Department of Electrical Eng. and Computer Science

© 2019, Nan Niu

Strategic Dependency (SD)

Page 9: Requirements Engineering - UC Homepages

9

University of Cincinnati Department of Electrical Eng. and Computer Science

© 2019, Nan Niu

Strategic Rationale (SR)

Page 10: Requirements Engineering - UC Homepages

10

University of Cincinnati Department of Electrical Eng. and Computer Science

© 2019, Nan Niu

Class Exercise – i* Modeling ➜ Let’s model our summer course

Ä Who’re the key stakeholders/actors? Ä How’re they depended on each other? Ä What’re their goals? Ä How to decompose the goals? Ä What’re the means and/or alternatives to achieve the goals?

Ä Are there any softgoals? Ä How’re the softgoals supported or hindered? Ä Does software-intensive system play any role here?

➜ Let me do SD with you first followed by SR

Page 11: Requirements Engineering - UC Homepages

11

University of Cincinnati Department of Electrical Eng. and Computer Science

© 2019, Nan Niu

Goal Analysis ➜ Goal Elaboration:

Ä “Why” questions explore higher goals (context) Ä “How” questions explore lower goals (operations) Ä “How else” questions explore alternatives

➜ Relationships between goals: Ä One goal helps achieve another (+) Ä One goal hurts achievement of another (-) Ä One goal makes another (++)

Ø Achievement of one goal guarantees achievement of another Ä One goal breaks another (--)

Ø Achievement of one goal prevents achievement of another Ä Precedence ordering (must achieve goals in a certain order)

➜ Obstacle Analysis: Ä Can this goal be obstructed, if so how? Ä What are the consequences of obstructing it?

Page 12: Requirements Engineering - UC Homepages

12

University of Cincinnati Department of Electrical Eng. and Computer Science

© 2019, Nan Niu

Softgoals as Selection Criteria

What’re (high-level) softgoals

of BART?

Page 13: Requirements Engineering - UC Homepages

13

University of Cincinnati Department of Electrical Eng. and Computer Science

© 2019, Nan Niu

Softgoals as Selection Criteria minimize costs

serve more passengers

improve safety

maintain safe

distance

reduce staffing

minimize operation

costs

minimize development

costs clearer signaling

automate collision

avoidance

automate braking

increase train speed

more frequent trains

add new tracks

maintain passenger comfort

buy new rolling stock hire more

operators

-

- ++ ++

++

-

-

-

+

- -