HyperCase Additional Exercises


Chapter 1 - Assuming the Role of the Systems Analyst

  1. Read the Instructions (linked from the HyperCase Home page). These will help to make your HyperCase experience enjoyable and educational.

  2. Start HyperCase (click the Start link) and explore the Reception Area. Write a paragraph describing the different objects found in the Reception Area. Which ones do you feel will be helpful in your exploration of HyperCase?

  3. Examine the MRE Building Layout. In a sentence, describe the different types of business activities that take place at MRE.

  4. Take a stroll through the corridors of MRE (click under the MRE entrance sign). In a sentence, what is the look and feel of the company?

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?

  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.

Chapter 3 - Determining Feasibility and Managing Analysis and Design Activities

    No additional exercises. Please refer to Systems Analysis & Design, by Kendall and Kendall for exercises.

Chapter 4 - Sampling and Investigating Hard Data

    No additional exercises. Please refer to Systems Analysis & Design, by Kendall and Kendall for exercises.

Chapter 5 - Interviewing

  1. In a small group, discuss what you learned from the interview with each of the following people (examine one interview per group). How did the interviewee's expression reinforce the answers they gave to the questions. Explain your findings to the class or write a paragraph or two explaining your observations.

    1. Kathy Blandford
    2. Snowden Evans
    3. Daniel Hill
    4. James F. Hyatt
    5. Thomas Ketcham
    6. Linda Lin
    7. Roger Rabin
    8. Cyril Sabin
    9. John Sherman
    10. Melissa Smith
    11. Warren F. Torrey

  2. In a small group, role play interviewing each of the persons mentioned above. Use the following guidelines:

    1. Each group should elect one person (or take turns) to represent the user that they studied in question number one.

    2. The persons being interviewed should assume the role of the person and make up answers consistent with what they learned in the interview.

    3. A different group should make up the questions for the user.

    4. Have either one or two persons ask the interview questions.

    5. The entire class should critique the interview after it has finished.

  3. In a small group, perform a JAD session with the major system users mentioned above participating. Have other students act as a session leader, a scribe, and observers.

Chapter 6 - Using Questionnaires

    No additional exercises. Please refer to Systems Analysis & Design, by Kendall and Kendall for exercises.

Chapter 7 - Observing Decision-Maker Behavior and Office Environment

  1. Use STROBE to analyze the following offices. In a paragraph or two, explain what inferences you can draw from your observations. You may alternatively work in a small group and discuss what you learned from your observations. Explain your findings to the class.

    1. Kathy Blandford
    2. Snowden Evans
    3. Daniel Hill
    4. James F. Hyatt
    5. Thomas Ketcham
    6. Linda Lin
    7. Roger Rabin
    8. John Sherman
    9. Melissa Smith
    10. Warren F. Torrey

Chapter 8 - Prototyping

    Either individually or in small groups, review the following screens and reports. Make a list of changes that you feel should be incorporated into the screen or report design. Things to consider are:

  1. Are all the fields on the screen necessary for accomplishing the screen function?

  2. Is the screen missing fields that would make it more useful?

  3. Which fields should not have to be entered (they would be on the system, read by the program and displayed on the screen)?

  4. Which of the fields could be turned into:
    1. List boxes
    2. Check boxes
    3. Radio buttons
    4. Drop-down list boxes
    5. Spin buttons (used to increment/decrement a number)

  5. What command buttons should be included for each screen?

  6. Is the screen aesthetically pleasing?

    Critique the following screens and reports:

    Edit/Update Screens

  1. Edit Project and Milestones screen. Each project may have many milestones.

  2. Edit Milestones and Tasks. Each milestone may have many tasks.

  3. Edit Project, used to add or change project information.

  4. Edit Milestones. The screen adds a single milestone.

  5. Edit Tasks, used to add or change a single task.

  6. Edit Resources, used to add or change a human resource.

  7. Edit Requirements, used for a single requirement.

  8. Edit Assignments. Each assignment links one resource to one task.

  9. Edit Leaders, used to add or change leader information.

    Inquiry Screens

  10. Query Projects & Milestones

  11. Query Requirements

  12. Query Milestones & Tasks

  13. Query Resources

  14. Query Tasks

  15. Query Leaders

  16. Query Assignments

    Reports

  17. Schedule Report, showing the milestones and task completion information for projects, as well as a Gantt chart.

  18. Budget Report, showing project milestone and task completion information.

    Creating Prototypes

  19. Create the following prototypes, either on paper or using software that you are familiar with. Elicit feedback from other students or members of your team.

    1. Project History Report, presenting summary information about the project.

    2. Project budget or time exception report. This would list all projects over budget or behind schedule.

    3. Project Resource Query, where an resource person's number is entered and the amount of time allocated for the person displays.

    4. Project progress query, listing the point that the project is currently at, along with milestones already accomplished.

