ICT115 System Design: Venue Booking System for Scene Brokers

This report outlines the system design for "Findyourvenue," a web and mobile application for Scene Brokers, an Australian company specializing in venue bookings for corporate and private functions. The report covers three key areas: use cases for the system, an analysis of the advantages of developing a mobile application alongside a website, and a work breakdown structure (WBS) for software development. The use cases detail the registration and booking processes, identifying actors such as clients, the system, and the database, and outlining the normal and alternative flows. The discussion on mobile applications highlights benefits like direct marketing, enhanced security, personalization, and faster interaction compared to websites. Finally, the WBS illustrates the breakdown of project activities, emphasizing the importance of proper resource allocation and task dependencies for successful project completion. The report concludes by summarizing the project's goals and the tasks involved in creating a user-friendly venue booking system.

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

1SYSTEM DESIGN
Table of Contents
Introduction:..............................................................................................................................2
TASK 1: use cases.......................................................................................................................3
1. Use case list.....................................................................................................................4
2. Findyourvanue................................................................................................................4
3.2.2 Topic 2...............................................................................................................................6
3.2.3 Topic 3...............................................................................................................................7
Conclusion:.................................................................................................................................9
References:...............................................................................................................................10

2SYSTEM DESIGN
Introduction:
This report consist of three different topics which are associated with the the scene
Brokers. It is Australian company and want to develop their web application along with a
mobile application. They provide venue for parties and after developing the application user
will be able to book venue through the application. Mainly, Scene Brokers used for both
medium to large corporate functions and small to medium private functions such as
wedding receptions and birthday parties. This application will be developed for both mobile
and website.

3SYSTEM DESIGN
Topic 1: use cases
UC-1: use case diagram for REGISTRATION

4SYSTEM DESIGN
UC-2: use case diagram for BOOKING
1. Use case list
Use Case ID Primary Actor Use Cases
UC-1 Clients Registration: Input Email Address, select password.
initial payment
log in
Database Store email address
Password
Register details
system Conformation email: Register details
Verify credentials
UC-2 client provide booking details: number of attendees, desired

5SYSTEM DESIGN
location, food menu, music genres, price limit, date and
time
select venue
Finalize the booking
Database Available venues
Tax invoice
System Available venues
Confirmation email: tax invoice
2. Findyourvanue
Use Case ID: UC-1, UC-2
Use Case Name: REGISTRATION AND LOGIN
Created By:
Date Created:
Actors: Client, system and database are identified as the key actors as clients will
search and book their desired venues. The application will be able to able to
showcase the available venues. Clients and the system are the primary
actors and the database can be considered as secondary actor as it stored
information of users and booking details.
Description: This use case diagram provides the functionality which must be conducted
by identified actors. In order to book any venue, clients’ needs to register into
the system. They need to input certain personal information for
authentication purpose. These cardinals are stored into the database. They
also needs to pay 100 dollar for stay as a member for one year. The
application sends an email to the register email address with the login
information. When user login through their authenticated email address and
password, the system validate those data with the information stored in the
database.
Trigger: FindYourVenue can be used for both medium to large corporate functions
and small to medium private functions such as wedding receptions and
birthday parties. Some constraints include that for business customers the
system will deal with only approved customers who has at least 100
attendees per booking, and for individual customers the system will not deal
with very large functions, i.e., it offers venues for not more than 500
attendees per private function.
Preconditions: 1. Minimum 100 attends per book is essential for business
customers.
2. Attendees limit for private functions is limited to Maximum 500.
Postconditions: Minimal guarantee:

6SYSTEM DESIGN
1. Clients will be able to check the available venues without
finalizing any venue.
Success guarantee:
1. User will be able to use the application for one year after
paying $100.
2. Use can book a venue after paying the full amount.
Normal Flow: When the user will request for registration :: system will provide a
username.
When user will login with their credentials :: system will validate the
inputs with the information stored in the database.
Provide booking details such as number of attendees, desired
location, food menu, music genres, date and time, and price range ::
system will showcase available venues.
Finalize the venue and make payment :: send confirmation email
along with tax invoices.
Alternative Flows:
[Alternative Flow 1 –
Not in Network]
Unavailability of desired venue. System can suggest some venues
which are someway related to the
desired venue.
Forgot username or password System can resend the registration
details to the registered email.
unable to pay required payment System can offer alternative payment
methods.
Exceptions: If users search results does not return any result, system can provide
the next vacancy date available for the desired venue.
Includes: 1. Registration
2.Conformation email
3.Login includes
4.Provide booking
details.
5.Finalize venue
6.Confirmation email
Includes
1.Email address and password.
2.Registration details.
3.Validate credentials.
4.Number of attendees, desired
location, food menu, music
genres, price limit, date and time.
5.Full payment.
6.Tax invoice.
Frequency of Use: On demand as many time as required.
Special Requirements: Clients’ needs to be either business executives or individual customer.
The desired venue location must be under the operating area of the
organization.

