Chapter 11:

Managing System Implementation

Learning outcomes:
Explain quality assurance and three techniques to help improve the finished product

Outline application development

Explain unit, integration and system testing

Differentiate between program, system, operations and user documentation

Explain the role of online documentation

Describe the five tasks involved in system installation

Side note: there are sections of this textbook that discusses structured development, object-oriented development,
agile development and coding. However based on the learning outcomes of the module, these are not part of the
syllabus.
Quality assurance
Quality assurance is to avoid problems or to identify them as soon as possible.
 inaccurate requirements, design problems, coding errors, faculty documentation, ineffective testing

1. Software Engineering – is the disciplined application of engineering principles to be creation of

complex, long-lived applications.
1. Combination of people, process and technology.
2. 5 technical activity areas: requirement, design, construction, testing and maintenance and evolution.
3. Nontechnical activities :cost, effort estimation, project management and process improvement
4. Capability Maturity Model (CMM) – improve software quality, reduce development time and cut costs.
5. Capability Maturity Model Integration (CMMI) – integrates software and system development into a larger
framework. Uses levels (1 bad to 5 optimal)

2. System Engineering – not only builds upon software engineering but includes other parts of
system such as hardware, networks and interfaces.
1. Heart of new created systems.
2. Responsible for concept, architecture and design. Analyse complexity and risk. Decide if system successful or
not.

3. International Organisation for Standardization (ISO) – global consensus of what constitutes

good management practices that can help firms deliver consistently high-quality products and
services.
1. Software is ISO 9000-3:2014
2. International standard for development of software.
Application Development
Application development is the process of constructing the programs and code modules that serve as
building blocks of the information system.
1. Review the system Design – look at the previous chapters and their intentions
2. Application Development tasks – traditional approach vs agile. Its about taking the project breaking
it into smaller pieces and start by designing, coding, testing and documenting. Or if you use agile,
intense interaction with the users.
3. System Development tools – structured relies on DFD and structured charts, OO relies on UML
diagrams, Agile uses spiral model. Generic tools include: ERD, flowchart, pseudocode, decision
tables and decision trees.
Structured Development Object-Oriented Agile Development
Development
Break system into smaller pieces = UML diagrams 4 key values of Agile:
partitioning

Top down approach Also has coupling and cohesion Individuals and interaction over process and
Modular design (small pieces that are tools
numbered like DFD)
Structured chart has: Modules that Working software over comprehensive
documentation

Data couple – passing data between Customer collaboration over contract

modules negotiations

Control couple – specifies a condition when Respond to change over following a plan
passing data between modules

Condition – control module determines Has XP(extreme programming) – two people

which subordinate module is invoked based working on the same machine and code
on conditions.
Loop – one or more modules repeating User stories – short, simple, requirement
definition.

Cohesion – merging similar modules Iteration and release – release plan, when
Coupling – linking everything is not a good will story be implemented (prototype),
thing iteration cycle is planning, designing, coding
and testing feature based on story
1. Review DFD
2. Identify modules and relationships
3. Ass couples, loops and conditions
Testing
Unit testing – individual program or module
 test plan – tests out all different scenarios with the various data to identify defects/errors

Integration testing – testing two or more programs that are dependent on each other
System testing – involves the entire information system
Objectives of system testing:
 Perform final test of all programs
 Verify system will handle input data properly (valid and invalid)
 Ensure IT staff have documentation and instruction needed to operate system
 Backup and restart capabilities are adequate
 Show that users can work with the system successfully
 Verify components are properly integrated and actual processing situation will be correctly handled
 Confirm IS can handle predicted volume in a timer and efficient manner
How much testing is needed? Depends on the results and how urgent the system is needed. No system will
be 100% cleared of defects/errors but it will determine if the system is installed or not.
Documentation
Program documentation describes the input, output and processing logic for all program modules.
 Starts in analysis and continues throughout implementation
 Defect tracking software / bug tracking – document and track program defects, code changes and patches/replacement
code.

System Documentation describes the system’s functions and how they are implemented
 Data dictionaries, DFD, screen layouts, source documents

 Created by SA and reviewed constantly to ensure the system is correct

