Q3. List and describe the steps in the Systems Development Life Cycle (SDLC) system as discussed in class and in the course PowerPoint presentation. Identify considerations of primary importance in each step. Diagram the cycle and discuss its operation. Identify, diagram and discuss implementation alternatives? Could you please rewrite this answer by using own words and the two diagram that help me understand the steps and alternative and explain this answer clearly

Planning establishing the plans for creating an IS by:

Defining system to be developed based on the systems prioritized according to the organizations critical success factor (CSF), a system must be identified and chosen

Defining project scope a high level of system requirements must be defined and put into a project scope document. Scope creep.

Developing project plan all details from tasks to be completed, who completed them and when they were completed must be formalized

Managing plan stay on track, creating project milestones and controlling feature creep which allow you to add to the initial plan (Haag, 2007)

Analysis the end users and IT specialists collaborate to collect, comprehend, and logistically formalize business requirements by:

Gathering the business requirements' IT specialists and knowledge workers collaborate in a joint application design (JAD) and discuss which tasks to undertake Development executing the design into a physical system by:

Building the technical architecture

purchasing and installing the material needed to build the system (HST)

Building the database and programs

the IT specialists write programs which will be used on the system (Haag, 2007)

Analyzing the requirements business requirements are prioritized and put in a requirements definition document where the knowledge worker will approve and place their signatures (Haag, 2007)

Design this is where the technical blueprint of the system is created by:

Designing the technical architecture. Choosing architectural designs for:

Telecommunications

Hardware

Software

Systems modeling graphically creating a model from graphical user interface (GUI), GUI screen design, and databases, to placement of objects on screen (Haag, 2007)

Development executing the design into a physical system by:

Building the technical architecture

purchasing and installing the material needed to build the system (HST)

Building the database and programs

the IT specialists write programs which will be used on the system (Haag, 2007)

Testing test the developed system

Write test requirements tests are conducted by comparing expected outcomes to actual outcomes. If these differ, backtracking to the development stage must occur (Haag, 2007).

Test as close to operating conditions as possible.

End user testing. End users can and will break it if possible. Nothing is idiot proof; the idiots win every time

Implementation the systems are placed and used in the actual workforce:

The user guide is created

Other necessary documentation completed

Training is provided to the users of the system (Haag, 2007)

Maintenance keeping system current with the changes in the organization and technology. Ensuring it meets goals of the organization by:

Building a help desk to support the system users having a team available to aid technical difficulties and answer questions

Implementing changes to the system when necessary (OBrien, 2007).

Evaluating system accomplishment of business requirements

Systems Implementation Alternatives

Direct turn off the old system and turn on the new system. Lower cost (only support one system at a time) but high risk of failure.

Parallel Keep old system running until new system is debugged and functional. Low risk because old system is fallback but high costs of supporting and operating two systems at once.

Phased install one component of new system, debug it and turn that component off in old system. Do one part at a time starting with less critical components. More secure than direct but less costly than parallel.