Government College University Faisalabad Page i

Bulk Branded SMS

By

Mohammad Zouraiz Butt 2017-GCUF-061518

Raza Abbas 2017-GCUF-061463

Usama Bin Afzal 2017-GCUF-061521

BACHELOR OF
SCIENCE IN
COMPUTER SCIENCE

DEPARTMENT OF COMPUTER SCIENCE

Government College University Faisalabad

2021

1
 DECLARATION

We hereby declare that this project, neither whole nor as a part has been copied out from any source.
We have developed this project and accompanied report entirely based on our personal efforts. If any
part of this project is proved to be copied out from any source. We will stand by all the consequences.
No Portion of the work presented has been submitted of any application for any other degree of this or
any other university or institute.

Signature of the Student

Name: USAMA AFZAL
Registration: 2017-GCUF-061521

Signature of the Student

Name: M.ZOURAIZ BUTT
Registration: 2017-GCUF-061518

Signature of the Student

Name: RAZA ABBAS
Registration:2017-GCUF-061463

2
 ACKNOWLEDMENT

We would like to express our gratitude to our advisor Miss Memoona for his guidance and support, and
his continuous enthusiasm and encouragement throughout the project. We are also very thankful and
extend our thanks to the Heads and staff members of the department of CS & IT for their cooperation by
sharing the load and for giving time to work on this project.
Finally, thanks to the friends, who have helped and give us many suggestions, supports and corrections
during the project.

3
TABLE OF CONTENTS
Table of Contents………………………………………………………..vi
1 INTRODUCTION……………………………………………………………………1
1.1introduction…………………………………………………………………………..8
1.2 Background.................................................................................................................8
1.3 Purpose........................................................................................................................9
1.4 Scope………………………………………………………………………………...9
1.5 Objective.....................................................................................................................10
1.6 Intended Audience and Reading Suggestions……………………………………………....10
2 SOFTWARE REQUIREMENTS AND SPECIFICATION....................................11
2.1 Overall Description.....................................................................................................12
2.1.1 Product Perspective..................................................................................................13
2.1.2 Product Features ......................................................................................................13
2.1.3 Design and Implementations Constraints …………………………………………14
2.1.4 Assumptions and Dependencies...............................................................................14
2.2 System Features...........................................................................................................14
2.2.1 System Features........................................................................................................15
2.3 External Interface Requirements…………………………………………………….15
2.3.1 User Interfaces……………………………………………………………………..15
2.3.2 Hardware Interfaces………………………………………………………………..15
2.3.3 Software Interfaces…………………………………………………………………16
2.3.4 Communication Interfaces………………………………………………………….16
2.4 Other Nonfunctional Requirements…………………………………………………..16
2.4.1 Performance Requirements……………………………………………………...….16
2.4.2 Safety Requirements……………………………………………………………..…16
2.4.3 Security Requirements…………………………………………………………..….16
3 Analysis (use case model)………………………………………………………….….17
3.1 Identifying Actors and Use Cases using Textual Analysis ………………………....17
3.2 Forming Use Case Diagram with Candidate and Use Cases ………………………19
3.3 Describe the Events Flow for Use Case …………………………………………….20
4 Design………………………………………………………………………………….32
4.1 Architecture Diagram ………………………………………………………………..33
4.2 ERD with Data Dictionary ………………………………………………………......34
4.3 Data Flow Diagram (Level 0 and Level 1) . ………………………………………...36
4.4 Class Diagram ……………………………………………………………………….38
4.5 Object Diagram ……………………………………………………………………...39
4.6 Sequence Diagram …………………………………………………………………..42
4.7 Activity Diagram ……………………………………………………………………44
4.8 Collaboration Diagram ………………………………………………………….......46
4.9 State Transition Diagram……………………………………………………………48
5 Implementation………………………………………………………………………50
5.1 Component Diagram ……………………………………………………………….52
5.2 Deployment Diagram ………………………………………………………………54
6 Testing (Software Quality Attributes) ……………………………………………56

4
6.1 Test Case Specification ……………………………………………………………58
6.2 Black Box Test Cases: …………………………………………………………….60
6.2.1 BVA or Boundary Value Analysis ……………………………………………..62
6.2.2 Equivalence Class Partitioning …………………………………………………66
7 Tools and Technologies ……………………………………………………………68
7.1 Programming Languages …………………………………………………………70
7.2 Operating Environment…………………………………………………………....72

5
List of Figures

