CPE2003 Analysis and design of distributed information systems , Unit Information Guide (Semester 1, 2006)

Chief Examiner Dr. Jana Polgar
Outline On successful completion of this unit, students should be able to: 1. Understand the major tasks involved in developing distributed information systems. 2. Understand the basic concepts of the object-oriented paradigm. 3. Use an object-oriented analysis and design methodology to design simple distributed information systems. 4. Use the Unified Modeling Language to analyse user requirements and propose design and implementation solutions. 5. Be familiar with typical object-oriented, client-server, Internet system architectures. 6. Be able to apply relevant professional communication techniques during the system development process. 7. Understand the role of documentation, CASE tools and the information repository in the system development process.
Objectives On successful completion of this unit, students should be able to: Knowledge of: 1.Object-oriented analysis and design of networked and distributed information systems; 2.System development methodology stages and deliverables: project initiation and planning, conceptualization, analysis and model refinement, system build, system implementation, system evaluation. 3.Methodology necessary for the analysis and design of networked systems; 4.The Unified Modeling Language (UML) notation: use cases, class diagrams, interaction diagrams, package diagrams, state diagrams, activity diagrams, deploymnet diagrams. 5.Object-oriented analysis and design skills necessary for analysis and design of networked and distributed systems; Skills in: 6.Capacity to apply the object-oriented modeling paradigm; classes and objects, object structure and behavior, object relationships, object properties (encapsulation), identity, attributes and operations, polymorphism; 7.Capacity to identify the abstractions (classification, instantiation, aggregation, generalization and association) in user requirements. 8.Ability to demonstrate how to meet user requirements throughout the analysis and design process; 9.Planning and analysis skills associated with the design and analysis of networked and distributed systems. 10.Capacity to identify potential problems in implementation 11.Professional communication techniques for systems analysis and design . Attitudes of: 12.The unit is designed to sustain a positive attitude towards design and analysis of networked and distributed information systems that facilitate a greater understanding of design process.
Prerequisites Before attempting this unit you must have satisfactorily completed [ CPE1001, or equivalent object oriented programming experience ] , or equivalent.

Unit relationships CPE2003 is a [core/elective] unit in the [BNC] of the [enter the names of the degrees]. It is a [prerequisite/corequisite] for Before attempting this unit you must have satisfactorily completed [ CPE1001, or equivalent object oriented programming experience ] , or equivalent.. You may not study this unit and [enter the unit codes of the prohibited units] in your degree.
Texts and software

Required text(s)

Quatrani Terry: Visual Modelling with Rational Rose 2000 and UML. Charles Richter: Designing Flexible Object-oriented Systems with UML, Macmillan Technical Publishing, 1999; Hassan Gomaa: Designing Concurrent, Distributed, and Real-Time Applications with UML, Addison-Wesley, 2000;

Selected chapters from: J. Polgar, R. Bram, T. Polgar: BUILDING AND MANAGING ENTERPRISE-WIDE PORTALS will be available on the subject web site

 

 

 

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.

Software requirements:

rational Rose in the labs

Hardware requirements:

Students studying off-campus are required to have the minimum system configuration specified by the faculty as a condition of accepting admission, and regular Internet access. On-campus students, and those studying at supported study locations 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 n hours per week for use of a computer, including time for newsgroups/discussion groups.

Recommended reading

J. Polgar, R. Bram, T. Polgar: BUILDING AND MANAGING ENTERPRISE-WIDE PORTALS, Idea Group Publishing, 2005 ·

or

Richard C. Lee & William M. Tepfenhart: Practical Object-Oriented Development with UML and Java, Prentice Hall, 2002

 

 
Library access You may need to access the Monash library either personally to be able to satisfactorily complete the subject.  Be sure to obtain a copy of the Library Guide, and if necessary, the instructions for remote access from the library website.
Study resources

Study resources for CPE2003 are:

view the following link: http://neptune.netcomp.monash.edu.au/cpe2003/index.html

 
Structure and organisation

Week

Topics

Study Guide

1 Software Engineering, requirements
2 Use case diagrams
3 Static modeling
4 Object and class structuring
5 Finite state machines
6 Activity diagrams
7 Concurrency models
Non-teaching
8 Multiple tier architectures
9 J2EE design principles
10 Modelling web pages with UML
11 Quality measurement
12 Testing principles
13 Portals and portlet design
Timetable

