MIS 581 Week 8 Final Exam
1. (TCO A) List and describe four of the seven phases of the systems
development life cycle. (Points : 27)
SDLC: It has 6 main phases: system engineering, requirement analysis, system analysis and design, coding, testing, and
maintenance.
1. In system engineering, the requirements of the client are completely understood and a documentation is done.
2. In the requirement analysis, the feasibility of the project is checked whether the project should be done or not.
3. During system analysis, designing is done that would result in coding.
4. The next phase is coding, where the actual code is written.
5. Testing is done to test the code, and maintenance is the help provided by the project team to the users for many
years to come.
The PMLC has different phases, and is more successful at managing projects than SDLC.
It is more clearly defined and has room for flexibility, which can take different forms depending from project to project.
Following are the seven phases of the SDLC:Planning (1), Systems Analysis (2), Systems Design (3),
Development (4), Testing (5), Implementation (6) and Maintenance (7)
1. Planning
This is the first phase in the systems development process. It identifies whether or not there is the need for a new
system to achieve a business’s strategic objectives. This is a preliminary plan (or a feasibility study) for a
company’s business initiative to acquire the resources to build on an infrastructure to modify or improve a service.
The company might be trying to meet or exceed expectations for their employees, customers and stakeholders
too. The purpose of this step is to find out the scope of the problem and determine solutions. Resources, costs,
time, benefits and other items should be considered at this stage.
2. Systems Analysis and Requirements
The second phase is where businesses will work on the source of their problem or the need for a change. In the
event of a problem, possible solutions are submitted and analyzed to identify the best fit for the ultimate goal(s) of
the project. This is where teams consider the functional requirements of the project or solution. It is also where
system analysis takes place—or analyzing the needs of the end users to ensure the new system can meet their
expectations. Systems analysis is vital in determining what a business"s needs are, as well as how they can be
met, who will be responsible for individual pieces of the project, and what sort of timeline should be expected.
There are several tools businesses can use that are specific to the second phase. They include:
CASE (Computer Aided Systems/Software Engineering)
Requirements gathering
Structured analysis
3. Systems Design
The third phase describes, in detail, the necessary specifications, features and operations that will satisfy the
functional requirements of the proposed system which will be in place. This is the step for end users to discuss
and determine their specific business information needs for the proposed system. It"s during this phase that they
will consider the essential components (hardware and/or software) structure (networking capabilities), processing
and procedures for the system to accomplish its objectives.
4. Development
The fourth phase is when the real work begins—in particular, when a programmer, network engineer and/or
database developer are brought on to do the major work on the project. This work includes using a flow chart to
ensure that the process of the system is properly organized. The development phase marks the end of the initial
section of the process. Additionally, this phase signifies the start of production. The development stage is also
characterized by instillation and change. Focusing on training can be a huge benefit during this phase.
5. Integration and Testing
The fifth phase involves systems integration and system testing (of programs and procedures)—normally carried
out by a Quality Assurance (QA) professional—to determine if the proposed design meets the initial set of
business goals. Testing may be repeated, specifically to check for errors, bugs and interoperability. This testing
will be performed until the end user finds it acceptable. Another part of this phase is verification and validation,
both of which will help ensure the program’s successful completion.
6. Implementation
1. (TCO A) List and describe four of the seven phases of the systems
development life cycle. (Points : 27)
SDLC: It has 6 main phases: system engineering, requirement analysis, system analysis and design, coding, testing, and
maintenance.
1. In system engineering, the requirements of the client are completely understood and a documentation is done.
2. In the requirement analysis, the feasibility of the project is checked whether the project should be done or not.
3. During system analysis, designing is done that would result in coding.
4. The next phase is coding, where the actual code is written.
5. Testing is done to test the code, and maintenance is the help provided by the project team to the users for many
years to come.
The PMLC has different phases, and is more successful at managing projects than SDLC.
It is more clearly defined and has room for flexibility, which can take different forms depending from project to project.
Following are the seven phases of the SDLC:Planning (1), Systems Analysis (2), Systems Design (3),
Development (4), Testing (5), Implementation (6) and Maintenance (7)
1. Planning
This is the first phase in the systems development process. It identifies whether or not there is the need for a new
system to achieve a business’s strategic objectives. This is a preliminary plan (or a feasibility study) for a
company’s business initiative to acquire the resources to build on an infrastructure to modify or improve a service.
The company might be trying to meet or exceed expectations for their employees, customers and stakeholders
too. The purpose of this step is to find out the scope of the problem and determine solutions. Resources, costs,
time, benefits and other items should be considered at this stage.
2. Systems Analysis and Requirements
The second phase is where businesses will work on the source of their problem or the need for a change. In the
event of a problem, possible solutions are submitted and analyzed to identify the best fit for the ultimate goal(s) of
the project. This is where teams consider the functional requirements of the project or solution. It is also where
system analysis takes place—or analyzing the needs of the end users to ensure the new system can meet their
expectations. Systems analysis is vital in determining what a business"s needs are, as well as how they can be
met, who will be responsible for individual pieces of the project, and what sort of timeline should be expected.
There are several tools businesses can use that are specific to the second phase. They include:
CASE (Computer Aided Systems/Software Engineering)
Requirements gathering
Structured analysis
3. Systems Design
The third phase describes, in detail, the necessary specifications, features and operations that will satisfy the
functional requirements of the proposed system which will be in place. This is the step for end users to discuss
and determine their specific business information needs for the proposed system. It"s during this phase that they
will consider the essential components (hardware and/or software) structure (networking capabilities), processing
and procedures for the system to accomplish its objectives.
4. Development
The fourth phase is when the real work begins—in particular, when a programmer, network engineer and/or
database developer are brought on to do the major work on the project. This work includes using a flow chart to
ensure that the process of the system is properly organized. The development phase marks the end of the initial
section of the process. Additionally, this phase signifies the start of production. The development stage is also
characterized by instillation and change. Focusing on training can be a huge benefit during this phase.
5. Integration and Testing
The fifth phase involves systems integration and system testing (of programs and procedures)—normally carried
out by a Quality Assurance (QA) professional—to determine if the proposed design meets the initial set of
business goals. Testing may be repeated, specifically to check for errors, bugs and interoperability. This testing
will be performed until the end user finds it acceptable. Another part of this phase is verification and validation,
both of which will help ensure the program’s successful completion.
6. Implementation
