Overview
This unit aims to teach you both theoretical and practical aspects of software engineering which involves specification, development, management and evolution of software systems. Theory will focus on software processes, requirements engineering, system models and modelling, robustness analysis, architectural design, object-oriented design, and software development methodology. The theoretical and practical aspects of software testing, software evolution, and quality management including quality assurance, and quality control are also discussed. You will also be introduced to the principles of software evolution and configuration management. This unit has a strong practical focus and the theoretical aspects are reinforced with practical work. The software engineering life cycle support functionality provided by modern software development environments is also addressed.
Details
Pre-requisites or Co-requisites
Pre-requisites: COIT20247 Database Design and Development, COIT20256 Data Structures and Algorithms, and COIT20248 Information Systems Analysis and Design Anti-requisites: COIT20226 Software Design and Implementation
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 - 2019
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 6-credit Postgraduate unit at CQUniversity requires an overall time commitment of an average of 12.5 hours of study per week, making a total of 150 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 feedback.
Agile development.
Emphasise in the assignment specifications that Agile development with two iterations is being used to develop an application. The two iterations correspond to Assignment 1 and Assignment 2.
- Apply the principles of software design
- Propose appropriate software management processes for a software engineering project
- Employ Unified Modeling Language (UML) and design patterns in the design and documentation of software systems
- Critique design alternatives and development methods available to a software developer
- Design, develop, and test non-distributed, three layered software applications
- Exploit the software engineering life cycle support functionality provided by modern software development environments.
Australian Computer Society (ACS) recognises the Skills Framework for the Information Age (SFIA). SFIA is in use in over 100 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 at https://www.acs.org.au/professionalrecognition/mysfia-b2c.html
This unit contributes to the following workplace skills as defined by SFIA:
- Systems Design (DESN)
- System Integration (SINT)
- Programming/Software Development (PROG)
- Data Analysis (DTAN)
- Database/Repository Design (DBDS)
- Testing (TEST)
- Applications Support (ASUP)
Alignment of Assessment Tasks to Learning Outcomes
Assessment Tasks | Learning Outcomes | |||||
---|---|---|---|---|---|---|
1 | 2 | 3 | 4 | 5 | 6 | |
1 - Practical Assessment - 20% | ||||||
2 - Practical Assessment - 30% | ||||||
3 - Examination - 50% |
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 |
Alignment of Assessment Tasks to Graduate Attributes
Assessment Tasks | Graduate Attributes | |||||||
---|---|---|---|---|---|---|---|---|
1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | |
1 - Practical Assessment - 20% | ||||||||
2 - Practical Assessment - 30% | ||||||||
3 - Examination - 50% |
Textbooks
Software Engineering
Edition: 10th. (2016)
Authors: Sommerville, I.
Pearson
Harlow Harlow , Essex , England
ISBN: 1-292-09613-6
Binding: Paperback
Additional Textbook Information
Paper copies can be purchased from the CQUni Bookshop here: http://bookshop.cqu.edu.au (search on the Unit code)
eBook copies can be purchased from the publisher here: http://www.pearson.com.au/9781292096148
IT Resources
- CQUniversity Student Email
- Internet
- Unit Website (Moodle)
- NetBeans IDE
All submissions for this unit must use the referencing style: Harvard (author-date)
For further information, see the Assessment Tasks.
d.jarvis@cqu.edu.au
Module/Topic
Introduction; NetBeans
Chapter
Chapter 1; Online Material
Events and Submissions/Topic
Module/Topic
Software Processes; Case Study 1 - AddressBook: Model/View (MV)
Chapter
Chapter 2; Online Material
Events and Submissions/Topic
Module/Topic
Agile Software Development; Case Study 1 - AddressBook: Model/View/Presenter (MVP)
Chapter
Chapter 3; Online Material
Events and Submissions/Topic
Module/Topic
Requirements Engineering; System Modelling
Chapter
Chapter 4, Chapter 5
Events and Submissions/Topic
Module/Topic
Requirements Analysis; Unit testing
Chapter
Online Material; Online material
Events and Submissions/Topic
Module/Topic
Chapter
Events and Submissions/Topic
Module/Topic
Architectural Design; GUI, DB Design
Chapter
Chapter 6; Online Material
Events and Submissions/Topic
Module/Topic
Design and Implementation; Design Documents
Chapter
Chapter 7; Online Material
Events and Submissions/Topic
Module/Topic
Design Principles; Case Study 1 - AddressBook: Model/View/Controller (MVC)
Chapter
Online Material; Online Material
Events and Submissions/Topic
Module/Topic
Software Testing; Case Study 1 - AddressBook: Critique
Chapter
Chapter 8; Online Material
Events and Submissions/Topic
Module/Topic
Software Evolution; Case Study 2 - Wumpus game: Specification
Chapter
Chapter 9; Online Material
Events and Submissions/Topic
Module/Topic
Quality Management; Case Study 2 - Wumpus game: Design
Chapter
Chapter 24; Online Material
Events and Submissions/Topic
Module/Topic
Configuration Management; Review
Chapter
Chapter 25; Online Material
Events and Submissions/Topic
Module/Topic
Chapter
Events and Submissions/Topic
Module/Topic
Chapter
Events and Submissions/Topic
1 Practical Assessment
Students will implement a Java application that conforms to the MVP (Model View Presenter) pattern. The view will contain a Swing based GUI and the model will interact with a Java DB database. The specification of the system to be built (including the design document) will be provided on the unit web site.
Week 6 Friday (26 Apr 2019) 11:45 pm AEST
Two weeks after submission
Criteria | Marks Available |
Application class | 1 |
Model + interface classes | 4 |
View + interface classes | 3 |
Presenter class | 3 |
Layer interactions (Application/MVP, V/P, P/M, M/database) | 4 |
Source code documentation / variable naming / code layout | 2 |
Package structure | 1 |
Acceptance tests (0 if any test fails) | 2 |
Total | 20 |
- Employ Unified Modeling Language (UML) and design patterns in the design and documentation of software systems
- Design, develop, and test non-distributed, three layered software applications
- Exploit the software engineering life cycle support functionality provided by modern software development environments.
- Knowledge
- Communication
- Cognitive, technical and creative skills
- Self-management
- Ethical and Professional Responsibility
2 Practical Assessment
Students will implement a revised specification for Assignment 1. New requirements will include conformance to the MVC (Model View Controller) pattern. The specification of the system to be built (including the design document) will be provided on the unit web site.
Week 10 Friday (24 May 2019) 11:45 pm AEST
Two weeks after submission
Criteria | Marks Available |
Application class | 2 |
Model + interface classes | 6 |
View + interface classes | 4 |
Controller class | 2 |
Layer interactions (Application/MVC, V/C, C/M, M/V, M/database) | 8 |
Source code documentation / variable naming / code layout | 3 |
Package structure | 1 |
Acceptance tests (0 if any test fails) | 4 |
Total | 30 |
- Apply the principles of software design
- Employ Unified Modeling Language (UML) and design patterns in the design and documentation of software systems
- Design, develop, and test non-distributed, three layered software applications
- Exploit the software engineering life cycle support functionality provided by modern software development environments.
- Knowledge
- Communication
- Cognitive, technical and creative skills
- Self-management
- Ethical and Professional Responsibility
Examination
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.