Module Code : AAPP003-4-2-ISWE-T

Intake Code : UCDF1811ICT

Lecturer Name : Dr. Fatemah Meskaran
Hand Out Date : 14 February 2020
Hand in Date : 20 April 2020
System Name : Darul Ehsan Club House Management System

Student TP Number Student Name

TP054014 Balraaj Singh Gill
TP053878 Seveshvarman Naaidu Paramasivam
TP053048 Krinath Kumar A/L Rajendran
TP054028 Daevern Raj Ganendrah
TP054038 Heather Tee Chuan Yeung
Contents
1.0 Introduction...................................................................................................................................3
1.1 Objectives....................................................................................................................................3
1.2 Scope...........................................................................................................................................4
2.0 Planning & Requirements Analysis..............................................................................................5
2.1 Gantt Chart..................................................................................................................................5
2.2 Functional Requirements.............................................................................................................6
2.3 Non-Functional Requirements..................................................................................................7
2.31 Product requirements.................................................................................................................7
2.32 Organisational requirements......................................................................................................7
2.33 External requirements................................................................................................................8
3.0 Logical Design Part 1....................................................................................................................8
3.1 UML Use Case Diagram..............................................................................................................8
3.2 Class Diagram............................................................................................................................10
4.0 Physical Design............................................................................................................................11
4.1 Staff User Manual......................................................................................................................11
4.11Main Menu............................................................................................................................11
4.12 Manage Bookings................................................................................................................12
4.13 Manage Facilities................................................................................................................17
4.14 Manage Inquiries and Feedbacks........................................................................................21
4.15 View Member Charges.........................................................................................................23
4.16 Generate Summary Report...................................................................................................26
4.17 Manage Coaching Services..................................................................................................28
4.2 Member User Manual................................................................................................................32
4.21 Login Page...........................................................................................................................32
4.22 Login Successfully...............................................................................................................32
4.23 Login Failed........................................................................................................................33
4.24 Register (Member)...............................................................................................................33
4.25 Register Successfully (Member)...........................................................................................34
4.26 Register Failed (Member)....................................................................................................34
4. 27 Member Main Menu (Member)...........................................................................................35
4.28 Booking Information (Member)...........................................................................................35
4.29 Booking for facilities and services (Member)......................................................................36
4. 30 Facilities and services successfully booked (Member)........................................................36
4.31 Cancel Bookings (Member).................................................................................................37
4.32 Booking Cancelled (Member)..............................................................................................37
 4.33 View Inquiries and Feedback (Member)..............................................................................38
4.34 Add Inquiries (Member).......................................................................................................38
4.35 Add Inquiries (Member).......................................................................................................39
5.0 Implementation............................................................................................................................40
6.0 Conclusion....................................................................................................................................41
7.0 Individual Part (Balraaj Singh Gill TP054014).........................................................................41
7.1 Methodology..............................................................................................................................41
7.11 Waterfall Model...................................................................................................................41
7.12 Advantages & Disadvantages of The Waterfall Model........................................................44
7.2 Activity Diagram.......................................................................................................................44
7.21 Manage Facilities (Add)......................................................................................................44
7.22 Manage Facility (Edit).........................................................................................................45
7.23 Manage Facility (Delete).....................................................................................................46
7.24 Manage Inquiries and Feedback..........................................................................................47
7.3 Testing.......................................................................................................................................48
7.31 Component Testing..............................................................................................................48
7.32 Testing Script.......................................................................................................................48
8.0 Individual Part (Krinath Kumar A/L Rajendran TP053048)..................................................49
8.1 Spiral Methodology...................................................................................................................49
8.21 Inquiries and Feedback.......................................................................................................51
8.22 Daily Generate Summary.....................................................................................................52
8.23 Weekly Generate Summary..................................................................................................53
8.24 Monthly Generate Summary................................................................................................54
8.3Testing........................................................................................................................................55
Testing Scripts.................................................................................................................................55
9.0 Individual Part (Heather Tee TP054038)...................................................................................57
9.1 UML Class Diagram..................................................................................................................57
Main Activity Diagram................................................................................................................57
9.2 Methodology..............................................................................................................................59
9.21 Incremental development.....................................................................................................59
9.12 Justification.........................................................................................................................60
9.3 Testing.......................................................................................................................................61
9.31 Acceptance Test...................................................................................................................61
9.32 Test Scripts..........................................................................................................................61
10.0 Individual Part (Seveshvarman Naaidu TP053878)................................................................62
10.1 Logical Design Part 2..............................................................................................................62
 10.11UML Activity Diagram.......................................................................................................62
Manage Available Services (Add)...............................................................................................62
Manage Available Services (Edit)...............................................................................................63
Manage Available Services (Delete)............................................................................................64
10.2 Methodology............................................................................................................................65
10.21 Reuse-oriented software engineering.................................................................................65
10.22 Justification and Phases....................................................................................................65
10.3 Testing.....................................................................................................................................66
10.31 Integration Testing.............................................................................................................66
10.32 Testing Scripts...................................................................................................................66
11.0 Individual Part (Daevern TP054028).......................................................................................67
11.1 UML ACTIVITY DIAGRAM.................................................................................................67
11.2 Methodology............................................................................................................................70
11.3 TESTING................................................................................................................................73
11.31 Test script..........................................................................................................................74
12.0 Prototype....................................................................................................................................75
13.0 References..................................................................................................................................76
1.0 Introduction
In this era of technological advancement, it is critical that every business should have a
reliable system that will help manage the daily task of employees in order to increase
productivity and efficiency of a specific business. Darul Ehsan Club House offers its
residents with facilities such as training courses for various sports. Residents can request for
available time slots for booking and coaching services, required charges and others.
However, The Club House manages their daily operations by using hardcopy and filing
system which is then entered into computer files such as Excel sheets for recording purposes.
This approach is not efficient to manage an increasing workload as these matters could not be
handled properly. Nevertheless, a new management system has been requested by the Club
House to tackle the issues mentioned.

1.1 Objectives

The new management system aims to be able to manage data more efficiently and to try to
reduce data redundancy. This new management system will be able to manage the available
facilities and services for the clubhouse. Staff will be able to add new bookings, edit or delete
new bookings and search for any bookings made previously. This will be able to help staff
manage residents’ requests for inquiries on available facilities and coaching services.
Furthermore, this new system will also be able to generate summary reports for daily,
weekly, or monthly booking and coaching services. Moreover, efforts to increase the security
of the new management system will also be implemented. All staff will be required to login
into the management system to prevent any theft of data. New staff will be required to create
a new user account in order to use the management system.

Residents as well have their own management system in which they are required to register
as a member and login before using it. Residences can view or search available facilities and
services and their respective charges. If there are any facilities available, they can book them
and if they change their mind, they can cancel the booking made. Lastly, residents can also
make an inquiry on available facilities and services and provide their feedback on any issues
that they have.
 1.2 Scope