Chapter 9 - Data Flow Diagrams

Create the following data flow diagrams. Refer to the process number that explodes to the diagram for further information.

  1. Diagram 1.2, Update Requirements, used to add a new requirement to the Requirements data store.

  2. Diagram 1.3, Update Tasks, used to update task information.

  3. Diagram 1.4, Update Milestones. This process adds new milestones for a project.

  4. Diagram 1.5, Update Leader Information, used to add or change leader records.

  5. Diagram 1.6, Close Completed Project. This process is responsible for closing projects that have been finished.

  6. Diagram 2, Update Resources, used to add or change information about human resources.

  7. Diagram 5.1, Produce Project Schedule. This process prints the Project Schedule Report

  8. Diagram 6.1, Query Project Information, used to find and display project information.

  9. Diagram 6.2, Query Milestone Information. This process displays a milestone and the related Project, Task and Requirement information.

  10. Diagram 6.4, Query Task Information, displaying task and related requirement information.

  11. Diagram 6.5, Query Requirement Information. Displays information about a single requirement.

  12. Diagram 6.6, Query Resource Information. This process displays information about a human resource and related tasks, milestones and projects.

  13. Diagram 6.7, Query Leader Information, displaying information about a single leader.

Chapter 10 - 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 19.

  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 19.

  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 19.

  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 19.

  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 19.

  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 19.

  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 19.

  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 19.

  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.

Chapter 11 - Analyzing Structured Decision Systems

Write the process logic for the following diagrams. Refer to any process on the diagram for further information.

  1. The logic for each process on Diagram 1.1, Update Project.

  2. Each process on Diagram 6.3 - Query Project Assignments.

  3. Create the process logic for any of the processes on diagrams that you have created in Chapter 9.

  4. Use the technique of horizontal balancing to examine the following processes. Write a short paragraph outlining the problems and the suggested changes to solve the problems.

    1. Process 5.2.6

    2. Process 4.1

    3. Process 4.2

    4. Process 6.6

  5. Create a decision tree for the logic of 6.3.1, Get Assignment Record.

  6. Create a decision tree for the logic of 1.1, Update Project. The decision tree should show the execution of the modules on Diagram 1.1.

  7. Create a decision tree for the logic of 1.4, Update Milestones. The decision tree should show the execution of the modules on Diagram 1.4.

  8. Create a decision table for 4.1, Edit Work Completed

  9. Create a decision table for the logic of 1.1, Update Project. The decision table should show the execution of the modules on Diagram 1.1.

  10. Create a decision table for the logic of 1.4, Update Milestones. The decision table should show the execution of the modules on Diagram 1.4.

Chapter 12 - Analyzing Decision Support Systems

    No additional exercises. Please refer to Systems Analysis & Design, by Kendall and Kendall for exercises.

Chapter 13 - Preparing the Systems Proposal

    No additional exercises. Please refer to Systems Analysis & Design, by Kendall and Kendall for exercises.

