1/23
Looks like no tags are added yet.
Name | Mastery | Learn | Test | Matching | Spaced |
|---|
No study sessions yet.
Systems Analysis & Design
Process of studying requirements, analyzing needs, and designing information systems.
Agile Development
Iterative, flexible approach to software development focused on collaboration and responding to change.
Functional Requirement
What the system must do (features, use cases).
Nonfunctional Requirement
Qualities of the system (performance, usability, security).
FURPS+
Framework for requirements (Functionality, Usability, Reliability, Performance, Security + design constraints).
Stakeholder
Anyone with interest in system success (users, managers, clients).
Activity Diagram
UML diagram that models workflow, decisions, and parallel processes.
Use Case
A goal an actor wants to achieve using the system.
Actor
External entity (user/system) that interacts with system.
Use Case Diagram
Diagram showing actors, system boundary, and use cases.
User Goal Technique
Identifying use cases by asking users what they want to achieve.
Event Decomposition Technique
Identifying use cases by analyzing external, temporal, and state events.
External Event
Triggered by outside actor.
Temporal Event
Triggered by time.
State Event
Triggered by system condition/state change.
Thing (Domain Class)
Object of interest in the problem domain (usually nouns).
Class
Definition of an object (with attributes and associations).
Object
Instance of a class.
Attribute
Data element describing a class.
Association
Relationship between two classes.
Multiplicity
Defines how many objects participate in relationship (1..*, 0..1, etc.).
Domain Model Class Diagram
UML diagram showing classes, attributes, associations, multiplicity.
Inheritance (Generalization/Specialization)
Subclasses share attributes/behaviors of superclass.
Whole-Part Relationship
Aggregation or composition relationship between objects.