The scope of an activity, project or procedure represents their limitations or defines the
boundaries of its application. The development of this system is to create an efficient system
for the Club House. In this system, we will have two main users who are the staff and
residents. We will need these deliverables:

Staff:

1.     Login into the system

2.     Create new user profiles

3.     Manage services and facilities

4.     Manage residents requests for instance inquiry, booking or coaching service

5.     Generate summary reports for daily, weekly, or monthly booking and coaching service.

Residents:

1.     Register as a new user, which will be classified under member/resident

2.     Login into the system

3.     View or search available facilities and services and their respective charges

4.     Book facilities and services

5.     Cancel any bookings made

6.     Provide feedback on related issues

2.0 Planning & Requirements Analysis
2.1 Gantt Chart

GANTT CHART
We started our assignment on March 18, 2020. Krinath, Balraaj and Heather did the
introduction. Then, for planning & Requirement Analysis was completed by Balraaj,
Varman, Daevern. Moreover, Varman, Krinath and Heather did logical design
part1.Implementation was done by Varman, Krinath and Daevern. For Part B, everyone had
participate in doing the Methodology, Testing, and Logical Design Part 2 as it was an
individual assignment. The whole assignment took an estimate of 30 days to complete.
2.2 Functional Requirements
Functional requirements describe ways a product must behave. The functional requirements
for this system are:

 Users shall be able to login to their accounts

 Certain users should be able to create new accounts for new users
 Users shall be able to manage the available facilities and the services for the
clubhouse
 Users must be able to manage residences’ requests such as inquiries, bookings, and
coaching services.
 The system should create summary reports daily, weekly, or monthly bookings and
coaching services.
 Users shall be able to create a new account as a member
 Users shall be able to view or search for the available facilities and services and the
respective prices for all of them
 Users shall be able to book the available facilities and services.
 The users shall be able to cancel bookings made
 Users shall be able to make inquiries or provide feedback on the related issues
 Users shall be able to see the available courts for the sport using the day, time, type of
sport, and the type of service they are looking for
 Users shall be able to cancel their bookings by selecting the type of sport, service,
day, and time
 Users shall be able to write down their inquiries
 Users shall be able to view the charges, which will be split into different criteria
which will also show the status of their payment
 Users shall be able to search and cancel bookings using Member IDs, which will
show detailed information about the booking made
 Users shall be able to edit the customer bookings
 Users shall be able to view customer charges and calculate the price
2.3 Non-Functional Requirements
2.31 Product requirements
1. The system can be accessible to several staffs concurrently spread all over the Darul
Ehsan Club House area during regular working hours. If the system crashes under
unexpected circumstances, the reboot time must not exceed more than one minute in
order to avoid unnecessary downtime during regular working hours.

a) The server that host the system must perform a stable operating system, that is either
Windows Server or Linux variant, such as Ubuntu, is ideally used to run servers in order
to reduce the chances of downtime.
b) The data should also be backed up on a regular basis to reduce the cumulative data loss.
c) Where power failure occurs, a power supply shall operate the server to prolong the
operating time and reduce the risk of losing of data loss in case of a short circuit.
d) The server must also have adequate resources to manage at least ten simultaneous
connections in Darul Ehsan Club House from various computers.

2.32 Organisational requirements

1. Users set in the system only be able to use the system service after they have
registered themselves with a validation from the administration.

2. Residences could view the facilities and services reservation schedule to decide when
they would be unoccupied.

a) Residences are not allowed to book during their chosen time to utilize the facilities
and services.

3. Residences could use the inquiry form to send a message to the club house
representatives.
2.33 External requirements

1. No personal information about library system of members shall be disclosed to other

parties except system administrators.

a) The system must comply to the requirements on data privacy as it is cited in the 2010
Personal Data Protection Act of Malaysia (Act 709) regarding the use of any software
tools.
b) A warning message will therefore be sent to higher authorities in the administration
immediately for investigation if the private information of any residences or
residences' data in the database are altered or copied. (Cheah, 2019)

3.0 Logical Design Part 1

3.1 UML Use Case Diagram
Figure 1: UML Use Case Diagram
The diagram above shows the UML use case diagram for the Darul Ehsan Club House
Management system. There are 2 main actors for Darul Ehsan Clube House Management
System which are the members and the staff. Members are allowed to register as a member,
log in as a member, make bookings, cancel their bookings, view and search available
facilities and services, view their charges and make inquiries and provide feedback. However,
staff are allowed to register as staff, login as staff, make bookings for members, cancel
bookings for members, view and search for available facilities and services, view member
charges, edit bookings and manage inquiries and feedbacks. Furthermore, staff can also add,
edit and delete the available services in the Darul Ehsan Club House Management System.
Moreover, the staff can also add, edit, delete the available facilities. Lastly, staff can also
generate daily, weekly and monthly report.
3.2 Class Diagram

The UML Class Diagram above , shows the relationship between the staff, members and facilities. a person can be either an employee, member or coach. then a

member can make an inquiry about the facility or make a booking. Furthermore, when booking a facility, the member also have an option to book a coach to train

them, the coaching can either be individual or group coaching. For each sport, being Batminton, Squash and Table Tennis , 1 coach is provided .
4.0 Physical Design
4.1 Staff User Manual
4.11Main Menu

Figure 4.2: Staff Main Menu Page

When a user logs in as a staff, they will be redirected to the Staff Main Menu as shown in the
figure above. This will enable the staff to navigate through the Darul Ehsan Club House
Management System. They will be able to see six buttons which opens up new forms when
they are selected. They can manage bookings, manage facilities, manage inquiries and
feedbacks, view member charges, generate summary, manage coaching services and log out
from the system.
4.12 Manage Bookings

Figure 4.3:Member Booking Information Page

If the staff clicks manage bookings in the staff main menu page, they will be redirected to the
customer booking information page which can be seen in the above figure. This page
contains three buttons which enables the staff to make member bookings, cancel member
bookings, edit member bookings and go back to the staff main menu.
 Figure 4.4: Make Member Bookings Page

When the staff clicks the Make Member Bookings button, they will be navigated to this page.
This page enables the staff to search, view and make bookings for members who wants to
make a booking but are unable to. The staff will be able to fill out the required fields based on
the information given by the members such as their Member ID, the day they want to book
the facility and service, the time they want to book the facility or service, the sport they want
to play and if they require a coaching service. Once the details have been filled out, the staff
needs to click the search button to view all the available courts based on the details given by
the members. All available courts will be listed in the list box. The staff can then select the
court and press book.

Figure 5.4: Booked Successfully

Once the staff press Book, a message box will appear to notify the staff that the booking has been
made. Once the booking has been made, the staff can click Back to go back to the Member Booking
Information page.

Figure 4.5: Cancel Member Booking

