Overview
In this integrative capstone project, you are required to synthesise and demonstrate your technical and generic skills developed across the units studied previously. This unit will help you to consolidate your competence with a relevant set of software engineering concepts, practices, and tools. To achieve this, you will work in small teams with a designated customer to identify an authentic problem, document and present the design process, and the results from a developed software solution to the identified problem. In addition to the documented application, your team will also identify and produce the project management, quality assurance, and cyber security components required to ensure that the project is delivered within specified project outcome parameters. You will also evaluate and discuss your contribution to the teamwork and the overall team performance.
Details
Pre-requisites or Co-requisites
Pre-requisites: PPMP20007 Project Management Concepts COIT20246 Networking and Cyber Security COIT20257 Distributed Systems: Principles and Development COIT20258 Software Engineering COIT20259 Enterprise Computing Architecture
Important note: Students enrolled in a subsequent unit who failed their pre-requisite unit, should drop the subsequent unit before the census date or within 10 working days of Fail grade notification. Students who do not drop the unit in this timeframe cannot later drop the unit without academic and financial liability. See details in the Assessment Policy and Procedure (Higher Education Coursework).
Offerings For Term 3 - 2024
Attendance Requirements
All on-campus students are expected to attend scheduled classes - in some units, these classes are identified as a mandatory (pass/fail) component and attendance is compulsory. International students, on a student visa, must maintain a full time study load and meet both attendance and academic progress requirements in each study period (satisfactory attendance for International students is defined as maintaining at least an 80% attendance record).
Recommended Student Time Commitment
Each 12-credit Postgraduate unit at CQUniversity requires an overall time commitment of an average of 25 hours of study per week, making a total of 300 hours for the unit.
Class Timetable
Assessment Overview
Assessment Grading
This is a graded unit: your overall grade will be calculated from the marks or grades for each assessment task, based on the relative weightings shown in the table above. You must obtain an overall mark for the unit of at least 50%, or an overall grade of 'pass' in order to pass the unit. If any 'pass/fail' tasks are shown in the table above they must also be completed successfully ('pass' grade). You must also meet any minimum mark requirements specified for a particular assessment task, as detailed in the 'assessment task' section (note that in some instances, the minimum mark for a task may be greater than 50%). Consult the University's Grades and Results Policy for more details of interim results and final grades.
All University policies are available on the CQUniversity Policy site.
You may wish to view these policies:
- Grades and Results Policy
- Assessment Policy and Procedure (Higher Education Coursework)
- Review of Grade Procedure
- Student Academic Integrity Policy and Procedure
- Monitoring Academic Progress (MAP) Policy and Procedure - Domestic Students
- Monitoring Academic Progress (MAP) Policy and Procedure - International Students
- Student Refund and Credit Balance Policy and Procedure
- Student Feedback - Compliments and Complaints Policy and Procedure
- Information and Communications Technology Acceptable Use Policy and Procedure
This list is not an exhaustive list of all University policies. The full list of University policies are available on the CQUniversity Policy site.
Feedback, Recommendations and Responses
Every unit is reviewed for enhancement each year. At the most recent review, the following staff and student feedback items were identified and recommendations were made.
Feedback from Unit Evaluation Data
The response rate for the evaluation survey was below the expected level.
Educate students about the importance of unit evaluation and encourage them to complete the survey.
- Apply a systems engineering process in the context of enterprise application development, including requirement analysis, application software design, algorithm design, coding and debugging, software testing, and software project management, informed by research into best practice
- Demonstrate professional standards of software development, including technical skills, documentation, software quality assurance, cyber security best practices, risk mitigation strategies, ethics and professional responsibility
- Plan and manage the software development project, particularly the scheduling of time and resources and the generation of supporting documentation
- Work collaboratively as part of a productive team
- Communicate effectively by using written and oral presentation, understanding the needs of various stakeholders
- Critically review individual and team performance, along with identifying areas for improvement.
The Australian Computer Society (ACS), the professional association for Australia's ICT sector, recognises the Skills Framework for the Information Age (SFIA). SFIA is adopted by organisations, governments, and individuals in many countries and provides a widely used and consistent definition of ICT skills. SFIA is increasingly being used when developing job descriptions and role profiles. ACS members can use the tool MySFIA to build a skills profile.
This unit contributes to the following workplace skills as defined by SFIA 8 (the SFIA code is included):
- Requirements definition and management (REQM)
- Programming/software development (PROG)
- Software design (SWDN)
- Database design (DBDS)
- Data modelling and design (DTAN)
- Systems integration and build (SINT)
- Configuration management (CFMG)
- Testing (TEST)
- Research (RSCH)
- User experience evaluation (USEV)
- Application support (ASUP)
- System installation and removal (HSIN)
- Systems and software life cycle engineering (SLEN)
- Information security (SCTY)
Alignment of Assessment Tasks to Learning Outcomes
| Assessment Tasks | Learning Outcomes | |||||
|---|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | 5 | 6 | |
| 1 - Written Assessment - 15% | ||||||
| 2 - Written Assessment - 10% | ||||||
| 3 - Written Assessment - 25% | ||||||
| 4 - Project (applied) - 40% | ||||||
| 5 - Presentation - 10% | ||||||
Alignment of Graduate Attributes to Learning Outcomes
| Graduate Attributes | Learning Outcomes | |||||
|---|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | 5 | 6 | |
| 1 - Knowledge | ||||||
| 2 - Communication | ||||||
| 3 - Cognitive, technical and creative skills | ||||||
| 4 - Research | ||||||
| 5 - Self-management | ||||||
| 6 - Ethical and Professional Responsibility | ||||||
| 7 - Leadership | ||||||
| 8 - Aboriginal and Torres Strait Islander Cultures | ||||||
Textbooks
There are no required textbooks.
IT Resources
- CQUniversity Student Email
- Internet
- Unit Website (Moodle)
- Zoom (both microphone and webcam capability)
- MySQL Community Server 8.0.26 (available from https://dev.mysql.com/downloads/mysql/)
- JavaFX 11.0.12 (available from https://gluonhq.com/products/javafx/)
- NetBeans 20 (available from: https://netbeans.apache.org/front/main/download/nb20/)
- Open JDK 21 (available from: https://jdk.java.net/21/)
- Scene Builder 21 (available from: https://gluonhq.com/products/scene-builder/)
- Jakarta EE 10 (available from https://jakarta.ee/release/10/)
All submissions for this unit must use the referencing style: Harvard (author-date)
For further information, see the Assessment Tasks.
p.poon@cqu.edu.au
Module/Topic
Project Management & Project Planning
Chapter
Reference book: Software Engineering by Ian Sommerville
Chapter 1
Section 1.2 Software Engineering Ethics
Chapter 22
22.1 Risk Management
22.3 Teamwork
Chapter 23
23.2 Plan-driven development
23.3 Project Scheduling
Events and Submissions/Topic
- Form project group, identify & discuss project topic
Module/Topic
Requirements Engineering & Quality Management
Chapter
Reference book: Software Engineering by Ian Sommerville
Chapter 23
23.4 Agile Planning
Chapter 4
4.1 Requirements elicitation
Chapter 5
5.1 Context Models
Chapter 24
24.2 Software Standards
24.4 Quality Management & Agile Development
Events and Submissions/Topic
- Finalize project topic & scope
- Work on project proposal
Module/Topic
System Modeling
Chapter
Reference book: Software Engineering by Ian Sommerville
Chapter 5
5.2 Interaction models
Events and Submissions/Topic
- Finalize project proposal
- Submit project proposal
Project Proposal Due: Week 3 Friday (22 Nov 2024) 11:55 pm AEST
Module/Topic
Requirements Engineering & Architectural Design
Chapter
Reference book: Software Engineering by Ian Sommerville
Chapter 4
4.1 Functional & Non-Functional Requirements
4.4 Requirements Speciifcation
Chapter 6
6.3 Architectural Patterns
Events and Submissions/Topic
- detailed user stories
- user interfaces
- data structures
- database schema
- software architecture
- platforms/tools/frameworks
- test plan
- project tracking tool
Module/Topic
Object-Oriented Design & Testing
Chapter
Reference book: Software Engineering by Ian Sommerville
Chapter 7
7.1 Object-Oriented design using the UML
Chapter 8
8.2 Test-driven development
Events and Submissions/Topic
- Start developing prototype
- Submit Progress Report 1
Progress Report 1 Due: Week 5 Friday (6 Dec 2024) 11:55 pm AEST
Module/Topic
Chapter
Events and Submissions/Topic
- Keep working on prototype
- Track progress
- Update GitHub repository
Module/Topic
System Implementation
Chapter
Reference book: Software Engineering by Ian Sommerville
Chapter 7
7.3 Implementation Issues
Events and Submissions/Topic
- Start developing in-class presentation
- Submit Progress Report 2
Progress Report 2 Due: Week 7 Friday (20 Dec 2024) 11:55 pm AEST
Module/Topic
Chapter
Events and Submissions/Topic
Module/Topic
Chapter
Events and Submissions/Topic
Module/Topic
System Implementation
Chapter
Events and Submissions/Topic
- Keep working on in-class presentation
- Keep working on prototype
- Track progress
- Update GitHub repository
Module/Topic
Configuration management
Chapter
Reference book: Software Engineering by Ian Sommerville
Chapter 24
24.3 Reviews & Inspections
Chapter 25
25.1 Version Management
25.2 System Building
Events and Submissions/Topic
- Keep working on in-class presentation
- Keep working on prototype
- Track progress
- Update GitHub repository
Module/Topic
Software Testing
Chapter
Reference book: Software Engineering by Ian Sommerville
Chapter 8
8.3 Release Testing
8.4 User Testing
Events and Submissions/Topic
- Deliver in-class presentation
- Start writing report
- Keep working on a prototype
- Track progress
- Update GitHub repository
Module/Topic
Chapter
Events and Submissions/Topic
- Keep working on report
- Keep working on prototype
- Test prototype
- Track progress
- Update GitHub repository
In-Class Project Demonstration & Report
Due: Week 11 Friday (31 Jan 2025) 11:55 pm AEST
Module/Topic
Chapter
Events and Submissions/Topic
- Submit report
- Complete software development
- Complete user acceptance test
- Complete final presentation development & practice
Module/Topic
Final Project Presentation
Chapter
Events and Submissions/Topic
Deliver a public presentation
Public Presentation & Demonstration of Final Project Outcomes
Due: Review/Exam Week Monday (10 Feb 2025) 9:00 am AEST
Unit Coordinator: Associate Professor Pak Poon
Email: p.poon@cqu.edu.au
1 Written Assessment
This is a group assessment. In this assessment, you are required to develop a project proposal for developing a complex real-world application. You should develop an original or semi-original idea for the application, which should be feasible and have business value.
The project proposal should be written into a document including the following 5 components or sections:
= Project background
= Project objectives
= High-level user requirements
= Hardware & software requirements
= Risk management & quality assurance plan
The detailed specification of this assessment will be provided on the Moodle unit website.
Week 3 Friday (22 Nov 2024) 11:55 pm AEST
Late submissions are subject to the university's late submission penalty policies.
Week 5 Friday (6 Dec 2024)
The feedback will be returned within two weeks of the submission due date.
The assessment criteria will be provided on the Moodle unit website.
- Plan and manage the software development project, particularly the scheduling of time and resources and the generation of supporting documentation
2 Written Assessment
This is a group assessment, however, individuals may receive different scores based on their contributions.
In this assessment, you are required to report progress on the following 8 items:
= Detailed user stories
= Wireframes of all user interfaces
= Major data structures
= Database schema
= Software architecture illustrating all components
= Platforms/languages/tools/frameworks
= Test plan (should include user acceptance test)
= Project tracking tool
The detailed specification of this assessment will be provided on the Moodle unit website.
Week 5 Friday (6 Dec 2024) 11:55 pm AEST
Late submissions are subject to the university's late submission penalty policies.
Week 7 Friday (20 Dec 2024)
The feedback will be returned within two weeks of the submission due date.
The assessment criteria will be provided on the Moodle unit website.
- Plan and manage the software development project, particularly the scheduling of time and resources and the generation of supporting documentation
- Work collaboratively as part of a productive team
3 Written Assessment
This is a group assessment, however, individuals may receive different scores based on their contributions. For this assessment, you will demonstrate the current prototype of your enterprise application in the class as well as submit an updated report on the progress.
In the demonstration, you will run the current prototype of your enterprise application in a lab computer/your personal computer/your mobile device to demonstrate the user stories/interfaces/features/business logic that have been fully or partially implemented during the current progress period. You are also required to show evidence of tracking the progress of your project using a project-tracking tool (e.g., Jira).
In the update report, you will provide a brief update on the following 6 items for the current progress period:
- User stories/interfaces/features/business logic implemented (provide screenshots of your outputs)
- Implementation details of the various components of the prototype (provide screenshots of your code)
- Test results for the implemented user stories/interfaces/features/business logic (provide screenshots & annotations)
- Errors/problems with the implemented user stories/interfaces/features/business logic (provide screenshots, if possible).
- User stories or other features introduced (if any)
- User stories or other features dropped or modified (if any)
A copy of the prototype source code must be maintained in a GitHub repository & the link to the repository must be included in the report. The repository must contain the history of all changes in the source code.
The detailed specifications of this assessment will be provided on the Moodle unit website.
Week 7 Friday (20 Dec 2024) 11:55 pm AEST
Late submissions are subject to the university's late submission penalty policies.
Week 9 Friday (17 Jan 2025)
The feedback will be returned within two weeks of the submission due date.
The assessment criteria will be provided on the Moodle unit website.
- Apply a systems engineering process in the context of enterprise application development, including requirement analysis, application software design, algorithm design, coding and debugging, software testing, and software project management, informed by research into best practice
- Demonstrate professional standards of software development, including technical skills, documentation, software quality assurance, cyber security best practices, risk mitigation strategies, ethics and professional responsibility
- Communicate effectively by using written and oral presentation, understanding the needs of various stakeholders
4 Project (applied)
This is a group assessment, however, individuals may receive different scores based on their contributions. This assessment has two components - Part 1: In-class Presentation & Demonstration, and Part 2: Final Report. Parts 1 & 2 submissions are due in Week 10 and Week 12 respectively.
Part 1: In-class Presentation & Demonstration (20 marks)
In this part, you are required to present all aspects of your enterprise application including the project background, objective, user stories, major data structures, database design, software architecture, sequence diagrams, platforms/tools/frameworks, test results (including user acceptance test), & lessons learnt. You will also run the current prototype of your enterprise application in a lab computer/your personal computer/your mobile device to demonstrate the user stories/interfaces/features/business logic that have been fully or partially implemented during the current progress period. You are also required to show evidence of tracking the progress of your project using a project tracking tool (e.g., Jira).
For this part, you must submit a presentation file to Moodle by the end of Week 10.
Part 2: Final Report (20 marks)
In this part, you are required to develop a final report containing a final project summary, user stories, major data structures, database design, software architecture, sequence diagram, platforms/tools/frameworks, test results (including user acceptance test), user manual & a project reflection.
A copy of the prototype source code must be maintained in a GitHub repository and the link to the repository must be included in the report.
For this part, you must submit the report as well a copy of the final source code to Moodle by the end of Week 12.
The detailed specification of this assessment will be provided on the Moodle unit website.
Note: This assessment task is selected to be included in your course-wide portfolio. The outcomes/artifacts of this assessment must be uploaded to Portfolium (https://portfolium.com/activity) by the submission due dates in addition to your submission to Moodle for marking.
Part 1 presentation must be submitted by Week 10 Friday 11:55 pm AEST. Part 2 report & source code must be submitted by Week 12 Friday 11:55 pm AEST.
The feedback will be returned within two weeks of the corresponding submission due dates.
The assessment criteria will be provided on the Moodle unit website.
- Apply a systems engineering process in the context of enterprise application development, including requirement analysis, application software design, algorithm design, coding and debugging, software testing, and software project management, informed by research into best practice
- Demonstrate professional standards of software development, including technical skills, documentation, software quality assurance, cyber security best practices, risk mitigation strategies, ethics and professional responsibility
- Work collaboratively as part of a productive team
- Critically review individual and team performance, along with identifying areas for improvement.
5 Presentation
This is a group assessment. In this assessment, each group is required to present their final project outcomes in a public presentation. Each member of a group MUST take part in the presentation. In general, all team members will receive the same mark in this assessment. However, if performance varies significantly across team members, individual marks can be awarded.
The presentation will cover:
- Demonstration of a fully-working enterprise application
- Presentation of the final project outcomes
Each group will have 15-20 minutes to present the above items to the plenary.
With (1) above, it is advised that each group must install their enterprise application on their personal computer/mobile device prior to the delivery of the presentation. The mobile app must be demonstrated during the presentation.
With (2) above, each group must also present all aspects of their enterprise application development project covering the project background, objectives, user stories, major data structures, database design, software architecture, sequence diagram, platforms/tools/frameworks, test results (including user acceptance test), & lessons learnt.
The final presentation session will be held on Monday Review/Exam Week. The presentation session will be a conference-style event, running up to 1 day. Groups will be assigned to present at time slots during the day, & also be required to view presentations of other groups. You will have to make yourself available for the whole day on the day of presentation. The Head of Course or Unit Coordinator will schedule the time of presentation.
The detailed specification of this assessment will be provided on the Moodle unit website.
Note: This assessment task is selected to be included in your course-wide portfolio. The outcomes/artifacts of this assessment must be uploaded to Portfolium (https://portfolium.com/activity) by the submission due date in addition to your submission to Moodle for marking.
Review/Exam Week Monday (10 Feb 2025) 9:00 am AEST
The feedback will be returned on the day of certification of grades.
The assessment criteria will be provided on the Moodle unit website.
- Communicate effectively by using written and oral presentation, understanding the needs of various stakeholders
As a CQUniversity student you are expected to act honestly in all aspects of your academic work.
Any assessable work undertaken or submitted for review or assessment must be your own work. Assessable work is any type of work you do to meet the assessment requirements in the unit, including draft work submitted for review and feedback and final work to be assessed.
When you use the ideas, words or data of others in your assessment, you must thoroughly and clearly acknowledge the source of this information by using the correct referencing style for your unit. Using others’ work without proper acknowledgement may be considered a form of intellectual dishonesty.
Participating honestly, respectfully, responsibly, and fairly in your university study ensures the CQUniversity qualification you earn will be valued as a true indication of your individual academic achievement and will continue to receive the respect and recognition it deserves.
As a student, you are responsible for reading and following CQUniversity’s policies, including the Student Academic Integrity Policy and Procedure. This policy sets out CQUniversity’s expectations of you to act with integrity, examples of academic integrity breaches to avoid, the processes used to address alleged breaches of academic integrity, and potential penalties.
What is a breach of academic integrity?
A breach of academic integrity includes but is not limited to plagiarism, self-plagiarism, collusion, cheating, contract cheating, and academic misconduct. The Student Academic Integrity Policy and Procedure defines what these terms mean and gives examples.
Why is academic integrity important?
A breach of academic integrity may result in one or more penalties, including suspension or even expulsion from the University. It can also have negative implications for student visas and future enrolment at CQUniversity or elsewhere. Students who engage in contract cheating also risk being blackmailed by contract cheating services.
Where can I get assistance?
For academic advice and guidance, the Academic Learning Centre (ALC) can support you in becoming confident in completing assessments with integrity and of high standard.
What can you do to act with integrity?
