Fyp1 1

Silkee Cosmetics
Developed by
Muhammad Umar Hayat 3340-FBAS/BSSE/F16
Ahsan Zafar 3307-FBAS/BSSE/F16
Supervised by
Qamar Abbas
Assistant Professor
Department of Computer Science and Software Engineering Faculty of Basic

and Applied Sciences
International Islamic University Islamabad
2021
-1-|Page Silkee Cosmetics

Final Approval
Date: ____________
It is certified that we have read the Project report title "Silkee Cosmetics" Submitted by M Umar Hayat 3340-
FBAS/BSSE/F16 and Ahsan Zafar 3307-FBAS/BSSE/F16 under the Supervision of our respected Teacher
Qamar Abbas Assistant Professor DCS & SE FBAS IIUI. It is our supposition that this project is of enough
standard to justify its acceptance by Department of computer science and software engineering, International
Islamic University Islamabad for the bachelor’s degree of Software Engineering.
COMMITTEE
____________
1-External Examiner:
Muhammad Nasir
Lecturer
DCS&SE, FBAS, IIUI.
____________
2-Internal Examiner:
Mr. Muhammad Imran
Lecturer
DCS&SE, FBAS, IIUI.
____________
3-Supervisor:
Qamar Abbas
Assistant Professor
DCS&SE, FBAS, IIUI.

DEDICATION
We commit this respectful effort to our dear parents and respected teachers with unwavering held up
love trust and inspiration. With the accomplishment of our last year project after donating this procurement and
efforts to our dear parents who have been supporting and providing all the resources we can absolute our
studies and project.

Declaration
We thus pronounce that the improvement of this task and its report is altogether founded on our own endeavors
and learning achieved under the total help and direction of the appointed director Qamar Abbas. Not a solitary
piece of this work showed up in this report has been submitted for some other degree or some other college or
university or some other instructive foundation. We further announce that this task, all code, and related archives
and reports are submitted as halfway prerequisites for the level of Bachelor of Software Engineering.
Muhammad Umar Hayat

3340-FBAS/BSSE/F16
Ahsan Zafar
3307-FBAS/BSSE/F16

Acknowledgement
All commend to Allah Almighty for His favors in finished this project and favors to our last Prophet Muhammad
(PBUH). We require like to thank our superintendent Qamar Abbas for his on going meaningful support and inspiration
for our project. Thank you for your sharp attention during the completion of the project.
M Umar Hayat
3340/FBAS-BS (SE)/F16
Ahsan Zafar
3307-FBAS / (BSSE)/F16

Project in Brief
Project Title: Silkee Cosmetics
Undertaken By: M Umar Hayat (3340-FBAS /BS (SE)/F16)

Ahsan Zafar (3307-FBAS /BS (SE)/F16)
Supervised By: Qamar Abbas
Date Started: 30 Dec 2018

26 Aug 2019
Date Completed:
Tools Technologies and Bootstrap J-query javascript html css
language Used: Asp.Net Core 2.2 Code First Approach
Entity Frame Work
Clean Architecture
CQRS Pattern
vue.js
SQL Server 2016 (Database)

Visual Paradigm
Git
System Used: Core i5 RAM 8 GB

Operating System: Microsoft Windows 10

Table of Contents
Chapter 1 ..................................................................................................................................................... 1
Introduction ................................................................................................................................................... 1
1. Introduction .......................................................................................................................................... 2
1.1 Problems Statements: ..................................................................................................................... 2
1.2 Silkee Cosmetics: ................................................................................................................................. 3
1.3 Control Flow Diagram(Super Admin): ............................................................................................... 4
1.4 Control Flow Diagram(Service Provider)....................................................................................... 5
1.5 Control Flow Diagram (User): ........................................................................................................ 6
Chapter 2 ...................................................................................................................................................... 7
System Analysis ............................................................................................................................................. 7
2. Requirement............................................................................................................................................... 8
2.1 Use Case Diagram: ............................................................................................................................... 9
2.2 Use Case Description in Detail Expanded Format: ............................................................................. 36
2.2.1 Use Case Login: ........................................................................................................................... 36
2.2.2 Use Case View Silkee Dashboard: ............................................................................................. 37
2.2.3 Use Case Company Creation: ...................................................................................................... 38
2.2.4 Use Case View Company information: ...................................................................................... 39
2.2.5 Use Case Update Company: .................................................................................................... 40
2.2.6 Use Case Delete Company: ......................................................................................................... 41
2.2.7 Use Case Add User: ..................................................................................................................... 42
2.2.8 Use Case Assigning Role: ............................................................................................................ 43
2.2.9 Use Case Add User of System :.................................................................................................... 44
2.2.10 Use Case Assign Role to User of system: .................................................................................... 45
2.2.11 Use Case View User of the System: ............................................................................................ 46
2.2.12 Use Case Add Customers:....................................................................................................... 47
2.2.13 Use Case View Customers : ...................................................................................................... 48

