COMP1551 Application & Web Dev: White Lotus Yoga Studio System

This project involves the design and implementation of a web-based system for the "White Lotus" yoga studio, focusing on managing yoga sessions and online reservations. The system is to be developed using Visual Studio.NET with C# and must include functionalities for adding and removing yoga teachers, classes, and workshops, as well as enabling online reservations with user registration and session management. The design phase requires the use of UML diagrams, specifically use case and class diagrams, to document the system's architecture. The deliverables include a comprehensive report with an introduction, design documentation, screenshots, and a conclusion, alongside the application's electronic copy and source code. Additional desired functionalities, such as waiting lists and a forum, are optional. The project also requires acceptance testing and a self-assessment sheet as part of the final submission, graded based on design, implementation, report quality, and demonstration performance. This assignment contributes 70% to the COMP1551 course grade and is due on November 10, 2016.

Course: COMP1551 Application & Web
Development
Contribution: 70% of course
23: Application & Web Development -
Term 1 - MAC
PDF file required - ZIP file also
required
Greenwich Course Leader: Dr Elena
Irena Popa
Due date: 10th November 2016
This coursework should take an average student who is up-to-date with tutorial work
approximately 40 hours
Learning Outcomes:
B,C
Plagiarism is presenting somebody else’s work as your own. It
includes: copying information directly from the Web or books
without referencing the material; submitting joint coursework as an
individual effort; copying another student’s coursework; stealing or
buying coursework from someone else and submitting it as your
own work. Suspected plagiarism will be investigated and if found
to have occurred will be dealt with according to the procedures set
down by the University.
All material copied or amended from any source (e.g. internet,
books) must be referenced correctly according to the
reference style you are using.
Your work will be submitted for electronic plagiarism
checking. Any attempt to bypass our plagiarism detection
systems will be treated as a severe Assessment Offence.
Coursework Submission Requirements
 An electronic copy of your work for this coursework should be fully
uploaded by midnight (local time) on the Deadline Date.
 The last version you upload will be the one that is marked.
 For this coursework you must submit a single Acrobat PDF
document. In general, any text in the document must not be an image
(i.e. must not be scanned) and would normally be generated from
other documents (e.g. MS Office using "Save As .. PDF").
 For this coursework you must also upload a single ZIP file
containing supporting evidence.
 There are limits on the file size. The current limits are displayed on
the coursework submission page on the Intranet

 Make sure that any files you upload are virus-free and not protected
by a password or corrupted otherwise they will be treated as null
submissions.
 Comments on your work will be available from the Coursework page
on the Intranet. The grade will be made available in the portal.
 You must NOT submit a paper copy of this coursework.
 All coursework must be submitted as above
The University website has details of the current Coursework Regulations,
including details of penalties for late submission, procedures for
Extenuating Circumstances, and penalties for Assessment Offences.
See http://www2.gre.ac.uk/current-students/regs for details.
Specification
This is an individual coursework
Case Scenario
“White lotus” is a small yoga studio centre in London that offers mainly yoga classes
and workshops.
The owner of the studio employed you to create a small on line computerised system
that would aid the admin and the management of the “White Lotus” studio.
The system requires the following main functionalities:
 Managing yoga sessions functionality
 On line reservation of yoga sessions
The owner would also desire, if possible, additional functionalities (listed under
“Other Desired functionality” section).
Managing yoga sessions functionality.
The system should allow the user to dynamically add information about types of
classes/workshops sessions and their schedule. The system will allow the yoga
studio owner / manager and the yoga instructors to:
a. Add a yoga teacher to the database.
b. Add a yoga session to the database. A session is taught by a certain yoga
teacher and it can be a class or workshop.
i. A workshop is a one-off session

 It has a date, time and usually lasts between 2 and 4 hours.
 It has a description.
ii. A class is a weekly session
 It is on a certain day of the week at a specific time.
 It has a level (beginner, intermediate or advanced)
 The class usually last 60 minutes or 90 minutes.
 The capacity of a class is between 6 and 20.
 It has a short description.
