HyperCase Additional Exercises

Chapter 2 - Understanding Organizational Style and Its Impact on Information Systems

Examine the MRE Corporate Web Site to answer the following questions. Either write a sentence or report your findings to the class.

1. What are the different business activities that take place at MRE? Describe each business activity.

2. Which is the largest department at MRE?

3. What was the previous year revenue generated by MRE?

4. How many people are employed by MRE?

5. How many offices are maintained by MRE? Which is the home office.

6. Which Vice President is responsible for the Management Information Systems department?

7. What four areas is the Executive VP for Administration responsible for?

8. Which division at MRE generates the most revenue?

9. What does the Webster Design group do?

10. Which is the newest department at MRE? What two groups were merged to form it?

11. Which division works with Fiscal Services and Communication to formulate and submit proposals to the United States Government?

12. Form a small group of students. Have each group (or student in the group, depending on class and group size) choose two of the staff members from the Staff page. Read the corporate biographies of the staff members and report back to the group what you found.

13. Form a small group of students. Have each group (or student in the group) choose a division of MRE. Explain the nature of the MRE division to the group.
    
    
14. Draw a use case diagram for the Ecommerce System. Refer to the JAD session linked from the Silver interview. Think about the actors and how they would use the system.

    When looking for actors, does the context level data flow diagram provide some of this information, perhaps some of the external entities?

    When looking at use cases, think about the different ways that the system would be used by the actors. Diagram 0 may provide some assistance in identifying how the system is used.

    Remember that this is what is called a logical view, and to look at what the system should do rather than how the system should accomplish the tasks. Use the following to help produce the diagram:

    Possible actors

    Customer
    Warehouse Operations and Shipping
    Credit Card Company
    Customer Service

    Possible activities

    Add new customer
    Verify existing customer
    Sending order confirmation to customer
    Send shipped order confirmation to customer
    Get credit card information
    Receive customer return information
    Select products for shopping cart
    Looking up customer information in response to an inquiry
    Producing statistical analysis reports

    
    For the next five exercises, click on the use case symbols in the GEMS use case for details. The use case diagrams are in Smith's office.
    
    
15. Write a use case description for the Logon User ID and Password use case. Refer to the use case specifications for details.
    
    
16. Write a use case description for the Report Project Progress use case. Refer to the use case specifications for details.
    
    
17. Write a use case description for the Add Client use case. Refer to the use case specifications for details.
    
    
18. Write a use case description for the Add Resource use case. Refer to the use case specifications for details.
    
    
19. Write a use case description for the Provide Project Status use case. Refer to the use case specifications for details.
    
    
20. Write a use case description for the check out customer order for the Ecommerce System. Include sending an email order confirmation to the customer, sending the order to Terra Shipping and sending a shipping confirmation email to the customer when the details are returned from Terra Shipping.
    
    
21. View the context level diagram for the GEMS system (refer to Rabin's office). In what way is the information similar to that found on a use case diagram? Answer in a paragraph.
    
    
22. View the entity-relationship diagram found in the GEMS system (refer to Rabin's office). In a paragraph, list the one-to-many relationships found on the diagram.