CPE4004 Analysis and design of distributed information systems - Semester 1 , 2008

Unit leader :

Osama Dandash

Lecturer(s) :

Caulfield

  • Osama Dandash

Tutors(s) :

Caulfield

  • Osama Dandash

Introduction

Welcome to CPE4004 Analysis and design of distributed information systems

This unit introduces students to understand the modeling concepts in the development of Web services and distributed information systems

Unit synopsis

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 of Unified 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.

Learning outcomes

At the successful completion of this subject students will have:

  1. Understand the modelling concepts in development of distributed and component based information systems.
  2. Use an object-oriented analysis and design methodology to develop simple distributed information systems.
  3. Understand Service Oriented Architecture (SOA) and be able to apply SOA in component modeling:
  4. SOA services focus on business level activities. They can be extensively re-used
  5. SOA service are linked dynamically and flexibly
  6. Be familiar with client-server architectures and the design of web service solutions with J2EE platform
  7. Understand Web service modeling with RR, Web modeler
  8. Understand modeling of business processes and integration principles

Workload

workload commitments are:
  • two-hour lecture and
  • two-hour tutorial (or laboratory) (requiring advance preparation)
  • a minimum of 2-3 hours of personal study per one hour of contact time in order to satisfy the reading and assignment expectations.
  • You will need to allocate up to 5 hours per week in some weeks, for use of a computer, including time for newsgroups/discussion groups.

Unit relationships

Prerequisites

Before attempting this unit you must have satisfactorily completed an undergraduate qualification in computing or closely related discipline is required or equivalent. Experience with OO programming preferably Java or C++.

Relationships

Before attempting this unit you must have entry qualifications into any master's or honours program of the FacultyIt.

Continuous improvement

Monash is committed to ‘Excellence in education' and strives for the highest possible quality in teaching and learning. To monitor how successful we are in providing quality teaching and learning Monash regularly seeks feedback from students, employers and staff. Two of the formal ways that you are invited to provide feedback are through Unit Evaluations and through Monquest Teaching Evaluations.

One of the key formal ways students have to provide feedback is through Unit Evaluation Surveys. It is Monash policy for every unit offered to be evaluated each year. Students are strongly encouraged to complete the surveys as they are an important avenue for students to "have their say". The feedback is anonymous and provides the Faculty with evidence of aspects that students are satisfied and areas for improvement.

Student Evaluations

The Faculty of IT administers the Unit Evaluation surveys online through the my.monash portal, although for some smaller classes there may be alternative evaluations conducted in class.

If you wish to view how previous students rated this unit, please go to http://www.monash.edu.au/unit-evaluation-reports/

Over the past few years the Faculty of Information Technology has made a number of improvements to its courses as a result of unit evaluation feedback. Some of these include systematic analysis and planning of unit improvements, and consistent assignment return guidelines.

Monquest Teaching Evaluation surveys may be used by some of your academic staff this semester. They are administered by the Centre for Higher Education Quality (CHEQ) and may be completed in class with a facilitator or on-line through the my.monash portal. The data provided to lecturers is completely anonymous. Monquest surveys provide academic staff with evidence of the effectiveness of their teaching and identify areas for improvement. Individual Monquest reports are confidential, however, you can see the summary results of Monquest evaluations for 2006 at http://www.adm.monash.edu.au/cheq/evaluations/monquest/profiles/index.html

Unit staff - contact details

Unit leader

Mr Osama Dandash
Fax Fax: + 6 13 990 32400

Lecturer(s) :

Mr Osama Dandash
Fax Fax: + 6 13 990 32400

Tutor(s) :

Mr Osama Dandash
Fax Fax: + 6 13 990 32400

Teaching and learning method

The lectures will provide students with the fundamental theories.This unit will be delivered via 2 hour lecture and 2 hour tutorial per week. Lecturers may go through specific examples, give demonstrations and present information that contains theorectical concepts.

In tutorials students will complete practical exercises which will aid in their understanding of the content and their ability to complete assignment work. The tutorials are particluarly useful in helping student consolidate concepts and practise their problem solving skills.

Tutorial allocation

Students should register for tutorials using Allocate+

Communication, participation and feedback

Monash aims to provide a learning environment in which students receive a range of ongoing feedback throughout their studies. You will receive feedback on your work and progress in this unit. This may take the form of group feedback, individual feedback, peer feedback, self-comparison, verbal and written feedback, discussions (on line and in class) as well as more formal feedback related to assignment marks and grades. You are encouraged to draw on a variety of feedback to enhance your learning.

It is essential that you take action immediately if you realise that you have a problem that is affecting your study. Semesters are short, so we can help you best if you let us know as soon as problems arise. Regardless of whether the problem is related directly to your progress in the unit, if it is likely to interfere with your progress you should discuss it with your lecturer or a Community Service counsellor as soon as possible.

Unit Schedule

