Overview
This unit is the capstone project for the application development major of the Bachelor of Information Technology (BIT) course. You are required to synthesise and apply your 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 a problem and develop a software application application adhering to software engineering principles and standards. You will document and present the requirement analysis, design artifacts, and the results from software testing. In addition to the documented application, your team will also identify and produce the project management and quality assurance components required to ensure that the project is delivered within specified project outcome parameters. You will also evaluate and discuss your contribution to the project team and the overall team performance.
Details
Pre-requisites or Co-requisites
Pre-requisite: COIT12200, (COIT12207 or COIT13224) and (COIT12208 or COIS13064) Co-requisite: COIT13229 and COIT13234
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 1 - 2022
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 Undergraduate 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 Student Evaluations
Students enjoyed having real world projects and meeting real clients.
Continue to provide real-world projects.
Feedback from Student Evaluations
Students wanted a cross-campus, mid-term presentation so students could compare themselves with all other groups.
Consider cross-campus presentations during and at the end of term.
Feedback from Student Evaluations
Students want more involvement with the real-world clients.
Add more meetings with clients.
Feedback from Student Evaluations
Students want more conflict resolution support.
Include a review of conflict resolution strategies.
Feedback from Unit Coordinator Reflection
There are not enough student project examples.
Add more student project examples.
- Apply software engineering processes, including requirement analysis, application software design, algorithm design, coding and debugging, software testing, and software project management.
- Manage a software development project, particularly the scheduling of time and resources, development of risk mitigation strategies, and the generation of supporting documentation
- Develop and implement a quality management plan for a small software development project adhering to ethical responsibility
- Communicate effectively by using written and oral presentation, understanding the needs of various stakeholders
- Work effectively as part of a development team
- Review and critically evaluate team and individual performance to reflect on the processes followed and identify areas for improvement.
- Requirements definition and management (REQM)
- Programming/software development (PROG)
- Software Design (SWDN)
- Data modelling and design (DTAN)
- User experience evaluation (HSEV)
- Database design (DBDS)
- Systems integration and build (SINT)
- Testing (TEST)
- Configuration management (CFMG)
- Application support (ASUP)
- System installation and removal (HSIN)
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 - Communication | ||||||
| 2 - Problem Solving | ||||||
| 3 - Critical Thinking | ||||||
| 4 - Information Literacy | ||||||
| 5 - Team Work | ||||||
| 6 - Information Technology Competence | ||||||
| 7 - Cross Cultural Competence | ||||||
| 8 - Ethical practice | ||||||
| 9 - Social Innovation | ||||||
| 10 - Aboriginal and Torres Strait Islander Cultures | ||||||
Textbooks
There are no required textbooks.
IT Resources
- CQUniversity Student Email
- Internet
- Unit Website (Moodle)
- JDK 11 - OpenJDK
- Apache NetBeans IDE 12.4 (available from https://netbeans.apache.org/download/nb124/nb124.html)
- Scene Builder 12 or later available from https://gluonhq.com/products/scene-builder/
- 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/)
- Apache TomEE 8.0.0 TomEE Plus (available from https://tomee.apache.org/download.html)
- Jakarta EE 8 (available from https://jakarta.ee/release/8/)
All submissions for this unit must use the referencing styles below:
For further information, see the Assessment Tasks.
m.tom@cqu.edu.au
Module/Topic
Project Management and Project Planning
Chapter
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
Module/Topic
Requirements Engineering and Quality Management
Chapter
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 and Agile Development
Events and Submissions/Topic
Read the recommended sections of the reference Textbook and apply the principles in your project plan.
Module/Topic
System Modeling
Chapter
Chapter 5
5.2 Interaction models
Events and Submissions/Topic
Module/Topic
Requirements Engineering and Architectural Design
Chapter
Chapter 4
4.1 Functional and Non-Functional Requirements
4.4 Requirements Specification
Chapter 6
6.3 Architectural Patterns
Events and Submissions/Topic
Module/Topic
Object-Oriented Design and Testing
Chapter
Chapter 7
7.1 Object-Oriented design using the UML
Chapter 8
8.2 Test-driven development
Events and Submissions/Topic
Project Progress Report 1 Due: Friday (8 April 2022) 11.45 pm AEST
Module/Topic
Chapter
Events and Submissions/Topic
Module/Topic
Chapter
Events and Submissions/Topic
Module/Topic
System Implementation
Chapter
Chapter 7
7.3 Implementation Issues
Events and Submissions/Topic
Project Progress Report 2 Due: Friday (29 April 2022) 11.45 pm AEST
Project Requirements Specification and Design Due: Week 7 Tuesday (26 Apr 2022) 11:45 pm AEST
Module/Topic
System Implementation
Chapter
Events and Submissions/Topic
Module/Topic
Configuration management
Chapter
Chapter 24
24.3 Reviews and Inspections
Chapter 25
25.2 System Building
Events and Submissions/Topic
Project Progress Report 3 Due: Friday (13 May 2022) 11.45 pm AEST
Module/Topic
Software Testing
Chapter
Chapter 8
8.3 Release Testing
8.4 User Testing
Events and Submissions/Topic
Module/Topic
Chapter
Events and Submissions/Topic
Project Progress Report 4 Due: Friday (27 May 2022) 11.45 pm AEST
Module/Topic
Chapter
Events and Submissions/Topic
Module/Topic
Project Presentation
Chapter
Events and Submissions/Topic
Module/Topic
Chapter
Events and Submissions/Topic
Unit Coordinator
Dr Mary Tom
College of Information and Communications Technology
School of Engineering and Technology
Central Queensland University
Brisbane QLD 4000, Australia
Phone: +61 7 3295 1119
Email: m.tom@cqu.edu.au
1 Written Assessment
This is a group assessment. In this assessment, you should clearly define the scope of the project you will be undertaking as a team. You should create a context diagram illustrating the main components of your proposed software application. You should include the following sections in your written submission.
- A Use case diagram showing the main use cases of the software application to be developed.
- User Requirements.
- A preliminary project schedule showing the main tasks, completion times, and mile stones, and team members responsible for the tasks.
- Risk management plan
- Quality Assurance plan
Further details and guidelines to complete this task will be provided in Moodle Unit website.
Week 3 Friday (25 Mar 2022) 11:45 pm AEST
Week 5 Thursday (7 Apr 2022)
- Clear concise and feasible scope of project
- Clear identification of System components and interaction
- Correct identification of Use cases
- Feasible project schedule with tasks, time, and responsible team member
- Correct identification of software tools to be used in the project development
- Clear identification of risks and risk mitigation strategy
- Appropriate selection of quality standards and software engineering ethical guidelines
- Manage a software development project, particularly the scheduling of time and resources, development of risk mitigation strategies, and the generation of supporting documentation
2 Written Assessment
This is an individual assessment. Each team member is required to submit four Periodic Project Progress Reports (2A, 2B, 2C, and 2D). The progress reports 2A, and 2B weigh 2 marks each and the other two progress reports 2C, and 2D weigh 3 marks each (totaling 10 marks for all project progress reports). All four reports must be written using the standard template file provided in the Moodle Unit website. The detailed specification of this assessment will be provided in the Moodle Unit website. The submission due dates for all 4 progress reports are as below:
| Project Progress Report 1 (Assessment 2A) | Friday of Week 5 (11:45 pm AEST) |
| Project Progress Report 2 (Assessment 2B) | Friday of Week 7 (11:45 pm AEST) |
| Project Progress Report 3 (Assessment 2C) | Friday of Week 9 (11:45 pm AEST ) |
| Project Progress Report 4 (Assessment 2D) | Friday of Week 11 (11:45 pm AEST ) |
Marked reports will be returned one week after submission.
The assessment specification and marking criteria will be provided in the Moodle Unit website.
- Work effectively as part of a development team
3 Written Assessment
This Assessment contains group and individual components. Group task is to prepare the written document containing software requirements specification and design. Individual component is an in-class presentation of the written document. The written document should include:
- Functional and non-functional requirements
- Use-case diagrams
- Use case scenarios
- Software architecture
- Subsystem models and sequence models
- Entity Relationship Diagrams
- User interface Designs
- Mapping of Requirements to use-cases
Each team member should prepare and submit presentation slides using Microsoft PowerPoint or other presentation software. This should also be presented in-class. Refer to the Assessment 3 specification available from the Moodle Unit website for further details.
Week 7 Tuesday (26 Apr 2022) 11:45 pm AEST
In-class presentations will take place in Week 7 and this will be organised by the local lecturer or tutor.
Week 9 Monday (9 May 2022)
- Clear identification of use cases that align with the defined scope of the project
- Correct identification of functional requirements following the use cases
- Appropriately chosen quality standards suitable for the application domain
- Correct and clear identification of non-functional requirements that can comply with the quality standards
- Correctly illustrated software architecture showing main components
- Clearly written use-case scenarios
- Correct sequence diagrams illustrating the important sequences of operation
Refer to the Assessment 3 specification and marking criteria available from the Moodle Unit website.
- Apply software engineering processes, including requirement analysis, application software design, algorithm design, coding and debugging, software testing, and software project management.
- Develop and implement a quality management plan for a small software development project adhering to ethical responsibility
- Communicate effectively by using written and oral presentation, understanding the needs of various stakeholders
4 Project (applied)
This assessment has two components -the final software application and written report. One member of each group must submit the completed software application source code files and binary file(s) (.jar or .war) for the fully executable software application. All team members should submit the final report which is a document file (.doc or .docx). The project final report should contain the revised project scope, requirements specification, design, test plan, evidence of testing, user manual, and teamwork details. This report should be prepared following the given template and should include all the details as required in the Assessment 4 Specification available from the Moodle Unit website.
Week 12 Friday (3 June 2022) 11:45 pm AEST
The marking sheet with comments will be returned after the certification of grades.
- Completely developed software application as per the defined scope and any changes
- Correct functioning of the developed application as per the functional requirements and use cases
- User interface adhering to the designed User Interface Design Principles
- Adherence to planned quality standards
Further details are available in the Assessment 4 specification and marking criteria available from the Moodle Unit website.
- Apply software engineering processes, including requirement analysis, application software design, algorithm design, coding and debugging, software testing, and software project management.
- Manage a software development project, particularly the scheduling of time and resources, development of risk mitigation strategies, and the generation of supporting documentation
- Develop and implement a quality management plan for a small software development project adhering to ethical responsibility
- Work effectively as part of a development team
- Review and critically evaluate team and individual performance to reflect on the processes followed and identify areas for improvement.
5 Presentation
This is an individual assessment. You should do an oral presentation of one part of your project to an audience including the cohort of students and staff in this unit, industry representatives, and students and staff from the School of Engineering and Technology. Each of you should prepare formal presentation slides such a way that the presentations by all group members should provide the complete project presentation to the audience.
Review/Exam Week Monday (6 June 2022) 11:45 pm AEST
The exact time of presentation will be informed nearing to the date. You should make yourself available for the whole day.
You should consider the following aspects for your presentation.
- Clearly written formal presentation slides
- Clear expression of ideas
- Convincing arguments
- Consideration of technical and non-technical audience in usage of terms.
Further guidelines and marking criteria are available from Project Presentation Specification available from the 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?
