Great Deal! Get Instant $10 FREE in Account on First Order + 10% Cashback on Every Order Order Now

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

1 answer below »
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 XXXXXXXXXXPlease 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 modeling, 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 assess 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 modeling of various aspects of systems to construct quality diagrams from a case study (Learning outcome 6).

Marking criteria
CriteriaHDDICRPSFL
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 Develped use Case description is accuratley 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 ommisions

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 activitya)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

Answered Same Day Apr 19, 2020 ITC508 Charles Sturt University

Solution

Navashree answered on Apr 27 2020
144 Votes
domain model class.png
domain model class.vsdx
Custome
Stereotype
paramete
- customerNumber: String
- customerName: String
- customerPhoneNumber: String
- customerAddress: String
- walletBalance: decimal
+ addMoney(Amount): decimal
+ bookSlot(slotNo): String
Ticket
Stereotype
paramete
- ticketNo: String
- entryTime: datetime
- exitTime: datetime
- duration: decimal
- status: String
- type: String
+ bookTicket(): Null
+ checkStatus(): Boolean
+ recordTime() datetime
ParkingSlot
Stereotype
paramete
- slotNo: String
- isAvailable : Boolean
+ checkStatus(): boolean
SecurityPersonnel
Stereotype
paramete
- securityCardNo: String
- personnelName
+ checkValidity(): boolean
Visit
Stereotype
paramete
- visitTime: datetime
- minDuration: decimal
+ recordVisit(): Null
Complaint
Stereotype
paramete
- complaintDetails: String
- time: datetime
+ lodgeComplaint(): Null
Log
Stereotype
paramete
- logDetails: String
+ addLog(): Null
Ordinary
Stereotype
paramete
Fixed
Stereotype
paramete
+ renew(): Null
+ checkValidity(): Boolean
M1
M2
M3
M4
M1
M2
M3
M4
ooks
M1
M2
M3
M4
makes
M1
M2
M3
M4
Has
M1
M2
M3
M4
may have
M1
M2
M3
M4
Has
M1
M2
M3
M4
solution.docx
Title Page
Table of Contents
Introduction    3
System Requirements    4
Functional Requirements    4
Non-Functional Requirements    5
Use Case Modeling    5
Brief Use Case Descriptions    6
Detailed Use Case Description    7
Domain Class Modeling    8
System Development Life Cycle    9
References    11
Introduction
The aim of this report is to present system analysis and design details and SDLC related information for the proposed car parking information system for the Collin’s Parking. The company has around twenty car parks in the Melbourne city. The business wants to implement a suitable information system so that the day to day operations of the car parks become automated.
A car park has two types of customers, ordinary customers and fixed customers. An ordinary customer issues a short term ticket whereas a fixed customer issues ticket for a week, a month, or a year. In that case, a specific car slot in a particular car park will be allocated to a fixed user for the duration.
In a car park, there is an entry pillar. When an ordinary customer a
ives, he needs to issue a ticket. If there is a slot available, then the system records the a
ival time and generates a ticket for the customer. The customer then parks the car on the slot and leaves. If no slot is available for ordinary customers, then the display on the entry pillar will indicate that. If a fixed customer a
ives then the person needs to enter the fixed ticket on a slot on the entry pillar. The system checks whether the ticket is valid for the car park or not. If that is a valid ticket then the ticket is returned to the customer and the customer may proceed to the slot.
When an ordinary customer takes the parked bar back from a car park, then the car must go to the payment station first. There the customer needs to place their ticket on a slot having a barcode reader, the system check the departure time, calculates the parking fees and notifies the customer. The customer can make the payment using cards or cash. Once payment is verified and completed, the ticket is given back to the customer. The customer then proceeds to the exit. Once they enter their ticket on the exit gate slot, it records the departure time and the ba
ier raised for the customer. If a fixed customer needs to take his car and exit the car park, then he can directly go to the exit point. There he must insert his ticket. The system will record the departure time and return the ticket. Then it will raise the ba
ier.
Other than the customers, security personnel from third party security companies visit the car parks. Contracts are made with the security companies. Each contracts have specifications on how many daily visits to a car park must be done by a security personnel and what must be the minimum duration for each visit. These information are also entered into the system. When a security personnel visits a car park, he must enter his card a slot on the entry gate. The system will check the validity of the card, record the time of entry and will return the card. After having a round of daily visit, when a security personnel leaves a car park then he must produce the card to a slot on the exit pillar. The system will again check the validity of the card, will record the departure time and return the card to the security personnel.
The proposed information system will automate the whole process of generating tickets, accepting tickets, managing payments, controlling the boom gates, recording problems in a log book and to manage the security of a car park.
In the following sections of the report, there will be detailed information about the system requirements for the Collin’s Car Parking information system. Following the system requirement specifications, there will be system designs like use case diagram along with use case descriptions and domain model class diagram for the proposed information system. A detailed discussion on the system development life cycle will be also in the report. The...
SOLUTION.PDF

Answer To This Question Is Available To Download

Related Questions & Answers

More Questions »

Submit New Assignment

Copy and Paste Your Assignment Here