Week Topic Key dates
1 Software Engineering, characteristics of distributed applications  
2 Use case diagrams, entity and activity modelling and business processes, static models  
3 Object and class structuring, relatinships, dynamic models  
4 Service-oriented modelling and architecture (SOA),  
Mid semester break
5 J2EE design principles, Servlets, JSP Assignment Discussions
6 EJB, Session beans, Entity Beans  
7 multiple-tier architectures, Web services, WSDL  
8 Web service discovery, UDDI; modelling issues for WS with UML  
9 Modelling web pages with UML. WSDL revisited  
10 Design of Web service endpoint considerations  
11 Introduction to Portal,portlets and portlet development.  
12 Web service problems and future directions, portal solutions Assignment due
13 Revision  

Unit Resources

Prescribed text(s) and readings

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

Text books are available from the Monash University Book Shops. Availability from other suppliers cannot be assured. The Bookshop orders texts in specifically for this unit. You are advised to purchase your text book early.

Recommended text(s) and readings

  • Dennis, A, B. Wixom, D. Tegarden: System Analysis and Design with UML V. 2.0, Wiley, 2004
  • Richard C. Lee & William M. Tepfenhart: Practical Object-Oriented Development with UML and Java, Prentice Hall, 2002
  • J. Polgar, R. Bram, T. Polgar: BUILDING AND MANAGING ENTERPRISE-WIDE PORTALS, Idea Group Publishing, 2005

very good book is:

  • Paul Reed, JR. : Developing Applications with Java and UML, Addison Wesley, 2002

Other optional books:

  • Terry Quatrani: Visual Modeling with Rational Rose 2000 and UML, Addison Wesley, 2002
  • Booch, G., J. Rumbaugh, I. Jacobson, The Unified Modeling Language User Guide, Addison Wesley, 1999, ISBN 0-201-57168-4

Web references:

  • The Object Management Group http://www.omg.org/
  • Rational Software http://www.rational.com/index.jtmpl

Required software and/or hardware

You will need access to:

  • Java Version 6 Update 1 (download from Sun Microsystems)
  • Blue-J
  • Rational Rose

On-campus students may use this software which is installed in the computing labs. Information about computer use for students is available from the ITS Student Resource Guide in the Monash University Handbook.

Equipment and consumables required or provided

On-campus students may use the facilities available in the computing labs. Information about computer use for students is available from the ITS Student Resource Guide in the Monash University Handbook. You will need to allocate up to 4 hours per week for use of a computer, including time for newsgroups/discussion groups.

Study resources

Study resources we will provide for your study are:

  • Weekly detailed lecture notes outlining the learning objectives, discussion of the content, required readings and exercises;
  • Weekly tutorial or laboratory tasks and exercises with sample solutions provided one to two weeks later;
  • Assignment specifications and sample solutions;
  • This Unit Guide outlining the administrative information for the unit;
  • The unit web site on MUSO, whereresources outlined above will be made available.

Library access

The Monash University Library site contains details about borrowing rights and catalogue searching. To learn more about the library and the various resources available, please go to http://www.lib.monash.edu.au.  Be sure to obtain a copy of the Library Guide, and if necessary, the instructions for remote access from the library website.

Monash University Studies Online (MUSO)

All unit and lecture materials are available through MUSO (Monash University Studies Online). Blackboard is the primary application used to deliver your unit resources. Some units will be piloted in Moodle.

