L3 - Requirements Elicitation & Analysis Flashcards Preview

EIST (IN0006) > L3 - Requirements Elicitation & Analysis > Flashcards

Flashcards in L3 - Requirements Elicitation & Analysis Deck (28):
1

Performance Requirements

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

2

Requirements are described by ______________.

Scenarios + Use Cases + User Stories

3

Entity Stereotype

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

4

Object Modeling

Identify structure of the system (Class Diagram)

5

Scenarios

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

6

How can classes be identified?

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

7

Types Of Scenarios

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

8

Re-Engineering

Reimplementation of legacy systems. Requirements triggered by new technology.

9

Analysis

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

10

Requirements Engineering

Requirements Elicitation + Analysis

11

Requirements

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

12

Interface Engineering

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

13

Functionality

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

14

Milestones

Set of acceptance criteria

15

Quality Requirements

Portability + Correctness + Security (phrased as negative assertions)

16

Functional Modeling

Identify functional requirements + deliver methods (Use Case Diagram)

17

Control Stereotype

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

18

Event

Sends informations between objects and has sender and receiver.

19

Dynamic Modeling

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

20

Application Domain Analysis

Talking to Client

21

Greenfield Engineering

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

22

Stages Of Software Development

  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)

23

Model Organization possible by ...

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

24

Requirements Elicitation

Definition of the system by a customer/user

25

Name three stereotypes.

Entity + Boundary + Control

26

URPS

Usability + Reliability + Performance + Supportability

27

Requirements Validation by checking ...

Correctness + Clarity + Completeness + Consistency + Realism + Traceability

28

Boundary Stereotype

Represents interaction between user and system: <>