1.2.14 Use Case Delete Customer: .................................................................................................. 49
1.2.15 Use Case Update Customers: ............................................................................................... 50
2.2.16 Use Case Add Supplier : ............................................................................................................. 51
2.2.17 Use Case View Supplier: ............................................................................................................ 52
2.2.18 Use Case Delete Supplier: ....................................................................................................... 53
2.2.19 Use Case View Update Supplier: ............................................................................................... 54
2.2.20 Use Case Add Employees: ....................................................................................................... 55
2.2.21 Use Case View Employee: ......................................................................................................... 56
2.2.22 Use Case Delete Employee: ....................................................................................................... 57
2.2.23 Use Case Update Employee: ...................................................................................................... 58
2.2.24 Use Case Add Product:............................................................................................................... 59
2.2.25 Use Case View Product : ............................................................................................................ 60
2.2.26 Use Case Delete Product : ........................................................................................................ 61
2.2.27 Use Case Update Product : ........................................................................................................ 62
2.2.28 Use Case Add Category: ............................................................................................................. 63
2.2.29 Use Case View Category :.......................................................................................................... 64
2.2.30 Use Case Delete Category : ....................................................................................................... 65
1.2.31 Use Case Update Category :................................................................................................. 66
2.2.32 Use Case Add Items: .................................................................................................................. 67
2.2.33 Use Case View Items: ................................................................................................................. 68
2.2.34 Use Case Delete Item: ................................................................................................................ 69
2.2.35 Use Case Update Item: ............................................................................................................. 70
2.2.36 Use Case Add Price Record: ....................................................................................................... 71
1.2.37 Use Case View Price Record: ............................................................................................... 72
2.2.38 Use Case Delete Price Record: .................................................................................................. 73
2.2.39 Use Case Update Price Record: ................................................................................................. 74
2.2.40 Use Case Add Purchase Order: .................................................................................................. 75
1.2.41 Use Case View Purchase Order: .......................................................................................... 76
2.2.42 Use Case Delete Purchase Order:............................................................................................... 77
2.2.43 Use Case Update Purchase Order: ............................................................................................. 78
2.2.44 Use Case Add Sale Order: .......................................................................................................... 79
2.2.45 Use Case View Sale Order:......................................................................................................... 80
2.2.46 Use Case Delete Sale Order: ...................................................................................................... 81

2.2.47 Use Case Update Sale Order: ..................................................................................................... 82
2.2.48 Use Case Add Sale Invoice: ........................................................................................................ 83
2.2.49 Use Case View Sale Invoice: ...................................................................................................... 84
2.2.50 Use Case Delete Sale Invoice: .................................................................................................... 85
1.2.51 Use Case Update Sale Invoice: ............................................................................................ 86
2.3 Sequence Diagrams: ...................................................................................................................... 87
2.3.1 Login: .......................................................................................................................................... 87
2.3.2 View Dashboard: ......................................................................................................................... 88
2.3.3 Add Company: ............................................................................................................................. 89
2.3.4 Delete Company:.......................................................................................................................... 90
2.3.5 Update Company Detail: .............................................................................................................. 90
2.3.6 Add Users: ................................................................................................................................... 92
2.3.7 Update Users: .............................................................................................................................. 92
2.3.8: Delete Users: .............................................................................................................................. 93
2.3.9: View Users: ................................................................................................................................ 93
2.3.10 Add Customers:.......................................................................................................................... 94
2.3.11 Update Customers: ..................................................................................................................... 95
2.3.12: Delete Customers: ..................................................................................................................... 96
2.3.13: View Customers: ....................................................................................................................... 97
2.3.14 Add Employee: ........................................................................................................................... 98
2.3.15 Update Employee: ...................................................................................................................... 98
2.3.16: Delete Employee: ...................................................................................................................... 99
2.3.17: View Employee: ........................................................................................................................ 99
2.3.18 Add Supplier: ........................................................................................................................... 100
2.3.19 Update Supplier: ...................................................................................................................... 100
2.3.20: Delete Supplier: ...................................................................................................................... 101
2.3.21: View Supplier: ........................................................................................................................ 101
2.3.22 Add Item: ................................................................................................................................. 102
2.3.23 Update Item: ............................................................................................................................ 102
2.3.24: Delete Item: ............................................................................................................................ 103
2.3.25: View Item: .............................................................................................................................. 103
2.3.26 Add Sale Order: ....................................................................................................................... 104
2.3.27 Update Sale Order: .................................................................................................................. 104
- 10 - | P a g e Silkee Cosmetics
2.3.28: Delete Sale Order: .................................................................................................................. 105
2.3.29: View Sale Order:..................................................................................................................... 105
2.3.30 Add Sale Invoice: ..................................................................................................................... 106
2.3.31 Update Sale Invoice: ................................................................................................................ 106
2.3.32: Delete Sale Invoice: ................................................................................................................ 107
2.3.33: View Sale Invoice: .................................................................................................................. 107
2.4 Domain Model: ................................................................................................................................ 108
Chapter 3 ................................................................................................................................................... 109
System Design ................................................................................................ Error! Bookmark not defined.
1. System Design .................................................................................................................................... 110
3.1 System Sequence Diagram of Super Admin ...................................................................................... 111
3.2 System Sequence Diagram of Service Provider Admin...................................................................... 112
1.3 System Sequence Diagram of Users: ............................................................................................ 113
3.4 Class Diagram .................................................................................................................................. 114
3.5 Entity Relationship Diagram(ERD): ................................................................................................. 116
Chapter 4 ................................................................................................................................................... 137
Implementation .............................................................................................. Error! Bookmark not defined.
2. Implementation .................................................................................................................................. 138
1.1 Functional Features: ................................................................................................................... 138
1.2 Deployment Diagram. ................................................................................................................. 139
Chapter 5 ..................................................................................................................................................... 46
System Testing ............................................................................................... Error! Bookmark not defined.
2. System Testing: .................................................................................................................................... 47
2.1 Black Box Testing:......................................................................................................................... 47
2.2 White Box Testing: ........................................................................................................................ 47
2.3 Test cases:...................................................................................................................................... 47
1.3.1 Authentication: ....................................................................................................................... 48
1.3.2 Add Users: .............................................................................................................................. 48
1.3.3 Add Employee: ........................................................................................................................ 49
1.3.4 Add Items:............................................................................................................................... 49
1.3.5 Pricing Of Items: .................................................................................................................... 50
1.3.6 Add Sale Order: ...................................................................................................................... 50
1.3.7 Add Sale Order To Invoice Test Case: ..................................................................................... 51
Test Case Result: ...................................................................................................................................... 52
Chapter 6 ..................................................................................................................................................... 53
Conclusion .................................................................................................................................................. 53
1. Conclusion ........................................................................................................................................... 54
Appendix--A................................................................................................................................................. 55
User Manual ................................................................................................................................................ 55
Chapter 2.
Chapter 1
Introduction
1|Page Silkee Cosmetics

