AAPP003-4-2-ISWE

Introduction to Software Engineering

Lecturer Name: Dr. Fatemeh Meskaran

Group Members

Mohamed Emad Atta (TP-053762)

Omar Mohamed Hussein (TP-053348)

Nadiya Asma Akther (TP-042382)

Contents
Introduction.................................................................................................................................................3
Objectives & scopes of system:...............................................................................................................3
Planning& requirements analysis:...............................................................................................................4
Functional requirements:........................................................................................................................4
Non-Functional requirements:................................................................................................................5
UML Design.................................................................................................................................................5
Class Diagram..........................................................................................................................................7
Use Case Diagram....................................................................................................................................8
Physical Design............................................................................................................................................9
Implementation:........................................................................................................................................11
Software requirements:.........................................................................................................................11
Hardware requirements:.......................................................................................................................11
Limitation:.................................................................................................................................................12
Conclusion:................................................................................................................................................12
Individual Components:.............................................................................................................................13
Logical Design Part 2..............................................................................................................................13
Acticity Digram 1................................................................................................................................13
Acticity Digram 2................................................................................................................................14
Activity Diagram 3..............................................................................................................................14
Methodology:........................................................................................................................................15
Testing:..................................................................................................................................................16
Introduction

One touch booking agent is a system can be used for hotels, clubs and big organization also. The
system can help the staff in filling system and manage all records for customers and members
easily. We operate the business in Malaysia, Singapore and other countries in Asia. And will
discuss what system can do in objectives.

Objectives & scopes of system:

 Use to staff that can login easily
 Staff can manage all records in the system
 Staff can search easily about any member
 Can add or delete members easily
 Can generate reports easily every week about new updates
 Can cancel booking of any services
 View the feedback of customers
 View or search the services and members
 Keep customer data safe
 Help staff to keep in track their customers
Planning& requirements analysis:

Gantt chart

Duration(week) 1 2 3 4 5 6 7 8 9 10 11 12

Planning &
requirement
Analysis
Logical design

Physical design

Testing

Implementation

Functional requirements:

 The system supports customers booking and ready to modify them

 Customers can search supported hotel, apartment.
 Customers ready to cancel their booking from their account.
 The system must send booking confirmation email after payment.
 Customers can book online and pay with credit card or cash when he arrives hotel.
  Staffs ready to edit customers booking information.
 Customers can write reviews about hotels and apartment and can rate hotels.
 Customers can check their booking status from his account.
 Customers can send feedback or call the staff for booking purposes.

Non-Functional requirements:

 The system must be ready to handle many transactions at the same time.
 Customers must cancel the booking before 24 hours, or their credit card will be charged.
 System should send promotions or deal to customers.
 The system should support most the browsers (Safari, Chrome,
and Firefox).
 The system should provide 24*7 hours services.
 The system must make sure that all transaction in secure connection.
 The system should be able to convert from all currencies.

UML Design
UML, short for Unified Modelling Language, is a standardized modelling language consisting of
an integrated set of diagrams, developed to help system and software developers for specifying,
visualizing, constructing, and documenting the artefacts of software systems, as well as for
business modelling and other non-software systems.

The elements in the structure diagram reflect the concrete concepts of the program, which may
include abstract concepts of the real world and the concepts of implementation.

There are seven types of structure diagram as follows:

 Class Diagram.
 Component Diagram.
 Deployment Diagram.
  Object Diagram.
 Package Diagram.
 Profile Diagram.
 Composite Structure Diagram.

Behavior diagrams display the dynamic behavior of objects in a system that can be represented
as a series of system changes over time, as follows are seven types of behavior diagrams:

 Use Case Diagram

 Activity Diagram
 State Machine Diagram
 Sequence Diagram
 Communication Diagram
 Interaction Overview Diagram
 Timing Diagram

We choose only 2 diagrams from 14 in our proposal system, the first one is “Class Diagram
“and the second one is “Use Case Diagram
Class Diagram

