Order from us for quality, customized work in due time of your choice.
I am sharing the assignment file instructions and also the SRS template that you have to fill the part that is purple in color include all what asked it is about software engineering for UML diagram follow this link https://en.wikipedia.org/wiki/Class_diagram
Parking Garage Requirements
on based on these requirements you have to the stuff
Topic
Parking garage program that can simulate the management of multiple parking garages
Functional Requirements
• Ticket Generation
。 Be able to generate a ticket with a unique id, parking spot number, and
entry time.
Parking Spot Management
。 Track the number of available and occupied spots
o Assign a spot to a vehicle upon entry
•
Self Parking Fee Calculation
o Calculates the parking fee based on the time a customer’s car parked Integrated Payment Processing System
o This feature will allow customers to pay their parking fees using various
payment methods such as credit/debit card, cash, mobile payments, or prepaid parking accounts
Car Removal
Allow user to remove vehicle, and trigger fee calculation
User Authentication
o Employees should be able to log in and access the system and process
payments
Generate Reports
。 A report with a breakdown of the revenue generated by month and
payment method.
o A report listing the available and unavailable spaces with details including
ticket number and entry time.
Graphical User Interface
。 Simple and easy-to-navigate GUI that allows employees to manage parking
operations
Non-functional Requirements
• Usability
•
。 GUI should be easy to use and intuitive for new users Performance
Should update parking availability fast
Handle transactions with minimal delay
what you have to do
Complete the Following Software Engineering Tasks
1. Your company has decided to utilize “best practices” in requirements elicitation and
iterative development practices. As a consequence, for the problem scenario described
above, perform a problem analysis and capture high-level requirements to be saved in a
Requirements Specification Document (in MS Word). See the SRS Template. Items 2
and 3 below will be inserted into the SRS Document.
2. Perform requirements model engineering and specify a set of essential and real use
cases describing the functionality that your business solution/system will exhibit. To
start, identify goals/sub goals, actors and their dependencies, and high-level tasks.
Perform scenario modeling and group scenarios as needed to identify essential use
cases. Using essential/real Use Case diagrams identify the following:
Actors – who/what interacts with the business solution/system?
Use Cases – what behaviors does the business solution/system exhibit?
For each use case you have identified, fill out the Use Case Specification (Description)
Template, one for each use case. Document all of the Use Case
Specifications/Descriptions using MS Word. This will become the reference listed in the
SRS, item 1.3. Use the following template for each Use Case Description.
Use Case Specification (Description) Template
Use Case ID: {This should be coded to identify the level of the use case}
Use Case Name: {Short descriptive phrase}
Relevant Requirements: * {Reference to relevant requirements document.}
Primary Actor: {Main sub-system/entity that initiates use}
Pre-conditions: {Requirements on the state of the system prior to this use being valid.}
Post-conditions: {This describes the state of the system following the successful
completion of this use. Effects on other systems and actors may also be described.}
Basic Flow or Main Scenario: {Numbered flow of events: 1 The user initiates an action
by… 2 The system responds by…}
Extensions or Alternate Flows: {This section presents variations on this use case. It
presents those use cases that have an extends relation with the current use case.}
Exceptions: {This section describes all error conditions that can arise in the use case.}
Related Use Cases: {use cases that are either usually performed just before or after the
current use.}
*Note: Establish proper requirements traceability to the Use Case requirements.
Integrate the Use Case in the template with the Requirements Specification Document.
3. Draw the UML Use Case Diagrams using a UML modeling tool of your choice. You
may also draw them by hand. Document all of the UML Use Case Diagrams using MS
Word. This will become the reference in the SRS, item 1.3.
4. Brainstorming:
Brainstorm a list of object candidates that model objects you consider key abstractions
necessary to solve the problem.
Consider the following questions:
“What do I know”? – what data will the object candidate encapsulate?
“What do I do”? – what methods (functions) will the object support?
5. Create Class Diagrams. Use the set of object candidates identified in step 4 and
develop a set of class diagrams that will document the classes and their relationships in
a more formal manner. Diagram all identified classes. This will become the reference in
the SRS, item 1.3.
6. Create Sequence Diagrams: Use the flow you have identified (in step 4) at the Use
Case and CRC level between objects and develop a set of sequence diagrams to
represent the flow of control from a given actor(s) and its execution of the methods you
have identified with your emerging model.
At the completion of this assignment you will have the following to submit:
SRS Document – Step 1
Use Case Specification Document – Step 2
UML Use Case Diagrams Document – Step 3
Class Diagrams – Step 5
Sequence Diagrams – Step 6
Comments from Customer
if you have some great requirements you can add those
I pretty much need use cases and use case diagram with detail like what’s going on
Order from us for quality, customized work in due time of your choice.