Management Information Systems
Specific cases are given during the conference. The case will be a decision‐making problem outlining a small business’ environment and needs. Competitors will analyze the situation and recommend an information system solution to address the issues raised.
Management Information Systems is a ‘Collaborative Object Test and Role Play Event’. These events consist of two parts: an objective test and an interactive role play.
Scroll down for object test subtopics.
Two 4″ by 6″ not cards will be provided to each competitor and may be used during event preparation and performance. Information may be written on both sides of the note cards. Note cards will be collected after the presentation.
No Additional Reference Materials Allowed
Prep Time: 20 minutes
Performance Time: 7 minutes
1. Demonstrate knowledge of the key functions and subsystems of the network system.
2. Demonstrate knowledge of the system life-cycle approach and identify and explain the steps in the systems development life cycle.
3. Identify the functions of systems analysts.
4. Select basic fact-gathering techniques to be used and conduct a preliminary investigation.
5. Record facts gathered through the system investigation.
6. Define the scope of the systems project.
7. Identify time, technology, and resource constraints.
8. Perform appropriate diagnostic tests.
9. Investigate system alerts.
10. Design system output, system input, files, and processing.
11. Analyze the interaction of the operating system and hardware architecture.
12. Justify the communications selections for the system (e.g., single PCs, LANS, and/or WANS).
13. Identify the system components and their relationships.
14. Specify the workflow system.
15. Develop programming specifications and program the system.
16. Test and document the system.
17. Design a framework for evaluating information system function and individual applications.
18. Compare the capabilities of an application with the requirements it is intended to meet.
19. Identify alternative outcomes of the application verification process.
20. Evaluate processes and outcomes including the results and probabilities of errors.
21. Modify inputs, outputs, and processing to refine an application.
22. Determine needed follow-up actions including recommendations for new features or enhancements to existing tools.