Term Paper: Systems Development Life Cycle

Pages: 5 (1403 words)  ·  Bibliography Sources: 1+  ·  Level: College Senior  ·  Topic: Education - Computers  ·  Buy This Paper


[. . .] Depending on the complexity of the system each subset of functions, or functions themselves are isolated and tested, as the development progresses the code is merged to create a multi-causal system of functions. This phase offers coders and developers the opportunity to test the functions they have created through code, to compare them to the functions the users, involved in the planning phase have deemed important and to check the overall functionality of the theory of the designs. The designers and creators of the project have the opportunity at this point to write code and rewrite code to better fit their idea of the needs of the system or workforce or both, ideally. Then in the old models near the end of this phase the designers implement the old system by allowing users to apply it for the first time. Remember after describing to the designer the needs of the system this is one of the first places where actual users come into contact with the system and its set of tasks. Some newer Lifecycle models separate the designer testing phase with the user implementation phase and attempt to allow users more access to other parts of the process through consultative work and input on updates of the phase, sort of a potential debugging of the system before it is implemented. (Kliem & Ludin, 1994, p. 12)


Thought by many to be the most important but least desired stage of growth for the developers, the maintenance stage is where the system is in full functionality and the debugging that was not alleviated during implementation begins. It is also during this phase that the system can be expanded upon as more features create a better sense of completed task ability. Security features that may not have been foreseen are added as users begin to understand the strengths and weaknesses of the system. Also during this phase the ease of use issue is brought up as real users begin to interact with the system to perform the functions for which it was intended, and fine tuning occurs.


In conclusion Systems Development Life Cycle is a multi-phase linear system for the development and implementation of new programs and processes in information technology. Within the system the work of each completed phase becomes the crucial needed information for the beginning and completion of the next phase.

Though design teams and organizations have made many attempts to refine the SDLC to meet the particular needs of the organization there have been many recent opponents of its use. One of the biggest complaints about the system is its linear nature, as the time it takes to offer investors and users a completed system can be seen as to great. There are more current multiphase systems development designs that allow more user interaction during each phase, allowing for a more ergonomic outcome. (Kliem & Ludin, 1994, p. 7)

In the past systems created by these means were effective in the implementation of automating existing manual tasks and new tasks yet the complexity of more modern systems requires a greater knowledge of user input and the speed at which information technology develops requires a more spiral timeline where different phases of development and implementation can be done simultaneously and with greater attention to the needs of the user.

One more modern theorist even describes the SDLC as archaic and says this of it:

The archaic paradigm made very little distinction between needs (what one had to have, or requirements) and wants (what one would like to have, or desires). Every requirement and specification, no matter how small, simple, trivial, or important, could not wait. "Everything" was considered top priority. That translated into delaying systems development projects and resulted in maintenance nightmares.

(Kliem & Ludin, 1994, p. 7)

In the present and future the refining of systems development will no doubt occur and the user will be more active in development, as well as the development will take less time and possibly develop less snags in the road along the way.



Kliem, R.L., & Ludin, I.S. (1994). Just-In-Time Systems for Computing Environments. Westport, CT: Quorum Books. [END OF PREVIEW]

Four Different Ordering Options:

Which Option Should I Choose?

1.  Buy the full, 5-page paper:  $28.88


2.  Buy + remove from all search engines
(Google, Yahoo, Bing) for 30 days:  $38.88


3.  Access all 175,000+ papers:  $41.97/mo

(Already a member?  Click to download the paper!)


4.  Let us write a NEW paper for you!

Ask Us to Write a New Paper
Most popular!

Utilizing Telecommunications Networks Essay

System Development Art or Science Term Paper

Work-Related Project Using Systems Analysis SDLC Term Paper

Product Life Cycle of SAP Essay

System Analyst Thesis

View 1,000+ other related papers  >>

Cite This Term Paper:

APA Format

Systems Development Life Cycle.  (2004, July 18).  Retrieved June 17, 2019, from https://www.essaytown.com/subjects/paper/systems-development-life-cycle/6092486

MLA Format

"Systems Development Life Cycle."  18 July 2004.  Web.  17 June 2019. <https://www.essaytown.com/subjects/paper/systems-development-life-cycle/6092486>.

Chicago Format

"Systems Development Life Cycle."  Essaytown.com.  July 18, 2004.  Accessed June 17, 2019.