Systems analysis and design methods 7th whitten and benley chapter 17

58 233 0
Systems analysis and design methods 7th whitten and benley chapter 17

Đang tải... (xem toàn văn)

Tài liệu hạn chế xem trước, để xem đầy đủ mời bạn chọn Tải xuống

Thông tin tài liệu

Systems Implementation Introduction  The chapter will address the following questions:    What is the systems implementation process in terms of the construction and delivery phases of the life cycle? Can you describe the systems implementation phases in terms of your information building blocks? Can you describe the systems implementation phases in terms of purpose, activities, roles, inputs and outputs, techniques, and steps? Systems Implementation What is Systems Implementation?  What is Systems Implementation?  Systems implementation is the construction of the new system and the delivery of that system into production (meaning day-today operation) Systems Implementation Operational System Construction Phase Documentation Delivery Phase Documentation Repository Approval to Continue Project System Owners/Users Production Information System Systems Implementation The Construction Phase of Systems Implementation  Introduction   The purpose of the construction phase is twofold:  To build and test a functional system that fulfills business and design requirements, and  To implement the interfaces between the new system and existing production systems The project team must construct the database, application programs, user and system interfaces, and networks  Some of these elements may already exist (subject to enhancement) Systems Implementation INFORMATION SYSTEMS FRAMEWORK FOCUS ON SYSTEM DATA FOCUS ON SYSTEM PROCESSES FOCUS ON SYSTEM INTERFACES Database Scehma Application Schema FAST Methodology FOCUS ON SYSTEM GEOGRAPHY SYSTEM OWNERS (scope) S Y S T E M A N A L Y S T S SYSTEM USERS (requirements) SYSTEM DESIGNERS (specification) (components) Initi at ion Routine Pr oces s an Orde r Shutdown Rout ine G et an Order Val idate an Orde r Fil e an O rder CREATE TABLE CUSTOMER (customer_no CHAR(10) NOT NULL customer_name CHAR(32) NOT NULL customer _rating CHAR(1) NOT NULL balance_due DECIMAL(5,2) CREATE INDEX cust_no_idx on CUSTOMER CREATE INDEX cust_rt_idx on CUSTOMER Database Technology (and standards) Network Schema Cust omer Fo rm New Cus tomer Logon Ord er Acce pted Change of Addre ss New Order Communications Controller St Louis Mainframe NT Server LA Order Help Complete O rder Fo rm Request Order He lp ORDER_PRODUCT ORDER order_no [Alpha(12)] INDEX ORDER.order_no order_date [Date(mmddyyyy) PRODUCT.product_no quantity_ordered [Integer(2) CUSTOMER.custom er_no Database Structures SYSTEM BUILDERS Interface Schema O rder Processing Pr ogram PRODUCT CUSTOMER product_no [Alpha(10)] INDEX customer_no [Alpha (10)] INDEXproduct_name [Alpha(32)] customer_name [Alpha(32)] unit_of_measure [Alpha(2)] customer_rating [Alpha(1)] INDEX unit_price [Real(3,2)] balance_due [Real(5,2)] quantity_available [Integer(4 )] Check Cus tome r Credit Che ck Product Data Cust ome rs Product s Check Credit Data Rel ease an O rder Help + First Order Request Product Lookup PBX NT Server NY Et hernet LAN/NT Ethernet LAN/NT Request Product Lookup Help Indy AIX Server Product Lookup Help C omplet e Or de rs Application Programs Pro duct Lookup Component Programs VALIDATE_AN_ORDER REPEAT UNTIL NO_MORE_ORDERS PERFORM CUSTOMER_VALIDATIO REPEAT UNTIL NO_MORE_ORDER PERFORM PRODUCT_VALIDATI END REPEAT PERFORM CREDIT_CHECK IF CREDIT_CHECK 'BAD' THEN On Event Help.ButtonClick Do Change Focus HelpDialog On Event OKButton Do Begin {proecdure} End On Event CancelButton Do Interface Technology Software (and Hardware) Technology Client PC Client PC Client PC Client PC Enternet LAN AIX/Lan Manager Network Programs Create AccountType = SalesClerk Set OrderDir.Rights=full Set CustomerDir.Rights=full Set ProductDir.Rights=read Set OrderAppDir.Rights=copy Networking Telchnology (and standards) (and standards) (and standards) Construction Phase Systems Implementation System Owners Approval to continue project Build and Test Networks Installed Network The Business New Databases Quality Assurance Group Network Network Design Details Requirements Revised Database Schema and Test Data Details Program Documentation Quality Recommendations and Requirements Write and Test New Programs DatabaseDesign Requirements Repository Integration Requirements & Program Documentation Technical Design Statement, Plan For Programming, and Test Data Build and Test Databases Modified S/W Specs and New Integration Requirements Database Structure Sample Data Install and Test New Software Package Software Packages and Documentation Production Databases System Vendors Software Package Program Documentation New Programs & Reusable S/W Components Reusable Software Components Software Library Systems Implementation The Construction Phase of Systems Implementation  Activity: Build and Test Networks (if Necessary)   Purpose:  The purpose of this activity is to build and test new networks and modify existing networks for use by the new system Roles:  This activity will normally be completed by the same system specialists that designed the network(s) • System Owners and system users - not involved in this activity • System analyst - The systems analyst’s role is more in terms of a facilitator and ensures that business requirements are not compromised by the network solution • Network designer - The network designer is a specialist in the design of local and wide area networks and their connectivity Systems Implementation The Construction Phase of Systems Implementation  Activity: Build and Test Networks (if Necessary)  Roles: (continued) • System builders – Network administrator - This person has the expertise for building and testing network technology for the new system He/she will also be familiar with network architecture standards that must be adhered to for any possible new networking technology  Prerequisites (Inputs):  This activity is triggered by the approval from the system owners to continue the project into systems design  The key input is the network design requirements defined during systems design Systems Implementation The Construction Phase of Systems Implementation  Activity: Build and Test Networks (if Necessary)   Deliverables (Outputs):  The principle deliverable of this activity is an installed network that is placed into operation  Network details will be recorded in the project repository for future reference Applicable Techniques:  Skills for developing networks are becoming an increasingly important skill for systems analyst especially given the industry trend toward downsizing existing applications Systems Implementation The Construction Phase of Systems Implementation  Activity: Build and Test Networks (if Necessary)  Steps:  The following steps are suggested to complete this activity • Step - Review the network design requirements outlined in the technical design statement developed during systems design • Step - Make any appropriate modifications to existing networks and/or develop new networks • Step - Revise network specifications for future reference 10 Systems Implementation The Delivery Phase of Systems Implementation  Activity: Install Databases   Purpose:  The purpose of this activity is to populate the new systems databases with existing data from the old system Roles:  This activity will normally be completed by application programmers • System Owners and system users - are not involved in this activity • System analysts and designers - may play a small role in completing this activity Their primary involvement will be the calculation of database sizes and estimating of time required to perform the task of installing them 44 Systems Implementation The Delivery Phase of Systems Implementation  Activity: Install Databases  Roles: (continued) • System builders - play a primary role in this activity – Application programmers - will write the special programs to extract data from existing databases and programs to populate the new databases – Date entry personnel or hired help - may be assigned to data entry for data that needs to be keyed  Prerequisites (Inputs):  Existing data from the production databases, coupled with the database schema(s) models and database structures for the new databases will be used to write computer programs to populate the new databases with restructured existing data 45 Systems Implementation The Delivery Phase of Systems Implementation  Activity: Install Databases   Deliverables (Outputs):  The principle deliverables of this activity is the restructured existing data that has been populated in the databases for the new system Applicable Techniques:  Database and application programming skills are essential to the successful completion of this activity 46 Systems Implementation The Delivery Phase of Systems Implementation  Activity: Install Databases  Steps:  The following steps are suggested to complete this activity • Step - Review the database structures for new databases • Step - Identify existing data currently in production databases (and other sources) to be used to populate the databases for the new system • Step - (optional) Obtain additional manual resources to ontime keying of data not obtained from existing production databases • Step - Write programs to extract data from production databases • Step - Write programs to load new databases 47 Systems Implementation The Delivery Phase of Systems Implementation  Activity: Install Databases  Steps: (continued) • Step - Conduct another system test to ensure new system is unaffected (see Activity: Conduct System Test) This preventative step will ensure that no task accomplished in this activity adversely affects the new system • Step - If necessary, revise the database schema and update the project repository 48 Systems Implementation The Delivery Phase of Systems Implementation  Activity: Train System Users   Purpose:  Provide training and documentation to system users to prepare them for a smooth transition to the new system Roles:  The activity is facilitated by the systems analyst • System owner - System owners must support this activity They must be willing to approve the release time necessary for their people to obtain the training needed to become successful users of the new system • System user - Remember, the system is for the user! User involvement is important in this activity because the end-users will inherit your successes and failures from this effort 49 Systems Implementation The Delivery Phase of Systems Implementation  Activity: Train System Users  Roles: (continued) • System analyst - This activity is typically performed by systems analysts is to train system users to use the new system Given appropriate documentation for the new system, the systems analysts will provide end-user documentation (typically in the form of manuals) and end-user training for the system users • System designers and builders are not normally involved in this activity  Prerequisites (Inputs):  Given appropriate documentation for the new system, the systems analyst will provide the system users with documentation and training needed to properly use the new system 50 Systems Implementation The Delivery Phase of Systems Implementation  Activity: Train System Users  Deliverables (Outputs):  The principle deliverable of this activity is user training and documentation • The golden rule should apply to user manual writing: ``Write unto others as you would have them write unto you.'' – You are not a business expert – Don't expect the reader to be a technical expert • Every possible situation and its proper procedure must be documented 51 Systems Implementation Training Manual End-Users Guide Outline I Introduction II Manual A The manual system (a detailed explanation of peoples' jobs and standard operating procedures for the new system) B The computer system (how it fits into the overall workflow) Monitor/keyboard familiarization First-time end-users a Getting started b Lessons C Reference manual (for nonbeginners) III Appendixes A Error messages 52 Systems Implementation The Delivery Phase of Systems Implementation  Activity: Train System Users   Applicable Techniques:  Written and oral communications skills are critical  Familiarity with organizational behavior and psychology may also prove helpful Steps:  The following steps are suggested to complete this activity • Step - Collect documentation that may prove useful in developing user documentation and training guides • Step - Write user documentation manuals • Step - Referring to the conversion plan, review the training needs of the system users 53 Systems Implementation The Delivery Phase of Systems Implementation  Activity: Train System Users  Steps: (continued) • Step - Schedule training sessions (individual and group sessions) • Step - Conduct training sessions and distribute user documentation 54 Systems Implementation The Delivery Phase of Systems Implementation  Activity: Convert to New System   Purpose:  Convert to the new system from the old system and evaluate the project experience and final system Roles:  The activity is facilitated by the project manager who will oversee the conversion process • System owner - provide feedback regarding their experiences with the overall project They may also provide feedback regarding the new system that has been placed into operation • System user - will provide valuable feedback pertaining to the actual use of the new system They will be the source of the majority of the feedback used to measure the systems acceptance 55 Systems Implementation The Delivery Phase of Systems Implementation  Activity: Convert to New System  Roles: (continued) • System analyst, designers, and builders - will be involved in assessing the feedback received from the system owners and users once the system is in operation In many cases, that feedback may stimulate actions on their part to correct shortcomings that have been identified Regardless, the feedback will be used to help benchmark new systems project down the road   Prerequisites (Inputs):  The input to this activity is the conversion plan that was created in an earlier delivery phase activity Deliverables (Outputs):  The principle deliverable of this is the product information system that is placed into operation in the business 56 Systems Implementation The Delivery Phase of Systems Implementation  Activity: Convert to New System   Applicable Techniques:  Project and process management Steps:  The following steps are suggested to complete this activity • Step - Review the conversion plan • Step - Complete the detailed steps outline in the conversion plan • Step - Schedule meeting with project team to evaluate the development project and the production system • Step - Conduct review meeting - record enhancement/fix requirements that are identified 57 Systems Implementation Summary     Introduction What is Systems Implementation? The Construction Phase of Systems Implementation The Delivery Phase of Systems Implementation 58 ... OrderAppDir.Rights=copy Networking Telchnology (and standards) (and standards) (and standards) Construction Phase Systems Implementation System Owners Approval to continue project Build and Test Networks Installed... into systems design  The key input is the network design requirements defined during systems design Systems Implementation The Construction Phase of Systems Implementation  Activity: Build and. .. solution • Network designer - The network designer is a specialist in the design of local and wide area networks and their connectivity Systems Implementation The Construction Phase of Systems Implementation

Ngày đăng: 10/01/2018, 16:09

Mục lục

  • Introduction

  • What is Systems Implementation?

  • Slide 3

  • The Construction Phase of Systems Implementation

  • Slide 5

  • Slide 6

  • Slide 7

  • Slide 8

  • Slide 9

  • Slide 10

  • Slide 11

  • Slide 12

  • Slide 13

  • Slide 14

  • Slide 15

  • Slide 16

  • Slide 17

  • Slide 18

  • Slide 19

  • Slide 20

Tài liệu cùng người dùng

  • Đang cập nhật ...

Tài liệu liên quan