Implementation and Training

Implementation and Training - Implementation and Training...

Info iconThis preview shows pages 1–2. Sign up to view the full content.

View Full Document Right Arrow Icon
Implementation and Training System Implementation | Coding and Testing | Types of Testing | Implementation Approaches | Planning the Installation and Training | Planning for Success | Designing Forms and Reports | Assessing Usability | Designing for e-Commerce | Designing Interfaces and Dialogues | Summary | Study Tools System Implementation Implementing a system is typically the most expensive and time consuming phase after maintenance (which is not covered in this class). Regardless of the methodology (traditional, OO, or agile), once the coding and testing are complete, the application must be installed; this includes purchased packages such as ERP (Enterprise Resource Planning) Systems. System implementation may be combined or done in parallel with new process implementation, organizational changes, or other activities performed by the user community to prepare themselves for the new system. A key activity during the later part of implementation is the development of user training. The six major activities of implementation are coding, testing, installation, documentation, training, and support. We will cover coding and testing briefly, then study installation, documentation, and training more in-depth, and lastly we will cover support. Coding and Testing How code is generated for the application can take on many forms, and specific programming languages are covered in other classes. Testing can be integrated with coding when using agile methods including eXtreme Programming, or they can be separate activities in large organizations using traditional methods. In some environments, it is the programmers and business users who do the testing; in other environments, there may be a separate staff that does the testing based on scripts created by the user base. The goal of coding and testing is to convert the detailed design specifications into a working system, free of errors. As part of coding and then validated through testing, documentation (both system and user) is created. It is better to create documentation as you go rather than try to go back and create the documentation post-implementation. In fact, one approach to requirements specifications, particularly when major business processes are being changed, is to create the user documentation before the detailed specifications. The users can then validate the processes in the context of the system. Of course, you would need to include detailed designs for forms, reports, and Web pages in the user documentation. Types of Testing Testing computer code -- no matter whether it is generated through some type of CASE or programming language or it is a purchased software package -- is a key to a successful implementation. The testing process has evolved into a major skill set and, as mentioned above, many organizations have a dedicated group of testers. The first type of testing is normally done by the person creating the code with, perhaps, help from peers. Desk checking is a process in which the programmer reviews the code visually in an attempt to catch any obvious errors. Inspections and
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 2
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 08/02/2009 for the course BIS 360 taught by Professor Price during the Summer '09 term at DeVry Cincinnati.

Page1 / 5

Implementation and Training - Implementation and Training...

This preview shows document pages 1 - 2. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online