HSC Assessment Task Notification

Enterprise Computing

Course: Enterprise Computing Student: __________________________________

Assessment Receipt:
You are to complete the Sign Off Quiz on Canvas to acknowledge receipt of your HSC Assessment
Notification.
Task Type: Project Proposal
Syllabus Outcomes, Weightings and Components:
Syllabus Components and Weighting
Outcomes Knowledge and understanding of Skills in critical thinking, research, Task Weightings
course content analysing and communicating
EC-12-01, EC-12-02, EC-12- 5% 15% 20%
03, EC-12-04, EC-12-08
Task Summary:
In this task, you will develop a proposal for an enterprise computing system. An enterprise computing
system is a system that supports the operations, management, and decision-making processes of a
business or organisation. These systems are often used for managing data, automating processes,
improving communication, and making informed business decisions.
Your proposal should describe how your system will solve a specific problem within an organisation or
enterprise. The proposal should draw on your knowledge of Data Science, Data Visualisation,
and Intelligent Systems to develop a well-researched, feasible solution.
This proposal will form the foundation for your next assessment task, where you will create a high-fidelity
prototype of the system you propose. Therefore, it is essential that you propose a system that is realistic
and achievable within the constraints of the task, which includes developing a prototype that demonstrates
the core functionality of your system. Make sure that your system design is well thought out and can be
practically implemented in the next phase of the project.
Overall Word limit: 2000 words (excluding diagrams and charts).
Section What to Include
1. Introduction • Briefly introduce the enterprise system and the problem it aims to solve.
(approx.150-200 words) • State the goals of the proposed system and why it’s important to address the issue.
2. Problem Definition • Define the problem clearly and explain its relevance.
(approx.200-250 words) • Use a simple diagram (e.g., flowchart) to illustrate the problem.
• Outline the research findings, focusing on key tools, technologies, resources relating to
3. Research & the defined problem.
Planning • Develop a planning strategy (e.g., Gantt chart) for time and resource management.
(approx.250-300 words)
• Briefly discuss the methodology (iterative process, testing, etc.).
4. Tools & • List and justify the tools and methods you’ll use to design and develop the system (e.g.,
Methodologies software, data management tools, collaboration platforms).
(approx.200-250 words)
• Provide an overview of the system design, including major components and how they
address the problem.
5. System Design • Identify key system features (e.g., user-friendliness, ease of maintenance).
(approx.300-400 words)
• Include relevant diagrams to illustrate the system design (e.g., system flowcharts, data
flow diagrams, decision trees).
6. Development • Outline the main stages of the development process (e.g., prototyping, testing).
Process • Identify how the project will be evaluated throughout against the chosen problem (e.g.,
(approx.200-300 words) feedback, testing).
7. Impact of Changing • Discuss how modern enterprise factors (remote work, offshore development, freelance
Enterprise work) influence the project.
Landscape • Explain how these factors support the system’s relevance or scalability in the future.
(approx.150-200 words)
• Summarise the key points of the proposal.
8. Conclusion • Reaffirm the problem the system solves and its potential impact.
(approx.150-200 words)
• Briefly discuss the next steps for development.

1
Marking Criteria (Outcome Based):
Students will be assessed on how well they:
• Explain how systems meet the needs of a range of enterprises.
• Explain the function of data and information within enterprise computing systems.
• Explain and evaluate how data is safely and securely collected, stored, and manipulated when developing
enterprise computing systems.
• Explain how data is used in enterprise computing systems.
• Justify the selection and use of tools and resources to design and develop an enterprise computing system.
Drafting Process and Assessment Feedback:
There will be no submission of drafts, however, feedback will be provided by the teacher during designated lessons.

Submission Information:
Digital Submission:
• You are to submit your assessment via the Canvas drop box prior to 8.30am on Wednesday 9th April 2025
• You must keep a copy of your assignment
• No emailed submissions or flash drives will be accepted
• If you are unable to submit the assessment on or before the due date, you will need to complete an
illness/misadventure form and submit to the Faculty Head Teacher as per the Assessment Handbook
• Late submissions will result in marks being deducted as per Assessment Handbook
• Unjustified and/or unexplained absences in any periods the day before and/or the day of the task may result in
a penalty as per the Assessment Handbook

Additional Information:
• Please carefully read and follow the Task Description and Marking Criteria above.
• Read the HSC Assessment Handbook for further information about assessment rules and procedures.
• You must submit the task on Canvas prior to 8.30am on Wednesday and 9th April 2025

