Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Software Requirement Engineering
Typology: Lecture notes
1 / 50
This page cannot be seen from the preview
Don't miss anything!
Source of PP slides :
- Lamsweerde, A. V. 2011. Requirements Engineering: From System goals to UML Models to Software Specification. 2 nd^ **ed.Wiley.
ļ½
ļ½
ļ½
ļ½
2 Lesson objectives:
ļ½
ā¦ (^) relevant position in the organization ā¦ (^) role in making decisions, reaching agreement ā¦ (^) type of contributed knowledge, level of domain expertise ā¦ (^) exposure to perceived problems ā¦ (^) personal interests, potential conflicts ā¦ (^) influence in system acceptance Stakeholder analysis (2) 4
ļ½ Distributed sources, conflicting viewpoints ļ½ (^) Difficult access to key people & data ļ½ (^) Different background, terminology, culture ļ½ (^) Hidden needs or/and Irrelevant details ļ½ (^) Internal politics, competition, resistance to change, ... ļ½ Personnel turnover, changes in organization, in priorities, ... Knowledge acquisition from stakeholders is difficult (1) 5
ļ½ 2 main categories of elicitation techniques:
7 Elicitation Techniques
8 Artefact-driven elicitation techniques
Background study (2) ļ½
ļ½
ļ½
ā¦ (^) know what you need to know & what you donāt need to know
Data collection ļ½
ā¦ (^) marketing data, usage statistics, performance figures, costs, ... ā¦ (^) selection of representative data sets from available sources (use of statistical sampling techniques) ļ½
ļ½
ļ½
ā¦ (^) Getting reliable data may take time ā¦ (^) Data must be correctly interpreted
Questionnaires (2) ļ½ Effective for acquiring subjective info quickly, cheaply, remotely from many people ļ½ Helpful for preparing better focused interviews (see next) ļ½ Subject to ... ā¦ (^) multiple biases: recipients, respondents, questions, answers ā¦ (^) unreliable info: misinterpretation of questions, of answers, inconsistent answers, ....
Questionnaires (3) Guidelines for questionnaire design and validation: ā¦ (^) Select a representative, statistically significant sample of people; provide motivation for responding ā¦ (^) Check coverage of questions, of possible answers ā¦ (^) Make sure questions, answers, formulations are unbiased & unambiguous ā¦ (^) Add implicitly redundant questions to detect inconsistent answers ā¦ (^) Have your questionnaire checked by a third party
16
17
Scenarios & storyboards ļ½
ā¦ (^) how things are running in the system- as-is ā¦ (^) how things should be running in the system- to-be
ā¦ (^) Snapshot = sentence, sketch, slide, picture, etc. ā¦ (^) Possibly structured with annotations: ļ¢ (^) WHO are the players, WHAT happens to them, WHY this happens, WHAT IF this does / does not happen, etc ā¦ (^) Passive mode (for validation): stakeholders are told the story ā¦ (^) Active mode (for joint exploration): stakeholders contribute
Scenarios ļ½ (^) Illustrate typical sequences of interaction among system components to meet an implicit objective ļ½ (^) Widely used for... ā¦ (^) explanation of system- as-is ā¦ (^) exploration of system- to-be + elicitation of further info ... e.g. WHY this interaction sequence? WHY among these components? ā¦ (^) specification of acceptance test cases ļ½ Represented by text or diagram