Figures Page No
Fig 2.3.1 Pg 12
Fig 2.3.2 Pg 14
Fig 3.3.1 Pg 18
Fig 3.3.2 Pg 19
Fig 3.3.3 Pg 20
Fig. 4.1.1 Pg 33
Fig. 4.2.1 Pg 45
Fig. 4.3.1 Pg 46
Fig. 4.4.1 Pg 47
Fig. 4.5.1 Pg 48
Fig. 4.6.1 Pg 49
Fig. 4.7.1 Pg 50
Fig. 4.8.1 Pg 51
Fig. 4.9.1 Pg 52
Fig. 5.1 Pg 54
Fig. 5.2 Pg 55
Fig 6.1 Pg 63
Fig 6.2 Pg 65
Fig 7.2 Pg 68

6
List of Tables

Table 4.1 Pg 34
Table 4.2.1 Pg 35
Table 4.2.2 Pg 36
Table 4.2.3 Pg 37
Table 4.2.4 Pg 38
Table 4.2.5 Pg 39
Table 4.2.6 Pg 40
Table 4.2.7 Pg 41
Table 4.2.8 Pg 42
Table 4.2.9 Pg 43
Table 4.2.10 Pg 44
Table 4.2.11 Pg 45

Chapter No 1:
Introduction to the Problem
Introduction:

7
Bulk messaging is the dissemination of large numbers of SMS messages for delivery to mobile phone terminals.
It is used by media companies, enterprises, banks for marketing and fraud control and consumer brands for a
variety of purposes including entertainment, enterprise and mobile marketing.
While SMS (Short Message Service), a text messaging service, elicits the appeal of instantaneous communication
by using mobile technology to send a text message to anyone anytime and anywhere, bulk SMS system has
expanded that capability of SMS by implementing the ability to easily send multiple SMS messages to intended
recipients with reliability. The advantages of bulk SMS can be applied in schools and universities to further
develop classroom interactions and set up a virtual community as a public relations system. Lecturers can conduct
mobile quizzes in many question forms with their students via SMS. Moreover, bulk SMS system provides an
information service such as sending special announcements, news and interest information for lecturers, students
and other related recipients.
Bulk SMS is nothing but send bulk amount of messages at a time or one click. The Bulk message sender generally
used to send a message to large number of recipient. It is a web based software is needed to send lacks of messages
at a time. Bulk message is the dissemination of the large number of message for delivery to mobile phones. No
software installation is required by your customer our bulk SMS module will be available through the SMS
platform web based administration tool. Now a day's it is very popular to send bulk amount of the message in the
organization & Used in Marketing and Banking. Bulk SMS is often used by Big & small business owners, E-
commerce industry, media Companies, Banks for Alerts, Marketing and Fraud control alerts, Reminders,
Marketing of products and services. It’s also commonly used between staffs of company or bank and their clients.
One advantage of Bulk Messaging is that it delivers your message directly to the mobile handsets anywhere
around World.
1.2 Types of Bulk SMS Services:
1.2.1 Promotional SMS service:
Promotional SMS is uses brands to registered and non-registered mobile numbers to boost their reach and sales.
These are SMS which are sent with the objective of promoting your product or service. This category includes
any sales & marketing messages which may or may not be solicited by the recipient. Promotional SMS can be
send only from 9AM to 9PM and only to numbers that are Non- DND numbers. Bulk SMS is widely used for
promotional services. It is known as a very important marketing tool. You can come up with a new offer for your
store and inform your customers about the same in just a matter of minutes. SMS service is very useful for
updating your customers about different information related to your “BULK SMS SENDER” business. You could
use this platform to entice your customers and get them to do more business with you. This is one of the very
important ways of sending bulk SMS. Benefits of promotional SMS are that it is cost effective and businesses
can get quick responses from their customers.
Examples of Promotional SMS: Dear Travel Agents, Now Get Flat 10% Off on Flight same has been updated
on the portal. Login now and start booking !
1.2.2 Transactional SMS service:
Transactional SMS is informative SMS people like to receive these SMS, Like banking, school , colleges , alerts
, bill payment reminders , OTP etc. And these SMS will be deliver to all DND and Non-DND numbers and it
works 24 hours. Messages can be sent 24/7 from your own 6-character Sender ID. These are messages Which are
sent to your customer to pass on information necessary for using your Product or service.
Examples of Transactional SMS:
1) A message sent by a bank to an account holder regarding his/her available account balance.
2) If you are a university and would like to send messages to the parents of your students about their marks