If the staff clicks the Cancel Member Booking button in the Member Booking Information
page, they will be navigated to this page. This page allows the staff to cancel bookings made
by members. Upon entering this page, the staff is required to search for the Member’s ID in
order to view all the current bookings made by the member. The staff can then select the
booking the member wishes to cancel in the Select Booking Made field. The field will show
all the current bookings that are made by the member. Once the booking has been selected,
the date, time, sports, coaching service and selected court details will be automatically filled
based on the booking selected to give a better view for the staff to see the details. The details
in textbox are not editable. The staff can then press delete to cancel the booking made.
 Figure 4.6: Deleted Successfully

Once the staff press Delete, a message box will appear to notify the staff that the booking has
been deleted. Once the booking has been deleted, the staff can click Back to go back to the
Member Booking Information page.

Figure 4.7: Edit Member Bookings

When the staff clicks the Edit Member Booking button in the Member Booking Information
page, they will be navigated to this page. This page allows the staff to edit bookings made by
members. Firstly, the staff is required to input the Member’s ID and press search in order to
view all their current bookings made. The staff can then select the booking the member
wishes to edit in the Select Booking Made field. Once selected, the date, time, sports,
coaching service and selected court details will be automatically filled. The details within the
textbox for day, time, sports and coaching service are editable.
 Figure 4.8: Edited Member Booking

The staff can then change the details such day, time, sports and coaching service based on the
member’s request and press search to view the available courts for the edited details. Once
the available courts are shown, the staff can then select any of the courts shown. Once this is
done, the staff then needs to press Update. The Update button will update details such as the
day, time, sports, coaching service and selected court.

Figure 4.9: Updated Successfully

Once the staff press Update, a message box will appear to notify the staff that the booking has
been updated. Once the booking has been updated, the staff can click Back to go back to the
Member Booking Information page.
4.13 Manage Facilities

Figure 4.10: Manage Facilities Page

The Manage Facilities page can be accessed by staff by pressing Manage Facilities in the
main page. This page allows the staff to add, delete and edit the facilities name and type. All
the current facilities of the club house are shown in the list box.
 Figure 4.11: New Facility Added

A facility can be added by pressing the Add button. This will add a new facility within the list
box.

Figure 4.12: Facility Added

Naturally, after clicking the Add button, a message will also show the staff that a new facility
has been added in the list box.
 Figure 4.13: Editing Facility Name

The staff can then edit the facility name and type. Once entered, the staff is required to press
Save Changes to update the facility list.

Figure 4.14: Facility Saved

Once clicked, a message will show that the facility has been saved successfully.
 Figure 4.15: Changes Made in Facility List

The facility will then automatically be updated in the facility list. A facility can be deleted by
pressing the Delete button. This will remove the facility from the facility list.

Figure 4.16: Facility Deleted

Once the Delete button is clicked, a message will show that the facility has been deleted
successfully from the list. The staff can then leave the Manage Facilities page by clicking
Back to go back to the staff main menu.
4.14 Manage Inquiries and Feedbacks

Figure 4.17: Manage Inquiries and Feedback Form

When a staff clicks the Manage Inquiries and Feedbacks button in the staff main menu, they
will be navigated to this page. This page shows all the inquiries and feedbacks sent by the
members and enables the staff to reply to them. The list box contains all the inquiries and
feedback sent by members. When an inquiry or feedback is selected, the Member ID, Name,
Subject and Inquiry fields will automatically be filled with the contents of it.
 Figure 4.18: Replying to a Feedback

The staff will be able to reply to the feedback or inquiry by typing an answer in the reply
field. The staff will then be able to send it back to the member by clicking the Send Reply
button.

Figure 4.19: Reply Sent

When a reply is sent, a message box will indicate to the staff that the reply has been sent to
the member. The staff can then click the back button to go back to the staff main menu.
4.15 View Member Charges

Figure 4.20: View Member Charges Form

When the staff clicks the View Member Charges button, they will be navigated to this page.
This page enables the staff to search and view member charges. The staff is required to search
for the Member’s ID to view the charges of the member. Once searched, the staff can view all
the charges of the customer based on the month. Once the month has been selected, the
facility fee, coaching fee, and member fee will be automatically filled with the amount
needed to pay by the member by the end of the month.
 Figure 4.21: Total Charges Calculated

The staff will be able to calculate the total amount needed to pay by the member by pressing
calculate total.
 Figure 4.22: Balance Calculated and Status Added

Once the staff receives payment from the member, they are required to type in the amount
paid. The staff is then required to click Calculate Balance to get balance amount. Once the
staff receives payment, they are required to type in “Paid” as the status. If the member has not
paid the charges, the status will be “Unpaid”.

Figure 4.23: Bill Saved

When the staff clicks Save, a message will appear indicating that the bill has been saved. The
customer can then click back to exit the form.
4.16 Generate Summary Report

Figure 4.24: Daily Summary Report

The staff will be redirected to this page when they click Generate Summary Report from the
staff main menu. Staff can generate three types of reports which are Daily, Weekly and
Monthly. If they select daily, the staff may choose the specific date for the report using the
date time picker.
 Figure 4.25: Weekly Summary Report

If the staff selects weekly, they can choose the month and the week of the month of the
report.

Figure 4.26: Monthly Summary Report

If the staff selects monthly, they can choose a specific month they want to generate a report
for. When they are done writing a report, they can click Generate Summary to generate the
report.

Figure 4.27: Generated Report Successfully

When they click Generate Summary, a message will appear to indicate that the report has
been generated successfully.
4.17 Manage Coaching Services

Figure 4.28: Manage Coaching Services Page

The Manage Coaching Services page can be accessed by staff by pressing Manage Coaching
Services in the main page. This page allows the staff to add, delete and edit the coach name
coach type, sports and phone number. All the current coaching services in the club house are
shown in the list box.
 Figure 4.29: New Coach Added

A coach can be added by pressing the Add button. This will add a new coach within the list
box.

Figure 4.30: Coach Added

After clicking the Add button, a message will also show the staff that a new facility has been
added in the list box.
 Figure 4.31: Editing Coach Details

The staff can then edit the coach name, coach type, the sports the coach specializes in and
their phone number. Once entered, the staff is required to press Save Changes to update the
coach list.

Figure 4.32: Coach Saved

Once clicked, a message will show that the coach details have been saved successfully.
 Figure 4.33: Change Made to Coaches List

The coach will then automatically be updated in the facility list. A coach can be deleted by
pressing the Delete button. This will remove the coach from the coaches list.

Figure 4.34; Coach Deleted

Once the Delete button is clicked, a message will show that the coach has been deleted
successfully from the list. The staff can then leave the Manage Coaching Services page by
clicking Back to go back to the staff main menu.
4.2 Member User Manual
4.21 Login Page

Figure 4.35 Login Page

The Login Page is the first page of this Darul Ehsan Club House Management System. In
here, users should be able to log in by inserting their UserID, Password and choosing their
roles to sign in this system.
4.22 Login Successfully

Figure 4.36 Login Page

This message shows that the users entered their information correctly. Therefore, this page
will bring to Member Main Menu after the resident login in or for the staff will bring to Staff
Main Menu.
4.23 Login Failed

Figure 4.37 Login Page

This message shows that if the member entered their credentials incorrectly. Therefore, this
page will not bring them to the following page.

4.24 Register (Member)

Figure 4.38 Register Page

In this Register Page, new users redirect to here to create a new account into this system for
authorized access. This page can be opened through a register button from the Login Page.
4.25 Register Successfully (Member)

Figure 4.39 Register Page

This message shows that the user has registered successfully.

4.26 Register Failed (Member)

Figure 4.40 Register Page

This message will show if the user has not registered successfully. Therefore, the user should
fill up all in the textboxes to register into this system.
4. 27 Member Main Menu (Member)

Figure 4.41 Member Main Menu

After the member login in the system, Member Main Menu will display. This page consists
of 3 main functions for the member to do within the system which can navigate from here. A
Log out button is provided to allow the member to log out from this system.
4.28 Booking Information (Member)

Figure 4.42 Booking Information Page

This page will show up after clicking the Booking Information button in Member Main
Menu. This page consists of 2 functions for the member to do within the system and a back
button to brings them to member main menu.
4.29 Booking for facilities and services (Member)

Figure 4.43 Booking for Facilities and Services Page

This page allows the member to book the facilities and services by choosing the Day, Time,
Sports and Coach service that they desire. Member should click the search button to view all
the available courts therefore, the member can choose courts that they wanted to book.

4. 30 Facilities and services successfully booked (Member)

Figure 4.44 Booking for Facilities and Services Page

This message shows that the member has booked successfully.

4.31 Cancel Bookings (Member)

Figure 4.45 Cancel Bookings Page

In this page, the member can cancel the booking by clicking the “Select Booking Done” to
display all their previous bookings. Therefore, the member can pick the booking that they
wanted to cancel. After the member choosing the unwanted booking, all the information will
show up in the textboxes to make it easier for them to see before they click “Delete” to cancel
the booking.

4.32 Booking Cancelled (Member)

Figure 4.46 Cancel Bookings Page

The “Booking Cancelled” message will display once the member cancelled the booking.
4.33 View Inquiries and Feedback (Member)

Figure 4.47 View Inquiries and Feedback Page

View inquiries and Feedback Page can be accessed from the Member Main Menu. All list of
submitted inquiries are displayed in the listbox at the left side. Details about inquiry,
including reply from admin, will display at the right side. An inquiry can be added by
accessing Add Inquiry Page by selecting Add Inquiry button.

4.34 Add Inquiries (Member)

Figure 4.48 Add Inquiry Page

This Add Inquiry Page is only accessible by member to submit or make inquiries.
4.35 Add Inquiries (Member)

Figure 4.49 Add Inquiry Page

The “Sent” message will display once the member submits their inquiries to staff.
View Charges (Member)

Figure 4.50 View Charges Page

This page allows the member to check the status of their payment by selecting the month. All
the member’s payment information will be displayed based on the month they selected
therefore; the member will know.
5.0 Implementation
The programming language that had been implement in this whole prototype of the full Darul
Ehsan Club House Management System was conducted in Visual Basic .NET. the aim of
using VB .NET is to style the full system is because it is not a problem during the prototyping
process. we will edit every single function that we would like to feature on inside the
prototype, and with no limitation like some function cannot be implement inside the
prototype. So, to let the prototype feels like a whole system, we plan to use Visual
Basic .NET.

Nonetheless, for the real system, we are going to host an Apache web server with Python
which uses Solaris Server as the OS, that will allow multiple concurrent connection from the
various users at the same time. The recommended specification for the server constituent is as
follows:

 Internet: High – speed Gigabit Ethernet Connection

 CPU: Intel Corei5
 RAM: 4 GB
 Storage: 512 GB SSD

The server connection is going to be routed through the network switch with proper firewall
configuration and an online application firewall to stop attacks on the entire Darul Ehsan
Club House Management System network infrastructure. The connection also will be directed
through a DDOS protection service to cut back downtime of the system thanks to an
incursion of hostile traffic.

System user’s we'll be advice to use the latest version of Google Chrome, safari or Mozilla
Firefox because, the system made use of HTML5 and JavaScript to supply the most effective
and efficient experience for the user and requires a decent browser to manage the system.

The software that had been implemented within the whole Darul Ehsan Club House
Management System can allow users to login as member or staff. Member are
allowed to make booking and enquiries for whole Darul Ehsan Club House Management
System facilities, and coach services, view and edit booking history, cancel booking, and
consider facilities and respective services. Otherwise, staff are allowed register/create an
account, manage enquiries, facilities, coaches’ services, and close and open the
service slot additionally.

6.0 Conclusion
There are some limitations Darul Ehsan Club House booking system design that was created
and implemented. To access the program, the Darul Ehsan Club House management system
needs a modern browser such as Microsoft Edge or Google Chrome otherwise the server
must update manually. During the prototyping phase there are certain challenges that had
faced. The program must ensure all the features are functional such as the calculations of the
View Member Charges which can calculate the total cost of the use of Facilities and Services.
To make the prototype work well, further implementation will be done by using HTML,
PHP, and JavaScript, and therefore become a real web-based system feature. The prototype
can be changed by adding some features to make it easier to use and more user-friendly. Most
importantly, users don’t always have to access the program on their web server, they can
even view the facilities via the network without constantly on the web server.

7.0 Individual Part (Balraaj Singh Gill TP054014)

7.1 Methodology
7.11 Waterfall Model
Waterfall model is a software process model where each phase is required to be completed
before it moves on to the next phases as there are no overlapping in the phases. For the
development of the prototype for the Darul Ehsan Club House Management System, I have
proposed to use the Waterfall model as the software process model to be based upon. The
Waterfall Model is a plan-driven model. The process of developing a software is separated
into distinctive phases which are requirement analysis, system design, implementation,
integration and testing, deployment of system and maintenance. The result of one phase will
be the input for the following phase sequentially. The Waterfall Model is a sequential plan
process in which progress is viewed as flowing down steadily. (ToolsQA, 2016).
The following is the sequential process of the waterfall model:

Figure 35: The Waterfall Model

Phase 1: Requirement analysis

As requirement analysis is the first phase of the waterfall model, it is also the first phase that
we must go through to start the Darul Ehsan Club House Management system. This stage
requires us to know the tools required for us to design the system and to know the functional
attributes of the system. For example, the functional requirements and non-functional
requirements for the system are recorded. Furthermore, a GANNT Chart was also created at
the beginning of the project to roughly estimate the time required for us to complete the
project for us to meet the deadline.

Phase 2: System Design

The second phase is system design and it was carried out in the project by first creating a
logical design for the Darul Ehsan Club House Management system. A use case diagram,
activity diagram and a class diagram were drawn based on the functional requirements of the
Darul Ehsan Club House Management System. Based on the logical design, a physical design
could be created to show how the prototype should look like at the end of the project. The
design helps to show how the system will be implemented such as the hardware and software
requirements.
Phase 3: Implementation

After system design, the third phase is implementation. With inputs provided from the system
design, the Darul Ehsan Club House Management System is first developed in small
programs knows as units, which are implemented in the following stage. Each unit is
developed and tested for its functionality which is knows as Unit Testing. Each unit can be
tested in detail to prevent any small-scale error of the system.

Phase 4: Testing

Follow-up to the system design is the testing phase. All the units developed within the Darul
Ehsan Club House Management System are integrated into a system after testing each unit in
the implementation process. The Darul Ehsan Club House Management System needs to go
through constant software testing to find out if there are any flaws or errors within the
system. Furthermore, testing is done so that members using the Darul Ehsan Club House
Management system will not face any problem while they are installing the software.

Phase 5: Deployment of system

The Darul Ehsan Club House Management System will be deployed after the testing stage.
They system will be deployed in the Darul Ehsan Club House Management System customer
environment.

Phase 6: Maintenance

This phase will only take place after the installation of the Darul Ehsan Club House
Management system. It involves making modifications to the system to make changes to it or
improve its performance. These modifications will only take place if defects are found in the
system or if a member requests for changes to be made to the current system. The Darul
Ehsan Club House Management System will be provided with regular maintenance.

7.12 Advantages & Disadvantages of The Waterfall Model

Advantages of The Waterfall Model

  Simple to understand, follow and manage tasks.
 Easy to manage due to rigidity of the model
 Processes are completed in steps and do not overlap one another
 Allows departmentalization and control

Disadvantages of The Waterfall Model

 It is very difficult to go back and make changes to a process

 It has lots of uncertainty and risks.
 Difficult to estimate time and cost for every phase.

7.2 Activity Diagram

7.21 Manage Facilities (Add)

Figure 36: Activity Diagram to Add Facilities

In the activity diagram shown, six activities are shown. The first activity is for the user is to
log in into the system. Then the user can select manage facilities. The user can decide if they
want to manage facilities or not. If they do not want to continue, the activity will end but if
they do want to continue, the page will show the facility list. The user can then select the add
button and insert the facility values. Once completed, the user is required to save the changes.
The user can then decide if they wish to continue.

7.22 Manage Facility (Edit)

Figure 37:Activity Diagram to Edit Facilities

The following activity diagram shows six activities can be found. The activity begins with the
user logging into the system. It then continues with the user selecting manage facilities. The
users can decide if they want to continue or not. The activity will end if they choose no and if
they choose yes, it will continue to proceed to the next activity. The page will show the
facilities list and the user is required to select a specific facility which is intended to be
modified. Once the facility details have been modified, the user is required to save the
changes. When completed, the user can decide to continue or to end the process.
7.23 Manage Facility (Delete)

Figure 38: Activity Diagram to Delete Facilities

In the above activity diagram, five activities are stated. The activity will begin when the
customer logs in into the system. The users can decide if they want to manage facilities or if
they do not want to. If they decided to not manage facilities, the activity will end, but if they
decide to manage facilities, the page will show the facilities list. The users can then select a
specified facility that they wish to delete and then click the delete button to remove it. The
user can then decide if they want to continue which will restart the activities or not to
continue which will end the activity.
7.24 Manage Inquiries and Feedback

Figure 39: Activity Diagram to Manage Inquiries and Feedback

In the following activity diagram, there are six activity shown. The activity begins with the
user logging into the system. It then continues with the user selecting manage inquiries and
feedback. The users can decide if they want to continue or not. The activity will end if they
choose no and if they choose yes, they will continue to proceed to the next activity. The page
will show the Inquiry list and the user is required to select a specific inquiry or feedback.
When they inquiry or feedback has been selected, they can insert a reply. Once the reply has
been written, the user is required to send the reply. When completed, the user can decide to
continue or to end the activity.
7.3 Testing
7.31 Component Testing
Component testing is characterized as a software testing type, in which testing is conducted
on each individual component separately without integrating with other components within a
system. Component testing is conducted by the tester and is performed under unit testing.
Components testing includes verifying functional and non-functional requirements of the
system components. It can be used for testing resource behaviour, performance testing and
structural testing. Component testing will be done on the manage facilities add, edit and
delete functions. (Software Testing Help, 2020).

7.32 Testing Script

Test Test Steps Description Expected Actual Pass/Fail
ID Date Result Result
T01 17/4/2020 1. Click the Add button New Facility New Facility Pass.
2. Add facility details in displayed in displayed in
new facilities the facility the facility
list. list and
message box
shows
confirmation
T02 17/4/2020 1. Select facility to edit. Facility Facility Pass.
2. Modify the facility details details
name and type. updated in updated in
3. Click Save Changes the list. the list and
message box
shows
confirmation.
T03 18/4/2020 1. Select facility to delete. Facility is Facility is Pass
2. Click Delete. removed removed the
from the list. list and
message box
shows
confirmation
8.0 Individual Part (Krinath Kumar A/L Rajendran TP053048)
8.1 Spiral Methodology

Spiral model was depicted by Barry Boehm in 1986 is a mix of iterative development method
and a sequential improvement model. Spiral model is a risk-driven process model which
implies the general project’s success relies on the risk analysis phase. The Spiral model is one
of the oldest types of the software development lifecycle (SDLC), where the development
process is carried out, incrementally and iteratively in a systematic and quick manner
(CLICK2CLOUD-BLOG, 2019).

The Spiral Model is usually utilized in the software industry as it is in sync with the natural
development process of any product. For instance, learning with maturity which includes the
lowest risk for the client as well as the development organizations. I think the appropriate to
create the clubhouse management system using Spiral Methodology because it matches all
the requirements that fulfilled to utilize this model. This model is one of the most vital
Software Development Life Cycle models, which delivers support for risk management and
besides, a prototype is compulsory in this clubhouse management system during developing
this system.

Figure 1 (CLICK2CLOUD-BLOG, 2019).

Phase 1: Planning

This phase includes estimating the cost, schedule and resources for the iteration. Besides, it
involves comprehending and gathering all the system requirements for continuous
communication between the system analyst and the client. Therefore, we have comprehended
and gathered all system requirements for the client. For instance in this system, residents of
Darul Ehsan Club House able to register as a member and allow to login to book
coach/facilities/services, cancel bookings, view charges and making enquiries. On the other
hand, the staffs able to make a new staff account that has just joined, add/edit/delete/search
available facilities and services, manage user enquiries and feedbacks, and generate daily,
weekly, monthly summary report.