Chapter 2.
Introduction
Silkee Cosmetic is web base project which is developed according to the needs of cosmetics
Industry. This is actually an ERP system in which we managed all aspects which company is
required.
• Finance Management
• Stock Management
• Inventory Management
• Sales Management
• Distribution Management
• Purchase Management
• HR Management
Problems Statements:
• They face many management problems.

• They face relationship between production and sales inventory resources and finance.
• You have to avoid many large losses.
• Company time loss Sales problems Financial management problems Distribution
management problems Insufficient record management and report generations.

Chapter 2.
1.2 Silkee Cosmetics:

Silkee Cosmetics Software for the cosmetics industry is designed and developed according to
the business process considering the special needs of cosmetics manufacturers. Silkee Cosmetic
managed all aspects of the cosmetics industry. Cosmetic companies are growing steadily. Along
with the increase they face many management problems that concern cosmetic companies.
Companies need to increase customer satisfaction. As well as balancing the relationship between
production and sales innovation resources and finances.
In Our System Admin identify the users who use the system and also assign their roles .Roles are
access the functionality of the dashboard.
For example Accountant only check Account Details. In Our System we managed their Product
items and also change item prices and Date limit.
Specific User of the system can make Sale Order according to the Customer needs. If Customer
is agreed to Purchase then its convert Sale Order to Invoice and also direct make invoice. If
Customer pay the Invoice then its goes to payment receipt and record has been saved according
to their transaction.

Chapter 2.
1.3 Control Flow Diagram(Super Admin):

Chapter 2.
Control Flow Diagram(Service Provider)

Chapter 2.
Control Flow Diagram (User):

Chapter 2.
Chapter 2
System Analysis

Chapter 2.
2. Requirement
System examine is way of business to determine goals objectives and to create plans that
will attain it in a build way. Examine the problem recognize the problem and its source. One
reads the manage plan and the other recognizes the needs and backgrounds of the current
system. By look into the foundations of the promise to be played the next step is to look at
the problem and recognize its unique nature. A large movement on stage explores the current
outline. In addition another understanding of the needs and location of the new substructure.
Comprehension the structures and needs of another structure is growingly frustrating and
need new thinking and the mandate of an existing structure that is equally problematic a
misunderstanding of the current structure can lead to reorganization from designing.
The model is obey by the Water fall Model which shows that the steps are organized by
specific application. As most importantly the assumption of acquisition is complete.

Chapter 2.
2.1 Use Case Diagram:

In this use case Diagram they represent the actions of user which interact the Systems.

