ACS Project Report Form

Australian Computer Society

Skills Assessment
1 July 2012

The ACS Project Report Form is required for all Recognition of Prior Learning (RPL) Applications
Information about the Areas of Knowledge
After studying the ACS Key Areas of Knowledge document, tick those areas of knowledge that you
believe you have learned from your experience.
Please Note: None of the areas are mandatory. Applicants will be allowed an opportunity to address
areas of knowledge they acquired through their experience.
Required Level of Knowledge Acquisition
You are required to demonstrate a clear comprehension of a number of the individual thematic modules
within your chosen knowledge areas. You should also be able to demonstrate application in at least one
of the units or modules which should be clearly supported by professional references included and the
Project Reports submitted in section 4.
Please detail the relationship between the selected Areas of Knowledge above and what you have
learned from the type of work and qualifications.
This section of RPL needs to be specific and detailed as to how and where you have learned the
knowledge from.
This is one of the most important parts of the assessment and therefore ought to be comprehensive in
its content and clarity.
It is important that you explain for each chosen area of knowledge:
(a) What you have learned,
(b) How you acquired the knowledge, and
(c) Your experience in applying the knowledge in your working environment.
Please complete the following template.

Areas of Knowledge that you believe you have learned from your experience

[EXPANDABLE TYPING AREA]

TR.Technology RESOURCES
TR1. Hardware and software fundamentals
TR2. Data and information management
TR3. Networking

This section approximately consists of 2200-2400

words based on the ANZSCO code. To purchase
a complete Version visit:
http://www.rpl-it.com
TB.Technology Building
TB1. Programming
TB2. Human-computer interaction
TB3 & TB4.System development and acquisition

Australian Computer Society | ACS Project Report Form | 1 July 2012

Page 2

This section approximately consists of 800-900

words based on the ANZSCO code. To purchase
a complete Version visit:
http://www.rpl-it.com
SM. Services Management
SM1. Service management
SM2. Security management

This section approximately consists of 800-1000

words based on the ANZSCO code. To purchase
a complete Version visit:
http://www.rpl-it.com
OM. Outcomes Management
OM1. Organisational and Management Concepts
OM2. Change management

This section approximately consists of 500-700

words based on the ANZSCO code. To purchase
a complete Version visit:
http://www.rpl-it.com
A brief summary of how you have learnt the area of knowledge

This section approximately consists of 250-350

words based on the ANZSCO code. To purchase
a complete Version visit:
http://www.rpl-it.com
Evidence of applying claimed knowledge to a working situation

[EXPANDABLE TYPING AREA]

Please submit certified verifiable statements from your employers to support your claims.
Declaration of Authorship
This declaration must be completed. Please tick to confirm the following:

Australian Computer Society | ACS Project Report Form | 1 July 2012

Page 3

 I am aware of the ACS regulations on plagiarism outlined in the ACS PASA Guidelines for Applicants.
The Section 3 responses I am submitting are entirely my own work except where otherwise indicated.
The above has not been submitted, either wholly or substantially, by any other applicant.
I have clearly indicated the presence of quoted or paraphrased material and referenced all sources.
I have acknowledged appropriately any assistance I have received.
I have not sought assistance from any professional writing/editing agency.
I agree to make available any electronic version of the work on request from the assessors should
this be required in order to check for plagiarism.

Applicants signature:

Date: ..

RPL Project Reports

A project report is a coherent written description of a project or engagement that provides you with the
opportunity to show how you perform as an IT (Computing) Professional, and enables assessors to
understand and question your thought processes and decisions. Each report is to relate to a significant
project or work episode undertaken by the applicant during his or her professional career.
The purpose of these reports is to enable applicants to demonstrate their command and
implementation of the areas of knowledge claimed in Sections 2 and 3 of your application.
Please note: Applicants are required to provide two project reports.
Of the two reports, one must pertain to project undertaken within the last three years, and the other for
project within the last five years. Projects over two years long may be used for both reports under either
of the following conditions:

The project has clearly-defined work efforts which took place in parallel, each with their own
solution development and design activities and their own deliverables.

Australian Computer Society | ACS Project Report Form | 1 July 2012

Page 4

The project had clearly-defined phases that were executed in succession, each with its own
solution development and design activities and deliverables. Note that a second project phase
that constructs and implements the solution developed by the first phase does not meet this
requirement.

Depending on the nature of the applicants role in the project, this would be expected to cover a
selection of such factors as:

System analysis and design and software engineering methodologies used;

Contribution to the processes involved in the design and implementation of enterprise-wide
computer systems;
Programming languages, design paradigms and implementation procedures adopted;
Database and/or file design and management techniques employed;
Network topologies, including size, distribution and security facilities installed;
Project management and quality assurance techniques followed;
Internet application design, including database interactivity and security measures
implemented;
ICT managerial activities, demonstrating the nature and extent of responsibilities

The following pages provide a template for your reports.

