Skip to content | Change text size

M O N A T A R

InfoTech Unit Avatar

CPE5007 Enterprise Application Development

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

CPE5007 Enterprise Application Development (26 Apr 2006, 11:15am) []

Reasons for Introduction

Obsolete Reasons for Introduction

The Master of Network Computing is directed, in part, to practising IT professionals who may have a first degree in computing, and now wish to upgrade their qualifications specifically in the network computing area. This master's course aims to produce graduates who will be specialists in the field of network computing, who will be able to design and construct distributed applications operating on local area networks, wide area networks, intranets, extranets and the Internet. As distributed software systems have grown in size, the granularity of the problem domain has also grown. This change has brought about the realisation that the greatest complexity in most systems manifest itself as a problem of how software can interact over heterogeneous and distributed environments.  Software engineers will often employ middleware to contain heterogeneity and distribution complexity. Frameworks, therefore, have to be designed with a clear understanding of the middleware they utilize. Existing middleware can be classified into three types, transactional, message-oriented and object-oriented. The object-oriented approach provides much promise as it address much of the complexity issues through encapsulation and modularity. This subject provides students with an advanced coverage of object oriented middleware.

Reasons for Introduction (26 Apr 2006, 12:06pm)

As distributed software systems have grown in size, the granularity of the problem domain has also grown. This change has brought about the realisation that the greatest complexity in most systems manifest itself as a problem of how software can interact over heterogeneous and distributed environments. The trend in IT is also moving towards building such systems for the enterprise.

Software engineers will often employ middleware to contain heterogeneity and distribution complexity for the enterprise. Frameworks, therefore, have to be designed with a clear understanding of the middleware they utilize. Existing middleware can be classified into three types, transactional, message-oriented and object-oriented. The object-oriented approach provides much promise as it address much of the complexity issues through encapsulation and modularity.

It is therefore necessary to provide a unit to address these issues and at the same time, provide practical experience in the development of such appplications with the focus on applications for the enterprise.

Reasons for Change (27 Apr 2006, 09:13am)

As distributed systems become more complex, moving towards the enterprise architectural framework, it is important to focus on developing large applications for the enterprise.

Role of Unit (26 Apr 2006, 12:09pm)

This unit is one of the core units for Master of Information Technology specialisation, Enterprise Architecture.

Relationship of Unit (27 Apr 2006, 09:15am)

There are two other existing units that deal explicitly with enterprise systems: CPE4004 and IMS5052. The former focuses on the object-oriented analysis and design of distributed enterprise systems, while the latter addresses the issues, problems and strategies of concern in the implementation of enterprise systems using a theoretical and case-based approach. This unit specifically deals with the object-oriented development of enterprise systems and provides hands-on experience using existing tools for the actual deployment.

Relevance of Unit (26 Apr 2006, 12:27pm)

As one of the core units for Enterprise Architecture specialisation, this unit will provide the development skills necessary to build enterprise applications.

Objectives

Statement of Objectives (26 Apr 2006, 12:35pm)

Upon completion of this unit, students should be able to:

  1. identify key components of the object-oriented enterprise architecture.
  2. understand the various advanced Java technologies used to build applications for the enterprise.
  3. use the advanced Java libraries to implement a medium-sized enterprise application.
  4. display an in-depth understanding of a selected topic related to enterprise application development.

Additionally, either via a literature survey or a case study, students should demonstrate the capacity to identify and critically evaluate current trends in distributed software development that might contribute to their implementation.

Knowledge and Understanding (Cognitive Domain Objectives) (26 Apr 2006, 1:48pm)

Upon the completion of this unit, students will have the knowledge of a commercially relevant programming language and its associated libraries, and gain the understanding of:

Attitudes, Values and Beliefs (Affective Domain Objectives) (26 Apr 2006, 1:49pm)

Upon the completion of this unit, the students will:

Practical Skills (Psychomotor Domain Objectives) (26 Apr 2006, 1:52pm)

Upon the completion of this unit, students will have skills in designing, developing, deploying and testing a small to medium sized web-based distributed application written in Java for the enterprise

Unit Content

Summary (26 Apr 2006, 1:42pm)

As application development advances towards web-based distributed applications for the enterprise, this unit introduces techniques and addresses various theoretical issues pertaining to the development of such applications. The Java programming language and Java technologies will be used in the practical assignments to implement the theoretical concepts. Advanced Java topics to be covered and discussed include Enterprise JavaBeans, Java ServerPages, Java Servlet Technology and Java Database Connectivity. Students will be able to address other issues related to the development of large scale enterprise systems including: transactions and distributed transaction processing, interoperability and persistence, scalability and the choices facing enterprise system architects and developers.

Handbook Summary (26 Apr 2006, 1:23pm)

As application development advances towards web-based distributed applications for the enterprise, this unit introduces techniques and addresses various theoretical issues pertaining to the development of such applications. The Java programming language and Java technologies will be used in the practical assignments to implement the theoretical concepts underpinning enterprise application development.

