L3 - Requirements Elicitation & Analysis Flashcards
Performance Requirements
Speed + Availability + Response Time + Recovery Time (phrased as negative assertions)
Requirements are described by ______________.
Scenarios + Use Cases + User Stories
Entity Stereotype
Represents persistent information tracked by the system (Application Domain Object): <>
Object Modeling
Identify structure of the system (Class Diagram)
Scenarios
Concrete and focused informal descriptions of a feature that is used by an actor.
How can classes be identified?
Application Domain Analysis + Intuition + Textual Analysis + Activities in State Chart Diagrams + Activity Lines in Sequence Diagrams
Types Of Scenarios
As-Is Scenario + Visionary Scenario + Evaluation Scenario + Training Scenario
Re-Engineering
Reimplementation of legacy systems. Requirements triggered by new technology.
Analysis
Definition of the system by a developer: semi-formal language (UML/SysML)
Requirements Engineering
Requirements Elicitation + Analysis
Requirements
User’s view of the system: Functionality + UI + Error Handling + Environmental Conditions (Interfaces)
Interface Engineering
Provide services of existing system in new environment. Triggered by technology or new market needs.
Functionality
Relationships of Inputs/Outputs + Response to irregular situations + Exact Sequence of operations
Milestones
Set of acceptance criteria
Quality Requirements
Portability + Correctness + Security (phrased as negative assertions)
Functional Modeling
Identify functional requirements + deliver methods (Use Case Diagram)
Control Stereotype
Represents control tasks that have to be done by the system: <>
Event
Sends informations between objects and has sender and receiver.
Dynamic Modeling
Identify new classes for the object model & supply operations (State & Sequence Diagrams)
Application Domain Analysis
Talking to Client
Greenfield Engineering
Developing from scratch with no prior system. Requirements from Client/User. Triggered by their needs.
Stages Of Software Development
- Requirements Elicitation (AD)
- Analysis (AD)
- System Design (SD)
- Object Design (SD)
- Implementation (SD)
- Testing (SD)
- Delivery (AD)
- Maintenance (AD)
Model Organization possible by …
System Hierarchy + System Model + Domain + Stakeholders + View Points
Requirements Elicitation
Definition of the system by a customer/user
Name three stereotypes.
Entity + Boundary + Control
URPS
Usability + Reliability + Performance + Supportability
Requirements Validation by checking …
Correctness + Clarity + Completeness + Consistency + Realism + Traceability
Boundary Stereotype
Represents interaction between user and system: <>