Chapter 4 Implementation
2.2 Use Case Description in Detail Expanded Format:

In these section list of steps and every actions of user to achieve their goals in the system .And other external
system which interact with the system.
2.2.1 Use Case Login:
Use Case No. UCase-01
Scopes Online Platform for Silkee Cosmetic
Name Login
Primary Actors Super Admin
Pre-Conditions Working Internet Connection and user is on webpage
Post Conditions User login to the system
Success Scenarios
a. User click the login button
b. System show the login screen.
c. User give the authentication details
d. System check the details and then give access to user to
logged the system
Alternate a. User give wrong details. System not verify the details and
generate the message of wrong credentials. .
36 | P a g e Silkee Cosmetics
2.2.2 Use Case View Silkee Dashboard:
Scopes Online Platform for Silkee Cosmetic
Name View Dashboard
Pre-Conditions User is login as Admin
Post Conditions User login to the system
Success Scenarios
a. User is login to the system
b. 2. System will show the dashboard screen to user
Alternate a. User is not login and not access the system dashboard.
2.2.3 Use Case Company Creation:
Scopes Online Platform for Silkee Cosmetics
Name Company Creation
Pre-Conditions User login the System
Post Conditions Create company Successfully
Success Scenarios a. User enter the Add Button options.

b. System show the screen to user.
c. User provide the Details which is required to the system..
d. System Create Company Successfully.
Alternate a. User give the wrong information.
2.2.4 Use Case View Company information:
Scopes
Online Platform for Silkee Cosmetics
Name
View Company Information’s
Pre-Conditions User Added Company in the System
Post Conditions View Company Detail Successfully
Success Scenarios
a. User Click the Company Dashboard
b. System present the company details
Alternate
a. User is not logged in.
Use Case Update Company:
Scopes
Name
Update the Company Details
Pre-Conditions User Added Company in the System
Post-Conditions Update Company Detail Successfully
Success Scenarios
a. User enter the Update Company Button.
b. System show the form of updating company information.
c. User Fill the Form and click the Button.
d. System save the information in database and display success
message.
Alternate
2.2.6 Use Case Delete Company:
Scopes
Name
Delete Company.
Pre-Conditions User Added Company in System
Post Conditions Delete Company Information
Success Scenarios
a. User enter the Delete Button.
b. System delete selected information.
Alternate
2.2.7 Use Case Add User:
Scopes Online Platform for Silkee Cosmetics
Name Add Users
Pre-Conditions User Create the Company.
Post Conditions User Added Successfully.
Success Scenarios a. User is logged in.

b. User entered all information about Users who user the
Application.
c. System save changes into database and return success message.
Alternate a. User not add information properly.
2.2.8 Use Case Assigning Role:
Scopes Online Platform for Silkee Cosmetics.
Name Assigning Roles
Pre-Conditions User Add User of Company.
Post Conditions User assigning the rule to the user successfully.
Success Scenarios a. User enter the roles button information.

b. System show the information about the user.
c. User Assigned the Role to the user who use the system.
d. System save the information into database and display
message.
Alternate
c. User not properly assigning role to the user.
2.2.9 Use Case Add User of System :
Name Add Users
Primary Actor Service Provider

Pre-Conditions User login the system
Post Conditions Add Users Successfully.
Success Scenarios
a. User enter the add User button
b. System will show the view form for adding the
information which is entered by the user.
c. User give the information the fields.
d. System retain the information and display a message.
Alternate b. User give wrong information to add.
2.2.10 Use Case Assign Role to User of system:
Name Assign Roles To Users
Primary Actor Service Provider

Pre-Conditions Add Users of the system.
Post Conditions Assigning Roles to the system users Successfully.
Success Scenarios
a. User enter the assign role button to assigning the role.
b. System will pop up the form for giving information in

the fields
c. User give information which is save in database.
d. System store the giving information and display a

success message.
Alternate d. User give wrong information
2.2.11 Use Case View User of the System:
Name View Users
Primary Actors Service Provider
Pre-Conditions Add Users of the system.
Post Conditions View Users Details of the system users Successfully.
Success Scenarios
a. User enter the information of Users.
b. System display information to user.
Alternate
2.2.12 Use Case Add Customers:
Name Add Customers
Primary Actors User

Pre-Conditions User are login.
Post Conditions Add Customers successfully.
Success Scenarios
a. User enter the add Customers information button
b. System show the form for adding the information about
Customers.
c. User give the information about Customers.
d. System store the information and display message.
Alternate
a. User give wrong information about customers.
2.2.13 Use Case View Customers :
Use Case No. Use Case -13
Name View Customers
Primary Actors user
Pre-Conditions User is logged in the system.
Post Conditions User information is present to the customers.
Success Scenarios
a. user is login to the system
b. System display information to users.
Alternate a. User have not access to these information
Use Case Delete Customer:
Scopes
Name
Delete Customer.
Primary Actor User
Pre-Conditions User Add Customer who the System
Post Conditions Delete Customer Detail Successfully
Success Scenarios
a. User enter the Delete Button.
b. System delete the information of customers
successfully.
Alternate
a. User is not logged In
Use Case Update Customers:
Scopes
Name
Update Customer Information
Primary Actors User
Pre-Conditions Added Customer of the System
Post Conditions Update Customer information.
Success Scenarios
a. User click update button of customer screen.
b. System show the form of Information which has been

