1996 Swinburne Higher Education Handbook

e.
IT906 Human-Computer Interaction
(HCI)
12.5 credit points *2 hours per wek
Instruction: combination of lectures, seminars and laboratory
sessions Assessment: two assignments and afinal examination
This is a subject in the Master of Information Technology.
Objectives
To appreciate the need for, and the role and characteristics
of, himan-computer interaction.
Content
Introduction points of view, scope and objectives of HCI,
metamodels of HCI; HCI technology human-machine fit
and adaptation, the user interface useability and its
components, input/output devices, interface objects,
dialogue styles, genre, architecture, enhanced/adaptive
interaction; HCI theory: modelling psychological
foundations of user interfaces, types of uses, human
information processing, language, communication and
interaction, formal models, cognitive models, social models,
ergonomic models, applications; HCI research methods
experiments and experimental design, measurement in the
behavioural sciences, data collection methods, data analysis
methods; HCI application: organisational impact; HCI
future developments.
Textbooks
To be advised.
"; IT91 1 Software Process 2
12.5 credit points 2 hours per week Hawthorn
Prerequisite: ID01 Sofware Pmcess 1 Assessment:
tests, laboratory work, arnarngnmmts andjnal examination
This is a subject in the Master of Information Technology.
Objectives
The subject continues to explore issues raised in IT901
Software Process I, adding the objectives:
To study the process management issues which span
projects which undertake to engineer large-scale
software systems. Special emphasis is given to issues
surrounding the management of software development
within the object-oriented paradigm
*To study software engineering environments, providing
students with experience working in select
environments
Content
Part 3: Process Management Issues (Peopleware;
Risk Management; Software Standards; Software Metrics;
Software Configuration Management; Software Quality
Management).
Part 4: Software Engineering Environments (including
laboratory experience).
Recommended Reading
Boehm, B.W. Software Risk Management, IEEE Computer
Society
DeMarco, T. and Lister T., Peopleware, Dorset House
Fenton, N.E., Software Metrics, Chapman & Hall
Fenton, N.E. Software Quality Assurance and Measurement,
Chaprnan & Hall
Hurnphrey, W.S. Managing the Software Process. Addison-Wesley.
Yourdon, E.'Decline and Fall of the American Programmer,
Yourdon Press
IT91 2 Project Management
12.5 credit points 2 hours per week Hawthorn
Instruction: lectures and tutorials Assessment: Grou~
project and individual assignments
A subject in the Information Technology Management cluster
of the Master of Information Technology. It is expected that
students taking the cluster will have completed a first course
in computing and will have had some exposure to the
organisational aspects of systems development.
Objectives
Develop students' understanding of the managment of
the software development process and of the factors that
contribute to project success and failure;
- ,
Develop students' ability to apply formal planning and
control methods including software metrics to the
development of quality software;
an appreciation of some current project management
tools and techniques, including risk management.
Content
The subject is approached from the perspective of the
management of the software development process and both
successful and failed projects are analysed to determine the
factors that influence project outcome. Specific topics
include estimation, project planning and control, product
and process metrics, quality and productivity,
implementation, project management tools and
methodologies. . .. . The management of risk provides an
underpining theme.
Recommended Readina
Gilb T., Principles of Software Engineering Management, Addison-
Wesley, 1988
Humphrey W. S. , Managing the Software Process, SE1 Series in
Software Engineering, Addison Wesley Publishing Co., 1990
Jones C., Applied Software Measurement, McGraw Hill Inc., New
York, 1991
Reifer D. J., Sofware Management, 4th Edition, IEEE Computer
Society Press, 1993
Sauer C., Why Information Systems Fail: A Case Study Approach,
Information Systems Series, Alfred Waller Ltd., Henley on
Thames, UK, 1993
IT91 3 Automated Systems Development
Project
50 credit points 4 hours per week for two semesters
Hawthorn Corequisites: IT954 Information Systems
Requirements, IT974 Systems Strategies, IT984 Automated
Development Methods, 1'1994 Information System Dynamics,
First or second year cluster in the Master of Information
Technology Assessment: by deliverable items (requirements
and specification documents, system and user manuals, the
working system itself; and an evaluation of its effectiveness in
satishing the requirements.
Objectives
To gain experience of the automated systems
development process.
To develop an information system.