ITC 508 Object Modelling
Assessment item 2
Elaboration phase
Value: 35%
Due date: 27-Apr-2018
Return date: 18-May-2018
Length: Word length 1800 to 2000
Submission method options
Alternative submission method
Task
In this assessment item, you are required to provide the detailed architecture and design of the system presented in Assessment Item 1 in report form. The total number of words should be between 1800-2000. Please note the words included in the diagrams/figures will not be counted. Amongst the information sought are answers to the following questions:
Questions you need to address are:
1. Identify and briefly describe the main functional and non-functional requirements for the major systems areas of the case study.
2. Draw a use case model for the information system. Write brief Use Case description for each Use Case in the diagram. Write one fully developed Use Case description for one of the important Use Cases identified. Select an important Use Case that is key part of the system, not a basic simple Use Case.
3. Draw a UML domain model class diagram for all systems in your chosen case study. Be as specific and accurate as possible, given the information provided. If needed information is not given, make realistic assumptions.
4. For each of the five-design activity of SDLC, list and briefly describe some specific tasks required for each design activities (i.e., describing the environment, designing application components, user interfaces, the database, and software methods.
Rationale
This assessment tasks covers the fundamental concepts of object modelling, use cases, dynamic models and has been designed to ensure that you are engaging with the subject content on a regular basis. The purpose of the assessment task is to strengthen the student's skill in developing a detailed OO design using UML notation, based on a set of user requirements. More specifically it assesses your ability to:
• Apply the concepts of object orientation methodology (Learning outcome 1).
• Analyse system requirements to determine the use cases and domain model of the problem domain (Learning outcome 3).
• Create class diagrams and dynamic models with UML notations (Learning outcome 4).
• Perform modelling of various aspects of systems to construct quality diagrams from a case study (Learning outcome 6).
Marking criteria
Criteria HD DI CR PS FL
Q1. Identify and briefly describe the main functional and non-functional requirements for the major systems areas of the case study.
(6 Marks)
a) All possible functional and non-functional requirements are identified and described for the major systems areas of the case study. a) All major functional and non-functional requirements are identified and described for the major systems areas of the case study. a) Some functional and non-functional requirements are identified and described for the major systems areas of the case study. a) Few functional and non-functional requirements are identified and described for the major systems areas of the case study. a) Functional and non-functional requirements are identified with major errors.
Q2. Draw the use case diagrams for all systems in the case study that show all actors and use cases.
(12 Marks) a) Comprehensive explanation about the role of use cases and all use case diagrams are accurate. One Fully Developed Use Case description is accurately done. a) Mostly comprehensive explanation about the role of use cases and all use case diagrams are mostly accurate.
One fully Developed Use description is done with minor omissions a) Mostly comprehensive explanation about the role of use cases and use case diagrams are mostly accurate. Minor omissions only. One fully developed use case description is done with some mistakes. a) Reasonable explanation about the role of use cases and use case diagrams are not always accurate. Some omissions only. a) Major omissions in the explanation.
Q3. Draw a UML domain model class diagram for all systems and subsystems in your chosen case study.
(6 Marks) a) UML domain model class diagram is accurate for all systems and subsystems; identified all possible domain classes and some attributes, showing logical relationships among all domain classes. a) UML domain model class diagram is mainly accurate for all systems and subsystems; identified all possible domain classes and some attributes, showing logical relationships among all domain classes.
Some omissions.
a) UML domain model class diagram is accurate for all systems and subsystems; however, domain classes and their attributes are not always accurate, logical relationships have some errors among domain classes. a) UML domain model class diagram is not always accurate for all systems and subsystems; domain classes and their attributes are not always accurate, logical relationships have some errors among domain classes. a) UML domain model class diagram have major omissions
Q4. For each of the five design activities of SDLC, list and briefly describe some specific tasks required for each design activity (i.e., describing the environment, designing application components, user interfaces, the database, and software methods.
(6 Marks)
a) All five design activities of SDLC are accurately listed and briefly described some specific tasks required for each design activity. a) All five design activities of SDLC are mostly accurately listed and briefly described some specific tasks required for each design activity a) Four design activities of SDLC are accurately listed and briefly described some specific tasks required for each design activity. a) Four design activities of SDLC are mostly accurately listed and briefly described some specific tasks required for each design activity. a) Less than four design activities of SDLC are listed and briefly described some specific tasks required for each design activity.
Major omissions in the explanation.

