System Implementation: SDLC Phase 4

1. System Implementation:SDLC Phase 4 Dr. Dania Bilal IS 582 Spring 2007

2. Steps in System Implementation:SDLC Phase 4 • Coding • Testing • Installation • Documentation • Training • Support • Maintenance • Evaluation

3. Purpose of Implementation • Convert the physical system specifications into working and reliable software and hardware • Document the work that has been completed • Provide assistance to users of system

4. Operations to Understake • From system design to operation • Coding, testing, and installation • Successful operation of the system • Documentation, training, and support • On-going operation of the system • Maintenance

5. Coding • Process whereby the physical design specifications created by system developers are turned into working computer code by the programming team

6. Testing • Can begin as coding for each module is completed • Modules can be tested individually and as part of the larger program • Need to determine what to be tested and collect test data during both planning and implementation

7. Software Testing • How to do it? • Check each module’s proper operation • Check each peripheral (e.g., printers, scanners) to see how well it works with the software • Make a list of the problems you encounter during testing and relay them to the vendor if you cannot solve them.

8. Site Preparation • Selection and placement of hardware • Computer stations • Lookup stations and placement • Number of stations • Administrative stations • Number of stations

9. Site Preparation • Facility design • Evaluation of existing layout (revisit) • ADA requirements • Cables, wires, etc. for the LAN • Evaluation of existing hardware (revisit)

10. Site Preparation • Selection and placement of hardware • Printers • Number of printers needed • Furniture • Standards (K-12) • Ergonomics • Users with special needs

11. Approaches to Installation • Direct installation (for new system) • Parallel installation (old and new system coexist) • Single location installation (pilot approach by selecting pilot sites) • Phase installation (staged, incremental based on system functional components)

12. Documentation • Two types • System documentation • User documentation

13. System Documentation • Detailed information about a system’s design specifications, its internal workings, and its functionality • Internal (part of the program source code) • External (all diagramming techniques such as data flow diagrams and entity relationship diagrams)

14. User Documentation • Manual containing information about how the application system works and how to use it. • May include all or most of these: • quick reference guide, user’s guide, release description (for a new version), system’s administrator’s guide, index, help, etc.

15. Training • Staff training • On-site via software vendor (fee-based) • All staff? • A group of staff • Off-site via software vendor (fee-based) • Senior staff join other staff undergoing training

16. Training • Staff training • Self-training • Training others • Frequency of training • Evaluation

17. Training • User training • When to do it? • How to do it? • Group presentations • Web-based tutorial (self-paced) • Class-integrated • One-on-one

18. Training • User training • Frequency of training • Initial (new system) • Subsequent training • System update • System migration (new training)

19. Support • Answer user questions about system • Assist with wide range of computer needs and system access • Provided through a help desk and online • Local support • Vendor technical support

20. Maintenance • Environmental care • Endpoints of LAN (e.g., cabling) to be placed in a secure wiring closet • Safety for staff and users • Hardware safety

21. Maintenance • Environmental care • Humidity: not to exceed 80% • Hardware devices to be placed in cool and secure areas • Hardware to be isolated from moisture, mold, and water

22. Maintenance • System backup • Back up the files daily and weekly • Make more than one backup copy • Keep one backup copy outside of the library/agency for security purposes • Make sure you have a UPS device

23. Maintenance • System security • Install firewalls to protect the system/network from breaching into by computer hackers • Install virus protection software • Install locking devices to prevent theft of hardware (questionable!)

24. Maintenance • System security • Have a security system to protect theft of materials • Use Library Technology Reports to review and evaluate security systems • Vendors of security systems/devices (see Text, p. 119; look up the topic on the Web)

25. Evaluation of System Use • Diagnosing problems • OPAC use • MARC records • Circulation records • Other areas

26. Evaluation of System Use • Keeping statistics • Collection use, circulation, cataloging, etc. • Transaction logs (OPAC) Some systems provide transaction logs of all types of searches performed in the OPAC. You will be able to extract data about successful and unsuccessful searches to diagnose problems.

27. Evaluation of System Use • Benefits of keeping statistics • Collection development • Staffing (scheduling) • Need for hardware (computer stations, printers, etc.) • Training (type and extent) • Meeting state requirements • Usability studies

28. Database Maintenance • Database clean-up (after installation and on a regular basis thereafter) • Cataloging database (MARC 21 records) • Accuracy & completeness during Recon • See Bilal, pp. 122-124. • Patron database • Other databases, as applicable