|
|
|
马上注册，结交更多好友，享用更多功能，让你轻松玩转社区。
您需要 登录 才可以下载或查看，没有帐号？FreeOZ用户注册
x
今日收到acs来信，看不明白，还要提供什么资料，请帮忙看看
* A new RPL Section 3 that has been completed in line with the instructions. The detail given is too vague for the assessor to make an accurate determination. (Description below)
Documents submitted for assessment will not be returned to the applicant therefore it is in the applicant's own interest to have multiple copies certified.
When sending in extra documents please attach a copy of this email or list your reference number.
If after 35 days (if you live in Australia) or 49 days (if you live overseas) from the date of this letter, the requested documentation is not received the Australian Computer Society will forward your file to an Assessor , whereupon a result will be issued on the documentation held.
PLEASE NOTE THAT FURTHER REQUESTS WILL NOT BE MADE FOR ADDITIONAL DOCUMENTATION.
Regards
---------------
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?
[ 本帖最后由 bigrixin 于 30-5-2007 12:32 编辑 ] |
|
发表于 30-5-2007 13:30:20
收藏
赞
踩
楼主