When writing your reports please provide your own thoughts do not just copy project documentation.
Diagrams from the project documentation may be helpful, but the text should be in your own words.
Please use the first person in your discussion, so it is clear to the assessors what you did versus what
others did say I did X rather than X was done.
Diagrams may be helpful, but please ensure that they are relevant, readable, and help the assessors to
understand what you did on the project.
Focus on quality rather than quantity.
You must complete and sign Declaration of Authorship for each project report.

Project Summary:
Project Name
Project 1
Project 2

XYZ-1
XYZ-2

Start Date
mm/yyyy
mm/yyyy

End Date
Mm/yyyy
Mm/yyyy

Project 1: <XYZ-1>
i. Project Summary
1. Identification
Clients Company
Name
Trading Name/s
Company Size
Business Address

XYZ
XYZ

#
XYZ

Contact Numbers

Tel: +1111

Web Address

http://www.example.com

Australian Computer Society | ACS Project Report Form | 1 July 2012

Fax: +1111

Page 5

Email Address
Nature of project
Location of project
Name of your
employer
2.

[email protected]

XYZ
XYZ

Duration
From
mm/yy
mm/yy

To
mm/yy
mm/yy

Project team size

Your Team
nn

Client
nn

Size of team led by you

nn

nn

Total project duration

Your involvement
3.

4.

Resources

Personal Involvement
Please list the phases of the project in which you were personally involved

Start
mm/yy
mm/yy
mm/yy
mm/yy

5.

Completion Phase Description

mm/yy
mm/yy
mm/yy
mm/yy

Describe your role(s) and responsibilities, including the leadership aspects.

Roles and Responsibilities

This section approximately consists of 40-60

words based on the ANZSCO code. To purchase
a complete Version visit:
http://www.rpl-it.com
ii. Business Opportunity or Problem
1.

Describe the business opportunity or problem(s) this project addressed and how it related to the
(internal or external) clients needs.

Australian Computer Society | ACS Project Report Form | 1 July 2012

Page 6

This section approximately consists of 60-80

words based on the ANZSCO code. To purchase
a complete Version visit:
http://www.rpl-it.com
2.

Describe the scope and complexity of the problem.

This section approximately consists of 20-40

words based on the ANZSCO code. To purchase
a complete Version visit:
http://www.rpl-it.com
3.

Describe your relationship and communications with client management / user management /
end users.

This section approximately consists of 60-80

words based on the ANZSCO code. To purchase
a complete Version visit:
http://www.rpl-it.com
iii. Solution
1.

Discuss your contribution to the solution, project or engagement including the rationale
behind key choices. Please enumerate the alternatives you considered and your reasons for
their rejection.

This section approximately consists of 100-150

words based on the ANZSCO code. To purchase
a complete Version visit:
http://www.rpl-it.com
2.

Enumerate and describe the key decisions you made, and the reasons for making them as you
did.

Australian Computer Society | ACS Project Report Form | 1 July 2012

Page 7

This section approximately consists of 170-220

words based on the ANZSCO code. To purchase
a complete Version visit:
http://www.rpl-it.com
3.

Describe the design method you used on this project and the rationale for its selection.

This section approximately consists of 140-160

words based on the ANZSCO code. To purchase
a complete Version visit:
http://www.rpl-it.com
4.

List the design tools you selected for use on this project and discuss the rationale for their
selection.

This section approximately consists of 380-450

words based on the ANZSCO code. To purchase
a complete Version visit:
http://www.rpl-it.com
5.

List the major deliverables of the project that you were responsible for or contributed to, and
summarize the reason for their inclusion.

This section approximately consists of 60-80

words based on the ANZSCO code. To purchase
a complete Version visit:
http://www.rpl-it.com
iv. Results
1.

Was your solution implemented? If so, describe the role, if any, you had in the implementation.
If not explain why not.

This section approximately consists of 40-60

words based on the ANZSCO code. To purchase
a complete Version visit:
http://www.rpl-it.com

Australian Computer Society | ACS Project Report Form | 1 July 2012

Page 8

2.

Assess the overall success or failure of the project. Comment on client satisfaction, attainment
of objectives, and ultimate versus proposed cost and schedule.

This section approximately consists of 30-50

words based on the ANZSCO code. To purchase
a complete Version visit:
http://www.rpl-it.com
v. Lessons Learned
In retrospect, what you might have done differently on this project and what lessons did you learn?

This section approximately consists of 80-110

words based on the ANZSCO code. To purchase
a complete Version visit:
http://www.rpl-it.com
vi. References
References are required to substantiate the experience cited in the above project report. Please include
verifiable certified statements from your referees.
vii. Project Report: Declaration of Authorship
This declaration must be completed and submitted with the securely bound copy of the Project Report.
Please tick to confirm the following:

I am aware of the ACS regulations on plagiarism, outlined in the ACS PASA Guidelines for Applicants.
The project report I am submitting is entirely my own work except where otherwise indicated.
It has not been submitted, either wholly or substantially, by any other applicant.
I have clearly indicated the presence of quoted or paraphrased material and referenced all sources.
I have acknowledged appropriately any assistance I have received.
I have not sought assistance from any professional writing/editing agency.
I agree to make available any electronic version of the work on request from the assessors should
this be required in order to check for plagiarism.