Chapter 14 - Writing and Presenting the Systems Proposal

    No additional exercises. Please refer to Systems Analysis & Design, by Kendall and Kendall for exercises.

Chapter 15 - Designing Effective Output

  1. Design a report for each client. A separate page should be printed for each client. The report should list all client projects and include information from the Project Master, Milestones and Task Master data stores. You should decide which of the elements on these data stores would be appropriate to include on this external report to the client.

  2. Design a report that lists all the projects and tasks for each resource. Refer to the Project Master and Task Master data stores. Choose which of the elements on these data stores should be included on this report.

  3. Design a report that shows all milestones that have not been met (the milestone completion date contains zeros. List the milestone, the project the milestone is for and the tasks for each milestone. Refer to the Milestone Master, the Project Master and Task Master data stores. Choose which of the elements on these data stores should be included on this report. Include a count of all outstanding milestones.

  4. Create the Requirement Inquiry screen. The elements and description of the screen may be found in the Requirement Inquiry Response data flow.

  5. Create the Leader Inquiry screen. The elements and description of the screen may be found in the Leader Inquiry Response data flow.

  6. Create the Milestone Inquiry screen. The elements and description of the screen may be found in the Milestone Inquiry Response data flow.

  7. Create the Project Inquiry screen. The elements and description of the screen may be found in the Project Inquiry Response data flow.

  8. Create the Assignment Inquiry screen. The elements and description of the screen may be found in the Assignment Inquiry Response data flow.

  9. Create the Resource Inquiry screen. The elements and description of the screen may be found in the Resource Inquiry Response data flow.

  10. Create the Task Inquiry screen. The elements and description of the screen may be found in the Task Inquiry Response data flow.

Chapter 16 - Designing Effective Input

  1. Design a form to add new projects. This form serves not only to add a new project, but is a legal document between the client and MRE. It should contain:

    1. Instructions

    2. A zone to capture client information, including:

      1. Client name
      2. Client address
      3. Phone and FAX number
      4. Contact person
      5. Contact eMail address
      6. Client number (for office use only area)
      7. Type of business

    3. Project information. Refer to the New Project Data data flow.

    4. Project Deliverables, that is, what will the client receive as a result of this project. Only include the name and target date for each deliverable.

    5. An area for signatures. Include the client representative signature and the MRE representative, as well as dates signed.

  2. Design a form to add resources. Refer to the Resource Information data flow for fields that should be included on the form.

  3. Create a form to add milestones and tasks to a project. Refer to the Milestone Information and Task Information data flows for fields that should be included on the form.

  4. Design a Web site that will allow training staff that is working at a distant location to update their hours worked. This is the input screen to process 4.1, Edit Work Completed.

  5. Design the following input screens. Use the data flow into the process that uses the screen for the screen contents.

    1. Process 1.1.1, Update Project. Input data flow: New Project Data

    2. Process 1.1.5, Edit Project Change Data. Input data flow: Project Status Updates.

    3. Process 1.3, Update Tasks. Input data flow: Task Information.

    4. Process 1.4, Update Milestones. Input data flow: Milestone Information.

    5. Process 1.5, Update Leader Information. Input data flow: Leader Information.

    6. Process 3.1, Edit Assignment Information. Input data flow: Assignment Information.

    7. Process 2, Update Resources. Input data flow: Resource Information.

    8. Process 4.1, Edit Work Completed. Input data flow: Work Completed Data.

Chapter 17 - Designing the File or Database

  1. Review the entity-relationship diagram for the GEMS system. Currently, only the Client Name is kept on the Project Master data store (Projects entity). Modify the entity-relationship diagram to include a new Client entity. Each Project is for only one client, but each client may have many projects.

  2. Add a new Deliverable entity to the entity-relationship diagram for the GEMS system. It contains the Deliverable Number, Deliverable Name and Type of Deliverable (such as software, equipment, and so on). Each project may have many deliverables, and each deliverable may be for many projects. Include the relational file linking deliverables and projects. Define the keys and foreign keys required to implement the Deliverable entity.

  3. Add a new Country entity to the entity-relationship diagram for the GEMS system. It contains the Country Number as well as other fields (refer to the last exercise in Chapter 10). Each unique project may be done in only one country, but each country may have many projects. Define the keys and foreign keys required to implement the Country entity.

Chapter 18 - Designing the User Interface

  1. Design a series of pull-down menus for the GEMS system. Refer to the prototype menus.

  2. Design a mainframe type of menu for the GEMS system.

  3. Create a help screen for any of the GEMS screens.

  4. Create a Internet home page main screen for the GEMS system.

Chapter 19 - Designing Accurate Data-Entry Procedures

    In all the exercises below, design the code scheme and include it in the Values and Meanings area in Visible Analyst or in the Discrete area of the Element Description Form.

    1. Modify the Resource Type Code element, located on the Resource data store structure.

    2. Modify the Project Type Code element, located on the Project data store structure.

    3. Modify the Project Category Code element, located on the Project data store structure.

    4. Modify the Project Size Code element, located on the Project data store structure.

    5. Modify the Project Priority Code element, located on the Project data store structure.

    6. Modify the Project Status Code element, located on the Project data store structure.

    7. Modify the Project Category Code element, located on the Project data store structure.

    8. Create and edit table for the following input validation processes. Refer to the data flow containing the input screen for the elements that need to be included in the edit table.

      1. Process 1.1, Update Project. Input data flow: New Project Data

      2. Process 1.1.5, Edit Project Change Data. Input data flow: Project Status Updates.

      3. Process 1.3, Update Tasks. Input data flow: Task Information.

      4. Process 1.4, Update Milestones. Input data flow: Milestone Information.

      5. Process 1.5, Update Leader Information. Input data flow: Leader Information.

      6. Process 3.1, Edit Assignment Information. Input data flow: Assignment Information.

      7. Process 2, Update Resources. Input data flow: Resource Information.

      8. Process 4.1, Edit Work Completed. Input data flow: Work Completed Data.

Chapter 20 - Quality Assurance Through Software Engineering

    Create a structure chart for the following processes. If the program is on-line, you will need to add a module for receiving the screen and displaying the output screen. You may also have to add modules to read and write or rewrite records.

  1. Process 1.1, Update Project. Review the child diagram to determine the modules and their execution order.

  2. Process 1.3, Update Tasks. Refer to the diagram specifications as a starting point. The diagram overview portion will provide information about the execution order of the modules.

  3. Process 1.4, Update Milestones. Refer to the diagram specifications as a starting point. The diagram overview portion will provide information about the execution order of the modules.

  4. Process 3, Assign Resources to Tasks. Review the child diagram to determine the modules and their execution order.

  5. Process 5.2, Produce Budget Report. Review the child diagram to determine the modules and their execution order.

  6. Process 6.2, Query Milestone Information. Refer to the diagram specifications as a starting point. The diagram overview portion will provide information about the execution order of the modules.

  7. Process 6.3, Query Project Assignments. Refer to the diagram specifications as a starting point. The diagram overview portion will provide information about the execution order of the modules.

  8. Process 6.6, Query Resource Information. Refer to the diagram specifications as a starting point. The diagram overview portion will provide information about the execution order of the modules.

  9. Create a test plan for the following processes/programs. Examine the input screen to determine the type of data that needs to be validated. Examine the data flow diagrams to determine what files are being read and design data to test both the record found and not found conditions.

    1. Process 1.1, Update Project

    2. Process 1.3, Update Tasks

    3. Process 1.4, Update Milestones

    4. Process 1.5, Update Leader Information

    5. Process 2, Update Resources

    6. Process 3, Assign Resources To Tasks

    7. Process 4, Update Task Work