- Usecases
- Constraints
-
Assumptions
-
Risks
- Goals
Functional requirements
- As a user, I want to do something
Non functional requirements
- Consistency - eventual consistency
- Security
- Persistency
- High Availability
- Latency - as low as possible
- Dependencies
- Connect with an existing system
- Conceptual View
- Input: business requirements, actors and systems
- Output: System Overview, High Level Class Diagram
- Methodologies: Modules - object oriented analysis
- Functional View
- Input: System Overview, Functional requirements
- Output: Usecase Diagrams
- Logical View
- Input: Dataset, Usecase Diagrams
- Output: Dataflow Diagram, Database Schema diagram
- Component View
- Network View
- Security View
...
- Conceptual View
FinanceData Component
- Funtional View
FinanceData Component - Import
- Logical View




















Template
1. Funtional
Design
2. Non-Funtional
3. Capacity
4. High Level
It should be interactions between components in system. No need to be specific, eg: database type
Notes