Still in the topic of Object Oriented Analysis Design (ADBO), but the topics I discuss is regarding Requirements Management. Requirements management is a systematic approach to obtaining, organizing, documenting and managing changes in application Requirements management software to ensure that software developers will solve the right problems and building the right system as well.
Aspects contained in the Management Requirements includes the following:
1. Problems Analytics. Finding problems for a solution found to these problems. This is an early stage in the Management Needs.
2. Understanding user needs. This can be done through questionnaires and jump directly to find information about the needs of users who will use the system later.
3. Defining the system. Once a problem is found and the data needs of the user already exists, then we determine what kind of system will be created.
4. Set the scope. Determine the scale of the system to be created. Include who the users, system usability later.
5. Refining the system definition. Add or correct the data for manufacturing systems.
6. Build the system. Implementation stage or making the system significantly.
Destination Management Requirements:
Behavior of the system is an explanation of how the system works. This behavior is an activity that can be viewed from the outside and can be tested. This system behavior can be described by Use Case Diagrams, Use Case describes the system in which, the system environment as well as their relationship.
The following is a brief description of the earlier Requirement Management on Information System. If there are errors or omissions please be corrected or added. May be useful.
Aspects contained in the Management Requirements includes the following:
1. Problems Analytics. Finding problems for a solution found to these problems. This is an early stage in the Management Needs.
2. Understanding user needs. This can be done through questionnaires and jump directly to find information about the needs of users who will use the system later.
3. Defining the system. Once a problem is found and the data needs of the user already exists, then we determine what kind of system will be created.
4. Set the scope. Determine the scale of the system to be created. Include who the users, system usability later.
5. Refining the system definition. Add or correct the data for manufacturing systems.
6. Build the system. Implementation stage or making the system significantly.
Destination Management Requirements:
- Establish and maintain agreements with users and other stakeholders about the ability of the system that can be done.
- Providing insight to system developers about the needs of the system are made
- Define system boundaries
- Provide basic technical planning
- Provide cost estimates for system development time
- Create a view (user interface) system
Behavior of the system is an explanation of how the system works. This behavior is an activity that can be viewed from the outside and can be tested. This system behavior can be described by Use Case Diagrams, Use Case describes the system in which, the system environment as well as their relationship.
The following is a brief description of the earlier Requirement Management on Information System. If there are errors or omissions please be corrected or added. May be useful.
0 komentar
Posting Komentar