Findyourvenue System Design: Use Cases, Mobile App Advantages, WBS

This report provides a comprehensive analysis of system design concepts within the context of Scene Brokers, focusing on the Findyourvenue platform. It begins by detailing three use cases (UC-1, UC-2, and UC-3) covering registration for individual clients, registration for business executives, and the booking process, respectively. Each use case outlines actors, triggers, preconditions, postconditions, and alternative flows. The report then discusses the advantages of developing a mobile application alongside a web application, emphasizing enhanced customer engagement, data collection capabilities, NFC technology for secure transactions, and improved accessibility. Finally, the report presents a work breakdown structure (WBS) to illustrate the project lifecycle, from initiation and planning to software selection, design, testing, and client handover, providing a structured approach to project management. Desklib offers a wealth of similar resources for students.

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

1SYSTEM DESIGN
Executive summary:
This report showcase three topic which are mainly associated with Scene Brokers and the
development process of Findyourvenue. First topic is consist of three use cases and the explanation.
The second part describes the advantages of the mobile application over the web application.
Further, the third topic is associated with WBS and the explanation around it.

2SYSTEM DESIGN
Table of Contents
Topic 1:..................................................................................................................................................3
Topic 2:..................................................................................................................................................9
Topic 3:................................................................................................................................................10
Conclusion:..........................................................................................................................................11
References:..........................................................................................................................................12

3SYSTEM DESIGN
Topic 1:
UC-1: Registration For individual

4SYSTEM DESIGN
UC-2: Registration For Business executives
UC-3: Booking

5SYSTEM DESIGN
Use Case ID Primary Actor Use Cases
UC-1 Clients Booking details: occupation, add password, add Email Address,
address.
Payment for membership
log in
Database Registration: occupation, add password, add Email Address,
address.
Verify credentials
system Conformation email: Register details
Validate credentials
UC-2 Clients Booking details: occupation, add Email Address, address.
Payment for membership
log in
Database Registration: occupation, add password, add Email Address,
address.
Verify credentials
system Conformation email: Register details
Validate credentials
UC-3 client provide booking details: number of attendees, desired location,
food menu, music genres, price limit, date and time
select venue
Finalize the booking
Database Available venues

6SYSTEM DESIGN
Tax invoice
System Available venues
Confirmation email: tax invoice
Use Case ID: UC-1
Use Case Name: REGISTRATION for individual client
Created By:
Date Created:
Actors: In this use case. Three actors are located as system, database and client.
Description: It shows the registration process for individual as they need to provide
personal information in order to register into the system. Client need to share
the email address, address and add password. Later these information are
stored into the system and the systems sends a confirmation email which
consists the registration details. Clients can login through this credentials in
order to search for information.
Trigger: If any individual client want to book a venue for private functions, they must
open the web or mobile application of the Findyourvenue in order to trigger
the functions.
Preconditions: 1. Attendees limit for private functions is limited to Maximum 500.
Postconditions: 1. Free registration for unlimited time.
Normal Flow: When user will login with their credentials :: system will validate the inputs
with the information stored in the database.
.
Alternative Flows:
[Alternative Flow 1 – Not
in Network]
Forgot username or password System can resend the registration
details to the registered email.
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
1.Email address and password.
2.Registration details.

