Assignment Cover Sheet
Technical Report
Accounting Systems 204
Due: Week 10 of semester (please refer to the unit outline, lecture and BB announcement for more details).
Name of Tutor:
Tutorial day / Tutorial Time:
Family Name / Surname:
Other Names:
Student ID:
Table of Contents
1.0 Introduction 1
2.0 The organisation 1
2.1 Background information 1
2.2 Key goals needed 1
2.3 Identification and assessment of risks relating to above goals 1
3.0 Business cycles 1
3.1 Revenue cycle 1
4.0 Database and file structure 2
5.0 Screens and Reports 2
6.0 Controls to mitigate risks & Residual risks identification 2
7.0 Appendices – File relationships and file structure, entry screens, and reports 2
8.0 Reference List 3
i
1.0 Introduction
Provide a very brief introduction to the technical report. State the purpose of the report (WHY you’re writing it) and a brief description of the plan or structure of the report so that the reader knows what to expect. 2.0 The organisation
Provide a short paragraph that briefly introduces the organisation relating to industry given by your tutor.
2.1 Background information
State the core business/es of your organisation as well as its vision and mission.
2.2 Key goals needed
Identify the key goals the organisation should have in order to achieve its vision and mission. It is important to include a consistent numbering system for the headings and subheadings and use the layout of the report's headings to indicate the sections and sub-sections.
2.3 Identification and assessment of risks relating to above goals
Identify the risks that the organisation faces when trying to achieve the goals you described in section 2.2. Then, assess these risks by given them a rating (e.g. Extreme, High, Moderate or Low) using the Risk Analysis – Risk Matrix given in the assignment pack. Identification of relevant business cycles3.0 Business cycles
Describe all the business cycles necessary to achieve the goals stated in 2.2 above.
3.1 Revenue cycle
Provide the narration, data flow diagrams (context and level 0) and document flowcharts for the revenue cycle stated in section 3.0. 4.0 Database and file structure
Using a relational database management system (RDBMS) of your choice (e.g. MS-Access, FileMaker, etc), create a database by linking the data files showing the attributes described in 3 above only. Attach screen dumps in an appendix.
Hint: Capture the screen displays by pressing the ctrl-PrtScn keys simultaneously. Paste the captured screen displays in the Paint software (click the start icon on your screen and select the Paint software). Crop and copy/cut, and then paste it in your document. Or, use Jing to capture screens (http://www.techsmith.com/download/jing/).
5.0 Screens and Reports
Describe why the 3 data entry screens and reports are necessary. Layout should be attached in the appendix.
6.0 Controls to mitigate risks & Residual risks identification
Refer to Risk Analysis – Risk ...
1. Assignment Cover Sheet
Technical Report
Accounting Systems 204
Due: Week 10 of semester (please refer to the unit outline,
lecture and BB announcement for more details).
Name of Tutor:
Tutorial day / Tutorial Time:
Family Name / Surname:
Other Names:
Student ID:
2. Table of Contents
1.0 Introduction 1
2.0 The organisation 1
2.1 Background information 1
2.2 Key goals needed 1
2.3 Identification and assessment of risks relating to above
goals 1
3.0 Business cycles 1
3.1 Revenue cycle 1
4.0 Database and file structure 2
5.0 Screens and Reports 2
6.0 Controls to mitigate risks & Residual risks identification
2
7.0 Appendices – File relationships and file structure, entry
screens, and reports 2
8.0 Reference List 3
i
1.0 Introduction
Provide a very brief introduction to the technical report. State
the purpose of the report (WHY you’re writing it) and a brief
description of the plan or structure of the report so that the
reader knows what to expect. 2.0 The organisation
Provide a short paragraph that briefly introduces the
organisation relating to industry given by your tutor.
2.1 Background information
State the core business/es of your organisation as well as its
vision and mission.
2.2 Key goals needed
Identify the key goals the organisation should have in order to
achieve its vision and mission. It is important to include a
3. consistent numbering system for the headings and subheadings
and use the layout of the report's headings to indicate the
sections and sub-sections.
2.3 Identification and assessment of risks relating to above
goals
Identify the risks that the organisation faces when trying to
achieve the goals you described in section 2.2. Then, assess
these risks by given them a rating (e.g. Extreme, High,
Moderate or Low) using the Risk Analysis – Risk Matrix given
in the assignment pack. Identification of relevant business
cycles3.0 Business cycles
Describe all the business cycles necessary to achieve the goals
stated in 2.2 above.
3.1 Revenue cycle
Provide the narration, data flow diagrams (context and level 0)
and document flowcharts for the revenue cycle stated in section
3.0. 4.0 Database and file structure
Using a relational database management system (RDBMS) of
your choice (e.g. MS-Access, FileMaker, etc), create a database
by linking the data files showing the attributes described in 3
above only. Attach screen dumps in an appendix.
Hint: Capture the screen displays by pressing the ctrl-PrtScn
keys simultaneously. Paste the captured screen displays in the
Paint software (click the start icon on your screen and select the
Paint software). Crop and copy/cut, and then paste it in your
document. Or, use Jing to capture screens
(http://www.techsmith.com/download/jing/).
5.0 Screens and Reports
Describe why the 3 data entry screens and reports are necessary.
Layout should be attached in the appendix.
6.0 Controls to mitigate risks & Residual risks identification
Refer to Risk Analysis – Risk Matrix used in section 2.3.
7.0 Appendices – File relationships and file structure, entry
screens, and reports
4. File relationships:
File structure:
Data Entry Screen and reports:
Textbook: Figure 12.6, page 358; Figure 13.4, page 399; Figure
12.8, page 361.8.0 Reference List
The reference list should be arranged in alphabetical order by
author surname and Chicago referencing style should be used.
More information on the Chicago referencing style can be
obtained from the Curtin library website:
http://libguides.library.curtin.edu.au/content.php?pid=141214&s
id=1212910
CBS Communications Skills Centre. 2013. Report Writing:
Structure and Content. Curtin University.
http://business.curtin.edu.au/local/docs/6_2011_post_IDQA_CS.
pdf
UniLife. 2013. “Report Writing.” Curtin University. Accessed
May 20,
http://unilife.curtin.edu.au/learning_support/report_writing.htm
#/learning_support/F1F437D92A4D49C6817991B0B3EA51EF.h
tm
1
Accounting Systems 204 - Assignment Marking Rubric
Standards
Criteria
5. Very Poor Effort
Poor Effort
Reasonable Effort
Exceeds Expectations
Excellent Work
Identification of inherent risks
Did not sufficiently identify basic key risks applicable to
achieving simple business goals (2).
Identified some basic key risks applicable to achieving simple
business goals (4).
Identified significant key risks applicable to simple business
goals (6).
Identified some significant key risks applicable to complex
business goals with interrelationships (8).
Identified most significant key risks applicable to complex
business goals (10).
Relevant business cycles
Did not sufficiently identify relevant business cycles and/or
relationships (1).
Identified some relevant business cycles but their relationships
are inappropriate (2).
Identified some relevant business cycles and their relationships
are appropriate (3).
Identified most business cycles but not all their relationships
are appropriate (4).
Identified most business cycles and their relationships are
appropriate (5).
Revenue cycle documentation
Did not sufficiently document the business cycle (4).
Sufficiently documented the business cycle but lacks many
important components (8).
Sufficiently documented the business cycle but lacks some
important components (12).
6. Completely documented the business cycle (16).
Completely documented an efficient business cycle (20).
Database, files and fields
Did not use any RDBMS software, DB normalized, primary &
foreign keys identified, tables properly related and important
fields identified (4).
Used RDBMS software, not normalized database. Fields and
primary & foreign keys insufficiently identified. Tables are not
properly related (12).
Used RDBMS software, database normalized, important fields
identified but not all primary & foreign keys identified (24).
Used RDBMS software, database normalized, all primary &
foreign keys identified and tables properly related but NOT all
important fields identified (32).
Used RDBMS software, database normalized, all primary &
foreign keys identified, tables properly related and all important
fields identified (40).
Screens and reports
Less than three relevant screens and reports designed (1).
Some of the three screens and reports designed are irrelevant
(2).
Three relevant screens and reports designed but not all fields
are identified (3).
Three relevant screens and reports designed and all fields are
identified (4).
Three screens and reports are relevant and properly formatted.
All fields are identified (5).
Risks mitigation
The controls identified are unclear and/or irrelevant.
Assumptions/limitations are not described (3).
The controls identified are clear and relevant.
7. Few assumptions/limitations are described (6).
The controls identified are clear and relevant.
Several assumptions/limitations are described (9).
The controls identified are relevant, significant and organised.
Assumptions/limitations are comprehensively described (12).
The controls identified are comprehensive, relevant, significant
and organised.
Assumptions/limitations are comprehensively described (15).
Written communication skills
Language used does not convey meaning to readers with clarity
and includes numerous errors (1).
Used language sufficiently well to convey basic meaning
although errors reduce effectiveness of communication (2).
Used language that generally conveys meaning to readers with
clarity although writing may include some errors (3).
Used language that conveys meaning to readers with clarity.
Any errors which occur do not reduce communication
effectiveness (4).
Uses language that skilfully and effectively communicates
meaning to readers with clarity and fluency, and is virtually
error-free (5).
Accounting Systems 204 (10804)
Assessment Task 1: Technical Report (to be completed
individually or in pairs)
Semester 1, 2014
Value: This assessment task accounts for 20% of the final
mark.
8. Due Date: Week 10 of semester (please refer to the unit outline
for more details).
Task: Write a technical report for a manager showing the:
a) attributes of a suitable database for management to achieve
the organisation’s* business goals and
b) control activities required to manage the inherent risks the
organisation faces.
*In week 1, your tutor will tell you which industry your
organisation is related to.
The report must include the following:
1.0 The organisation
1.1 Provide a brief background to the organisation including its
core business(es). State its vision and mission. (2 marks)
1.2 Identify the key goals needed to achieve its mission and
vision. (4 marks)
1.3 Identify and assess the inherent risks pertaining to the
achievement of these goals. (4 marks)
2.0 Identify all the business cycles necessary to achieve the key
goals stated in 1.2 above. (5 marks)
3.0 Provide details of the REVENUE cycle provided in 2 above
by drawing a context DFD, level 0 DFD, and document
flowchart, and the data attributes required. (20 marks)
4.0 Create a database by linking the data files showing the
attributes described in 3 above only using a relational database
management system (RDBMS) of your choice (e.g. MS-Access,
FileMaker, etc). (40 marks)
5.0 Design 3 data entry screens and 3 reports related to the
business cycle in 4 above. The layout must be shown but there
is no need to use the software used for 4 above. (5 marks) –
Describe why screens and reports are necessary but attached
screens and reports layout in the appendix.
9. 6.0 List the controls to mitigate the inherent risks identified in
1.3 above. For each control, state the type of control -
preventive, detective and corrective. (15 marks)
7.0 Written communication skill (5 marks).
Each of the seven points above will be a separate section in
your report. As well as these sections, you should also include
an introduction, a conclusion and a reference list. As well as
the points shown above, 5 points will be awarded to your ability
to communicate appropriately in written English.
Your report should have sections and numbering based on the
“template_Report_AS204_CS (1).docx” document.
Plagiarism is a serious academic offence. Students should get
familiar with Curtin policy on plagiarism to avoid committing
the offence. Student Guidelines for Avoiding Plagiarism and
Student Checklist to Prevent Plagiarism can be downloaded
from
http://academicintegrity.curtin.edu.au/global/studentbook.cfm.
Report Format:
The assignment must be:
· in 12-point Times New Roman font
· double-spaced with 1-inch margins, and
· printed single-sided in A4-sized paper.
The maximum length of the assignment is 7 pages, excluding
the cover page and references. Do not exceed the page limit or
use inappropriate formatting such as using smaller font size, 1.5
line spacing, or narrower page margin, etc. Note that it is the
quality, not the length of the report that determines the grade of
the assignment. Good business writing should be concise –
expressing more with fewer words.
10. File Format and File Name:
MS Word with a file name “Tutor’s Name_Student ID_Student
Name.docx”. For example, “Vincent_12345678_JoeBlogg.docx”
if your student ID is 1234567.
Submission:
The hard copy of your report must be submitted to your tutor’s
mailbox during the tutorial in week 10.
The soft copy of your work must also be submitted via Turnitin
on Blackboard. (You can refer to
http://www.youtube.com/watch?v=PcbGIAcNXjs for how to
submit your Turnitin assignment.)
Please note that the Blackboard site may be taken offline
occasionally for maintenance purposes. During these
maintenance periods, you will not have access to the materials
on Blackboard and will not have access to Turnitin. Curtin
Technology Services (CITS) will notify the university
community of the scheduled maintenance work generally around
two weeks in advance. Please make sure to check your Curtin
email regularly and to pay attention to the maintenance schedule
since this can affect the submission of your assessment tasks.
Late submissions will be subjected to penalties (please refer to
unit outline for more details).
11. INSTRUCTIONS FOR SUBMISSION OF ASSIGNMENT
1. The Assignment criteria have been made available in
Blackboard under the Unit Resources tab in the Assignment
folder.
2. The assignment that you are submitting will be marked in
accordance to the rubrics criteria that is available in
Blackboard. The criteria used are in line with the requirements
of the Assignment pack. For example, the criterion of Database,
files and fields requires you to use any relational database
management system (RDBMS) to construct database, files and
fields. Failure to use RDBMS will result in the tutor marking
your assignment consider the “Very Poor Effort: 0-20” column.
Marks up to 8 will also depend on the other criteria stated in
that cell. This is an example where the use of a RDBMS is very
important in meeting the unit’s objective.
3. All students are required to submit their assignments via
Turnitin. A Turnitin assessment with the title “Assignment ” has
been created under the Assessments folder.
Please follow the steps indicated in Turnitin when you submit
your Assignment. The following are instructions that you need
to comply with:
a. Select “Single file upload”.
b. Submission Title should be “Assignment”
c. The MS Word file submitted should be named as “Tutor’s
Name_Student ID_Student Name”. For example,
“Vincent_12345678_JoeBlogg”.
d. Please DO NOT submit any later than 5pm on 23rd May
12. 2014in which case marks equivalent to 10% to the total
allocated for the assignment will be deducted from the marked
value for every day that the assignment is late.
4. Please DO NOT include the assignment question in your MS
Word file that will be submitted via Turnitin. Only the answers
to the assignment question should be included in the MS Word
file.
5. You will only be given ONE attempt to submit your
assignment via Turnitin.
Good luck with your assignment and should you have any
further queries, please contact your respective tutor or myself.
Kind Regards, Vincent Chang
Risk Analysis – Risk Matrix
Risk Rating (E, H, M or L) is determined from the combination
of Likelihood and Consequence assigned to the risk behind each
finding.
1 (Insignificant)
2 (Minor)
3 (Moderate)
4 (Major)
5 (Catastrophic)
5 (Almost Certain)
M
14. EXTREME risk – senior or executive management’s immediate
attention needed, action plans and management responsibility
specified.
H
HIGH risk – senior or executive management’s immediate
attention needed, action plans and management responsibility
specified.
M
MODERATE risk – manage by specific monitoring or response
procedures, with management responsibility specified.
L
LOW risk – manage by routine procedures, unlikely to need
specific application of resources.
LIKELIHOOD
CONSEQUENCES
Rating
Descriptor
Description
Rating
Descriptor
Description (examples)
5
Almost certain
Can expect more than one event annually.
15. Occurs frequently in this industry.
5
Catastrophic
Multiple deaths;
Significant asset/facilities destruction greater than $25m or
greater than 6% of operational budget;
National TV news coverage and/or Parliamentary investigation;
Catastrophic, long term environmental harm;
Total cessation of services for more than one week and
disruption over subsequent months. Major facility is involved.
4
Likely
Can expect event to occur annually.
4
Major
Single death and/or multiple injuries;
Loss of asset/facilities $10M to $25M or up to 6% of
operational budget;
Major state media coverage and/or departmental investigation;
Significant long term environmental harm;
Total cessation of services for up to seven days and subsequent
disruption for two/three months.
3
16. Possible
Can expect event to occur once every three years.
3
Moderate
Individual serious injury;
Loss of asset/facilities $1M to $10M or up to 2% of operational
budget;
Regional media story and regional/district enquiry;
Significant release of pollutants with mid-term recovery;
Total cessation of services for up to one day and subsequent
disruption for one/two months.
2
Unlikely
Can expect event to occur once every ten years.
Has happened in the industry in Australia.
2
Minor
First Aid;
Loss of asset/facilities $10,000 to $1M or up to 1% of
operational budget;
Regional newspaper mention;
Minor/transient environmental harm;
Minor disruption to services for up to one month.
17. 1
Rare
Can expect event to occur only in exceptional circumstances.
Not known to happen in this industry.
1
Insignificant
No injuries;
Loss of asset/facilities up to $10,000 or up to 0.5% of
operational budget;
Regional newspaper, not front page;
Brief pollution but no environmental harm;
No disruption to operations.
Academic Activity:
1.
Teaching and Learning - Course Design & Implementation
No.
Academic Risk Identification
Analysis
Academic Risk Treatments
Risk No
What can happen
L
C
R
Key controls currently in place
Residual Risks
1
Areas of Risk: Quality of learning facilities and resources
18. 1.1
Unable to attract and retain suitable staff
4
4
H
(a) Strategies to attract and retain quality staff
(b) Academic staff engagement in research/scholarships in their
disciplines
(c) Specification in policies on required experience and
qualifications, application of policies across departments
(d) Policies to supporting equity and diversity of staff profile
(a) Current economic/RQF environment
Learning facilities inadequate, over-crowded or otherwise
inconsistent with student and/or legislative requirements
3
3
H
(a) Design and equipping of teaching spaces e.g. Engaging
Learning Spaces Working Party
(b) Provision of resources identified through benchmarking,
allocation of resources to priority teaching areas, provision of
resources to meet equity obligations
(c) Policies and processes on resource acquisitions, archiving
and/or decommissions
19. (d) Consultation with staff and students on research and
teaching needs
(e) Currency and relevance of library collections
(f) Policies and processes on use of the internet
(g) Archiving of course profiles and teaching materials
(h) Disaster recovery plan
(i) Provision of learning technology and network capacity for
staff/students
(j) Access to learning resources, compliance with equal
opportunity legislation
(k) Physical facilities and time-tabling software
(a) (i) Quality of offshore learning facilities
(ii) Insufficient flexible learning spaces
PAGE