CSC-325: Quiz 8 Review Questions

Steps of the system development lifecycle

1. System Analysis/Planning 2. System Design 3. Building the System 4. Testing 5. Implementation and Maintenance

Economic Feasibility

Do benefits exceed costs? (e.g. ROI)

Legal Feasibility

Does the system meet all regulations and laws?

1. Planning phase

Establishes a high-level plan of the intended project and determines project goals

3. Design phase

Establishes descriptions of the desired features and operations of the system including screen layouts, business rules, process diagrams, pseudo code, and other 4.

SDLC Phases

SDLC has seven main phases: Planning, Analysis, Design, Development, Testing, Implementation, and Maintenance.

Systems Development Lifecycle

The Systems development lifecycle (SDLC) is the process of developing software or information systems from start to finish.

Operational Feasibility

Will our organization be able to operate the system?

System development lifecycle

is used to build and maintain websites

System development lifecycle definition

methodology for understanding business objectives of a system and designing an appropriate solution

Testing

• Alpha Unit, Module, Functional, Systems Testing • Alpha, Beta, Acceptance Performance Testing.

Planning

• Main actors: project manager, project sponsor (usually a VP or other high-level manager who pushed this project into approval), senior analysts • Planning is exactly what it sounds like: the systems development team makes a plan for the systems development project. During this phase, it is vital to conduct several types of feasibility analyses, in order to assess whether developing the system is a good idea. (see other terms)

Design

• Main actors: project manager, system architects, programmers (in a support role; not programming), users (to give input and advice) • During this phase, the system is laid out using "mockups" (if graphical) and the basic modules and logic for the software portion of the system are outlined. This means that example screens and windows are developed (sort of like storyboarding in cinema) to illustrate the basic flow and feel of the system. Hardware requirements are also determined during this phase.

System analysis/planning consists of

• business objectives system functionalities information requirements • business objectives • capabilities you want your site to have • system functionalities • information system capabilities needed to achieve business objectives

2. Analysis phase

Involves analyzing end-user business requirements and refining project goals into defined functions and operations of the intended system

5. Testing phase

Involves bringing all the project pieces together into a special testing environment to eliminate errors and bugs, and verify that the system meets all of the business requirements defined in the analysis phase

6. Implementation phase

Involves placing the system into production so users can begin to perform actual business operations with it

4. Development phase

Involves taking all of the detailed design documents from the design phase and transforming them into the actual system

Scheduling Feasibility

Is the project timeline realistic given our resources?

Technical Feasibility

Is the system realistic, and de we have the expertise to develop it?

Systems development life cycle (SDLC)

The overall process for developing information systems from planning and analysis through implementation and maintenance 1. Planning phase: Establishes a high-level plan of the intended project and determines project goals 2. Analysis phase: Involves analyzing end-user business requirements and refining project goals into defined functions and operations of the intended system 3. Design phase: Establishes descriptions of the desired features and operations of the system including screen layouts, business rules, process diagrams, pseudo code, and other 4. 4. Development phase: Involves taking all of the detailed design documents from the design phase and transforming them into the actual system 5. Testing phase: Involves bringing all the project pieces together into a special testing environment to eliminate errors and bugs, and verify that the system meets all of the business requirements defined in the analysis phase 6. Implementation phase: Involves placing the system into production so users can begin to perform actual business operations with it

Analysis

• Main actors: systems analysts, business analysts • One of the key tasks during the analysis phase is determining user requirements (i.e., what do they want the system to be able to do). Users might be customers, clients, our own organization, or other stakeholders. This is called requirements gathering, or requirements elicitation. These requirements are then compiled in a requirements definition document: a more detailed version of the requirements matrix