SOFTWARE DEVELOPMENT

Prioritizing Requirement in Software Development

[Author Name]

[Student Number]

Prioritizing requirement in software development

Introduction

Many of the researchers have done adequate amount of research on prioritizing requirement in software development and have identified various problems that lead to the implementation of prioritizing requirement in software development. Majority of the projects which suffer failures is only because the requirements were not elicited and analyzed before the starting of the project. Whenever a project is initiated it has to go through various stages of processes which are often critical and require utmost attention and time. Managing these priorities is the major problem which is solved through the implementation of prioritizing requirements.

Discussion

According to Frank (2002), prioritizing requirements helps in discussing and rating candidate requirements. The activity of prioritizing requirements in system development project is done during the requirement phase of engineering. The systems that being developed for current market designed in such a way that they are quick in responding to the market condition, bound by strict budget constraints and produced in modern versions. The collection of requirements is a part of requirements management in the system development process and part of the business analysis. The aim is to make the requirements of the client to be developed in the system to determine. At present, there are many processes of development of software in existence (Donald, 2004, pp. 36).

Frank (2002) has reported the fundamental requirement of prioritization process. According to the researcher, the prioritization should be in such a way that it does not include any biasness towards the stakeholders of the project (Frank, 2002, pp. 4-6). The process of prioritization should cater all the requirements of the project, if that is not possible then the process of prioritization do not exist. Lack of definition of the corporate and project objectives, power requirements, lack of user involvement and uncoordinated changes in the course of the project are key reasons for project failure (Sebastian, 2005, pp. 26). The prioritization process should support the evolution of the requirements into appropriate specifications for the system.

Requirements need only be complete, accurate, consistent, testable, of course, necessary to clear and enforceable. The art of successful requirements management, however, is to get the company's goals with the budget, the stakeholders, the interfaces, the functional requirements and the available time under one roof. Requirements Management is a customer-oriented approach, the needs of customers and their own management to capture, provide ...