Background:
8
Bulk SMS is nothing but send bulk amount of messages at a time or one click. The Bulk message sender generally
used to send a message to large number of recipient. It is a web based software is needed to send lacks of messages
at a time. Bulk message is the dissemination of the large number of message for delivery to mobile phones. No
software installation is required by your customer our bulk SMS module will be available through the SMS
platform web based administration tool Now a day's it is very popular to send bulk amount of the message in the
organization & Used in Marketing and Banking. Bulk SMS is often used by Big & small business owners, E-
commerce industry, media Companies, Banks for Alerts, Marketing and Fraud control alerts, Reminders,
Marketing of products and services. It’s also commonly used between staffs of company or bank and their clients.
One advantage of Bulk Messaging is that it delivers your message directly to the mobile handsets anywhere
around World. Bulk SMS is one of the most popular & effective marketing tool. Bulk SMS is a big revolution in
mobile industry. In these days Bulk SMS is most preferable services for marketing purpose and many enterprises
used this service. Bulk SMS is one of the best and effective tools of marketing. History of Bulk SMS is very
effective and innovative. SMS was an accidental success that surprise mobile industry. Some people criticize that
SMS service but it is used by few network operators for marketing and promotion. After some time Bulk SMS is
very popular and it prove own importance in market. Bulk SMS adopted by enterprises, advertising industry etc.
SMS stands on short message service. Every one sends and receives SMS easily but in early days SMS is less
used by people. Bulk SMS is creating a big revolution in mobile industry and build own importance with big
popularity. Today mobile phone is an integral part of our modern life that connects one people to another instantly.
Mobile phone is the effective way of communication; you can use this path to reach easily every people. Mobile
phones provide some facility like voice call, SMS etc. SMS is the term that change the world and make own
innovative history. Today you get in touch with large number of people on his mobile within seconds using Bulk
SMS. Enterprises always touch with own customers and staff via Bulk SMS.

Purpose:
The main purpose is to build a website that can help user to send bulk SMS to their target audience. And give
reports in the form of dashboard so that user can analyze how much SMS has he sent and in
Which group the desire message is reached. The project is also helpful to marketing users in which they can send
bulk messages to their targeted audience about their products. It is a cross network app that can send messages to
any user that is registered with different companies
Scope:
This system provides functionality to the user in which it can send messages to their desired place. Helping
business users and any other client to build their business and any other type of campaign.
• Banking:
• Marketing And Advertising Agencies:
• School And Education:
• Travel Agencies:
• Insurance Companies:
• Healthcare:
• Marriage Invitations:
• E-Commerce:

Objective:

Keeping in mind about today Business goals. Following are the objectives that needs to be achieved to accomplish
the desire goals. Business goals are following,

9
 • Allowing user to send bulk SMS to the targeted audience.
• User can see reports in the form of dashboard and can also export data in raw form.
• User can monitor their Campaigns
• It can also be used to spread awareness
•
• Objectives that needs to be achieved.
• Creating User login
• Off-Net/On-Set Support
• Giving access to user depending upon their package
• Priority to send SMS on On-set ( Distinguish Feature)
• Assigning page access control.
• Creating package details
• Dynamic Template usage
• Dynamic Masking Change
• Export information option.
• Dashboard report.
Intended Audience and Reading Suggestions:
Following Users are intended Audiences
• Banking:
• Marketing And Advertising Agencies:
• School And Education:
• Travel Agencies:
• Insurance Companies:
• Healthcare:
• Marriage Invitations:
• E-Commerce:

Chapter No 2:
Software Requirement Specification

10
2.1 Overall Description:
2.1.1 Product Perspectives:
The idea that inspired us to do this project is an SMS bulk sender website. That could send million of messages
in short period of time. That is the main reason for building this project that can help users in building their market.

2.1.2 Product Features:

The main features are following
.
➢ Sending bulk sms to the end user
➢ Giving packages to the user based on their package selection
➢ Giving users the option to select template of their own choice
➢ Sending messages on their desired group separately
➢ Complete information given regarding illness in which we are dealing with

2.1.3 Design and Implementation Constraints:

➢ Frontend design limitations (Responsive design)

➢ Requirement of Telecommunication company API’s to send bulk messages

2.1.4 Assumptions and Dependencies

We are assuming that the application will be working in line with expectations of planned functionality as we are
mainly depending on ASP.NET and C# framework for backend development, MySQL Server for database, and
HTML, CSS, JQuery and Javascript for frontend with other 3rd party libraries

2.2 System Features

2.2.1 System Features 1:

This system has following major roles / layers, where each role has different features,
Administration
➢ Can manage masking
➢ Can manage user management
➢ Can manage ranking management
➢ Can manage packages
➢ Can manage user access
Description and Priority

This interface has full access to all application features and is primarily responsible for maintaining
control over user creation / modification and role management. All other attributes are also available

11
 under this role as specified.

Stimulus/Response Sequences:

Fig . 2.3.1

Functional Requirements
This section contains all functional requirements of super admin user
REQ-SF1-1: Create/Read operation in Contact Groups
REQ-SF1-2: Update/Delete operation in contact Groups
REQ-SF1-2: Create/Read operation in Contact Numbers

12
 REQ-SF1-2: Update/Delete operation in Contact Numbers
