Home

19 Systems Construction and Implementation

image

Contents

1. Chapter Nineteen Systems Construction and Implementation Slide 15 i Teaching Notes Installation Strategies Discuss the risks and potential rewards of each strategy Toca Versions Slide 16 No additional notes e Systems Acceptance Test 19 16 E L TS Slide 17 Systems Acceptance Test No additional notes continued 19 17 19 7 Copyright 2007 by McGraw Hill Companies Inc 19 8 Chapter Nineteen Slide 18 Implementation Phase No additional notes 3 Install Databases 19 18 Slide 19 Implementation Phase No additional notes 4 Train Users 19 19 Slide 20 An Outline For A nn No additional notes nn Copyright 2007 by McGraw Hill Companies Inc Systems Construction and Implementation 19 9 Implementation Phase No additional notas 5 Convert to New System Slide 21 Copyright 2007 by McGraw Hill Companies Inc 19 10 Chapter Nineteen Answers to End of Chapter Questions and Exercises Review Questions 1 The purpose of the construction phase is to develop a functional system which will fulfill business and design requirements After development testing is also needed The major activity of this phase is programming al though acquiring software packages is coming popular 2 Network designers are responsible for designing the local and wide area network LAN and WAN and how they connect with each other The net work administrators are in charge of building
2. 19 Systems Construction and Implementation Overview Chapter 19 teaches students more about the systems construction and im plementation phases of systems development Although some of the techniques of systems construction and implementation are introduced in this chapter it is not the intent of this chapter to teach the techniques This chapter only teaches the process of systems construction and implementation Chapter to Course Sequencing Students are encouraged to read Chapter 3 to provide perspective for sys tems construction and implementation It would also be beneficial if Chapters 5 and 12 were read before this chapter This would provide a better perspective and foundation for studying Chapter 19 What s Different Here and Why This chapter did not necessitate many changes from the sixth edition 1 As with all chapters we have streamlined the SoundStage episode into a quick narrative introduction to the concepts presented the chapter 2 We updated all technology references throughout the chapter 19 2 Lesson Planning Notes for Slides Chapter Nineteen The following instructor notes keyed to slide images from the PowerPoint repository are intended to help instructors integrate the slides into their indi vidual lesson plans for this chapter Slide 1 E Chapter 19 slide appearance after initial mouse click in slide show mode aea Objectives Copyright 2007 by McGraw Hill Companies Inc Th
3. and testing the network They also need to specify the network architecture standards and maintain net work security 3 First database schemas that are specified in the system design phase are needed as a major input After that we can load the data from the produc tion databases into the tables of the database to conduct any testing activi ties Lastly the product is an unpopulated database structure meaning a database being implemented without actual data loaded into it Program mers will be in charge of populating the database through writing programs 4 e System analysts will need to make sure the requirements are clear dur ing this process e System designers will also need to make sure the integration require ments and program documentation are clear e Network administrators will need to install the software package on the server e Software vendors and consultants will provide help in the process if nec essary 5 Chief programmer teams are one common strategy used by organization when it comes to programming This team is supervised by a very experi enced and proficient programmer or chief programmer who is responsible for the overall program design strategy standards and constructions The chief programmer also manages all the activities regarding coding and test ing In addition to the chief programmer there are other members in this programmer team including backup chief programmer program librarian programmer
4. ed to be allocated for that Consequently additional cost will then be attached to it e Alpha testing is also known as verification testing Verification testing is done in a simulated environment with hypothetical simulated data The test focuses on finding errors and omissions concerning the design and end user specification e Beta testing is also known as validation testing Validation testing is done in a live environment using real data Upon conducting validation testing the testing will test the system for its performance peak work load processing performance and other testing such as human engi neering testing methods and procedure testing and backup and recov ery testing System builders are the major player in installing databases Application programmers will write special programs to transfer the data from the old databases to the new ones so that the new databases will be populated with real data The system analysts will need to make the end user documentation or manuals of the system available for the users and start the training proc ess More importantly system analysts must encourage the users to par ticipate because they are the ones using the system User involvement is vital Thus system analysts should facilitate the training process well so that users can really be comfortable using the new system Feedback is essential because through feedback we can identify inadequa cies of the system which will need t
5. ed in devel oping the conversion plan strategy acceptance testing training users and in the actual conversion to the new system 9 1K 2J 3E 4F 5B 6A 7D 8L 9M 10C 11H 121 13G 10 This question addresses a fundamental aspect of human interface design to design a system that is so intuitive to use that in theory at least no us er s manual is necessary But is this objective achievable There is no right or wrong answer to this question only a well reasoned argument one way or the other 11 The PIER serves a number of purposes particularly the following two e Assuming that since the system worked immediately after implementa tion it must still be working to expectations months later can be a seri ous mistake The PIER formally reviews the system to determine if pro ject objectives have been met expectations are being satisfied and no unanticipated problems have surfaced e The PIER also serves as a lessons learned for future projects It docu ments what went right what didn t go so well PIERs can be an in valuable reference before embarking on a new project Copyright 2007 by McGraw Hill Companies Inc Systems Construction and Implementation 19 15 12 13 A poorly designed and constructed project will almost definitely fail no matter how well planned and well executed the implementation effort is In the end the product must work otherwise to users it is just hype As for t
6. he opposite situation a sound design and construction effort may carry a new system through a poor implementation effort But a little plan ning can save a great deal of pain on everyone s part The project team and stakeholders should throw a party The successful completion of a project is an event that does not occur every day worthy of celebration Projects and Research Students should find information readily available on the web for numerous products of this type including those made by Rational and Mercury Inter active who are leaders in this market Students should be able to effec tively compare and contrast their different features Selections may vary but expect most students to choose Rational because of its widespread use and familiarity Responses may vary but the analysis should address the advantages and disadvantages in this situation of each of the different strategies described in the textbook Also given the scenario described most students should recommend and provide a valid rationale for a parallel and or location con version strategy The purpose of this question is to provide the student with the opportunity to develop a simulated conversion plan and to receive real world feedback from those with expertise in this area The conversion plan should be con sistent with the components described in the textbook As with the previous exercise the purpose of this question is to provide the student wi
7. is repository of slides is intended to support the named chapter The slide repository should be used as follows Copy the file to a unique name for your course and unit Edit the file by deleting those slides you don t want to cover editing other slides as appropriate to your course and adding slides as desired Print the slides to produce transparency masters or print directly to film or present the slides using a computer image projector Each slide includes instructor notes To view those notes in PowerPoint click left on the View Menu then click left on Notes View sub menu You may need to scroll down to see the instructor notes The instructor notes are also available in hard copy as the Instructor Guide to Accompany Sys tems Analysis and Design Methods 6 ed No additional notes Systems Construction and Implementation Slide 3 Slide 4 What Is System Construction and Implementation Slide 5 19 3 Teaching Notes This slide shows the how this chapter s content fits with the building blocks framework used throughout the textbook The emphasis of this chapter is with the construction amp testing phase and installation amp delivery phase spanning the communication focus knowledge focus and process focus It involves system builders and systems analysts and users Teaching Notes Depending on the development techniques used portions of these phases may have been com pleted For example protot
8. lly happened to a non fictitious company The lost revenue was not nearly as great but there were many angry phone calls exchanged Moral of the story parallel conversion is the ONLY way to go on a website 3 Make sure the students document preferably in a table ALL of the peer recommended changes and how specifically they addressed them in their revised prototype 4 Best way to grade this is to hand the manual to a non techie and show them the prototype If the non techie can figure out how to use the proto type without much trouble then the manual passes a usability bar Team and Individual Exercises There are no answers to this section Copyright 2007 by McGraw Hill Companies Inc
9. o be corrected and which will provide us with a benchmark for the new systems to be built in the future Problems and Exercises Unfortunately situations like this do occur at times and too often the pre vailing philosophy is there is not enough time to do it right but there is al ways time to fix it later As the system testing team leader you have a re sponsibility to tactfully point out to the CEO that the cost of fixing problems Copyright 2007 by McGraw Hill Companies Inc Systems Construction and Implementation 19 13 2 3 after implementation may very well be higher than the cost of delaying im plementation Further the impact of a buggy system upon users may di minish or even destroy the ultimate success of the project the good will of the users may be lost permanently If you are unable to persuade the CEO to approve the time needed your contingency plan is to adopt a risk based testing strategy identify the areas of highest risk in the new system and test those areas first This is a difficult situation that consultants and contractors may face at times The organization for which you are doing the testing is paying your company for a certain level of quality and reliability You have an ethical re sponsibility to ensure that the system you deliver meets that expected level of quality If you can t meet that responsibility you should ask yourself if that position is the right one for you There are
10. ransition period e Parallel conversion Using this strategy the old and the new systems will be in use for a pe riod of time together This approach has less risk because the old sys tems can serve as a back up while the new system is put in operation e Location conversion Since some systems may need to be used in different geographic location location conversion will make sure the system is working properly in one location before implementing the systems in the other locations e Staged conversion Systems are implemented using the versioning concept under this ap proach 10 Since abrupt cut over will terminate the old system abruptly and replace the old system with the new one the risk an organization needs to face is very high There may be technical problems that are not identified in the testing stage because the system has not been fully operational in a real life environment In addition to the technical problems system users may Copyright 2007 by McGraw Hill Companies Inc 19 12 Chapter Nineteen 11 12 13 14 15 not even be fully accustomed to the new systems The new system may even face resistance because of that Since parallel conversion requires both the old and the new system to work simultaneously for a period of time cost will become a major issue Having two systems operating in the same time will increase the demand of the computer on which the systems are run Thus more resources may ne
11. s and specialists 6 Stub test testing done on the modules of a program Copyright 2007 by McGraw Hill Companies Inc Systems Construction and Implementation 19 11 Unit or program test testing done after the stub test for a program This kind of test tests all the events and modules together System test All the programs written and tested will be tested here as one integrated system to make sure everything works together properly 7 The implementation phase is needed because in order for a new system to work effectively in an organization a smooth transition from the old to the new system is essential It is also necessary to provide the system users with assistance during this transition period The goal of the implementa tion phase is to make the production system into operation 8 e System analysts will talk to the project team members and let them know if there are any problems or issues during testing e System owners and users will decide if a system is working properly or not e System builders such as programmers database programmers and networking specialists will help solve problems identified in the testing 9 e Abrupt cut over The old system under this strategy will be shut down on a specific day and the new system will replace the old one and will be used for opera tion This approach bears a very high risk because the new system may not be functioning as anticipated and problems may arise during the t
12. several reasons that the programmers who built the system should not do the system testing First like proofreading we tend to be blind to errors and mistakes in the work we ve done ourselves Second there is a very different approach between stub and unit testing which pro grammers do and systems testing In stub and unit testing programmers not necessarily the same ones who wrote the code are testing to make sure the modules work In systems testing the testers are testing the system to see if they can break it This is because if they don t users will Systems testing teams should be composed of primarily systems analysts and business analysts since this type of testing is not focused on the tech nical code but on whether the application meets the business require ments System tester skills include e Attention to detail e Knowledge of testing techniques e Business knowledge of the system and the organization e Integrity and commitment to the organization e False they should be built first because the programs to be written will be dependent upon them as shared resources e True parallel conversion significantly reduces the risk of major or catas trophic damage if the new system does not work properly e False stub and unit testing are activities that can and should take place throughout the construction phase e False users should receive training in close proximity to the implementa tion date to ensure reten
13. th the opportunity to develop a simulated systems acceptance test plan and to receive real world feedback from those with expertise in this area The plan should use the general guidelines described in the textbook as a springboard and should build on them with additional information and templates available on numerous websites The purpose of this question is two fold first to have students gain experi ence in developing a training plan for end users Second to research web based training methodologies and to customize these methodologies so that they are applicable for end user training Copyright 2007 by McGraw Hill Companies Inc 19 16 Chapter Nineteen 6 The intent of this question is to expose the student to contingency planning for implementation based upon both research and real world experiences Responses are open ended but should indicate that the student has thought through some of the possible things that might go wrong and more important has developed a contingency plan for dealing with the unex pected Minicases 1 Note to professor Insist that students test each other s work with the inten tion of finding ALL of the flaws and making the prototype the best it can be You will need to be clear that the class will not be graded on a curve that if all prototypes are excellent they can all get an A Otherwise students will forget to test a portion of the other team s work 2 Yes this actua
14. tion of knowledge e True systems development is a term that is sometimes used to refer to systems construction but which is also used to describe the full devel opment life cycle Copyright 2007 by McGraw Hill Companies Inc 19 14 Chapter Nineteen 6 The intent of this exercise question is to give you the opportunity to write a portion of a user manual in order to appreciate the expertise required to write a user manual Congratulations if your fellow students or co workers found your writing to be understandable clear and appropriately detailed if not remember that good business writers are always in demand so it would be worth your time to develop your skills in this area 7 The final authority on whether the system is operating correctly and ready for implementation is the system owner and users The key input in to the implementation phase is the functional system from the construction phase The systems construction phase is initiated or triggered when the physical design specifications are approved and the design phase is completed Once the conversion to the new system is complete ownership transfers from the project team to the end users Migrating data from the old database and populating a new one is a complex activity that requires careful planning and execution 8 No users are essential to the implementation portion of this phase In addi tion to being involved in system testing they must also be involv
15. yping may have re sulted in the construction of system components as well as the testing and training The Context of System No additional notes Construction and Implementation Copyright 2007 by McGraw Hill Companies Inc 19 4 Slide 6 Tasks for Completing The No additional notes Construction Phase Slide 7 Construction Phase No additional notes 1 Build and Test Networks Slide 8 Construction Phase No additional notes 2 Build and Test Databases Copyright 2007 by McGraw Hill Companies Inc Chapter Nineteen Systems Construction and Implementation 19 5 Slide 9 Construction Phase No additional notes 3 Install and Test New Software Construction Phase No additional notes 4 Write and Test New Programs Slide 10 Slide 11 Teaching Notes Levels of Testing Describe several scenarios of testing and ask the Stub test atest ponarnedionca Subset one system level testing rogra Share with the class personal case studies of the students to characterize them as stub unit or ramifications of failure to properly test otal syste Copyright 2007 by McGraw Hill Companies Inc 19 6 Slide 12 Tasks for Completing The No additional notes Implementation Phase Slide 13 Implementation Phase No additional notes 1 Conduct System Test Slide 14 Implementation Phase No additi nal notes 2 Prepare Conversion Plan Copyright 2007 by McGraw Hill Companies Inc

Download Pdf Manuals

image

Related Search

Related Contents

Jacuzzi 7260 Hot Tub User Manual  Manuel du propriétaire FOX FORX 2003  通信機能付 環境放射線モニタRadi(ラディ) PA-1100 製品  MANUEL D`UTILISATION DU MAGIC FLIGHT LAUNCH BOX L  Metadata Capture User Guide  C-0333 CVT-2/8WB - SmartHomeUSA.com  Manual de Instruções  Voix des Air N°39, 06-2015  User manual  N0000029 V6 Istruzioni URC 3 IT-FR_modif.indd  

Copyright © All rights reserved.
Failed to retrieve file