System Modelling | Assignment

Running head: SYSTEM MODELLING
SYSTEM MODELLING
Name of the Student
Name of the University
Author Note

1SYSTEM MODELLING
Table of Contents
User Stories......................................................................................................................................2
User Goal Table...............................................................................................................................2
Use Case Diagram...........................................................................................................................3
Use Case Description.......................................................................................................................3
Class Diagram for Sub-system......................................................................................................11
Bibliography..................................................................................................................................12

2SYSTEM MODELLING
User Stories
Member: As a G!gM@n@g3rs’ member, I can query available spaces for rent so I can utilize
the place..
Acceptance criteria
1. Available spaces are displayed.
2. The duration of availability is displayed.
3. The rent is claculated
Agents: As a G!gM@n@g3rs’ agent, I can provide buildings to the company so I can contribute
in the organization.
Acceptance criteria
1. The list of the agents displayed.
2. The payment is offered.
3. The record is updated.
User Goal Table
User User Goals Resulting Use case
Member To make booking against a proposal for
space.
Submission of proposal and
submission of bookings
Agents To provide buildings and manage
interaction records.
Maintain record of interaction

3SYSTEM MODELLING
Use Case Diagram
Figure 1: Use case diagram
Source: created by author
Use Case Description
Use Case Name Management of building records
Actor Owner

4SYSTEM MODELLING
Description The person owning the company keeps a track over all the records
belonging to the building in accordance to the existing facilities,
status of location as well as payment details of lease.
Preconditions Existence of building and existence of owner.
Post conditions Considerable change in status.
Priority High
Normal Course Administrator of the system communicates with the agent.
Gets authorized for access.
Creation of every record belonging to buildings on lease.
Storage of records in system.
Change in status of individual buildings on lease.
Alternative Course Not applicable.
Includes Status change in situation where building is already occupied.
Extends Not applicable.
Assumptions Business owner has access to the whole system.
Use Case Name Sending out of requests related to fit-out
Actor Owner
Description Requests related to fit-out regarding the newly modified or the
newly acquired infrastructure belonging to the building.
Preconditions Existence of specialist.

5SYSTEM MODELLING
Existence of owner.
Existence of individual buildings.
Post conditions Request of fit out that shall be received by specialist.
Priority High
Normal Course Assessment of state related to building.
Checking of the entire register by the owner related to fit out.
Alternative Course Not Applicable.
Includes Not Applicable.
Extends Not Applicable.
Assumptions Unidentified or improper state of building.
Storage of email within the system sent by email.
Use Case Name Payment
Actor Owner
Description Payment shall be made against all of the services along with the
building rent.
Preconditions Existence of owner.
Existence of proper building and infrastructure.
Existence of specialist for fit-out.
Existence of agents belonging to real estate.
Existence of technicians.
Existence of suppliers.
Post conditions Notification of payment that shall be sent with the help of a

6SYSTEM MODELLING
beneficiary email.
Storage of every payment record within the system.
Priority High
Normal Course Inspection of services by owners.
Update of records for owner.
Update of records related to billing within the system.
Making of payments regarding the records.
Alternative Course Not Applicable.
Includes Not Applicable.
Extends Not Applicable.
Assumptions Individual changes in records updates within the system.
Use Case Name Creation of account
Actor Member
Description Members need to create account in order to access the system.
Preconditions Existence of users.
Newer details related to members that are already no present within
the records.
Post conditions Ability of members to log into the system.
Checking of available space my individual members before creation
of account.
Priority High
Normal Course Members visit the company website.

7SYSTEM MODELLING
Members provide the website with required details belonging to the
same.
Storage of information entered by the members into the system.
Alternative Course Not Applicable.
Includes Not Applicable.
Extends Not Applicable.
Assumptions Proper understanding of website by members before creating
accounts.
Use Case Name Booking related Queries
Actor Administrator
Description Asking for information by administrator related to payment, space
as well as location.
Preconditions Existence of administrators.
Existence of bookings.
Existence of history related to payment.
Existence of location regarding website.
Post conditions Display of results by the entire system.
Rejections suffered by bookings.
Authorization regarding bookings.
Priority Moderate
Normal Course System gets asked by the administrator.

