This unit develops students understanding of and skills in professional software engineering practices at the personal level. Students experience work in a team environment and extend their programming skills by learning a new object oriented language and maintaining a system that is larger than their experience in prior units. Students develop skills in estimating, monitoring, reviewing and reporting on practical projects.
Minimum total expected workload equals 12 hours per week comprising:
(a.) Contact hours for on-campus students:
(b.) Additional requirements (all students):
See also Unit timetable information
CSE2201, GCO3811, FIT3037
FIT1007 or FIT1008 or FIT1015 or CSE1303 or CSE1203 or BUS2011 or FIT2034
David Squire
Robyn Mcnamara
Andre Oboler
Andreas Limberopoulos
Hongli Song
Monash is committed to excellence in education and regularly seeks feedback from students, employers and staff. One of the key formal ways students have to provide feedback is through the Student Evaluation of Teaching and Units (SETU) survey. The University’s student evaluation policy requires that every unit is evaluated each year. Students are strongly encouraged to complete the surveys. The feedback is anonymous and provides the Faculty with evidence of aspects that students are satisfied and areas for improvement.
For more information on Monash’s educational strategy, see:
www.monash.edu.au/about/monash-directions/ and on student evaluations, see: www.policy.monash.edu/policy-bank/academic/education/quality/student-evaluation-policy.html
Based on student feedback:
A hand-out will be produced to support the code-along lectures in weeks 1 and 2.
If you wish to view how previous students rated this unit, please go to
https://emuapps.monash.edu.au/unitevaluations/index.jsp
| Week | Activities | Assessment |
|---|---|---|
| 0 | No formal assessment or activities are undertaken in week 0 | |
| 1 | Unit Overview; Fundamentals of Object Orientation 1 | |
| 2 | Fundamentals of Object Orientation 2 | Tutorials commence |
| 3 | SE Process, PSP; Design By Contract | Assessment Task 1 - Exercise 1 due in tutorial |
| 4 | Specification; Configuration Management | Assessment Task 1 - Exercise 2 due in tutorial |
| 5 | Project & Quality Management; Testing; | Assessment Task 1 - Exercise 3 due in tutorial; Hand out Assignment |
| 6 | Writing Test Plans and Test Reports | Assessment Task 1 - Exercise 4 due in tutorial and PIP due |
| 7 | Software Metrics | Team Project - Stage 1-Planning and development due Friday |
| 8 | Software Maintenance; Software Design | Team Project - Stage 1-Implementation and Testing due Friday |
| 9 | SQA & Reviews (PSP2) | |
| 10 | Software Reuse | Team Project - Stage 2-Planning and development due Friday |
| 11 | Software Performance | |
| 12 | SE Tools | Team Project - Stage 2 - Implementation and Testing due Monday |
| SWOT VAC | No formal assessment is undertaken in SWOT VAC | |
| Examination period | LINK to Assessment Policy: http://policy.monash.edu.au/policy-bank/ academic/education/assessment/ assessment-in-coursework-policy.html |
*Unit Schedule details will be maintained and communicated to you via your learning system.
Examination (2 hours): 40%; In-semester assessment: 60%
| Assessment Task | Value | Due Date |
|---|---|---|
| Individual Exercises | 10% | Weeks 3, 4, 5 and 6 during tutorial |
| Team Project | 10 + 10 + 15 + 15 = 50% | Stage 1 - P & D - Friday, week 7: Stage 1 - I & T - Friday, week 8: Stage 2 - P & D - Friday, week 10: Stage 2 - I & T - Monday, week 12: |
| Examination 1 | 40% | To be advised |
Faculty Policy - Unit Assessment Hurdles (http://intranet.monash.edu.au/infotech/resources/staff/edgov/policies/assessment-examinations/assessment-hurdles.html)
Academic Integrity - Please see resources and tutorials at http://www.monash.edu/library/skills/resources/tutorials/academic-integrity/
Each program will be assessed for correctness with respect to:
Plans will be assessed for completeness with respect to the requirements and the PSP.
Designs and code will be assessed for:
All PSP metrics and test documentation will be assessed for completeness, accuracy and conformance to PSP guidelines.
The tutor will monitor individual contributions to the group when allocating marks to members of the group
Other texts you might find useful include:
Further Reading:
Monash Library Unit Reading List (if applicable to the unit)
http://readinglists.lib.monash.edu/index.html
Types of feedback you can expect to receive in this unit are:
Submission must be made by the due date otherwise penalties will be enforced.
You must negotiate any extensions formally with your campus unit leader via the in-semester special consideration process: http://www.monash.edu.au/exams/special-consideration.html
It is a University requirement (http://www.policy.monash.edu/policy-bank/academic/education/conduct/student-academic-integrity-managing-plagiarism-collusion-procedures.html) for students to submit an assignment coversheet for each assessment item. Faculty Assignment coversheets can be found at http://www.infotech.monash.edu.au/resources/student/forms/. Please check with your Lecturer on the submission method for your assignment coversheet (e.g. attach a file to the online assignment submission, hand-in a hard copy, or use an electronic submission). Please note that it is your responsibility to retain copies of your assessments.
If Electronic Submission has been approved for your unit, please submit your work via the learning system for this unit, which you can access via links in the my.monash portal.
Please check with your lecturer before purchasing any Required Resources. Limited copies of prescribed texts are available for you to borrow in the library, and prescribed software is available in student labs.
You will need access to:
This software is installed in the computing labs; links to sites where these tools can be downloaded for free will be provided on the unit website. Information about computer use for students is available from the ITS Student Resource Guide in the Monash University Handbook.
Pressman, Roger S.. (2010). Software Engineering, A Practioner's Approach. (7th Edition) McGraw-Hill.
Meyer, Bertrand. (1997). Object-Oriented Software Construction. () Prentice-Hall.
Monash has educational policies, procedures and guidelines, which are designed to ensure that staff and students are aware of the University’s academic standards, and to provide advice on how they might uphold them. You can find Monash’s Education Policies at: www.policy.monash.edu.au/policy-bank/academic/education/index.html
Important student resources including Faculty policies are located at http://intranet.monash.edu.au/infotech/resources/students/
The University provides many different kinds of support services for you. Contact your tutor if you need advice and see the range of services available at http://www.monash.edu.au/students. For Malaysia see http://www.monash.edu.my/Student-services, and for South Africa see http://www.monash.ac.za/current/.
The Monash University Library provides a range of services, resources and programs that enable you to save time and be more effective in your learning and research. Go to www.lib.monash.edu.au or the library tab in my.monash portal for more information. At Malaysia, visit the Library and Learning Commons at http://www.lib.monash.edu.my/. At South Africa visit http://www.lib.monash.ac.za/.
This unit is a core unit in the Bachelor of Software Engineering accredited by Engineers Australia. Engineers Australia Accreditation Policy of Professional Engineering Programs requires that programs demonstrate how engineering graduates are prepared for entry to the profession and achieve Stage 1 competencies. The following information describes how this unit contributes to the development of these competencies for the Bachelor of Software Engineering. (Note: not all competencies may be emphasised in this unit).
| Stage 1 competency | How the compency is developed in this unit |
| 1. Knowledge and Skills base | |
| 1.1. Comprehension, theory based understanding of the underpinning natural and physical sciences and the engineering fundamentals applicable to the engineering discipline. | N/A |
| 1.2. Conceptual understanding of the mathematics, numerical analysis, statistics, and computer and information sciences, which underpin the engineering discipline. | Understanding of fundamental concepts of object-oriented (OO) programming |
| 1.3. In-depth understanding of specialist bodies of knowledge within the engineering discipline. | Understanding of basics of software engineering processes and associated practices |
| 1.4. Discernment of knowledge development and research directions within th engineering discipline. | N/A |
|
1.5. Knowledge of engineering design practice and contextual factors impacting the engineering discipline. |
Knowledge of basic OO design principles |
| 1.6. Understanding of the scope, principles, norms, accountabilities and bounds of sustainable engineering practice in the specific discipline. | N/A |
| 2. Engineering application ability | |
| 2.1. Application of established engineering methods to complex engineering problem solving. | Application of OO language and design principles in a complex project |
| 2.2 Fluent application of engineering techniques, tools and resources. | Application of SE techniques for project management, planning, and testing. |
| 2.3. Application of systematic engineering synthesis and design processes. | Application of basic OO design principles |
| 2.4. Application of systematic approaches to the conduct and management of engineering projects. | Application of a disciplined SE project management process |
| 3. Professional and personal attributes | |
| 3.1. Ethical conduct and professional accountability. | N/A |
| 3.2. Effective oral and written communication in professional and lay domains. | Production of written project plans and design documents, written and oral reporting on project process and approaches employed. |
| 3.3. Creative, innovative and proactive demeanour. | N/A |
| 3.4. Professional use and management of information. | N/A |
| 3.5. Orderly management of self, and professional conduct. | Application of the Personal Software Process |
| 3.6. Effective team membership and team leadership. | Participation in a team for the major assignment |
| No. | CO 1 | CO 2 | CO 3 | CO 4 | CO 5 | CO 6 | CO 7 | C0 8 | CO 9 | CO 10 | CO 11 | CO 12 | CO 13 |
| 1 | X | X | |||||||||||
| 2 | X | ||||||||||||
| 3 | X | X | X | ||||||||||
| 4 | X | X | X | X | X | ||||||||
| 5 | X | X | |||||||||||
| 6 | X | X | X | X | X | ||||||||
| 7 | X | X | |||||||||||
| 8 | X | X | X | X |
| No. | Assignments | Quizzes | Practical Exercises | Exam |
| 1 | X | X | X | |
| 2 | X | X | ||
| 3 | X | X | ||
| 4 | X | X | ||
| 5 | X | X | ||
| 6 | X | X | ||
| 7 | X | X | ||
| 8 | X |