Skip to content | Change text size

M O N A T A R

InfoTech Unit Avatar

CPE4004 Analysis and design of distributed information systems

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

CPE4004 Analysis and design of distributed information systems (22 Feb 2007, 5:35pm) [CPE4004 (23 May 2007, 3:12pm)]

Reasons for Introduction

Reasons for Introduction (31 Jan 2005, 12:43pm)

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 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 varianty of networks. This subject will provide the skills and knowledge required to allow students to analyse user requirements and design distributed information systems using the services of computer networks that meet these requirements using object oriented approach and service oriented analysis in the system development process.

Objectives

Statement of Objectives (22 Feb 2007, 5:56pm)

Objectives should be written in terms of learning outcomes for the student.

-Understand the modelling concepts in development of distributed and component based information systems. -Use an object-oriented analysis and design methodology to develop simple distributed information systems. -Understand Service Oriented Architecture (SOA) and be able to apply SOA in component modeling:

  • SOA services focus on business level activities. They can be extensively re-used
  • SOA service are linked dynamically and flexible -Be familiar with client-server architectures and the design of web service solutions with J2EE platform -Understand Web service modeling with RR, Web modeler -Understand modeling of business processes and integration principles
  • Objectives should be measurable.

    One way of achieving this is to avoid the use of broad or

    general terms like {\dq be familiar with, be aware of,
    etc.
    If the words "A student should be able to appreciate ..." is used, a list of criteria for } appreciation should be included.
    Poor example: A student is able to appreciate a good red wine.
    Good
    example:
    A student is able to appreciate a good red wine } in terms of its colour, amount of fruit, amount of oak, aroma, tannin level and cellaring potential. }

    Learning Domains for Objectives

    There are four learning domains that categorise learning

    objectives. You may not have all domains present in your objectives, but they should at least be considered. See below for the four domains.

    References:

    Bloom, B.S. (Ed) (1956 - 1964). Taxonomy of educational

    objectives: the classification of educational goals. Vol 1 & 2.

    Simpson, E. (1972). The classification of educational

    objectives in the psychomotor domain. The psychomotor domain, vol. 3 Washington, D.C.: Gryphon House.

    http://wwww.nwlink.com/~donclark/hd/bloom.html

    Knowledge and Understanding (Cognitive Domain Objectives) (31 Jan 2005, 1:04pm)

    This subject aims to provide students with an understanding of how to analyse and design distributed as well as service oriented information systems that support organizational activities. The specific objectives of this subject are to enable students to:

    1. Be familiar with typical client-server architectures, the component based design of Internet based information systems (B2B, B2E, B2C) and Web services.
    2. Understand the issues relevant to the development of distributed information systems and Web services.
    3. Understand the major workflows involved in developing Web services and distributed systems interacting with Web services.
    4. Understand the elements of Service Oriented Analysis and Service Oriented modelling and architectures.
    5. Use the Unified Modelling Language to model user requirements Web service based solutions.

    Unit Content

    Summary (31 Jan 2005, 1:20pm)

    Characteristics of distributed information systems. Introduction to Service Oriented Analysis, SOA. Elements of Service Oriented Analysis and development life cycle modedels. Client server architectures and architecture of Web services and Internet based information systems. Distributed system development methodology, processes, artifacts and core workflows and basic elements ofUnified Modelling Language (UML). UML use case diagrams, class diagrams, sequence diagrams, component and deplyment diagrams. Modelling concurerncy and distribution aspects in Web services and Internet based applications. Modelling J2EE components with UML. Modelling web pages with UML. Testing methodologies to Web services. Future directions in component based architectures.

    Recommended Reading (31 Jan 2005, 1:26pm)

    Richard C. Lee & William M. Tepfenhart: Practical Object-Oriented Development with UML and Java, Prentice Hall, 2002 or Paul R. Reed, Jr. : Developng Applications with Java and UML, Addison Wesley, 2002

    Teaching Methods

    Mode (31 Jan 2005, 1:28pm)

    on campus

    Strategies of Teaching (31 Jan 2005, 1:30pm)

    Teaching will be conducted through lectures, tutorials, discussion groups and the provision of materials enabling flexible delivery approaches.

    Teaching Methods Relationship to Objectives (31 Jan 2005, 1:37pm)

    Lectures:

    The lectures will introduce and explore each topic, introducing students to the development of distributed information systems and major elements of Web services and SOA (objectives 1,2 &3), the principles and concepts underpinning Service oriented analysis (objective 4)and way in which UML may be used to support the development of service based distributed information systems (objectives 3,4, & 5).

    Tutorials:

    Tutorials will invole students determining and modelling requirements for distributed web service based information systems and discussing issues in the development of web services and service-oriented analysis (objectives 1,2,3,4, 5).

    Assessment

    Strategies of Assessment (31 Jan 2005, 1:39pm)

  • A final examination of 2 hours and worth 40%
  • Practical assignment worth 60%
  • Assessment Relationship to Objectives (31 Jan 2005, 1:44pm)

    A final examination will test students conceptual understanding of the topics covered in objectives 1 -5.

    Student will be required to undertake practical assignments worth 60% of the subject assessment. This will involve them preparing models and other artifacts outlining the requirements for service oriented information systems together with the complete model of the distributed application (objectives 1 -5).

    Workloads

    Workload Requirement (31 Jan 2005, 1:47pm)

    2 hours lecture per week

    2 hours tutorials per week

    8 hours individula studies per week

    Resource Requirements

    Lecture Requirements (31 Jan 2005, 1:48pm)

    Standard lecture theatre (projector, availability to connect laptop). Expected class size 60 students.

    Tutorial Requirements (31 Jan 2005, 1:50pm)

    Current on campus resources are adequate:

    For each student: 1 workstation with MS Office, allow access to Rational Rose software (UML).

    Staff Requirements (31 Jan 2005, 1:55pm)

    Subject lecturer and subject tutors (one tutor for every 20 students). Caulfield Campus based.

    Software Requirements (21 Oct 2005, 1:04pm)

    Rational Rose software

    Teaching Responsibility (Callista Entry) (22 Feb 2007, 5:41pm)

    Prerequisites

    Prerequisite Units (31 Jan 2005, 1:57pm)

    An undergraduate qualification in computing or closely related discipline is required.

    Corequisites (31 Jan 2005, 1:58pm)

    NONE

    Prohibitions (31 Jan 2005, 1:59pm)

    NONE

    Level (31 Jan 2005, 2:00pm)

    Level 4 in the Master of Network Computing

    Proposed year of Introduction (for new units) (31 Jan 2005, 2:00pm)

    Semester 1 of 2001

    Frequency of Offering (31 Jan 2005, 2:01pm)

    Once per year

    Enrolment (31 Jan 2005, 2:02pm)

    60 students

    Location of Offering (31 Jan 2005, 2:02pm)

    Caulfield Campus

    Faculty Information

    Proposer

    Jana Polgar

    Contact Person (22 Feb 2007, 5:43pm)

    Osama Dandash

    Approvals

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

    Version History

    31 Jan 2005 Jana Polgar Initial Draft; modified Abbreviation; modified ReasonsForIntroduction/RIntro; modified UnitObjectives/ObjAffective; modified UnitObjectives/ObjCognitive; modified UnitObjectives/ObjAffective; modified Classification; modified UnitContent/Summary; modified UnitContent/RecommendedReading; modified Teaching/Mode; modified Teaching/Strategies; modified Teaching/Objectives; modified Teaching/Objectives; modified Assessment/Strategies; modified Assessment/Objectives; modified Workload/WorkHours; modified ResourceReqs/LectureReqs; modified ResourceReqs/TutorialReqs; modified ResourceReqs/StaffReqs; modified ResourceReqs/SoftwareReqs; modified ResourceReqs/StaffReqs; modified ResourceReqs/SchoolReqs; modified Prerequisites/PreReqUnits; modified Corequisites; modified Prohibitions; modified Level; modified DateOfIntroduction; modified Frequency; modified Enrolment; modified LocationOfOffering; modified FacultyInformation/FIContact; modified FacultyInformation/FICoordinator
    17 Oct 2005 David Sole Added Software requrirements template
    21 Oct 2005 David Sole Updated requirements template to new format
    22 Feb 2007 Osama Dandash modified UnitName; modified ResourceReqs/SchoolReqs; modified FacultyInformation/FIContact; modified FacultyInformation/FICoordinator

    This version: