Speed + Availability + Response Time + Recovery Time (phrased as negative assertions)
Requirements are described by ______________.
Scenarios + Use Cases + User Stories
Represents persistent information tracked by the system (Application Domain Object): <>
Identify structure of the system (Class Diagram)
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
Reimplementation of legacy systems. Requirements triggered by new technology.
Definition of the system by a developer: semi-formal language (UML/SysML)
Requirements Elicitation + Analysis
User's view of the system: Functionality + UI + Error Handling + Environmental Conditions (Interfaces)
Provide services of existing system in new environment. Triggered by technology or new market needs.
Relationships of Inputs/Outputs + Response to irregular situations + Exact Sequence of operations
Set of acceptance criteria
Portability + Correctness + Security (phrased as negative assertions)
Identify functional requirements + deliver methods (Use Case Diagram)
Represents control tasks that have to be done by the system: <>
Sends informations between objects and has sender and receiver.
Identify new classes for the object model & supply operations (State & Sequence Diagrams)
Application Domain Analysis
Talking to Client
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
Definition of the system by a customer/user
Name three stereotypes.
Entity + Boundary + Control
Usability + Reliability + Performance + Supportability
Requirements Validation by checking ...
Correctness + Clarity + Completeness + Consistency + Realism + Traceability
Represents interaction between user and system: <>