Project Sample 1

Kingdom of Saudi Arabia
Ministry of Education
Jouf University
College of Computer and Information Sciences
Beauty Website
PROJECT SUPERVISOR
Dr. Mamoona Humayun
GROUP MEMBERS
Duaa Alibrahim
Jory Slman
Elham Ibrahim
Department of Information Systems, College of Computer

and Information Sciences, Jouf University.
2023/2024
CONTENTS
ABSTRACT
This project outlines the key features and functionalities of an

innovative beauty website system designed to cater to the diverse
needs of beauty enthusiast in the digital era. this beauty platform offers
a holistic and user-centric experience by seamlessly combining various
elements of beauty, include skincare cosmetics, in a single accessible
online environment.
"Her" website is built on a robust architecture that prioritizes user
engagement and personalization. Through an intuitive interface, users
can explore a wide range of beauty products, access expert advice, and
stay updated on the latest trends and innovations within the beauty
industry. The platform leverages cutting-edge technologies, to provide
personalized product recommendations based on individual
preferences, skin type, and beauty goals.
Page ii
CONTENTS
Contents
1 PROJECT OVERVIEW 1
1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2 Project Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.3 Problem Description . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.4 Proposed Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.5 Proposed System Components . . . . . . . . . . . . . . . . . . . . . 3
1.6 Proposed System Output . . . . . . . . . . . . . . . . . . . . . . . 3
1.7 Main Features of the Proposed System . . . . . . . . . . . . . . . . . 4
1.8 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2 SYSTEM ANALYSIS 5
2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.2 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.3 Specification Requirements . . . . . . . . . . . . . . . . . . . . . . 6
2.3.1 Functional Requirements . . . . . . . . . . . . . . . . . . . . 7
2.3.2 Non-Functional Requirements . . . . . . . . . . . . . . . . . . 8
2.3.3 Use case diagram . . . . . . . . . . . . . . . . . . 8
2.4 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3 SYSTEM DESIGN 10
3.1 Introduction.................................................................................................................10
3.2 Sequence Diagrams....................................................................................................12
3.3 Activity Diagrams......................................................................................................14
3.4 Class Diagram............................................................................................................17
Page iii
CONTENTS
3.5 Conclusion..................................................................................................................23
REFERENCES 36
Page iv
CHAPTER 2. PROJECT OVERVIEW
Chapter
1
PROJECT OVERVIEW
1.1 Introduction
A beauty website called Her aims to create a comprehensive online platform dedicated to all things
beauty-related. The website will serve as a one-stop destination for anyone seeking for products
that can’t find it in stores, tips, and recommendations on skincare, makeup, haircare, and more. It
will feature a wide range of content, including tutorials, product reviews, and expert advice, The
project also includes the development of a community forum where users can connect, share
experiences, and seek guidance from fellow beauty enthusiasts. The goal of the beauty website is
to provide a valuable resource that empowers individuals to enhance their beauty routines, stay
updated with industry trends, and foster a supportive community of beauty lovers.
"Her" website is built on a robust architecture that prioritizes user engagement and personalization.
Through an intuitive interface, users can explore a wide range of beauty products, access expert advice,
and stay updated on the latest trends and innovations within the beauty industry. The platform leverages
cutting-edge technologies, to provide personalized product recommendations based on individual
preferences, skin type, and beauty goals.
1.2 Project Scope

In this project, we will do the analysis and design of the Beauty Website. The project scope
can be outlined as following:
 The main objective of the project is to design and develop an Beauty Website
 Provide interactive graphical interfaces.
 Beauty related things will appear directly after the customer register the website
1.3 Problem Description
This project is needed when the Customers searching about products and unfortunately they
can’t find it in any other stores or websites so we will provide these products that don’t available
in our area which is will help and solve a problem.
1.4 Proposed Solution

The proposed system has two main roles as described below
Admin:
o Admin have access to the website and provides the products on the website.
Customer:
o The customers who enter the website and find the products then they can order.
Page v
Figure 1: Key stakeholders of the project
1.5 Main Features of the Proposed System
 The purpose of the project is to save time, save money. Through online
shopping one can save his valuable time. One can watch and select things
he wants to buy.so any one can find the item he wants.
1.6 Conclusion
 This project built on a robust architecture that prioritizes user engagement and
