5 research outputs found

    The requirements management practices: A study at UUM IT

    Get PDF
    Requirements engineering is a main process in software engineering that focusing on development and managing the user requirements. One of the requirements engineering activities is requirements management. It plays an important role when it comes to the support of product development teams. Despite this, there is a lack of practice in requirements management activity in the software project development. Malaysian software markets are still facing several problems in requirements management practices such as requirements quality, requirements inadequately, and identification of requirements; with limited studies that address it. In this study, UUM IT as computer services provider in a local universities in Malaysia is design as case study, to represent as one organization in Malaysia software markets. This study aims to investigate the current situation for the requirement management in UUM IT, and assess the relationship CMMI level 2 with the requirements management practices in UUM IT. This study adopted mixed method through used questionnaire with the UUM IT team, as well as, interviews with managers of UUM IT for more reliability. The outcome of study showed that the UUM IT are used requirements management activities but there is a need for more attention and improve. Moreover, the study proposes CMMI appraisal method to enhance the performance of software development tea

    Enhancing Requirements Change Request Categorization and Prioritization in Agile Software Development Using Analytic Hierarchy Process (AHP)

    Get PDF
    Software development now relies heavily on agile methods, which call for the efficient administration and prioritization of change requests. In order to improve requirement prioritization using the Analytic Hierarchy Process (AHP) in Agile methods, this study article presents a new framework for classifying software requirements into Small Change Requests (SCRs) and Large Change Requests (LCRs). The paper examines the difficulties associated with requirement prioritization and categorization in Agile settings and offers a methodical system for dividing change requests into categories based on complexity, impact, and timeline. In order to provide a thorough grasp of the project scope and objectives, the framework considers both functional and non-functional needs. A case study containing several Agile software development projects is used to evaluate the performance of the suggested categorization and prioritization model. According to the findings, the combination of SCR and LCR categorization with AHP enables more effective teamwork and greater matching of development goals with partner objectives. The research also shows that the suggested framework's integration into the Agile development process results in a more efficient decision-making process, less time wasted on talks, and improved resource distribution. The model aids in risk mitigation by allowing a methodical and quantifiable approach to requirement prioritization. These risks are related to quick changes in project scope and changing client requirements. By presenting a fresh framework for requirement categorization and prioritization, this study adds to the current discussion on successful requirement management in Agile methods. Agile software development projects become more effective and adaptable overall thanks to the incorporation of AHP, which guarantees a more methodical and objective prioritization process. This study has the potential to greatly improve the administration of shifting needs and user expectations in Agile settings by offering a structured method to classify and rank change requests
    corecore