SOFTWARE REQUIREMENTS

SOFTWARE REQUIREMENTS

1. 1.Requirements Discovery

   • Gathering and understanding the requirements is a difficult process
   • That’s because stakeholders may not know what exactly they want the software to do, or they may give un-realistic requirements.
   • It can be done using some techniques, like interviews, scenarios, prototypes, etc,

2. 2. Requirements classification and organization

   • It’s very important to organize the overall structure of the system.
   • Putting related requirements together, and decomposing the system into sub components of related requirements. Then, we define the relationship between these components.
   • What we do here will help us in the decision of identifying the most suitable architectural design patterns.

3. 3. Requirements prioritization and negotiation

   • Prioritizing your requirements will help you later to focus on the essentials and core features of the system, so you can meet the user expectations. It can be achieved by giving every piece of function a priority level. So, functions with higher priorities need higher attention and focus.
   • We shouldn’t reach a situation where a stakeholder is not satisfied because his requirements is not taken into consideration
   • This activity is concerned with prioritizing requirements and finding and resolving requirements conflicts through negotiations until you reach a situation where some of the stakeholders can compromise.
   • One of the reasons is the conflicts that may arise as a result of having different stakeholders involved.

4. 4.Requirements Spefification

   • System Requirements
     • The system requirements on the other hand are expanded version of the user requirements that are used by software engineers as the starting point forthe system design.
   • Ways of Writing Requirements Specification
     • there are different ways to specify the requirements. The most two common ways are the natural and structured languages.