Describe The Characteristics Of Solution And How They Meet Business Requirements

Solution requirements
Solution requirements describe the characteristics of a solution and how they meet business requirements and stakeholder requirements. They are frequently divided into sub-categories, particularly when the requirements describe a software solution. Solution requirements are composed of functional requirements and non-functional requirements. Functional requirements describe the behavior and information that the solution will manage. They describe capabilities the system will be able to perform in terms of behaviors or operations, specific information technology application actions or responses. In summary, a functional requirement describes the things the product must do. Non-functional requirements are capture conditions

It serves to make the software or system development more clearly and to make it manageable in complexity. There is a wide selection of different process models, which differ in certain aspects and content, depending on the project, various advantages and disadvantages. However, all process models have four fundamental process activities. These processes are specification, development, validation and evolution (Sommerville, 2007, pp. 34–35). In the specification phase, customers and developers define the system together. This is designed and programmed in the development phase and followed by the validation phase in which the whole system is checked whether it has the functionality that is desired by the customer. Evolution is the last process and describes the maintenance and development enhancements of the system. In all of these phases requirements play an important role. The phases mentioned above are considered in the various process models. Before a software project is started, the appropriate process models for the project must be selected. The proper selection and application of the process model is a major factor for the success of the project. Examples of typical process models are the waterfall model, V-model, agile methods