1. Jesse wants to see a structure chart. She said to use program modules based on the

processes we identified earlier. She wants the modules to be cohesive and loosely coupled.

2. Need a testing plan that includes unit integration and system testing as Jesse requested.

Also, need a reminder about careful documentation.

3. Jesse says it's important to understand the difference between the test and operational

environments, and she wants me to draft a message that explains the installation process

and includes guidelines for all concerned. Also need to develop a training plan for TIMS,

with groups that should receive training, the topics that should be covered, and training

methods we might use.

4. Jesse wants me to recommend a data conversion plan and a changeover method for

TIMS. She also wants a plan for post-implementation review, including fact-gathering

methods, topics to cover, the timing of the review, and who should perform it.

Session 11: Managing Systems Implementation INBOX VOICEMAIL TO DO LIST MESSAGES Jesse Baker System implementation Hi Kate, You did a nice job on the system design specification... To: kate_mason@scrassociates.com From: jesse_baker@scrassociates.com Subject: System implementation Hi Kate, Jesse Baker Testing Hi Kate, Hope you had a good weekend - I know you spent most of Saturday... You did a nice job on the system design specification, and I heard some favorable comments after the presentation yesterday. Now we're ready to tackle the systems implementation phase, which includes application development, coding, testing, and training. After all that, we'll work on a data conversion process and select a changeover method. I know it sounds like a lot to do, but let's just take one step at a time. Jesse Baker System installation, training... Hi Kate, Thanks for your hard work on the structure charts... Our first task is to establish a set of program modules that represent the processes that we identified earlier. If you look back at the DFDs, JAD sessions, and other documentation, you'll see that we identified four main functions in the TIMS system: class scheduling, student registration, class tracking, and producing necessary output Jesse Baker Post-implementation review Hi Kate, Thanks for keeping me up to date on the installation process... Remember our discussion about structure charts that show the program modules and how they interact? Now I want you to create structure chart that translates the TIMS design into a set of modules that programmers can use. The modules should be highly cohesive and loosely coupled, so they will be easier to maintain. I know that some of this might sound confusing, so you probably should go back over your notes before you start. Let me know if you have any questions. Thanks. Jesse Baker Session 11: Managing Systems Implementation INBOX VOICEMAIL TO DO LIST MESSAGES To: kate_mason@scrassociates.com From: jesse_baker@scrassociates.com Subject: Testing Jesse Baker System implementation Hi Kate. You did a nice job on the system design specification... Hi Kate, Jesse Baker Testing Hi Kate, Hope you had a good weekend - I know you spent most of Saturday... Hope you had a good weekend I know you spent most of Saturday in the office working on the structure chart. Jesse Baker System installation, training... Hi Kate, Thanks for your hard work on the structure charts... The executive committee wants to see a fully functioning system, properly tested, and ready for implementation in six weeks. I've talked to the programming team; they think it will be a stretch, but it can be done. As soon as the modules are developed, we should start unit testing and integration testing. Please come up with an overall plan for testing and get it to me by the end of the week. Jesse Baker Post-implementation review Hi Kate, Thanks for keeping me up to date on the installation process... Keep me posted. Thanks. Jesse Baker Session 11: Managing Systems Implementation INBOX VOICEMAIL TO DO LIST MESSAGES Jesse Baker System implementation Hi Kate, You did a nice job on the system design specification... To: kate_mason@scrassociates.com From: jesse_baker@scrassociates.com Subject: System installation, training, data conversion, and changeover strategy Hi Kate, Jesse Baker Testing Hi Kate, Hope you had a good weekend - I know you spent most of Saturday... Thanks for your hard work on the structure charts and testing plan. Unit testing, integration testing, and system testing were successful, and we now have a functioning system running in a test environment. I know that you received some suggestions for improvements and new features, but we'll have to defer those until TIMS becomes operational. Jesse Baker System installation, training... Hi Kate, Thanks for your hard work on the structure charts... Now, I want you to develop an overall plan for installing the new system in an operational environment. You can start by drafting a message that clearly explains the importance of separating the test environment and the operational environment. Be sure to explain the installation process and list some guidelines for users. Jesse Baker Post-implementation review Hi Kate, Thanks for keeping me up to date on the installation process... Also, we need a training plan. Come up with a proposal to provide hands-on training for anyone at SCR who will be using or supporting the new system. Please work with Jill Martin on this, and be sure to include people from the administrative support group. We'll plan to handle everything in-house time and budgets are both too tight to consider outside resources. We also should hold an overview session for all SCR managers. Finally, TIMS will replace the training records system that we have been using, so you'll need to decide how handle data conversion and select a changeover strategy. Please get back to me with your recommendations. I'm sure you know that everyone at SCR is excited about the new system. Our next tasks will be to set up the operational environment, load live data, and install the working version of the system on client workstations. This is going to be a very busy couple of weeks! Please keep me posted daily. Jesse Baker Session 11: Managing Systems Implementation INBOX VOICEMAIL TO DO LIST MESSAGES Jesse Baker System implementation Hi Kate, You did a nice job on the system design specification... To: kate_mason@scrassociates.com From: jesse_baker@scrassociates.com Subject: Post-implementation review Hi Kate, Jesse Baker Testing Hi Kate, Hope you had a good weekend - I know you spent most of Saturday... Thanks for keeping me up to date on the installation process. So far, so good. Here is another item to add to your agenda Jesse Baker System installation, training... Hi Kate, Thanks for your hard work on the structure charts... I want you to send me a plan for a post-implementation review for the TIMS system. I've decided to do the review sooner, rather than later. Please start thinking about what should be included in the review, when it should take place, and who should perform it. Jesse Baker Post-implementation review Hi Kate, Thanks for keeping me up to date on the installation process... We'll need plenty of feedback from everyone who uses or supports the TIMS system. Start thinking about fact-finding methods, a list of topics to cover, the best time to conduct the review, and who should perform it. Just a thought we might want to suggest that users log their observations and comments. Maybe we should provide an online form for that purpose. I'll talk to you more about this as the installation process continues. One more thing - after the post-implementation review, we'll present a final report to management. It's too early to worry about that, but I want you to know that you'll be the key presenter. This will give you a chance to meet the Executive Committee and get some visibility! I know you'll be in the office again this weekend. I'll probably drop in on Saturday afternoon to see how you're doing. Don't run out of steam - we're almost there! Jesse Baker Session 11: Managing Systems Implementation INBOX VOICEMAIL TO DO LIST Voicemail 1: I sent you an email message about creating structure charts, and I want to add a tip. I asked you to make the charts highly cohesive and loosely coupled. Remember, cohesion measures a module's complexity. A highly cohesive module has a single function so it easier to code and reuse. So a highly cohesive module is like a function primitive that we identified when we drew our DFDs. Same idea, different terminology. That's all! One more thing. Coupling describes the relationship between modules. We want them to be loosely coupled so that the logic in one does not affect the logic in any others. Kind of like stand- alone units. Make sense? Let's get together tomorrow morning and go over this again. Voicemail 2: I enjoyed our chat this morning! By the way, when you work on the testing plan be sure to consider what kind of test data we should use and include that in the proposal. I'm especially interested in whether we should use purposely incorrect data as well as valid data. Give this some thought and let me know.