This unit will provide students with an introduction to systems development using an agile development approach. The unit will focus on the application of UML models to the analysis and design of a system. The unit will introduce students to the nature of systems analysis and design as a problem-solving activity, describe the key elements of analysis and design, and explain the place of the analysis and design phases within the an agile development life cycle. The unit will introduce students to the nature of modelling as an analytical and a communicative process.
Major topics include: Agile development and the role of prototyping in systems development, user interface design, domain modelling with UML class diagrams, process modelling with use-case diagrams, use-case driven development and testing, use-case realisation with sequence diagrams, requirements gathering and the implementation and support phases of systems development.
2 hrs lectures/wk, 2 hrs laboratories/wk
Students will be expected to spend a total of 12 hours per week during semester on this unit.
This will include:
Lectures: 2 hours per week
Tutorials/Lab Sessions: 2 hours per week per tutorial
and up to an additional 8 hours in some weeks for completing lab and project work, private study and revision.
BUS2021, CPE2003, CSE1204, CSE1205, GCO1813, GCO2601, GCO2852, GCO2826, IMS1001, IMS1002, IMS1805, IMS2071, IMS9001
FIT1004 or FIT2010
For students in courses 2380, 2770, 3517 and 2672 who commenced prior to 2011: FIT1008
David Grant
David Grant
Examination (3 hours): 60%; In-semester assessment: 40%
| Assessment Task | Value | Due Date |
|---|---|---|
| Requirements specification with UML and prototypes | 20% | Assignment 1 due 9 September, 2012 |
| Design specification and test planning | 20% | Assignment 2 due 21 October, 2012 |
| Examination 1 | 60% | To be advised |
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 SETU, Student Evaluation of Teacher and Unit. 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, and on student evaluations, see:
http://www.monash.edu.au/about/monash-directions/directions.html
http://www.policy.monash.edu/policy-bank/academic/education/quality/student-evaluation-policy.html
Previous feedback has highlighted that unit is strong in its core content and is reflective of contemporary system development practice. Students have appreciated the opportunity to use CASE and prototyping tools.
Student feedback has indicated that the delivery of the content sometimes seemed 'out of order' and it differed from the order of the material in the textbook.As a result the delivery of the content has been changed to better reflect the textbook.
Students also indicated that the number of individual assignments and their associated workload was excessive and limited the amount of effort they were able to devote to the tasks. The assignment tasks have been reduced to two major assignments both of which are group-based. This will give students the opportunity to collaborate, develop their teamwork skills, and benefit from a greater collective effort.
If you wish to view how previous students rated this unit, please go to
https://emuapps.monash.edu.au/unitevaluations/index.jsp
Please check with your lecturer before purchasing any Required Resources. Limited copies of prescribed texts are available for you to borrow in the library, and prescribed software is available in student labs.
Students will require access to an "industrial strength" CASE (computer aided software engineering) tool. In 2011, the tool choosen is Visual Paradigm for UML. This is available for download from the FIT2001 Moodle-based unit web site.
Students will also require access to standard personal productivity tools (word processing , graphics and presentation)
John W Satzinger, Robert B Jackson, Stephen D Burd. (2011). Systems Analysis And Design In A Changing WorldSystems Analysis And Design In A Changing World . (Sixth edition) Course Technology.
Doug Rosenberg, Matt Stephens. (2007). Use case driven object modeling with UML theory and practice. () Apress.
| Week | Activities | Assessment |
|---|---|---|
| 0 | No formal assessment or activities are undertaken in week 0 | |
| 1 | The development environment | |
| 2 | Domain modelling with UML | |
| 3 | Prototyping in analysis and design | |
| 4 | Process modelling with use case models | |
| 5 | Interface design principles Interface design principles | |
| 6 | Usability testing | |
| 7 | Principles of good design | Assignment 1: Requirements specification with UML and prototypes - due 9 September, 2012 |
| 8 | Use case realisation with sequence diagrams | |
| 9 | The requirements specification and RFPs | |
| 10 | Use case driven testing | |
| 11 | Requirements gathering and stakeholder expectation management | |
| 12 | The implementation and support phase | Assignment 2: Design specification and test planning - due 21 October, 2012 |
| SWOT VAC | No formal assessment is undertaken 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 MUSO (Blackboard or Moodle) learning system.
Faculty Policy - Unit Assessment Hurdles (http://www.infotech.monash.edu.au/resources/staff/edgov/policies/assessment-examinations/unit-assessment-hurdles.html)
Academic Integrity - Please see the Demystifying Citing and Referencing tutorial at http://lib.monash.edu/tutorials/citing/
This assignment is a group assignment.
The assignment will be assessed using the following main criteria:
Each team member will assess the contribution of their team members and themselves using a peer assessment form. The criteria students will use to make their assessment are their interest an energy, reliability, quality of work, organisation and planning, initiative, teamwork, problem solving, and extent of contribution.
The peer assessments will be used to recognise different contibutions to the assignment.
For full details see the unit web site.
This assignment is a group assignment.
The assignment will be assessed using the following main criteria:
Each team member will assess the contribution of their team members and themselves using a peer assessment form. The criteria students will use to make their assessment are their interest an energy, reliability, quality of work, organisation and planning, initiative, teamwork, problem solving, and extent of contribution.
The peer assessments will be used to recognise different contibutions to the assignment.
For full details see the unit web site.
It is a University requirement (http://www.policy.monash.edu/policy-bank/academic/education/conduct/plagiarism-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).
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.
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:
http://policy.monash.edu.au/policy-bank/academic/education/index.html
Key educational policies include:
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 www.monash.edu.au/students. For Sunway 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 and resources that enable you to save time and be more effective in your learning and research. Go to http://www.lib.monash.edu.au or the library tab in my.monash portal for more information. At Sunway, visit the Library and Learning Commons at http://www.lib.monash.edu.my/. At South Africa visit http://www.lib.monash.ac.za/.
Academic support services may be available for students who have a disability or medical condition. Registration with the Disability Liaison Unit is required. Further information is available as follows:
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.
Shelley, G.B. and H.J. Rosenblatt (2010) Systems Analysis and Design, 8th Edition, Thomson Course Technology.