This work is licensed under a Creative Commons Attribution 3.
This work is licensed under a Creative Commons Attribution 3. Please contact mpub-help umich. Abstract The systems development life cycle SDLCwhile undergoing numerous changes to its name and related components over the years, has remained a steadfast and reliable approach to software development.
Although there is some debate as to the appropriate number of steps, and the naming conventions thereof, nonetheless it is a tried-and-true methodology that has withstood the test of time.
This paper discusses the application of the SDLC in a 21st century health care environment. Specifically, it was utilized for the procurement of a software package designed particularly for the Home Health component of a regional hospital care facility.
We found that the methodology is still as useful today as it ever was. By following the stages of the SDLC, an effective software product was identified, selected, and implemented in a real-world environment. Lessons learned from the project, and implications for practice, research, and pedagogy, are offered.
Insights from this study can be applied as a pedagogical tool in a variety of classroom environments and curricula including, but not limited to, the systems analysis and design course as well as the core information systems IS class.
It can also be used as a case study in an upper-division or graduate course describing the implementation of the SDLC in practice. While it has evolved over the years in response to ever-changing scenarios and paradigm shifts pertaining to the building or acquiring of software, its central tenants are as applicable today as they ever were.
Life-cycle stages have gone through iterations of different names and number of steps, but at the core the SDLC is resilient in its tried-and-true deployment in business, industry, and government.
In fact, the SDLC has been called one of the two dominant systems development methodologies today, along with prototyping Piccoli, Thus, learning about the SDLC remains important to the students of today as well as tomorrow.
This paper describes the use of the SDLC in a real-world heath care setting involving a principle component of a regional hospital care facility. The paper can be used as a pedagogical tool in a systems analysis and design course, or in an upper-division or graduate course as a case study of the implementation of the SDLC in practice.
First, a review of the SDLC is provided, followed by a description of the case study environment.
Next, the application of the methodology is described in detail. Following, inferences and observations from the project are presented, along with lessons learned.
Finally, the paper concludes with implications for the three areas of research, practice, and pedagogy, as well as suggestions for future research.
While such classes offer an overview of many different means of developing or acquiring software e. As this paper will show, following the steps and stages of the methodology is still a valid method of insuring the successful deployment of software.
While the SDLC, and systems analysis and design in general, has evolved over the years, at its heart it remains a robust methodology for developing software and systems.
Early treatises of the SDLC promoted the rigorous delineation of necessary steps to follow for any kind of software project. The Waterfall Model Boehm, is one of the most well-known forms. In this classic representation, the methodology involves seven sequential steps: In the original description of the Boehm-Waterfall software engineering methodology, there is an interactive backstep between each stage.
Thus the Boehm-Waterfall is a combination of a sequential methodology with an interactive backstep Burback, Other early works were patterned after the Waterfall Model, with varying numbers of steps and not-markedly-different names for each stage.
For example, Gore and Stubbe advocated a four-step approach consisting of the study phase, the design phase, the development phase, and the operation phase p. Martin and McClure described it as a multistep process consisting of five basic sequential phases: Another widely used text Whitten, Bentley, and Ho, during the s advocated an eight-step method.
Almost two decades later, a book by the same set of authors in general Whitten, Bentley, and Dittman, also advocated an eight step series of phases, although the names of the stages changed somewhat albeit not significantly. The methodology proceeded through the steps of Scope definition, Problem analysis, Requirements analysis, Logical design, Decision analysis, Physical design and integration, Construction and testing, and ending with Installation and delivery p.
It is interesting to note that nearly 20 years later, the naming conventions used in the newer text are almost synonymous with those in the older work. The Whitten and Bentley text, in its present form, still breaks up the process into eight stages.
While there is no consensus in the naming or number of stages e. Even one of the most current and popular systems analysis and design textbooks Kendall and Kendall, does not depart from tradition, emphasizing that the SDLC is still primarily comprised of seven phases.
Although not immune to criticism, Hoffer, George, and Valacich believe that the view of systems analysis and design taking place in a cycle continues to be pervasive and true p.
Thus, while the SDLC has evolved over the years under the guise of different combinations of naming conventions and numbers of steps or stages, it remains true to form as a well-tested methodology for software development and acquisition.Project Management Journal, 44(4), 65– Reprints and Permissions In a deliberate attempt to shift the analytical focus away from critical examination of the underlying ideological assumptions of project management standards, this paper focuses on the performativity of a specific project life cycle .
SHORTENING THE PROJECT LIFE CYCLE IN INFORMATION TECHNOLOGY AND TELECOMUNICATION PROJECTS. Armando Alejandro Florian Buitrago. Project Management. the difference between project management life cycle and project life cycle, How to take a project from idea to closure, explained via a simple project (trip), and We closed with how many life cycles – focusing on product life cycle.
Project Management Examples giving you case studies of project management. More than 30 comprehensive project management example case studies describe how to undertake every activity within the Project Life Cycle. These examples will: So if you want to view project management examples and case studies to see first hand how other.
A process is a series of actions directed toward a particular result. Project management process groups progress from initiating activities to planning activities, executing activities, monitoring and controlling activities, and closing activities.
Initiating processes include defining and authorizing a project or project . The Project Management Life Cycle has four phases: Initiation, Planning, Execution and Closure. Each project life cycle phase is described below, along with the tasks needed to complete it.
You can click the links provided, to view more detailed information on the project management life cycle.