Applicants signature:

Australian Computer Society | ACS Project Report Form | 1 July 2012

Date: ..

Page 9

Project 2: <project name>

i. Project Summary
1. Identification
Clients Company
Name
Trading Name/s
Company Size
Business Address

XYZ
XYZ

#
XYZ

Contact Numbers

Tel: +1111

Web Address

http://www.example.com

Email Address

[email protected]

Nature of project
Location of project
Name of your
employer
2.

XYZ
XYZ

Duration

Total project duration

Your involvement
3.

To
mm/yy
mm/yy

Your Team
nn
nn

Client
nn
nn

Personal Involvement
Please list the phases of the project in which you were personally involved

Start
mm/yy
mm/yy
mm/yy
mm/yy
5.

From
mm/yy
mm/yy

Resources

Project team size

Size of team led by you
4.

Contact Numbers

Completion Phase Description

mm/yy
mm/yy
mm/yy
mm/yy

Describe your role(s) and responsibilities, including the leadership aspects.

Roles and Responsibilities

This section approximately consists of 40-60

words based on the ANZSCO code. To purchase
a complete Version visit:
http://www.rpl-it.com

Australian Computer Society | ACS Project Report Form | 1 July 2012

Page 10

ii. Business Opportunity or Problem

4.

Describe the business opportunity or problem(s) this project addressed and how it related to the
(internal or external) clients needs.

This section approximately consists of 60-80

words based on the ANZSCO code. To purchase
a complete Version visit:
http://www.rpl-it.com
5.

Describe the scope and complexity of the problem.

This section approximately consists of 20-40

words based on the ANZSCO code. To purchase
a complete Version visit:
http://www.rpl-it.com
6.

Describe your relationship and communications with client management / user management /
end users.

This section approximately consists of 60-80

words based on the ANZSCO code. To purchase
a complete Version visit:
http://www.rpl-it.com
iii. Solution
6.

Discuss your contribution to the solution, project or engagement including the rationale
behind key choices. Please enumerate the alternatives you considered and your reasons for
their rejection.

This section approximately consists of 100-150

words based on the ANZSCO code. To purchase
a complete Version visit:
http://www.rpl-it.com
7.

Enumerate and describe the key decisions you made, and the reasons for making them as you
did.

Australian Computer Society | ACS Project Report Form | 1 July 2012

Page 11

This section approximately consists of 170-220

words based on the ANZSCO code. To purchase
a complete Version visit:
http://www.rpl-it.com
8.

Describe the design method you used on this project and the rationale for its selection.

This section approximately consists of 140-160

words based on the ANZSCO code. To purchase
a complete Version visit:
http://www.rpl-it.com
9.

List the design tools you selected for use on this project and discuss the rationale for their
selection.

This section approximately consists of 380-450

words based on the ANZSCO code. To purchase
a complete Version visit:
http://www.rpl-it.com
10. List the major deliverables of the project that you were responsible for or contributed to, and
summarize the reason for their inclusion.

This section approximately consists of 60-80

words based on the ANZSCO code. To purchase
a complete Version visit:
http://www.rpl-it.com
iv. Results
3.

Was your solution implemented? If so, describe the role, if any, you had in the implementation.
If not explain why not.

This section approximately consists of 40-60

words based on the ANZSCO code. To purchase
a complete Version visit:
http://www.rpl-it.com

Australian Computer Society | ACS Project Report Form | 1 July 2012

Page 12

4.

Assess the overall success or failure of the project. Comment on client satisfaction, attainment
of objectives, and ultimate versus proposed cost and schedule.

This section approximately consists of 30-50

words based on the ANZSCO code. To purchase
a complete Version visit:
http://www.rpl-it.com
v. Lessons Learned
In retrospect, what you might have done differently on this project and what lessons did you learn?

This section approximately consists of 80-110

words based on the ANZSCO code. To purchase
a complete Version visit:
http://www.rpl-it.com
vi. References
References are required to substantiate the experience cited in the above project report. Please include
verifiable certified statements from your referees.
vii. Project Report: Declaration of AuthorshipP
This declaration must be completed and submitted with the securely bound copy of the Project Report.
Please tick to confirm the following:

I am aware of the ACS regulations on plagiarism, outlined in the ACS PASA Guidelines for Applicants.
The project report I am submitting is entirely my own work except where otherwise indicated.
It has not been submitted, either wholly or substantially, by any other applicant.
I have clearly indicated the presence of quoted or paraphrased material and referenced all sources.
I have acknowledged appropriately any assistance I have received.
I have not sought assistance from any professional writing/editing agency.
I agree to make available any electronic version of the work on request from the assessors should
this be required in order to check for plagiarism.

Australian Computer Society | ACS Project Report Form | 1 July 2012

Page 13

Applicants signature:

Australian Computer Society | ACS Project Report Form | 1 July 2012

Date: ..

Page 14