System Design: Use Cases, Mobile Applications, and WBS Analysis

This report provides a comprehensive overview of system design, focusing on three key areas. First, it presents three use cases (UC-1, UC-2, and UC-3) detailing the registration process for business executives and individual clients, as well as a venue booking system. Each use case includes actors, triggers, preconditions, postconditions, normal and alternative flows, and exceptions. Second, the report discusses the advantages of developing a mobile application alongside a web application, highlighting cost-effectiveness, competitive edge, brand identity, faster download speed, and improved user experience. Finally, it explains the importance of a Work Breakdown Structure (WBS) in managing project activities effectively, breaking down complex tasks into smaller, measurable components. The WBS example outlines project planning, requirement analysis, system design, development, testing, and client handover.

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

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

2
SYSTEM DESIGN
Topic 1:
UC-1: registration for business executives

3
SYSTEM DESIGN
UC-2: Registration for individual
UC-3: venue booking system
Use Case ID Primary Actor Use Cases
UC-1 Clients  log in
 Payment for membership
 Booking details
Database  Verify credentials
 Registration:
system Validate credentials
Conformation email

4
SYSTEM DESIGN
UC-2 Clients log in
Payment for membership
Booking details
Database Verify credentials
Registration
system Validate credentials
Conformation email: Register details
UC-3 client Finalize the booking
select venue
provide booking details
Database Tax invoice
Available venues
System Confirmation email: tax invoice
Available venues
Use Case ID: UC-1
Use Case Name: REGISTRATION for business executives
Created By:
Date Created:

5
SYSTEM DESIGN
Actors: Client
Database
system
Description: These use case describes the registration and login process for business
executives. In order to be a member they must pay 100 dollar and share
personal information such as email address. Later the system send the
username to the members email. Clients can login into the system through
this credentials.
Trigger: The use case trigger when clients visits the system interface while looking for
venues.
Preconditions: 1. Minimum 100 attends per book is necessary for business
customers.
Postconditions: 2. clients will be able to use the application for one year after
paying 100 dollar.
Normal Flow: registration:: system will provide a username.
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: 3. Registr
ation
2.Conformation email
3.Login includes
Includes
1.Email address and password.
2.Registration details.
3.Validate credentials.
Frequency of Use: When clients want to be a member
Special Requirements: Clients’ needs to be a 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-2
Use Case Name: REGISTRATION for individual client
Created By:

6
SYSTEM DESIGN
Date Created:
Actors: Client
Database
system
Description: These use case describes the registration and login process for individual
clients. In order to be a member they must share personal information such
as email address. Later the system send the username to the members
email. Clients can login into the system through this credentials.
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: 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
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 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-3

7
SYSTEM DESIGN
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.
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.

8
SYSTEM DESIGN
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 a web application
as it offer more functionality and accuracy.
Cost effective option:
Having a mobile website is much cheaper as compared to going for a mobile app. It is
considered to be a cost effective method for reaching the targeted users.
Competitive edge:
If you have a mobile site, you can stay ahead of your competitors. Hence, mobile websites
offers a great competitive edge to your organization
Brand identity:
Mobile websites can help you stand out of the crowd. It provides you a distinct,
contemporary brand identity to your business.
Faster download speed:
As mobile sites are designed as per the mobile standards, browsing becomes faster. The
download speed is also optimal.
Improved user experience:
As mobile sites are specifically designed for hand-held devices, they can be accessed by
mobile and smartphones easily.

9
SYSTEM DESIGN
Topic 3:
Figure 1: work break down structure
The main purpose of a WBS is to reduce complicated activities to a collection of
tasks. Work break down structure is constructed to manage several actives effectively. 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. The figure 3 describes the activities which needs to be completed according
to the dependencies. The project starts with the project planning in which several activities
are conducted which are associate with scope completion, determining the stakeholder,
determine preliminary and core resources along with the project scope. Next, the
requirement analysis is conducted through critical analysis and developing the budget
(Brettin et al. 2015). Later the system design is developed through proper monitoring. This is
the most crucial phase where the whole application is constructed. After completing the
development process, the system goes through several test and finally been handed to the
clients.
Conclusion:
This report present three different aspects of system design. In the first topic three use
cases are drawn and explained properly with proper description. The second topic describes
the advantages of mobile application extend to web application. The last topic describes the
importance of WBS.

10
SYSTEM DESIGN
References:
Andrews, M., Goehring, J., Hui, S., Pancras, J. and Thornswood, L., 2016. Mobile promotions:
A framework and research priorities. Journal of Interactive Marketing, 34, pp.15-24.
Brettin, T., Davis, J.J., Disz, T., Edwards, R.A., Gerdes, S., Olsen, G.J., Olson, R., Overbeek, R.,
Parrello, B., Pusch, G.D. and Shukla, M., 2015. RASTtk: a modular and extensible
implementation of the RAST algorithm for building custom annotation pipelines and
annotating batches of genomes. Scientific reports, 5, p.8365.
Brewer, A.C., Endly, D.C., Henley, J., Amir, M., Sampson, B.P., Moreau, J.F. and Dellavalle,
R.P., 2013. Mobile applications in dermatology. JAMA dermatology, 149(11), pp.1300-1304.
Liu, Y.Q. and Briggs, S., 2015. A library in the palm of your hand: mobile services in top 100
university libraries. Information technology and libraries, 34(2), pp.133-146.
Mehdipour, Y. and Zerehkafi, H., 2013. Mobile learning for education: Benefits and
challenges. International Journal of Computational Engineering Research, 3(6), pp.93-101.
Ploderer, B., Smith, W., Pearce, J. and Borland, R., 2014. A mobile app offering distractions
and tips to cope with cigarette craving: a qualitative study. JMIR mHealth and uHealth, 2(2).
Ventola, C.L., 2014. Mobile devices and apps for health care professionals: uses and
benefits. Pharmacy and Therapeutics, 39(5), p.356.