2. Making Decisions

This stage involves making decisions using the data gathered in the preliminary investigation

The first task is to develop one or more potential solutions to the problem. 

  • A computer system should be seen only as a tool that may offer the best solution to the problem. 
  • It is not the solution to every problem. 
  • Each potential solution is developed using the requirement report and the scope of the problem. 
    • The scope of the problem places constraints on the new system. 
    • A constraint is factor that affects the system and may prevent it from achieving its objectives
    • There are different types of constraints such as financial, technical, environmental and personal. 
      • For example, a financial constraint would be the amount of money an organisation is prepared to spend on the system. 

After establishing several potential solutions, 

  • the systems analyst seeks approval from the management of the organisation.
  • Management receives a brief written or verbal statement outlining the advantages and disadvantages of each solution. 
  • If the potential solutions are accepted, a feasibility study is carried out.



For Your Information:

The Concept of a System Constraint

All systems, whether open or closed, are limited (or constrained) in some way. Organizational systems are no exception. What, exactly, is a system constraint? It's some factor that limits what the system can achieve. Were it not for this limiting factor, the rest of the system might be able to achieve much more in realizing its goal. 

The limiting factor may be internal or external to the system. It may be a physical component, a condition, or an imposed policy of some kind. 
Whatever it is, however, it does frustrate efforts from within the system to achieve better performance.


A constraint is a restriction on the degree of freedom you have in providing a solution. Constraints are effectively global requirements, such as limited development resources or a decision by senior management that restricts the way you develop a system. Constraints can be economic, political, technical, or environmental and pertain to your project resources, schedule, target environment, or to the system itself. Figure 1 presents several potential constraints for the university system. Constraints are documented in a similar manner to business rules and technical requirements.

Figure 1. Constraints (summary form).

  • C24 The system will work on our existing technical infrastructure - no new technologies will be introduced.
  • C56 The system will only use the data contained in the existing corporate database.
  • C73 The system shall be available 99.99% of the time for any 24-hour period.
  • C76 All master's degree programs must include the development of a thesis.

http://agilemodeling.com/artifacts/constraint.htm