personalization. Through an intuitive interface, users can explore a wide range of beauty
products, access expert advice, and stay updated on the latest trends and innovations
within the beauty industry. The platform leverages cutting-edge technologies, to provide
personalized product recommendations based on individual preferences, skin type, and
beauty goals.
Page vi
Chapter
2
SYSTEM ANALYSIS
2.1 Introduction
System analysis is a crucial phase in the development and implementation of any project.
It involves a comprehensive study and evaluation of the existing system or the proposed
system to identify problems, requirements, and opportunities for improvement. The
primary goal of system analysis is to bridge the gap between the current state and the
desired future state of the system.
During the system analysis phase, a team of analysts and stakeholders work together to
gather information, analyze processes, and define the functional and non-functional
requirements of the system. This phase focuses on understanding the underlying business
processes, identifying areas of inefficiency or bottlenecks, and proposing solutions to
enhance the overall performance and effectiveness of the system.
System analysis is a collaborative effort involving various stakeholders, including

analysts, users, managers, and technical experts. It lays the foundation for the subsequent
phases of the project, such as system design and development. By thoroughly
understanding the existing system and defining clear requirements, system analysis helps
ensure the successful implementation of a project that meets the needs of the
organization and its users.
2.2 Requirements
Requirement is a singular documented physical or functional need that a particular

design, product or process aims to satisfy. It is commonly used in a formal sense in
engineering design, including for example in systems engineering, software engineering,
or enterprise engineering. It is a broad concept that could speak to any necessary. Indeed,
it brings together the activities to be carried out to transform the requirements of a user
into a software system whatever the class, the size and the field of application of this
system.
Page vii
2.2.1 Functional Requirements
Functional requirement outlines the functions and features as well as specifications of the
system. Table 1 outlines the important functional requirements of our project
Table 1: List of functional requirements

Identifier Priority Stakeholder Requirements Requirement description
weight (low Name
1- high 5)
REQ-001 5 Admin, Login Users should be able to create an
Customer account to access personalized features.
REQ-002 4 Admin Search the item The Admin should search and add the
item.
REQ-003 5 Admin Manage item Controlling various aspects of the order,

updating the information of the product
or setting price or making discounts.
REQ-004 5 Admin Manage order Controlling various aspects of the order,
tracking the order or updating order
information.
REQ-005 5 Admin, Make Registration To be able to order customer should do
Customer Customer the Registration.
REQ-006 3 Customer View item Customer enter the website then view or
looking for the product.
REQ-007 5 Customer Make order Process of placing the product services,

the customer select the item with the
necessary details.
REQ-008 5 Customer Make Payment When the Customer confirm the order
he should do the Payment.
Page viii
2.2.2 Non-Functional Requirements

The non-functional requirements of the system are intended to define the system properties
and limitations such as response time and storage requirements. The non-functional
requirements of our system are:
Table 2: List of Non-functional requirements

Identifie Requirements Requirements Measurement criteria
r Name
REQ-010 Reliability The website should be The website uptime should be at least
operational with minimal 99.9%, and error should be less than
disruption or errors 0.5%
REQ-011 Availability The website should be The website well be available and
available accessible to users all the
time
REQ-012 Scalability The website should be able to The website should maintain consistent
handle accommodate performance even during peak
growing number of usage periods , with no
users significant slowdowns
REQ-013 Performance The website should loud Page loud time should be less than 3
quickly and respond seconds
promptly to user
interactions
Page ix
Use Case Diagram 2.5
Beauty
Websit
e
Use
Case Scenario
Use Case Name: Make Order UniqueID: REQ-007
Area: beauty websites
Actors: CUSTOMER
Stockholder: ADMIN
Description: customer confirmed the order
Description: customer confirmed the order
Triggering Event: customer enter the website and login enter ID,
.password, make order
Trigger Type: External
Steps performed (main path) Information for steps
Customer logs to website using secure web server UserID, Password
Successful registration Do the order,
confirm
Page x
Preconditions: Selection of the item

Postconditions: The order is confirmed
Assumptions: Customer should make payment
Success Guarantee: Customer should receive the order
Minimum Guarantee: Customer was able to order
Requirements Met: To be able to order customer should do the
registration
Outstanding Issue: How should a rejected credit card be handled
Priority: High
Risk: High
Page xi
Use Case Name: Make Registration Customer UniqueID: REQ-005

Actors: CUSTOMER
Stockholder: ADMIN
Description: Allow the customer to make order
Triggering Event: Customer uses registration Website, enters userID and
.password, and clicks the logon button
Trigger Type: External / Temporal
Successful registration Can make their own
account
Preconditions: Customer has already registered and has created a user
account
Postconditions: Customer can make order
Assumptions: Customer has a browser and a valid userlD and password
Success Guarantee: customer has orderd
Minimum Guarantee: Customer was able to logon
Requirements Met: Customer to be able to register for the website must
use a secure browser
Priority: High
Risk: Medium
Page xii
Use Case Name: Make Payment UniqueID: REQ-008