A straightforward (basic) way to add a class is to set every class
session manually. In this case the manager would have to create the
instance sessions for the yoga classes one by one.
A more desired (advanced) way is to set the class once in the system
and the manager to make the classes available for a certain number of
weeks in one go.
c. Remove a workshop or a class.
d. Cancel a certain instance of a class. This would be done as a “soft delete”
The difference between removing a class and cancelling it is that in the
second case, the class will be still visible on the page, but flagged that it
has been cancelled.
e. List all the classes available in the system (from the current day onwards)
f. List all workshops available (from the current day onwards)
Online reservation of yoga sessions.
The system should allow online reservation of a particular yoga session
a. In order for somebody to be able to reserve a yoga class or workshop,
she/he would have to be registered and provide the following details:
a. Name
b. Date of birth
c. Yoga experience
d. Health issues
e. Contact details: telephone and email
b. In order to reserve a yoga class/workshop the user needs to be logged in.
Then the client should be able to see all the yoga classes and/or
workshops. The system should automatically check if there are any
spaces left before making the reservation.
The system should save in the DB who made the reservation and time
stamp it.
c. A client should be able to cancel a reservation up to 24 hours prior to the
class.
Other Desired functionality
The following are a set of functionalities desired, but not essential:
a. If a session is fully booked, a client should be able to go on a waiting list. If
there is any cancelation, the first person on the waiting list should move to
the reservation list for that class.
Clients should be able to log in and check if they are on the reservation or
waiting list
b. A forum page where members could post questions and answers.

You should attempt one (or both) of these functionalities only after you completed all
other required functionalities.
Requirements
You are required to design and implement the “White lotus” System which should
provide the required functionalities from the above case study. The system should be
implemented using Visual Studio.NET with C#. The “White lotus” owner asked you
to provide supporting design documentation for it.
1. The design must be produced by known tools such as UML (at least use case
diagrams and class diagram)
2. The application should include appropriate controls
3. The application should be validated where appropriate

Deliverables:
All deliverables are mandatory and they should include a report, an electronic copy
of the coursework application described in Part B and a demonstration.
1. The report
Please make sure that you include a title page and table of contents.
A report for the system described in the case study, including the following
sections:
 Introduction: A concise specification of what you expect your program to
do (approx. 200 words).
 The Design documentation supporting your application (such as a class
diagram in UML notation and use case diagrams). This section must also
contain an explanation of your design ( approx. 1000 words)
 Screen shots of the working program together with explanations.
 A conclusion where you state the design and implementation strengths
and weaknesses/bugs of your system (approx. 400 words).
 In the appendix include:
 User instructions if appropriate
 The source code written by you, including appropriate comments. Do
not include automatically generated code.
2. The electronic copy of your coursework application.
An electronic copy of your coursework application should be uploaded by
the coursework deadline. You will have to zip up the folder before you upload it.
NOTE: If solutions prove too big for uploading, you can delete the contents of
the Bin folder from your solution before compressing the application.

3. Acceptance testing
Please note that you are required to attend a scheduled session where you will
show your work to your tutor/assessor.
The place and the time slots for this task of your coursework will be made available
by your tutor.
4. Self-Assessment:
You will find a self-assessment sheet attached at the end of this coursework.
You are to complete this sheet and submit it with your report.
The grade that you award yourself in the self-assessment is NOT the final grade that
you will be awarded. Your coursework will still be graded by an academic member of
staff.
There are 5 marks allocated for accurate self-assessment. These marks are
available for accurately assessing how well you completed the coursework, so be as
objective as possible when completing the form.

Grading Criteria
In general the marks are awarded as follows:
 >=70% well documented work that follows the requirements both in design and
implementation to a high standard and which shows detailed critical understanding
of relevant concepts with an excellent report and demonstration.
 >=60% work that follows the requirements both in design and implementation well
and which show very good understanding of relevant concepts with a very good
report and demonstration.
 >=50% work that follows the requirements both in design and implementation
reasonably well and which show good understanding of relevant concepts with a
good report and demonstration.
 >=40% work displaying minimal functionality, and generally correct use of concepts
with a reasonable report and demonstration.
 >=30% work displaying little or incorrect functionality, and a simplistic or partially
incorrect use of concepts with a poor report and/or demonstration.
 <30% work displaying no functionality, and a simplistic and incorrect use of concepts
with a very poor report and demonstration.

Self-Assessment Sheet
(Place a tick in the box that you deem to be most indicative of the quality of the work)
Student Name :__________________________________ Student ID:__________________
% No
Attempt
to Very
Poor
Poor Fair Good Very
Good
Excellent
Managing yoga
sessions
functionality.
25
On line
reservation of
yoga sessions
25
UI 5
Other
functionalities
5
OO System Design 15
Report 10
Acceptance testing 10
Accurate Self-
Assessment
5
Totals 100
Note: You must submit this self-assessment as part of the final report. You must also bring
a copy to the demonstration. The boxes in bold are for examiner use only.