CHAPTER 1

Gathering & Analyzing Information

Chapter No. 1

Gathering and Analyzing Information

1.1 Introduction
In todays modern, sophisticated and fast world, online classified Ads become a medium
of communication among the internet users. On one end it is informative and on the other
end it is convenient and cost effective. Online classifieds are most effective and proved
market winner in current vast competitive business era. No one can ignore such a
powerful medium in totally changed market environment.
Online Classified Portal is available to serve as your online marketplace, which gives
following benefits:

Online Classifieds offer simple solutions to your classified advertising

needs.
Promote your product, company or service to a vast audience.
Build consideration, awareness, and buyer response.
Customize ads to fit individual or company needs.
Convenient and easy to use.

Online classified portal site provides different categorized classifieds/ads. It also allow
user to upload their ads.
Online classified portal allows two types of registration:
1.

User registration
User can get own account id to interact with advertiser.

2. Advertiser registration
3.

User can register themselves as advertiser who can upload ads

There are four major section of online classified portal.

Guest section

User section

Advertiser section

Admin section

Guest section
2

Chapter No. 1

Gathering and Analyzing Information

Guest can perform the following actions:

In this section, guest user can view categorized classifieds/ads.

Register themselves as a user or advertiser.

Guest user can search a particular classifieds.

Guest user can view company information, contact detail and can also
give suggestion/feedback about site or classifieds.

User Section
User can perform the following actions:

In this section, user can view categorized classifieds/ads and also

able to save the particular ads.

User can send a query request for particular classified/ad and get
response from advertiser for that query.

User can also search particular classifieds/ads.

User can also update their personal profile and password.

User can also give a feedback for the site or classified.

Advertiser Section
Advertiser can perform the following actions:

In this section advertiser can purchase scheme to upload their

classifieds/ads.

Advertiser can upload and manage different classifieds in particular

scheme.

Advertiser can receive query from user and able to give response
too.

Advertiser also able to view his/her scheme ledger that contains

information like:

How many schemes are there

How many classifieds/ads are uploaded in particular scheme

Scheme status (i.e. running, expired or inactive) and sufficient

balance, etc.

Chapter No. 1

Gathering and Analyzing Information

Admin Section
Admin can perform the following actions:

Admin can manage different database entries.

Admin can view the information related registered users, advertisers

with their scheme details and their feedback.

Admin can also upload/update ads.

Admin can approve scheme activation and ad activation request of

the advertiser.

1.2 Purpose
The main purpose of this system is:

The system has maintained new innovative technologies to provide

good information to the user

This web application provides facility to user to search and to

advertiser to advertise in reliant category

It saves time as it allows number of users and advertisers to do their

work.

Administrator has privileges such as creating new users and

granting roles to those newly created users.

1.3 Scope
For the current website of Dynamic Micro link Pvt. Ltd. that we have under taken, the
corresponding scope of our website is as follow:
Context
Guest Site
Our website allows the Guest:

Our website enables the Guest user to register themselves as user or

advertiser.

Guest user can see the categorized classifieds/ads uploaded by

advertiser and also search particular classified.

Chapter No. 1

Gathering and Analyzing Information

User Site
Our website allows the User:

User can see the categorized classified/ads and also search particular
classified.

User can send a query to advertiser for particular classified and get
response for that query.

User can save particular ads.

User can update personal detail

Advertiser Site
Our website allows the Advertiser:

Advertiser can purchase scheme to upload classifieds/ads.

To upload classified, advertiser has to select particular scheme that

have sufficient balance and has to define display format for that
classified.

Advertiser

can

receive

query

from

user

for

particular

classifieds/ads and give the response.

Advertiser can view scheme ledger that contain current status of

scheme

and Classifieds/ads upload in different scheme.

Advertiser can get remainder related scheme status i.e. scheme

expiry and Point expiry.

Advertiser can update their personal detail

Advertiser can search particular classifieds/ads.

Admin Site
Our website allows the Admin:

Admin can manage the different databases.

Admin can also upload and mange classifieds behalf of advertiser.

Admin can approve scheme activation and ad activation request of

the advertiser.

Admin can view the details of user, advertiser and their scheme
detail and feedback detail.
5

Chapter No. 1

Gathering and Analyzing Information

Admin can search particular classifieds/ads.

1.4 Definitions, Acronyms and Abbreviations

While making the Online Classified Ads no special acronyms and abbreviations can be
used.
1.5 Use cases and usage scenarios
The Unified Modeling Language (UML) is a standard language for specifying,
visualizing, constructing, and documenting the articles of software systems, as well as for
business modeling and other non-software systems. The UML represents a collection of
best engineering practices that have proven successful in the modeling of large and
complex systems. The UML is very important part of developing object oriented software
and the software development process. The UML uses mostly graphical notations to
express the design of software projects. Using the UML helps project team communicate,
explore potential designs, and validate the architectural design of the software.
Goals of Unified Modeling Language (UML)
The primary goals in the design of UML were:

