Southampton Solent University: Game Cafe System Design Project

Verified

Added on  2022/11/29

|17
|939
|279
Project
AI Summary
This document presents a comprehensive project on the analysis and design of an information system for a game cafe. The project utilizes various techniques, including mind maps, system context diagrams, data flow diagrams, entity matrices, entity-relationship diagrams, entity life history diagrams, user stories, use case diagrams, domain model diagrams, robustness diagrams, and state transition diagrams. It also includes a reflection on object-oriented techniques and a bibliography. The solution addresses potential weaknesses in the system design, such as internet connection failures and computer configuration issues. The project aims to provide a detailed understanding of system development methodologies and their application in a real-world scenario. This assignment is a referral assessment, indicating that the student has reworked and represented their work based on tutor feedback. The document is contributed by a student and is available on Desklib, a platform offering AI-based study tools.
Document Page
Running head: INFORMATION SYSTEM DEVELOPMENT
INFORMATION SYSTEM DEVELOPMENT
Name of student
Name of university
Author’s note:
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
1
INFORMATION SYSTEM DEVELOPMENT
Table of Contents
Mind map.......................................................................................................................2
System context diagram.................................................................................................2
Data flow diagram..........................................................................................................3
Entity matrix...................................................................................................................4
Entity relationship diagram............................................................................................5
Entity life history diagram.............................................................................................6
User stories mind map....................................................................................................7
Use case diagram............................................................................................................8
Domain model diagram..................................................................................................9
Robustness diagram.....................................................................................................10
State transition diagram................................................................................................12
Reflection on the object oriented techniques...............................................................14
Bibliography.................................................................................................................15
Document Page
2
INFORMATION SYSTEM DEVELOPMENT
Mind map
System context diagram
Document Page
3
INFORMATION SYSTEM DEVELOPMENT
Data flow diagram
It could be interpreted that there might be some weaknesses while designing the
system for the game café. Some of the common weakness could be the failure of customers to
login into the system due to the failure of internet connection. The game could be not be
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
4
INFORMATION SYSTEM DEVELOPMENT
played properly without the availability of internet connection. There could be disparity in the
booking timing and the appointment could be hampered.
Entity matrix
Staff Customer Database
updating
Internet
service
Supplies of
equipment
Staff
Customer
System
administrator

Internet service
provider

Supplier
Document Page
5
INFORMATION SYSTEM DEVELOPMENT
Entity relationship diagram
Document Page
6
INFORMATION SYSTEM DEVELOPMENT
Entity life history diagram
Some of the common weakness in this stage are the inability of the customers to access the
computers of the organisation that are not properly configured for playing the games with
ease. The computer that has been provided to the individual users could not be according the
requirements of the customers.
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
7
INFORMATION SYSTEM DEVELOPMENT
User stories mind map
Document Page
8
INFORMATION SYSTEM DEVELOPMENT
Use case diagram
As the user of the system of game café, I would like the use the system for registering for the
eSports events and then play according to the booking date.
Document Page
9
INFORMATION SYSTEM DEVELOPMENT
As the user of the system, I would like the login into the system of the organisation and then
play the fames of my choice for the allocated duration.
Domain model diagram
It could be interpreted from the domain model diagram that the user of the system have to
take permission prior accessing the system of the organisation. There is an aggregation of the
computer class, events class, charge class, and the customer class with the permission class as
all these classes are included in the permission class. The user class is in direct association
with the role class and the permission class. The usage class is aggregated with the
permission class that forms the direct association for the system.
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
10
INFORMATION SYSTEM DEVELOPMENT
Robustness diagram
Document Page
11
INFORMATION SYSTEM DEVELOPMENT
chevron_up_icon
1 out of 17
circle_padding
hide_on_mobile
zoom_out_icon
[object Object]