7SYSTEM DESIGN
Assumptions: This uses cases are created while strictly following the case study and no
assumptions are used to doing so.
Notes and Issues: The use case are constructed while following the basic instruction. In order to
evaluate system like “Findyourvenue” in real life, much complex use case
functions required.
3.2.2 Topic 2
As the technology is advancing day by day websites becomes popular more than
ever. However, a new trend is uprising and getting popular along with the websites. A study
found that approximately 2.53 billion people all over the world uses smartphones
embedded with either android or ios. As the rate of smartphone user is growing, mobile
applications are getting popular among them as it provides easy accessibility,
personalization and secure connection. There are several advantages to develop a mobile
application along with a website as it can extends the business in terms of revenue,
popularity and recognition. It enables new opportunities to engage with potential customers
and earn huge amount of revenue. For instance, Facebook app has almost 4.119 billion
download only on play store.
Figure 1: smartphone user in billions
Source: (Bakshi 2013)
Market directly: mobiles applications uses the devices location in order to provide
relevant information region wise. Organization can understand their strong and weak

8SYSTEM DESIGN
influence area in terms of sells and popularity. Further, they can directly interact with the
user through mobile devices with secure connection.
Security: one of the other advantages of mobile application over the website is
secure connectivity. With the development of NFC technology, currency transaction process
can be conducted without any interfere by debit card, credit card and net banking.
Personalization: organization can personalize the user interface according to the user
preferences. Multiple mobile application provide several categories to set as prefer by the
user. Mobile application are also capable storing user information which could be useful to
understand the user’s preferences.
Faster interaction: mobile applications are 1.5 faster than website. Mobile
applications are capable of performing way faster than website. Most of the interface
structure were stored in the device which could be accessible on online and offline. While
when user type a URL, web browser send request to the server than the receives data
(Coleman, Seaton and Chuang 2015). Mobile applications are also accessible offline, for
instance, Google newsletter can be accessed offline to read news.
3.2.3 Topic 3
Figure 2: work break down structure

9SYSTEM DESIGN
The main purpose of a WBS is to reduce complicated activities to a collection of
tasks. This is important for the project manager because she can oversee the tasks more
effectively than the complex activities. Tasks must be measurable and independent, with
clearly defined limits. Every project consist of several activities and every activities needs to
be conducted properly within time in order to complete the project successfully
(Marchewka 2014). There are also situation occur where an activity cannot be initiated
before completing certain activity. For instance, it is not possible to implement css on front
end before HTML pages are constructed.
For develop the findyourvenye, there are several activities needs to be conducted
with proper resource allocation. In order to manage huge amount of activities, it is suitable
to categories them according to their dependencies. The initiation phase is involved with
project planning, cost and schedule management, scope management, task management,
resource management, risk management and quality management. This phase is very
important where the whole project timeline along with the resource allocation is planned.
The next phases follow the standard set in these phase. For software development,
technical management is essential. Before start developing the project, it is necessary to set
the platform and expertise which has the capability to perform such tasks (Charland and
Leroux 2013). After setting the hardware and software specification, project teams can start
developing the application. After complete the development process, the application must
be installed into the clients platform.
Conclusion:
This tasks is associate with the scene Brokers who want to develop a web and mobile
application named findyourvenue. The want to assist the users to search and book for a
venue as desired by them. Mainly, Scene Brokers used for both medium to large corporate
functions and small to medium private functions such as wedding receptions and birthday
parties. This report consist of three tasks. The first part showcase some use cases for the
findyourvenue system. The second part discuss about the advantages of mobile application
extend to website. The last part discuss a WBS for software development.

10SYSTEM DESIGN
References:
Bakshi, K., 2013, March. Considerations for software defined networking (SDN):
Approaches and use cases. In Aerospace Conference, 2013 IEEE (pp. 1-9). IEEE.
Charland, A. and Leroux, B., 2013. Mobile application development: web vs. native. Queue,
9(4), p.20.
Coad, P., Yourdon, E. and Coad, P., 1991. Object-oriented analysis (Vol. 2). Englewood
Cliffs, NJ: Yourdon press.
Coleman, C.A., Seaton, D.T. and Chuang, I., 2015, March. Probabilistic use cases:
Discovering behavioral patterns for predicting certification. In Proceedings of the Second
(2015) ACM Conference on Learning@ Scale (pp. 141-148). ACM.
Holmberg, C., Hakansson, S. and Eriksson, G., 2015. Web real-time communication use
cases and requirements (No. RFC 7478).
Jeng, Y.L., Wu, T.T., Huang, Y.M., Tan, Q. and Yang, S.J., 2015. The add-on impact of
mobile applications in learning strategies: A review study. Educational Technology &
Society, 13(3), pp.3-11.
Ku, I., Lu, Y. and Gerla, M., 2014, August. Software-defined mobile cloud: Architecture,
services and use cases. In Wireless Communications and Mobile Computing Conference
(IWCMC), 2014 International (pp. 1-6). IEEE.
Lu, Y., Yang, S., Chau, P.Y. and Cao, Y., 2011. Dynamics between the trust transfer process
and intention to use mobile payment services: A cross-environment perspective. Information
& Management, 48(8), pp.393-403.
Marchewka, J.T., 2014. Information technology project management. John Wiley & Sons.
Motiwalla, L.F., 2007. Mobile learning: A framework and evaluation. Computers &
education, 49(3), pp.581-596.
Rumbaugh, J., Jacobson, I. and Booch, G., 2004. Unified modeling language reference
manual, the. Pearson Higher Education.
Shankar, V. and Balasubramanian, S., 2013. Mobile marketing: a synthesis and prognosis.
Journal of interactive marketing, 23(2), pp.118-129.