Industry Project Report Format and ACS CBOK

Industry Project Report Format and ACS CBOK

Industry Project 1

(Report Format and ACS CBOK)

Institution Affiliation

The ACS CBOK is the body with the mandate of accrediting the Information Communication Technology professionals in Australia [1]. The report of the ACS CBOK consists of several subtopics which must be in line with body standards. These subtopics are what build the project. According to the given case scenario, I will discuss on the quality of the format used in writing the report and the appropriateness of the ACS CBOK mapping to the project description and justification.

To ensure a clear visualization of the project report, the table of content must clearly show the chronological procedure of the parts in the project report [3]. It must start with an introduction followed by the literature review all the way to the appendix which comes after the references. However, in our case, the table of content has not shown any consideration of the requirements as it has mixed up different parts. Moreover, both the seconds and the fifth (appendix) page of the report contains the report title "Low-cost Network Protocol Analyzer." The report title in the appendix is against the standards of a quality report format.

An appendix in the project contains supplementary materials that are not part of the project, but they help in better understanding of the project [4]. Nevertheless, the appendix of the project does not encompass these materials. It contains the project title and purpose of the project which should be included in the main part of the project. Moreover, the appendix contains some logical diagrams which help in the further understanding of the content [6]. However, in the case, the report has not considered any logical diagram such as the diagram showing how scanning was implemented. In addition to the content, it is clear that appendix comes after the references. The report has not considered the formatting for the appendix as it is placed even before the references and they contain the wrong information which should not be included in the appendix.

For the analysis in any report, the scope analysis and requirement study are the essential part of the report [5]. The scope analysis is done to search for the high-performance but at the same time of low cost. The security requirement is well outlined such that it is evidenced that unused ports are vulnerable to various cyber-attacks [2]. The product selected is the Raspberry Pi which is the affordable network analyzer. Additionally, the project has also provided a list of some of the low-cost tools which can help reduce data loss. Therefore, the objective of the project has been achieved after research was conducted.

Although the aim of the report has been achieved through analysis, its presentation format has not shown any consideration to the required standards. The format that has been used has no chronological order of how the activities should follow each other. It, therefore, becomes hard for the readers to have a flow understanding of the project. The ACS CBOK guideline moreover, has been followed appropriately followed. It is, therefore, essential to ensure the correct format of a report has been followed for a better understanding of the objective.


[1] C. Walker, "Accrediting agencies: Toward practical ethics of professional accreditation," In the Oxford Conference. A re-evaluation of education in architecture, vol. 12, 2008, pp. 249-253.

[2] J. Chris and D. Gurugubelli, "Identifying the cyber-attack surface of the advanced metering infrastructure," The Electricity Journal vol. 28, 2015, pp. 94-103.

[3] E. Pupa, Lawrence and L. Carpenter, "Morning report: a successful format," Archives of Internal Medicine, vol.14, no. 5, 2017, pp. 897-899.

[4] R. Steven, Writing a proposal for your dissertation: Guidelines and examples. Guilford Publications, vol. 8, 2013, pp. 211-231.

[5] Serrador, Pedro and K. Pinto. "Does Agile work? —A quantitative analysis of agile project success," International Journal of Project Management, vol. 33, 2015, pp. 1040-1051.

[6] Wolery, Mark, K. Lane, and E. Common, "Writing tasks: Literature reviews, research proposals, and final reports" In Single Case Research Methodology, vol. 7, 2016, pp. 43-76.