http://www.monash.edu.au/pubs/handbooks/subjects/CSE2201.html
Completion of Prerequisites: CSE1203 (or equivalent) + Prohibitions: CFR2128, CFR3042, CSC2050, CSC3020, GCO3811, RDT2231, SFT2201
Some basic familiarity with object-oriented programming and principles may be helpful, but is not assumed in the course materials.
Related subjects are CSE2305 and CSE3302, and supplement the content of this subject .
Prescribed Texts
Meyer, B., Object Oriented Software Construction, (2nd Edition) Prentice Hall 1997.
Pressman R.S., Software Engineering: A Practitioners Approach (4th Edition), McGraw Hill 1996.
Recommended References
Brooks F., The Mythical Man Month, Addison Wesley 1995
Walden K., Nerson J-M, Seamless Object Oriented Software Architectures, Prentice Hall 1995.
Watts Humphreys A Discipline for Software Engineering, Addison Wesley 1995
Wiener R.S., Introduction to Computer Science with Eiffel, Prentice Hall 1996
Further Reading
Humphrey W.S., Managing the Software Process, Addison Wesley 1990
Jezequel, Jean-Marc., Engineering Software with Eiffel, Addison Wesley 1995
Pfleeger S.L., Software Engineering Theory and Practice, Prentice Hall 1998
Somerville I.S., Software Engineering Addison Wesley 1995
Software package
Personal Eiffel for Windows
Each student group will have access to Personal Eiffel for Windows Version 4.4. If you have not used the centralised computer systems this year you will need to obtain a password (refer to Caulfield Computer Centre Information Handout Semester 1 1996 - PC Network Accounts). Eiffel for Windows is loaded from a local server and so will be available even if links to other campuses are down.
Access is by starting Win95 or NT.
As you do not have access to a permanent filestore from PCs you must up and download your source files from floppy to drive C: and up/download before and after an Eiffel session.
Computing and Laboratory Requirements for the Subject
Personal Eiffel for Windows (Home use)
Personal Eiffel for Windows will run on PCs with 16MB of memory or more. A free demonstration version may be obtained for home use. A licensed version will cost $50. (applied in 2000 - may change in 2001. Watch this space)
Download the Personal Eiffel for Windows Version 4.4 software
or
Install the software.
The software that you have obtained and installed in the above manner is a demonstration version, which has some class libraries missing. For this subject these classes are not used so there is no effect on your work, however you may wish to purchase a licensed copy. A licensed copy will cost $50 with a 2 - 3 week wait for the licence to become available. (Applied in 2000 - may change in 2001. Watch this space) Note that ISE have released Eiffel 4.5 recently. We will not be using it for sem. 1 2001 as we have not arranged for licencing requirements for that yet.
Hand to Kym Ferguson, Asst. lecturer the following:
You will be contacted when the lecturer has received your licence number from the producers of Eiffel.
Study materials
It is essential for all students to have
Meyer, B., Object Oriented Software Construction, (2nd Edition) Prentice Hall 1997.
Pressman R.S., Software Engineering: A Practitioners Approach (4th Edition), McGraw Hill 1996
Personal Eiffel for Windows Version 4.4
We provide:
Other study and teaching materials available at http://www.sd.monash.edu.au/education/subjects/cse2201/
Component A
Final Exam 30%
Unit Test 15%
Component B
Tutorial Mini Interview 5%
Programming Assignment, including
Software Engineering Documentation 50%
TOTAL 100%
In order to pass the subject overall you must attain:
Final Exam
The final exam will be conducted during the formal day time examination period at the end of the Semester. Students who miss this exam for medical reasons and can demonstrate this with a medical certificate may sit a Deferred Exam in the formal examination period in January 2001.
Unit Test
The Unit Test will be for 0.75 hour (CSE2201) and will be conducted during the lecture time in Week 8. Students who miss the Unit Test for medical reasons and can demonstrate this with a medical certificate will be allowed to sit the Unit Test at a later specified date.
Tutorial Mini Interview
This Mini Interview will be assessed by your tutor during tutorial time in week 5. Weekly exercises will give assistance prior to assessment of this test. You are advised to attend tutorials to learn what is expected of you. The tasks themselves and the exercises are designed to improve your Eiffel programming skills prior to commencing the assignment work. Students who miss the Mini Interview for medical reasons and can demonstrate this with a medical certificate will be allowed to sit the Mini Interview at a later specified date.
Assignments
All assignment work must be done in teams of two. The two team members are to be in the same tutorial group. The division of work among the team is up to the team to decide, but every team member must be able to demonstrate an understanding of every part of the team’s work. You must be prepared to demonstrate your progress at every tutorial. Each student will be individually interviewed to assess their understanding of the team’s assignment work.
There is one assignment which is to be handed out and assessed in 2 Stages. Each Stage will consist of a Software Engineering component and a Programming component. Marks will be allocated as below, but will be dependent upon your demonstrated understanding of your work as determined by your tutor at your interview.
Stage 1 - Software Engineering submission 10 marks
- Interview based on Programming submission 15 marks
Stage 2 - Software Engineering submission 10 marks
- Interview based on Programming submission 15 marks
Start work on each stage as soon as you receive it, plan what you are going to do, and be organised. The week that each component is due is shown in the Semester Schedule (below).
Your Assignment work is to be handed in within the first 30 minutes of your tutorial for that week. If you have not completed your work, then you hand in what you have done.
Your interview, which ascertains your understanding of the assignment work, will be scheduled by your tutor for later that week or in the following week. It would therefore be possible for you to continue working on the assignment to improve your understanding prior to the interview but the assignment documentation handed in is the documentation that will be assessed.
You will lose 1 mark for documentation that is handed in after 30 minutes into the tute but before the end of the tute. You will lose 2 marks for documentation that is handed in after the tute but by the end of that day. Documentation handed in any later will not be included in the marks and students in this situation will not have an interview. As all marks are obtained by interview, students in this situation or students not attending the interview will achieve no marks. Extensions will not be granted unless a medical certificate indicates an adequate reason for the granting of an extension.
You are expected to go about your work in an orderly manner. Your tutor will expect you to produce up to date design documentation including a Class Model, and an outline of your Requirements Test Plan when reviewing your work. Keep a diary of work done, significant events and problems, task status, ideas, notes, decisions and agreements. Final documentation is to be well presented in a Practical Folder and is to include:
- for the Software Engineering component
- for the Programming component:
Make sure that any work you submit is your own. You are encouraged to assist others and seek assistance from others, but you must acknowledge the author of any work you incorporate into your submission.
Failure to acknowledge the authors of work submitted by you is known as plagiarism and is treated very seriously.
The penalty for plagiarism is 0 marks for that assessment task. For example if one student copies another students work then both students will receive 0 marks. Read on for more information about University policy on plagiarism
Students should consult University materials on cheating, in particular:
It is the student's responsibility to make themselves familiar with the contents of these documents.
If you are in doubt about this discuss it with your tutor before you submit the work.
Note
Note that this subject expects you to build on your existing software development knowledge and skills. The assessment work is developed in such a way as to progressively develop your knowledge and skills. Each Task or Stage builds on the one before and, as the semester progresses, each assessment becomes progressively more complex and difficult.
The subject, however, expects more maturity from you than was expected in first year. It is expected that you will seek out knowledge from the various resources that are available to you rather than wait for a lecturer or tutor to tell you where and when to find the material. In other words staff are not expected to ‘hand-hold’ you through this subject. Ask questions, no matter how basic, and develop your knowledge, skills and maturity as a computing professional. Your success depends upon your own initiative and your desire to gain understanding by seeking answers to your own questions. The assessment for this subject attempts to determine whether you have been able to gain this understanding for yourself.
It is important that your solutions to the assignment questions be your own work. It is perfectly acceptable to seek help and advice when completing the assignments, but this must not be taken to the point where what is submitted is in part someone else's work.
Please note that, since the assignments are used in assessing your final grade in this subject, the following Faculty policy applies.
"Students should note that cheating is regarded as a very serious offence which is likely to lead not only to failure in the subject concerned but also to additional penalties including exclusion. Students should carefully note that the taking of any unauthorised material into examinations such as notes and unauthorised dictionaries will be regarded as cheating. Students should also note that essays, assignments and other work are generally understood to be the student's own work and where such work is identical with, or similar to, another student's work, an assumption of cheating may arise. Where students wish to undertake work in conjunction with other students, it is suggested that the matter be discussed with the lecturer concerned."
Faculty of Computing and Information Technology Handbook
In addition, the following School policy applies.
"The assignments set in this subject are designed primarily as learning exercises, but they also contribute to your final grade.
Copying of other student's assignment solutions is unacceptable.
All students have a responsibility to ensure that their assignment solutions are their own work. You must ensure that others do not obtain access to your solutions for the purpose of copying a part of them. Where such plagiarism is detected, both of the assignments involved will receive no marks.
In significant cases of plagiarism, action may be taken against the offenders under the University's disciplinary regulations."
Your subject adviser for this subject at Clayton is Sita Ramakrishnan
email: sitar@csse.monash.edu.au
Phone: (03) 99052485
Faculty of Information Technology | Monash University
Copyright © 2000 Monash University - All Rights Reserved - Disclaimer
First published: 27 Jan 2000, Last Updated: 26 Feb 2001 by Sita Ramakrishnan
Maintained by sitar@csse.monash.edu.au