updated.
c. User enter details in the Form and click the Button.
d. System save the information providing by user and

display message of saving data .
Alternate
a. User click the Cancel Button.
b. System generate duplicate Name error.
2.2.16 Use Case Add Supplier :
Name Add Supplier
Primary Actors User
Post Conditions Add Supplier successfully.
Success Scenarios
a. User enter the add Supplier information button
b. System show the form for adding the information
about Supplier.
c. User give the information about Supplier.
Alternate
a. User give wrong information
b. System generate duplicate Name error
2.2.17 Use Case View Supplier:
Name View Supplier
User
Primary Actor
Pre-Conditions User is login.
Post Conditions User list is displayed.
Success Scenarios
a. User is log in.
b. System display the list of user’s successfully.
Alternate a. User not login to the system that why information not shown
successfully.
2.2.18 Use Case Delete Supplier:
Use Case No. Use Case - 18
Scopes
Name
Delete Supplier.
Primary Actors User
Pre-Conditions Add Supplier of the system
Post Conditions Delete Supplier Detail Successfully
Success Scenarios
a. User Click the Delete Button.
b. System Delete information successfully.
Alternate
a. 1.User is not logged In
2.2.19 Use Case View Update Supplier:
Use Case No. UseCase-19
Scopes
Name
Update Supplier Information
Primary Actors User
Pre-Conditions User Add Supplier in the System
Post Conditions Update Supplier Detail Successfully
Success Scenarios
a. User click the Update Information Button.
b. System display the form of updating Information.
c. User enter in all the fields of form and click the Button.
d. System store information into database and display message.
Alternate
2.2.20 Use Case Add Employees:
Name Add Employee
Primary Actors User
Post Conditions Add Employee successfully.
Success Scenarios
a. User enter the add Employee information button
Employee.
c. User give the information about Employee.
Alternate
a. User give wrong details.
2.2.21 Use Case View Employee:
Name View Employee
Primary Actors User
Post Conditions List is displaying to the user.

b. System will display List of users.
Alternate a. User is not logged in.
2.2.22 Use Case Delete Employee:
Scopes
Name
Delete Employee.
Primary Actors User
Pre-Conditions User Add Employee in the System
Post Conditions Delete Employee Detail Successfully
Success Scenarios
Alternate
2.2.23 Use Case Update Employee:
Scopes
Name
Update Employee Information
Primary Actors User
Pre-Conditions User Add Employee in the System
Post Conditions Update Employee Detail Successfully
Success Scenarios
Alternate
2.2.24 Use Case Add Product:
Name Add Product
Primary Actors User
Post Conditions Add Product successfully.
Success Scenarios a. User enter the add Product information button

b. System show the form for adding the information about Product.
c. User give the information about Product.
Alternate a. User give wrong information.

2.2.25 Use Case View Product :
Name View Product
Primary Actors User

2.2.26 Use Case Delete Product :
Scopes
Name
Delete Product.
Primary Actors User
Pre-Conditions User Add Product in the System
Post Conditions Delete Product Detail Successfully
Success Scenarios
Alternate
2.2.27 Use Case Update Product :
Scopes
Name
Update Product Information
Primary Actors User
Pre-Conditions User Add Product in the System
Post Conditions Update Product Detail Successfully
Success Scenarios

Alternate
2.2.28 Use Case Add Category:
Name Add Category
Primary Actors User
Post Conditions Add Category successfully.
Success Scenarios a. User enter the add Category information button

Categories.
c. User give the information about Category.

e. .

2.2.29 Use Case View Category :
Name View Category
Primary Actors User

2.2.30 Use Case Delete Category :
Scopes
Name
Delete Category.
Primary Actors User
Pre-Conditions User Add Category in the System
Post Conditions Delete Category Detail Successfully
Success Scenarios
Alternate
Use Case Update Category :
Scopes
Name
Update Category Information
Primary Actors User
Pre-Conditions User Add Category in the System
Post Conditions Update Category Detail Successfully
Success Scenarios
d. System store information into database and display
message.
Alternate
2.2.32 Use Case Add Items:
Use Case no. Use Case -32
Name Add Item
Primary Actors User
Post Conditions Add Item successfully.
Success Scenarios a. User enter the add Items information button