Phase 2: Risk Analysis

In Risk Analysis phase, the project prototype is set up for the solution. All the planning which
is being planned in the planning phase is proceed with the risk analysis phase to overcome the
problems and risks at the beginning stage of the project. Technical and management risk are
the aspect that involves in the risk analysis phase. For example, we manage to make a user-
friendly interface to make simpler for the users to utilize this system and less technical for
them. In this way, we can overcome the problem of the user or customer dissatisfaction of
this system.

Phase 3: Engineering and execution

In this phase, the execution part is being done once the planning and risk analysis finalized
that being proceed where all the coding, testing and deploying of software takes place. In our
case, we have added some codes to function as register, booking, make enquiry, login, view
facilities/services, booking history and cancel booking into the prototype. After adding the
codes, we initiated to test this prototype. As for the testing part, we have prepared test scripts
to test the prototype. Therefore, we discover that the prototype has mostly functioning as we
expected but there are few errors found in our prototype.

Phase 4: Evaluation

In this phase, the customers evaluate the software and provide their feedback and approval. In
here, member of the clubhouse can submit their inquiries about what they feel about the
system or suggestion to let the system functions better and also asking related to the system to
allow staffs to answer their inquiries. But before that, the user must create their account in the
system to sign in (CLICK2CLOUD-BLOG, 2019).
Benefits

There are some benefits of utilizing Spiral Model compare to using other using model. First,
it will manage in a strategic way to develop huge projects or software. Moreover, the risk
evaluation of this model is more suitable compared to other models. Furthermore, it has more
room for customer feedback and the changes are implemented quicker than other models. The
cost estimation of this methodology becomes simpler than other models as the prototype
building is done in small fragments.

Disadvantages

When comes to benefits there will be disadvantages as well. In this case, there is too much
reliance on risk analysis. Therefore, the successful completion of the project is very much
reliant on risk analysis. Without the experts, it is going to be a failure to make a project
utilizing this model. Next, this model is tougher in time management. As the number of
phases is unknown at the begin of the project, so time estimation is very problematic.

8.2 Activity diagram

8.21 Inquiries and Feedback

In the activity diagram shown, 7 activities are displayed. The first activity is for the user is to
log in into the system. Then the user can click View Inquiries and Feedback button. The user
can decide if they want to continue View Inquiries and Feedback or not. If they do not want
to continue, the activity will end but if they do want to continue, the page will show all the
inquiries and feedback that they received before. The user can then select the Add Inquiry
button and insert the subject and inquiry information. Once completed, the user needs to click
Submit this Inquiry button to send inquiry to the staff.
8.22 Daily Generate Summary

The following activity diagram shows 7 activities can be found. The process begins with the
user logging into the system then clicking the Generate Summary button. The user can decide
if they want to continue to Generate Summary or not. Then the user can select what type of
report that wanted to insert. In here, user select daily report and a specific date. After that, the
user can type their comments in the textbox. Next, user click generate summary button to
send the feedback to the member who submits their inquiry. If user desire to continue, this
page will clear everything so the user can select and type again.
8.23 Weekly Generate Summary

The following activity diagram shows 7 activities can be found. The process begins with the
user logging into the system then clicking the Generate Summary button. The user can decide
if they want to continue to Generate Summary or not. Then the user can select what type of
report that wanted to insert. In here, user select weekly report and specific week. After that,
the user can type their comments in the textbox. Next, user click generate summary button to
send the feedback to the member who submits their inquiry. If user desire to continue, this
page will clear everything so the user can select and type again.

8.24 Monthly Generate Summary

The following activity diagram shows 7 activities can be found. The process begins with the
user logging into the system then clicking the Generate Summary button. The user can decide
if they want to continue to Generate Summary or not. Then the user can select what type of
report that wanted to insert. In here, user select monthly report and specific month. After that,
the user can type their comments in the textbox. Next, user click generate summary button to
send the feedback to the member who submits their inquiry. If user desire to continue, this
page will clear everything so the user can select and type again.
8.3Testing
The objectives of interface testing are to detect faults due to interface errors or invalid
assumptions about interfaces. The types of Interface Testing are parameter interfaces that
data passed from one method or procedure to another. Secondly, shared memory interfaces
which block of memory is shared between procedures or functions. Thirdly, procedural
interfaces refer that the sub-system encapsulates a set of procedures to be called by other sub-
systems. And fourth, message passing interfaces which means the sub-systems request
services from other sub-system (Meskaran,2020).

Testing Scripts
Generate Summary
Test ID Date Steps Expected Actual Pass/ Fail
Description Result Result

1 19/4/2020 1. Select the Message box Message box Pass

daily of of
report “Generated “Generated
2. Select a Report Report
specific Successfully Successfully”
date ” not not is
3. Type delayed. delayed
comments
in report
textbox.
4. Click
Generate
Summary
button.
Inquiries and Feedback
Test ID Date Steps Description Expected Actual Pass/ Fail
Result Result
2 19/4/2020 1. Type the New New Pass
subject in member’s member’s
the subject inquiry inquiry
text box appeared in appears in
and inquiry staff inquiry staff inquiry
information and and
in the feedback feedback
inquiry text page. page.
box.
2. Click the
Add
Inquiry
button.

3 19/4/2020 1. Click the The The Pass

history of information information
inquiry in displayed in is displayed
the inquiry all the text in all the
list box. boxes text boxes
9.0 Individual Part (Heather Tee TP054038)
9.1 UML Class Diagram
Main Activity Diagram

In the activity diagram above, these are all the activities in general shown. Users without an
account must register an account in order to use the systems feature. After registered, staff
users can utilize 8 functions on the left whereas the resident users utilize 4 functions on the
right. After that, users can log out after using the system.
Register Activity Diagram

In this diagram above, there are 2 activities shown, those without an account must register
otherwise login at the Login page. After registering an account will lead to the Login page.
Where there is a failed registration, it will restart and must redo the registration.

Book Facilities and Services

In this diagram above, there are 4 activities total in this process. User can book either
Facilities or Services. The service route has an extra activity than the Facility route as the
Service requires the facilities as well.
9.2 Methodology
9.21 Incremental development

In order to build a prototype for Darul Ehsan Club House system to solve the problems while
using its manual method, using incremental development is suggested as an accurate software
process model. Incremental development requires three separate software processes that are
software specification, development, and validation to be carried out simultaneously on
separate prototype modules.

Incremental development can be either an agile process or can be a guided plan. An agile
process requires gradual preparation in which the plans can be changed to meet the
unpredictable needs of the customer on the move, while a guided plan involves a preliminary
planning of operations, and progress is then measured against the schedule or budget. This
project will need to be split into many variants first, for it to work on incremental
development. Then, every change is again linked to smaller subsystems to allow to work on
various parts of the system. Whenever each newer development will replace the previous
development by adding new functionality.
Phases

