Note: This unit version is currently being edited and is subject to change!

ISYS3888: Information Systems Project (2020 - Semester 2)

Download UoS Outline

Unit: ISYS3888: Information Systems Project (6 CP)
Mode: Normal-Day
On Offer: Yes
Level: Senior
Faculty/School: School of Computer Science
Unit Coordinator/s: Dr Hasan, M. Rabiul
Session options: Semester 2
Versions for this Unit:
Campus: Camperdown/Darlington
Pre-Requisites: (INFO2110 OR ISYS2110) AND (INFO2120 OR ISYS2120) AND (ISYS2140 OR ISYS2160).
Prohibitions: INFO3600 OR ISYS3207 OR ISYS3400.
Brief Handbook Description: This unit will provide students an opportunity to apply the knowledge and practise the skills acquired in the prerequisite and qualifying units, in the context of a substantial information systems research or development project and to experience in a realistic way many aspects of analysing and solving information systems problems. Since information systems projects are often undertaken by small teams, the experience of working in a team is seen as an important feature of the unit. Students often find it difficult to work effectively with others and will benefit from the opportunity provided by this unit to further develop this skill.
Assumed Knowledge: None.
Lecturer/s: Dr Hasan, M. Rabiul
Timetable: ISYS3888 Timetable
Time Commitment:
# Activity Name Hours per Week Sessions per Week Weeks per Semester
1 Project Work - in class 2.00 1 13
2 Project Work - own time 6.00 1 13
3 Site Visit 1.00 1 13
4 Independent Study 2.00 1 13
5 Meeting 1.00 1 13
T&L Activities: Project Work - own time: Team or individual work

Site Visit: Meeting with project sponsor

Independent Study: Individual investigation and research

Meeting: Team meeting and discussion

Learning outcomes are the key abilities and knowledge that will be assessed in this unit. They are listed according to the course goal supported by each. See Assessment Tab for details how each outcome is assessed.

(7) Project and Team Skills (Level 3)
1. Communicate project success/failure and personal contribution to the project
2. Present complex ideas to relatively large audience
3. Work as a team to develop an IT solution to the sponsor thru team work.
(4) Design (Level 3)
4. Translate user's business requirements into specifications.
5. Design IT solution and develop prototype.
Assessment Methods:
# Name Group Weight Due Week Outcomes
1 Project Plan Yes 10.00 Week 3 4,
2 Proposal Yes 10.00 Week 5 4,
3 Presentation/Seminar Yes 10.00 Week 11 2,
4 Report Yes 30.00 Week 11 3,
5 Participation No 10.00 Multiple Weeks 2,
6 Progress Report (Presentation) No 10.00 Multiple Weeks 2,
7 Final Exam (Oral) No 20.00 Week 13 1,
Assessment Description: Project Plan: A document to guide the project

Proposal: Project Proposal

Progress Report: Weekly progress report presentation

Participation: Individual participation

Report: Final prototype and report

Presentation/Seminar: Group Presentation

Final Exam: Individual Oral Exam

Grade Type Description
Standards Based Assessment Final grades in this unit are awarded at levels of HD for High Distinction, DI (previously D) for Distinction, CR for Credit, PS (previously P) for Pass and FA (previously F) for Fail as defined by University of Sydney Assessment Policy. Details of the Assessment Policy are available on the Policies website at . Standards for grades in individual assessment tasks and the summative method for obtaining a final mark in the unit will be set out in a marking guide supplied by the unit coordinator.
Minimum Pass Requirement It is a policy of the School of Computer Science that in order to pass this unit, a student must achieve at least 40% in the written examination. For subjects without a final exam, the 40% minimum requirement applies to the corresponding major assessment component specified by the lecturer. A student must also achieve an overall final mark of 50 or more. Any student not meeting these requirements may be given a maximum final mark of no more than 45 regardless of their average.
Policies & Procedures: IMPORTANT: School policy relating to Academic Dishonesty and Plagiarism.

In assessing a piece of submitted work, the School of Computer Science may reproduce it entirely, may provide a copy to another member of faculty, and/or to an external plagiarism checking service or in-house computer program and may also maintain a copy of the assignment for future checking purposes and/or allow an external service to do so.

Other policies