Recommended Reading (26 Apr 2006, 1:28pm)

Teaching Methods

Mode (26 Apr 2006, 1:29pm)

On Campus

Strategies of Teaching (26 Apr 2006, 1:53pm)

Teaching Methods Relationship to Objectives (26 Apr 2006, 1:54pm)

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

Attitudes and beliefs objectives are achieved mainly through laboratory 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 laboratory exercises and assignment work.

Assessment

Strategies of Assessment (26 Apr 2006, 1:55pm)

Assignment 50%, Research paper 50%

Assessment Relationship to Objectives (26 Apr 2006, 1:57pm)

Knowledge and understanding objectives are assessed through the assignment work and research paper.

Attitudes, values and belief objectives are assessed mainly through assignment work and research paper.

Practical skills objectives are assessed mainly through assignment work.

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

Workloads

Credit Points (26 Apr 2006, 1:57pm)

6

Workload Requirement (26 Apr 2006, 1:58pm)

12 hours per week including lectures, laboratory sessions and private study.

Resource Requirements

Lecture Requirements (27 Apr 2006, 08:53am)

High-tech lecture theatre with data display and internet connection with a PC and facility to plug in a laptop. Two hours per week throughout the semester.

Laboratory Requirements (27 Apr 2006, 08:55am)

Laboratories equipped with standard PCs running on Windows OS

Staff Requirements (27 Apr 2006, 08:55am)

One lecturer per semester and one tutor per laboratory session per semester.

Software Requirements (27 Apr 2006, 09:02am)

Library Requirements (27 Apr 2006, 09:03am)

Adequate copies of at least the recommended texts listed above.

Teaching Responsibility (Callista Entry) (27 Apr 2006, 09:04am)

FIT

Prerequisites

Prerequisite Knowledge (27 Apr 2006, 09:06am)

The prequisite for this unit is knowledge and practical experience with Java programming language.

Research Interest (27 Apr 2006, 09:09am)

Research component comes in the form of a research paper to be submitted as part of the assessment.

Proposed year of Introduction (for new units) (27 Apr 2006, 09:09am)

Semester 1 2007

Frequency of Offering (27 Apr 2006, 09:10am)

At least once per year.

Location of Offering (27 Apr 2006, 09:10am)

Caulfield

Faculty Information

Proposer

Jana Dospisil

Contact Person (27 Apr 2006, 09:11am)

Sea (Chris) Ling

Unit Coordinator (27 Apr 2006, 09:12am)

Sea (Chris) Ling

Approvals

School:
Faculty Education Committee:
Faculty Board:
ADT:
Faculty Manager:
Dean's Advisory Council:
Other:

Version History

17 Oct 2005 David Sole Added Software requrirements template
21 Oct 2005 David Sole Updated requirements template to new format
26 Apr 2006 Sea Ling modified UnitName
26 Apr 2006 Sea Ling modified ReasonsForIntroduction/RIntro; modified ReasonsForIntroduction/RChange; modified ReasonsForIntroduction/RIntro; modified ReasonsForIntroduction/RRole; modified ReasonsForIntroduction/RRelation; modified ReasonsForIntroduction/RRelevance; modified UnitObjectives/ObjText; modified Classification; modified UnitContent/Summary; modified UnitContent/Summary
26 Apr 2006 Sea Ling modified UnitContent/Summary; modified UnitContent/HandbookSummary; modified UnitContent/RecommendedReading; modified UnitContent/RecommendedReading; modified Teaching/Mode; modified Teaching/Strategies
26 Apr 2006 Sea Ling modified UnitContent/Summary; modified UnitObjectives/ObjCognitive; modified UnitObjectives/ObjAffective; modified UnitObjectives/ObjPsychomotor; modified UnitObjectives/ObjPsychomotor; modified Classification; modified Teaching/Strategies; modified Teaching/Objectives; modified Assessment/Strategies; modified Assessment/Objectives; modified Workload/CreditPoints; modified Workload/WorkHours
27 Apr 2006 Sea Ling modified ResourceReqs/LectureReqs; modified ResourceReqs/TutorialReqs; modified ResourceReqs/TutorialReqs; modified ResourceReqs/LabReqs; modified ResourceReqs/StaffReqs; modified ResourceReqs/SoftwareReqs; modified ResourceReqs/LibraryReqs; modified ResourceReqs/SchoolReqs; modified Prerequisites/PreReqKnowledge; modified Research; modified Research; modified DateOfIntroduction; modified Frequency; modified LocationOfOffering; modified FacultyInformation/FIContact; modified FacultyInformation/FICoordinator; modified FacultyInformation/FIContact; modified FacultyInformation/FICoordinator
27 Apr 2006 Sea Ling modified ReasonsForIntroduction/RChange; modified ReasonsForIntroduction/RRelation
03 May 2006 Sea Ling

This version: