Whether a company is a startup or an established corporation, having an acquisition plan is essential. It develops the acquisition framework that directs stakeholders in making decisions and establishing milestones. Such a program also clarifies its objectives and examines high-level technical requirements as well as other requirements related to acquisition criteria. Only with the aid of an acquisition strategy can stakeholders assess the costs, timelines, and risks associated with a certain choice (Cohen, Dori, & de Haan, 2010). The interests of the firm and its stakeholders must be taken into account while creating an acquisition plan, which must be comprehensive, realistic, and inclusive. This research tries to create a high-level framework that incorporates these rules and this paper aims to develop a high-level Information Technology (IT) Systems Acquisition Plan. The model embraces the Systems Development Life Cycle (SDLC) approach, which details the steps of the process and the roles and responsibility of every stakeholder in each phase.
Description and Justification of the SDLC System Design and Development
The System Development Life Cycle (SDLC) synonymous as Application Development Life-Cycle (ADLC) is a phrase used to explain the procedure of planning, building, experimenting, and implementing information systems. The SDLC concept is compatible with a broad array of software and hardware configurations since a system can be composed of strictly hardware or software or a combination of both. Business analysts and IT experts acknowledge the System Development Life Cycle (SDLC) as a roadmap that allows users to convert a newly-developed project into a functional one. Numerous people attest to the fact that the SDLC approach offers a model for technical and non-technical actions that establish an efficient IT system that satisfies or exceeds the expectations of a business and its stakeholders. Also, The SDLC approach helps stakeholders in the decision-making processes.
A Summary of the Steps in the SDLC System Acquisition Process
In the past, the System Development Life Cycle (SDLC) model comprised of five phases that experts have now increased to seven. System analysts opine that increasing the number of steps from five to seven clarified the particular actions and goals imperative for a successful system acquisition plan (Leau et al., 2012). Developers and users fathom the type of activities involved in every phase. Additionally, the multiple steps notify stakeholders that each stage can be repeated at any time in case there is a need to modify or enhance the system. Overall, the System Development Life Cycle integrates seven steps.
Planning
Also famous as the initiation phase, the goal of this first step is to establish the extent of the problem and establish solutions. The most important factors of consideration include benefits, time, costs, and resources. Overall, in this stage of systems acquisition, stakeholders examine whether there exists a real need for systems.
System Analysis & Requirements
In the second phase of SDLC, stakeholders examine the functional requirements of the proposed solution. In most cases, after problem identification, team members submit multiple possible solutions and pick the best. In tandem with acquiring a new IT system, the team explores the functions of the ideal equipment. Stakeholders conduct a thorough system analysis at this stage. They analyze whether the system is user-friendly and whether it meets the needs of end-users. Businesses can use the following tools in this second phase of system acquisition: Computer Aided System/ Software Engineering (CASE), Requirements gathering, and structured analysis.
System Design
Once the ideal solution is identified, the third step details the appropriate specifications, features, and operations that meet the functional needs of the projected system. In this stage, end users discuss and decide the exact business information needs that they would want the new IT system to address. More specifically, in this phase, users analyze the critical software and hardware components, structure, and procedures needed for the system to accomplish its goals.
Development
Admittedly, the real system acquisition starts in the fourth stage as it marks the tail end of the selection section and the start of production. Primary features of this phase are installation and change. During this period, the IT system developer, network engineer, or programmer is invited to execute the most critical part of the system acquisition. The expert may use flow charts to ensure that every process of the system meets expectations. It is advisable to focus on user training during the development phase.
Integration and Testing
Naturally, after the development of the IT system, integration and trials follow. In most cases, a Quality Assurance (QA) expert analyzes the programs and procedures to establish whether the system meets the expected businesses' and personnel's goals. To ensure accuracy, QA professionals repeatedly test for errors, interoperability, and bugs in the new IT system. The experts repeat the testing activities until the end-user is satisfied that the system appropriately meets needs. Later in this phase, the profession conducts validation and verification, both which contribute to a successful completion.
Implementation
In the process of systems acquisition, program coding occurs during the sixth phase. Notably, this step marks the actual setting up of the newly-established system as the stakeholders use a direct cutover to move data from the old to the new system. Given the sensitivity and complexity of data transfer, it is advised to start an immediate cutover at off-peak hours. At this stage, end-users and system experts should affirm the project performs as it should.
Operations and Maintenance
The final phase of the SDLC system acquisition approach entails operations and maintenance. As users get acquainted with the new IT system, they can fine-tune it to fit their preferences, enhance performance, and add unique abilities. Also, the stage encompasses long-term activities that focus on keeping the system in good condition for a long time.
Overview of Participants
Although all stakeholders should be equally involved in all phases of the System Development Life Cycle (SDLC), some steps require the attention of specific personnel (Highsmith,2013). In the first period, the primary participants are the managers and other stakeholders who explore the enterprise's and personnel's needs. During brainstorming, the participants may aim to understand why production is the company is low and what should be done to solve the problem. In the second phase, the participation of all stakeholders continues as they submit possible solutions to the problem. People in the problematic department should participate more than others since they know the issues better and are likely to identify feasible solutions. In the third phase, the system design, end-users discuss and agree on the specific needs that the new system should address. At this stage, the end-users consider the primary components of the IT system such as hardware, software, structure, and procedures. The actual work starts in the fourth step where programmers, database developers, network engineers among other experts manufacture a seamless system. In the fifth phase of integration and testing, Quality Assurance (QA) experts examine whether the new system performs as expected (Highsmith,2013). The QA experts tests for interoperability, bugs, and errors. During implementation, the sixth phase, code programmers are the primary participants as they are the system installers. Programmers help transfer data from old to new system. The final stage of operations and maintenance involves all stakeholders since it is a moral obligation of every person to take care of resources. Nonetheless, the maintenance phase dramatically involves end-users and IT experts who resolve arising problems.
References
Cohen, S., Dori, D., & de Haan, U. (2010). A software system development life cycle model for improved stakeholders’ communication and collaboration. International Journal of Computers Communications & Control, 5(1), 20-41.
Highsmith, J. (2013). Adaptive software development: a collaborative approach to managing complex systems. Addison-Wesley.
Leau, Y. B., Loo, W. K., Tham, W. Y., & Tan, S. F. (2012). Software development life cycle AGILE vs traditional approaches. In International Conference on Information and Network TechnologyVol. 37, No. 1, pp. 162-167.
