IS201: Midterm #3- VBA
System Developement Lifecycle (SDLC) - ANS-The process of developing software or
information systems from beginning to end.
SDLC Phases: Planning (1) - ANS--Technical Feasibility: Is the system realistic and do we need
experts to develop it.
-Economic Feasibility: Do benefits exceed costs?
-Legal Feasibility: Does it meet regulations and laws?
-Operational Feasibility: Will the organization be able to operate this system?
-Scheduling Feasibility: Is the project timeline realistic given our resources?
SDLC Phases: Analysis (2) - ANS-The objective is to determine the 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.
SDLC Phases: Design (3) - ANS-Diagraming to illustrate the conceptual thought and basic
flow/feel for the system.
SDLC Phases: Development (4) - ANS-Where the actual coding takes place (alpha system is
created).
SDLC Phases: Testing (5) - ANS-Closely related to the development phase this phase is to test
out the system, find bugs, and try to break the system. Penetration testing is performed to
ensure that the system cannot be hacked. Unit testing, Integration testing, system testing, and
user-acceptance testing.
SDLC Phases: Implementation (6) - ANS-this phase is when the development team must train
users how to use the new system. 1.) Direct Conversion: The old system is discontinued and the
new system is live. 2.) Parallel Conversion: Continue to run old system until the new one is
completely activated and working. Then once the new system is stable, the old system is
dicontinued
3.)Phased Conversion: Implement modules one at a time after each module is stable.
4.) Pilot Conversion: Activate and test the system in one branch of an organization to resolve
bugs and see how it does.
SDLC Phases: Maintenance (7) - ANS-Continued support for the system even after its
implementation. Errors found are fixed by development teams.
Make-Build-Buy Software decision - ANS--Make: means that the organization will write the
software code—or some portion of it—themselves using their own programmers.
System Developement Lifecycle (SDLC) - ANS-The process of developing software or
information systems from beginning to end.
SDLC Phases: Planning (1) - ANS--Technical Feasibility: Is the system realistic and do we need
experts to develop it.
-Economic Feasibility: Do benefits exceed costs?
-Legal Feasibility: Does it meet regulations and laws?
-Operational Feasibility: Will the organization be able to operate this system?
-Scheduling Feasibility: Is the project timeline realistic given our resources?
SDLC Phases: Analysis (2) - ANS-The objective is to determine the 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.
SDLC Phases: Design (3) - ANS-Diagraming to illustrate the conceptual thought and basic
flow/feel for the system.
SDLC Phases: Development (4) - ANS-Where the actual coding takes place (alpha system is
created).
SDLC Phases: Testing (5) - ANS-Closely related to the development phase this phase is to test
out the system, find bugs, and try to break the system. Penetration testing is performed to
ensure that the system cannot be hacked. Unit testing, Integration testing, system testing, and
user-acceptance testing.
SDLC Phases: Implementation (6) - ANS-this phase is when the development team must train
users how to use the new system. 1.) Direct Conversion: The old system is discontinued and the
new system is live. 2.) Parallel Conversion: Continue to run old system until the new one is
completely activated and working. Then once the new system is stable, the old system is
dicontinued
3.)Phased Conversion: Implement modules one at a time after each module is stable.
4.) Pilot Conversion: Activate and test the system in one branch of an organization to resolve
bugs and see how it does.
SDLC Phases: Maintenance (7) - ANS-Continued support for the system even after its
implementation. Errors found are fixed by development teams.
Make-Build-Buy Software decision - ANS--Make: means that the organization will write the
software code—or some portion of it—themselves using their own programmers.