Provide users with a ready-to-use, expressive visual modeling

language so they can develop and exchange meaningful models.

Provide extensibility and specialization mechanisms to extend the

core concepts.

Be independent of particular programming languages

and

development processes.

Provide a formal basis of understanding the modeling language

Encourage the growth OO tools market.

Support higher-level development concepts such as collaborations,

frameworks, patterns and components.

Integrate best practices.

Chapter No. 1

Gathering and Analyzing Information

Why Use UML?

As the strategic value of software increases for many companies, the industry looks for
techniques to automate the production of software and to improve quality and reduce cost
and

time-to-market.

These

techniques

include

component

technology,

visual

programming, patterns and frameworks. Business also seeks techniques to manage the
complexity of systems as they increase in scope and scale. In particular they recognize the
need to solve recruiting architectural problems, such as physical distribution,
concurrency, replication, security, load balancing and fault tolerance. Additionally, the
development for the World Wide Web, while making some things simpler, has
exacerbated these architectural problems. The Unified Modeling Language (UML) was
designed to respond to these needs.
Each UML diagram is designed to let developers and customers view a software system
from a different perspective and in varying degrees and abstraction. UML diagrams
commonly created in visual modeling tools include
Here is now use case diagram for the Online Classified Ads which can represents Admin
and Customer.

Chapter No. 1

Gathering and Analyzing Information

1.5.1 Use Case Diagram

Guest User Diagram
Guest user performs the tasks that are depicted in the following ovals.

Chapter No. 1

Gathering and Analyzing Information

Fig 1.1 Guest User use case diagram

Customer Diagram
Customer user performs the tasks that are depicted in the following ovals.

Fig 1.2 Customer use case diagram

9

Chapter No. 1

Gathering and Analyzing Information

Administrator Diagram
Administrator user performs the tasks that are depicted in the following ovals.

Fig 1.3 Administrator use case diagram

10

Chapter No. 1

1.5.2

Gathering and Analyzing Information

Usage Scenarios

It is easy to mix up the definitions of use case and use case scenario. A use case
represents the actions that are required to enable or abandon a goal. A use case has
multiple paths that can be taken by any user at any one time. A use case scenario is a
single path through the use case. This article provides an example use case and some
diagrams to help visualize the concept.
A usage scenario, or scenario for short, describes a real world example of how one or
more people or organizations interact with a system. They describe the steps, events,
and/or actions which occur during the interaction.
Here are some usage scenarios with UML activity diagrams which can show the process
flow of Online Classified Ads.
Usage Scenario for Searcher
Sr. No
1
2
3
4
5
6
7
8

Actor
User
Customer

Administrator

Use
case ID
UC_01
UC_02
UC_03
UC_04
UC_05
UC_06
UC_07
UC_08

Use case name

View Product information
Register
Login
Make Account
View products
Add, delete and view customers and users
Add, delete and view products
Login

11

Chapter No. 1

Gathering and Analyzing Information

Use case ID
Use case Name
Primary actor
Stakeholder

UC-01
View product information
User
User wants to view products information in fast and easy way.

requirement
Pre-condition
Post condition
Main Success

User should be authorized and authenticated.

System display the complete information of all products
User wants to view the complete information of products. He

Scenarios

enter name, user name password and phone number to login

Alternative success

and view products.

If user does not enter name, user name, password and phone

scenarios

number for login then system display the message Please filled
the blank fields. User select the appropriate values and system
display the product details.

Table 1.1 Use cases 1

Use case ID
Use case Name
Primary actor
Stakeholder

UC-02
Register
Customer
User wants to register himself in fast and efficient way.

requirement
Pre-condition
Post condition
Main Success

Customer should be authorized and authenticated.

System will display the registration page
User wants to register him for this website. He enter name, last

Scenarios

name, user name, password, city, country, address and phone

Alternative success

number for registration.

If user does not enter name, last name, user name, password,

scenarios

city, country, address and phone number for registration. Then

system display the message Please filled the blank fields.
Customer then filled the appropriate values. System register
him/ her successfully.
12

Chapter No. 1

Gathering and Analyzing Information

Table 1.2 Use cases 2

Use case ID
Use case Name
Primary actor
Stakeholder

UC-03
login
Customer
Customer wants to login on website.

requirement
Pre-condition
Post condition
Main Success

Customer should be authorized and authenticated.

System will display the login page.
Customer wants to login. He enters name, user name and

