The purpose of the RPL procedure

RPL, Recognition for Prior Learning, is an established practice in equating non-formal learning with formal university/college courses. The objective is to establish whether or not the applicant has acquired the body of knowledge represented by the course concerned. The "course" in this sense may vary from a single subject to a complete degree, diploma or certificate qualification. In the latter case of a complete qualification, it would be extremely rare for an educational institution to grant such a blanket exemption, most institutions requiring a minimum amount of time spent in formal study towards the award.

In the context of ACS membership requirements, an applicant is required to have reached one of two levels of academic achievement depending on the level of membership applied for:

• A "Professional Level Course" - a university degree or graduate diploma which covers the prescribed ACS Core Body of Knowledge; or
• An "Associate Level Course" - a course which covers a substantial proportion of the Core Body of Knowledge, typically a TAFE Diploma, a computing major within a university degree or the ACS Examination in Information Technology.

The nature of the Core Body of Knowledge (CBOK)

In applying to have prior learning and experience credited towards this CBOK, the following points need to be kept in mind:

• The CBOK is not entirely skills-based. While there will normally be some component of skill to be acquired, the CBOK is based on the ability to understand underlying principles and concepts, to be able to appraise these concepts critically, to be aware of possible alternatives and to be able to apply the knowledge in a variety of situations.

• Applicants are expected to be abreast of current literature. Most topics within the CBOK are based around the work of authors who are currently regarded as leading developers of their disciplines. Applicants are expected to have a working knowledge of this literature and to be able to appraise it critically in comparison to the work of others and to workplace practices.

• Years of practical experience may not be regarded as being as relevant as the applicant would expect. Past practices may no longer be seen as desirable. Volume of practice is not necessarily a guarantee of exposure to a variety of situations, of being able to distil underlying principles nor of being able to extrapolate from one environment to another.

• Most practitioners of any discipline are usually caught up with the daily problems of the workplace. They may not be abreast of new developments nor have the time to read current professional literature.

• In short, the qualities which make practitioners valuable to their clients and employers are not necessarily those which promote a wide knowledge of contemporary information technology for which an RPL applicant would claim exemption.

What will the RPL process expect you to demonstrate?

As mentioned above, the qualities which would impress a prospective employer are not necessarily those which will count towards credit for the CBOK. An exhaustive list of specific systems worked on, programming languages written, manufacturer-specific products used, operating systems mastered, etc, are not as impressive in an RPL context as they might be in applying for a promotion in the marketplace. A litmus test would be the acceptability of the applicant’s submission as granting an exemption from one or more of the academic units comprising the formal qualification for which equivalence is being claimed.

The factors which will carry the most weight in RPL applications are likely to be:

• Indicate what you have learned from what you have done rather than what you have done. What is important in gaining credit towards, say, software knowledge is not so much the number of languages you know nor the number of lines of code you have written but rather what you have come to understand about the processes of designing and developing high quality software. In information systems knowledge, it is more important to be able to explain the issues involved in designing and implementing successful computer-based systems rather than providing a long catalogue of the types of systems on which you have worked.

• Be able to show some introspection in terms of the changes to your methods of working which have occurred over your time of employment. This may apply to your own effectiveness and productivity and to dealing with clients and other practitioners.

• Show that you have made an attempt to keep abreast of developments in your profession. Know what these developments are, who are their proponents, why they may be seen as advances in professional practice and not merely as fads or local phenomena. Do not be afraid to be critical of these issues but have reasoned criticisms not just reaction, be it positive or negative, to change.

• Demonstrate the level of involvement which you have had in the things which you claim to have done. A claim such as "I was involved in the design of our company’s computerised accounting system" is meaningless. What was the nature of your involvement? Did you merely contribute some suggestions as to what the system should do? Did you carry out a formal feasibility study to determine the system’s requirements? Did you assist in the technical design of a relational database? Did you write the software which implemented the system? Did you write the user documentation and train the prospective users of the system? Did you participate in the specification and selection of the hardware/software/communication network?

What evidence to present in support of your application?

The nature of the supporting evidence is more important than its volume. Be as specific about the learning outcomes of your activities as you can.

In particular :

• If you are claiming attendance at training courses, professional development seminars, etc, as being one avenue for your acquisition of knowledge then:
• Provide the course name, presenting organisation, date, the presenter, a detailed list of its contents and any assessment which may have taken place;
• Provide a statement of what you learned from the course;
• Describe what aspects of the course content you have been able to apply to your working environment - or what prevented their application.

• Describe the methods which you use to maintain your professional knowledge.
• List any journals which you read and explain why you think that they are relevant; if possible, quote some specific items which have made an impact on you.
• List books which you have read or authors whose work you feel is relevant and explain what you have gained from them.

• In describing the nature and extent of your work experience :
• Don’t merely give the titles of your positions, explain the specific nature of your duties and attempt to relate them, where possible, to the content of the CBOK.
• Explain what you have learned from what you have done.

• If you are claiming software development experience :
• If samples of your code are easily obtainable, include something which will illustrate what you think is important about programming. Sheer volume will NOT impress!
• Remember that programming methodology will often be more important than the language used.

• If you are claiming information systems experience :
• Explain what, if any, development methodology(ies) or tools you may be familiar with.
• Explain precisely the part which you played in the system project(s) and provide copies of any documentation to which you may have made some contribution and which are able to be released for outside perusal.
• If you have contributed to technical factors such as database design or data communications/network facilities, describe the nature of your contribution and the reasons for taking the design choices used.

In conclusion . . .

The basic approach stressed here has been to demonstrate what you have learned rather than what you have done. RPL is recognition of learning not a reward for work done for an employer or client. Examine what the CBOK components expect you to know and attempt to provide evidence that you have already gained some or all of that knowledge.

Remember that your application is taking the place of a university or college degree or diploma. Experience alone, of however long a duration, is no longer sufficient for ACS membership. The benefit to all ACS members of this greater rigour is the recognition of the ACS as a truly professional society.