You can access MUSO and Blackboard via the portal (http://my.monash.edu.au).

Click on the Study and enrolment tab, then Blackboard under the MUSO learning systems.

In order for your Blackboard unit(s) to function correctly, your computer needs to be correctly configured.

For example :

  • Blackboard supported browser
  • Supported Java runtime environment

For more information, please visit

http://www.monash.edu.au/muso/support/students/downloadables-student.html

You can contact the MUSO Support by: Phone: (+61 3) 9903 1268

For further contact information including operational hours, please visit

http://www.monash.edu.au/muso/support/students/contact.html

Further information can be obtained from the MUSO support site:

http://www.monash.edu.au/muso/support/index.html

If your unit is piloted in Moodle, you will see a link from your Blackboard unit to Moodle at http://moodle.med.monash.edu.au.
From the Faculty of Information Technology category, click on the link for your unit.

Assessment

Unit assessment policy

The unit is assessed with one assignment and a two hour closed book examination. To pass the unit you must:

  • obtain 40% for the assignments overall ·
  • obtain 40% for the examination ·
  • obtain 50% for the unit overall

If a student does not achieve 40% or more in the unit examination or the unit non-examination assessment then a mark of no greater than 44-N will be recorded for the unit.

Assignment tasks

  • Assignment Task

    Title : Ass 1

    Description :

    UML and J2EE Assignment

    Weighting : 60%

    Criteria for assessment :

    • J2EE, web services and web service client are the platform of the assignment
    • Servlets and EJBs are involved
    • Business and detail models to be created using Rational Rose
    • Students should read assignment marking guide to see full break down of marks 

    Due date : week 12

Examinations

  • Examination

    Weighting : 40%

    Length : 2 hours

    Type ( open/closed book ) : Closed book

    Remarks ( optional - leave blank for none ) :

    Examination will cover UML, Web Services and J2EE components of the unit

Assignment submission

Assignments will be submitted by electronic submission to the student server with the appropriate cover sheet correctly filled out and attached. Hard copy is required (you need to print your hard copy and have a cover sheet).

The due date is the date by which the submission must be received.

Assignment coversheets

Students are required to submit an electronic cover sheet with their assignment This cover sheet can be downloaded from the unit web site

University and Faculty policy on assessment

Due dates and extensions

The due dates for the submission of assignments are given in the previous section. Please make every effort to submit work by the due dates. It is your responsibility to structure your study program around assignment deadlines, family, work and other commitments. Factors such as normal work pressures, vacations, etc. are seldom regarded as appropriate reasons for granting extensions. Students are advised to NOT assume that granting of an extension is a matter of course.

Requests for extensions must be made to the unit lecturer at your campus at least two days before the due date. You will be asked to forward original medical certificates in cases of illness, and may be asked to provide other forms of documentation where necessary. A copy of the email or other written communication of an extension must be attached to the assignment submission.

Late assignment

Late assignments will be panalised 5% for each late day up to 3 days. Assignments received later than three days after the due date are not accepted for correction, and zero marks are awarded accordingly. The only exception to this is in the case of illness or other serious cause. In any such cases, proper third party documentation (e.g. a doctor's certificate) would have to be supplied. Where a doctor's certificate is supplied, then an extension may be allowed for time specified on the doctor's certificate.

Return dates

Students can expect assignments to be returned within two weeks of the submission date or after receipt, whichever is later.

Assessment for the unit as a whole is in accordance with the provisions of the Monash University Education Policy at http://www.policy.monash.edu/policy-bank/academic/education/assessment/

We will aim to have assignment results made available to you within two weeks after assignment receipt.

Plagiarism, cheating and collusion

Plagiarism and cheating are regarded as very serious offences. In cases where cheating  has been confirmed, students have been severely penalised, from losing all marks for an assignment, to facing disciplinary action at the Faculty level. While we would wish that all our students adhere to sound ethical conduct and honesty, I will ask you to acquaint yourself with Student Rights and Responsibilities (http://www.infotech.monash.edu.au/about/committees-groups/facboard/policies/studrights.html) and the Faculty regulations that apply to students detected cheating as these will be applied in all detected cases.

In this University, cheating means seeking to obtain an unfair advantage in any examination or any other written or practical work to be submitted or completed by a student for assessment. It includes the use, or attempted use, of any means to gain an unfair advantage for any assessable work in the unit, where the means is contrary to the instructions for such work. 

When you submit an individual assessment item, such as a program, a report, an essay, assignment or other piece of work, under your name you are understood to be stating that this is your own work. If a submission is identical with, or similar to, someone else's work, an assumption of cheating may arise. If you are planning on working with another student, it is acceptable to undertake research together, and discuss problems, but it is not acceptable to jointly develop or share solutions unless this is specified by your lecturer. 

Intentionally providing students with your solutions to assignments is classified as "assisting to cheat" and students who do this may be subject to disciplinary action. You should take reasonable care that your solution is not accidentally or deliberately obtained by other students. For example, do not leave copies of your work in progress on the hard drives of shared computers, and do not show your work to other students. If you believe this may have happened, please be sure to contact your lecturer as soon as possible.

Cheating also includes taking into an examination any material contrary to the regulations, including any bilingual dictionary, whether or not with the intention of using it to obtain an advantage.

Plagiarism involves the false representation of another person's ideas, or findings, as your own by either copying material or paraphrasing without citing sources. It is both professional and ethical to reference clearly the ideas and information that you have used from another writer. If the source is not identified, then you have plagiarised work of the other author. Plagiarism is a form of dishonesty that is insulting to the reader and grossly unfair to your student colleagues.

Register of counselling about plagiarism

The university requires faculties to keep a simple and confidential register to record counselling to students about plagiarism (e.g. warnings). The register is accessible to Associate Deans Teaching (or nominees) and, where requested, students concerned have access to their own details in the register. The register is to serve as a record of counselling about the nature of plagiarism, not as a record of allegations; and no provision of appeals in relation to the register is necessary or applicable.

Non-discriminatory language

The Faculty of Information Technology is committed to the use of non-discriminatory language in all forms of communication. Discriminatory language is that which refers in abusive terms to gender, race, age, sexual orientation, citizenship or nationality, ethnic or language background, physical or mental ability, or political or religious views, or which stereotypes groups in an adverse manner. This is not meant to preclude or inhibit legitimate academic debate on any issue; however, the language used in such debate should be non-discriminatory and sensitive to these matters. It is important to avoid the use of discriminatory language in your communications and written work. The most common form of discriminatory language in academic work tends to be in the area of gender inclusiveness. You are, therefore, requested to check for this and to ensure your work and communications are non-discriminatory in all respects.

Students with disabilities

Students with disabilities that may disadvantage them in assessment should seek advice from one of the following before completing assessment tasks and examinations:

Deferred assessment and special consideration

Deferred assessment (not to be confused with an extension for submission of an assignment) may be granted in cases of extenuating personal circumstances such as serious personal illness or bereavement. Information and forms for Special Consideration and deferred assessment applications are available at http://www.monash.edu.au/exams/special-consideration.html. Contact the Faculty's Student Services staff at your campus for further information and advice.