## 3 Proposed Framework
### Integrated Prioritization Module (IPM)
#### 3.2.3 AHP Processing Unit (APU)  
The APU is preset in the GPU Final Group. This unit is purely based on AHP. AHP is preferred because it is a reliable technique that meets many requirements. The number of requirements covered by our proposed model is up to 50. The APU will work on a FIFO basis if the requirement exceeds 100. It will process and manage only 48 requirements at one time. It is an iterative and incremental model. The simple aim of the APU is to allocate a proper priority to every specific REQ listed in the groups. This will overcome the misperceptions associated with the question of which REQ to execute first. The outcome of the APU will be the final outcome, including the list of prioritized REQs. The result of the APU will be required to be accurate and have actual priority so it can be executed to develop and design the application without any misunderstandings. The algorithm of the proposed framework is as follows:  
1. The initial requirements are stored in a repository. * This should be explored as three keywords: for instance, Requirement/Need/Feature; * This should be distinct in three words: Object/Action/Result.
2. A specific requirement is not entered again, but its value/importance is incremented by one if the requirement already exists in the repository. * It is just added to the repository if it is not already present in the repository.
3. The requirements listed in the repository are argued based on the win-win pattern.
4. Additional requirements coming at run-time during the design process are added to the repository using step 2.
5. Primarily, 40-48 maximum requirements (12 requirements in the four different groups) should be adequately defined and then sent to the prioritization process from the repository. These requirements are initially moved to the GPU. The 12-requirement set is demonstrated in a 12 \(\times\) 12 table (matrix) in such a form that it denotes the distinctive pairs. This matrix represents 12 requirements per group. Four groups will entertain 48 requirements at the same time.  
Requirements are manually prioritized in the GPU based on the significance of the practicality of execution/designing it and the availability of resources.
* The manual process is used because the elicitation of requirements is a manual method.
* The requirements are categorized into four groups: Preliminary, Group 2, Group 3, and Final.
* Afterwards, the domain expert (such as a programmer/developer) inspects all the requirements regarding feasibility and importance.
* The problems concerning grouping and categorization are resolved in this step;
* The misplaced requirements are moved to their correct place.
* The APU is fixed in the most serious group, which scans serious and important requirements and sorts only the important requirements, with respect to the importance, cost, and risk associated with every requirement in this group.
* The prioritized (sorted) requirements are then moved for development and execution.
* The requirements from the Preliminary Group are extracted to Group 2, Group 2 to Group 3, and Group 3 to the Final Group at particular intervals to avoid severe issues, such as the danger of starvation.
* If two or more than 2 REQs have equal priorities once the APU prioritization process is complete
* The REQs are moved for execution and development using the FIFO approach.