Question

Prepare a memo to management recommending data storage, input and output devices, networking equipment, and how the Systems Development Life Cycle (SDLC) can be used to analyze, plan, and document systems changes.

Answer 1

Answer:-

There is a lot of literature on specific systems development life cycle (SDLC) methodologies, tools, and applications for successful system deployment. Not just limited to purely technical activities, SDLC involves process and procedure development, change management, identifying user experiences, policy/procedure development, user impact, and proper security procedures. Books such as David Avison and Guy Fitzgerald’s Information Systems Development and Alan Daniels and Don Yeates’ Basic Systems Analysis, delve into the intricacies of information systems development lifecycles.
This article will provide an in-depth analysis of the history, definition, phases, benefits, and disadvantages, along with solutions that support the system development life cycle.

In order to understand the concept of system development life cycle, we must first define a system. A system is any information technology component - hardware, software, or a combination of the two. Each system goes through a development life cycle from initial planning through to disposition. Some methodologies provide the necessary framework to guide the challenging and complex process with an aim to avoid costly mistakes and expedite development, all of which have the same goal of moving physical or software-based systems through phases.

A system development life cycle is similar to a project life cycle. In fact, in many cases, SDLC is considered a phased project model that defines the organizational, personnel, policy, and budgeting constraints of a large scale systems project. The term “project” implies that there is a beginning and an end to the cycle and the methods inherent in a systems development life cycle strategy provide clear, distinct, and defined phases of work in the elements of planning, designing, testing, deploying, and maintaining information systems.

Those involved in the SDLC include the c-suite executives, but it is the project/program managers, software and systems engineers, users, and the development team who handle the multi-layered process. Each project has its own level of complexity in planning and execution, and often within an organization, project managers employ numerous SDLC methods. Even when an enterprise utilizes the same methods, different project tools and techniques can differ dramatically.

A System (or Software) Development Lifecycle (SDLC) is useful for managing a planned and controlled development effort. The biggest advantages are that it provides some level of control of the development process to ensure that the ultimate solution is consistent with the original requirements and to ensure that the design process and testing process leading to release of a solution is sound and well-managed. It also has the advantage that it is a repeatable process. If you develop something with a given SDLC and a similar project comes along, you should be able to use the same process with some level of confidence of success.

The biggest disadvantages of an SDLC are that it does not work well in an environment where there is some level of uncertainty and it can also create a lot of unnecessary bureaucracy and overhead. It is designed around a situation that emphasizes planning and control and it isn’t well-designed to encourage creativity and innovation as the project is in progress. For those reasons, many projects are moving to a more Agile and adaptive incremental development process approach rather than a sequential SDLC.