110 likes | 216 Views
CIS 210 Systems Analysis and Development. ,. Week 9 Part I System Implementation. Objectives . Upon completion of part I you will be able to: Understand and be able to explain the concepts related to coding and testing during system implementation
E N D
CIS 210Systems Analysis and Development , Week 9 Part I System Implementation
Objectives • Upon completion of part I you will be able to: • Understand and be able to explain the concepts related to coding and testing during system implementation • Understand and be able to create a test plan • Understand and be able to explain the concepts related to four installation strategies: direct, parallel, single location, and phased installation • Understand and be able to creating a training plan for users during system implementation • Understand and be able to explain the common issues related to system implementation • Understand and be able to explain the concepts related to factor and political models of the implementation process
Overview • Implementation Phase • Very Expensive • Not a mechanical process • Shaped by people • History • Politics • Environmental demands • Testing • Installation • Documentation • Training
SystemImplementation • Coding, Testing and Installation • Process • Deliverables • Code, • Program documentation • Test scenarios and test data • Results of program and systems testing • User guides • A user training plan • A installation and conversion plan • Documentation, Training, and Support • Process • Deliverables • System documentation • User documentation • Classes • Tutorials • Training materials • Computer-based training aids • A help desk • Online help • Bulletin boards and other support mechanisms
SoftwareApplication Testing • Overview • Purpose of tests • Master test plan • Testing managers • Testing specialists • Types of Testing • Inspection • Walk-through • Desk checking • Unit testing • Integration testing • System testing • Stub testing
SoftwareApplication Testing • The Testing Process • Confirm requirements met • Testing must be planned • Test case • Combining Coding and Testing • Test soon after code is generated • Acceptance testing • Alpha • Beta • System audit
Installation • Approaches to Installation • Direct • Parallel • Single-location • Phased • Planning for Installation • Software • Hardware • Documentation • Work methods • Offices
Documentation • Types of Documentation • System • Design specifications • Internal workings • Functionality • Internal system documentation • External system documentation • User • Written or visual • How system works • How to use it
Training and Supporting Users • Training Topics • System use • Computer concepts • IS concepts • Organizational information • System management • Installation • Methods of Delivery • Tutorials • Courses • Computer-aided instruction • Interactive training manuals • Resident expert • Software help • Externals sources • Support • Automated • Help desk
OrganizationalIssues • Characteristics of success • Conventional wisdom • Management support • Involvement of users • Factors models • Ginzberg • Commitment to change and the project • Extent of project definition and change • User expectations • Lucas • User’s personal stake • System characteristics, • User demographics • Organizational support • Performance • Satisfaction • Political models • Self-interested goals • Power distribution
Summary • The coding, testing, and installation process • The documentation, training, and support process • Types of testing • Combining coding and testing • Approaches to installation • Planning for installation • Types of documentation • Training topics • Methods of training delivery • User support • Implementation success factors