Case Study. Read the case and write a paper. Here are some guidelines:
1. Executive Summary – ruin the ending for me. A two-paragraph to one page overview of what is contained within. Includes explanation of the recommendations.
2. Overview – very brief summary of the key issues of the case. Remember that this section is intended to motivate the discussion only – not to rehash in detail what we already know.
3. Problem Statement – Rank ordered hierarchy of the problems facing the organization. Be brief, concise and crisp. Do not be wordy.
4. Discussion – Explain why these are the problems, why you have rank ordered them as such, and provide some further details about the nature of each problem.
5. Alternatives – Provide a list of possible strategic organizational alternatives. Identify which are mutually exclusive, which are not. Explain the relative advantages and disadvantages of each.
6. Scenarios – Hypothesize several different environmental/organizational scenarios that might affect the firm. Assign likelihood to each.
7. Praxis – Cross-analyze the alternatives provided (#5 above) with the scenarios (#6) to determine the most functional strategies.
8. Recommendations / Conclusions – Again, concise.
The following is another way of looking at a case study and provides a framework for analyzing an existing system or designing a new one, as far content is concerned. Whether you are considering an analysis of an existing information system or a design of a proposed system in an organization, this framework should be helpful in providing a structure and contingent conditions that will help with the analysis. The analysis should provide a clear and detailed description of the system, its purpose, and its place in the organization. In order to accomplish this you should include the following:
A description of the organization and its mission, goals, structure, influencers, stakeholders and staff. Include information on culture, politics, standard operating procedures and any other organizational factors that are relevant. A strategic analysis, such as a SWOT analysis, can be considered.
A description of the organization’s environment, including key players and their impact on the demand for information output, and therefore the Information System design.
An Analysis of user needs (informational and otherwise) and how users may perceive and use the Information System. Special attention should be given to managers and their needs for decision-making. Given the importance of users in the success of a system, this section is as important as the organizational and technology issues.
A description of the technology, i.e., hardware, software, database and security needs and applications in the system.
A description of the system’s development process: systems development life cycle, prototyping, etc., and who was or should be involved in the development process.
Last Completed Projects
| topic title | academic level | Writer | delivered |
|---|