Đang chuẩn bị liên kết để tải về tài liệu:
Moving into Implementation

Moving into Implementation.Systems analysis and design, 6th.edition.Dennis, wixom, and roth.Roberta M. Roth © 2015 John Wiley & Sons. All Rights 1Learning Objectivesq Be familiar with the system construction processq Explain different types of tests and when to use themq Describe how to develop user documentation © 2015 John Wiley & Sons. All Rights 2Key Definitionsq Implementation is the development of all parts of. the system: the software itself, documentation, and. new operating procedures © 2015 John Wiley & Sons. All Rights 3Managing the Programming.ProcessProject management during construction. © 2015 John Wiley & Sons. All Rights 4Project Manager’s Tasks During.Programming.q Assigning the programmers.q Coordinating the activities.q Managing the schedule. © 2015 John Wiley & Sons. All Rights 5The Programmer Paradoxq More is not always better than less!.q After the “right” number of people are assigned to a. programming task, adding more people slows down. rather than speeds up completion of the projectq Projects requiring a large team should be broken. into a series of independent, smaller parts. © 2015 John Wiley & Sons. All Rights 6Assigning Programmers. Minimize the number of programmers. Two communication. channels Twelve communication. channelso Match programming tasks with programmer capabilities.o When skills are deficient, apply mentoring and training. © 2015 John Wiley & Sons. All Rights 7Coordinating Activitiesq Weekly (hopefully brief) meetings.q Create and follow standards.q Organize programmers’ work areas. o Development area. o Testing area. o Production area.q Implement change control mechanisms.q Use program log Wileymonitor program changes. © 2015 John to & Sons. All Rights 8Managing the Scheduleq Use initial time estimates as a baseline.q Revise time estimates as construction proceeds.q Fight against scope creep.q Monitor “minor” slippage.q Create risk assessment and track changing risks.q Fight the temptation to lower quality to meet. unreasonable schedule demands © 2015 John Wiley & Sons. All Rights 9Avoid Classic Mistakes.üResearch-oriented development. If you use state-of-the art technology, lengthen planned time.üUsing “low-cost” personnel. If using a significant number of entry level personnel,.lengthen planned time.üLack of code control. Use source code library to keep programmers from changing.the same code at the same timeüInadequate testing. Always allocate sufficient time for formal testing. © 2015 John Wiley & Sons. All Rights 10Testing.Ensuring the system fulfills requirements. © 2015 John Wiley & Sons. All Rights 11Testing Philosophyq Testing helps ensure that the system performs as outlined. in the specificationsq It is dangerous to test early modules without an overall. testing plan.q It may be difficult to reproduce sequence of events causing. an error.q Testing must be done systematically and results. documented carefully © 2015 John Wiley & Sons. All Rights 12Test Plan.Roberta M. Roth © 2015 John Wiley & Sons. All Rights 13Categories of Testing q Stub testing. o Tests control structures before all modules are written. q Unit testing. o Tests each module – Does it performs its function?. q Integration testing. o Tests the interaction of modules - do they work together?. q System testing. o Tests to assure that the software works well as part of.Roberta M. Roth © 2015 John Wiley & Sons. All Rights 14Stub.Testing.Roberta M. Roth © 2015 John Wiley & Sons. All Rights 15Unit Testingq Black Box