8SYSTEM MODELLING
Display of results by the system in accordance to the query that has
been made.
Rejection or granting of request by the administrator.
Alternative Course Not Applicable.
Includes Not Applicable.
Extends Authorization as well as rejection.
Assumptions Privileges related to the system belongs to the Administrator.
Use Case Name Submission of Booking
Actor Member
Description Application of Member regarding the space for proposal.
Preconditions Existence of proposal shall be contracted.
Existence of a Member.
Post conditions Booking information stored within the system.
Proposal getting flagged by the system.
Priority Moderate
Normal Course Checking if the proposal is contracted by the Member.
Date and place selection.
Request related to booking getting submitted.
Alternative Course Change of place as well as date by the member.
Includes Not Applicable.
Extends Not Applicable.

9SYSTEM MODELLING
Assumptions Privileges regarding booking and checking of availability belongs to
the member.
Provision lying with member to make bookings regarding the
choice of place.
Use Case Name Proposal submission
Actor Member
Description Submission of proposal having the inclusion of description type,
potential, market as well as technology that has been used by the
member.
Preconditions Existence of member.
Postconditions Storage of proposal within the system belonging to the company.
Priority Moderate
Normal Course Logging in of the member within the system that is existent.
Proposal creation.
Submission of proposal by the member.
Alternative Course Not Applicable.
Includes Not Applicable.
Extends Not Applicable.
Assumptions Submission privileges belongs to the member.
Use Case Name Ticket management

10SYSTEM MODELLING
Actor Administrator.
Description During malfunctioning of the system, creation of ticket in an
automated manner by the existing system.
Preconditions Detection ability of malfunctioning by the existing system.
Existence or incorporation of proper sensors to detect such
malfunctions within the system that might hamper the proper
working of the system in particular.
Post conditions Creation of ticket.
Priority High
Normal Course Collection of sensor related data by the existing system.
Detection of malfunction caused to the system.
Creation of ticket by the system.
Alternative Course Collection of sensor related data by the system.
Detection of the malfunctioning caused to the system.
Creation of ticket by the administrator.
Includes Not Applicable.
Extends Not Applicable.
Assumptions Proper working of all the sensors that have been incorporated.
Correction of all the readings.

11SYSTEM MODELLING
Class Diagram for Sub-system
Figure 2: class diagram
Source: created by author

12SYSTEM MODELLING
Bibliography
Al-Khiaty, M. A. R., & Ahmed, M. (2016). UML class diagrams: Similarity aspects and
matching. Lecture Notes on Software Engineering, 4(1), 41.
Almutairi, S., Abu-Samaha, A., Bell, G., & Chen, F. (2013, October). An enhanced use case
diagram to model Context Aware Systems. In 2013 Science and Information
Conference (pp. 270-274). IEEE.
Lin, J., Yu, H., Shen, Z., & Miao, C. (2014, June). Using goal net to model user stories in agile
software development. In 15th IEEE/ACIS International Conference on Software
Engineering, Artificial Intelligence, Networking and Parallel/Distributed Computing
(SNPD) (pp. 1-6). IEEE.
Lindqvist, E., Larsson, T. J., & Borell, L. (2015). Experienced usability of assistive technology
for cognitive support with respect to user goals. NeuroRehabilitation, 36(1), 135-149.
Petre, M. (2013, May). UML in practice. In 2013 35th International Conference on Software
Engineering (ICSE) (pp. 722-731). IEEE.
Raengkla, M., & Suwannasart, T. (2013). A Test Case Selection from Using Use Case
Description Changes. In Proceedings of the International MultiConference of Engineers
and Computer Scientists (Vol. 1, pp. 13-15).
Wautelet, Y., Heng, S., Hintea, D., Kolp, M., & Poelmans, S. (2016, November). Bridging user
story sets with the use case model. In International Conference on Conceptual
Modeling (pp. 127-138). Springer, Cham.