|
|
|
Chapter 10 gives a good overview of the tasks involved in actually going beyond the analysis and design stages and implementing a new system. Implementation is obviously a huge and technical topic, so approach this more as a guide to the many tasks involved beyond actually writing code than as a detailed how-to. Skip the section on Structure Charts and flowcharts as these are rather confusingly explained and you don't get enough context to really understand what they mean. You'll just have to take it on faith that all those DFDs and data dictionaries you've been toiling on really are useful when the coding starts. Discussion Questions 1) The textbook talks about different forms of testing, including desk checking, design walkthroughs, unit testing, integration testing, and system testing. Make sure you know what each one is. Why do you think so many different kinds of testing are needed? What might be the strengths and weaknesses of each one in terms of catching different kinds of errors? 2) The project assignment for this phase is "Develop a plan for the implementation phase, including programming, testing, training, data conversion and changeover strategy. Include at least a paragraph on each, with an estimate of the person-days required. Produce a timeline showing start and end dates for each activity." Read the textbook description of each of these phases carefully. Think about your individual project and make some notes on what issues might surface in each of these stages and how you would tackle them. I'll look for volunteers, but will pick victims at random if necessary to be prepared! |
|
|