FIT9030 Systems analysis and design - Semester 2, 2010

Caulfield

Prohibitions

Teaching approach

The teaching and learning in this unit is structured in the traditional manner around lectures and laboratory-based tutorial workshops. Most of the lecture and tutorial material is strongly supported by the prescribed text for the unit. It is important that you obtain a copy of the text. Each week there is reading set from the text and you will find that the unit isn't too difficult if you study consistently throughout the semester, and keep up with reading and exercises.

Your learning is also supported by some additional resources on the Moodle-based web site. You will find a forum - which will be actively monitored by staff - that you can use to ask questions or follow up on any issues you may have.

Timetable information

For information on timetabling for on-campus classes please refer to MUTTS, http://mutts.monash.edu.au/MUTTS/

Tutorial allocation

On-campus students should register for tutorials/laboratories using the Allocate+ system: http://allocate.its.monash.edu.au/

Unit Schedule

*Please note that these dates may only apply to Australian campuses of Monash University. Off-shore students need to check the dates with their unit leader.

Prescribed text(s) and readings

There is one prescribed text. Note that students are expected to purchase this text.

• Satzinger, J. W., Jackson, R. B., Burd, S. D. and Johnson, R., (2008), Systems Analysis and Design in a Changing World, 5th Edition, Thomson Course Technology.

Text books are available from the Monash University Book Shops. Availability from other suppliers cannot be assured. The Bookshop orders texts in specifically for this unit. You are advised to purchase your text book early.

Recommended text(s) and readings

Dennis, A., Wixom, B.H. and D. Tegarden (2008) Systems Analysis and Design with UML Version 2.0: An Object-Oriented Approach, 3rd Edition, Wiley.

Hoffer, J.A., George, J.F. and J.S. Valacich (2001) Modern Systems Analysis and Design 3rd Edition, Prentice Hall.

George, J.F., Batra, D., Valacich J.S. and J.A. Hoffer, (2004) Object-Oriented System Analysis and Design Prentice-Hall.

Lee, R. and W. Tepfenhart (2002) Practical Object-Oriented Development with UML and Java, Prentice Hall.

Maciaszek, L. (2004) Requirements Analysis and System Design, 2nd Edition, Addison-Wesley.

Page-Jones, M. (1988) The Practical Guide to Structured Systems Design 2nd Edition, Prentice-Hall.

Page-Jones, M. (2000) Fundamentals of Object-Oriented Design in UML Addison-Wesley.

Required software and/or hardware

Students will require access to an "industrial strength" CASE (computer aided software engineering) tool. In 2009, the tool choosen is Visual Paradigm for UML. This product can be downloaded from the Visual Paradigm web site but to run requires a license key. This is available for download from the FIT9030 Moodle-based unit web site or from your tutor.

Students will also require access to traditional personal productivity tools (word processing , graphics and presentation).

Equipment and consumables required or provided

Study resources

Study resources we will provide for your study are:

* Weekly detailed lecture notes outlining the learning objectives, discussion of the content, required readings and exercises;
* Weekly tutorial or laboratory tasks and exercises with sample solutions provided one to two weeks later;
* Assignment specifications and sample solutions;
* A sample examination and suggested solution
* Access to past examination papers;
* Discussion groups;
* This Unit Guide outlining the administrative information for the unit;
* The unit web site on Moodle, where resources outlined above will be made available.

Overview

Faculty assessment policy

To pass a unit which includes an examination as part of the assessment a student must obtain:

• 40% or more in the unit's examination, and
• 40% or more in the unit's total non-examination assessment, and
• an overall unit mark of 50% or more.

If a student does not achieve 40% or more in the unit examination or the unit non-examination total assessment, and the total mark for the unit is greater than 50% then a mark of no greater than 49-N will be recorded for the unit.

The unit is assessed with two assignments (the first one is in two parts) and a three hour closed book examination. If you maintain a reflective blog a further bonus mark can be added to your assignment mark.

To pass the unit you must:

• attempt the assignments and examination
• achieve no less than 40% of the possible marks individually in the assignment and exam
• achieve no less than 50% of possible marks (of assignment and examination taken together) for the unit.

Assignment tasks

Assignment coversheets

Assignment coversheets are available via "Student Forms" on the Faculty website: http://www.infotech.monash.edu.au/resources/student/forms/
You MUST submit a completed coversheet with all assignments, ensuring that the plagiarism declaration section is signed.

Assignment submission and return procedures, and assessment criteria will be specified with each assignment.

Assignment submission and preparation requirements will be detailed in each assignment specification. 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.infotech.monash.edu.au/resources/student/equity/special-consideration.html.

• Assignment task 1

  Title:

  Assignment 1a: Draft requirements specification with event table

  Description:

  Assignment work in the unit is fully described, along with the assessment criteria, on the assignment page of the Moodle-based unit web site.In this first assignment task you will create a draft of your requirements specification that will include a fully developed event table.

  Weighting:

  5%

  Criteria for assessment:

  The criteria used to assess submissions are:

  1. Correctness and understanding - there may be more than one "valid" answer in many cases. We will look for answers that reflect understanding of the nature of the system being described.
  2. Completeness - that you have addressed all required parts of each assignment.
  3. Presentation - that you have presented your answers in a suitably formatted report style.

  Due date:

  Midnight, Friday, end of week 6.

