ITC211 Systems Analysis (8)

Systems analysis provides students with knowledge and skills in: feasibility analysis; requirements gathering; requirements writing; and requirements modelling of business problems and systems. Object oriented and structured modelling techniques are a major part of the subject content.

Availability

Session 1 (30)
On Campus
CSU Study Centre Sydney
Session 2 (60)
On Campus
Albury-Wodonga Campus
Bathurst Campus
CSU Study Centre Melbourne
CSU Study Centre Sydney
Wagga Wagga Campus
Online
Wagga Wagga Campus
Session 3 (90)
On Campus
CSU Study Centre Sydney

Continuing students should consult the SAL for current offering details: ITC211. Where differences exist between the Handbook and the SAL, the SAL should be taken as containing the correct subject offering details.

Subject Information

Grading System

HD/FL

Duration

One session

School

School of Computing and Mathematics

Enrolment Restrictions

Available to undergraduate students only.

Not available to students who have completed ITC412 or ITC548

Assumed Knowledge
ITC106 or ITC114
Incompatible Subjects

ITC412, ITC548

Learning Outcomes

Upon successful completion of this subject, students should:
  • be able to describe the context of an information system;
  • be able to discuss and describe processes to systems analysis;
  • be able to compare the range of requirements gathering techniques;
  • be able to describe and apply feasibility study methods and approaches;
  • be able to develop system requirements models;
  • be able to demonstrate the ability to use the tools and techniques of object oriented and structured systems modelling.

Syllabus

This subject will cover the following topics:
  • Introduction to information systems.
  • Approaches to system analysis (object oriented and structured).
  • Processes to systems analysis (i.e. system development life cycle, iterative, Rational Unified Process).
  • Problem definition.
  • Feasibility analysis.
  • Requirements gathering.
  • Requirements specification (i.e. functional and nonfunctional).
  • Events, use cases and test cases.
  • System requirements models (i.e. analysis of class diagrams and data flow diagrams).
  • Unified Modeling Language (UML) and case tools.

The information contained in the CSU Handbook was accurate at the date of publication: January 2020. The University reserves the right to vary the information at any time without notice.

Back