REQ-SF1-2: Create/Read operation in Message Template
REQ-SF1-2: Update/Delete operation in Message Template
REQ-SF1-2: Start/Assign in Campaign
REQ-SF1-2: View in Campaign
REQ-SF1-2: View reports of Campaign
REQ-SF1-2: Change Password
REQ-SF1-2: Create/Read operation in Masking
REQ-SF1-2: Update/Delete operation in Masking
REQ-SF1-1: Create/Read operation in User
REQ-SF1-2: Update/Allow operation in User
REQ-SF1-1: Create/Assign operation in Ranking
REQ-SF1-2: Update/Delete operation in Ranking
REQ-SF1-1: Assign operation in Packages
REQ-SF1-2: Update operation in Packages

2.2.1 System Features 2:

This system has following major roles / layers, where each role has different features,
User
➢ Can Create/update/delete/view in group contact
➢ Can Create/update/delete/view in template
➢ Can Create/update/delete/view in contacts
➢ Can start/delete/view Campaign

Description and Priority

This interface has partial access to all application features and is primarily responsible for control over
assign tasks in creation / modification and role management. All other attributes are also available under this role
as specified.

Stimulus/Response Sequences

13
Functional Requirements Fig . 2.3.2

This section contains all functional

requirements of super admin user
REQ-SF1-1: Create/Readoperation in Contact Groups
REQ-SF1-2: Update/Delete operation in contact Groups
REQ-SF1-2: Create/Read operation in Contact Numbers
REQ-SF1-2: Update/Delete operation in Contact Numbers
REQ-SF1-2: Create/Read operation in Message Template
REQ-SF1-2: Update/Delete operation in Message Template
REQ-SF1-2: Start/Assign in Campaign
REQ-SF1-2: View in Campaign
REQ-SF1-2: View reports of Campaign
REQ-SF1-2: Change Password
REQ-SF1-2: View masking

2.3 External Interface Requirements:

14
2.3.1 User Interfaces:

User interface is pretty friendly. User can easily understand that interface is made for SMS purposes.
Front end is responsive for all devices. User can easily understand the required areas he needs to visit.

2.3.2 Hardware Interfaces

The most common set of requirements defined by any operating system are software application is the physical
computer resources also known as hardware a hardware requirement list is often accompanied by a hardware
compatibility list (HCL), especially in case of operating system HCL lists tested compatibility and sometimes in-
compatibility hardware devices for a particular operating system or application. The following sub-sections
discuss the various aspects of hardware requirement.

 Hardware Requirements For Present Project:

• Processor : Intel core i3

• RAM : 2GB
• Hard disk : 500GB ( Minimum 80GB)

2.3.3 Software Interfaces:

Software specification deal with defining software resource requirements and prerequirement that needs to be
installed on a computer to provide optimal functioning of an application. These requirement are pre requirement
are generally not included in the software installation package and need to be installed separately before the
software is installed. 

Software Requirements For Present Project:

• Operating System : Windows 7

• Front - end : C# .NET , HTML, CSS, Java Script

• Back - end : MySQL

15
 a. Tools: MS SQL Server

2.3.4 Communications Interfaces

This is a web based application and relies on internet HTTP protocol for communication with client web browser
software. Users are recommended to use latest web browsers for ultimate experience from the application.

2.4 Other Nonfunctional Requirements

2.4.1 Performance Requirements
Following are the performance requirements of web application,
• Device performance
Windows 10, 500 GB Storage/4GM RAM
• Server performance
➢ Requests per second (RPS)
➢ Uptime.
➢ Error rates.
➢ Thread count.
System-level performance metrics.
Average response time (ART)
Peak response times (PRT) • Security-related metrics.

c. Database performance
• Number of Queries executed per second
• Network performance
• Measuring Bandwidth
• Measuring latency

2.4.2 Safety Requirements

If there is extensive damage to a wide portion of the database due to catastrophic failure, such as a disk crash,
the recovery method restores a past copy of the database that was backed up to archival storage and reconstructs
a more current state by reapplying or redoing the operations of committed transactions from the backed up log,
up to the time of failure. Server database should be backed up weekly.
If user enter password 3 times in wrong attempts. Account will be blocked which it has to opened by Admin on
request. If login on another device or pc. Without logging out. If you try to login in another browser or device
Login portal will ask a security question.
Signing up first time. Login portal will ask to set a security question.

2.4.3 Security Requirements

System is protected by authentication and authorization policies, so every users has a limited access to certain
application parts. They can only view or use functionality as allowed by super admin of their domain. Hence,
application assets are protected from unauthorized access at all times.

16
Chapter No 3:

Analysis (Use Case Model)

3.1 Identifying Actors and Use Cases using Textual Analysis