Presentation and clarity (accuracy, spelling, grammar, punctuation)
(5 Marks) b) Fluent writing style appropriate to the assignment with accurate grammar and spelling.
Referencing is mainly accurate and according to the APA standard
b) Mostly Fluent writing style appropriate to assignment with accurate grammar and spelling.
Referencing is mainly accurate and according to the APA standard. Most of the references are cited in the text.
b) Mostly fluent writing style appropriate to the assignment with mostly accurate grammar and spelling. Minor omissions only.
Some attempt in referencing and according to the APA standard. Few references are cited in the text.
b) Writing style not always fluent or well organised and grammar and spelling contain errors.
Tried to reference according to APA standard and only few references are cited in the text as well.
b) Writing style not fluent or well-organised, and many grammatical and spelling mistakes.
Presentation
Reports should be submitted is MS Word format, using the CSU referencing style of APA.
Diagrams can be created using any available tools.
Requirements
Students should visit and read the CSU Referencing Policy at http://student.csu.edu.au/study/referencing-at-csu
Submit your assignment via Turnitin in your specified class. Details will be provided by your lecturer during the session.
ITC508 – Case Study 1
Collin’s Parking Car Park System
Collin’s Parking operates twenty car parks in Melbourne CBD. The city administration has a requirement for a new and innovative system to control its car parks. The new system should therefore be capable to handle the day-to-day operation of each car park, which include: generate tickets (i.e. daily, weekly, monthly, and annual), accept tickets, handle payments, control boom gates, record problems in a log book, and manage security.
Detailed information on some aspects of the Collin’s Parking car parking system is listed below.
Types of customers
There are two types of customers: ordinary customers, who pay every time whenever they use the car park; and fixed customers, who pay a fixed amount in advance to park their vehicles for week(s), month(s) and year in a specific car park. It is compulsory that a fixed customer can only park their vehicles in the designated spaces which are not available to ordinary customers.
Tickets generation
Depending on the type of user, the following types of tickets can be generated: (1) a fixed ticket is issued to a name individual or company, and the contact details (i.e. name, mobile number, residential address and emergency details) is recorded. These tickets could be issued for week(s), month(s) and year with a certain expiry date.
However, an ordinary ticket is issued for a short term (i.e. daily for few hours or a complete day) stay at the car park.
Parking fees
Parking fees need to be calculated by using the following mechanism
Fixed customer
1 week 50 AUD
2 weeks 95 AUD
1 month 150 AUD
3 months 350 AUD
6 months 575 AUD
12 months 800 AUD
Ordinary customer
Early bird (during weekday’s midnight to 10 AM) 2.5 AUD per hour
Normal rate (during weekdays 10 AM to midnight) 5 AUD per hour
Early bird (during weekend’s midnight to 10 AM) 5 AUD per hour
Normal rate (during weekend’s 10 AM to midnight) 10 AUD per hour
Mode of payment
Payment at car park can only be made through Card (Master / VISA / DEBT) or Cash (50c, 1$, 2$, 5$, 10$, 20$, 50$)
Access to the Car Park
When a car approaches an entry barrier, its presence is detected by a sensor under the road surface, and a ‘Press Button’ display is flashed on the control pillar.
The ordinary customer must press a button on the control pillar, and a ticket is printed and issued. The ticket must be printed within five seconds. A ‘Take Ticket’ display is flashed on the control pillar. When the customer pulls the ticket from the control pillar, the barrier is raised. If the car park is full, no ticket is issued, and a ‘Full’ display is flashed on the control pillar.
The fixed ticket holder does not press the button, but insert their fixed ticket into as lot on the control pillar. A check is made that the ticket is valid for this car park and has not expired. If all these checks are passed, then the barrier is raised. The checks must take no longer than five seconds. A record is made of the time of entry.
Exit the Car Park
Fixed ticket holders do not have to go to the pay station, when they are ready to leave the car park, they go to the exit and insert their ticket into a slot on the exit barrier control pillar. The barrier is raised and a record is made of the time at which the ticket holder left.
Ordinary ticket holders should go to the payment station to pay for their trip. To do so, the ticket is inserted into a slot, the bar code is checked and the fees will be calculated. Upon successful payment, the customer can go to the exit and insert their ticket into a slot on the exit barrier control pillar. The barrier is raised and a record is made of the time at which the ticket holder left.
Security management
The City administration has a contract with security companies to visit the car parks at regular intervals. The contract specifies the number of visits per day to each car park and the minimum duration of each visit. When a security guard arrives in a car park, he or she puts a card into the card reader and the date and time of arrival is recorded. When the security guard leaves, he or she puts the card in again, and the departure time is recorded. (This card also allows security guards to enter and leave the car park in the same way as fixed ticket holders. However, this is not used to record the arrival and departure of security guards, as they may not be able to enter with a vehicle if there is a queue of cars at the barrier.)
Note
In case of missing information, kindly make suitable assumptions and mention them in your assignment.