See the policies page of the faculty website at for information regarding university policies and local provisions and procedures within the Faculty of Engineering and Information Technologies.
Recommended Reference/s: Note: References are provided for guidance purposes only. Students are advised to consult these books in the university library. Purchase is not required.

Note that the "Weeks" referred to in this Schedule are those of the official university semester calendar

Week Description
Week 1 Finalising Projects, Teams and Supervisors
Week 2 Problem exploration: strategies, methods, difficulties, good and bad experiences, outcomes.
Week 3 Defining the Project: key issues, focus, exact formulation, objectives, team acceptance, approval.
Assessment Due: Project Plan
Week 4 Deciding on a Methodology: using the literature, tools, techniques and technologies, selection criteria, evaluation.
Week 5 Confirmation of Project Proposal: selling the idea, negotiation, compromise, agreement, signing off.
Assessment Due: Proposal
Week 6 Development: specifics of the task - what, how, problems encountered, strategies adopted, execution, selection of tool/resources.
Data Collection and Analysis/ Prototype
Week 7 Progress and Findings: progress, literature cited & evaluation, products/tools selected & why, research/ development strategies, methods of recording/documenting.
Week 8 Team Dynamics & the Group Culture: team work, strategies, problems, solutions, making se of individuals, team culture, comparison with theory.
Week 9 Testing and Evaluation: identifying targets, determining performance/ satisfaction measures, test scenarios/ research evaluation, testing strategies
Week 10 Achievement of Objectives: measuring success, gauging client/user satisfaction, evaluating benefits to client, next step for the client, project review.
Week 11 Group Presentations
Assessment Due: Presentation/Seminar
Assessment Due: Report
Week 12 Group Presentations
Week 13 Finalist Presentations
Assessment Due: Final Exam (Oral)

Course Relations

The following is a list of courses which have added this Unit to their structure.

Course Year(s) Offered
Bachelor of Advanced Computing (Information Systems Major) 2018, 2019, 2020
Bachelor of Advanced Computing/Bachelor of Commerce 2018, 2019, 2020
Bachelor of Advanced Computing/Bachelor of Science 2018, 2019, 2020
Bachelor of Advanced Computing/Bachelor of Science (Health) 2018, 2019, 2020
Bachelor of Advanced Computing/Bachelor of Science (Medical Science) 2018, 2019, 2020
Bachelor of Advanced Computing (Computational Data Science) 2018, 2019, 2020
Bachelor of Advanced Computing (Computer Science Major) 2018, 2019, 2020
Bachelor of Advanced Computing (Software Development) 2018, 2019, 2020
Biomedical Mid-Year 2018, 2019, 2020
Biomedical 2016, 2017, 2018, 2019, 2020
Software Mid-Year 2021
Software 2020, 2021
Bachelor of Information Technology 2017
Bachelor of Information Technology/Bachelor of Arts 2017
Bachelor of Information Technology/Bachelor of Commerce 2017
Bachelor of Information Technology/Bachelor of Medical Science 2017
Bachelor of Information Technology/Bachelor of Science 2017
Bachelor of Information Technology/Bachelor of Laws 2017

Course Goals

This unit contributes to the achievement of the following course goals:

Attribute Practiced Assessed
(7) Project and Team Skills (Level 3) No 80%
(8) Professional Effectiveness and Ethical Conduct (Level 3) No 0%
(5) Interdisciplinary, Inclusiveness, Influence (Level 3) No 0%
(4) Design (Level 3) No 20%
(2) Engineering/ IT Specialisation (Level 3) No 0%
(3) Problem Solving and Inventiveness (Level 3) No 0%
(1) Maths/ Science Methods and Tools (Level 3) No 0%

These goals are selected from Engineering & IT Graduate Outcomes Table 2018 which defines overall goals for courses where this unit is primarily offered. See Engineering & IT Graduate Outcomes Table 2018 for details of the attributes and levels to be developed in the course as a whole. Percentage figures alongside each course goal provide a rough indication of their relative weighting in assessment for this unit. Note that not all goals are necessarily part of assessment. Some may be more about practice activity. See Learning outcomes for details of what is assessed in relation to each goal and Assessment for details of how the outcome is assessed. See Attributes for details of practice provided for each goal.