The timetable for on-campus classes for this unit can be viewed in Allocate+
Assessment

Assessment for the unit consists of n assignments with a weighting of x% and an examination with a weighting of y%. Read this section VERY carefully.

Practical Assignments :
Assignment 1- individual assignment (15% of subject assessment)
Assignment 2 - individual assignment (25% of subject assessment)
Examination (60% of subject assessment)

 

Assessment Policy

To pass this unit you must:

Your score for the unit will be calculated by:

Assessment Requirements

Assessment

Due Date

Weighting

Assignment 1 TBA 15 %
Assignment 2 TBA 25 %

Assignment specifications will be made available . Information about assignments will be published on the Unit's Notices Newsgroup.

Assignment Submission Methods

Assignments will be submitted by [electronic/paper] submission to [enter submission URL/location] On-campus Students Submit the assignment to the [enter submission location] by [enter submission date], with the appropriate cover sheet correctly filled out and attached Off Campus (OCL) students [OCL only] Mail your assignment to the Off-Campus Learning Centre with the cover sheet attached. Singapore and Hong Kong Students [Gippsland only] Mail your assignment to the Distance Education Centre with the cover sheet attached. Do not email submissions. The due date is the date by which the submission must be received/the date by which the the submission is to be posted.

Extensions and late submissions

Late submission of assignments

Assignments received after the due date will be subject to a penalty of [describe penalty for late submission, describe the deadline for late assignment acceptance or any conditions that are placed on late assignments, e g, "Assignments received later than one week after the due date will not normally be accepted."]

This policy is strict because comments or guidance will be given on assignments as they are returned, and sample solutions may also be published and distributed, after assignment marking or with the returned assignment. 

Extensions

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. 

Requests for extensions must be made by [method of request, for example, 'email to the unit lecturer'] 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.

Grading of assessment

Assignments, and the unit, will be marked and allocated a grade according to the following scale:

HD High Distinction - very high levels of achievement, demonstrated knowledge and understanding, skills in application and high standards of work encompassing all aspects of the tasks.
In the 80+% range of marks for the assignment.
D Distinction - high levels of achievement, but not of the same standards. May have a weakness in one particular aspect, or overall standards may not be quite as high.
In the 70-79% range.
C Credit - sound pass displaying good knowledge or application skills, but some weaknesses in the quality, range or demonstration of understanding.
In the 60-69% range.
P Pass - acceptable standard, showing an adequate basic knowledge, understanding or skills, but with definite limitations on the extent of such understanding or application. Some parts may be incomplete.
In the 50-59% range.
N Not satisfactory -  failure to meet the basic requirements of the assessment.
Below 50%.

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

Feedback Feedback to you

You will receive feedback on your work and progress in this unit. This feedback may be provided through your participation in tutorials and class discussions, as well as through your assignment submissions. It may come in the form of individual advice, marks and comments, or it may be provided as comment or reflection targeted at the group. It may be provided through personal interactions, such as interviews and on-line forums, or through other mechanisms such as on-line self-tests and publication of grade distributions.

Feedback from you

You will be asked to provide feedback to the Faculty through a Unit Evaluation survey at the end of the semester. You may also be asked to complete surveys to help teaching staff improve the unit and unit delivery. Your input to such surveys is very important to the faculty and the teaching staff in maintaining relevant and high quality learning experiences for our students.

And if you are having problems

It is essential that you take action immediately if you realise that you have a problem with your study. The semester is 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.

Plagiarism and cheating

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 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.
Communication

Notices

Notices related to the unit during the semester will be placed on the Notices Newsgroup in the Unit Website. Check this regularly. Failure to read the Notices newsgroup is not regarded as grounds for special consideration.

Consultation Times

If direct communication with your unit adviser/lecturer or tutor outside of consultation periods is needed you may contact the lecturer and/or tutors at:

Dr Jana Polgar
Lecturer
Phone +61 3 990 44135
Fax +61 3 990 44124

All email communication to you from your lecturer will occur through your Monash student email address. Please ensure that you read it regularly, or forward your email to your main address. Also check that your contact information registered with the University is up to date in My.Monash.

Last updated: Feb 27, 2006