Actors: CUSTOMER
Stockholder: ADMIN
Description: Transaction fees based on the payout currency
Triggering Event: Making a purchase ,completing a transaction
Trigger Type: Internal / External
Successful registration
Preconditions: The customer has put his card information
Postconditions: Confirmation message, a receipt, and the completion of
the transaction
Assumptions: Customer has put the right card information
Success Guarantee: Customer should receive the receipt
Minimum Guarantee: Customer has not receive the receipt
Requirements Met: to be able to pay the customer should confirm the
order
Priority: High
Risk: High
Page xiii
Chapter
3
SYSTEM DESIGN
3.1 Introduction
Page 14
3.2 Sequence Diagrams
Page 15
Page 16
3.3 Activity Diagrams
Page 17
Page 18
Page 19
3.4 Class Diagram
Page 20
3.5 Entity Relationship Diagram
Page 21
3.6 Database Diagram
Page 22
3.7 Architecture Diagram
Page 23
3.8 Data Dictionary
Page 24
Page 25
3.9 Conclusion
Page 26
CHAPTER 2. SYSTEM ANALYSIS
Chapter
4
IMPLEMENTATION AND TESTING
4.1 Introduction
4.2 Technologies Used
Page 27
Page 28
4.3 System Interfaces
Page 29
Page 30
Page 31
Page 32
4.4 System Coding
Figure 20. Login Code
Page 33
4.5 System Testing
Page 34
Page 35
Page 36
CHAPTER 3. SYSTEM DESIGN
Chapter
5
CONCLUSION AND FUTURE WORK
5.1 Achievements
5.2 Limitations
Page 37
CHAPTER 3. SYSTEM DESIGN
5.3 Future Work
Page 38
REFERENCES
[1] Online Grocery. URL: https://todoorstep.com/ (visited on 0002–2021).
[2] Dusan Petkovic. Microsoft SQL Server 2016: A Beginner’s Guide. McGraw-Hill Education,
2016.
[3] Svetlozar Nestorov Nenad Jukic Susan Vrbsky. Database Systems: Introduction to
Databases and Data Warehouses. Prospect Press, 2016.
[4] Harry J. Rosenblatt Scott Tilley. Systems Analysis and Design. Cengage Learning,
2016.
[5] Avathe Shamkant Elmasri Ramez. Fundamentals Of Database System. Pearson, 2017.

Project Sample 1

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Project Sample 1

Uploaded by

Copyright:

Available Formats

Kingdom of Saudi Arabia

Department of Information Systems, College of Computer

This project outlines the key features and functionalities of an

1.2 Project Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

1.3 Problem Description . . . . . . . . . . . . . . . . . . . . . . . . . . 2

1.4 Proposed Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

1.5 Proposed System Components . . . . . . . . . . . . . . . . . . . . . 3

1.6 Proposed System Output . . . . . . . . . . . . . . . . . . . . . . . 3

1.7 Main Features of the Proposed System . . . . . . . . . . . . . . . . . 4

2.3.1 Functional Requirements . . . . . . . . . . . . . . . . . . . . 7

2.3.2 Non-Functional Requirements . . . . . . . . . . . . . . . . . . 8

2.3.3 Use case diagram . . . . . . . . . . . . . . . . . . 8

3.2 Sequence Diagrams....................................................................................................12

3.3 Activity Diagrams......................................................................................................14

3.4 Class Diagram............................................................................................................17

1.2 Project Scope

1.4 Proposed Solution

Figure 1: Key stakeholders of the project

1.5 Main Features of the Proposed System

System analysis is a collaborative effort involving various stakeholders, including

Requirement is a singular documented physical or functional need that a particular

2.2.1 Functional Requirements

Table 1: List of functional requirements

REQ-003 5 Admin Manage item Controlling various aspects of the order,

REQ-007 5 Customer Make order Process of placing the product services,

2.2.2 Non-Functional Requirements

Table 2: List of Non-functional requirements

Use Case Diagram 2.5

Preconditions: Selection of the item

Use Case Name: Make Registration Customer UniqueID: REQ-005

Use Case Name: Make Payment UniqueID: REQ-008

3.2 Sequence Diagrams

3.3 Activity Diagrams

3.4 Class Diagram

3.5 Entity Relationship Diagram

3.6 Database Diagram

3.7 Architecture Diagram

3.8 Data Dictionary

4.2 Technologies Used

4.3 System Interfaces

4.4 System Coding

Figure 20. Login Code

4.5 System Testing

5.3 Future Work

[1] Online Grocery. URL: https://todoorstep.com/ (visited on 0002–2021).

You might also like