A Summary Section 1.5 pages This should summarize the key themes/problems/issues in the case. An Analysis section 2.5 pages The analysis section should not repeat what is already in the case study and the summary. Instead, students are required to apply the concepts learned in the lectures and readings pertaining to the modules in their analysis of the case studies. Failure to do so will result in the deduction of points.
Students are expected to apply the concepts learned in the lectures and to discuss in their own words, as part of the analysis, what they think are the positives or negatives in the management and execution of the projects in the case, the causes of those positives or negatives, what specifically could have been done to avoid the negatives, and what specifically could be done to address such issues in the public IT world. For example, some of the concepts in Module 1 lectures regarding minimization of IT failures include defining and implementing goals and objectives, developing and enforcing policies and procedures, performing requirement analysis, and recruiting and retaining competent IT management and staff. In Module 2, some concepts regarding acquiring software include specifying operating requirements, requesting vendor demonstrations, and checking a vendor’s historical performance. Students are expected to discuss in the analysis, based on the information in the case studies, the extent to which these concepts occurred in managing and executing the projects in the case studies. See the case studies analysis rubrics (grading criteria) for further details.
#Innovative #adaption #accounting #software