Operations Documentation contains all the information needed for processing and distributing
online and printed output.
◦ Must be clear, concise and available online

◦ Created by SA but must be previewed often by IT department to ensure system on track

User documentation consists of instructions and information to users who will interact with the
system and includes user manuals, help screens, and online tutorials.
◦ Should not just be thrown together, the skill is not the same as someone who develops the system

Online documentation provides immediate help when they have questions or encounter problems.
◦ 2 issues: document can be created quickly and will be useless or it can take time which can cause a delay
Installation
Tasks that need to be done (whether in-house or purchased):
1. Prepare operational and test environment – environment/platform – hardware and software
1. Separate test environment to maintain security and integrity and protect operational environment. (on its own
server in IT department)
2. Access to the test environment is limited to IT staff and operational environment to users, so that there are no
mistakes made.

2. Perform System change over

1. Direct cutover- end the old one, begin the new one. Cheap but risky
2. Parallel operation – old and new operate fully for a certain period of time. Cut old one once new one
proves it can maintain. Expensive (running two systems), extra employees to handle new/old system,
processing delays as it burdens operating environment.
3. Pilot operations – implementing complete new system at a selected location. Old system works
everywhere as normal and once new system is maintaining, the new system is directly implemented
over the whole company. It’s a combination of parallel and direct.
4. Phased operations – phase in new system in stages. Each subsystem can be implemented either
directly / pilot/parallel. Risk of failure is low and less expensive.
Installation
3. Perform Data conversion
 Existing data is loaded into the new system
 Can be done before, after or during operational environment is complete.
 Must be done early and tested
 Old system should be able to transfer data over to new system using Open database connectivity (ODBC)
 Replacing a manual system means manual input of data
 Must have security and even if careful there can be issues

4. Provide training for users, managers and IT staff

 Need a training plan – right training for the right people at the right time
 Different levels (users, managers and IT staff) have different needs of training
 Vendor training – its either part of the service or extra cost, either at vendor location or user, might need to supplement vendor
training if you have some in-house programs
 Webinars -group of preregistered users and an instructor, interactive experience
 Podcasts -web-based broadcast that allows multimedia file downloads, not live, can access anytime anywhere
 Tutorials – series of online interactive lessons, presents material and provide dialog with users.
 Outside training resources – like universities
 Training tips – if there is a helpdesk, maybe they can train the users. Use multimedia as a method.
 Following guidelines when developing a training program:
 Train people in groups, with separate training programs for distinct groups
 Select the most effective place to conduct the training
 Provide for learning by hearing, seeing, and doing
 Rely on previous trainees
 Interactive Training – this is best form of training but cost sometimes doesn’t allow it
 Online training – this is when there is actual documentation of the actual system online to assist / AI to answer questions
Installation
5. Carry out post-implementation tasks
1. Post-implementation evaluation – assesses the overall quality of the IS.
Feedback on the following areas (also for future projects):
1. Accuracy, completeness, timeliness of IS output
2. User satisfaction
3. System reliability and maintainability
4. Adequacy of system controls and security measures
5. Hardware efficiency and platform performance
6. Effectiveness of database implementation
7. Performance of IT team
8. Completeness and quality of documentation
9. Quality and effectiveness of training
10. Accuracy of cost-benefit estimates and development schedules
Fact-find techniques – interviews, observation, read documentation, examine source documentation,
questionnaires, analyse held desk logs.
When to do this? Not too early, user wont have the experience and not too late, user would have forgotten.
2. Deliver final report to management
Should include:
3. Final version of documentation
4. Planned modifications and enhancements to the system that has been identified
5. Recap all system development costs and schedules
6. Compare actual costs and schedule to original estimates
7. Post-implementation evaluation
Conclusion
Quality assurance and three techniques to help improve the finished product is identified

Application development is briefly outlined

Unit, integration and system testing is listed and briefly explained

Program, system, operations and user documentation is differentiated

The role of online documentation is listed

The five tasks involved in system installation is described

Side note: there are sections of this textbook that discusses structured development, object-oriented
development, agile development – SLIDE 5 and coding. However based on the learning outcomes of the module,
these are not part of the syllabus.