1쪽
16 Chapter 16: Making the System Operational Systems Analysis and Design in a Changing World, 3rd Edition www.goupee.com
자료 내용
2쪽
16 Learning Objectives Describe implementation and support activities Choose an appropriate approach to program development 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
3쪽
16 Learning Objectives (continued) List various approaches to data conversion and system installation and describe the advantages and disadvantages of each Describe different types of documentation and the processes by which they are developed and maintained Describe training and user support requirements for new and operational systems Systems Analysis and Design in a Changing World, 3rd Edition 3
4쪽
16 Overview This chapter focuses on activities of implementation and support phases of systems development life cycle (SDLC) Implementation activities occur before system is turned over to users Implementation consumes more time and resources than earlier phases of the SDLC Support activities occur after system becomes operational and may continue for years Systems Analysis and Design in a Changing World, 3rd Edition 4
5쪽
16 Activities of the Implementation and Support Phases www.goupee.com Systems Analysis and Design in a Changing World, 3rd Edition 5
6쪽
16 Program Development 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 quality Systems Analysis and Design in a Changing World, 3rd Edition 6
7쪽
16 Order of Implementation Input, process, output (IPO) development order Based on data flow through system Simplifies testing User interfaces developed early to reduce change Disadvantage is late implementation of outputs Structured design – IPO order based on system flowchart and structure chart OO design – IPO order in package diagrams Systems Analysis and Design in a Changing World, 3rd Edition 7
8쪽
16 Order of Implementation (continued) Top-down and bottom-up order from traditional structured design and structured programming Top-down begins with top structure chart module Always a working version of program Requires three or more iterations to complete Bottom-up begins with modules at lowest level of structure chart Many programmers can begin immediately Requires driver programs to test Systems Analysis and Design in a Changing World, 3rd Edition 8
9쪽
16 System Flowchart for a Payroll System Systems Analysis and Design in a Changing World, 3rd Edition 9
10쪽
16 Structure Chart for a Payroll System Systems Analysis and Design in a Changing World, 3rd Edition 10
11쪽
16 Package Diagrams for RMO Subsystems Systems Analysis and Design in a Changing World, 3rd Edition 11
12쪽
16 Package Diagram for Three-Layer OO Systems Analysis and Design in a Changing World, 3rd Edition 12
13쪽
16 Construction and Test Plan Development order Testing order Data used to test modules, module groups, methods, classes, programs, and subsystems Acceptance criteria Relevant personnel assignments (construction and testing) Systems Analysis and Design in a Changing World, 3rd Edition 13
14쪽
16 Framework Development When developing large OO systems, object frameworks or foundation classes are often constructed Foundation classes typically implemented first Minimizes impact of errors and changes Reused in many parts of the system and across applications Assigned to best programmers and thoroughly tested Systems Analysis and Design in a Changing World, 3rd Edition 14
15쪽
16 Team-Based Program Development Management Issues Organization of programming teams Task assignment to specific teams or members Member and team communication and coordination Variety of different models used for organization Systems Analysis and Design in a Changing World, 3rd Edition 15
16쪽
16 Comparison and Summary of Development Team Types Systems Analysis and Design in a Changing World, 3rd Edition 16
17쪽
16 Source Code Control Source code control system (SCCS) Automated tool for tracking source code files and controlling changes to those files Repository of code and programmer actions Check out file in read-only mode Check out file in read/write mode Check in a modified file Systems Analysis and Design in a Changing World, 3rd Edition 17
18쪽
16 Versioning Mechanism to manage systems changes Complex systems developed, installed, and maintained in series of versions to simplify testing and support Alpha Version – incomplete testing version Beta Version – end user testing version Production Release Version – formally distributed to users or made operational Maintenance Release – bug fixes, small changes Systems Analysis and Design in a Changing World, 3rd Edition 18
20쪽
16 Quality Assurance Process of ensuring information system meets minimum quality standards Determined by users, implementation staff, management Identification of gaps or inconsistencies in systems requirements QA integrated into project throughout SDLC Cost of fixing errors rise as project progresses Systems Analysis and Design in a Changing World, 3rd Edition 20
앞 20페이지만 표시됩니다. 전체를 보려면 자료를 다운로드하세요.
댓글 (0)
댓글이 없습니다. 첫 댓글을 남겨보세요!