Following are the actors that take part in the process

• Admin

• User

1: Super Admin:

Super Admin plays a crucial role in this application. He can perform many tasks on the application. Admin is
managing many tasks on the program. He is managing the following tasks

• Masking
• User management
• Ranking
• Packages

2: User:

User also plays a major role in this application. He can perform many tasks as well on the application related to
their campaign. He can run the following tasks

• Create Groups
• Create Contact Number
• Add Message Template
• Create Campaign

3.2 Forming Use Case Diagram with Candidate and Use Cases:

1: User

17
 Fig . 3.2.1

2: Admin.

18
 Fig . 3.2.2

3.2.3 Complete Diagram with Actors

19
 Fig . 3.2.3

3.3 Describe the Events Flow for Use Case

20
Use Case Descriptions
Groups Management
1. Use Case: Create Groups

Primary Actors: User

Secondary Actor: System
Status: developed
Goals in Context: to create Groups
Pre-Condition:
• System has an updated browser and working internet connection
• User must login first

Post-Condition: Groups Created

Scenario: Go to View Group page
Exception: server exception

2. Use Case: Update Groups

Primary Actors: User

Secondary Actor: System
Status: developed
Goals in Context: to update Groups
Pre-Condition:
• System has an updated browser and working internet connection
• User must login first

Post-Condition: Groups Updated

Scenario: Go to View Group page
Exception: server exception

3. Use Case: Delete Groups

Primary Actors: User

Secondary Actor: System
Status: developed
Goals in Context: to Delete Groups

21
 Pre-Condition:
• System has an updated browser and working internet connection
• User must login first

Post-Condition: Groups Deleted

Scenario: Go to View Group page
Exception: server exception

4. Use Case: View Groups

Primary Actors: User

Secondary Actor: System
Status: developed
Goals in Context: to view Groups
Pre-Condition:
• System has an updated browser and working internet connection
• User must login first

Post-Condition: Viewing Groups

Scenario: Go to View Group page
Exception: server exception

Contact Numbers:
5. Use Case: Create Contact Numbers

Primary Actors: User

Secondary Actor: System
Status: developed
Goals in Context: to create contact numbers
Pre-Condition:
• System has an updated browser and working internet connection
• User must login first

Post-Condition: Contact numbers created

Scenario: Go to View Contact Number page
Exception: server exception

6. Use Case: Update Contact Numbers

22
 Primary Actors: User
Secondary Actor: System
Status: developed
Goals in Context: to update contact numbers
Pre-Condition:
• System has an updated browser and working internet connection
• User must login first

Post-Condition: Contact numbers updated

Scenario: Go to View Contact Number page
Exception: server exception

7. Use Case: Delete Contact Numbers

Primary Actors: User

Secondary Actor: System
Status: developed
Goals in Context: to delete contact numbers
Pre-Condition:
• System has an updated browser and working internet connection
• User must login first

Post-Condition: Contact numbers deleted

Scenario: Go to View Contact Number page
Exception: server exception
8. Use Case: View Contact Numbers
Primary Actors: User
Secondary Actor: System
Status: developed
Goals in Context: to View contact numbers
Pre-Condition:
• System has an updated browser and working internet connection
• User must login first

Post-Condition: viewing Contact Centers

Scenario: Go to View Contact Number page
Exception: server exception

23
 Message template
9. Use Case: View message template

Primary Actors: User

Secondary Actor: System
Status: developed
Goals in Context: View Message Template
Pre-Condition:
• System has an updated browser and working internet connection
• User must login first

Post-Condition: Message template Viewed

Scenario: Go to View Message Template page
Exception: server exception
10. Use Case: Update message template

Primary Actors: User

Secondary Actor: System
Status: developed
Goals in Context: Update Message Template
Pre-Condition:
• System has an updated browser and working internet connection
• User must login first

Post-Condition: Message template updated

Scenario: Go to View Message Template page
Exception: server exception

11. Use Case: Delete message template

Primary Actors: User

Secondary Actor: System
Status: developed
Goals in Context: Update Message Template
Pre-Condition:
• System has an updated browser and working internet connection
• User must login first

Post-Condition: Message template updated

Scenario: Go to View Message Template page

24
 Exception: server exception

12. Use Case: Add message template

Primary Actors: User

Secondary Actor: System
Status: developed
Goals in Context: Add Message Template
Pre-Condition:
• System has an updated browser and working internet connection
• User must login first

Post-Condition: Message template added

Scenario: Go to View Message Template page
Exception: server exception
Campaign:
13. Use Case: Start Campaign

Primary Actors: User

Secondary Actor: System
Status: developed
Goals in Context: Start Campaign
Pre-Condition:
• System has an updated browser and working internet connection
• User must login first

