School of Computer, Data and Mathematical Sciences
300144 Object Oriented Analysis Sydney City Session 1 2021
Unit Details
Unit Code:
300144
Unit Name:
Object Oriented Analysis
Credit Points:
10
Unit Level:
2
Assumed Knowledge:
General understanding of what an information system is and how information systems devel- opment is undertaken and
– Introductory knowledge about system analysis and design, including
– basic problem solving experience in computerised information systems
– ability to derive systems requirements from problem definitions
– ability to produce system models using process, data, object and network modelling.
– understanding design and implementation issues include, (but may not be limited to), ele- mentary database design, input, output and user interface design and prototyping.
– General knowledge on programming languages
– Understanding difference between procedure programming and object oriented programming – Introductory knowledge of classes and objects and the class construction
– Introductory knowledge on object orientation, including encapsulation, inheritance
Note: Students with any problems, concerns or doubts should discuss those with the Unit Coordinator as early as they can.
Unit Convenor (SCC)
Name: Dr Mahsa Razavi
Email: M.Razavi@city.westernsydney.edu.au
Consultation Arrangement:
Please liaise directly with the academic teaching this unit regarding appropriate consultation times. It is usually best to make contact with these staff via email.
Program Convenor (SCC)
Name: Antoinette Cevenini
Email: a.cevenini@city.westernsydney.edu.au
Consultation Arrangement:
Please liaise directly with the academic teaching this unit regarding appropriate consultation times. It is usually best to make contact with these staff via email.
Edition: Sydney City Session 1 2021
Copyright ©2021 University Western Sydney trading as Western Sydney University ABN 53 014 069 881 CRICOS Provider No: 00917K No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or by any information storage and retrieval system, without the prior written permission from the Dean of the School. Copyright for acknowledged materials reproduced herein is retained by the copyright holder. All readings in this publication are copied under licence in accordance with Part VB of the Copyright Act 1968.
Contents
1 About Object Oriented Analysis 2
1.1 AnIntroductiontothisUnit ………………………………… 2 1.2 WhatisExpectedofYou ………………………………….. 2 1.3 ChangestoUnitasaResultofPastStudentFeedback ……………………. 3
2 Assessment Information 4
2.1 UnitLearningOutcomes ………………………………….. 4
2.2 ApproachtoLearning ……………………………………. 4
2.3 ContributiontoCourseLearningOutcomes …………………………. 5
2.4 AssessmentSummary ……………………………………. 7
2.5 AssessmentDetails …………………………………….. 8
2.5.1 Participation…………………………………….. 8 2.5.2 AppliedProject …………………………………… 9 2.5.3 OnlineFinalExam………………………………….. 13
2.6 GeneralSubmissionRequirements………………………………. 14
3 Teaching and Learning Activities 16
4 Learning Resources 21
4.1 RecommendedReadings…………………………………… 21
Note: The relevant Learning Guide Companion supplements this document 1
1 About Object Oriented Analysis 1.1 An Introduction to this Unit
The core strength of this unit is to analyse and model business objectives and critical requirements of software systems to be developed using object-oriented (OO) approaches. The system analysis is taken to greater depths within the context of Object Orientation. The Unified Modelling Language version 2.0 (notably use cases, user case diagrams, activity diagrams, class diagrams and sequence diagrams) is used as the modelling standard for creating OO models in the problem space. The unit also covers the rational unified process methodology and applications of design patterns for software development through practical case studies.
1.2 What is Expected of You
Study Load
A student is expected to study an hour per credit point a week. For example a 10 credit point Unit would require 10 hours of study per week. This time includes the time spent within classes during lectures, tutorials or practicals.
Attendance
It is strongly recommended that students attend all scheduled learning activities to support their learning.
Online Learning Requirements
Unit materials will be made available on the Unit’s vUWS (E-Learning) site (https://vuws.westernsydney.edu.au/). You are expected to consult vUWS at least twice a week, as all Unit announcements will be made via vUWS. Teaching and learning materials will be regularly updated and posted online by the teaching team.
Special Requirements
Essential Equipment:
Not Applicable
Legislative Pre-Requisites:
Not Applicable
Policies Related to Teaching and Learning
The University has a number of policies that relate to teaching and learning. Important policies affecting students include:
– Assessment Policy
– Bullying Prevention Policy and
– Guidelines
– Enrolment Policy
– Examinations Policy
– Review of Grade Policy
– Sexual Harassment Prevention Policy
– Special Consideration Policy
– Student Misconduct Rule
– Teaching and Learning – Fundamental Code – Student Code of Conduct
2
Academic Integrity and Student Misconduct Rule
In submitting assessments, it is essential that you are familiar with the policies listed above and that you understand the principles of academic integrity. You are expected to act honestly and ethically in the production of all academic work and assessment tasks, submit work that is your own and acknowledge any contribution to your work made by others.
Important information about academic integrity, including advice to students is available at https://www.westernsydney. edu.au/studysmart/home/academic_integrity_and_plagiarism. It is your responsibility to familiarise yourself with these principles and apply them to all work submitted to the University as your own.
When you submit an assignment or product, you will declare that no part has been: copied from any other stu- dent’s work or from any other source except where due acknowledgement is made in the assignment; submitted by you in another (previous or current) assessment, except where appropriately referenced, and with prior permission from the Unit Coordinator; written/produced for you by any other person except where collaboration has been au- thorised by the Unit Coordinator.
The Student Misconduct Rule applies to all students of Western Sydney University and makes it an offence for any student to engage in academic, research or general misconduct as defined in the Rule.
The University considers plagiarism, cheating and collusion as instances of academic misconduct. The University also considers submitting falsified documentation in support of applications for special consideration, including sitting of deferred examinations, as instances of general misconduct. You should be aware that changes were made to the Student Misconduct Rule commencing 1 January 2020 that provide for minimum sanctions that apply to certain conduct, including the provision of falsified documentation to the University.
You are strongly advised to read the Student Misconduct Rule and the Inappropriate Behaviour Guidelines at the commencement of each session to familiarise yourself with this process and the expectations of the University in relation to work submitted for assessment.
1.3 Changes to Unit as a Result of Past Student Feedback
The University values student feedback in order to improve the quality of its educational programs. The feedback provided helps us improve teaching methods and Units of study. The survey results inform Unit content and design, learning guides, teaching methods, assessment processes and teaching materials.
You are welcome to provide feedback that is related to the teaching of this Unit. At the end of the semester you will be given the opportunity to complete a Student Feedback on Unit (SFU) questionnaire to assess the Unit. You may also have the opportunity to complete a Student Feedback on Teaching (SFT) questionnaire to provide feedback for individual teaching staff.
As a result of student feedback, the following changes and improvements to this subject have recently been made:
– Project groups are formed by students themselves with variable sizes (3~5 members, 4 is preferred).
– The project result of each project group member is composed of group mark (50%) and individual mark (50%). While the group mark is based on the quality of the overall project work and is the same to all the group members, the individual mark is subject to adjustment in accordance with the peer reviews from all the group members (if one chooses not submitting the review, his/her mark will be adjusted according to the reviews
from the other group members).
– If a group member doesn’t have any contribution (or very little) to the project, the team should report this to
the tutor of the class and remove the member’s name from the submitted project report.
– A project briefing sessions are conducted in tutorial classes to provide more detailed requirements on this
assessment, including explanation of the project marking in different circumstances.
– The contents of the Intro-session Exam is reduced and the feedback to the exam results is provided in the
lecture.
– A more recent textbook is adopted as one significant reference of the unit.
– Continuing and unabated efforts are undertaken to improve the teaching and learning experiences.
3
2 2.1
Assessment Information Unit Learning Outcomes
Outcome
1
Explain the theoretical fundamentals underpinning Object Oriented Analysis
2
Identify Unified Modelling Language (UML) of the Object Management Group (OMG) for analysing software requirements
3
Outline an object oriented lifecycle and methodology and explain the process of object oriented analysis, especially within the context of iterative and incremental nature of the process
4
Apply the iterative and adaptable process frame work of RUP in software development
5
Construct well-documented UML-based artefacts from the early phases of the development process for the case study
6
Construct the Model of the Problem Space based on the analysis in an industrial CASE tool
7
Apply team work skills in a small development team, including: distributing the development workload, resolving disputes, running meetings, and taking minutes
8
Identify and create operational (non-functional) requirements of a system including performance and security
9
Develop a report based on verbal and written instructions about the performance of software development tasks and associated administrative duties
10
Illustrate quality assurance, quality control and user-expectations via reports and theoretical explanation
11
Explore possibilities of applying design patterns in software design
2.2
Approach to Learning
This unit is a 10 credit point unit (so need averagely 10-hour studying time per week) and will require your full and continuous attention to maintain the highest possible grades. Some weeks you will spend more time on learning activities and assessments and in other weeks the workload will be somewhat less.
We will provide lecture notes, tutorials and reading materials to support the unit content so that you can practice further in your own time.
Attendance at the tutorials/practicals is compulsory. The participation mark for each tutorial/ practical class can only be achieved through attending the session. Before each class you need to read carefully the question sheet and start to work on some of them as the two hour tutorial time is usually not enough for completing all the exercises. Attendance at the lectures is highly desirable as it will reflect students’ participation, performance and understanding.
You should go through the lecture notes before attending the class. Students should access vUWS and check their student email accounts at least three times per week for announcements, teaching materials, recommended readings, documents and other relevant information.
4
5
2.3 Contribution to Course Learning Outcomes
Key: (I)ntroduced (D)eveloped (A)ssured
Western Sydney University Graduate Attributes
GraduateAttributes 1 1. Command multiple skills and literacies to enable adaptable lifelong learning I
2 3 4 5 D D D D
6 7 D D
8 9 D D
10 11 I I
2. Demonstrate knowledge of Indigenous Australia through cultural competency and professional capacity
3. Demonstrate comprehensive, coherent and connected knowledge D 4. Apply knowledge through intellectual inquiry in professional or applied contexts I 5. Bring knowledge to life through responsible engagement and appreciation of diversity in an evolving world I
I D D I D D D I D D D I
I I D D I D
I D D D I I
D D D D D I
3639: Bachelor of Information and Communications Technology
Program Learning Outcomes 1
2 3 4 5 I
6 7 I
8 9
10 11 I
1. Explain the complex networks involved when dealing with people, business and government in the context of ICT D development, support and service provision.
2. Evaluate the technological and software core of ICT theory and practice analysing and designing applications
D D I
D D
3. Apply the knowledge and skills required for the development of new applications and new application areas
D
4. Innovate by keeping up to date with the rapid development in technology and practice across the ICT domain, as an extension of their current understandings and the ability to find innovative ICT solutions and move the ICT field forward.
I D
5. Perform work of high quality with an awareness of the professional code of conduct, professional and personal ethics, and the legal and social implications of technological change relating to privacy of information and professional practice.
I
6
3684: Bachelor of Information and Communications Technology (Advanced)
Program Learning Outcomes 1 2
3
4 I
5
6
7 I
8
9
10 11 I
1. Explain the complex networks involved when dealing with people, business and government in the context of ICT D development, support and service provision.
2. Evaluate the technological and software core of ICT theory and practice analysing and designing applications D
D
D D
3. Apply the knowledge and skills required for the development of new applications and new application areas
I
D
4. Innovate by keeping up to date with the rapid development in technology and practice across the ICT domain, as an extension of their current understandings and the ability to find innovative ICT solutions and move the ICT field forward.
I
D
5. Perform work of high quality with an awareness of the professional code of conduct, professional and personal ethics, and the legal and social implications of technological change relating to privacy of information and professional practice.
I
3711: Bachelor of Information and Communications Technology (Health Information Management)
Program Learning Outcomes 1 2
3
4 I
5
6
7 I
8
9
10 11 I
1. Explain the complex networks involved when dealing with people, business and government in the context of ICT D development, support and service provision within healthcare.
2. Evaluate the technological and software core of ICT theory and practice analysing and designing applications; D
D
D D
3. Apply the knowledge and skills required for the management of health information and the development of new applications and new application areas;
I
D
4. Innovate by keeping up to date with the rapid development in technology and practice across the ICT domain, as an extension of their current understandings and the ability to find innovative ICT solutions and move the health ICT field forward.
I
D
5. Perform work of high quality with an awareness of the professional code of conduct, professional and personal ethics, and the legal and social implications of technological change relating to privacy of information and professional practice.
I
2.4 Assessment Summary
The assessment items in this Unit are designed to enable you to demonstrate that you have achieved the Unit learning outcomes. Completion and submission of all assessment items which have been designated as mandatory or compulsory is essential to receive a passing grade.
To pass this Unit you must:
– Achieve at least 50% overall.
– Attend all mandatory assessments including Applied Project (students with very low participation are not allowed to attend the applied project), and Final Exam.
Item
Weight
Due Date
ULOs Assessed
Threshold
Participation
20%
Weekly in each tutorial session
1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11
No
Applied Project
30%
Friday of Week 13 at 17:00
2, 5, 6, 7, 8, 9, 10
No
Online Final Exam
50%
Formal University exam period
1, 2, 3, 4, 5, 6, 8, 9, 10
No
Feedback on Assessment
Feedback is an important part of the learning process that can improve your progress towards achieving the learning outcomes. Feedback is any written or spoken response made in relation to academic work such as an assessment task, a performance or product. It can be given to you by a teacher, an external assessor or student peer, and may be given individually or to a group of students. As a Western Sydney University student, it is your responsibility to seek out and act on feedback that is provided to you as a resource to further your learning.
In this unit you can expect feedback on tutorial exercises orally during the demonstrations. Detailed feedback will be given by the lecturer(s) during lecture sessions and upon request at the consultation hours. Further informal feedback will also be provided in lectures and tutorials.
7
2.5 Assessment Details 2.5.1 Participation
Weight:
20%
Type of Collaboration:
Individual
Due:
Weekly in each tutorial session
Submission:
In each marked tutorial/practical session
Format:
Students should demonstrate their work to the tutor before the end of each marked tutorial/practical session (ten sessions all together). Students will receive no marks if they do not attend the tutorials.
Length:
Ten 2-hour Tut/Lab sessions
Curriculum Mode:
Participation
By examining students’ understanding of materials from previous lecture(s), this weekly tutorial/practical exercise provides students with continuous feedback on how they are progressing. It also provides an opportunity for each group knowing the progress of all the members toward the completion of the group work.
Marking is based on the weekly attendance, participation to the class/group discussions, and the quantity and quality of the completed tutorial/practical work (project work and tutorial exercises).
Students need to inform the unit coordinator and the tutor before the tutorial or as early as practical if they are unable to attend a class. If their absence has been approved, they need to demonstrate their work of the missed week in the following class and the participation mark will then be issued based on the demonstrated work only.
Resources:
Check vUWS regularly for hints and information
Refer to the example at the appendix B of the book: Practical Object Oriented Analysis, Bhuvan Unhelkar, ISBN 0-17-012298
Marking Criteria:
Criteria
High Distinction
Distinction
Credit
Pass
Unsatisfactory
Attendance and participation in group discussion (60%)
Full attendance and very active participation in class and group discussions and excellent contribution to tutorial/project work.
Full attendance and active participation in class and group discussions and good contribution to tutorial/project work.
Good attendance (80% of class time) and participation in group discussions and tutorial/project work.
Attendance (more than 50% of class time) and attempt to contribute to tutorial/project work.
No or only partial attendance (less than 50% of class time) and poor participation in class activities.
Completion of tutorial exercises (40% )
Satisfactory completion of more than 85%tutorial/project work
Completion of 75~85% tutorial/project work
Completion of 65~75% tutorial/project work
Completion of 50~65% tutorial/project work
No or very limited tutorial/project work (less than 50%)
8
2.5.2 Applied Project
Weight:
30%
Type of Collaboration:
Group
Due:
Friday of Week 13 at 17:00
Submission:
Online submission via vUWS
Format:
Each project group needs to write a project report based on the group members’ work and the report template provided together with other instructions that will be published on the unit website at the vUWS. Each group will submit one copy of the project report in A SINGLE WORD FILE through the vUWS. Each group member should also submit a peer review (the form will be provided) to assess the contributions of fellow group members (including him/herself) for each task of the project. The final project mark of each member (the individual part) will be adjusted according to the peer reviews from all the group members.
Length:
1 group project, equal score for every member in the group, take 30 – 40 hours for each member to complete his/her own work (group assessment).
Curriculum Mode:
Applied Project
The Applied Project, being completed in a group environment, is to provide the team members with an opportunity to build up Object Oriented (OO) analysis models with CASE tools.
At the completion of the group assignment, a deliverables report needs to be submitted to reflect each group students’ capability of applying gained knowledge and skills in OO analysis and design throughout the semester, based on their weekly project work.
Making a Group
In the applied project, groups are formed as follows:
1. Each project group is formed by students themselves. By the end of Week 2, you need to sign up for your group with other students at the same tutorial class, with each group containing 3 to 5 members (4 is preferred).
2. Each group should inform the tutor about the formation of the group and it is not allowed to change groups after you’ve signed up unless you have strong reasons for the change and obtain the approval of your tutor.
Resources:
Check vUWS for a template, references and an example of the project.
9
Marking Criteria:
Criteria
High Distinction
Distinction
Credit
Pass
Unsatisfactory
Executive Summary and Introduction 5%
Provides excellent content with deep understanding and clarity in description of the requirements, executive summary, and introduction of the project.
Clear description and shows good understanding on the requirements of the project with a well written introductory section.
While the summary covers the main components of this section, some provided information is not comprehensive OR does not accurately refer to the case study.
The summary covers some main information of the project with some elements missed OR provides some irrelevant information.
Not provided OR provides very limited information OR the provided information is misleading or irrelevant to the case study.
Package Diagrams 5%
Provides comprehensive package description and the diagrams AND connections and notes are used thoroughly in the diagram AND the provided diagrams and documentation have little incorrect syntaxes.
Completes required package diagrams including connections and notes with minor incorrect syntaxes
Provides less than 75% required packages, diagrams and description OR connections and/or notes are missing in some diagrams OR has incorrect syntaxes.
Around 40% packages, diagrams, connections or notes are missing OR have significant syntax errors.
No or very limited packages (less than 50%) and related information are provided OR the provided package diagram(s) are irrelevant to the case study.
Actor List and Documentation 5%
Provides comprehensive and detailed actor list and documents (at least 20 actors) AND provides diagram(s) to indicate the connectivity and/or relationship among actors where necessary.
Provides more than 85% required number of actors and documents, with diagram(s) to show connectivity and/or relationship among the actors where necessary.
Provides less than 75% required actors and documents OR given actor list and documents are not comprehensive or have incorrect syntax.
Provides incomplete actors (up to 50% are missing) OR lack of documentation OR has significant incorrect syntaxes.
No or very few actors with documents are provided (less than 50%) OR the given actor list and documents are irrelevant to the case study.
Use Cases 10%
Provides comprehensive, detailed and logically sound use cases with no syntax errors, including use case thumbnail, use case description, stereotype and package, actors, pre-conditions, post-conditions, use case relationships, basic flow, alternative flow, exceptions, constraints, user interface specification, metrics, priority, status, author & history, and reference material (around 5 use cases for each package, → 20 use cases for 4 packages).
Provides required number of valid use cases with documentation including most of the details, and with correct format and little syntax errors.
Provides less than 75% use cases with reasonable details OR some main requirements are not addressed OR given use cases are not clear OR given use cases contain syntax errors.
Provides less than 65% required use cases OR misses significant details in the documentation OR have significant syntax errors OR some given use cases are irrelevant.
Not provided or majority of use cases (50% or more) are missing, OR the given use cases and documentation contain very limited information and/or irrelevant to the case study.
Use Case Diagrams 5%
Provides clear use case diagrams with related use cases in each diagram, containing all details like diagram name, notes and relationships (around 2 use cases for each package, → 8 use case diagrams for 4 packages).
Provides required number of use case diagrams based on the user cases and actors with good details.
Provides less than 75% required use case diagrams OR given diagrams are incomplete OR have syntax errors OR with unrelated use cases in the same diagrams.
Completes less than 65% required use case diagrams OR completed diagrams contain severe syntax errors and wrong format OR some diagrams are irrelevant.
Not provided OR less than 50% use case diagrams are provided OR most of diagrams are irrelevant to the case study.
Activity Diagrams 5%
Provides detailed activity diagrams showing processes and workflow clearly (with correct format and using most of ingredients when required) from above use cases and actors (1 activity diagram for each use case, → 20 diagrams for 4 packages).
Provides more than 80% required number of activity diagrams with good details, and correct format and symbols.
Provides less than 75% activity diagrams with reasonable details OR some activity diagrams are not complete and/or contain inaccuracies and syntax errors.
Completes less than 65% activity diagrams OR has significant inaccuracies and/or syntax errors.
Not provided OR provides less than 50% required number of activity diagrams OR the diagrams are irrelevant to the case study.
10
Criteria
High Distinction
Distinction
Credit
Pass
Unsatisfactory
Class Descriptions 5%
Provides excellent identification of all core classes (around 8 per package), definition of classes including attributes and operations (around 5 attributes and 5 operations for each class).
Identifies more than 80% required number of classes with definition of attributes and operations.
Provides less than 75% classes with class descriptions, OR some classes are not complete OR misses some core classes OR have inaccuracies and/or syntax errors.
Around 40% required number of classes are not identified OR lack of definition for significant number of classes.
Not provided OR provides less than 50% classes OR provides less than 2 attributes and 2 operations for most of classes OR the classes are irrelevant to the case study.
Class Diagrams 10%
Provides clear and comprehensive class diagrams to model the static view of all main system components, with details of class relationships, class stereotype, multiplicities, and notes. It is also required to show minimal two attributes and two operations for each class in the diagram. Note: a class can be used across packages. (around 4 to 6 class diagrams for 4 packages).
Provides required number of class diagrams with most of the main information including class relationship, multiplicities and notes, and attributes and operations of each class.
Provides less than 75% required class diagrams with reasonable details OR some given class diagrams are not complete OR have some inaccuracies and/or syntax errors OR lack of details.
Completes around 60% required number of class diagrams with reasonable details and without severe mistakes.
Not provided OR provides less than 50% required number of class diagrams OR provided diagrams containing severe syntax errors OR the diagrams are irrelevant to the case study.
Sequence Diagrams 10%
Provides clear and comprehensive sequence diagrams (around 1 sequence diagram for each use case), with high quality in message syntax and semantics. The message in the diagrams must consistently match with operations in classes.
Provides required number of sequence diagrams with good quality in terms of message syntax and semantics.
Provides reasonably detailed sequence diagrams but some main requirements are not addressed OR messages in the diagrams do not match with operations of classes OR given diagrams contain syntax errors OR some sequence diagrams (up to 35%) are missing.
Completes around 60% required number of sequence diagrams without severe mistakes.
Not provided OR provides less than 50% required sequences diagrams OR provided diagrams contain severe syntax errors OR the diagrams are irrelevant to the case study.
Interaction Overview Diagrams
5%
Provides comprehensive interaction overview diagrams to show all main high level interactions of the system (around 6 diagrams), without message syntax, semantics errors.
Complete required number of interaction overview diagrams with little syntax, semantics errors.
Provides around 70% required number of interaction overview diagrams with some main interactions not addressed OR given diagrams contain syntax errors.
Provides around 60% required interaction diagrams without severe syntax errors.
Not provided OR provides less than 50% required interaction overview diagrams OR provided diagrams contain severe syntax errors OR the diagrams are irrelevant to the case study.
State machine diagrams
5%
Provides clear state machine diagrams of the core objects using most of ingredients (around 6 diagrams) without message syntax, semantic errors.
Completes required number of state machine diagrams with little syntax, semantic errors.
Provides around 70% required number of state machine diagrams OR with some core objects not addressed OR given diagrams contain some syntax errors.
Provides around 60% required state machine diagrams without severe syntax errors.
Not provided OR provides less than 50% required state machine diagrams OR has severe mistakes
or irrelevant for most of provided diagrams.
Prototypes (functional prototypes) using
“mock up”screens 5%
Provides clear “mock up”screens
reflecting all the main functional requirements and
flow of the project. The fields in the
“mock up”screens are consistent with fields in classes and use cases.
Provides good quality “mock up”screens
reflecting main functional requirements and flow of the project.
Provides “mock up” screens reflecting functional requirements and
flow of the project but with some main requirements not addressed, causing one or two screens missed.
Provides “mock up” screens reflecting some functional requirements and
flow of the project, but with significant requirements not addressed, causing several main screens missed.
Not provided OR provides less than 50% number of
“mock up”screens OR the screens provided are irrelevant to the case study.
11
Criteria
High Distinction
Distinction
Credit
Pass
Unsatisfactory
Operational Requirements and environmental consideration
5%
Provides detailed description on all operational requirements including performance, volume, scalability and security AND all environmental requirements, including test environment, operational environment and any additional environmental considerations.
Provides most of relevant operational and environment requirements with good details.
Provides main operational and environmental requirements with some requirements not clearly described.
Provides majority of operational and environment requirements but with some main requirements missed OR lack of details for several requirements.
Not provided OR very limited details about the given operational and environmental requirements OR the given requirements are irrelevant to the case study.
Test 5%
Provides excellent description on quality assurance, test designs and particularly focus on testing plan AND provides comprehensive test cases corresponding to use cases AND performs exhaustive tests to two important use cases. It’s required one test case for each use case → around 20 test cases for 20 use cases with 4 packages.
Provides very good testing plan for quality assurance. Designs more than 80% required number of test cases according to use cases, with some exhaustive tests.
While test cases and quality assurance, test designs and test plan are given they are not comprehensive and incomplete (around 30% are missing) OR have inaccuracies, and/or syntax errors.
Provides less than 65% required number of test cases and related documents OR has significant inaccuracies and/or syntax errors.
Not provided OR provides less than 50% test cases OR provided test cases contain severe syntax errors OR the test cases and related documents are irrelevant to the case study.
Emerging Technologies 5%
Provides relevant and consistent emerging technologies package with all requirements and all above UML diagrams for the package.
Every member in the group should involve in this extra package.
Provides relevant emerging technologies package including above UML diagrams.
Good effort in emerging technologies package with some description in requirements and UML diagrams for the package.
Demonstrates some effort in describing emerging technologies adopted in the project.
Not provided OR provides very limited information in the emerging technologies section.
Overall Quality 10%
Content provided is excellent, well organised and presented, reflecting students’ in-depth research and discussions in finding the answers AND where appropriate proper referencing is given to the sources. Also includes project management, project plans, project time management, report writing and other extra works.
The project report is well presented based on good research for the solution with all the main components of a project.
While the provided content is good it does not show that students have conducted extensive research in souring the answers.
Provides the report with main contents and information of the project.
Poor quality from the content and solution point of view AND/OR has not carried out any additional research in sourcing the answers.
TOTAL 100%
Every group member will get the same group mark (50%). If peer reviews are received, each member’s individual mark (50%), will be adjusted accordingly based on the group performance.
12
2.5.3 Online Final Exam
Weight:
50%
Type of Collaboration:
Individual
Due:
Formal University exam period
Submission:
At the exam site or online
Format:
A paper based and closed book exam. The exam is 2 hours long including reading time (3 hours if the exam is conducted online).
Length:
3 hours
Curriculum Mode:
Final Exam
Students will get 5 written answer questions and 30 multiple choice questions, covering all teaching materials of the semester. All the written answer questions of the exam paper will use the same problem statement (may have different problem statements for different versions of the exam papers if the the final exam is conducted online). Resources:
Refer to the revision session in the lecture of week 14 and the example in the appendix C of the reference book: Practical Object Oriented Analysis, Bhuvan Unhelkar, ISBN 0-17-012298.
Marking Criteria:
Criteria
High Distinction
Distinction
Credit
Pass
Unsatisfactory
See following criteria and standards for marking examination questions.
85-100% of the solutions to examination questions are correct.
75-84% of the solutions to examination questions are correct.
65-74% of the solutions to examination questions are correct.
50-64% of the solutions to examination questions are correct.
0-49% of the solutions to examination questions are correct.
Multiple Choice Question Marking
100%The correct choice being selected.
0%An inappropriate choice or more than one choice being selected.
Written Answer Question Marking
100%Demonstrates complete and very good understanding of the problem. All requirements of the question are included in the response.
75%Demonstrates good understanding of the problem. Most requirements of the question are included in the response.
65%Demonstrates understanding of the problem. Main requirements of the question are included in the response.
50%Demonstrates partial understanding of the problem. More than half requirements of the question are included in the response.
0%Demonstrates little understanding of the problem,Almost no requirements of the question are included in the response, or not attempted.
13
2.6 General Submission Requirements Submission
– All assignments must be submitted by the specified due date and time.
– Complete your assignment and follow the individual assessment item instructions on how to submit. You must
keep a copy of all assignments submitted for marking.
Turnitin
– The Turnitin plagiarism prevention system may be used within this Unit. Turnitin is accessed via logging into vUWS for the Unit. If Turnitin is being used with this Unit, this means that your assignments have to be submitted through the Turnitin system. Turnitin from iParadigms is a web-based text-matching software that identifies and reports on similarities between documents. It is also widely utilised as a tool to improve academic writing skills. Turnitin compares electronically submitted papers against the following:
– Current and archived web: Turnitin currently contains over 24 billion web pages including archived pages
– Student papers: including Western Sydney University student submissions since 2007
– Scholarly literature: Turnitin has partnered with leading content publishers, including library databases, text-book publishers, digital reference collections and subscription-based publications (e.g. Gale, Pro- quest, Emerald and Sage)
– Turnitin is used by over 30 universities in Australia and is increasingly seen as an industry standard. It is an important tool to assist students with their academic writing by promoting awareness of plagiarism.By submitting your assignment to Turnitin you will be certifying that:
– I hold a copy of this assignment if the original is lost or damaged
– No part of this assignment has been copied from any other student’s work or from any other source except
where due acknowledgement is made in the assignment
– No part of the assignment has been written for me by any other person/s
– I have complied with the specified word length for this assignment
– I am aware that this work may be reproduced and submitted to plagiarism detection software programs for the purpose of detecting possible plagiarism (which may retain a copy on its database for future plagiarism checking).
Self-Plagiarising
– You are to ensure that no part of any submitted assignment for this Unit or product has been submitted by yourself in another (previous or current) assessment from any Unit, except where appropriately referenced, and with prior permission from the Lecturer/Tutor/Unit Coordinator of this Unit.
Late Submission
– If you submit a late assessment, without receiving approval for an extension of time, (see next item), you will be penalised by 10% per day for up to 10 days. In other words, marks equal to 10% of the assignment’s weight will be deducted from the mark awarded.
– For example, if the highest mark possible is 50, 5 marks will be deducted from your awarded mark for each late day.
– Saturday and Sunday are counted as one calendar day each.
– Assessments will not be accepted after the marked assessment task has been returned to students.
– This is consistent with Western Sydney University’s Assessment Policy
14
Extension of Due Date for Submission
Extensions are only granted in exceptional circumstances. To apply for an extension of time, locate an application form via the Western Sydney University homepage or copy the following link: https://www.westernsydney.edu.au/currentstudents/current_students/forms
Application forms must be submitted to the Unit Coordinator/Convenor. Requests for extension should be made as early as possible and submitted within policy deadlines. Appropriate, supporting documentation must be submitted with the application. An application for an extension does not automatically mean that an extension will be granted. Assessments will not be accepted after the marked assessment task has been returned to students.
Resubmission
Resubmission of assessment items will not normally be granted if requested.
Application for Special Consideration
It is strongly recommended that you attend all scheduled learning activities to support your learning. If you have suffered misadventure, illness, or you have experienced exceptional circumstances that have prevented your attendance at class or your completion and submission of assessment tasks, you may need to apply for Special Consideration via the Western Sydney University website. http://www.westernsydney.edu.au/currentstudents/current_students/services_ and_facilities/special_consideration2 or the Student Centre/Sydney City Campus Reception. Special Consideration is not automatically granted. It is your responsibility to ensure that any missed content has been covered. Your lecturer will give you more information on how this must be done.
15
16
3 Teaching and Learning Activities
Weeks
Topic
Lecture
Tutorial
Independent
Assessments Due
Week 1 08-03-2021
Fundamentals of Object-Orientation (OO) – Starting the OO Journey
OO Fundamentals: – Concepts (Class, Object, Message) – Principles Classification, Abstraction, Inheritance, Encapsulation and Polymorphism) – Modelling spaces
No tutorials in the week.
Students are expected to read Lecture note, learning guide and supplemented documents in vUWS
Week 2 15-03-2021
The Unified Modelling Language in Object Oriented Analysis
UML in a nutshell: – What comprises the UML – The purpose it serves, and – A walkthrough of 13 UML 2.0 diagrams. Project Work 1: Students to form groups of FOUR to work on the project. All actual group work will be carried out in the Tutorial sessions in the Labs
Tutorial 1
Students are expected to read Lecture note and supplemented documents in vUWS.
– Participation
Week 3 22-03-2021
Process, Prioritization and Package Diagrams
Understanding software processing – Its relevance to the UML – Iterative, Incremental, and Parallel process – The process architecture and elements: Roles, Activities, Deliverables – Specific discussion: Business analysis and Requirements Modelling process-component. + Critical Requirement Analysis for Prioritization. + Package Diagrams Project Work 2: Students should informally experiment creating these diagrams in their CASE tool – individually and in groups.
Tutorial 2
Students are expected to read Lecture note and supplemented documents in vUWS. Students are expected to practise various UML diagrams using a CASE Tool, e.g. MS Visio or Ration Rose
– Participation
17
Weeks
Topic
Lecture
Tutorial
Independent
Assessments Due
Week 4 29-03-2021
Use Case Models: Actors, Use cases and Documentation
Modelling the requirements in the form of Use cases – System scope: What and Who – Use Cases – Actors – High level UC documentation using a Template Project Work 3: Undertake Critical Requirement Analysis, Identification and prioritization of Package, Creation of an IIP Project Plan.
Tutorial 3
Students are expected to read Lecture note and supplemented documents in vUWS. Students are expected to practise package diagrams using a CASE Tool, e.g. MS Visio or Ration Rose.
– Participation
Week 5 05-04-2021
Use Case Diagrams and Activity Diagrams; UML’s Extensibility Mechanisms
– Use case diagrams – visual modelling + Placing Actors and Use cases on use case diagrams. – Creation of activity diagrams. – UML extensibility + Studying stereotypes and notes. Project Work 4: Identify Actors and Use cases based on the Problem Statement. Document them separately for each Package.
Tutorial 4
Students are expected to read Lecture note and supplemented documents in vUWS. Students are expected to practise identifying/document actors and draw actor diagrams using a CASE Tool, e.g. MS Visio or Ration Rose
– Participation
Note: Public Holidays may affect classes this week. More information will be provided on vUWS.
Note: Public Holidays may affect classes this week. More information will be provided on vUWS.
18
Weeks
Topic
Lecture
Tutorial
Independent
Assessments Due
Week 6 12-04-2021
Classes and Class Diagrams
– Revisit classes and objects – Modelling tasks: + Extract classes from use cases and activity diagrams + Model classes – define Attributes and Operations of Classes + Relate classes + Create Class diagrams Project Work 5: Create use case diagrams; Create corresponding activity diagrams. Apply stereotypes and notes to diagrams.
Tutorial 5
Students are expected to read Lecture note and supplemented documents in vUWS. Students are expected to practise creating use case diagrams and corresponding activity diagrams using a CASE Tool, e.g. MS Visio or Ration Rose.
– Participation
Week 7 19-04-2021
Sequence Diagrams; Interaction Overview Diagrams; State Machines
Modelling Interaction (in use cases/activity diagrams) – Sequence diagrams. – Interaction overview diagrams. – Modelling dynamic object states – State machine diagrams. Project Work 6: Identify classes from use case documentation and problem statement. Model classes with attributes and operations. Create class diagrams and apply multiplicities, stereotypes and notes
Tutorial 6
Students are expected to read Lecture note and supplemented documents in vUWS. Students are expected to practise identifying classes, document 1-2 classes, and draw a class diagram using a CASE Tool, e.g. MS Visio or Ration Rose.
– Participation
Week 8 26-04-2021
Interface specifications; Prototyping.
Specification of Interfaces in the problem space: – Graphic User Interfaces – Creation of navigation maps for front-ends and web sites. – Mapping sequences to Interfaces. – Prototypes as models. Project Work 7: Create sequence diagrams for sequences identified in use cases / or activity diagrams. Also, create state machines for selected object/classes from the class diagrams.
Not marked tutorial (self study for mid-term revision)
Students are expected to read Lecture note and supplemented documents in vUWS. Students are expected to revise all materials (lecture notes and tutorials) from week 1 to week 7
– Participation
19
Weeks
Topic
Lecture
Tutorial
Independent
Assessments Due
Week 9 03-05-2021
Revision
– The CLOSED book test conducted DURING LECTURE TIME. – For 80 minutes including reading time – Test the knowledge gained by the students thus far (up to Lecture 6), as well as provide them with a feedback on how they are progressing.
Tutorial 7
Students are expected to practise creating sequence diagrams using a CASE Tool, e.g. MS Visio or Ration Rose.
– Participation
Week 10 10-05-2021
Quality Assurance and Acceptance Testing
Quality management: – Quality assurance and quality control – Planning and organizing testing for units (e.g. use cases) – Writing good test cases. Project Work 8: Create interface specifications corresponding to interface actors within use cases. Create navigation maps. Create possible prototype interfaces.
Tutorial 8
Students are expected to read Lecture note and supplemented documents in vUWS. Students are expected to practise drawing
– Participation
Week 11 17-05-2021
Operational Requirements in Analysis Feedback to Intra-session Exam
Operational issues: – Performance, Scalability, Security & Volume – Their specifications during analysis work. Project Work 9: Write a mini Test Plan; Write test cases corresponding to use cases with valid and invalid input. Discuss on web technologies: – Web services and emerging technologies – Web services and modelling – Web services dynamics
Tutorial 9
Students are expected to read Lecture note and supplemented documents in vUWS. Students are expected to continue working on combining, integrating prior works and adding missing works into the provided project template
– Participation
“mock up”screens.
20
Weeks
Topic
Lecture
Tutorial
Independent
Assessments Due
Week 12 24-05-2021
Advanced Topics including Design Patterns and Final Discussion on Project
Discuss on advanced topics in O-O analysis and design including Design Patterns Discussion on Project: – Revision of project, binding and submission (together with soft copies of OO Analysis Report, UML models and Project Plans) – Sorting of outstanding issues in Project Project Work 10: Specify operational requirements; specify development environment for your project.
Tutorial 10
Students are expected to read Lecture note and supplemented documents in vUWS. Students are expected to continue working on combining, integrating prior works and adding missing works into the provided project template
– Participation
Week 13 31-05-2021
Consolidation and Preparation for final exam
Unit revision, Discussion on Final Exam. Suggested timings and markings Submission of Project Work in corresponding Lectures or Tutorials
Not marked tutorial (self study for project and final exam revision)
Students are expected to refine the project report and submit it by the end of the week.
– Applied Project
Week 14 07-06-2021
Formal Examination Period
– Online Final Exam
The above timetable should be used as a guide only, as it is subject to change. Students will be advised of any changes as they become known on the Unit’s vUWS site.
4 Learning Resources
4.1 Recommended Readings Prescribed Textbook
Daoust, Norman, UML Requirements Modeling for Business Analysts: Steps to Modeling Success
Essential Reading
Booch, G., et al, The UML User Guide, 2005, 2nd edition, Addison-Wesley, ISBN: 0321267974. This is a substantial text and should be occasionally referred to, when students (especially teams) are looking for additional and in-depth material on a particular topic.
Booch, G. et al., Object-Oriented Analysis and Design with Applications, 2007, Addison-Wesley, ISBN: 020189551X. This book outlines object-oriented methods using the Unified Modeling Language 2.0 with real applications.
Brown, D., An Introduction to Object-Oriented Analysis: Objects and UML in Plain English, 2nd edition, 2002, New York: Wiley, ISBN: 0471371378. This book is a very general and accessible introduction to Object Oriented Analysis. It contains extensive pedagogy and incorporates patient explanations, making it ideal for beginners as a complement reading material.
Craig Larman, Applying UML and Patterns: An introduction of Object- Oriented Analysis and Design and Iterative Development, 3rd Edition 2004, Addition Wesley Professional, ISBN 0-13-148906-2
Erich Gamma, Design Patterns: Elements of Reusable Object-Oriented Software, 2004, Pearson Education
Fowler, M., UML Distilled, 3rd Edition, 2004, Addison-Wesley. ISBN: 0321193687. This is a good readable book and should be referred to in addition to the course material
Garzas, J. and Piattini, M., Object-Oriented Design Knowledge: Principles, Heuristics, and Best Practices, 2007, Hershey, PA: Idea Group Pub, ISBN: 1591408962. This book is suitable for students who would like to learn more about the design perspective of OO.
George, J.F., Object-Oriented Systems Analysis and Design, 2nd edition, 2007, Pearson Prentice Hall, ISBN: 0132279002. This covers variety topics in both OO analysis and design
Ian, G., O’Callaghan, A. and Wills, A. C., Object-Oriented Methods: Principles & Practice, 3rd edition, Addison- Wesley, 2001, ISBN: 020161913X. This book is very comprehensive and informative about Object Orientation. This is suitable for deep study students.
O’Docherty, M., Object-Oriented Analysis and Design: Understanding System Development with UML 2.0, 2005, Hoboken, NJ : Wiley, ISBN: 0470092408. This book provides a thorough grounding in object-oriented analysis and design, providing authoritative and accessible coverage of object-oriented concepts, the software development process, UML and multi-tier technologies.
Unhelkar, B. (2005). Practical object oriented analysis. Southbank, Vic: Thomson Learning.
Unhelkar, B., Process Quality Assurance for UML-Based Projects, 2003, Boston: Addison-Wesley. ISBN: 0201758210. This book contains detailed discussion on the process aspect of quality. Chapter 1 for UML-based models, Chapter 3 for relevant process components, and Chapter 6 for testing are quite relevant.
Weisfeld, M. A., The object-oriented thought process, 2009, Upper Saddle River, NJ: Addison-Wesley, ISBN: 9780672330162. This book covers the foundation in object-oriented concepts and then explains how various ob-
21
ject technologies are used.
Additional Reading
Booch, G., Rumbaugh, J., & Jacobson, I. (2005). The Unified Modeling Language user guide (2nd ed.). Indianapolis, IN: Addison Wesley.
Daoust, Norman, UML Requirements Modeling for Business Analysts: Steps to Modeling Success, 2012, Technics Publications
Erich Gamma, Design Patterns: Elements of Reusable Object-Oriented Software, 2004, Pearson Education, ISBN: 1405837306, 9781405837309. (Campbelltown, Parramatta, Penrith)
22