Phase 1: Specification

First the system goes through the specification phase, using the specifications process to
evaluate the criteria for implementing such a system for Darul Ehsan Club House, by
evaluating the resources, in accordance with the necessary elements. In this process, the
criteria are decided for the user positions, mainly the residents and staff. Those users'
requirements are later listed in detail as user requirements and system requirements. Such
statements of specifications are later discussed among members of the club house and then
submitted for approval to the residents.

Phase 2: Development

After the specification phase, developing a workable prototype to the customer is then tasked.
Logical design is generated for each part based on user and system specifications, using
diagrams such as the use case diagram, operation diagram, and class diagram. This is because
Visual Basic enables a high degree of versatility and a quick drag and drop method and
Minimal coding is then used to give the components its functions.

Phase 3: Validation

After the prototype has been completed, we conduct system testing with test cases on
different prototype modules to ensure that it works as expected, because testing is a widely
used method of verification and validation. The test cases are based on the specification that
were outlined in Phase 1. The person responsible for the modules would obtain the test
results, so they would need to redo or repair it promptly.

9.12 Justification
Incremental development is suitable for this task as the expense and time required to make
any improvements than the Waterfall Model would be necessary. This also takes less time to
correct any changes to the report and to redo the report. In addition, having the customer
regularly track the system's progress makes it easier to get feedback and suggestions on it, so
that the system can be updated to better suit the customer's requirements.

9.3 Testing
9.31 Acceptance Test
The main aim of Acceptance Test is to determine the consistency of the system with the
specifications and to validate that it has met the necessary standards for delivery to end users.
Acceptance Testing is the final step of software development carried out after system
validation and before making the program usable for actual use.

9.32 Test Scripts

Test Date Test No. Steps Executed Actual Status
Description Result Result (Pass/Fail)
19/4/2020 1 1. Insert Message Message Pass
content Box stating Box
in the ‘Reply sent’ displayed
Inquiry displayed ‘Reply sent’
and
Feedback
Form.
2. Click
Send
19/4/2020 2 1. Insert Message Message Pass
content Box stating Box
in the ‘Booked displayed
Booking Successfully’ ‘Booked
Facilities displayed Successfully’
and
Services
Form
2. Click
Book
19/4/2020 3 1. Insert Message Message Pass
content Box stating Box
in the ‘Booking displayed
Cancel Cancelled’ ‘Booking
Booking displayed Cancelled
Form
2. Click
 Confirm

10.0 Individual Part (Seveshvarman Naaidu TP053878)

10.1 Logical Design Part 2

10.11UML Activity Diagram

Manage Available Services (Add)

In the activity diagram above, there are 6 activities shown. When the manage available
services (add) process starts, the user will start by logging in to the system. After that they
will move on to manage available services. After this activity, depending on the user’s choice
to proceed, the process is carried on and finished. Otherwise, the process will end.

Manage Available Services (Edit)

In the diagram above, there are 6 activities shown. When this process starts, the user will first
login to the system. After that they will click manage available services, in which if the user
decides to edit coaches, they will select the edit button, and then save changes. If they decide
not to edit, they will stop the process.

Manage Available Services (Delete)

In the process shown above, there are 5 activities shown. The user logs in to the system, then
moves on to manage available services. After that if they choose to delete coaches, they can
proceed and save changes. If they do not choose to delete any coaches they will end the
process.

10.2 Methodology

10.21 Reuse-oriented software engineering

Reuse-oriented software engineering is based on systematic reuse where systems are
integrated from existing components.

10.22 Justification and Phases

Reuse-oriented software engineering will have the team use previous versions of the system
to improve the systems current version. This in turn helps reduce wastage and reduce costs.

This model consists of these phases:

1. Starting off, the 1st phase is requirements specification. Which is the functional and
non-functional requirements for the system.
2. 2nd phase will be the component analysis which will be based on the requirements
specification, a thorough analysis on the components that will implement the
specifications which are required will be done.
3. The 3rd phase will then come to requirements modification. In this stage, the
requirements will be analyzed using the information regarding components that have
been discovered. Which are then modified to match the systems needs, when
components cannot be modified, the component analysis will be redone to find any
possible solutions.
4. 4th phase is system design with reuse. In this phase, the main framework of the system
will be designed. Otherwise, a framework that already exists will be reused. The
systems designers will make the design according to the components that are reused
and will organize the framework accordingly to prevent any errors.
5. The 5th phase is development and integration. Systems that cannot be externally
procured will be developed, and the components are then integrated to create the new
system.
6. The final phase will come down to system validation. The system will go through a
proper testing process until it is decided to be free of any errors.
As the development team will go through these phases, it can prevent any wastage of
materials as components will be reused making it more efficient and speeding up the entire
process

10.3 Testing
10.31 Integration Testing
Integration Testing tests the interface between components, interaction with different parts of
a system, such as operating system, file system and hardware and interfaces between the
system.

10.32 Testing Scripts

Test ID Test Date Steps Expected Actual Result Pass/Fail
Description Result
1 18.04.20 1.Click the Dialogue box New coach is Pass
Add button stating ‘Coach displayed in
2.Add coach Added’ will the list of
details be displayed, coaches
3.Click save New Coach Dialogue box
button displayed in is displayed
the list of
coaches
2 18.04.20 1.Click edit Dialogue box Coach details Pass
button stating ‘Coach is successfully
2.Edit coach saved’ will be updated and
details displayed, displayed in
3.Click save Coach details the list
button should be Dialogue box
updated in the is displayed
list
3 18.04.20 1.Select the Dialogue box Coach details Pass
coach name stating ‘Coach is successfully
2.Click the Deleted’ pops removed,
delete button up, and details hence no
3.Click the of the coach is longer in the
save button no longer list
displayed in Dialogue box
the list is displayed
11.0 Individual Part (Daevern TP054028)
11.1 UML ACTIVITY DIAGRAM
UML Activity Diagram (UserLogIn)
The activity diagram above, three activities are stated. When the the user wants to log into the
sytem, he or she must enter their UserID and password first. Then, the system will check the
database if the user is registered or if the credentials entered are correct. If there is a problem,
then the system will ask you to re-enter the password or UserID. However, if there are no
problems then the user will be successfully logged in and the system will display user
settings.
UML Activity Diagram (inquire of facilities)
Three activities are shown in the activity diagram above. First, the user will make inquires
about the availability of facilities. They will then select the sport court/facility, if they
sport court/facility is not available, then the system will inform you of the status of the
availability and ask you to choose another one. On the other hand, if the court/facility is
available then the system will ask the user to select a date and time to book the
cour/facility. Then the system will ask you to confirm booking if yes then it will be keyed
 into the database and a receipt is printed. If no then they system will go back to inquiry
page.