Post-Condition: Campaign Started

Scenario: Go to Campaign page
Exception: server exception

14. Use Case: View Campaign

Primary Actors: User

Secondary Actor: System
Status: developed
Goals in Context: View Campaign
Pre-Condition:
• System has an updated browser and working internet connection
• User must login first

25
 Post-Condition: Campaign Viewed
Scenario: Go to Campaign page
Exception: server exception

15. Use Case: Delete Campaign

Primary Actors: User

Secondary Actor: System
Status: developed
Goals in Context: Deleted Campaign
Pre-Condition:
• System has an updated browser and working internet connection
• User must login first

Post-Condition: Campaign Deleted

Scenario: Go to Campaign page
Exception: server exception

Admin Role:
User Management
16. Use Case: Create User

Primary Actors: Admin

Secondary Actor: System
Status: developed
Goals in Context: Create User
Pre-Condition:
• System has an updated browser and working internet connection
• User must login first

Post-Condition: User Created

Scenario: Go to User Managment page
Exception: server exception

17. Use Case: Update User

26
 Primary Actors: Admin
Secondary Actor: System
Status: developed
Goals in Context: Update User
Pre-Condition:
• System has an updated browser and working internet connection
• User must login first

Post-Condition: User Updated

Scenario: Go to User Management page
Exception: server exception

18. Use Case: View User

Primary Actors: Admin

Secondary Actor: System
Status: developed
Goals in Context: View User
Pre-Condition:
• System has an updated browser and working internet connection
• User must login first

Post-Condition: User Viewed

Scenario: Go to User Management page
Exception: server exception

19. Use Case: Allow Access to User

Primary Actors: Admin

Secondary Actor: System
Status: developed
Goals in Context: Allow Access to User
Pre-Condition:
• System has an updated browser and working internet connection
• User must login first

Post-Condition: Accessed Allowed to user

Scenario: Go to User Management page

27
 Exception: server exception

Ranking Management
20. Use Case: Assign Ranking

Primary Actors: Admin

Secondary Actor: System
Status: developed
Goals in Context: Assign Ranking
Pre-Condition:
• System has an updated browser and working internet connection
• User must login first

Post-Condition: Ranking Assigned to User

Scenario: Go to Ranking page
Exception: server exception

21. Use Case: Add Ranking

Primary Actors: Admin
Secondary Actor: System
Status: developed
Goals in Context: Add Ranking
Pre-Condition:
• System has an updated browser and working internet connection
• User must login first

Post-Condition: Ranking Added

Scenario: Go to Ranking page
Exception: server exception
22. Use Case: Update Ranking
Primary Actors: Admin
Secondary Actor: System
Status: developed
Goals in Context: Update Ranking
Pre-Condition:
• System has an updated browser and working internet connection
• User must login first

Post-Condition: Ranking Updated

28
 Scenario: Go to Ranking page
Exception: server exception

23. Use Case: Delete Ranking

Primary Actors: Admin
Secondary Actor: System
Status: developed
Goals in Context: Delete Ranking
Pre-Condition:
• System has an updated browser and working internet connection
• User must login first

Post-Condition: Ranking Deleted

Scenario: Go to Ranking page
Exception: server exception

Packages:
24. Use Case: Assign packages

Primary Actors: Admin

Secondary Actor: System
Status: developed
Goals in Context: Assign packages
Pre-Condition:
• System has an updated browser and working internet connection
• User must login first

Post-Condition: packages assigned

Scenario: Go to Packages page
Exception: server exception

29
25. Use Case: Update Packages
Primary Actors: Admin
Secondary Actor: System
Status: developed
Goals in Context: Update Packages
Pre-Condition:
• System has an updated browser and working internet connection
• User must login first

Post-Condition: packages updated

Scenario: Go to Packages page
Exception: server exception

Masking
26. Use Case: Add Masking

Primary Actors: Admin

Secondary Actor: System
Status: developed
Goals in Context: Add Masking
Pre-Condition:
• System has an updated browser and working internet connection
• User must login first

Post-Condition: Masking Added

Scenario: Go to Masking page
Exception: server exception

27. Use Case: Update Masking

Primary Actors: Admin
Secondary Actor: System
Status: developed
Goals in Context: Update Masking
Pre-Condition:
• System has an updated browser and working internet connection
• User must login first

30
 Post-Condition: Masking updated
Scenario: Go to Masking page
Exception: server exception

28. Use Case: Delete Masking

Primary Actors: Admin

Secondary Actor: System
Status: developed
Goals in Context: Delete Masking
Pre-Condition:
• System has an updated browser and working internet connection
• User must login first

Post-Condition: Masking deleted

Scenario: Go to Masking page
Exception: server exception

