Skip to content

Ctts Case Study Milestone 5% Solution

Prepared by Gary B. Randolph for

Systems Analysis & Design Methods 7ed by J. L. Whitten, L. D. Bentley, & K.C. Dittman Copyright Irwin/McGraw-Hill 2007

MILESTONE 2 - PROBLEM ANALYSIS

Problems, Opportunities, Objectives, and Constraints Matrix.

he matrix should be completed based on the solution of Milestone 1, the case background information, and the user interviews. The students should try to identify the causes and effects of the problems identified in Milestone 1. Make sure students identify a cause and not restate the problem. Also, make sure they specify proper objectives to correct the problems. You will have a multitude of different answers. Evaluate their thought processes. The following matrix illustrates one possible solution.

he matrix should be completed based on the solution of Milestone 1, the case background information, and the user interviews. The students should try to identify the causes and effects of the problems identified in Milestone 1. Make sure students identify a cause and not restate the problem. Also, make sure they specify proper objectives to correct the problems. You will have a multitude of different answers. Evaluate their thought processes. The following matrix illustrates one possible solution.

T

上一页下一页

CTTS CASE STUDY - Milestone 3: Solution Page: 3-1 MILESTONE 3 – MODELING SYSTEM REQUIREMENTS  Activity 1 – Use-Case Glossary he following use cases and their descriptions and actors can be determined from the interview. Some students may identify other use cases based on standard maintenance functions. These are not incorrect, but have been left out of the glossary for the sake of simplicity. We have chosen to focus only on the use cases that will be most used. T A few notes on the use cases included in the glossary:  M ANUALLY R ESOLVE S ERVICE R EQUEST was made a separate use case from A UTOMATICALLY R ESOLVE S ERVICE R EQUEST because the steps that each follow are very different.  An abstract use case called R ESOLVE S ERVICE R EQUEST was added to encapsulate the logic that actually marks a service request as resolved. This will be used by M ANUALLY R ESOLVE S ERVICE R EQUEST and A UTOMATICALLY R ESOLVE S ERVICE R EQUEST .  From the interview we could easily add another abstract use case for logon. But since every other use case would use logon, this was left out solely to keep the use case diagram that follows from becoming messy.  An Employee role was added for two use cases that could be accessed by any employee.