7SYSTEM DESIGN
3.Login includes
Includes
3.Validate credentials.
Frequency of Use: new user want to register
Special Requirements: Clients’ needs to be individual customer.
The desired venue location must be under the operating area of the
organization.
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.
Use Case ID: UC-2
Use Case Name: REGISTRATION for business executives
Created By:
Date Created:
Actors: In this use case. Three actors are located as system, database and client.
Description: It shows the registration process for individual as they need to provide
personal information in order to register into the system. Client need to share
the email address, address and add password. The system auto generate an
username and later these information are stored into the system and the
systems sends a confirmation email which consists the registration details.
Clients can login through this credentials in order to search for information.
Trigger: If any business executive want to book a venue, they must open the web or
mobile application of the findyotvenye in order to trigger the functions.
Preconditions: 1. Minimum 100 attends per book is essential for business
customers.
Postconditions: 2. User will be able to use the application for one year
after paying $100.
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.
Alternative Flows:
[Alternative Flow 1 – Not Forgot username or password System can resend the registration
details to the registered email.

8SYSTEM DESIGN
in Network]
Exceptions: If users search results does not return any result, system can provide the
next vacancy date available for the desired venue.
Includes: 3. Registr
ation
2.Conformation email
3.Login includes
Includes
1.Email address and password.
2.Registration details.
3.Validate credentials.
Frequency of Use: new user want to register
Special Requirements: Clients’ needs to be either business executives.
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.
Use Case ID: UC-3
Use Case Name: Booking system
Created By:
Date Created:
Actors: In this use case. Three actors are located as system, database and client.
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.
Trigger: Client must have an authenticated membership.
Preconditions: 2. Attendees limit for private functions is limited to Maximum 500.
3. Minimum 100 attends per book is essential for business
customers.
Postconditions: Minimal guarantee:
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.

9SYSTEM DESIGN
2. Use can book a venue after paying the full amount.
Normal Flow: Deliver 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.
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:
Finalize venue
Confirmation email includes
Full payment.
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.
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.
Topic 2:
There are several advantages to develop a mobile application along with the web application
as it can offer more functionality which would beneficial for any certain organization. Mobile
applications are more suitable to engage with potential customer frequently and notify the users
about different information. Business can also gather location related data and understand the
popularity of their services or products by analysing network. Addition to that, NFC technology is
embedded in mobile devices which enables secure transaction among the client and business. Other
than that, mobile application offers more accessibility and functionality over the simple web
application.
 Mobile Apps are faster
 Personalized content
 Instant Online and Offline access

10SYSTEM DESIGN
 Using device features
 Push Notifications and instant updates
 Branding and Design
 Productivity Improvement and Cost reduction
 Interactive Engagement
 Increased SEO potential for your website
Topic 3:
Figure 1: Work breakdown structure
Work breakdown structure is designed to set a baseline which must be followed throughout
the project lifecycle. Every activity is categorise in several phases depends on their dependencies.
For instance, walls cannot be painted before primer has been done. From the above figure, it is
identified that the project planning is the trigger and the development process ends after handing
over the project to client tasks (Charland and Leroux 2013). The initiation phase is associated with
defining scope, resources, stakeholders and other fundamental planning. Next the software and
platforms are selected along the resource allocation. After that, the project design is conducted
where the application is developed while considering the project scope. After developing the

11SYSTEM DESIGN
application, it is run through several testing to validate the application. Then the system will be
handed to the client.
Conclusion:
This report consist of three topics associated with Scencebroker. The first topic showcase the use
cases of the Findyoursvenue. The second topic consists description of advantages of mobile
application over the web application. The third topic presents a work breakdown structure and
explanation.

12SYSTEM DESIGN
Bibliography:
Bakshi, K., 2013, March. Considerations for software defined networking (SDN): Approaches and use
cases. In Aerospace Conference, 2013 IEEE (pp. 1-9). IEEE.
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.
Holmberg, C., Hakansson, S. and Eriksson, G., 2015. Web real-time communication use cases and
requirements (No. RFC 7478).
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.
Rumbaugh, J., Jacobson, I. and Booch, G., 2004. Unified modeling language reference manual, the.
Pearson Higher Education.
Coad, P., Yourdon, E. and Coad, P., 1991. Object-oriented analysis (Vol. 2). Englewood Cliffs, NJ:
Yourdon press.
Motiwalla, L.F., 2007. Mobile learning: A framework and evaluation. Computers & education, 49(3),
pp.581-596.
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.
Charland, A. and Leroux, B., 2013. Mobile application development: web vs. native. Queue, 9(4),
p.20.
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.
Shankar, V. and Balasubramanian, S., 2013. Mobile marketing: a synthesis and prognosis. Journal of
interactive marketing, 23(2), pp.118-129.
Marchewka, J.T., 2014. Information technology project management. John Wiley & Sons.