29. Use Case: View Masking

Primary Actors: Admin

Secondary Actor: System
Status: developed
Goals in Context: View Masking
Pre-Condition:
• System has an updated browser and working internet connection
• User must login first

Post-Condition: Masking Viewed

Scenario: Go to Masking page
Exception: server exception

31
Chapter 4:
System Design
This chapter explains about the system design and architecture of WFM portal. UML diagrams including class diagram, architecture
diagram, entity relationship diagram, component diagram, sequence diagram etc. are used to provide insight on software design.

4.1. Architecture Diagram

Fig . 4.1.1

32
4.2. Entity Relationship Diagram with data dictionary

Fig . 4.2.1

33
Data Dictionary
1: Campaign Detail

Table . 4.2.1

2: Contacts

Table . 4.2.2

34
3: Account Maincode

Table 4.2.3

4: Applications

Table . 4.2.4

35
5: Groups

Table . 4.2.5

6: Masking

Table . 4.2.6

36
7: Master Campaign

Table . 4.2.7

8: Menu

Table . 4.2.8

37
9: Page

Table . 4.2.9

10: User Access

Table . 4.2.10

38
11: Template

Table . 4.2.11

12: User Log

Table . 4.2.12

39
13: Users

Table . 4.2.13

40
14: User Log

Table . 4.2.14

41
15: User Access Template

Table . 4.2.15

42
16: Users Template type

Table . 4.2.16

17: User Login Rights

Table . 4.2.17

18: User Log

Table . 4.2.18

43
4.3 Data Flow Diagram

Fig . 4.3.1

44
4.4 Class Diagram

Fig . 4.4.1

45
4.5 Object Diagram

Fig . 4.5.1

46
4.6 Sequence Diagram

Fig . 4.6.1

47
4.7 Activity Diagram

Fig . 4.7.1

48
4.8 State Transition Diagram

Fig . 4.8.1

49
Chapter No 5: Implementation
5.1 Component Diagram

Fig . 5.1.1

50
5.2 Deployment Diagram

Fig . 5.2

51
Chapter No 6:

Testing (Software Quality Attributes)

6.1 Test Case Specification

This Chapter provides details about testing and evaluation. Major areas of testing are use case testing, equivalence
partitioning, boundary value analysis, data flow testing, unit testing, integration testing, performance testing, and stress
testing.

6.1. Use Case Testing

6.1. Use Case Testing

TEST CASE(S) Steps Expected Results
Test Case: Login-1
System will display message of successful Login and
1) Fill all the fields and submit data
divert the user towards the dashboard page.
Test Case: Login-2 -
System will display a message containing errors
1) User skip some fields and submit data
summary.
Test Case: Login-3 -
User choose the username which already has been System will display the message to change the
1)
taken and not available for the current user. username.
Test Case: Login-4 – Short length password -
User put the password containing characters less than System will display message that password shall be 4 to
1)
4 or greater than 8. 8 characters.

Table 6.1.1 Use Case Test

TEST CASE(S) Steps Expected Results
Test Case: Admin-Add Masking -

1) Add Masking Name It will Tell Name Added Successfully

Test Case: Admin- Remove Masking -

1) Remove Masking It will give an alert message and ask for confirmation.

52
Test Case: Update Masking -

1) admin will Update Masking Admin will update the masking and give an alert message

Table 6.1.2 Use Case Test

TEST CASE(S) Steps Expected Results

Test Case: Admin: Create Groups -
1) Add Groups Groups will be added Successfully and verify if it is not empty
Test Case: Admin Delete Groups -
1) Delete Groups Page will give an alert message and remove the group

Test Case: Admin: Update Group -

1) Update Group Update Group and will give an Alert if data is updated or not

Table 6.1.3 Use Case Test

TEST CASE(S) Steps Expected Results

Test Case: Add User Management -
System will display message of success and reset
1) Fill all the fields and submit data
the form.
Test Case: Admin: Allow Access -
User will allow access and give Access to
1) Allow Access to user end and give an alert
user
Test Case: Admin: Update user -
Admin can update user and give access
1) Update user and give an alert to user
to user

Table 6.1.4 Use Case Test

TEST CASE(S) Steps Expected Results

Test Case: Add Contact Numbers -
System will display message of success and save
1) Upload Excel sheet and add contact numbers
changes.
Test Case: Remove Contact Numbers -
Remove Excel Sheet which will remove the contact System will display a message containing errors
1)
numbers summary.

53
 Table 6.1.5 Use Case Test

TEST CASE(S) Steps Expected Results

Test Case: Admin: Create Campaigns -
System will display a success message and update attendance of
1) Click on campaign and add new Campaigns
user.
System will display a success message and update attendance of
2) Select the Campaign you want to select.
user.
Test Case: Admin: Remove Campaigns -
Click on the Campaigns to remove the System will not display a success message. An error in logged in
1)
function console.

