CQUniversity Unit Profile
COIT11226 Systems Analysis
Systems Analysis
All details in this unit profile for COIT11226 have been officially approved by CQUniversity and represent a learning partnership between the University and you (our student).
The information will not be changed unless absolutely necessary and any change will be clearly indicated by an approved correction included in the profile.
General Information

Overview

This unit develops skills in the planning, selection and analysis phases of the systems development lifecycle (SDLC). Topics include feasibility studies, fact finding techniques, system modelling, project planning and user requirements.

Details

Career Level: Undergraduate
Unit Level: Level 1
Credit Points: 6
Student Contribution Band: 8
Fraction of Full-Time Student Load: 0.125

Pre-requisites or Co-requisites

There are no requisites for this unit.

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).

Offerings For Term 2 - 2017

Adelaide
Brisbane
Cairns
Distance
Melbourne
Rockhampton
Sydney
Townsville

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).

Class and Assessment Overview

Recommended Student Time Commitment

Each 6-credit Undergraduate 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.

Class Timetable

Bundaberg, Cairns, Emerald, Gladstone, Mackay, Rockhampton, Townsville
Adelaide, Brisbane, Melbourne, Perth, Sydney

Assessment Overview

1. Written Assessment
Weighting: 20%
2. Practical and Written Assessment
Weighting: 40%
3. Examination
Weighting: 40%

Assessment Grading

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.

Previous Student Feedback

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.

Feedback from email

Feedback

More tutorial questions to discuss

Recommendation

MoreTutorial questions should be discussed

Feedback from Email and forum

Feedback

Flex students require MS Project Access

Recommendation

One year free subscription is now available. Students can download it from the Web. This should be written in the course website

Unit Learning Outcomes
On successful completion of this unit, you will be able to:
  1. Describe, discuss and apply systems analysis techniques.
  2. Apply fact-finding techniques in the analysis phase of the SDLC.
  3. Model the existing system/environment using appropriate techniques.
  4. Document the analysis phase of the SDLC by preparing analysis and user requirements reports.

Australian Computer Society (ACS) recognises the Skills Framework for the Information Age (SFIA). SFIA is in use in over 100 countries and provides a widely used and consistent definition of ICT skills. SFIA is increasingly being used when developing job descriptions and role profiles.

ACS members can use the tool MySFIA to build a skills profile at https://www.acs.org.au/professionalrecognition/mysfia-b2c.html

This unit contributes to the following workplace skills as defined by SFIA. The SFIA code is included:

  • Information Analysis (INAN)
  • Business Analysis (BUAN)
  • Data Analysis (DTAN)
  • Systems Design (DESN)
  • Database/Repository Design (DBDS)
  • Testing (TEST)

Alignment of Learning Outcomes, Assessment and Graduate Attributes
N/A Level
Introductory Level
Intermediate Level
Graduate Level
Professional Level
Advanced Level

Alignment of Assessment Tasks to Learning Outcomes

Assessment Tasks Learning Outcomes
1 2 3 4
1 - Written Assessment - 20%
2 - Practical and Written Assessment - 40%
3 - Examination - 40%

Alignment of Graduate Attributes to Learning Outcomes

Graduate Attributes Learning Outcomes
1 2 3 4
1 - Communication
2 - Problem Solving
3 - Critical Thinking
4 - Information Literacy
5 - Team Work
6 - Information Technology Competence
7 - Cross Cultural Competence
8 - Ethical practice
9 - Social Innovation
10 - Aboriginal and Torres Strait Islander Cultures

Alignment of Assessment Tasks to Graduate Attributes

Assessment Tasks Graduate Attributes
1 2 3 4 5 6 7 8 9 10
1 - Written Assessment - 20%
2 - Practical and Written Assessment - 40%
3 - Examination - 40%
Textbooks and Resources

Textbooks

Prescribed

Systems Analysis and Design in a Changing World

Seventh Edition (2015)
Authors: John Satzinger,Robert Jackson,Stephen Burd
CENGAGE Learning
Boston Boston , MA , USA
ISBN: ISBN-13: 9781305117204
Binding: Hardcover

IT Resources

You will need access to the following IT resources:
  • CQUniversity Student Email
  • Internet
  • Unit Website (Moodle)
  • Microsoft Project
  • Microsoft Visio (or similar)
