The Case study provides the opportunity for students to focus their skills of system analysis and development, software design and development, documentation development and quality, system and software quality, interpersonal relationships and formal and quality documentation in the development of a solution to the Case Study project. Working as members of supervised teams, students undertake the analysis, design, documentation and implementation of an appropriate software system to assist with the resolution of a realistic business problem. As part of their success, teams will decide their methodology, and demonstrate quality planning and project planning skills.
1 hr seminar/wk, 3 hrs tutorials/wk
Workload commitments per week are:
You are expected to spend an additional 8 hours per week on various activities including reading, communication with other students and unit lecturers, and preparation for learning tasks and formal assessments.
Tutorials are to be used as the first point of contact for your groups and as such attendance is a necessary prerequisite.
CSE3900, CSE9020, FIT3015, FIT3048, GCO9800,GCO3500
FIT9017, FIT9018, FIT9019 and FIT9030
Must be enrolled in course 3309, 0366, 0539, 0360 or 1772
Sue Foster
To be advised
| Week | Activities | Assessment |
|---|---|---|
| 0 | No formal assessment or activities are undertaken in week 0 | |
| 1 | Introduction to Case Study | Students are provided with FIT4037 survival kit. As part of their assessment requirements attendance and contribution is assessed weekly during tutorials and is referred to as assessment Task 7: Tutorial participation and team contribution. |
| 2 | Forming teams | Working on Team project management document. |
| 3 | IT Projects and Project management | Assessment Task 1: Team project management document due. Next key deliverable, Business case is discussed. |
| 4 | Functional requirements | Assessment Task 2: Business case document and requirements due. Next key deliverable, Functional documents are discussed. |
| 5 | Database structures | Working on Functional documents. |
| 6 | IT Projects and Risk management | Assessment Task 3: Functional requirements and design document due. Next key deliverable discussed. |
| 7 | Project testing | Working on Technical documents and user manuals. |
| 8 | Technical documents and user manuals | Working on Technical documents and user manuals. |
| 9 | User Manuals and presentation discussion | Assessment Task 4: Technical documents and user manuals due. Working on next key deliverable. |
| 10 | Developing prototypes | Working on prototype. |
| 11 | Team presentations of Prototype functionality | Assessment Task 5: Presentation of project due. Working on prototype. |
| 12 | Presentation of working prototype | Assessment Task 6: Presentation of working prototype due in tutorial. |
| SWOT VAC | No formal assessment is undertaken in 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 learning system.
Practical work: 100%
| Assessment Task | Value | Due Date |
|---|---|---|
| Team project management document | 5% | Tuesday 13 August 2013 |
| Business case document and requirements | 10% | Tuesday 20 August 2013 |
| Functional requirements and design document | 15% | Tuesday 3 September 2013 |
| Technical documents and user manuals | 25% | Tuesday 24 September 2013 |
| Presentation of project | 10% | Tuesday 15 October 2013 |
| Presentation of working prototype | 25% | Tuesday 22 October 2013 |
| Tutorial participation and contribution | 10% | Weekly during tutorials |
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/
Students will be assessed in tutorials on their contribution within their teams. Contribution is assessed by the supervisor in the tutorial. The supervisor will assess how the student interacts in the project teams and how their contribution is valued by the project team members. This contribution will be on going throughout the semester.
Specific tasks and marking criteria will be distributed at the beginning of the semester.
The criteria for assessing this project management document is to:
Specific tasks and marking criteria will be distributed at the appropriate time.
The criteria for development a business document is:
Project teams are expected to provide requirements in the form of minutes of meetings, and individual timesheets as well as confidential peer reviews. These are assessable items. Students may be individually assessed on the level and standard of their contributions where applicable.
Specific tasks and marking criteria will be distributed at the appropriate time.
The criteria for assessment is to:
Project teams are expected to provide requirements in the form of minutes of meetings, and individual timesheets as well as confidential peer reviews. These are assessable items. Students may be individually assessed on the level and standard of their contributions where applicable.
Specific tasks and marking criteria will be distributed at the appropriate time.
Teams will be assessed on:
Project teams are expected to provide requirements in the form of minutes of meetings, and individual timesheets as well as confidential peer reviews. These are assessable items. Students may be individually assessed on the level and standard of their contributions where applicable.
Specific tasks and marking criteria will be distributed at the appropriate time.
Students are marked on:
Students may be individually assessed on the level and standard of their contributions where applicable.
Specific tasks and marking criteria will be distributed at the appropriate time.
The prototypes will be assessed, by the unit leader and supervisor from a marking criteria designed by the unit leader, at the time project teams present their prototype. Project teams will be given this marking guide closer to the time of their presentation.
Criteria for assessment:
Project teams are expected to provide requirements in the form of minutes of meetings, and individual timesheets as well as confidential peer reviews. These are assessable items. Students may be individually assessed on the level and standard of their contributions where applicable.
Tutorial and group contribution.
To ensure all group members participate in tutorials, students will be allocated a mark out of 10.
This will be assessed over the 12 weeks of the semester.
Yardley, D. (2002) ‘Successful IT Project Delivery’, Addison-Wesley, UK. ISBN 0-201-75606-4
Schwalbe, K. (2004) ‘Information Technology Project Management’, Thomson Course Technology – 3rd (or 4th) Edition. ISBN 0-619-15984-7
Curry, J. & Stanford, P. (2005) ‘Practical System Development: A Project-based Approach’, Pearson SprintPrint, Australia. ISBN 0-7339-7336-1
Monash Library Unit Reading List
http://readinglists.lib.monash.edu/index.html
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.monash.edu.au/exams/special-consideration.html
Assignments in this unit cannot be resubmitted.
Students are required to be aware of the referencing requirements for creating assignments. All assignments in this unit are required to be referenced where a contribution to the assignment has come from a source other than the student themselves.
The following link will provide you with an appropriate array of referencing requirements:
http://www.monash.edu/lls/llonline/quickrefs/19-styles.xml
If you are unsure about the appropriate reference style to use please talk with your supervisor.
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). Please note that it is your responsibility to retain copies of your assessments.
If Electronic Submission has been approved for your unit, please submit your work via the learning system for this unit, which you can access via links in the my.monash portal.
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.
You will need Adobe Acrobat reader to access weekly lecture and class materials. This is freely available from: http://get.adobe.com/uk/reader/
Access to Microsoft Office software (PowerPoint, Word, and Excel) for document preparation. These software programs are available for use in University computer labs.
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: www.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 http://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, resources and programs that enable you to save time and be more effective in your learning and research. Go to 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/.
For more information on Monash’s educational strategy, see:
www.monash.edu.au/about/monash-directions and on student evaluations, see: www.policy.monash.edu/policy-bank/academic/education/quality/student-evaluation-policy.html
Students have found this unit intellectually stimulating, with sufficient resources and support to complete the learning objectives.
Students have found the pace and structure of this unit sufficiently appropriate to complete the tasks required of them in a timely manner.
Students have found this unit extremely helpful in bringing together information from core units. However, they have also indicated they would like to have more help with database design, structure and management. Unfortunately this unit is designed to facilitate the knowledge previously obtained from the core units. To aid students with this dilemma handouts will provide database design etc, and more dedicated tutoring will focus on this issue.
Students did mention issues regarding group involvement and support. To provide teams with the opportunity to communicate team member concerns or issues they are supplied with Confidential Peer Review forms that are completed and given to their supervisor confidentially. This is an opportunity for the supervisor and client to view issues within the team that may not be evident in the weekly tutorial meetings. These forms are an important opportunity for each team member to have their say and to have the information they provide to their supervisor and client acknowledged and assessed. This form when compared to other team members' forms can influence a mark differential for team members.
If you wish to view how previous students rated this unit, please go to
https://emuapps.monash.edu.au/unitevaluations/index.jsp