COIT20248 - Information Systems Analysis and Design

General Information

Unit Synopsis

Information systems analysis and design is a complex, challenging, and stimulating organisational process, that a team of business and systems professionals use to develop and maintain computer-based information systems. In this unit, you will learn the importance of responding to and anticipating problems through the innovative use of systems development process. You will learn how understanding user-centered design and task-centered design are fundamental to good systems design. In order to understand these concepts, you will study how to determine user-requirements and convert user requirements to system design. You will demonstrate this understanding by designing web-interfaces of given case studies and practical examples. You will study different phases of the systems development life cycle, which includes developing a system proposal, determining user requirements, designing a system, and applying key principles to the implementation of a system. You will also explore the organisational context and the iterative nature of systems analysis and design.

Details

Level Postgraduate
Unit Level 8
Credit Points 6
Student Contribution Band SCA Band 2
Fraction of Full-Time Student Load 0.125
Pre-requisites or Co-requisites

Anti-requisites: COIS20025 Systems Development Overview. Students who have studied COIS20025 in the past cannot take COIT20248.

Important note: Students enrolled in a subsequent unit who failed their pre-requisite unit, should drop the subsequent unit before the census date or within 10 working days of Fail grade notification. Students who do not drop the unit in this timeframe cannot later drop the unit without academic and financial liability. See details in the Assessment Policy and Procedure (Higher Education Coursework).

Class Timetable View Unit Timetable
Residential School No Residential School

Unit Availabilities from Term 2 - 2024

Term 2 - 2024 Profile
Brisbane
Melbourne
Online
Rockhampton
Sydney
Term 3 - 2024 Profile
Brisbane
Melbourne
Online
Sydney

Attendance Requirements

All on-campus students are expected to attend scheduled classes – in some units, these classes are identified as a mandatory (pass/fail) component and attendance is compulsory. International students, on a student visa, must maintain a full time study load and meet both attendance and academic progress requirements in each study period (satisfactory attendance for International students is defined as maintaining at least an 80% attendance record).

Assessment Overview

Recommended Student Time Commitment

Each 6-credit Postgraduate unit at CQUniversity requires an overall time commitment of an average of 12.5 hours of study per week, making a total of 150 hours for the unit.

Assessment Tasks

This information will not be available until 8 weeks before term.
To see assessment details from an earlier availability, please search via a previous term.

This is a graded unit: your overall grade will be calculated from the marks or grades for each assessment task, based on the relative weightings shown in the table above. You must obtain an overall mark for the unit of at least 50%, or an overall grade of ‘pass’ in order to pass the unit. If any ‘pass/fail’ tasks are shown in the table above they must also be completed successfully (‘pass’ grade). You must also meet any minimum mark requirements specified for a particular assessment task, as detailed in the ‘assessment task’ section (note that in some instances, the minimum mark for a task may be greater than 50%).

Consult the University’s Grades and Results Policy for more details of interim results and final grades

Past Exams

To view Past Exams,
please login
Previous Feedback

Term 1 - 2022 : The overall satisfaction for students in the last offering of this course was 78.95% (`Agree` and `Strongly Agree` responses), based on a 19.39% response rate.

Feedback, Recommendations and Responses

Every unit is reviewed for enhancement each year. At the most recent review, the following staff and student feedback items were identified and recommendations were made.

Source: Unit Coordinator reflections
Feedback
The time allocated to some topics (e.g. Agile) is too short to cover in sufficient depth.
Recommendation
Re-arrange the ordering of some topics (e.g. bring Agile earlier) and remove some content covered in later units (e.g. details of database design).
Action Taken
The Database design and Data Warehousing topics were replaced with a topic dedicated to Agile methodology.
Source: Unit Coordinator reflections
Feedback
It is difficult for students to appreciate the importance of writing unambiguous requirements for systems.
Recommendation
Introduce a tutorial activity with peer review of requirements tasks, e.g. one team creates a requirements specification, which another team uses an input to create a design.
Action Taken
Requirements specification is one of the early topics in the term, but student teams were formed later in the term. Hence a different approach was taken. In this approach, students were given relatively vague descriptions of assignment requirements, where they needed to clarify the information in order to archive accurate requirements specifications.
Source: Student Feedback
Feedback
Some students found the open-ended nature of the assignments challenging.
Recommendation
The nature of the open-ended descriptions of assignment requirements must be clearly communicated to the students in the assignment description to avoid possible confusion.
Action Taken
Nil.
Source: Unit Coordinator
Feedback
Most of the content is based on one textbook, so students that do not connect with the textbook approach can find the content difficult.
Recommendation
Introduce more diverse content resources, for example, industry use cases.
Action Taken
Nil.
Unit learning Outcomes
This information will not be available until 8 weeks before term.
To see Learning Outcomes from an earlier availability, please search via a previous term.