logo

ITC560 - Software Validation for XYZ Car Park System - Assignment

29 Pages4201 Words108 Views
   

Charles Sturt University

   

Internet of Things (ITC560)

   

Added on  2020-03-02

About This Document

ITC560 - In this assignment we will get to know about the validation phase of software has some typical tasks associated with it that need to be followed in the designated way. This report consists of the validation phase of the XYZ Car Parking System. A deep study was conducted over each subsystem for the XYZ car parking and prototypes of these subsystems have been represented in this report for validation.

ITC560 - Software Validation for XYZ Car Park System - Assignment

   

Charles Sturt University

   

Internet of Things (ITC560)

   Added on 2020-03-02

ShareRelated Documents
Software Validation forXYZ Car Park SystemAssessment Item 2
ITC560 - Software Validation for XYZ Car Park System - Assignment_1
Table of Contents1. Introduction..................................................................................................................................32. Statement of Goals.......................................................................................................................33. Requirements...............................................................................................................................33.1 Functional Requirements.......................................................................................................3System Administrator..............................................................................................................3Database...................................................................................................................................3Business Requirements............................................................................................................4Actors and Goals......................................................................................................................43.2 Non-Functional Requirements...............................................................................................5Scalability................................................................................................................................5Enactment................................................................................................................................5Obtainability............................................................................................................................5Reliability................................................................................................................................5Security....................................................................................................................................54. Use Case......................................................................................................................................54.1 Use Case Diagram.................................................................................................................6.....................................................................................................................................................65. UML Diagrams Prototype using Java..........................................................................................75.1 Payment handling Subsystem................................................................................................75.1.1 UML pattern Prototype for Payment Handling system..................................................75.2 Access to the Car Parking....................................................................................................105.2.1 UML pattern Prototype for Access to the Car Parking.................................................105.3 Fault Management...............................................................................................................13
ITC560 - Software Validation for XYZ Car Park System - Assignment_2
5.3.1 UML pattern Prototype for Fault Management............................................................136. Prototype Design Pattern...........................................................................................................166.1 Programming Code in Java for Payment Handling Subsystem...........................................166.2 Programming Code in Java for Access to the car parking Area..........................................196.3 Program code in Java for the Fault Management................................................................217. System Vision Document..........................................................................................................237.1 Introduction..........................................................................................................................237.2 Assumptions........................................................................................................................237.3 Design Driver.......................................................................................................................237.4 System Users.......................................................................................................................237.5 Target Environment.............................................................................................................247.6. System Requirements.........................................................................................................247.6.1 Software and Hardware Requirements.........................................................................247.6.2 Features.........................................................................................................................24Bibliography..................................................................................................................................26
ITC560 - Software Validation for XYZ Car Park System - Assignment_3
1. IntroductionAll software has lifecycle events and validation of software is one of those activities. The validation phase of software has some typical tasks associated with it that need to be followed in designated way. This report consists of the validation phase of XYZ Car Parking System. A deepstudy was conducted over each subsystem for the XYZ car parking and prototypes of these subsystems have been represented in this report for the purpose of validation. 2. Statement of GoalsThe aim of this software to validate a system design for XYZ car parking which has been createdin order to provide a user-friendly mechanism which will help customers in locating and reserving appropriate parking area in the garage for both type of customers ordinary and season ticket holders.3. Requirements3.1 Functional RequirementsSystem AdministratorPerson with this role will be allowed to access the profiles of season ticket holders along with their statistics. System Administrator will also be responsible for deciding the prices for various distinct services that will be provided to both, the registered customers and the ordinary one, for example overstays, fee for reserved interval of time etc (Richards, Adrion & Branstad, 2013).Database This is the crucial module of this system as it will contain all the data related to registered customers, parking reservations and so on. It will hold the state of each parking area, whether it is occupied or vacant. All the pricing information along with different discounts available to deserving customers will also be stored in the database such that all of this information can be easily accesses whenever required.
ITC560 - Software Validation for XYZ Car Park System - Assignment_4
Business RequirementsEvery individual or company is allowed to get registered with XYZ and they need to provide their email-id, phone number and other relevant details to get their account created. Car entry is detected through a sensor and ordinary customer gets their ticket after pressing the required button. The season ticket holder instead of pressing button will insert his/her season ticket in a slot which will be checked for its validity.Payment for car parking will only be accepted though credit card, debit card and cash. Card holders must carry one of the following card Debt/Visa/MasterEvery season ticket will only be valid for a maximum period of one year, post that holder will need to renew their ticket or get a new one.Actors and GoalsThe one who will directly interact with the software are actors which are of two kinds the one who initiates and the other who participates. Here initiators will be Ordinary CustomersCustomers holding season ticketSystem AdministratorControl deviceAnd Participants will beCar entry and exit spot sensorsCameras at different locationsDatabase3.2 Non-Functional RequirementsScalabilityThe updated software should be accessible and all the demands of customers should be met properly and timely.
ITC560 - Software Validation for XYZ Car Park System - Assignment_5
EnactmentThe action performed by the develop system should be quick as it might have to handle huge client requests on weekends.ObtainabilityThe software must be available to its customers every time they need it and if some mandatory maintenance is required it can be done in no rush hours.ReliabilityThe developed software must be very reliable as it will also generate prices according to the timeduration, so it must be very accurate otherwise customers may lose their faith in the software.SecurityThe system must be made secure from all the possible threats it might be vulnerable to, such as database which contains all the personal information of its customers should only be accessible to authorized personnel and must be secured with passwords.4. Use CaseThe XYZ car parking system consists of many subsystems in it which is Automatic Generation of tickets, Acceptance of tickets, Payment Handling, Controlling boom gates, Recording Problems in a log book, Access to the car parking, Parking fees, Fault Management and managing security. This section will discuss in details about the three subsystems which are Payment Handling, Access to the Car Parking and Fault Management. Also their prototypes will be developed using use case diagram and UML Diagrams using Java (Richards, Adrion & Branstad, 2013)..
ITC560 - Software Validation for XYZ Car Park System - Assignment_6

End of preview

Want to access all the pages? Upload your documents or become a member.

Related Documents
The Java Programming Document
|19
|2557
|43

Sequence Diagram for Collin's Car Parking System
|14
|2724
|403

Collin Parking Car Park System Name of the University
|14
|2710
|189

Object and Data Modelling: Functional and Non-Functional Requirements, Use Case Modeling, UML Domain Model Class Diagram, Activities of SDLC
|13
|2709
|467

Object Modelling: Collin’s Parking Car Park System
|19
|3250
|102

Object Modeling: Case Study of Collin’s Parking Car Park System
|11
|2133
|60