RPL Sample for ACS Australia

Please complete the following 2 sections:

  1. The Key Areas of Knowledge – Section 1
  2. The Project Report Forms – Section 2

 RPL applications are for those applicants who do not hold a recognised tertiary ICT qualification and who have a minimum of 6 years of closely related experience.

This document provides the opportunity for applicants to demonstrate the knowledge learnt throughout their professional experience.


SECTION 1 – Key Areas of Knowledge

 Section 1 is based and will be assessed on the following document.  Please ensure you read and understand – The ACS Core Body of Knowledge for ICT Professionals (CBOK).

You must clearly explain how your experience and qualifications meet the selected Areas of Knowledge and specifically how and where you acquired the knowledge.

You are required to select one topic from the Essential Core ICT Knowledge (Topic 1 or Topic 2) and one topic from the General ICT Knowledge (Topic 3, Topic 4 or Topic 5).

Please ensure you address at least 2 subtopics from each of the topics chosen.

The ICT Key Areas of Knowledge:

Essential Core ICT Knowledge


  • ICT Professional Knowledge

Sub Topics are –

  1. Ethics
  2. Professional Expectations
  3. Teamwork Concepts and Issues
  4. Communication
  5. Societal Issues
  • ICT Problem Solving

Sub Topics are –

  1. Modelling Methods
  2. Processes to understand problems
  3. Methods and tools for handling abstraction

General ICT Knowledge

  • Technology Resources

Sub Topics are –

  1. Hardware and Software Fundamentals
  2. Data and Information Management
  3. Data Communications and Networking
  • Technology Building

Sub Topics are –

  1. Human Factors
  2. Programming
  3. Information Systems Development and Acquisition
  • ICT Management

Sub Topics are –

  1. IT Governance and Organisational Issues
  2. IT Project Management
  3. ICT Service Management
  4. Security Management


  • Identify the Area of Knowledge topic that you have chosen to explain by entering the name of the Area of Knowledge topic in the box.
  • Explain, in the expandable typing area, how you have acquired the knowledge and illustrated the depth of that knowledge.
  • You should NOT address all sub topics included in the Area of Knowledge in your explanation. Address at least TWO of the sub topics. Enter the sub topic name(s) in the box.
  • Be clear and concise in your explanation.
  • Limit each explanation to no more than one to one and a half pages.

In the following expandable typing areas, explain how you have acquired your in-depth knowledge in these topic areas through your professional experience. 

Essential Core ICT Area of Knowledge:

Topic 1.               ICT Professional Knowledge

Sub Topics are –

a.        Ethics

b.       Teamwork Concepts and Issues

c.        Communication


Sub topic 1:

Communication skills:

                 Communication skills are as necessary as technical skills in software engineering. The majority of software engineers work in teams, and to accomplish their tasks, it is essential for them to communicate with each other and also with clients through detailed discussion on software requirements. This issue is often neglected and overlooked, but it is equally essential to the success of teams, projects, and individuals in software.

I have always given communication and social skills high importance, and I still try to learn and improve my communication skills. These skills have been a catalyst to the success in my career as a software engineer.  As a junior software developer, I was responsible for providing training and demo to the end users of the software. I also had to make presentations to managerial level. It was that time when I realized that communication skills also have a vital importance in software engineering and I started to learn about improving my social skills and how to interact with my team members from the internet and books about communication. I began to understand that to get my job done I need to have excellent communication skills. I always preferred face to face communication rather than chatting or emailing because in face to face communication I had a better understanding of the person I was interacting with. I always tried to maintain good interaction with my colleagues and managers and users whom I provided training about the software. Working with different teams in different projects I got to interact with many different people, and that helped me a lot in learning more about communication skills. I welcomed feedback from my project fellows and my managers and always tried to be open to criticism and took it as an opportunity to improve myself and I still take their advice about how I can improve my performance.

Being a team leader, my primary task was to mentor junior software engineers and collaborate with colleagues, and I also interacted with software quality assurance team. At this post, I started to learn how to communicate as a leader, and I made sure I had an honest communication with every member of my team. I conducted regular meetings with my team to talk about outcomes of our project and listened to the opinions of each member. While communicating with junior team members, I chose to show encouragement instead of criticism which gave them the motivation to make extra effort to achieve our goals.

Sub topic 2:


Ethics is an essential part of work regardless of profession. Ethics play a crucial role in the life of Software Engineer because they have to interact with clients and also with team members and managers. I have always tried my best to follow the ethical and professional standards throughout my career. I still kept a professional relationship with my colleagues and respected my supervisors.

