Systems Development - Systems Implementation
Learning Outcomes:
Systems inplementation
- Design and prepare computer-based solutions.
- Explain different types of testing and their uses.
- The types included are unit testing, system testing and acceptance testing.
- Design a simple test plan for functionality of parts of a system.
Systems conversion and maintenance
- Compare different strategies of systems conversion.
- The strategies included are pilot conversion, phased conversion, parallel conversion and direct cutover conversion.
- Explain the need for ongoing maintenance, upgrading and training.
Systems documentation
- Differentiate different types of documentation and their purposes.
- The types included are system documentation, technical documentation and user manuals.
- Document the processes and specifications.
- The examples of documentation are requirement statements, project plans and design plans.
The personnel
- Identify various job titles for different stages of systems development.
Systems implementation
Sequence of testing: unit test à system test à
user acceptance test
- Unit test: Check if each module functions as expected. Done by developer.
- System test: Check if the whole system functions as expected, after integration. Done by developer.
- User acceptance test: Check if the system fulfills user’s requirements. Users are involved.
Relevant past paper:
DSE ICT Elect B(SP-2017): 2012 2ci. 2014 1ai-iii. 2017 3c.
AL CS2(2003-2012): 2008 9f. 2012 2bc.
Learn more (integration test): AL CS2 2012 2a.
Systems conversion and maintenance
|
Approaches |
Advantages |
Disadvantages |
|
Pilot conversion: Implementation of new system in a small section of a
company first (pilot area), before promoting to other sections |
If problem arises, only a small section of the company
affected |
Take more time |
|
Phased conversion: The new system is divided into smaller parts (modules) and
introduced to the existing system in parts, one at a time |
Get used to the system gradually |
Take more time |
|
Parallel conversion: Old and new system operate simultaneously for a certain period
of time |
Failure of new system has lowest impact |
Highest cost (more equipment and personnel needed), data
inconsistency may arise |
|
Direct cutover conversion: Implementation of new system and discontinuation of old
system |
Lowest cost |
If problem arises, the whole system may be affected |
System maintenance:
- correct errors in the system, enhance the functions of the system
- Mode of user training: online teaching, face-to-face, self-study
Relevant past paper:
DSE ICT Elect B(SP-2017): SP 4f. PP 2cii. 2012 2cii.
AL CS2(2003-2012): 2006 3b. 2009 9f. 2012 8e.
Systems documentation
- System documentation: Overview of the system. Usually contains the requirements, design, coding, maintenance, etc. information.
- Technical documentation: Intended for technical maintenance of the system. Contains information such as source code and data flow.
- User manuals: instructions for users on how to use the system.
Relevant past paper:
DSE ICT Elect B(SP-2017): 2015 2bii.
AL CS2(2003-2012): -
Personnel
- Project manager: monitor and coordinate the whole project.
- System analyst: define the user requirements and translates them into requirement specification.
- Programmer: write the code according to requirement specification and test the code.
Relevant past paper:
DSE ICT Elect B(SP-2017): SP 4d. PP 4e.
AL CS2(2003-2012): 2006 10g.
References:
https://www.techbeamers.com/testing-types/
http://archives.cpajournal.com/old/09626913.htm
https://www.teach-ict.com/as_a2_ict_new/ocr/A2_G063/331_systems_cycle/slc_stages/miniweb/pg22.htm
No comments:
Post a Comment