OOPT(Object-Oriented Process with Traceability)
- A software development process based on RUP
Stage
- Stage 1000 : Plan
Planning, defining requirements, building prototyping, etc
Corresponding to Incpetion phase in the RUP - Stage 2000 : Build
Elaboration and Construction of the system
Corresponding to Elaboration/Construct phase in the RUP - Stage 3000 : Deployment
Implementation of the system into use
Corresponding to Transition phase in the RUP
1001. Define A Draft Plan
- Write a draft plan for schedule, resources, budget, objective, etc
- Input : all related documents of previous similar projects
- Output : a draft project plan
1002. Create Preliminary Investigation Report
- Write a requirement specification for a product
- Input : draft project paln, invetigation report
- Output : a requirement specification
1003. Define Requirements
- Write a draft plan for schedule, resources, budget, objective, etc
- Input : all related documents of previous similar projects
- Output : a draft project plan
- Write a draft plan for schedule, resources, budget, objective, etc
- Input : all related documents of previous similar projects
- Output : a draft project plan
- What is a requirement
- A condition or capability needed by a user to solve a problem or achieve an objective.
- A condition or capability that must be met or possessed by a system or system component to satisfy a contract, standard, specification, or other formally imposed documents.
- A documented rerepresentation of a condition or capabilities as in (1) or (2) - Functional requirements
- A requirement that specifies a function that a system or system compnent must be able to perform
- Analyzed and Realized in Use-Case model, later - Non-functional requirements
- Constraints on the services or functions offered by the system as timing constraints, constraints on the development process, standards, etc.
- Portability, Reliability, Usability, Efficiency
- Delivery, Implementation, Startdards
- Ethical, Interoperability, Legislative
'Computer Science' 카테고리의 다른 글
Object-Oriented Analysis Design (6) (0) | 2021.07.27 |
---|---|
Object-Oriented Analysis Design (5) 2030. Analyze (0) | 2021.07.27 |
Object-Oriented Analysis Design (3) (0) | 2021.07.26 |
Object-Oriented Analysis Design (2) (0) | 2021.07.26 |
Object-Oriented Analysis Design (1) (0) | 2021.07.26 |
댓글