In the early part of my career, I was a junior software developer where part of my job was to report regular project progress to managers, and I performed this task in very formal manner. One of my duties was to provide training to the operators of the software my team developed. I respectably interacted with operators and tried to answer their queries politely. In the development process, I maintained a decent relationship with my team members and decided to contribute to the development to the best of my ability. I focused on learning more about software developing from colleagues and managers. Whenever I had Issues with my work, I approached my supervisors in a gracious way and asked them about solutions. By showing respect to my colleagues and managers I also gained their esteem and confidence.

To improve my social and ethical skills, I started to search on the internet about ethics in professional life and read the moral codes of software engineering through which I got a better understanding as for how I could improve myself morally.  I started to realize more about the importance of moral behavior in software engineering. Later on, in my career as a senior software engineer, I worked in projects as a team leader where I was responsible for monitoring and supervising the project. I always tried to be supportive and fair towards my team members and gave them advice whenever they got puzzled in their work. I still showed honesty to my colleagues. I also took part in requirement gathering, and I always maintained a respectful relationship with the clients and stakeholders.

Maintaining a professional behavior with my project teams and interacting positively with clients played a significant role in the success of my projects. I showed continued professionalism in my work which earned me respect and trust of people I worked with.

General ICT Area of Knowledge: ICT Management

Sub Topics are –

e.       IT Project Management

f.         Security Management

Sub topic 1: 

Security Management:

                Today, software engineering is evolving at a fast pace and keeping up with the pace of the modern technologies software organization have to deal with the security issues. The management of security is an essential part of developing software and running a successful business.

Being a software engineer, I have come across numerous security issues throughout my career. I have always tried to be careful in developing software and focused on building secure systems. I always follow the rules and regulations to maintain security in the product I develop and write the code according to the industrial standards. I always make sure to prevent any flaws in my code that can cause security problems.

I have always kept it my priority to develop the software to the best interest of the clients and gave importance to the safety and security of the products. During the requirement gathering and analysis process, I have held meetings with clients and discussed their security requirements. I interacted with security specialists in my team and spoke with them in detail about software safety issues and how we can overcome them. From design to the development phase, my team analyzed the security complications that could occur in our software and tried to find the solutions.

As a senior software developer, I took the responsibility of monitoring what measures were being taken by my team members to protect data security. In the code reviewing process, I made sure that my team took the necessary steps to make the product efficient and secure. I checked the flaws that could lead to harm the software and informed the security teams about them and guided them to resolve those issues. My project team always tried to develop systems that can resist malicious attacks.

I took part in the development of many projects that involved gathering sensitive information of the users and involved online payments. We made sure to implement advanced login and verification techniques in those projects so that users’ data remains secure. We developed our projects in such a way that authorized people could only access the data. We ensured that our system resisted external attacks from damaging data and programs.

I learned about new technologies and new techniques that could help us in making our systems more secure. I also instructed my clients about the strategies we used in developing their products and how they could control and use their system safely and securely. 

Sub topic 2:

Team Management:

                During my career as a software engineer, I have been working auspiciously on many projects over the last five years. Proper management helps in the success of projects and aids in achieving business goals of our organization. I have learned and implemented the fundamentals of project management as well as concept exploration & definition, analysis, development, design, etc. in my projects. I learned the practical implementation of my theoretical knowledge. I learned the practical application of IT project management skills during the execution of different projects. I performed well individually and as a part of a team during all the stages of prject management such as; analysis, design, development, and implementation of various projects wrapping the entire project lifecycle from concept development to yielding.

As a Senior Software developer, I have coordinated in several projects. I was responsible for setting up teams and providing tasks to the members according to their skills and knowledge.  I always picked up a team of people who had common technology interests. By talking to each person individually, I got to recognize their abilities and provided tasks accordingly. I avoided giving nontechnical functions to programmers in my team. I handed out specialized tasks to people who had expertise in a particular task. I mentored junior members of the team and provided them guidance to solve their issues. I monitored all the functionality of the projects and tried to provide expertise and recommendations to colleagues to achieve our goals. I made sure everyone on the team was inputting their equal effort to complete their tasks.

I always tried to facilitate growth and told my employees to focus on one thing at a time. This technique helped in boosting the work rate of the employees. I made sure everyone was working as a team and kept a steady momentum to complete our projects. I tried to listen to every member of the team individually, and one on one conversation with them helped me to understand the interests of my employees. I encouraged them to research new technologies so that we can keep up with the latest tools and techniques to develop our software. I worked with software quality assurance teams to get to know if we were following the industrial standards and I also suggested improvements to them.