ࡱ> mqnq 5bjbjt+t+ 4TAAo1]8L~("KV$ymzz ~   rbPAl uMONASH UNIVERSITY SCHOOL OF COMPUTER SCIENCE AND SOFTWARE ENGINEERING CSE2201 - Software Engineering Practice Subject Handbook Semester 1, 2000 Objectives .................................................1Assessment ...............................................1 Final Exam...............................................2 Unit Test...................................................2 Tutorial Mini Interview .......................2 Assignments ............................................2Resources .................................................4 References ...............................................4 Software ..................................................4 CSSEHELP ..................................................5 Subject Materials .................................5Staff ..........................................................6Semester Schedule.....................................7 CSE2201 CSE2201 is a 6 point subject in the Bachelor of Software Engineering and in the restructured Bachelor of Computing (2330). Objectives At the completion of this subject students should: have further developed their skills as software engineers and have a deeper appreciation of software engineering principles in the development and maintenance of computer systems have further developed their skills in problem solving, abstraction, and software design and generalisation recognise the role of, and be able to use, specific software engineering tools and techniques such as quality assurance plans, software metrics models and formal specification in the software development process. Assessment 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: 50% overall and at least 40% of the available marks in both Component A AND Component B 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 Teams 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 teams work. You must be prepared to demonstrate your progress at every tutorial. Each student will be individually interviewed to assess their understanding of the teams assignment work. Marks 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. Documentation 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 documents as specified for each Stage of the assignment - for the Programming component: Design Document - the Class Model Test Plan Test Results Source Code Program Listing of all Classes Time and Defect Log Sheets and Project Summary 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. 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. Resources References 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 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. 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. 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. Demonstration Version Download the Personal Eiffel for Windows Version 4.4 software from the ISE Web site (defined below) or from the CSE2201 Web page (defined below) or obtain a CD-ROM from the lecturer (Version 4.4) use the CD-ROM in the prescribed Bertrand Meyer text book (Version 4.0) Install the software. Licensing your 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. Obtain the licence in the following manner: Hand to the lecturer the following: a cheque for $50 made payable to Monash University your contact details such as your email address and your phone number You will be contacted when the lecturer has received your licence number from the producers of Eiffel. CSSEHELP AT CAULFIELD CAMPUS Your first port of call for assistance on any of your assessment work outside your tutorial time is the CSSEHELP desk. Check the HELP desk timetable for the times allotted to CSE2201. Subject Materials Training Wheels for Eiffel This is an excellent on-line tutorial/help facility for Eiffel and is available on Windows lab machines after typing win cse2201. Web Site All of the lecture material (in MS Powerpoint format), tutorial notes (MS Publisher HTML) and assignment specifications (MS Word) will be available on the CSE2201 web site which may be accessed via Netscape at http://www.sd.monash.edu.au/education/subjects/cse2201 Also Eiffel source code for tutorials and assignments will be placed on the web site as downloadable zip files. Anonymous Feedback This resource is available as a forum for discussion but it is not CSSEHELP and is not a good medium for solving individual problems. Interactive Software Engineering (ISE) Eiffel Site This is a web site maintained by the company which produces the Eiffel software we use. It has a lot of useful material, including FAQ and references to other Eiffel sites. Its address is: http://www.eiffel.com Eiffel newsgroup Some students may be interested in reading the international Eiffel newsgroup: comp.lang.eiffel STAFF Lectures At Clayton Sita Ramakrishnan Room G.05, Bldg 63 at Clayton, B5.14 at Caulfield) Ph: 99032702 email:  HYPERLINK mailto:sitar@csse.monash.edu.au sitar@csse.monash.edu.au (Jan Miller is in charge of running CSE2201/SFT2201 at Caulfield Campus. CSE2201/SFT2201 is a core subject in the Bachelor of Computing Degree. Her email is  HYPERLINK mailto:jan.miller@infotech.monash.edu.au jan.miller@infotech.monash.edu.au. We will be reusing material that has been put together by Jan and her team of CSE2201 staff, and providing updated contents as required.) Guest lecturers as required. PAGE  PAGE 6 FGH  < H T {   ,jqz|B@N(3QOT#####$@$b$y$$$$$%C%d%%%%%%&/&T&|&&&&&& 56>*CJ 5>*CJ6CJ 56CJ>*CJCJ5CJ55CJOJQJSFGp*,-y{|_ab0<H84 $$x#$$$FGp*,-y{|_abMOP9;<   H g < = H T h {   = N   ,bkl@   `MOP9;<   H @D@(H  & F$ $$x# g < = H T h {   = N    & F,bkl@N$]~ & F & F@N$]~UVOT #####$b$c$z$$ %X%%%%%E&&&&&&&;(<(=(`(a();)<))))9*c**** + +!+9+,,,,&-l-----....^/_/`/i/;0<0t0u000        XUVOT #####$b$c$z$$ %X%%%%%E&&&&&&&&;(<(=(`(a();)<))))9*c**** + +!+9+,, & F & F8 h8 & F  & F&)<)))!+9+,,--....P/[/^/`/i/t0u000112223 3$33333333i4j444444n5o5p5v5w5x5z5{55555550J!mH0J! j0J!UjCJU0J"jCJU jCJU6CJ5CJCJ;,,,&-l-----....^/_/`/i/;0<0t0u00001111 & F & F001111s2t222222223 3$373W3l3z3333O5P5m5n5o5z555555  #1s2t222222223 3$373W3l3z3333O5P5m5n5o5x5y5z5 h &`#$1$z5555551$ &`#$200 &P . A!"#$% DyK sitar@csse.monash.edu.auyK @mailto:sitar@csse.monash.edu.au DyK "jan.miller@infotech.monash.edu.auyK Rmailto:jan.miller@infotech.monash.edu.au# [(@(Normal1$mH J@J Heading 1 $<5CJKHOJQJkHH@H Heading 2 $<56CJOJQJkH:@: Heading 3 $<5CJ<A@<Default Paragraph FontTOTBody"d1$ ;r B*CJOJQJkHmH VVBulletedgd1$ gB*CJOJQJkHmH HHCellBody d1$5B*CJOJQJkHmH P"P CellHeading$d1$5B*CJOJQJkHmH V2VFootnoteXXd1$ XB*OJQJkHmH RBRHeading1$d@x1$5B*CJOJQJkHmH RRRHeading2$d<1$5B*CJOJQJkHmH VbV HeadingRunIn$dx1$5B*CJOJQJkHmH RrRIndentedgd1$ gB*CJOJQJkHmH VVNumberedgd1$ gB*CJOJQJkHmH ^^ Numbered1gdTP1$ g5B*CJOJQJkHmH `` TableFootnoteXXd1$ XB*OJQJkHmH NN TableTitle$d1$5B*CJOJQJkHmH @>@Title$$dT5B*CJOJQJkHNN CellFooting$d1$B*CJOJQJkHmH ExampleKmd1$ 5R . e @w S"$5B*CJOJQJkHmH @@@Header$d H$ OJQJkHD @DFooter $d H$B*OJQJkH&)@& Page Number(U@!( Hyperlink>*B*1T &5% &,1z55 !#$&()@05"'///i0001XX !! !!!!!"E"M"$$&&++..B/F/a/j/l/n///////0 0i000000o1w1z1111)hxN^l<L^8pgp " V ^ { ?Jx =qIN_b ! ""&&--..z//\00o1w1z1111 Jan Miller1C:\WINDOWS\TEMP\AutoRecovery save of HAND-299.asd Jan Miller1C:\WINDOWS\TEMP\AutoRecovery save of HAND-299.asdsramakriC:\BSE\Handcse2201.docsramakriA:\Handcse2201.docSita Ramakrishnan,C:\TEMP\AutoRecovery save of Handcse2201.asdSita RamakrishnanA:\Handcse2201.docSita RamakrishnanC:\BSE\Handcse2201.docSita RamakrishnanC:\BSE\Handcse2201.docSita RamakrishnanA:\Handcse2201.doc Ramakrishnan#C:\cse2201\handbook12000clayton.doc g%!$L~2 )5 8E I=v!Idv *44o(- hhOJQJo( hhOJQJo( hhOJQJo(44o(- hhOJQJo(  g%I=v$L~28E)5Idv @ OJQJo(@HP LaserJet 2100 Series PCL 6LPT1:winspoolHP LaserJet 2100 Series PCL 6HP LaserJet 2100 Series PCL 6$w odLetter$JAPD!CdTimes New RomanH  !CHP LaserJet 2100 Series PCL 6$w odLetter$JAPD!CdTimes New RomanH  !C01`@GTimes New Roman5Symbol3& Arial3TIMES"h BF BFA&(V!0 2MONASH UNIVERSITYMonash University RamakrishnanOh+'0   < H T `lt|MONASH UNIVERSITYdONAMonash Universitydona Normal.dote Ramakrishnansit2maMicrosoft Word 8.0@F#@[b@JAl@JAl&(՜.+,D՜.+,L hp  Monash UniversitycV 21 MONASH UNIVERSITY Title(RZ _PID_GUID _PID_HLINKSAN{E6D63F80-8F97-11D2-8307-00A00C11483C}A S/)mailto:jan.miller@infotech.monash.edu.au> mailto:sitar@csse.monash.edu.au  !"#$%&'()*,-./012456789:;<=>?@BCDEFGHJKLMNOPSRoot Entry FVAl@"AlUData +1Table3WordDocument4TSummaryInformation(ADocumentSummaryInformation8ICompObjjObjectPool@"Al@"Al  FMicrosoft Word Document MSWordDocWord.Document.89qOh+'0   < H T `lt|MONASH UNIVERSITYdONAMonash Universitydona Normal.dote Ramakrishnansit3maMicrosoft Word 8.0@G@[b@JAl@Al)(՜.+,D՜.+,L hp  Monash UniversitycW%21 MONASH UNIVERSITY Title(RZ _PID_GUID _PID_HLINKSAN{E6D63F80-8F97-11D2-8307-00A00C11483C}A S/)mailto:jan.miller@infotech.monash.edu.au> mailto:sitar@csse.monash.edu.au&)<)))!+9+,,--....P/[/^/`/i/t0u000112223 3$33333333i4j444444n5o5p5v5w5x5z5{55555556TfThTjTlTCJ0J!mH0J! j0J!UjCJU0J"jCJU jCJU6CJ5CJCJ@200 &P . A!"#$% Handbook12000clayton.doc6 z5555556TjTlT1$ &`#$# [(@(Normal1$mH J@J Heading 1 $<5CJKHOJQJkHH@H Heading 2 $<56CJOJQJkH:@: Heading 3 $<5CJ<A@<Default Paragraph FontTOTBody"d1$ ;r B*CJOJQJkHmH VVBulletedgd1$ gB*CJOJQJkHmH HHCellBody d1$5B*CJOJQJkHmH P"P CellHeading$d1$5B*CJOJQJkHmH V2VFootnoteXXd1$ XB*OJQJkHmH RBRHeading1$d@x1$5B*CJOJQJkHmH RRRHeading2$d<1$5B*CJOJQJkHmH VbV HeadingRunIn$dx1$5B*CJOJQJkHmH RrRIndentedgd1$ gB*CJOJQJkHmH VVNumberedgd1$ gB*CJOJQJkHmH ^^ Numbered1gdTP1$ g5B*CJOJQJkHmH `` TableFootnoteXXd1$ XB*OJQJkHmH NN TableTitle$d1$5B*CJOJQJkHmH @>@Title$$dT5B*CJOJQJkHNN CellFooting$d1$B*CJOJQJkHmH ExampleKmd1$ 5R . e @w S"$5B*CJOJQJkHmH @@@Header$d H$ OJQJkHD @DFooter $d H$B*OJQJkH&)@& Page Number(U@!( Hyperlink>*B*1T//N1m11111@@ &lT% &,1z5lT !#$&()@05"'Unknown Ramakrishnan///h0001XX !! !!!!!"E"M"$$&&++..B/F/a/j/l/n///0 000111)hxN^l<L^8pgp " V ^ { ?Jx =qIN_b ! ""&&--..z//111 Jan Miller1C:\WINDOWS\TEMP\AutoRecovery save of HAND-299.asd Jan Miller1C:\WINDOWS\TEMP\AutoRecovery save of HAND-299.asdsramakriC:\BSE\Handcse2201.docsramakriA:\Handcse2201.docSita Ramakrishnan,C:\TEMP\AutoRecovery save of Handcse2201.asdSita RamakrishnanA:\Handcse2201.docSita RamakrishnanC:\BSE\Handcse2201.docSita RamakrishnanC:\BSE\Handcse2201.docSita RamakrishnanA:\Handcse2201.doc Ramakrishnan#C:\cse2201\handbook12000clayton.doc g%!$L~2 )5 8E I=v!Idv *44o(- hhOJQJo( hhOJQJo( hhOJQJo(44o(- hhOJQJo( g%I=v$L~28E)5Idv@ OJQJo(@HP LaserJet 2100 Series PCL 6LPT1:winspoolHP LaserJet 2100 Series PCL 6HP LaserJet 2100 Series PCL 6$w odLetter$JAPD!CdTimes New RomanH  !CHP LaserJet 2100 Series PCL 6$w odLetter$JAPD!CdTimes New RomanH  !Cl1l10l1l1CJ//m1n1v11111111`@`4T`g@a6Ta8TaHT`k@`j@afT`k@`hT`k@GTimes New Roman5Symbol3& Arial3TIMES"Ah BF BFA)(W!20%2MONASH UNIVERSITYMonash University Ramakrishnanq 5bjbjt+t+ VAA1]~~~8Lb ( " KZ$| l  2 0l l l    l l .   5Al~ Root Entry FVAl5AlsData +1Table3WordDocumentkV  !"#$Y'([,-./012456789:;<=>?@&Z]^_`abcdefghijlpotr0Table\SummaryInformation(DocumentSummaryInformation8CompObjjObjectPool@"Al@"Al _PID_GUID _PID_HLINKSAN{E6D63F80-8F97-11D2-8307-00A00C11483C}A S/)mailto:jan.miller@infotech.monash.edu.au> mailto:sitar@csse.monash.edu.auOh+'0  FMicrosoft Word Document MSWordDocWord.Document.89q՜.+,D՜.+,L hp  Monash UniversitycW%21 MONASH UNIVERSITY Title(RZ    < H T `lt|MONASH UNIVERSITYdONAMonash Universitydona Normal.dote Ramakrishnansit3maMicrosoft Word 8.0@G@[b@JAl@Al)(