Mr Peter O'Donnell
Lecturer
Phone: +61 3 990 32502
Dr Rob Meredith
Lecturer
Phone: +61 3 990 32396
Fax: +61 3 990 31204
Welcome to FIT2001 Systems Analysis and Design. It is a fun unit to study but it is also very important to your development as a professional in the field of Information Technology.
Every graduate of our Faculty needs to understand the basics of systems analysis and systems design, it is a very important aspect of the work of an information technology professional. As a result this introductory unit on analysis and design is part of the common core that is studied by all undergraduates of the Faculty.
Many students will go on to have careers as systems analysts and systems designers. Even those who don't will work with and for analysts and designers and will need to know what and how they do what they do. One good analogy that is can be used to explain the difference between the work of a programmer from an analyst, is to compare the roles to that of a builder and architect. A builder - like a programmer - does the actual construction work. The architect does the design work - in consultation with a client - and develops a plan that will be implemented by the builder. The architects need to know what builders can and can't do, as well as the various properties and uses of different building materials and techniques. In the same way, an analyst needs to know what a programmer can and can't do and what the available technology is capable of. The builder needs to be able to read and understand the plans that they are provided with so they can create the structure the client wanted. Similiarly, a programmer needs to be able to understand the "plans" called requirements specifications and design specifications that the analysts and designers create. Often, especially earlier in your career, you are very likely to find your self performing both roles as a junior analyst/programmer (a very common graduate job title).
Students who hope to work in more specialised areas like networking, multimedia and games development still need to master the basics of analysis and design. The core of analysis and design is to understand some information problem in some "real" world domain and create a model of that. The model is created in tools that are formal enough to become the basis of the design of an information technology system. However, at the same time they are often graphical so they can be developed with and shared with end-users, who may not be IT-design literate, to ensure that the system developed will meet their needs and provide the intended benefits.
This semester the unit will run on the Caulfield campus.
For on campus students, workload commitments are:
You will need to allocate up to 5 hours per week in some weeks, for use of a computer, including time for newsgroups/discussion groups.
Off-campus students generally do not attend lecture and tutorial sessions, however, you should plan to spend equivalent time working through the relevant resources and participating in discussion groups each week.
You will need to allocate around 12 hours per week during the semester for this unit.FIT2001 is a common core unit for all Faculty of IT undergraduate degrees. It is a prerequisite for many units in the second and third years of these degrees.
You may not study this unit and BUS2021, BUS2071, CSE1204, CSE1205, GCO1813, GCO2601, GCO2852, GCO2826, IMS1001, IMS1002, IMS1805, or IMS2701 in your degree.
The teaching and learning in the unit is structured in the traditional manner around lectures and laboratory-based workshops. Most of the lecture and tutorial material is strongly supported by the prescribed text for the unit, it is very important that you get a copy of the text. Each week there is reading set from the text, you will find the unit isn't too difficult if you study consistently through the semester and keep up with the reading and exercises.
Your learning is also supported by additional web-based resources including a Moodle-based web site. You will find on the unit web site a forum - which will be actively monitored by staff - that you can used to ask questions or follow up on any issues you have. You will also find a set of lecture recordings (synchronised with the lecture slides) and some interviews with practising systems analysts in a podcast stream along with resources to make it easy for you to download and listen in.
For information on timetabling for on-campus classes please refer to MUTTS, http://mutts.monash.edu.au/MUTTS/
On-campus students should register for tutorials/laboratories using the Allocate+ system: http://allocate.cc.monash.edu.au/
| Week | Topic | Study guide | References/Readings | Key dates |
|---|---|---|---|---|
| 1 | Introduction to systems analysis and design | Study guide 1: Introduction to systems analysis and design | Chapter 1 from unit text (SJB) - Satzinger, J. W., Jackson, R.B., and S.D. Burd (2008) Systems Analysis and Design in a Changing World, 5th Edition, Thomson Course Technology. | |
| 2 | The context of systems analysis and design | Study guide 2: The context of systems analysis and design | Chapter 2 and parts of chapter 3 SJB | |
| 3 | Requirements gathering | Study guide 3: Requirements gathering | Chapter 4 SJB | |
| 4 | Beginning analysis | Study guide 4: Beginning analysis | Chapter 5 SJB | |
| 5 | The traditional or structured approach to analysis | Study guide 5: The traditional or structured approach to analysis | Chapter 6 SJB | |
| 6 | Use case modelling | Study guide 6: Use case modelling | Chapter 7 SJB | Assignment 1a due |
| 7 | Finishing analysis | Study guide 7: Finishing analysis | Chapter 8 SJB | |
| 8 | The nature of good design | Study guide 8: The nature of good design | Chapter 9 SJB | |
| 9 | Structured design | Study guide 9: Structured design | Chapter 10 SJB | Assignment 1b due |
| 10 | Design - use case realisation | Study guide 10: Design - user case realisation | Chapter 12 SJB | |
| Mid semester break | ||||
| 11 | The user interface | Study guide 11: The user interface | Chapter 14 SJB | |
| 12 | System interfaces | Study guide 12: System interfaces | Chpater 15 SJB | Assignment 2 due |
| 13 | Unit review | Past exam papers available on unit web site. | ||
There is one prescribed text. Note that students are expected to purchase this text.
Satzinger, J. W., Jackson, R.B., Burd, S.D. and R. Johnson (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.
Booch, G., Rumbaugh, J. and I. Jacobson (1999) The Unified Modeling Language User Guide Addison Wesley Professional.
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.
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 FIT2001 Moodle-based unit web site or from your tutor.
Students will also require access to traditional personal productivity tools (word processing , graphics and presentation).
Software may be:
Study resources we will provide for your study are:
The major study resources for FIT2001 are:
To pass a unit which includes an examination as part of the assessment a student must obtain:
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 44% then a mark of no greater than 44-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 a unit which includes an examination as part of the assessment a student must obtain:
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.
Weighting:
60%
Length:
3 hours
Type (open/closed book):
Closed book
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
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.
Students can expect assignments to be returned within two weeks of the submission date or after receipt, whichever is later.
Please visit the following URL: http://www.infotech.monash.edu.au/units/appendix.html for further information about: