Systems Development Life Cycle Systems development life cycle (SDLC) is a distinct process independent of software or other information Technology considerations. It is used by a systems analyst to develop an information system, including requirements, validation, training, and user ownership through investigation, analysis, design, implementation, and maintenance. SDLC should result in a high quality system that meets or exceeds customer expectations, within time and cost estimates, works effectively and efficiently in the current and planned information technology infrastructure, and is cheap to maintain and cost-effective to enhance. A brief description of seven phases of SDLC is given below: Project Definition The project definition phase prompts collection of information to determine if a project warrants the investment of personnel resources and funding. The project definition should identify the customer, user, mandate, and basic operating concept. Additionally, the project definition should provide a preliminary investigation of alternatives and risk analysis, and a high level cost-benefit analysis to determine if the project has a favorable return on investment.
User Requirements Definition The user requirements definition phase is based on the processes that users conduct in their day-to-day activity. The user requirements should clearly describe what part of the user process (activity) should be automated or enhanced, and the expected capabilities and features. System/data Requirements Definition The system/data requirements definition phase is based on merging user processes and requirements in a way that allows a system to support many different users or functions in similar areas. The system/data requirements phase marks the start of establishing key technical areas to use technology to make the work easier. Analysis and Design The analysis and design phase is a complex and critical step in determining which system design, based on systems engineering and technology analysis, meets the user and system requirements. For non technical solutions, the design may simply be a support process to be implemented over time.
The Essay on Systems Gathering Requirements Document
During the systems planning phase a feasibility analysis was performed in determining if purchasing a software program would meet the demands of operations (need), technical (practicality), and economic (financial) factors of the project. Given the fact that over time, collateral analysts spend a tremendous amount of time manually calculating borrowing base ineligibles from cumbersome agings, ...
System Build/Prototype/Pilot The system build phase is the execution of the approved design and in some cases may blend into the implementation phase. A smaller test system is sometimes a good idea in order to get a proof of concept validation prior to committing funds for large scale fielding of a system without knowing if it really works as intended by the user. For non-technical solutions, the system build may involve creation of a support process and move directly to implementation. Implementation and Training Implementation includes all necessary activity to procure, receive, configure, and install the new or revised system. For non-technical solutions, implementation may be limited to a new support process requiring a change in the business process. Training is conducted during this phase according to the training plan, which would have been developed in one or more of the previous phases. Sustainment The sustainment phase is a dedicated effort to keep the system operating at an optimum level by conducting maintenance and enhancements as determined by periodic reviews. For non-technical solutions, sustainment may be the continuation of a support process.
The Business plan on Understanding Erp System Implementation in Higher Education: a Grounded Theory Approach
... the go-live phase. Parallel to the implementation of the ERP system, managers started changing the business processes while explaining them ... 220. The HEI implementation project followed the typical implementation phases: planning, design, realization, go live, and support. At the beginning ... person being allocated to economics management tasks. The solution has been to create a special group in ...
References ; 1) Richard W. Pew and Anne S. Mavor, Committee on Human Factors, National Research Council, Committee on Human-System Design Support for Changing Technology. 2) Ian Bray, Introduction to Requirements Engineering, 2003. 3) Steve Skidmore, Malcolm, Eva Introducing Systems Development..
