L3 - Requirements Elicitation & Analysis

Question 1

Performance Requirements

Answer 1

Speed + Availability + Response Time + Recovery Time (phrased as negative assertions)

Question 2

Requirements are described by ______________.

Answer 2

Scenarios + Use Cases + User Stories

Question 3

Entity Stereotype

Answer 3

Represents persistent information tracked by the system (Application Domain Object): <>

Question 4

Object Modeling

Answer 4

Identify structure of the system (Class Diagram)

Question 5

Scenarios

Answer 5

Concrete and focused informal descriptions of a feature that is used by an actor.

Question 6

How can classes be identified?

Answer 6

Application Domain Analysis + Intuition + Textual Analysis + Activities in State Chart Diagrams + Activity Lines in Sequence Diagrams

Question 7

Types Of Scenarios

Answer 7

As-Is Scenario + Visionary Scenario + Evaluation Scenario + Training Scenario

Question 8

Re-Engineering

Answer 8

Reimplementation of legacy systems. Requirements triggered by new technology.

Question 9

Analysis

Answer 9

Definition of the system by a developer: semi-formal language (UML/SysML)

Question 10

Requirements Engineering

Answer 10

Requirements Elicitation + Analysis

Question 11

Requirements

Answer 11

User’s view of the system: Functionality + UI + Error Handling + Environmental Conditions (Interfaces)

Question 12

Interface Engineering

Answer 12

Provide services of existing system in new environment. Triggered by technology or new market needs.

Question 13

Functionality

Answer 13

Relationships of Inputs/Outputs + Response to irregular situations + Exact Sequence of operations

Question 14

Milestones

Answer 14

Set of acceptance criteria

Question 15

Quality Requirements

Answer 15

Portability + Correctness + Security (phrased as negative assertions)

Question 16

Functional Modeling

Answer 16

Identify functional requirements + deliver methods (Use Case Diagram)

Question 17

Control Stereotype

Answer 17

Represents control tasks that have to be done by the system: <>

Question 18

Event

Answer 18

Sends informations between objects and has sender and receiver.

Question 19

Dynamic Modeling

Answer 19

Identify new classes for the object model & supply operations (State & Sequence Diagrams)

Question 20

Application Domain Analysis

Answer 20

Talking to Client

Question 21

Greenfield Engineering

Answer 21

Developing from scratch with no prior system. Requirements from Client/User. Triggered by their needs.

Question 22

Stages Of Software Development

Answer 22

1. Requirements Elicitation (AD)
2. Analysis (AD)
3. System Design (SD)
4. Object Design (SD)
5. Implementation (SD)
6. Testing (SD)
7. Delivery (AD)
8. Maintenance (AD)

Question 23

Model Organization possible by …

Answer 23

System Hierarchy + System Model + Domain + Stakeholders + View Points

Question 24

Requirements Elicitation

Answer 24

Definition of the system by a customer/user

Question 25

Name three stereotypes.

Answer 25

Entity + Boundary + Control

Question 26

URPS

Answer 26

Usability + Reliability + Performance + Supportability

Question 27

Requirements Validation by checking …

Answer 27

Correctness + Clarity + Completeness + Consistency + Realism + Traceability

Question 28

Boundary Stereotype

Answer 28

Represents interaction between user and system: <>