UML Activity Diagram (Cancel Booking)

In the above activity diagram shows four activities. First, the user will request to make a
cancellation of the booking to the staff. The staff will then enter the cancellation details
provided by the user. The system will then validate and verify the request. If the request is
not okay then the system will ask the staff to re-enter the cancelation details. If there is no
problem, then the system will approve the request and calculate the refund amount.

11.2 Methodology
Prototype

Prototyping is a working model of software with some limited functionality which may be defined
as method during which a prototype is built, tested and reviewed before the planning stage.
Furthermore, Prototyping is employed to permit the users evaluate developer proposals and
test them out before implementation. It also helps understand the wants which are user
specific which may have not been considered by the developer during product design. Furthermore,
since the prototype doesn't always hold the accurate logic utilized in the actual software application,
it may be viewed as an additional effort to be considered under effort estimation. However, due to
the model being built on customer requirements. When this process is followed, customers can get a
sensible feeling of how the system is being developed.

Justification

Prototyping enables developer and customer to work and co-operate together to deliver
constructive criticism on the model assessed by them which allows the development team to
induce a higher insight of the system created and to produce a system which meets the customer
requirements.
This model consists of several phases and are as follows:

Step 1: Requirements gathering and analysis

A prototyping model starts with requirement analysis. during this phase, the necessities of the
system are defined detail. During the process, the users of the system are interviewed to grasp what
are their needs and wants from the system and to also identify the difficulties they face within
the managing facilities module and imply the advantages of already implemented features.

Step 2: Quick design

The second phase, a simple design or a fast design related to the club house is produced for the
system. during this stage, a straightforward design of the system is developed. However, it's not the
full design. It gives a quick idea of the system to the user. the fast design helps in developing the
prototype.

Step 3: Build a Prototype

From the data collected in the first phase, we are going to use that data to build and actual
prototype model based on the information gathered from quick design.  It is a small working model
of the specified system.

Step 4: Initial user evaluation 

In this stage, the proposed system is presented to the customer for an initial evaluation. It
helps the customer to identify the strength and the difficulties faced in the working model.
The comments and suggestion are collected from the customer and provided to the developer
to further improve the system.

Step 5: Refining prototype

If the user isn't pleased with the present prototype, you need to refine the prototype in line with the
user's feedback and suggestions. 
This phase won't over until all the necessities specified by the user are met. Once the user is satisfied
with the developed prototype, a final system is developed supported the approved final prototype.
Step 6: Implement Product and Maintain
Once the ultimate system is developed supported the ultimate prototype, it's thoroughly tested and
deployed to production. The system undergoes routine maintenance for minimizing downtime and
stop large-scale failures.

Advantages of Prototype model:

• Users are actively involved in development. Therefore, errors may be detected within the initial

stage of the software development process. 
• Missing functionality may be identified, which helps to cut back the danger of failure as
Prototyping is additionallyconsidered as a risk reduction activity. 
• Helps team member to speak effectively
• Quicker user feedback is accessible resulting in better solutions.
• Confusing or difficult functions may be identified
Requirements validation, Quick implementation of, incomplete, but
functional, application.

Disadvantages of Prototype model:

• Leads to implementing and so repairing way of building systems.

• Practically, this system may increase the complexity of the system as scope of the system may
expand beyondoriginal plans.
• Incomplete application may cause application to not be used because the
full system wasdesigned
Incomplete or inadequate problem analysis.
11.3 TESTING
Performance testing, a non-functional testing technique performed to determine the system
parameters in terms of responsiveness and stability under various workload. Performance testing
measures, validates and verifies other quality attributes of the system, such as scalability, reliability
and resource usage. There are 4 main types of performance testing techniques. They are described
below:

 Load testing - It is the simplest form of testing conducted to understand the behaviour
of the system under a specific load. Load testing will result in measuring important
business critical transactions and load on the database, application server, etc., are
also monitored. 
 Stress testing - It is performed to find the upper limit capacity of the system and also
to determine how the system performs if the current load goes well above the
expected maximum.
 Soak testing - Soak Testing also known as endurance testing, is performed to
determine the system parameters under continuous expected load. During soak tests
the parameters such as memory utilization is monitored to detect memory leaks or
other performance issues. The main aim is to discover the system's performance
under sustained use.
 Spike testing - Spike testing is performed by increasing the number of users suddenly
by a very large amount and measuring the performance of the system. The main aim
is to determine whether the system will be able to sustain the workload.

11.31 Test script

Test Test Steps Description Expected Result Actual Pass/Fail
 ID Date Result
1 17/04/20 1. Enter user To display User User details Pass
loginID details. system and system
displayed
2 18/04/20 1. Inquiry of facility User is able to make User was able Pass
2. Selecting facility an inquiry about the to make
3. Confirm booking facility aswell as inquiry and
booking booking
3 19/04/20 1. To enter 1. System will System was Pass
cancelation make the able to make
details cancellation cancellation
and refund the and refund
full amount full amount

12.0 Prototype
https://drive.google.com/open?id=1o6KYYnd_xiA7D0NPnA5VoJvVujTUMCAX
13.0 References
Cheah, D., 2019. legal resources. [Online]
Available at: https://www.hg.org/legal-articles/up-close-and-personal-the-malaysian-personal- data-
protection-act-33273
[Accessed 23 june 2019].
Elgabry, O., 2017. Software Engineering — Software Process and Software Process Models (Part 2).
[Online]
Available at: https://medium.com/omarelgabrys-blog/software-engineering-software-process- and-
software-process-models-part-2-4a9d06213fdc
[Accessed 10 September 2019].
GeeksforGeeks, 2019. Software Engineering | Spiral Model - GeeksforGeeks. [Online]
Available at: https://www.geeksforgeeks.org/software-engineering-spiral-model/
[Accessed 11 September 2019].
Guru99.com, 2019. What is Spiral Model? When to Use? Advantages & Disadvantages. [Online]
CLICK2CLOUD-BLOG, 2019. Spiral Model in SDLC. [Online] Available at:
http://blog.click2cloud.net/?p=1264 [Accessed 18 April 2020].

Software Testing Help, 2020. What Is Component Testing Or Module Testing (Learn With
Examples). [Online]

Available at: https://www.softwaretestinghelp.com/what-is-component-testing-or-module-testing/

[Accessed 16 April 2020].

ToolsQA, 2016. Waterfall Model. [Online]

Available at: https://www.toolsqa.com/software-testing/waterfall-model/

[Accessed 14 April 2020].

Tutorials Point, 2015. SDLC - Waterfall Model. [Online]

Available at: https://www.tutorialspoint.com/sdlc/sdlc_waterfall_model.htm

[Accessed 14 April 2020].

Cheah, D., 2019. legal resources. [Online]

Available at: https://www.hg.org/legal-articles/up-close-and-personal-the-malaysian-personal-data-

protection-act-33273