2
 Marking Criteria – 55 Total Marks
A B C D E
5 4 3 2 1-0
Introduction
EC-12-01, EC-12-02
Demonstrates extensive understanding of Demonstrates thorough Demonstrates sound Demonstrates basic
Demonstrates elementary
the enterprise system and problem being understanding of the system and its understanding of the system and understanding with some
understanding with minimal
solved. Clearly states the goals and the goals, with a clear explanation of the goals, with a basic explanation of reference to the system and
5 marks importance of addressing the issue. problem. the problem. goals.
explanation.
Problem Definition Defines the problem clearly and provides
Defines the problem well with a clear Defines the problem adequately, Provides a limited definition of Problem definition is unclear or
EC-12-03, EC-12-04 a comprehensive, well-illustrated diagram.
diagram. Provides good analysis of with a basic diagram. Provides the problem, with an unclear or missing, with little or no
Demonstrates perceptive analysis of the
the problem’s relevance. some explanation of relevance. incomplete diagram. diagram.
5 marks problem's relevance.
Research & 8 7-6 5-4 3-2 1-0
Planning Provides in-depth research, identifying key Provides thorough research with Provides basic research with
Provides sound research and Provides little or no research,
EC-12-08 findings (tools, resources, technologies) clear findings, outlining the planning minimal findings. Planning
identifies key findings. Mentions with an unclear or missing
with a well-organised planning strategy. strategy. Methodology is generally strategy is unclear or
planning strategy but lacks detail. planning strategy.
8 marks Clearly explains methodology. clear. incomplete.
Tools & 7 6-5 4-3 2 1-0
Methodologies Justifies the selection of tools and Justifies tool and methodology
Lists tools and methodologies with Lists tools with minimal
EC-12-08 methodologies with deep understanding of selection well, with some analysis of Lists tools with no or minimal
brief justification of their relevance justification of their relevance to
how they will support the development of how they support system justification of their relevance.
to the project. the project.
7 marks the system. development.
8 7-6 5-4 3-2 1-0
Provides a comprehensive overview of the Clear overview of system design, Adequate overview with some
System Design Limited overview with few details
system design, detailing components and explaining components and their explanations of components. Provides little to no overview or
EC-12-01, EC-12-02 on system components.
how they solve the problem. Includes relevance to the problem. Includes Includes one or more diagrams but relevant diagrams. Key
Diagrams may be unclear or
relevant diagrams and demonstrates at least one diagram and addresses may lack clarity or detail. Mentions components and features are
8 marks creative thinking on system features like key features such as user- key features like user-friendliness
missing. Key features are not
missing or unclear.
explained thoroughly.
user-friendliness and maintainability. friendliness and maintainability. and maintainability.
Development 7 6-5 4-3 2 1-0
Process Outlines a clear and well-organised Outlines the development process Provides an adequate outline of Provides a vague outline of the
EC-12-08 development process, including stages with most stages well defined. the development process with development process with Development process is
and how feedback and testing will be Discusses feedback and testing limited reference to feedback and minimal mention of feedback unclear or missing.
7 marks integrated. clearly. testing. and testing.
Impact on 5 4 3 2 1-0
Enterprise Provides an insightful discussion of how
Provides a thorough discussion of Provides an adequate discussion Provides a basic discussion of
EC-12-03 modern enterprise factors (remote work, Provides little or no discussion
how enterprise factors influence the of how enterprise factors influence enterprise factors with limited
offshore, freelance) influence the project’s of enterprise factors.
5 marks project’s relevance. the project, with limited analysis. insight into their relevance.
relevance and scalability.
Conclusion Summarises key points effectively,
Summarises key points clearly and Provides a basic summary of the Summary is unclear or
EC-12-02, EC-12-04 reaffirming the problem and impact. Provides a limited summary, with
discusses next steps with proposal, with some mention of missing, with no mention of
Discusses next steps with clear, feasible little discussion of next steps.
5 marks reasonable direction. next steps. next steps.
direction.
Adherence to
Fully adheres to the word limit, with clear, Generally, adheres to the word limit, Noticeable deviation from the Significant deviation from the
Word Limit Minor deviation from the word limit.
concise content across all sections. with only minimal deviation. word limit. word limit.
5 marks

3
Appendix
The following is extracted from the Enterprise Computing Course Specifications. You must ensure that you
use the format as shown in this appendix in the diagrams you include in your Project Proposal.

The following data flow diagram models a voting system.

4
5
6
7
8
9