b. System show the form for adding the information about Items.
c. User give the information about Items.

2.2.33 Use Case View Items:
Name View Item
Primary Actors User

2.2.34 Use Case Delete Item:
Scopes
Name
Delete Item.
Primary Actors User
Pre-Conditions User Add Item in the System
Post Conditions Delete Item Detail Successfully
Success Scenarios
Alternate
2.2.35 Use Case Update Item:
Scopes
Name
Update Item Information
Primary Actors User
Pre-Conditions User Add Item in the System
Post Conditions Update Item Detail Successfully
Success Scenarios
message.
Alternate
2.2.36 Use Case Add Price Record:
Use Case ID No Use Case -36
Name Add Price Record
Primary Actors User
Post Conditions Add Price Record successfully.
Success Scenarios a. User enter the add Price Record information button
b. System show the form for adding the information about Price
Records.
c. User give the information about Price Records.

Use Case View Price Record

Name View Price Record
Primary Actors User

2.2.38 Use Case Delete Price Record:
Scopes
Name
Delete Price Record.
Primary Actors User
Pre-Conditions User Add Price Record in the System
Post Conditions Delete Price Record Detail Successfully
Success Scenarios
Alternate
a. User is not logged In.
2.2.39 Use Case Update Price Record:
Scopes
Name
Update Price Record Information
Primary Actors User
Pre-Conditions User Add Price Record in the System
Post Conditions Update Price Record Detail Successfully
Success Scenarios
message.
Alternate
2.2.40 Use Case Add Purchase Order:
Name Add Purchase Order
Primary Actors User
Pre-Conditions Prices of item and Date added in Price Record.
Post Conditions Add Purchase Order successfully.
Success Scenarios a. User enter the add Purchase Order information button
Purchase Order.
c. User give the information about Purchase Orders.

Use Case View Purchase Order:
Name View Purchase Order
Primary Actors User

2.2.42 Use Case Delete Purchase Order:
Scopes
Name
Delete Purchase Order.
Primary Actors User
Pre-Conditions User Add Purchase Order in the System
Post Conditions Delete Purchase Order Detail Successfully
Success Scenarios
Alternate
2.2.43 Use Case Update Purchase Order:
Scopes
Name
Update Purchase Order Information
Primary Actors User
Pre-Conditions User Add Purchase Order in the System
Post Conditions Update Purchase Order Detail Successfully
Success Scenarios
c. User enter in all the fields of form and click the
Button.
message.
Alternate
2.2.44 Use Case Add Sale Order:
Name Add Sale Order
Primary Actors User
Pre-Conditions Purchase Order customer employee are added.
Post Conditions Add Sale Order successfully.
Success Scenarios a. User enter the add Sale Order information button
b. System show the form for adding the information about Sale
Orders.
c. User give the information about Sale Orders.

2.2.45 Use Case View Sale Order:
Name View Sale Order
Primary Actors User
Post Conditions List is displaying to user.

2.2.46 Use Case Delete Sale Order:
Scopes
Name
Delete Sale Order.
Primary Actors User
Pre-Conditions User Add Sale Order in the System
Post Conditions Delete Sale Order Detail Successfully
Success Scenarios
Alternate
a. User is not logged in
2.2.47 Use Case Update Sale Order:
Scopes
Name
Update Sale Order Information
Primary Actors User
Pre-Conditions User Add Sale Order in the System
Post Conditions Update Sale Order Detail Successfully
Success Scenarios
message.
Alternate
2.2.48 Use Case Add Sale Invoice:
Name Add Sale Invoice
Primary Actors User
Pre-Conditions Purchase Order customer employee Sale Order are added.
Post Conditions Add Sale Invoice successfully.
Success Scenarios
a. User enter the add Sale Order information button
b. User also convert Sale Order to Invoice
c. System show the form for adding the information about Sale
Order.
d. User give the information about Sale Orders.
e. System store the information and display message.

2.2.49 Use Case View Sale Invoice:
Name View Sale Invoice
Primary Actors User
Pre-Conditions User login to the system.

2.2.50 Use Case Delete Sale Invoice:
Scopes
Name
Delete Sale Invoice.
Primary Actors User
Pre-Conditions User Add Sale Invoice in the system.
Post Conditions Delete Sale Invoice Detail Successfully
Success Scenarios
Alternate
Use Case Update Sale Invoice:
Scopes
Name
Update Sale Invoice Information
Primary Actors User
Pre-Conditions User Add Sale Invoice in the system
Post Conditions Update Sale Invoice Detail Successfully
Success Scenarios
c. User enter in all the fields of form and click the
Button.
message.
Alternate
Sequence Diagrams:
Sequence diagram is use for specific situation of use case the event that external actors generate their
order and possible inter system event.
2.3.1 Login:
Figure 2.3.1 Sequence diagram Login
2.3.2 View Dashboard:
Figure 2.3.2: Sequence Diagram: View Dashboard Information
2.3.3 Add Company:
2.3.4 Delete Company:
Figure 2.3.4 Sequence Diagram: Delete Company
2.3.5 Update Company Detail:
2.3.6 Add Users:
2.3.7 Update Users:
2.3.8: Delete Users:
2.3.9: View Users:
2.3.10 Add Customers:
2.3.11 Update Customers:
2.3.12: Delete Customers:
2.3.13: View Customers:
2.3.14 Add Employee:
2.3.15 Update Employee:
2.3.16: Delete Employee:
2.3.17: View Employee:
2.3.18 Add Supplier:
2.3.19 Update Supplier:

