CIS 319 Week 1 - SDLC Methodology
CIS 319 Week 1 - SDLC Methodology
Popular in Course
verified elite notetaker
Popular in Department
This 0 page Study Guide was uploaded by Experthelper Notetaker on Thursday November 12, 2015. The Study Guide belongs to a course at a university taught by a professor in Fall. Since its upload, it has received 16 views.
Reviews for CIS 319 Week 1 - SDLC Methodology
Report this Material
What is Karma?
Karma is the currency of StudySoup.
You can buy or earn more Karma at anytime and redeem it for class notes, study guides, flashcards, and more!
Date Created: 11/12/15
SDLC Methodology SDLC Methodology Your Name University of Phoenix SDLC Methodology SDLC Methodology The Systems Development Life Cycle SDLC is a business practice used by many companiescorporations and serves as a guideline for developing systems amp software To understand how the SDLC can be either beneficial or detrimental to any system designer we must first understand what the SDLC is and how it applies The Higher Level SDLC is a universal four step process consisting of the following Analysis is generally preceded by a preliminary investigation and is a bit different than identifying it Instead of just listing the problem this phase focuses on what the problem is as well as the final expectations It also provides the designer an opportunity to review the logistics economics operational and technological aspects of the softwaresystem Planning is broken down into two sub phases the Scheduling and Design These phases operate in parallel and necessitate repetition Moore Nolan Gillard 2006 The Planning Phase is an integral part of the SDLC The project team can use this time to identify all the options available to resolve the problem faced and choose the one the best fits into the scheme After that portion of the phase has been completed then the actual design of the project can move forward During the design phases aws in the original plan may appear an require minor adjustments Implementation is the third phase of the SDLC and as with design there are two sub phases construction and deployment However unlike implementation these sub phases do not operate concurrently and could conceivably be considered individual phases Moore Nolan Gillard 2006 This can sometimes be the most frustrating phase of a project because this is when the SDLC Methodology actual change occurs In this phase of the project the solutions agreed upon in the previous steps are placed into a test training and production platform After some time of use the designer will have a better understanding of whether or not the implementation is working Maintenance is exactly what is says With any system development things will go wrong and the maintenance phase is an important part of creating the final productsolution This phase allows the designer to identify problems based on customer feedback programming errors or lack or project output Minor changes are made to maintain the softwaresystem A perfect example of this is Microsoft Windows With every new version there are is a multitude of problems that arise during the Maintenance Phase you can often receive support and resolutions to problems from system design developerstechnical support There are many challenges a designer faces during the SDLC because the process itself is formatted in a linear structure There are many opportunities for things to be missed during the initial phases which show during the deploymentpost production Although problems are generally resolved as they are identified too many problems can project a negative feel towards the softwaresystem as well as the designer Another issue is if you have too many designers or project managers involved You run the risk of duplication of work by multiple teams which affects the overall capital budget since valuable time was wasted Improper training during the Implementation phase can also result in poor technical service during the maintenance phase SDLC Methodology Lastly after the life cycle of any softwaresystem when the program has become obsolete a disposition plan is required to migrate to the new platform MS Windows provides another example of this scenario When we went from Windows NT to XP and now to Vista each platform utilized the SDLC both pre amp post production Support is still required even though a system is rendered obsolete which can takes valuable time away from the designer if he is a part of the newer platform release Although many challenges and issues may arise for a system designerprogrammer the steps provided in a Systems Development Life Cycle does help to manage what solutions are best and corrections required if the SDLC is executed properly SDLC Methodology References Willam Moore Ernest Nolan Sharett Gllard 2006 Towards a HigherLevel Systems Development Life Cycle With UnlversaAppllcatons International journal of Management2 233 646652 Retrieved june 17 2010 from ProQuest database
Are you sure you want to buy this material for
You're already Subscribed!
Looks like you've already subscribed to StudySoup, you won't need to purchase another subscription to get this material. To access this material simply click 'View Full Document'