White Lotus Application Report: UML Design and Implementation

This report presents the design and implementation of a yoga studio management system, referred to as the White Lotus application. The report begins with an introduction outlining the system's purpose: to automate and streamline the operations of a yoga studio, including managing yoga sessions, t...Read More

WHITE LOTUS APPLICATION REPORT
STUDENT NAME:
9 November 2016

Contents
INTRODUCTION.........................................................................................................2
UML DESIGN..............................................................................................................2
USECASE DIAGRAM..............................................................................................2
CLASS DIAGRAM...................................................................................................4
SCREENSHOTS OF WORKING PROGRAM.............................................................6
CONCLUSION............................................................................................................ 6
APPENDIX..................................................................................................................7
1 | P a g e

INTRODUCTION
As per the scenario, the system is based on a yoga session studio. The system will
be able to perform the tasks as per the requirements. As the scenario says, it will be
able to add/edit/update yoga sessions, yoga teacher, create or update reservation
related to yoga sessions, information about workshops etc. Apart from that there will
be provision for client waiting list. The application will have a user interface to easily
access the data or create records. This will automate the entire system and make
everything very accessible and manageable. There will be other features like storing
customer information. It will also contain validation of data so that human errors,
syntax errors and format errors are avoided and records are correctly created and
stored. The application will have a database at the backend of the application. The
use of this backend is manager or admin will no longer have to remember any
information, rather it will be stored in the form of tables and also a backup of the data
can be taken to guard against any calamities. Earlier it was done manually. So after
development of this application the manual errors, record keeping and maintenance
and carbon footprint will be reduced.
UML DESIGN
USECASE DIAGRAM
The Usecase diagram is designed so as to visualize the all the actors that will
communicate with the system and the process that will be implemented into the
system. As per the requirements we see that the actors that will communicate with
the system are admin, one who will be able handle all the process, yoga instructor
who will be able to add and view information related to yoga teachers, sessions,
reservations etc. and client who will have to register (if new) and then login to view
yoga session like workshops or classes and reserve their place as per the available
schedules.
So to implement all this functionality, we have designed the following
processes:
a. Yoga teacher info: this process will help admin or yoga instructor to add
update or delete teacher info.
2 | P a g e

b. Client info: this process will help admin or yoga instructor to add update or
delete client info into the database.
c. Yoga session: this will contain all the information about yoga sessions and will
help users to add, update or delete info.
d. Schedule: this process will be designed to handle the schedule addition,
updating and deletion of the schedules related to the yoga sessions
e. Session reservation: this process will be designed to handle the reservations
and waiting list or other reports related to the yoga session.
f. Login: this process will be designed to provide a login to the actors as per the
requirement of the system.
g. Register: this process has been designed to add new client to the system
So as we see in the diagram, all the requirements have been modelled as verified as
well. This diagram will help in further designing like class diagram, sequence
diagram etc. All these diagram help the developers in designing and implementing
the system in a better way and making it sure that all the requirements have been
covered.
3 | P a g e

CLASS DIAGRAM
This diagram consists of the classes, attributes and functions that will be
implemented into the system. This diagram is designed to create a visual design of
the system on the basis of Usecase diagram. It is done so that beforehand all the
elements, their container classes and their respective functions are modelled for the
developers to refer and implement. Moreover this design ensures that further all the
operations have been added visually and if not, or some new, then they can be
added to the design rather than doing the addition on the hard coded system. If the
system is edited. The classes will be designed in accordance with the Usecase
diagram, its actors and processes. This done so that all the requirements are
correctly modelled at each phase. The diagram will show how all the classes are
connected and how data will flow between them. Also the functions related to
creation, update or other instances as per scenario. This diagram also helps in
designing the further diagram designs like sequence diagram, activity diagram, data
flow diagram etc. The classes may be associated with, inherited from or dependent
on each other. So this diagram can be seen as the model of what actually will be
coded in to the system application so fulfil user requirements. The diagram below
shows the classes, attributes and functions as per the user requirements. The
classes that added to the system are:
a. Login
b. Client
c. Yoga_teacher
d. Yoga_session
e. Yoga_workshop
f. Yoga_class
g. Reservations
h. Schedule
4 | P a g e

5 | P a g e

SCREENSHOTS OF WORKING PROGRAM
CONCLUSION
As we see in the diagrams above and in the screenshots of the working system, we
find that the system was designed as per the requirements that were stated by the
user and were then analysed to prepare model and the actual product. We firstly
designed the basic processes and users into a Usecase diagram and then further
modelled them into a class diagram before we implemented the product. Then on the
basis of these diagrams, we designed the product and tested it. All the validation,
security and controls also have been added and all the functions that were
mentioned by the user have also been designed in the diagrams as well as the in the
hard coded product. Thus this proves that there is hardly chance for the errors or
bugs to occur. All the functionality and modules were verified by running them and
analysing the output.
The strengths of the system were examined by doing the following:
1. Verification of the data on record creation
2. Implementation of functions
3. Validation of data
4. Testing of the product after implementation.
5. Analysis of the correct output.
6. User friendly GUI.
7. Consistent database
All the above things done prove that the system has strengths which are:
1. Reliability
2. Consistency
3. Completeness
4. Ease of use
5. Durability
6. Integrity
7. Security
8. Authentication
6 | P a g e

APPENDIX
In the appendix include:
1. User instructions if appropriate
2. The source code written by you, including appropriate comments. Do not
include automatically generated code.
7 | P a g e