The class diagram is a key technique in modelling that goes through almost all object-oriented
methods. This diagram defines the types of objects in the system, and the various types of static
relationships between them.
Use Case Diagram
use case graph for the Darul Ehsan Club House Management system. There are two primary on-
screen characters for Darul Ehsan Clube House Management System which are the individuals
and the staff. Individuals are permitted to enlist as a part, sign in as a part, make appointments,
drop their appointments, view and search accessible offices and administrations, see their
charges and make requests and give input. Notwithstanding, staff are permitted to enroll as staff,
login as staff, make appointments for individuals, drop appointments for individuals, view and
quest for accessible offices and administrations, see part charges, alter appointments and oversee
requests and inputs. Besides, staff can likewise include, alter and erase the accessible
administrations in the Darul Ehsan Club House Management System. Besides, the staff can
likewise include, alter, erase the accessible offices. Finally, staff can likewise produce day by
day, week by week and month to month report.

Use Case of our proposal system:

Physical Design

When the residence chooses Badminton facility this page will appear to him and he wither can chose one
out of 2 selection “Group Coaching” or “Personal Coaching”

And then the residences must choose date for course to book it and this tap appears when they clicked on
bottom date.
Payment:

This will be the payment page for the residences, and they can fill all the boxes by their account
information to book their facilities they had chosen.
Implementation:

System implementation is that the most vital steps just in case of finalizing the approved web
system. we'd like to justify some basic requirement (software & hardware) in order that the
system will
work without having obligation and customers dissatisfaction.

Software requirements:

 Operation system: Mac OS (Lion, tiger, leopard) and windows (7, 8, 8.1, 10)

 Web browser: Google chrome, Firefox, safari (MAC).

 Database management system: MySQL, SQL server, Microsoft access.

Hardware requirements:

 Processor: Intel Platinum 4 and AMD or above.

 HDD: 30GB or above.

 RAM: 4GB or Higher

Limitation:
Although this method will provide the booking facilities to customers, it's having some
limitations. just in case of enquiry when customers send their feedback through the
system, it'll go on to the staff mailbox. It means the system don’t have the
separate website for checking all the shopper’s enquiry and send reply promptly.

Conclusion:

The system has some benefits for purchasers too. In home page customers can put their
email address or phone number for downloading the booking apps directly on their
phone. the appliance will work for both OS Platform (IOS & Android). By this customer
can book by using this application. Besides, customers can even book online without
registering into the system. Again, customers now must worry for payment.
Individual Components:
Logical Design Part 2

Acticity Digram 1
Acticity Digram 2

Activity Diagram 3
Methodology:
1
2.

Testing:

 Regression testing: Regression testing may be a software testing practice that ensures an

application still functions obviously after any code changes, updates, or improvements.

Regression testing is responsible for the general stability and functionality of the

existing features. Whenever a brand-new modification is added to the code, regression
testing is applied to ensure that after each update, the system stays sustainable under
continuous improvements.

 Performance testing: tests a software program's speed, response time, reliability,

resource utilization, scalability under their planned workload. Performance Testing is not
 aimed at finding functional defects but at removing performance bottlenecks in the
software or system.

 Acceptance testing: Acceptance Testing is always done by the customer.

The goal of this testing is to establish confidence in the system. Is a form of test
performed out by the end user or developer to verify / accept the software system before
bringing the software application into the production environment?

Test scripts:

Test Case 1
Test Title: Customer & Staff Login.
 Test Procedures: Type username & password.
 Test Data: Username & password must be in alphanumeric.
 Expected Result: It will redirect to login page

Test Case 2

 Test Title: Sign Up

 Test Procedures: Click sign up page.
 Test Data: Input customer’s information and click on the button “SIGN
UP”.
 Expected Result: It will register new customer
Test Case 3

Test Title: Search.

 Test Procedures: Type destinations name with selecting check-in and

check-out.
 Test Data: Valid destinations name with date.
 Expected Result: System will search according to customer’s choice.

Test Case 4

 Test Title: Manage Booking.

 Test Procedures: Click on the link “Manage Booking”.
 Test Data: Add, Edit, Del & Save button.
 Expected Result: Staffs can edit, add and Del individual customers
booking records.

Test Case 5

Test Title: View Booking Cancel Button

 Test Procedures: Customers need to sign in and can cancel the booking
when they press cancel button.
 Test Data: Cancel their booking record.
 Expected Result: Will cancel their booking records from database.