Referencing Style

All submissions for this unit must use the referencing style: Harvard (author-date)

For further information, see the Assessment Tasks.

Teaching Contacts
Lisa Soon Unit Coordinator
l.soon@cqu.edu.au
Schedule
Week 1 Begin Date: 10 Jul 2017

Module/Topic

From Beginning to End: An Overview of Systems Analysis and Design





Chapter

Chapter 1





Events and Submissions/Topic






Week 2 Begin Date: 17 Jul 2017

Module/Topic

Approaches to system development.





Chapter

Chapter 10





Events and Submissions/Topic






Week 3 Begin Date: 24 Jul 2017

Module/Topic

The Role of the Systems Analyst.





Chapter

Online chapter A





Events and Submissions/Topic






Week 4 Begin Date: 31 Jul 2017

Module/Topic

Project Planning and Project Management





Chapter

Chapter 11





Events and Submissions/Topic






Week 5 Begin Date: 07 Aug 2017

Module/Topic

Project Management Techniques





Chapter

Online Chapter C







Events and Submissions/Topic






Vacation Week Begin Date: 14 Aug 2017

Module/Topic






Chapter






Events and Submissions/Topic






Week 6 Begin Date: 21 Aug 2017

Module/Topic

Investigating System Requirements





Chapter

Chapter 2





Events and Submissions/Topic

Written Assessment Due: Week 6 Monday (21 Aug 2017) 9:00 am AEST
Week 7 Begin Date: 28 Aug 2017

Module/Topic

Identifying User Stories and Use Cases





Chapter

Chapter 3





Events and Submissions/Topic






Week 8 Begin Date: 04 Sep 2017

Module/Topic

Domain Modelling





Chapter

Chapter 4





Events and Submissions/Topic






Week 9 Begin Date: 11 Sep 2017

Module/Topic

Use Case Modelling





Chapter

Chapter 5





Events and Submissions/Topic






Week 10 Begin Date: 18 Sep 2017

Module/Topic

Designing the User Interface





Chapter

Chapter 8





Events and Submissions/Topic

Practical and Written Assessment Due: Week 10 Wednesday (20 Sept 2017) 9:00 am AEST
Week 11 Begin Date: 25 Sep 2017

Module/Topic

Deploying the New System





Chapter

Chapter 14





Events and Submissions/Topic






Week 12 Begin Date: 02 Oct 2017

Module/Topic

Revision





Chapter

All covered unit materials including all chapters above.







Events and Submissions/Topic

Exam Preparation (Exam: 40%)





Review/Exam Week Begin Date: 09 Oct 2017

Module/Topic

Chapter

Events and Submissions/Topic

Exam Week Begin Date: 16 Oct 2017

Module/Topic






Chapter






Events and Submissions/Topic






Term Specific Information

Unit Coordinator: Dr Lisa Soon
Office Location: Level 1, 538 Flinders Street West Townsville QLD 4810
Phone: +61 07 4726 5317 Ext 55317
Emai: l.soon@cqu.edu.au
Note: For all inquiries, please send me an email. For urgent matter, phone me whenever needed. if unavailable, please leave a voice message or email me.

Assessment Tasks

1 Written Assessment

Assessment Title
Written Assessment

Task Description

Title

System Development and Planning

Description

An individual assessment that requires you to answer questions on early stages of systems development, including how you approach systems development and how you deal with project planning activities. There will be multiple questions on different topics, and you will be expected to submit a report containing answers. You will be required to use software, such as Microsoft Excel and Microsoft Project, to answer some questions. See Moodle for the questions and expected written assessment format.


Assessment Due Date

Week 6 Monday (21 Aug 2017) 9:00 am AEST

Please submit all assessments online through Moodle. Late submissions are subject to the university late submission penalty.


Return Date to Students

Monday (4 Sept 2017)

Assessments will be returned through Moodle. Late submissions with or without extension approvals will be returned after the above date.


Weighting
20%

Assessment Criteria

This assessment consists of multiple questions, each marked separately. The criteria for marking each question are:

  • Correctness: the answer should be technically correct, not contain errors; justifications should explain the correct advantages and benefits, while also touch on disadvantages.
  • Clarity: explanations, formatting and diagrams should be clear, consistent and relevant.