Scenarios
Alternative success

password to login and view products.

If user does not enter name, user name and password for login

scenarios

then system display the message Please filled the blank fields.
Customer filled the blank fields. System login him/ her.

Table 1.3 Use Case 3

Use case ID
Use case Name
Primary actor
Stakeholder

UC-04
Make account
Customer
User wants to make account in fast and efficient way.

requirement
Pre-condition
Post condition
Main Success

Customer should be authorized and authenticated.

System displays the sign up form for new customers.
User wants to make the account. He enters name, user name,

Scenarios

password, city, country, date of birth and phone number to make

Alternative success

account.
If user does not enter name, user name, password, city, country,

scenarios

date of birth and phone number for making account. Then system
display the message Please filled the blank fields. User then
selects the appropriate values and system will maintain his
account.

Table 1.4 Use cases 4

Use case ID
Use case Name
Primary actor
Stakeholder

UC-05
View product
Customer
Customer wants to view products in fast and easy way.
13

Chapter No. 1

Gathering and Analyzing Information

requirement
Pre-condition
Post condition
Main Success

Customer should be authorized and authenticated.

System will display the products with description.
User wants to view products. He enters name, user name, and

Scenarios
Alternative success

password and phone number to login and view products.

If user does not enter name, user name, password and phone

scenarios

number for login then system display the message Please filled
the blank fields. User then selects the appropriate values.
System then display products.

Table 1.5 Use cases 5

Use case ID
Use case Name
Primary actor
Stakeholder

UC-06
Add, delete and view customers
Administrator
Administrator wants to view customers information in fast and

requirement
Pre-condition
Post condition
Main Success

easy way.
Administrator should be authorized and authenticated.
System display the complete information of all customers.
Administrator wants to view the complete information of

Scenarios

Customers. He enter user name password to login and view

Alternative success

Customers.
If administrator does not enter user name, password for login

scenarios

then system display the message Please filled the blank fields.
User filled the appropriate values and system display the
customers details.

Table 1.6 Use cases 6

Use case ID
Use case Name
Primary actor
Stakeholder

UC-7
Add, delete and view products
Administrator
Administrator wants to view products information in fast and

requirement
Pre-condition
Post condition
Main Success

easy way.
Administrator should be authorized and authenticated.
System will display the complete information of all products.
Administrator wants to view the complete information of

Scenarios

products. He enter user name, password to login and view

Alternative success

products.
If administrator does not enter user name, password for login
14

Chapter No. 1
scenarios

Gathering and Analyzing Information

then system display the message Please filled the blank fields.
User filled the appropriate values and system display the
products details.

Table 1.7 Use cases 7

Use case ID
Use case Name
Primary actor
Stakeholder

UC-8
Login
Administrator
Administrator wants to login himself in fast and easy way.

requirement
Pre-condition
Post condition
Main Success

Administrator should be authorized and authenticated.

System will display the login page.
Administrator wants to login. He enter user name, password to

Scenarios
Alternative success

login.
If administrator does not enter user name, password for login

scenarios

then system display the message Please filled the blank fields.
User filled the appropriate values and system display will login
him.

Table 1.8 Use cases 8

1.6 Supplementary Requirements

The supplementary requirements are part of software system specifications which covers
the non-functional requirements that the software system need to address.
For example the security features the system is suppose to cover, the auditing features
etc. There could be a long list based on the context of the system in scope like the
scalability, performance, no-of users supported etc.
1.6.1

Usability

The term usability in the context of creating software represents an approach that puts
the user, rather than the system, at the centre of the process. This philosophy, called usercentered design, incorporates user concerns and advocacy from the beginning of the
design process and dictates that the needs of the user should be foremost in any design
decisions.

15

Chapter No. 1

Gathering and Analyzing Information

In designing of this Online Classified Ads it is taken care that it can be easy to use no
more complex abilities.
1.6.2

Reliability

Software reliability is the probability of failure-free software operation for a specified

period of time in a specified environment. So it is also taken care while making online
classified Ads that it should be reliable that is why it is developed in most advanced
language c#.
1.6.3

Supportability

Supportability is also very important factor that a system which can design it can be
supportable in most of environment. On line advertising is a website which has not too
much supportability issues because it can run on sipper browser.
Hardware Requirements
There are Following Hardware Components:

2.8 GHz processor and Above

RAM 512MB and Above

HDD 20GB Hard Disk Space and Above

Software Requirements
There are Following Software Components:

WINDOWS OS (XP/VISTA/WIN7)

Visual Studio.Net2013 Professional Edition

Visual Studio.Net Framework(Minimal for Deployment)

SQL Server 2012 Express Edition

Microsoft c# & ASP.NET language

HTML, CSS

16