2.3.20: Delete Supplier:
2.3.21: View Supplier:

2.3.22 Add Item:
2.3.23 Update Item:

2.3.24: Delete Item:
2.3.25: View Item:

2.3.26 Add Sale Order:
2.3.27 Update Sale Order:

2.3.28: Delete Sale Order:
2.3.29: View Sale Order:

2.3.30 Add Sale Invoice:
2.3.31 Update Sale Invoice:

2.3.32: Delete Sale Invoice:
2.3.33: View Sale Invoice:

2.4 Domain Model:
Conceptual model is also called as domain model and it is used to identify all the concerning concepts (which
may will be later turn into classes) of the system. The high level collaboration between concepts is used to
explain the greater picture of the system.

Chapter 3
System Design

System Design
In this chapter we have develop Sequence diagram Class diagram and Entity Relation Diagram. Sequence
diagram shows message that passing between object. Class diagram describe the class having attribute and
method. ERD is relational database. It have column detail and relationship between table.

3.1 System Sequence Diagram of Super Admin
Figure 1.1 System Sequence Diagram of Super Admin

3.2 System Sequence Diagram of Service Provider Admin

System Sequence Diagram of Users:

3.4 Class Diagram


3.5 Entity Relationship Diagram(ERD):

















3.6DatabaseRelationship




Chapter 4
Implementation

Implementation
Implementation is also called software programming or coding. In this chapter we discuss about deployment
diagram.
Functional Features:
Features of Silkee Cosmetics are:
a. Ease to use
b. Responsiveness
c. Inventory Management
d. Cost-Accounting
e. Financial Management
f. Sales Management
g. Warehouses Management
h. Multi-Company Accounting
i. Stock Management
j. HR Management
k. Reliability
l. Security

Deployment Diagram.
Figure 4.1 Deployment Diagram

Chapter 6 Conclusion
Chapter 5
System Testing
System Testing:
System testing is to improve the system and minimize system error. Testing the system at specific situation
condition and requirement to check whether system run at specific condition.
Black Box Testing:

Black box testing is a type of testing where we test the code externally. In this type of testing we test
code in running form. Test application under some certain condition and value.
White Box Testing:

White box testing is a type of testing where we test our code with different condition and scenario.
This is also called code based testing and structural inspection. In this type of testing we test
implementation of code object and function. We test every behavior of the code.
Test cases:
Test system at certain condition and scenario whether software will work or not work under given
scenario.
Authentication:
Test Case # Test Case-I

Functional Module Authenticate
Action to Accomplish a. User go to login page
b. User enter login details.
c. User is Sign in
d. Finish
Pre-condition Application is in running state

Test By Ahsan Zafar
Domain Web browsers
Expected Outcome User Sign in
Remarks: Test passed successfully
Add Users:
Test Case # Test Case-II

Functional Module User Registration
Action to Accomplish a. User fill Add User form first.
b. System save record and notify User
Added Successfully.
Purpose Add User

Pre-condition User should have opened as Service
Provider
Test By Ahsan Zafar
Domain Web browsers
Expected Outcome Add User of the System
Add Employee:
Test Case # Test Case-III

Functional Module Add Employee
Action to Accomplish a. Click Employee from sidebar and
open Employee list
b. Click Add Employee Button
c. Enter Employee details.
d. User will click if any employee with
same code is exist or not
e. System will Successfully Add
Employee
Pre-condition Employee List

Test By M Umar Hayat
Domain Web browsers
Expected Outcome Successfully Add Employee
Add Items:
Test Case # Test Case-IV

Functional Module Add Item
Action to Accomplish a. Open Product tab and click on item
b. Click Add Item Button
c. User enter details
d. System record in Database and notify
the User
Pre-condition User Sign in

Domain Web Browser
Expected Outcome Item has been added Successfully.
Remarks: Test passed successfully.
Pricing Of Items:
Test Case # Test Case-V

Functional Module Pricing of Item
Action to Accomplish a. Open Product tab and click price
record
b. System will Popup model of Add
New Price
c. User give the pricing of item.
d. System Saved the following Detail
and notify the User

