HyperCase Additional Exercises

Chapter 8 - Analyzing Systems Using Data Dictionaries

1. Define the following data flow, found on Diagram 1.1. Refer to the diagram for further information.

   1. New Project Data

   2. Project Journal Record

   3. Project Status Updates

   4. Canceled Transaction

2. Define the Project Schedule data flow, providing information for Team Leaders. Refer to Diagram 5.

3. Define the Project Query data flow providing information for Unit Managers. Refer to Diagram 6.

4. Define the Project Summary Response data flow providing information for Unit Managers. Refer to Diagram 6.

5. Define the Task Inquiry data flow. Refer to Diagram 6.

6. Define the Task Inquiry Response data flow. Refer to Diagram 6.

7. Define the Leader Inquiry Response data flow. Refer to Diagram 6.

8. Create the Resource Title element. You may wish to reflect on various organizational titles to determine the length. Refer to the Resource data store structure.

9. Create the Precedent Task Number element. Refer to the Task data store structure.

10. Create the Weekly Amount Billed element, located on the Resource data store structure.

11. Create the Original Task Scheduled Start Date element, located on the Task data store structure.

12. Create the Task Revised Start Date element, located on the Task data store structure.

13. Create the Task Actual Start Date element, located on the Task data store structure.

14. Create the Year-To-Date Amount Billed element, located on the Resource data store structure.

15. Create the Total Hours Worked element, located on the Resource data store structure.

16. Create the Task Notes element, located on the Task data store structure.

17. Create the Task Status element, located on the Task data store structure. This is a coded element, but leave the description of the codes for Chapter 15.

18. Create the Resource Type Code element, located on the Resource data store structure. This is a coded element, but leave the description of the codes for Chapter 15.

19. Create the Project Type Code element, located on the Project data store structure. This is a coded element, but leave the description of the codes for Chapter 15.

20. Create the Project Category Code element, located on the Project data store structure. This is a coded element, but leave the description of the codes for Chapter 15.

21. Create the Project Size Code element, located on the Project data store structure. This is a coded element, but leave the description of the codes for Chapter 15.

22. Create the Project Priority Code element, located on the Project data store structure. This is a coded element, but leave the description of the codes for Chapter 15.

23. Create the Project Status Code element, located on the Project data store structure. This is a coded element, but leave the description of the codes for Chapter 15.

24. Create the Project Category Code element, located on the Project data store structure. This is a coded element, but leave the description of the codes for Chapter 15.

25. Create the Journal File data store. Refer to Diagram 1.1 for further information.

26. Create the Country File data store. This is a new file used to keep track of information about each country that MRE is thinking about doing business with. The data store contains the following elements: Country Name, International Telephone Country Code, Currency Name, Currency Exchange Rate, the name of a contact person, and a comment field (or fields) for keeping track of specific zoning laws or other unique situations that would impact the completion of MRE projects in that country.
    
    
27. Define the Contact data store. This is used to keep track of contacts working on MRE projects in a specific country.
    
    
28. Create and print the data flow entry for New Customer in the Ecommerce system.
    
    
29. Create and print the data flow entry for New Order in the Ecommerce system.
    
    
30. Define and print the elements for the New Customer in the Ecommerce system. Use reasonable assumptions about the type of elements that would be added.
    
    
31. Define and print the elements for the New Order in the Ecommerce system. Use reasonable assumptions about the type of elements that would be stored.
    
    
32. Define and print the Order Details XML document sent to Terra Shipping. Think about what data would need to be sent to an external partner.
    
    
33. Define and print the Customer data store. Use reasonable assumptions about the type of elements that would be stored (remember that additional elements are needed to keep track of financial information about a customer).
    
    
34. Define and print the Order data store. Use reasonable assumptions about the type of elements that would be stored.
    
    
35. Define and print the Item data store. Use reasonable assumptions about the type of elements that would be stored. Think about what sort of elements would be need to manage inventory.
    
    
36. Examine the Order DTD found in Nathan Donaldson's office. Which elements are repeating? Which elements are optional? What attributes are being used?