Table 6.1.6 Use Case Test

TEST CASE(S) Steps Expected Results

Test Case: Create Ranking -
System will display a success message and save the leave
1) Create Ranking and Check it
application.

Click approve button for individual Leave System will display a success message, update the status of
2)
Application to accept the leave application leave application as approved, and update attendance of user.

System will display a success message, update the status of

Click reject button for individual Leave
3) leave application as rejected, and will not update attendance of
Application to reject the leave application
user.

Test Case: Leave Application1 – Unusual Workflow -

Applying leave without entering note or
1) System will display error summary.
selecting leave type or selecting date
Click approve button for individual Leave
2) System will not update and logs an error.
Application to accept the leave application

Click reject button for individual Leave

3) System will not update and logs an error.
Application to reject the leave application
T ABLE 6.1.7 USE CASE TEST

TEST CASE(S) Steps Expected Results

Test Case: Roster1 – Normal Workflow -
Create monthly roster, add skills, add users, add off days, select System will display a success message and
1)
month and year and save. save the roster.
Test Case: Roster1 – Unusual Workflow -

54
6.2. Boundary value analysis
Test Scenario Description Expected Outcome
Password length = 1 System should not accept

Password length = 2 System should not accept

Password length = 3 System should not accept

Password length = 4 System should not accept

Password length = 5 System should not accept

Password length = 6 System should not accept

Password length = 7 System should not accept

Password length = 8 System should not accept

Password length = 9 System should not accept

Password length = 10 System should accept

Password length = 11 System should not accept

Password length = 12 System should not accept

Password length = 13 System should not accept

Figure 6.2 Boundary Value Analysis

6.3. Unit testing

Test type Unit testing

Test case number 1

Test case name Add Contact Number

Test case description Admin will enter contact number and see data is loaded

Item to be tested Need to check if data is loaded or not.

Figure 6.3.1 Unit Testing

55
Test type Unit testing

Test case number 2

Test case name Login

Test case description User enter Password length and Check password length

Item to be tested Need to check if its displays the error message of password length

Figure 6.3.2 Unit Testing

Test type Unit testing

Test case number 3

Test case name Create Template

Test case description Admin can create template and see the template

Item to be tested It needs to check if the template is created or not

Figure 6.3.3 Unit Testing

56
Test type Unit testing
Test case number 4
Test case name Create groups.

Test case description Create Groups and need to check

Item to be tested Needs to check if group is created or not

Figure 6.3.4 Unit Testing

Test type Unit testing

Test case number 5

Test case name Create Ranking

Test case description Needs to create Ranking and Check

Item to be tested Needs to check if ranking is created or not

Figure 6.3.5 Unit Testing

57
Test type Unit testing

Test case number 6

Test case name Create Campaigns

Test case description Campaigns Created

Item to be tested Needs to create and check if campaigns is created.

Figure 6.3.6 Unit Testing

58
 Chapter 7 :
WBS Project Management

Fig . 7.1

Model 1 Model 2 Model 3

Mohammad Zouraiz Butt Usama Bin Afzal Raza Abbas

M.Zouraiz Butt Usama Bin Afzal Raza Abbas

59
7.2 Application Interface:

1: Dashboard:

Fig . 7.2.1

60
2: Change Password:

Fig . 7.2.2

3: Report:

Fig . 7.2.3

61
4: Report Detail:

Fig . 7.2.4
5: Group:

Fig . 7.2.5

62
6: Contact:

Fig . 7.2.6

7: Add New Contact:

63
8: Upload Excel Sheet

Fig . 7.2.8

64
9: View Excel Sheet

Fig . 7.2.9

10: Delete Contact :

Fig . 7.2.10

65
11: Template:

Fig . 7.2.11

12: New Template :

Fig . 7.2.12

66
13: Delete Template:

Fig . 7.2.13

14: Masking:

Fig . 7.2.14

67
15: New Masking:

Fig . 7.2.15

16:Campaign:

68
17: Ranking

Fig . 7.2.17

18: Users:

Fig . 7.2.18

69
19: User List:

Fig . 7.2.19

70
20: User Release

Fig . 7.2.20

21.User Creation:

Fig . 7.2.21

71
Chapter 8:
Tools & Technologies

8.1 Programming Languages

• ASP.NET,
• C#, HTML,
• CSS 3,
• JavaScript,
• J query

8.2 Databases/Data storages

• MS SQL Server

7.4 Operating Environment:

Hardware Requirements For Present Project:

• Processor : Intel core i3

• RAM : 2GB
• Hard disk : 500GB ( Minimum 80GB)

72