The purpose of an SDLC methodology is to provide IT Project Managers with the tools to help ensure successful implementation of systems that satisfy University strategic and business objectives. The documentation provides a mechanism to ensure that executive leadership, functional managers and users sign-off on the requirements and implementation of the system. The process provides University Project Managers
with the visibility of design, development, and implementation status needed to ensure delivery on time and within budget. This Guideline applies to all major application projects, both new applications and upgrades of existing applications. The goals of this SDLC approach are to:
ObjectivesThe SDLC methodology will help to achieve these goals by:
Guidelines and ProceduresA software application typically undergoes several development lifecycles, corresponding to its creation and subsequent upgrades. Each such development lifecycle constitutes a project. Such projects continue until the underlying technology ages to the point where it is no longer economical to invest in upgrades and the application is considered for either continued as-is operation or retirement. The SDLC PhasesMichigan Tech’s SDLC includes six phases, during which defined work products and documents are created, reviewed, refined, and approved. Not every project will require that the phases be subsequently executed and may be tailored to accommodate the unique aspects of a projects. These phases are described in more detail in the following paragraphs. Initiation PhaseThe Initiation Phase begins when management determines that it is necessary to enhance a business process through the application of information technology. The purposes of the Initiation Phase are to:
Feasibility PhaseThe Feasibility Phase is the initial investigation, or brief study of the problem to determine whether the systems project should be pursued. A feasibility study established the context through which the project addresses the requirements expressed in Business Case and investigates the practicality of a proposed solution. The feasibility study is used to determine if the project should get the go-ahead. If the project is to proceed, the feasibility study will produce a project plan and budget estimates for the future stages of development. Requirements Analysis PhaseThis phase formally defines the detailed functional user requirements using high-level requirements identified in the Initiation and Feasibility Phases. The requirements are defined in this phase to a level of detail sufficient for systems design to proceed. They need to be measurable, testable, and relate to the business need or opportunity identified in the Initiation Phase. The purposes of this phase are to:
Design PhaseDuring this phase, the system is designed to satisfy the functional requirements identified in the previous phase. Since problems in the design phase can be very expensive to solve in later stages of the software development, a variety of elements are considered in the design to mitigate risk. These include:
Development PhaseEffective completion of the previous stages is a key factor in the success of the Development phase. The Development phase consists of:
Integration, system, security, and user acceptance testing is conducted during this phase as well. The user, with those responsible for quality assurance, validates that the functional requirements are met by the newly developed or modified system. Implementation PhaseThis phase is initiated after the system has been tested and accepted by the user. In this phase, the system is installed to support the intended business functions. System performance is compared to performance objectives established during the planning phase. Implementation includes user notification, user training, installation of hardware, installation of software onto production computers, and integration of the system into daily work processes. This phase continues until the system is operating in production in accordance with the defined user requirements. Operations and MaintenanceThe system operation is ongoing. The system is monitored for continued performance in accordance with user requirements and needed system modifications are incorporated. Operations continue as long as the system responds to the organization’s needs. When modifications are identified, the system may reenter the planning phase. End of document. Rev 9/20/16 In which phase of the systems development life cycle are the broad needs of the users converted into detailed specifics that are coded and tested?In which phase of the systems development life cycle are the broad needs of the users converted into detailed specifics that are coded and tested? Physical design.
What are the phases in system development life cycle?Systems development life cycle phases include planning, system analysis, system design, development, implementation, integration and testing, and operations and maintenance.
Who is responsible for ensuring that the new information system developed will meet the needs of users?DUTIES OF A SYSTEM ANALYST
Their duties include the following: Consulting with management and users to determine the needs of the system\ Designing a system to meet the business objectives and goals.
Which phase in the systems life cycle involves installing the new system and training people?Implementation Phase
Implementation includes user notification, user training, installation of hardware, installation of software onto production computers, and integration of the system into daily work processes.
|