Skip to content | Change text size

M O N A T A R

InfoTech Unit Avatar

FIT3097 Enterprise integration

Chief Examiner

This field records the Chief Examiner for unit approval purposes. It does not publish, and can only be edited by Faculty Office staff

To update the published Chief Examiner, you will need to update the Faculty Information/Contact Person field below.

NB: This view restricted to entries modified on or after 19990401000000

Unit Code, Name, Abbreviation

FIT3097 Enterprise integration (22 May 2006, 4:24pm) [EntInt (22 May 2006, 3:02pm)]

Reasons for Introduction

Reasons for Introduction (22 May 2006, 3:13pm)

This unit is a third year component of the Information Systems major in the BITS. This unit will give students an understanding of the inter-relationship of the systems in a portfolio of information systems that are needed to support a large organization. It will examine the forms and mechanisms of business process integration and of data integration between the Enterprise System and other business information systems and databases. The unit will introduce the issues of integration types associated with the different software and database technologies. The role of integration middleware software in the specification of business process workflows is addressed in both the homogenous environments of an ERP package and heterogenous environments involving ERP packages, legacy systems and office systems.

Reasons for Change (19 May 2006, 1:27pm)

FIT3097 Enterprise Systems is a new unit for offer from 2007.

Role of Unit (22 May 2006, 3:17pm)

Enterprise scale software systems are used extensively by organisations in which graduates are likely to find employment. Enterprise Integration will acquaint students with the types and mechanisms of integration that they are likely to encounter in their professional practice.

Relationship of Unit (19 May 2006, 1:31pm)

A core unit of the Information Systems specialisation in the BITS.

Relevance of Unit (22 May 2006, 3:21pm)

A significant career pathway for IS major students is into global, national and local companies, and substantial government departments. Information systems support for the business process is the focus of IT activity in such organisations. Designing and supporting business process integration through applications and databases linked by middleware software is a significant concern for the professional systems analyst.

Objectives

Statement of Objectives (22 May 2006, 3:31pm)

Enterprise Integration has the overall objective of preparing IS major students for professional practice as systems analysts in corporate environments that implement complex workflow solutions for day to day business processes. The principal objective is to enable the students to hold informed discussions with both the business users and the software implementers about the software tools available to technically deliver the required business functionality.

Knowledge and Understanding (Cognitive Domain Objectives) (22 May 2006, 3:27pm)

Cognitive Domain Objectives At the completion of the unit students will have knowledge of:

and have an understanding of:

Attitudes, Values and Beliefs (Affective Domain Objectives) (22 May 2006, 3:39pm)

Affective Domain Objectives.

At the completion of the unit the student will have had the opportunity to develop appreciations of:

the business users' requirements for particular information flows and processes in the conduct of normal business activities;

the IT professionals' technological imperitives and constraints in meeting user requirements;

organisational cultures and value judgements that guide the negotiation of trade-offs between the two positions above.

Practical Skills (Psychomotor Domain Objectives) (22 May 2006, 3:42pm)

Psychomotor Domain Objectives.

At the completion of the unit students will be able to:

Relationships, Communication and TeamWork (Social Domain Objectives) (22 May 2006, 3:44pm)

Social Domain Objectives.

At the completion of the unit the student will have had the opportunity to lead and/or engage in team developed solutions to integration problems.

Unit Content

Summary (22 May 2006, 5:23pm)

This unit will give students an understanding of the portfolio of information systems needed to support a large organization and identify Enterprise System (ERP) scale packages as the principal business information system in large organisations. It will examine the forms and mechanisms of business process integration and data integration between the Enterprise System and other business information systems, including legacy systems and office systems. It will introduce students to the concepts of workflow and to selected software tools for process modelling, workflow design and to the different types of integration middleware software and technologies that enables business process integration. ASCED: 020305

Handbook Summary (22 May 2006, 3:52pm)

This unit will give students an understanding of the portfolio of information systems needed to support a large organization and identify Enterprise System (ERP) scale packages as the principal business information system in large organisations. It will examine the forms and mechanisms of business process integration and data integration between the Enterprise System and other business information systems, including legacy systems and office systems. It will introduce students to the concepts of workflow and to selected software tools for process modelling, workflow design and to the different types of integration middleware software that enables business process integration.

Recommended Reading (22 May 2006, 3:55pm)

Britton & Bye (2004) IT Architectures and Middleware. 2e. Addison-Wesley.

O'Rourke, Fishman & Selkow (2003) Enterprise Architecture: Using the Zachman Framework. Thomson-Course Technology.

Hohpe & Woolf (2004) Enterprise Integration Patterns. Addison-Wesley.

Teaching Methods

Mode (22 May 2006, 3:57pm)

On campus.

Strategies of Teaching (22 May 2006, 3:58pm)

2 hour lecture plus 2 hours laboratory exercise and tutorial discussions per week.

Teaching Methods Relationship to Objectives (22 May 2006, 3:59pm)

Knowledge and understanding objectives are achieved mainly through lectures and tutorial and laboratory exercises.

