MBA 815 MODULE 2
UNIT 3 DEVELOPMENT, INTEGRATION AND TESTING
OF INFORMATION SYSTEM
CONTENTS
1.0 Introduction
2.0 Objectives
3.0 Main Content
3.1 Development and Integration and Testing Phases
3.1.1 Development
3.1.2 Integration and Testing
3.2 Tasks and Activities
3.2.1 Development
3.3 Roles and Responsibilities
3.3.1 Development
3.3.2 Integration and Testing
3.4 Deliverables
3.4.1 Development
3.4.2 Integration and Testing
3.5 Issues for Consideration
3.5.1 Development
3.5.2 Integration and Testing
3.6 Phase Review Activity
3.6.1 Development
3.6.2 Integration and Testing
4.0 Conclusion
5.0 Summary
6.0 Tutor-Marked Assignment
7.0 References/Further Readings
1.0 INTRODUCTION
This unit dwells mainly on tasks, activities, roles and responsibilities of
both Development and Integration and testing phases.
2.0 OBJECTIVES
This unit is designed for you to:
• understand what constitutes system’s development, integration
and testing phase in designing and developing information system
• identify the tasks you need to embark on during the
development, integration and testing phase of systems
development
• comfortably answer the question of responsibilities and
roles in executing the development, integration and testing
85
MBA 815 MANAGEMENT INFORMATION SYSTEM
phase of a systems development project
• be able to know what are the deliverables from
development, integration and testing to be used for subsequent
phases
• identify some issues that need to be considered in
development,integration and testing phase of a system.
3.0 MAIN CONTENT
3.1 Development and Integration and Testing Phases
3.1.1 Development
The objective of the Development Phase will be to
convert the deliverables of the Design Phase into a complete
information system. Although much of the activity in the Development
Phase addresses the computer programs that make up the
system, this phase also puts in place the hardware, software, and
communications environment for the system and other important
elements of the overall system.
The activities of this phase translate the system design produced in the
Design Phase into a working information system capable of addressing
the information system requirements. The development phase
contains activities for building the system, testing the system,
and conducting functional qualification testing, to ensure
the system functional processes satisfy the functional process
requirements in the Functional Requirements Document (FRD). At
the end of this phase, the system will be ready for the activities of
the Integration and Test Phase.
3.1.2 Integration and Testing
The objective of this phase is to prove that the
developed system satisfies the requirements defined.
Several types of tests will be conducted in this phase.
First, subsystem integration tests shall be executed and
evaluated by the development team to prove that the
program components integrate properly into the subsystems and that the
subsystems integrate properly into an application. Next, the testing team
conducts and evaluates system tests to ensure the
developed system meets all technical requirements, including
performance requirements. Next, the testing team and the
Security Program Manager conduct security tests to validate
that the access and data security requirements are met. Finally, users
participate in acceptance testing to confirm that the developed system
86
MBA 815 MODULE 2
meets all user requirements as stated. Acceptance testing shall be
done in a simulated “real” user environment with the
users using simulated or real target platforms and infrastructures.
3.2 Tasks and Activities
3.2.1 Development
Code and Test Software
Code each module according to established standards.
Integrate Software
Integrate the software units, components and modules.
Integrate the software units and software components and test in
accordance with the integration plan. Ensure that each module satisfies
the requirements of the software at the conclusion of the integration
activity.
Conduct Software Qualification Testing.
Conduct qualification testing in accordance with the
qualification requirements for the software item. Ensure that the
implementation of each software requirement is tested for
compliance. Support audit(s) which could be conducted to ensure
that:
• as-coded software products (such as software item) reflect the
design documentation
• the acceptance review and testing requirements prescribed
by the documentation are adequate for the acceptance
of the software products
• test data comply with the specification
• software products were successfully tested and meet
their specifications
• test reports are correct, and discrepancies between
actual and expected results have been resolved
• user documentation complies with standards as specified.
The results of the audits shall be documented. If both
hardwaresoftware are under development or integration,
the audits maypostponed until the System Qualification Testing.
Upon successful completion of the audits, if
conducted, update prepare the deliverable software product for
System Integration, System Qualification Testing, Software
Installation, or Software Acceptance Support as applicable. Also,
establish a baseline for the design and code of the software item.
87
MBA 815 MANAGEMENT INFORMATION SYSTEM
3.2.2 Integrate System
Integrate the software configuration items with hardware configuration
items, manual operations, and other systems as
necessary, into the system. The aggregates shall be tested, as
they are developed, against their requirements. The integration
and the test results shall be documented. For each qualification
requirement of the system, a set of tests, test cases (inputs, outputs,
test criteria), and test procedures for conducting System
Qualification Testing, shall be developed and documented.
Ensure that the integrated system is ready for System
Qualification Testing.
Conduct System Qualification Testing
Conduct system qualification testing in accordance with
the qualification requirements specified for the system.
Ensure that the implementation of each system requirement is tested
for compliance and that the system is ready for delivery. The
qualification testing results shall be documented.
Install Software
Install the software product in the target environment as designed, and in
accordance with the Installation Plan. The resources and
information necessary to install the software product shall
be determined and be available. The developer shall assist
the acquirer with the set-up activities. Where the installed
software product is replacing an existing
system, the developer shall support any parallel running activities
that are required. Ensure that the software code and
databases initialize, execute, and terminate as specified in
the contract. The installation events and results shall be
documented.
Document Software Acceptance Support
Acceptance review and testing shall consider the results of
the Joint Reviews, Audits, Software Qualification Testing,
and System Qualification Testing (if performed). The results
of the acceptance review and testing shall be documented.
The developer shall complete and deliver the software
product as specified. The developer shall provide initial and
continuing training and support to the acquirer as specified.
Revise Previous Documentation
Review and update previous phase documentation, as needed.
88
MBA 815 MODULE 2
Integration and Testing
The tasks and activities actually performed depend on the nature of the
project. The following tasks should be completed during the Integration
and Test phase.
Establish the Test Environment
Establish the various test teams and ensure the test system(s) are ready.
Conduct Integration Tests
The test and evaluation team is responsible for creating/loading the
test database(s) and executing the integration test(s). This is to ensure
that program components integrate properly into the
subsystems and the subsystems integrate properly into an
application.
Conduct Subsystem/System Testing
The test and evaluation team is responsible for creating/loading the
test database(s) and executing the system test(s). All
results should documented on the Test Analysis Report, Test
Problem Report, and on the Test Analysis Approval
Determination. Any failed components should be migrated back
to the development phase for rework, and the passed components
should be migrated ahead for security testing.
Conduct Security Testing
The test and evaluation team will again create or
load the database(s) and execute security (penetration) test(s). All
tests will be documented, similar to those above. Failed components
will be migrated back to the development phase for rework, and passed
components will be migrated ahead for acceptance testing.
Conduct Acceptance Testing
The test and evaluation team will create/load the test
database(s) and execute the acceptance test(s). All tests will be
documented, similar to those above. Failed components will
be migrated back to the development phase for rework,
and passed components will migrate ahead for implementation.
Revise Previous Documentation
During this phase, the Systems Technical Lead or the Developer(s) will
finalize the Software Development Document from the
Development Phase. He/They will also finalize the
Operations or Systems Administration Manual, User Manual,
Training Plan, Maintenance Manual, Conversion Plan,
Implementation Plan, Contingency Plan, and Update the Interface
89
MBA 815 MANAGEMENT INFORMATION SYSTEM
Control Document from the Design Phase. The Project
Manager should finalize the System Security Plan and
the Security Risk Assessment from the Requirements Analysis Phase,
and the Project Management Plan from the Planning
Phase. The Configuration Manager should finalize the
Configuration Management Plan from the Planning Phase. The
Quality Assurance office/person should finalize the Quality
Assurance Plan from the Planning Phase. And finally, the
Project Manager should finalize the Cost Benefit
Analysis and the Risk Management Plan from the
System Concept Development Phase.
3.3 Roles and Responsibilities
3.3.1 Development
• Project Manager: The project Manager is responsible
and accountable for the successful execution of the
Development Phase. The project Manager is responsible
for leading the team that accomplishes the tasks shown
above. The Project Manager is also responsible for
reviewing deliverables for accuracy, approving
deliverables and providing status reports to management.
• Project Team: The project team members (regardless
of the organization of permanent assignment) are
responsible for accomplishing assigned tasks as directed by the
project manager.
• Contracting Officer: The contracting officer is
responsible and accountable for the procurement
activities, and signs contract awards.
• Oversight Activities: Agency oversight activities,
including the IRM office, provide advice and counsel to
the project manager on the conduct and requirements of
the Development Phase. Additionally, oversight
activities provide information, judgments, and
recommendations to the agency decision makers during project
reviews, and in support of project decision milestones.
• Developer: The developer is responsible for the
development activities to include coding, testing, documenting
and delivering the completed system.
3.3.2 Integration and Test
• Project Manager: The project manager is responsible
and accountable for the successful execution of the Integration
and Test Phase. The project manager is responsible for leading the
90
MBA 815 MODULE 2
team that accomplishes the tasks shown above. The Project
Manager is also responsible for reviewing deliverables
for accuracy, approving deliverables and providing status
reports to management.
• Project Team: The project team members (regardless
of the organization of permanent assignment) are
responsible for accomplishing assigned tasks as directed
by the project manager. This includes establishing the test
environment.
• Contracting Officer: The contracting officer is
responsible and accountable for the procurement activities and
signs contract awards.
• Security Program Manager: The Security Program
Manager is responsible for conducting security tests
according to the Systems Security Plan.
• Oversight Activities: Agency oversight activities,
including the IRM office, provide advice and counsel for the
project manager on the conduct and requirements of
the Integration and Test A dditionally, oversight
activities provide information, judgments, and
recommendations to the agency decision makers during project
reviews and in support of project decision milestones.
• User: Users participate in acceptance testing to
ensure systems perform as expected.
3.4 Deliverables
3.4.1 Development
Thecontentofthesedeliverablesmay
beexpandedordependingonthesize,scope,andcomplexityofthesystemsdev
elopmenteffort. The following deliverables shall beinitiated
during the Development Phase:
Contingency Plan
The Contingency Plan contains emergency response procedures; backup
arrangements, procedures, and responsibilities; and post-
disaster recovery procedures and responsibilities. Contingency
planning is essential to ensure that organizations systems are able
to recover from processing disruptions in the event of localized
emergencies or large-scale disasters. It is an emergency
response plan, developed in conjunction with application owners,
and maintained at the primary and backup computer installation, to
ensure that a reasonable continuity of support is provided if events
occur that could prevent normal operations.
91
MBA 815 MANAGEMENT INFORMATION SYSTEM
Contingency plans shall be routinely reviewed, updated, and
tested to enable vital operations and resources to be
restoredas quickly aspossibleand to keep system downtime
to an absolute minimum. A Contingency Plan is synonymous
with a disaster plan and an emergency plan. If the system/subsystem is
to be located within a facility with an acceptable contingency plan,
system-unique contingency requirements should be added as an annex
to the existing facility contingency plan.
Software Development Document
Contains documentation pertaining to the development of each unit
or module, including the test cases, software, test results,
approvals, and any other items that will help explain the functionality of
the software.
System (Application) Software
This is the actual software developed. It is used
for the Test integration Phase and finalized before
implementation of the system. Include all the disks (or other
medium) used to store the information.
Test Files/Data
All the information used for system testing should be provided
at the end of this phase. Provide the actual test data and files used.
Integration Document
The Integration Document explains how the software
components, hardware components, or both are combined,
and the interaction between them.
3.4.2 Integration and Testing
The following deliverables shall be initiated during the Integration and
Test Phase:
Test Analysis Report
This report documents each test - unit/module, subsystem
integration,system, user acceptance and security.
Test Analysis Approval Determination
Attached to the test analysis report as a final result of the test
reviews and testing levels above the integration test; briefly
summarizes the perceived readiness for migration of the software.
Test Problem Report Document problems encountered during testing;
the form is attached to the test analysis reports.
92
MBA 815 MODULE 2
IT Systems Security Certification and Accreditation
The documents needed to obtain certification and accreditation
of an information system before it becomes operational. They include:
System Security Plan; Rules of Behavior; Configuration Management
Plan, Risk Assessment; Security Test & Evaluation;
Contingency Plan; Privacy Impact Assessments; and the
certification and accreditation memorandums. The Systems
Security Plan and certification/accreditation package should
be approved prior to implementation, and every three years
thereafter.
3.5 Issues for Consideration
3.5.1 Development
There are threephaseprerequisitesthat shouldbe completedbeginning
this phase:
• Project management plan and schedule indicating
target date for completion of each module, and target date for
completion of system testing.
• System design document, containing program logic flow,
identifying any existing code to be used, and the subsystems
with their inputs and outputs.
• Unit/module and integration test plans, containing
testing requirements, schedules, and test case
specifications for unit and integration testing.
3.5.2 Integration and Testing
Security controls shall be tested before system
implementation to uncover all design and implementation flaws that
would violate security policy. Security Test and Evaluation
(ST&E) involves determining a system’s security mechanisms
adequacy for completeness and correctness, and the degree
of consistency between system documentation and actual
implementation. This shall be accomplished through a variety of
assurance methods such as analysis of system design
documentation, inspection of test documentation, and
independent execution of function testing and penetration
testing. Results of the ST&E affect security activities developed
earlier in the life cycle such as security risk assessment,
sensitive system security plan, and contingency plan. Each of these
activities will be updated in this phase, based on the results of
the ST&E. Build on the security testing recorded in the
software development documents, unit testing, integration testing,
93
MBA 815 MANAGEMENT INFORMATION SYSTEM
and system testing.
3.6 Phase Review Activity
3.6.1 Development
Upon completion of all Development Phase tasks and
receipt of resources for the next phase, the Project Manager,
together with the project team, should prepare and present a project
status review for the decision maker and project stakeholders. The
review should address:
(1) development Phase activities status,
(2) planning status for all subsequent life cycle phases
(with significant detail on the next phase, to
include the status of pending contract actions),
(3) resource availability status, and
(4) acquisition risk assessments of subsequent life cycle
phases, given the planned acquisition strategy.
3.6.2 Integration and Testing
Upon completion of all Integration and Test Phase tasks and receipt of
resources for the next phase, the Project Manager, together
with the project team, should prepare and present a project status
review for the decision maker and project stakeholders. The review
should address:
(1) integration and Test Phase activities status,
(2) planning status for all subsequent life cycle phases
(with significant detail on the next phase, to
include the status ofpending contract actions),
(3) resource availability status, and
(4) acquisition risk assessments of subsequent life cycle
phases given, the planned acquisition strategy.
4.0 CONCLUSION
Development is what converts the design model into
reality. It is important phase of system’s development. On
the other hand, integration and testing is used to fine-tune a system
to detect errors and shortcomings in systems development processes.
94
MBA 815 MODULE 2
5.0 SUMMARY
• The objective of the Development Phase will be
to convert the deliverables of the Design Phase into a
complete information system.
• The objective of the integration and testing phase is to prove that
the developed system satisfies the requirements defined. Several
types of tests will be conducted in this phase.
• Conduct qualification testing in accordance with the
qualification requirements for the software item. Ensure that
the implementation of each software requirement is tested for
compliance.
• The project Manager is responsible and
accountable for the successful execution of the Development
Phase.
• The Configuration Manager should finalize the
Configuration Management Plan from the Planning Phase.
• The Contingency Plan contains emergency response
procedures; backup arrangements, procedures, and
responsibilities; and post-disaster recovery procedures and
responsibilities.
• Security controls shall be tested before system
implementation to uncover all design and
implementation flaws that would violate security policy.
• Upon completion of all Development, Integration
and Test Phase tasks and receipt of resources for the next
phase, the Project Manger, together with the project team, should
prepare and present a project status review for the decision maker
and project stakeholders.
The next study unit is on implementation and disposition of system.
6.0 TUTOR-MARKED ASSIGNMENT
Compare and contrast roles and responsibilities during
development phase and integration and testing phases of systems
development.
7.0 REFERENCES/FURTHER READING
Information Resources Management (2003). The Department of
Justice Systems Development Lifecycle Guidance Document.
Norton, P (1995). Introduction to Computers. Macmillan/McGraw-Hill.
95
MBA 815 MANAGEMENT INFORMATION SYSTEM
UNIT 4 IMPLEMENTATION AND DISPOSITION
OF SYSTEM
CONTENTS
1.0 Introduction
2.0 Objectives
3.0 Main Content
3.1 Implementation and Disposition Phases
3.1.1 Implementation
3.1.2 Disposition
3.2 Tasks and Activities
3.2.1 Implementation
3.2.2 Disposition
3.3 Roles and Responsibilities
3.3.1 Implementation
3.3.2 Disposition
3.4 Deliverables
3.4.1 Implementation
3.4.2 Disposition
3.5 Issues for Consideration
3.5.1 Implementation
3.5.2 Disposition
3.6 Phase Review Activity
3.6.1 Implementation
3.6.2 Disposition
4.0 Conclusion
5.0 Summary
6.0 Tutor-Marked Assignment
7.0 References/Further Readings
1.0 INTRODUCTION
From the previous study unit, you have leant about the Development and
Integration and testing phase.
This unit focuses on Implementation and Disposition of system, related
tasks and activities, roles and responsibilities as they concern
system implementation and disposition.
2.0 OBJECTIVES
This unit is designed for you to:
• know what constitutes system’s implementation and
disposition phase in designing and developing information
96