“So the project involves more than simply performing maintenance work on the current programs,” Chip says. “Are we using a formal methodology for analyzing and designing the new system?” “Yes,” replies Anna. “We are also using Microsoft Visio to create and modify the diagrams and some simple repository information. We also have a CASE tool, Visible Analyst, to analyze and design the system.1We’ve recently installed the products on the computer in the office.” With a few easy mouse clicks Anna comes to a context-level data flow diagram (see Figure). “It’s very useful to begin thinking of the system this way,” Anna says as they look at the diagram on the screen. Chip agrees, saying, “I can very easily see what you think is happening with the system. For instance, I see that the external entity Management supplies hardware and software inquiries and receives the corresponding responses in return. It shows the system within the larger organization.”

1. Use Microsoft Visio or Visible Analyst to view and print the context-level data flow diagram for the computer inventory system, as Chip and Anna did.

2. Use the Repository feature or the Repository Web page to view the entry for the central process.

3. Use Microsoft Visio or Visible Analyst to view and print the entity-relationship diagram for the computer inventory system.

4. Explain why the external entities on the context-level diagram are not found on the entity relationship diagram.

5. Explain why the entities MANAGEMENT and FACULTY are found on both sides of the process on the context-level diagram.

6. Use Microsoft Visio or Visible Analyst to view and print the use case diagram for the computer inventory system.

7. Add the following actors and use cases to the use case diagram:

a. FACULTY actor in the lower left side of the use case diagram.

b. Connect the FACULTY actor to the QUERY TRAINING CLASSES use case.

c. Since the computers may have software installed for a specific computer lab, the clerical support staff may be responsible for installing software on the computers. Connect the CLERICAL SUPPORT actor to the ADD SOFTWARE use case.

d. Add two new use cases below the QUERY TRAINING CLASSES use case: QUERY SOFTWARE EXPERT and below it, QUERY SOFTWARE INFORMATION.

e. Connect the FACULTY actor to the QUERY SOFTWARE EXPERT and QUERY SOFTWARE INFORMATION use cases.

f. Connect the MANAGEMENT actor to the QUERY SOFTWARE EXPERT use case.

8. Add the INSTALL DESKTOP COMPUTER use case to the upper right area of the diagram. This use case extends the ADD NEW COMPUTER use case.

9. Add a use case description for the ADD SOFTWARE use case. It should contain the following information:

a. Obtain the use case name and actors from the use case diagram. The stakeholder and level are the same as those in Figure.

b. The description should be: Add new software to the Software database table and print an installation listing.

c. The activity is started (triggered) when the user clicks the Add Software menu item.

d. The steps performed and information for steps are:

Software is keyed into the new system and validated ....Software received form

Software is added to the Software Master .......Software Master

The Software Installation List is produced .......Software Master, Order

The software user is notified about installed software ...Order

e. Preconditions are that software has been received. Post conditions are that the software has been added to the database and reports have been created. Assumptions are that the user has successfully logged on with access to the Add Software entry screen. A success guarantee is that the software has been added to the database and the required report printed. A minimum guarantee is that the software has been received. The objectives met are to add and install new software. The outstanding issue is how to determine which software to install on which machines. The priority is high and the risk is medium.

10. Write a use case description for the PRODUCE HARDWARE SOFTWARE CROSS REFERENCE REPORT use case. Use the use case diagram to determine the heading information, making any reasonable assumptions. The steps would be to read a software record, use that information to read the hardware-software relational table, then read the hardware record. Use the hardware record to print a line, accumulating totals. Print subtotals and grand totals. This is a medium priority, low-risk activity. Preconditions are that all the information must have been previously added to the appropriate database tables. Post conditions are that the report has been printed. Assumptions are that all the information on the database tables is correct. A success guarantee would be the report has been successfully created. A minimum guarantee would be the report could not be printed. The objectives met are to produce information about what software is found on which machine. Outstanding issues are: What if the software is older and is not currently installed on any machines, how should the report be produced: printed, in a PDF file, or should it really be a query for one software package?

11. Write the use case description for the PRODUCE HARDWARE INVESTMENT REPORT use case. Use the use case diagram to define the header information. The steps involve reading each hardware record, counting the number of machines, and totaling the amount invested in them for each computer model. When the computer brand changes, produce subtotals, with a grand total at the end of the report. All information comes from the Hardware Master Database table. Make any reasonable assumptions about preconditions, post conditions, assumptions, success guarantee, minimum guarantee, objectives met, outstanding issues, priority, and risk.

12. Write the use case description for the QUERY TRAINING CLASSES use case. Use the use case diagram to define the header information. The steps involve entering information on the Web form, validating the information, and storing the data on a Training Request database table. Make any reasonable assumptions about preconditions (such as if the software have to be already purchased), post conditions, assumptions, success guarantee, minimum guarantee, objectives met, outstanding issues, priority (would this be a high priority task), and risk.