Attitudes and beliefs objectives are achieved mainly through tutorial exercises and assignment work.

Practical skills objectives are achieved mainly through laboratory exercises and assignment work.

Relationships, communication and team work objectives are achieved mainly through tutorial and laboratory exercises and assignment work.

Assessment

Strategies of Assessment (22 May 2006, 4:01pm)

Examination 60% and practical assignments 40%.

Assessment Relationship to Objectives (22 May 2006, 4:02pm)

Knowledge and understanding objectives are assessed mainly through the examination.

Attitudes, values and belief objectives are assessed mainly through the examination and assignment work.

Practical skills objectives are assessed mainly through assignment work.

Relationships, communication and team work objectives are assessed mainly through assignment work.

Workloads

Workload Requirement (22 May 2006, 4:05pm)

Approximately 12 hours per week apportioned as 4 hours contact time in lectures and tutorials or laboratory sessions, 4 hours preparation for lectures and practical sessions and 4 hours research, assignment preparation and revision for examination.

Resource Requirements

Lecture Requirements (19 May 2006, 3:18pm)

Lecture theatre with electronic display facilities and internet connection.

Tutorial Requirements (22 May 2006, 4:06pm)

Combination of tutorial room and PC laboratory, or Studio space.

Laboratory Requirements (22 May 2006, 4:07pm)

Combination of tutorial room and PC laboratory, or Studio space.

Staff Requirements (22 May 2006, 4:08pm)

One lecturer, and one tutor per tutorial group of 16 to 20 students.

Software Requirements (19 May 2006, 3:22pm)

Process modelling software and middleware software to be advised.

Library Requirements (22 May 2006, 4:17pm)

Reserve Collection copies of the required text books at the Library's standard rate of copies for cohort size.

Access to indexed databases of Information Systems and Information Technology peer-reviewed journal articles such as Business Source Premier, ACM Digital Library and IEEE Xplore.

Teaching Responsibility (Callista Entry) (19 May 2006, 3:22pm)

100% Caulfield School of IT

Interfaculty Involvement (22 May 2006, 5:24pm)

Not Applicable

Interschool Involvement (22 May 2006, 5:25pm)

Not Applicable

Other Resource Requirements (22 May 2006, 5:25pm)

Not Applicable

Prerequisites

Prerequisite Units (22 May 2006, 5:25pm)

none

Corequisites (22 May 2006, 5:26pm)

Not Applicable

Prohibitions (22 May 2006, 4:21pm)

None

Alias Titles (22 May 2006, 5:26pm)

Not Applicable

Level (19 May 2006, 3:28pm)

Level 3

Proposed year of Introduction (for new units) (22 May 2006, 4:21pm)

Semester 1, 2007

Frequency of Offering (19 May 2006, 3:30pm)

Semester 1, semester 2 and summer semester as required.

Enrolment (22 May 2006, 5:28pm)

up to 100

Location of Offering (19 May 2006, 3:30pm)

Caulfield campus.

Faculty Information

Proposer

Andrew Barnden

Approvals

School: 24 May 2006 (Geraldine DCosta)
Faculty Education Committee:
Faculty Board:
ADT:
Faculty Manager:
Dean's Advisory Council:
Other:

Version History

19 May 2006 Andrew Barnden Initial Draft; modified UnitName; modified Abbreviation; modified ReasonsForIntroduction/RIntro; modified ReasonsForIntroduction/RChange; modified ReasonsForIntroduction/RRole; modified ReasonsForIntroduction/RRelation; modified Classification; modified Classification
19 May 2006 Andrew Barnden modified ReasonsForIntroduction/RRelevance; modified UnitContent/Summary; modified ReasonsForIntroduction/RRelevance; modified UnitContent/HandbookSummary; modified UnitContent/RecommendedReading; modified UnitContent/RecommendedReading; modified UnitObjectives/ObjText; modified UnitContent/RecommendedReading; modified UnitContent/RecommendedReading; modified Teaching/Mode; modified Assessment/Strategies; modified ResourceReqs/LectureReqs; modified ResourceReqs/LabReqs; modified ResourceReqs/StaffReqs; modified ResourceReqs/SoftwareReqs; modified ResourceReqs/SchoolReqs; modified Level; modified DateOfIntroduction; modified Frequency; modified LocationOfOffering; modified FacultyInformation/FICoordinator
19 May 2006 Andrew Barnden
22 May 2006 Andrew Barnden
22 May 2006 Andrew Barnden modified ResourceReqs/LibraryReqs; modified Prerequisites/PreReqKnowledge; modified Prohibitions; modified DateOfIntroduction
22 May 2006 Andrew Barnden
22 May 2006 Andrew Barnden modified UnitName; modified UnitContent/Summary; modified ResourceReqs/InterFaculty; modified ResourceReqs/IntraFaculty; modified ResourceReqs/OtherResources; modified Prerequisites/PreReqUnits; modified Corequisites; modified AliasTitles; modified Enrolment
22 May 2006 Andrew Barnden
24 May 2006 Geraldine DCosta FIT School Approval, Approved for submission FEC Mtg 3/06

This version: