Unit 2 Flashcards

1
Q

Requirement engineering

A
  1. Inception
  2. Elicitation
  3. Elaboration
  4. Negotiation
  5. Specification
  6. Validation
  7. Management
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Req Eng definition

A
  • tasks and tech lead to understanding of requirements
  • start commu, through modelling
  • adaptive to needs of project, process, product and people
  • bridge bw design and construction
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Feasibility test

A
  • system, worthwhile or not
  • checks
    1. Contribution to org objective
    2. Computed using current tech
    3. Integrated with other sys
  • Info collection & report
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Elicitation requirements

A
  1. Collaborative requirements gathering
  2. Quality of function development
  3. User scenario’s
  4. Work products
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Probelms in elicitation

A
  1. Scope (boundaries undefined, unnecessary tech details)
  2. Understanding
  3. Volatility (changes)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Types of requirements in quality function development

A
  1. Normal
  2. Expected
  3. Excited
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Customer meeting has

A
  1. Info& function deployment
  2. Task deployment
  3. Value analysis
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Analysis model Elements

A
  1. Scenario based element
    -activity diagrams
  2. Class based element
    • objects into classes
    • eg: safe home sensors
  3. Behaviour element
    • Influence the design and it’s built
    • state diagram represents the behaviour of the state
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Requirement modelling for elaboration

A
  1. Scenario based
  2. Class oriented
  3. Behaviour and pattern based
  4. Data model
  5. Flow oriented models
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Objectives of requirements modelling

A
  1. System description
  2. Analysis model
  3. Design model
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Domain analysis IP OP

A

IP
Technical literature
Existing application
Expert advice
Customer survey
Current or future requirements

OP
Class taxation
Domain language
Reusable standards
Function models

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

SRS (software requirements specifications) format

A

Format:
1. Introduction
2. Information
3. Function description
4. Behavioral description
5. Validation criteria

How well did you know this?
1
Not at all
2
3
4
5
Perfectly