Test By Ahsan Zafar
Domain Web Browsers
Expected Outcome Item Prices has been updated
Add Sale Order:
Test Case # Test Case-VI

Functional Module Add Sale Order
Action to Accomplish a. Open sale order from sale order tab
then click add sale order.
b. Enter the required data and click the
save button
c. System will save the Record and
generate Message Record Saved
Successfully.
d. Finish
Prerequisites User are login on system

Domain Web Browsers
Expected Outcome Successfully Added Sale Order
Add Sale Order To Invoice Test Case:
Test Case # Test Case-VII

Functional Module Sale Order To Invoice
Action to Accomplish a. User will go to Invoice Dashboard.
b. User will select sale order to Invoice
Filed they all data insert in the fields.
And User click the Save Button.
c. System will save the Record and
generate Message Record Saved
Successfully.
d. Finish

Domain Web Browsers
Expected Outcome Convert Sale Order to Invoice Successfully
Test Case Result:
Test Case # Result

Test Case-I Passed
Test Case-II Passed
Test Case-III Passed
Test Case-IV Passed
Test Case-V Passed
Test Case-VI Passed
Test Case-VII Passed
Chapter 6
Conclusion
1. Conclusion
“Silkee Cosmetics” is an ERP is designed and developed according to the business process
considering the special needs of cosmetics manufacturers. Cosmetic companies are expanding
continuously. Along with the expansion they face many management problems that plague cosmetic
companies. Companies need to increase customer satisfaction. As well as balance the relationship
between production and sales inventory resources and finance.
In Our Silkee Cosmetics System we manage all aspect which silkee cosmetics required. We manage
their Inventory finance Customers Employees and their order
Appendix--A
User Manual
A. User Manual
User manual is the complete information of the system functionality and usage for the user. To follow
these instruction user easily learn how to use system functionality feature and step by step procedure.
Login Page:
DashBoard:
Customers:
Chart of Account:
Add Product:
Add Company:
Department:
Employees:
Financial Year:
Invoice:
Add Invoice:
Items:
Journal Vouchers :
Purchase Orders:
Invoice Reports:
Sale Orders:
Suppliers:
Transaction:

Fyp1 1

Uploaded by

Document Information

Original Title

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

Fyp1 1

Uploaded by

Copyright:

Available Formats

Silkee Cosmetics

Muhammad Umar Hayat 3340-FBAS/BSSE/F16

Ahsan Zafar 3307-FBAS/BSSE/F16

Department of Computer Science and Software Engineering Faculty of Basic

International Islamic University Islamabad

-1-|Page Silkee Cosmetics

DCS&SE, FBAS, IIUI.

Mr. Muhammad Imran

DCS&SE, FBAS, IIUI.

DCS&SE, FBAS, IIUI.

-3-|Page Silkee Cosmetics

-4-|Page Silkee Cosmetics

Muhammad Umar Hayat

-5-|Page Silkee Cosmetics

-6-|Page Silkee Cosmetics

Project Title: Silkee Cosmetics

Undertaken By: M Umar Hayat (3340-FBAS /BS (SE)/F16)

Supervised By: Qamar Abbas

Date Started: 30 Dec 2018

SQL Server 2016 (Database)

System Used: Core i5 RAM 8 GB

-7-|Page Silkee Cosmetics

-8-|Page Silkee Cosmetics

-9-|Page Silkee Cosmetics

1|Page Silkee Cosmetics

• They face many management problems.

2|Page Silkee Cosmetics

1.2 Silkee Cosmetics:

3|Page Silkee Cosmetics

1.3 Control Flow Diagram(Super Admin):

4|Page Silkee Cosmetics

Control Flow Diagram(Service Provider)

5|Page Silkee Cosmetics

Control Flow Diagram (User):

6|Page Silkee Cosmetics

7|Page Silkee Cosmetics

8|Page Silkee Cosmetics

2.1 Use Case Diagram:

9|Page Silkee Cosmetics

2.2 Use Case Description in Detail Expanded Format:

2.2.1 Use Case Login:

Use Case No. UCase-01

Scopes Online Platform for Silkee Cosmetic

Primary Actors Super Admin

Pre-Conditions Working Internet Connection and user is on webpage

Post Conditions User login to the system

2.2.2 Use Case View Silkee Dashboard:

Use Case No. UCase-02

Scopes Online Platform for Silkee Cosmetic

Name View Dashboard

Primary Actors Super Admin

Pre-Conditions User is login as Admin

Post Conditions User login to the system

2.2.3 Use Case Company Creation:

Use Case No. UCase-03

Scopes Online Platform for Silkee Cosmetics

Name Company Creation

Primary Actors Super Admin

Pre-Conditions User login the System

Post Conditions Create company Successfully

Success Scenarios a. User enter the Add Button options.

Alternate a. User give the wrong information.

2.2.4 Use Case View Company information: