1 / 47

CHAPTER 11 MAKING THE SYSTEM OPERATIONAL

CHAPTER 11 MAKING THE SYSTEM OPERATIONAL. Phase Description. Systems Implementation is the fourth of five phases in the systems development life cycle Includes application development, documentation, testing, training, data conversion, and system changeover

lanaj
Download Presentation

CHAPTER 11 MAKING THE SYSTEM OPERATIONAL

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CHAPTER 11MAKING THE SYSTEM OPERATIONAL

  2. Phase Description • Systems Implementation is the fourth of five phases in the systems development life cycle • Includes application development, documentation, testing, training, data conversion, and system changeover • The deliverable for this phase is a completely functioning information system

  3. Chapter Objectives • Explain the importance of software quality assurance and software engineering • Describe the application development process for structured, object-oriented, and agile methods • Draw a structure chart showing top-down design, modular design, cohesion, and coupling • Explain the coding process • Explain unit, integration, and system testing • Differentiate between program, system, operations, and user documentation • List the main steps in system installation and evaluation

  4. Chapter Objectives • Develop a training plan for each group of participants, compare in-house and outside training, and describe effective training techniques • Describe data conversion and changeover methods • Explain post-implementation evaluation and the final report to management

  5. Introduction • The system design specification serves as a blueprint for constructing the new system • The initial task is application development • Before a changeover can occur, the system must be tested and documented carefully, users must be trained, and existing data must be converted • A formal evaluation of the results takes place as part of a final report to management

  6. Software Quality Assurance • The main objective of quality assurance is to avoid problems or to identify them as soon as possible. • To improve the finished product, software systems developers should consider software engineering and internationally recognized quality standards • Software Engineering-is a software development process that stresses solid design, accurate documentation and careful testing • To achieved that Software Engineering Institute set a standard: • Capability Maturity Model (CMM) • Capability Maturity Model Integration (CMMI) • Process improvement • CMMI tracks an organization's processes, using five maturity layers

  7. Software Quality Assurance • International Organization for Standardization (ISO) • Many firms seek assurance that software systems will meet rigid quality standards • In 1991, ISO established a set of guidelines called ISO 9000-3 • ISO requires a specific development plan • Standard was updated in 2004,now referred as ISO 90003:2004

  8. Overview of Application Development • Application development-the process of constructing the programs and code modules that serve as the building blocks of the information system • Objective is to translate the design into program and code modules that will function properly • Review the System Design • Tasks produced an overall design and a plan for physical implementation

  9. Overview of Application Development • Application Development Tasks • Traditional methods • Start by reviewing documentation from prior SDLC phases and creating a set of program designs • At this point, coding and testing tasks begin • Agile Methods • Intense communication and collaboration will now begin between the IT team and the users or customers • Objective is to create the system through an iterative process

  10. Overview of Application Development • System Development Tools • Entity-relationship diagrams • Flowcharts • Pseudocode • Decision tables and decision trees

  11. Overview of Application Development • Project Management • Even a modest-sized project might have hundreds or even thousands of modules • Important to set realistic schedules, meet project deadlines, control costs, and maintain quality • Should use project management tools and techniques

  12. Structured Application Development • Structure Charts • Show the program modules and the relationships among them • Consist of: • Rectangles-represent the program modules • Arrows and other symbols that provide additional information • Control module-higher level module • Subordinate modules-direct lower level modules • Structure chart symbols represents: • Module • Data Couple • Control Couple • Condition • Loop

  13. An example of structure chart modules

  14. Structured Application Development • Cohesion and Coupling • Cohesion-measures a module’s scope and processing characteristics . • If you need to make a module more cohesive, you can split it into separate units, each with a single function • Coupling describes the degree of independence among modules • Loosely coupled-modules that are independent • Tightly coupled

  15. An example of tightly coupled and loosely coupled structure charts

  16. Structured Application Development • Drawing a Structure Chart • Step 1: Review the DFDs • Review all DFDs for accuracy and completeness • Step 2: Identify Modules and Relationships • Transform functional primitives or object methods into program modules • Three-level structure charts relate to the three DFD levels

  17. Structured Application Development • Step 3: Add Couples, Loops, and Conditions • Identify the data elements that pass from one module to another • Step 4: Analyze the Structure Chart and the Data Dictionary • Ensure that the chart reflects all previous documentation and that the logic is correct

  18. Object-Oriented Application Development • Object-oriented development (OOD) • Characteristics of Object-Oriented Application Development • The application's structure is represented by the object model itself • Implementation of Object-Oriented Designs • Main objective is to translate object methods into program code modules and determine what event or message will trigger the execution of each module • Object-Oriented Cohesion and Coupling • Classes – loosely coupled • Methods – loosely coupled and highly cohesive

  19. Agile Application Development • Is a distinctly different systems development method • Development team is in constant communication with the customer • Focuses on small teams, intense communication, and rapid development iterations • Extreme Programming (XP) is one of the newest agile methods

  20. Agile Application Development • An extreme programming (XP) Example • User story • Release plan • Iteration cycle • Iteration planning meeting • Parallel programming • Test-driven design

  21. Agile Application Development • The Future of Agile Development • Critics claim it lacks discipline and produces systems of questionable quality • Before implementing agile development, the proposed system and development methods should be examined carefully • A one-size-fits-all solution does not exist

  22. Coding • Coding-process of turning program logic into specific instructions that the computer system can execute. • Programming Environments • Integrated development environment (IDE) • Generating Code • Can generate editable program code directly from macros, keystrokes, or mouse actions

  23. Testing the System • Unit Testing • testing of individual program or module • Objective is to identify and eliminate execution errors that could cause the program to terminate abnormally, and logic errors that could have been missed during desk checking • Integration Testing • Testing two or more programs that depend on each other • System Testing • Involves the entire information system • You should regard thorough testing as a cost-effective means of providing a quality product

  24. The first step in testing is unit testing, followed by integration testing and ten system testing

  25. Documentation • Documentation describes an information system and helps the users, managers and IT staff who must interact with it. • Types of documentation: • Program Documentation-describes the inputs, outputs and processing logic for all program modules • System Documentation-describes the system’s functions and how they are implemented • Operations Documentation-contain all the information needed for processing and distributing online and printed output • User Documentation-consist of instructions and information to users who will interact with the system and includes user manual, help screen and tutorials • Systems analysts usually are responsible for preparing documentation to help users learn the system

  26. Documentation • User Documentation • Effective online documentation is an important productivity tool • Written documentation material also is valuable

  27. Management Approval • After system testing is complete, you present the results to management • If system testing produced no technical, economical, or operational problems, management determines a schedule for system installation and evaluation

  28. System Installation and Evaluation • Remaining steps in systems implementation: • Prepare a separate operational and test environment • Provide training for users, managers, and IT staff • Perform data conversion and system changeover • Carry out post-implementation evaluation of the system • Present a final report to management

  29. Operational and Test Environments

  30. Operational and Test Environments • The operational environment includes hardware and software configurations and settings, system utilities, telecommunications resources, and any other components that might affect system performance • If you have to build or upgrade network resources to support the new system, you must test the platform rigorously before system installation begins

  31. Training • Training Plan • The three main groups for training are users, managers, and IT staff • You must determine how the company will provide training • Vendor Training • Training supplied by h/w or s/w vendor • Often gives the best return on your training dollars because it is focused on products that the vendor developed

  32. Examples of training topics for three different groups, users,managers and IT staff members have different training needs

  33. Training • Webinars, Podcasts, and Tutorials • Offer by vendors • Webinars-Internet based training session that provides an interactive experience • Webcast-one way transmission • Podcast –web based broadcast that allows a user to download multimedia files • Subscribers can access the recorded material anywhere, anytime • Tutorials-a series of online interactive lessons that present material and provide a dialog with user • can be developed by software vendors, or by a company’s IT team

  34. Training • Outside Training Resources • Many training consultants, institutes, and firms are available that provide either standardized or customized training packages • In-House Training • The IT staff and user departments often share responsibility

  35. Data Conversion • During data conversion, existing data is loaded into the new system. • Data Conversion Strategies • The old system might be capable of exporting data in an acceptable format for the new system or in a standard format such as ASCII or ODBC • If a standard format is not available, you must develop a program to extract the data and convert it • Often requires additional data items, which might require manual entry

  36. Data Conversion • Data Conversion Security and Controls • You must ensure that all system control measures are in place and operational to protect data from unauthorized access and to help prevent erroneous input • Some errors will occur • It is essential that the new system be loaded with accurate, error-free data

  37. System Changeover

  38. System Changeover • System change over is the process of putting the new information system online and retiring the old system. • Direct Cutover • Changeover from the old system to the new system to occur immediately when the new system becomes operational. • Involves more risk than other changeover methods • Companies often choose the direct cutover method for implementing commercial software packages • Cyclical information systems usually are converted using the direct cutover method at the beginning of a quarter, calendar year, or fiscal year

  39. System Changeover • Parallel Operation • Requires that that both the old and the new information systems operate fully for a specified period • Ata is input to both systems, and output generated by the new system is compared with the equivalent output from the old system • When users, management and IT group are satisfied that the new system operates correctly,the old system is terminated. • Easier to verify that the new system is working properly under parallel operation than under direct cutover • Running both systems might place a burden on the operating environment and cause processing delay • Is not practical if the old and new systems are incompatible technically • Also is inappropriate when the two systems perform different functions

  40. System Changeover • Pilot Operation • Involves implementing the complete new system at a selected location of the company • The group that uses the new system first is called the pilot site • The old system continues to operate for the entire organization • After the system proves successful at the pilot site, it is implemented in the rest of the organization, usually using the direct cutover method • Is a combination of parallel operation and direct cutover methods

  41. System Changeover • Phased Operation • Implement the new system in stages or modules • You give a part of the system to all users • The risk of errors or failures is limited to the implemented module only • Is less expensive than full parallel operation • Is not possible, however, if the system cannot be separated easily into logical modules or segments

  42. Relative risk and cost characteristics of the four changeover methods

  43. Post-Implementation Tasks • 2 tasks to do after new system is operational • Post-Implementation Evaluation • Deliver final report to management Post-implementation evaluation • A post-implementation evaluation should examine all aspects of the development effort and the end product — the developed information system • You can apply the same fact-finding techniques in a post-implementation evaluation that you used to determine the system requirements during the systems analysis phase

  44. Post-Implementation Tasks • Final Report to Management • Your report should include the following: • Final versions of all system documentation • Planned modifications and enhancements to the system that have been identified • Recap of all systems development costs and schedules • Comparison of actual costs and schedules to the original estimates • Post-implementation evaluation, if it has been performed

  45. Chapter Summary • The systems implementation phase consists of application development, testing, installation, and evaluation of the new system • Analysts and technical writers also prepare operations documentation and user documentation • Develop a training program • A post-implementation evaluation assesses and reports on the quality of the new system and the work done by the project team

  46. Chapter Summary • The final report to management includes the final system documentation, describes any future system enhancements that already have been identified, and details the project costs • The report represents the end of the development effort and the beginning of the new system’s operational life • Chapter 11 complete

  47. Review Questions • Describe structure charts and symbols • Define cohesion and coupling • Define unit testing, integration testing and system testing • Who must receive training before a new information system is implemented? • What is the purpose of documentation? State 4 types of documentation. • What is the purpose of operational environment and a test environment? • List and describe the four system changeover methods. • Which of the system change over is the most expensive? explain your answer • Which is the riskiest? Explain your answer.

More Related