REQUIREMENTS AND RISK

Requirements and Risk



Acquisition - Requirements and Risk

Introduction

The acquisition of software today is one of the main strategies adopted by organizations. In relation to Information Technology (IT), the failure rates of software acquisition projects that are carried out are above 50 %. This failure is closely related to the failures in the management of software acquisition projects, or lack of it (over 60 %). Proper management of project risks is a key process to attack the causes of failure mentioned. A second cause of failure is the complexity of standards and management models that hampers their implementation projects, particularly in very small environments, which require frames and working guidelines that indicate how to carry out the project management process.

Discussion

Within this general framework, this thesis aims to define a methodology for risk management, proper for the acquisition of software, which allows specially for small environments, reducing the problems that affect the success of a project software acquisition. (McConnell, 2000)

Statement of Need

The statement of need is an important document prepared to get things straight and to have a proper plan according to which the whole process is run and checked against.

Translate Problem into a Need Statement

The acquisition of a proprietary database program to integrate into organization encompassing al the requirements and risk.

The basic problem lies in the fact that proprietary database programs are complex software that need to b3e properly evaluated in order before they can be implemented for an origination.

The basic changes and outcomes depend on the effectiveness of the program and its relation with the organizational structure and processes. The basic requirements have to be determined in order to make the software effective and the possible risks involved with its implementation be known.

Verify the Accuracy of the Need Statement against the Problem

Primary Research is attributed to do federal agency that is directly involved in the act and is evaluating the risks and requirements for the proprietary database program acquisition.

Networking is also an essential aspect of many organizations which is certainly kept well under consideration to accommodate the importance of networking for the proprietary database program being acquired.

Careful evaluation of all the written programs and modules has to be made to ensure successful implementation and execution of the proprietary database program. (King, Slotegraaf & Kesner, 2008)

Validate that the Scope of the Need Is Appropriate

The statement of need has to be clear and concise to reflect the scope of appropriateness of the program acquisition required in the proprietary database program.

It should be ensured that the need statement is not too over generalized in the context that it does not specifically address the problem and issue being resolved.

Innovators have to observe and gather information from secondary research in order to come up with the best possible proprietary database program acquisition to ensure that the required execution is met. (King, Dalton, Daily & Covin, 2004)

Acquisition System

An Acquisition system encompasses the functions, processes, and activities that Federal agencies use to acquire products and services. Figure 1 (on the next page) depicts the basic ...