This unit provides an introduction to the discipline of software engineering at the postgraduate level. The emphasis is upon a broad coverage of various aspects of software engineering. We assume the students will at this stage have adequate programming skills and are able to put theories to practice. The notion of a software system as a model or approximation of a desired system is introduced, and used as a way of describing such things as the software life cycle and its various models, programming by contract, design and testing issues, maintenance, reuse, complexity, divide and conquer strategies, metrics and measurement, project management and software legacy.
Minimum total expected workload equals 12 hours per week comprising:
(a.) Contact hours for on-campus students:
(b.) Additional requirements (all students):
FIT5131 or FIT9017 or equivalent
Chris Ling
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
| Week | Activities | Assessment |
|---|---|---|
| 0 | Check your lab class enrolments | No formal assessment or activities are undertaken in week 0 |
| 1 | Introductions | No prac/lab this week. Prac/Lab classes start in Week 2 |
| 2 | Software Life-cycle Models | Assessment task 1: Weekly quizzes (Weeks 2-12) to be submitted via Moodle, closing each Wednesday before 11.59pm. Assessment task 2: Practical class assessments - Weekly in Lab classes. |
| 3 | Requirements | |
| 4 | Analysis | |
| 5 | Dynamic Modelling | |
| 6 | Design | |
| 7 | Modules | |
| 8 | Testing | |
| 9 | Implementation | |
| 10 | Formal Methods | |
| 11 | Ethics | |
| 12 | Tools/Review | Assessment task 3: Work Folio due Friday |
| 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 (3 hours): 60%; In-semester assessment: 40%
| Assessment Task | Value | Due Date |
|---|---|---|
| Weekly Quizzes | 5% | Weekly, on-line, before 11.59pm Wednesday (Week 2 to Week 12) |
| Practical class assessments | 30% | Weekly in lab classes (Week 2 to 12) |
| Work Folio | 5% | Friday, Week 12 |
| Examination 1 | 60% | 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/
Correct answers demonstrating basic knowledge and understanding of course material.
For group work, some marks will be for the group as a whole, some for an individual's contribution; details will be specified in the assessment task description.
Some tasks will be assessed in the lab class itself. When marking is done outside the lab, in most cases students must submit their work at the end of the lab class. Details will be given with each lab class description provided each week.
A set of guidelines for the eFolio is provided online.
Criteria for assessing the folio are:
Recommended (good general "classic" software engineering texts):
Also, for the "Ethics" topic, the reading will be Chapter 8 from Michael J. Quinn. Ethics for the Information Age, 4th Edition. Boston, MA: Addison-Wesley, 2011 (available electronically from the Monash library reading list).
Monash Library Unit Reading List (if applicable to the unit)
http://readinglists.lib.monash.edu/index.html
Faculty of Information Technology Style Guide
Examination/other end-of-semester assessment feedback may take the form of feedback classes, provision of sample answers or other group feedback after official results have been published. Please check with your lecturer on the feedback provided and take advantage of this prior to requesting individual consultations with staff. If your unit has an examination, you may request to view your examination script booklet, see http://intranet.monash.edu.au/infotech/resources/students/procedures/request-to-view-exam-scripts.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
If students do not attend a laboratory class, they cannot submit work for that assessment later. Late or resubmissions may be permitted at the discretion of the demonstrator or lecturer, for example if there have been technical difficulties during the laboratory class.
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 online quiz). Please note that it is your responsibility to retain copies of your assessments.
Limited copies of prescribed texts are available for you to borrow in the library.
Stephen R. Schach. (2008). Object-Oriented Software Engineering. (1st Edition) McGraw-Hill (ISBN: 978-0-07-352333-0).
Note: Schach's "Object-Oriented & Classical Software Engineering", 7th Edition and 8th Edition are very similar, and can be used in place of the prescribed textbook mentioned above.
The exam will be an "open book" exam. Students may bring in textbooks, any of the unit teaching material and any notes they have made themselves. More details will be provided on the unit website prior to the exam.
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
Key educational policies include:
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/.