See Moodle for detailed marking allocation.


Referencing Style

Submission
Online

Learning Outcomes Assessed
  • Describe, discuss and apply systems analysis techniques.


Graduate Attributes
  • Communication
  • Critical Thinking
  • Information Literacy
  • Ethical practice

2 Practical and Written Assessment

Assessment Title
Practical and Written Assessment

Task Description

Title

System Analysis: Techniques and Models

Description

An individual assessment that requires you to apply techniques and models to complete tasks in systems development, specifically during systems analysis . Techniques in this assessment refers to information gathering techniques. You will need to select, justify or use different techniques to identify, analyse and specify requirements. Models may include use cases, domain class models, activity diagrams, system sequence diagrams, and others. There will be multiple questions on different topics, and you will be expected to submit a written assessment containing answers containing model diagrams. You will be required to use software, such as Microsoft Visio, to answer some questions.



Assessment Due Date

Week 10 Wednesday (20 Sept 2017) 9:00 am AEST

Please submit all assessments online through Moodle. Late submissions are subject to the university late submission penalty policy.


Return Date to Students

Week 12 Wednesday (4 Oct 2017)

Any student who submits an assessment late with or without an assignment extension approval will receive the returned assignment later than the above date.


Weighting
40%

Assessment Criteria

This assessment consists of multiple questions, each marked separately. The criteria for marking each question are:
  • Correctness: the answer should be technically correct, not contain errors; justifications should explain the correct advantages and benefits, while also touch on disadvantages.
  • Clarity: explanations, formatting and diagrams should be clear, consistent and relevant.

See Moodle for detailed marking allocation.



Referencing Style

Submission
Online

Submission Instructions
All assignments must be submitted online via Moodle.

Learning Outcomes Assessed
  • Describe, discuss and apply systems analysis techniques.
  • Apply fact-finding techniques in the analysis phase of the SDLC.
  • Model the existing system/environment using appropriate techniques.
  • Document the analysis phase of the SDLC by preparing analysis and user requirements reports.


Graduate Attributes
  • Communication
  • Problem Solving
  • Critical Thinking
  • Information Technology Competence
  • Ethical practice

Examination

Outline
Complete an invigilated examination

Date
During the examination period at a CQUniversity examination centre

Weighting
40%

Length
180 minutes

Exam Conditions
Closed Book

Materials
No calculators permitted
Dictionary - non-electronic, concise, direct translation only (dictionary must not contain any notes or comments).
Academic Integrity Statement

As a CQUniversity student you are expected to act honestly in all aspects of your academic work.

Any assessable work undertaken or submitted for review or assessment must be your own work. Assessable work is any type of work you do to meet the assessment requirements in the unit, including draft work submitted for review and feedback and final work to be assessed.

When you use the ideas, words or data of others in your assessment, you must thoroughly and clearly acknowledge the source of this information by using the correct referencing style for your unit. Using others’ work without proper acknowledgement may be considered a form of intellectual dishonesty.

Participating honestly, respectfully, responsibly, and fairly in your university study ensures the CQUniversity qualification you earn will be valued as a true indication of your individual academic achievement and will continue to receive the respect and recognition it deserves.

As a student, you are responsible for reading and following CQUniversity’s policies, including the Student Academic Integrity Policy and Procedure. This policy sets out CQUniversity’s expectations of you to act with integrity, examples of academic integrity breaches to avoid, the processes used to address alleged breaches of academic integrity, and potential penalties.

What is a breach of academic integrity?

A breach of academic integrity includes but is not limited to plagiarism, self-plagiarism, collusion, cheating, contract cheating, and academic misconduct. The Student Academic Integrity Policy and Procedure defines what these terms mean and gives examples.

Why is academic integrity important?

A breach of academic integrity may result in one or more penalties, including suspension or even expulsion from the University. It can also have negative implications for student visas and future enrolment at CQUniversity or elsewhere. Students who engage in contract cheating also risk being blackmailed by contract cheating services.

Where can I get assistance?

For academic advice and guidance, the Academic Learning Centre (ALC) can support you in becoming confident in completing assessments with integrity and of high standard.

What can you do to act with integrity?