IT INFRASTRUCTURE EVALUATION REPORT [YOUR NAME AND ID] [DATE] Report Prepared for Assignment A01 ISYS90048 Managing ICT Infrastructure Semester 1, 2017 Table of Contents ________________________________________ Table of Contents 1. Introduction 2 1.1 Report Objectives 2 2. Background 2 3. Analysis 2 3.1 Choice of Framework 2 3.2 Detailed Analysis 2 4. Key Findings and Recommendations 3 4.1 Key Findings 3 4.2 Recommendations 3 Appendix 4 References 4 1. Introduction An overview of the purpose of this report, including:  What are the basic questions being addressed by the report?  What other requirements are being addressed by the report?  What is the scope of the report – what is included and what is not included?  A statement of any relevant assumptions made in preparing this report. 1.1 Report Objectives In this section, explain in simple terms the objective of this report in a single paragraph, and how this report is meeting the requirements of the assignment. 2. Background This section describes the organization that is being studied in this report, and for whom this report is intended. As an introduction provide an overview of the purpose and business environment of this organization. 3. Analysis A brief introduction to the mode of analysis adopted in this report. 3.1 Choice of Framework A statement of the framework chosen for analysis of this report. The choice of the framework requires a short justification. The framework provides objective material, against which the report will be analysed, so that the analysis is not based on your interpretation, but on the guidelines and requirements of the chosen framework. 3.2 Detailed Analysis The analysis should take the form of a detailed breakdown of the report against criteria that have been derived from the framework. A good way to present this is as a table: Guidelines / Criteria Evidence Assessment / Findings Statements of relevant criteria or guidelines, chosen from the framework. Each row of this table deals with a distinct statement of criteria / guideline. It is good practice to • Number these rows, for reference in other sections; • State criteria as conditions in the form: “The [client] should …” or “The [client] must …”. • Only have one criterion per row, so that it is clear against which criterion you are evaluating the respective evidence Evidence from the original report, using page / section references to indicate where that evidence is drawn from. This may be direct evidence, such as quotes from the report, or statements about the presence or absence of material in the report, or it may be indirect evidence that is implied by the content of the report being analysed. An assessment of the evidence in column 2, with references to the framework and other literature. A statement of any additional comments, and findings from the above assessment. Each assessment should apply to, and be within the scope of, the evidence and criterion for that particular row. It is good practice to: • State each of your findings using direct, clear statements, such as: “Conforms”, or “Does not Conform”, or “Partially Conforms” • Number your findings as F1, F2, F3 etc, for reference in later sections. Note that your analysis should also meet the requirements of the assignment, so that you include guidelines relevant to each of the requirements in this table, and address how well the organization has dealt with each of these issues. 4. Key Findings and Recommendations This section presents the key findings that arise from the analysis in section 3.2, and then present the recommendations for further action. It is important to clearly justify each recommendation, based on the analysis in section 3.2, and on other sources of material from the literature. The key findings are a summary of the main findings from the analysis in section 3.2. From the detailed findings in column 3 of the table in section 3.2, consideration of the deeper issues underlying these findings should lead you to these key findings. Present an overview of the method by which the key findings and recommendations of the report have been formulated. 4.1 Key Findings  What are the key findings of the report?  How have each of these key findings been derived, based on the analysis in section 3.2? References to numbered rows in the table from section 3.2 are a good practice to make it clear how your key findings have been derived.  It is good practice to number your key findings as KF1, KF2, KF3 etc, for reference in later sections. 4.2 Recommendations As a guide, recommendations should be restricted to the scope of the report. They should be forward-looking, and address the big issues being raised by the report. As a consultant, one of your tasks is to open the minds of the organizational staff to the wider issues in the marketplace, of technological change, of better structuring and management of information systems, and of organizational change. Each recommendation is suggesting that the organization do something to address an issue or problem that has been identified in the report through the analysis in section 3. In order for that recommendation to be accepted it must be justified, based on the analysis in section 3, and on information gained from the literature. Each recommendation should address a single topic, be simply worded, and be phrased in the form: It is recommended that [someone] should [do something] in order to address the [target issue of the recommendation]. Justification of this recommendation, based on the evidence, analysis and findings in section 3, and on material from the literature. The justifications form the core of this section. Each justification should provide a solid case in support of its recommendation, clearly based on the evidence and analysis in section 3, and on material from the literature. If a recommendation cannot be justified then it should not be included in the report. The reader of the report will base their assessment primarily on the quality of the recommendations and their justifications It is good practice to number your recommendations as R1, R2, R3 etc. Appendix The appendix is where you should provide all of the documentation that supports the body of your business plan, but are too large for the body, or would detract from the flow of the information content of the body. References All material that has been cited in the report must be referenced, using Harvard-style referencing. In particular, all web-based references must be in Harvard style. Examples: University of Melbourne Library (2010), University of Melbourne, Parkville, viewed 15 May 2013, . Laan, S (2013) IT Infrastructure Architecture – Infrastructure Building Blocks and Concepts, 2nd Ed, LuLu Press Inc.. Sotomayor, B, Montero, Ruben S, Llorente, IM & Foster, I (2009) "Virtual Infrastructure Management in Private and Hybrid Clouds," Internet Computing, IEEE , vol.13, no.5, pp.14,22, Sept.-Oct. 2009 .