Lecture Chapter 16: Making the system operational

Lecture "Chapter 16: Making the system operational" provides students with the knowledge: Program development, order of implementation, structure chart for a payroll system, system flowchart for a payroll system, construction and test plan,...Invite you to consult.

Nội dung trích xuất từ tài liệu:
Lecture Chapter 16: Making the system operational 16 16 Learning Objectives Chapter 16:  Describe implementation and support activities Making the System Operational  Choose an appropriate approach to program development Systems Analysis and Design in a Changing World, 3rd Edition  Describe various types of software tests and explain how and why each is used Systems Analysis and Design in a Changing World, 3rd Edition 2 16 16 Learning Objectives (continued) Overview  List various approaches to data conversion and  This chapter focuses on activities of system installation and describe the advantages implementation and support phases of systems and disadvantages of each development life cycle (SDLC)  Implementation activities occur before system is  Describe different types of documentation and turned over to users the processes by which they are developed and maintained  Implementation consumes more time and resources than earlier phases of the SDLC  Describe training and user support requirements for new and operational systems  Support activities occur after system becomes operational and may continue for yearsSystems Analysis and Design in a Changing World, 3rd Edition 3 Systems Analysis and Design in a Changing World, 3rd Edition 4 16 16 Activities of the Implementation Program Development and Support Phases  Program development is time consuming  One-third of development labor  One-third to one-half of project development schedule  Programming and testing considerations:  Required resources  Managerial complexity  System qualitySystems Analysis and Design in a Changing World, 3rd Edition 5 Systems Analysis and Design in a Changing World, 3rd Edition 6 16 16 Order of Implementation Order of Implementation (continued)  Input, process, output (IPO) development order  Top-down and bottom-up order from traditional  Based on data flow through system structured design and structured programming  Simplifies testing  Top-down begins with top structure chart module  User interfaces developed early to reduce change  Always a working version of program  Disadvantage is late implementation of outputs  Requires three or more iterations to complete  Structured design – IPO order based on system  Bottom-up begins with modules at lowest level of flowchart and structure chart structure chart  OO design – IPO order in package diagrams  Many programmers can begin immediately  Requires driver programs to testSystems Analysis and Design in a Changing World, 3rd Edition 7 Systems Analysis and Design in a Changing World, 3rd Edition 8 16 16 System Flo ...