• Assignment task 2

  Title:

  Assignment 1b: Requirements specification

  Description:

  Assignment work in the unit is fully described, along with the assessment criteria, on the assignment page of the Moodle-based unit web site.In this second assignment task you will create a finalise of your requirements specification, this will include a context diagram, an event table, a use case diagram and associated use case narratives and and domain class model.

  Weighting:

  20%

  Criteria for assessment:

  The criteria used to assess submissions are:

  1. Correctness and understanding - there may be more than one "valid" answer in many cases. We will look for answers that reflect understanding of the nature of the system being described.
  2. Completeness - that you have addressed all required parts of each assignment.
  3. Presentation - that you have presented your answers in a suitably formatted report style.

  Due date:

  Midnight, Sunday, end of week 9.

• Assignment task 3

  Title:

  Assignment 2: Design specification

  Description:

  Assignment work in the unit is fully described, along with the assessment criteria, on the assignment page of the Moodle-based unit web site.In this final assignment task you will create a design-specification that will include a partial design class model, a sequence diagram, a partial interface design and a database design model.

  Weighting:

  25%

  Criteria for assessment:

  The criteria used to assess submissions are:

  1. Correctness and understanding - there may be more than one "valid" answer in many cases. We will look for answers that reflect understanding of the nature of the system being described.
  2. Completeness - that you have addressed all required parts of each assignment.
  3. Presentation - that you have presented your answers in a suitably formatted report style.

  Due date:

  Midnight, Sunday, end of week 12.

• Assignment task 4

  Title:

  Reflective blog posts

  Description:

  Reflective blog posts give students the means to reflect their viewpoints about the work they are undertaking and the outcomes they are achieving. They provide students with an opportunity to critically assess themselves and the unit.

  Weighting:

  Bonus of 3% added to overall assignment mark

  Criteria for assessment:

  Blog postings will be assessed based on the number of posts during the semester, and on the the extent to which students reflect on their unit-based activities.

  Due date:

  Your last blog entry can be made anytime before the exam.

  Remarks:

  Each student is invited to keep a reflective journal on the  Moodle-based unit web site. This blog will provide the opportunity to reflect on the learning that takes place throughout the unit. Each week you will be able to make a new posting to your blog. The blog entries should include a reflection on what has happened in terms of your progress on assignment and tutorial work, your management of the assignment project and its tasks, what lessons have been learned to date and what you (and the staff) could do differently. A page listing all the reflective journals of FIT9030 students will be maintained on the Moodle-based unit web site.To obtain the 3% bonus mark for this task students must complete a minimum of 10 weekly blog entries during the semester. Each blog post will be read and assessed by the chief examiner. To get the 3% bonus 6 of these posts should be assessed as "satisfactory".
  
  The 3% bonus will be added to the assignment component of the mark available for the unit. Note that that component cannot exceed 40%. So, for example, a student who obtained 36/40 for their assignment work who earns the bonus will get 39%. While a student who got 39/40 would get 40/40 - the maximum available - if they earned the bonus.
  
  For more details, please refer to the Moodle-based unit web site.

Examination

• Weighting:

  50%

  Length:

  3 hours

  Type (open/closed book):

  Closed book

  Electronic devices allowed in the exam:

  None

Due dates and extensions

Please make every effort to submit work by the due dates. It is your responsibility to structure your study program around assignment deadlines, family, work and other commitments. Factors such as normal work pressures, vacations, etc. are not regarded as appropriate reasons for granting extensions. Students are advised to NOT assume that granting of an extension is a matter of course.

Students requesting an extension for any assessment during semester (eg. Assignments, tests or presentations) are required to submit a Special Consideration application form (in-semester exam/assessment task), along with original copies of supporting documentation, directly to their lecturer within two working days before the assessment submission deadline. Lecturers will provide specific outcomes directly to students via email within 2 working days. The lecturer reserves the right to refuse late applications.

A copy of the email or other written communication of an extension must be attached to the assignment submission.

Refer to the Faculty Special consideration webpage or further details and to access application forms: http://www.infotech.monash.edu.au/resources/student/equity/special-consideration.html

Late assignment

If you believe that your assignment will be delayed because of circumstances beyond your control such as illness you should apply for an extension before the due date. Medical certificates or certification supporting your application may be required. Assignments submitted after the due date may incur a penalty for lateness. An assignment submitted more than seven days after the due date may be given a score of zero. If you anticipate being late then discuss the situation with your unit lecturer as early as possible; your unit lecturer will decide how many marks you will be penalised for each day your assignment is late, and whether or not any extension is warranted.

Assignments received after the due date will normally be subject to a penalty of 5% per day, including weekends. Assignments received later than one week (seven days) after the due date will not normally be accepted. In some cases, this period may be shorter if there is a need to release sample solutions.

This policy is strict because comments or guidance will be given on assignments as they are returned, and sample solutions may also be published and distributed, after assignment marking or with the returned assignment.

Return dates

Students can expect assignments to be returned within two weeks of the submission date or after receipt, whichever is later.

Feedback

Types of feedback you can expect to receive in this unit are:

Informal feedback on progress in labs/tutes

Graded assignments with comments

Quiz results

Solutions to tutes, labs and assignments