Sign Up Now
Get instant access to over 1 million+ study documents
OR
Already registered? click here to login
By creating your account, you agree to our terms of service, privacy policy and student honor code.
d.).
In this case the Jefferson County School system administrators did not do well at all. They did not develop at project team nor assign a project manager in order to oversee the implementation. They had no real implementation plan in place that laid out all the steps that needed to be done. There was no risk management plan developed so as risks presented themselves they had no idea how to handle them. There was no real testing phase in order to work through any of the bugs that the system had. They just put the system into production and then discovered that it didn't work. They had no plan in place to keep the old system up and running so that work could continue if the new system did not work. The implementation of the new software was basically a disaster.
Critique the performance of JCSS management in the purchase of this system.
The performance of JCSS management in the purchase of this system was a failure. They did not evaluate each system to the extent that they could guarantee that it would do what they needed it to do. Although they had many people on the team and each had ideas that were vital to the process they did not seem to have the right people on the team in order to make this process successful. There was not enough participation from the IT department from the beginning so that they knew whether what they were buying was going to be useable in the end.
The implementation problems illustrated in this case may occur when the system is built by the IS department and they build it using the SDLC methodology. Do the lessons of this case apply...
The SDLC is basically the part of process in which the coding/programming is put to use solving the problem in regards to an existing or planned application. The stages of SDLC can vary somewhat but generally include the following: conceptualization, requirements and cost/benefits analysis, detailed specification of the software requirements, software design, programming, testing, user and technical training, and maintenance (SDLC Resources, 2009).
Yes, the lessons in this case definitely apply to SDLC. These phases are all ones that need to be done in order to be successful. If just one of these phases is skipped or not fully thought through disaster is sure to occur. Each step is important and dependent on the step before it. Without proper planning, testing, training and maintenance there is no way that a software implementation will work in the end.
References
Implementing Your Technology. (n.d.). Retrieved January 28, 2010, from National Center for Education Statistics Web site: http://nces.ed.gov/pubs2005/tech_suite/part_4.asp
SDLC Resources. (2009). Retrieved January 28, 2010, from MKS Web site:
http://www.mks.com/sdlc
Select the Enterprise Software Best Matching Yours Needs. (2010). Retrieved January 28, 2010,
http://it.toolbox.com/wiki/index.php/Select_The_Enterprise_Software_Best_Matching_Y
Systems Development Life Cycle has historically been a very useful tool in the development of software and operating systems in Computer Information Technology. Through the Systems Development Life Cycle there are at least five distinct phases that are delineated and performed within a linear patter. Meaning, that each step must be complete or at least very close in order for the next set of experts to begin the next phase
However, the company did feel it should develop its own Database infrastructure that would work with the new underlying database management system and would mesh with existing organizational skills and the selected enterprise software solution. Because the company followed a standardized implementation process, they were able to successfully reengineer their existing business structure. The objective of the System Development Life Cycle is to help organizations define what an appropriate system
system development life cycle (SDLC) approach to the development of Information Systems and/or software is provided. An explanation of SDLC is offered, with different models applied in implementing SDLC delineated. Advantages and disadvantages associated with each of the models will be identified. System Development Life Cycle According to Walsham (1993), system development life cycle (SDLC) is an approach to developing an information system or software product that is characterized by a
Systems Development Life-Cycle is a framework for an evolution from abstract ideas to a concrete reality Systems development life-cycle (SDLC) is a structured process of systems development is an evolutionary process that proceeds from a broad concept of information requirements and finally ends into the manufacturing of a product -- development of a new system. From this conception it can be seen that the ideas of SDLC begin to narrow
Software Development Life Cycle ( SDLC) Explain Requirement process ( in SDLC) in detail. Why is this exercise important? Requirements engineering is a fundamental activity in systems development and it is the process by which the requirements for software systems are identified, systematized and implemented and are followed through the complete lifecycle. Traditionally engineers focused on narrow functional requirements. Now it is being argued by Aurum and Wohlin (2005) that focusing only
This process places the user in a central position for both determining system requirements and ensuring they are met. The benefits of these systems include not only improvements in user efficiency, but also others, such as reduced training costs, reduced user errors, reduced maintenance costs, and increased customer satisfaction. However, the chief requirements in these kinds of systems become to understand the users' information needs. As we argued earlier, the systems