Online Advertismnet System (Ad Agency) Report

B.Sc.
IT(Semester VI)
INDEX
TOPIC NO. SUB TOPIC
1.1
1.2
1.3
Online Advertising Agency (2014-15)
1.4
2
2.1
2.2
[1
]
3.1
3.2
4.1
4.2
Annexure
Topic no
I.
II.
III.
[2]
]
[3
E
IS
PHAS
ANALYS
B.Sc.IT(Semester VI)
1.1- Requirement Gathering

1.1.1 Problem statement:
The Online Advertising Agency is to automate all operation. Generally it
includes the order processing, Reservation management and Schedule
management. before automating Reservation we have to understand
the concept of Online Advertising Agency. Of any operation we make a
system which do work automatically as the respective events occurs, for
which it is meant. These are best examples of the management system.
Here we are try to developed such type of system is provide the

automation on any type of Reservation. That means a Agency which
has the type system which provide the facility to the User of the reserve
for advertising in different media without any complexity.
For example any customer wants to register in listed newspaper from

the system than first of all customer choose the day from/to he/she can
see the more than one type of there and then he.
1.1.2 Fact Finding Technique:
Today, with great diversity of goods and services, competition, advertising

is becoming one of the most important existing and potential
buyers of persuasion measures.
Advertising helps the user to choose a product, encourages buyers to

perform some kind of action.
In the absence of advertising, we could not possibly know about many

of us necessary and useful goods or services.
1.1.3 Objective and scope of the project:
An advertising agency or ad agency is a service business

dedicated to creating, planning and handling Advertising (and
sometimes other forms of promotion for its clients.
An ad agency is independent from the client and provides an

outside point of view to the effort of selling the client's products or
services. An agency can also handle overall marketing and
branding strategies and Sales Promotion for its clients.
[4]
1.1.4 Problem with existing system:
If an agency does not communicate or relay its clients goals and

creative wishes properly problems can occur.
Most Full-Service Agencies work on a combination of fee-based and
commission based compensation.
The fee is paid by the entity for which the marketing is being done.
However an agency may have better negotiating powers than your
company and save you more money in the long run anyways.
There are far more advantages to having the right advertising agency
than not.
So there is no problem with existing system in our project.
1.1.5 Advantage of proposed system:
In order to avoid the above problem this project is to provide

advertisement details like advertisement cost in various

channels.
Depending upon the budget the various channels can allot different
advertisements.
Most Full-Service Agencies work on a combination of fee-based and
commission based compensation.
Enumerate potential proposed system.
Define and identify characteristics of proposed system.
Determine and evaluate performance and cost effective of each
proposed system.
1.2 Feasibility Study
Feasibility study is made to see if the project on completion will serve the
purpose of the organization for the amount of work, effort and the time
that spend on it.
Feasibility study lets the developer foresee the future of the project and
the usefulness.
A feasibility study of a system proposal is according to its workability, which is
the impact of the organization is proposed it normally goes through feasibility
study before it is approved for development.
The document provide the feasibility of the project that is begin designed
and lists various areas that were considered very carefully during the
feasibility
[5]
study of this project such as Technical, Economical and

Operational feasibilities.
In its simplest terms, the two criteria to judge feasibility are cost required
and value to be attained.
1.2.1 Operational feasibility:
In this project, the management will know the details of each project where he
may be presented and the data will be maintained as decentralized and if any
inquires for that particular contract can be known as per their requirements
and necessaries.
It is mainly related to human organizations and political aspects. The points to
be considered are:
What changes will be brought with the system?
What organization structures are disturbed?
What new skills will be required? Do the existing staff members have
these skills? If not, can they be trained in due course of time?
The system is operationally feasible as it very easy for the End users to
operate it. It only needs basic information about System platform.
1.2.2 Technical Feasibility:
A study of resource availability that may affect the ability to achieve an

acceptable system. This evaluation determines whether the technology
needed for the proposed system is available or not.
Can the work for the project be done with current equipment existing software
technology & available personal?
Can the system be upgraded if developed?
If new technology is needed then what can be developed?
This is concerned with specifying equipment and software that will
successfully satisfy the user requirement. The technical needs of the system
may include:
Front-end and back-end selection

An important issue for the development of a project is the selection of suitable
front-end and back-end. When we decided to develop the project we went
through an extensive study to determine the most suitable platform that suits
the needs of the organization as well as helps in development of the project.
The aspects of our study included the following factors.
[6
]
Front-end selection:
1. It must have a graphical user interface that assists employees that are not from IT
background.
2. Scalability and extensibility.
3. Flexibility.
4. Robustness.
5. According to the organization requirement and the culture.
6. Must provide excellent reporting features with good printing support.
7. Platform independent.
8. Easy to debug and maintain.
9. Event driven programming facility.
10. Front end must support some popular back end like Ms Access..
Back-end Selection:
1. Multiple user support.
2. Efficient data handling.
3. Provide inherent features for security.
4. Efficient data retrieval and maintenance.
5. Stored procedures.
6. Popularity.
7. Operating System compatible.

8. Easy to install.
9. Various drivers must be available.
10. Easy to implant with the Front-end.
According to above stated features we selected Ms-Access as the backend.
The technical feasibility is frequently the most difficult area encountered at this
stage. It is essential that the process of analysis and definition be conducted in
parallel with an assessment to technical feasibility. It centers on the existing
computer system (hardware, software etc.) and to what extent it can support the
proposed system. Hardware Requirements
Computer:-Window 7
RAM:-2GB
Monitor,CPU .
Software Requirements:
Linux (Apache), Windows (Apache/IIS)

MySQL 4.1 or later (v5 preferred)
PHP 4.3 or later (v5 preferred)
Xampp Server(For Window)
[7]
The following Xampp settings

- Apache-Start
- MySql-Start
1.2.3 Economical/Behavioral Feasibility:
Economic justification is generally the Bottom Line consideration for most systems.
Economic justification includes a broad range of concerns that includes cost
benefit analysis. In this we weight the cost and the benefits associated with the
candidate system and if it suits the basic purpose of the organization i.e. profit
making, the project is making to the analysis and design phase.
The financial and the economic questions during the preliminary investigation
are verified to estimate the following:
The cost to conduct a full system investigation.

The cost of hardware and software for the class of application being
considered.
The benefits in the form of reduced cost.
The proposed system will give the minute information, as a result the
performance is improved which in turn may be expected to provide increased
profits.
This feasibility checks whether the system can be developed with the
available funds.
The Online Advertising Agency does not require enormous amount of money
to be developed. This can be done economically if planned judicially, so it is
economically feasible. The cost of project depends upon the number of man-
hours required.
1.2.4 Cost benefit analysis:
The computerized system will help in automate the selection leading the
profits and details of the organization.
With this software, the machine and manpower utilization are expected
to go up by 80-90% approximately.
The costs incurred of not creating the system are set to be great,
because precious time can be wanted by manually.
Weight system performance and cost data.
Select the best-proposed system.
1.3 Requirement Specification

1.3.1 Functional Requirement:
[8]
Login form:-The Online Advertisement agency also comes with the customer
registration details page, where the customer can enter his detail and register.
He can also create id and password.
Available Various forms: - The system allows the user or member to

choose various media types for advertising as a different channel.
Add station/channel/location form:- The Admin rights to add station/channel and

location.
Logout: - After clicking the logout user exit from the system
1.3.2 Technical Requirement:
Hardware Requirements:
Computer:-Window 7
RAM:-2GB
Monitor, CPU.
Software Requirements:
Xampp Server(For Window)

The following Xampp settings
- Apache-Start
- MySql-Start
1.3.3 Software Requirement Specification:
Aim:-Creation of website on Online Advertising Agency.
Introduction:-
The main aim of this project is to provide advertisement details like

advertisement cost in various channels.
Depending upon the budget the various channels can allot different
advertisements.
The Online Advertising Agency is to automate all operation . generally it
includes the order processing, Reservation management and
Schedule management.
Before automating Reservation we have to understand the
concept of Online Advertising Agency.
Of any operation we make a system which do work automatically as the
respective events occurs, for which it is meant.
These are best examples of the management system.
[9]
Here we are try to developed such type of system is provide the

automation on any type of Reservation.
That means a Agency which has the type system which provide the
facility to the User of the reserve for advertising in different media
without any complexity.
For example any customer wants to register in listed newspaper from the
system than first of all customer choose the day from/to he/she can
see the more than one type of there and then he.
Overall description: - The newly developed system will be invoked mainly when:
The detail of available test provided to a client.
The client who want to choose available media.
It also provides the admin to modify employee detailed or to add new
employee.
System own information storage:- .

Client detail file.
Available media detail file.
Download uploaded file.
Major transactions to be provided by the system are:-

Customer view profile.
Customer choose available media .
The main function of system:-

Provide user interface.
Verify use identities and access rights.
Do error checking on all inputs.
Project constraints:-
Compatibility: - The website should run compatibly in browser. It should
allow registering new users and giving them access rights registered by
their duties.
Reliability and availability:-The factor needed to establish the software
expected reliability is the user input should be within given range.
Normal termination of the program. Backup should spot tested to ensure
they are reliable.
Security: - It must be insured that access will be provided to the
authorized person through user ID and password. Network security will be
provided by the use of firewall.
Methodology adopted:-
The methodology that used in my proposed system is waterfall model .The for
selecting this model is very simple to understand and use.
The reason for selecting this model is given below
[10]
The advantage of waterfall development is that it allows for

departmentalization and control.
A schedule can be set with deadlines for each stage of development and a
product can proceed through the development process model phases one
by one.
Development moves from concept, through design, implementation, testing,
installation, troubleshooting, and ends up at operation and maintenance.
Each phase of development proceeds in strict order.
1.4 Tools And Technologies

The organizations in which all the works are done manually. During the study
of existing system following Points are observed.
As the current system is totally manual.
Due to manually process is requires more time for completion of any
work
Existing system is manual. So it increases the chances of errors.
Lot of time consumed for each report generation.
More man Power is require and timely updating complicated.
Immediate responses to the queries are difficult and time consuming.
Software and Hardware Requirement:
HARDWARE REQUIREMENT FOR DEVLOPEMENT:-

-> 256 MB of RAM
-> Pentium 4(2.40 GHz) processor
-> 40 GB HDD
SOFTWARE REQUIREMENT FOR DEVLOPEMENT:-
o Linux (Apache), Windows (Apache/IIS)
o MySQL 4.1 or later (v5 preferred)
o PHP 4.3 or later (v5 preferred)
o Xampp Server(For Window)
o The following Xampp settings
- Apache-Start
- MySql-Start
-> Platform support:
(i)Microsoft Windows XP or
(ii)Microsoft Windows Vista or
(iii)Microsoft Windows 7
HARDWARE REQUIREMENT FOR CLIENTSIDE:-
-> 256 MB of RAM
-> Pentium 3(2.40 GHz) processor
-> 40 GB HDD
SOFTWARE REQUIREMENT FOR CLIENTSIDE:-
[1
1]

-> Platform support:

(i)Microsoft Windows XP or Vista or 7
Modules:
The different types of modules of this site are as follows:
Reservation modules:
This modules gives a reservation from to the registration. In this module
which ever user wants to reserve seat from this site.
Modules after reservation by user:
o Personal information
In this module, personal information is arranged in a place and user can

access the information .

In the search box, in the case we put the information of the personal
related to the particular organization and any one can retrieve the
information from this module, just like the various offices web site.
Modules after login by administrator:
o Administrator:
Administrator controls all the details of the project. In other words it
controls over all working of the project.
o Personal information:
These modules store the personal information of the person and
facilitate the user that he can access the details. In this module entry
editing and deletion of the new and old details can be done be only by
the admin.
o Security module:
This module handles the security of software. it checks for unauthorized
login/accesses ,unauthorized deletion/editing , defining the access
permissions to users, etc.
o Reporting modules:
This modules handles the process of all types of reports generation. By
this module the user/admin can got the print of the user desired queries
like for personal information, cricket, tourism, movies and books.
[1
2]
These reports are very beneficial for both user and the admin.
Documentations
a) Microsoft Word Professional Plus 2013:-
Microsoft Word is word processor tool developed by Microsoft.

Among its features, Word includes a built-in spell checker, a thesaurus, a dictionary,
and utilities for manipulating and editing text. The following are some aspects of its
feature set.
Word can import and display images in common bitmap formats such as JPG and
GIF. It can also be used to create and display simple line-art. No version of Microsoft
Word has support for the common SVG vector image format.
Chart and Diagram:-
Key Features
Feature
Accurate UML
standard model
Open software model format
True MDA Support
Applicability of methodologies and platforms
Excellent
extensibility
Software model verification Function
Useful Add-Ins
The following are the minimum system requirements for running Star UML(tm).
In te l(R ) P e n tiu m (R ) 2 3 3 MHz o r h ig h e r.
W in d o ws (R ) 2 0 0 0 , W in d o ws XP , o r h ig h e r
1 2 8 MB R AM (2 5 6 MB re c o m m e n d e d )
1 1 0 MB ha rd d is c s p a c e (1 5 0 MB s p a c e re c o m m e n d e d )
S VGA o r h ig h e r re s o lu tio n m o n ito r (1 0 2 4 x7 6 8 re c o m m e n d e d )
Mo u s e o r o th e r p o in tin g device
PHASE
DESIGN
2.1 Detailed life Cycle of Project (logical design):
Design is the first step in the development phase for any techniques
and principles for the purpose of defining a device, a process or system
in sufficient detail to permit its physical realization.
The basic idea of the system development life cycle is that there is a well-
defined process by which an application is conceived and developed
and implemented.
The life cycle gives structure to a creative process.
2.1.1 Class Diagram:
A class diagram is a diagram showing a collection of classes and interfaces,

along with the collaborations and relationships among classes and interfaces.
A class diagram is a pictorial representation of the detailed system design. Design

experts who understand the rules of modeling and designing systems design the
system's class diagrams. A thing to remember is that a class diagram is a static
view of a system. The structure of a system is represented using class diagrams..
UML provides a class notation to represent classes in class diagram. The

class notation has three components:
The first compartments depict the name of the class.
The second compartments depicts the attributes of the class
The third compartments depicts the operations of the class
Representing Relationships in class diagram
In UML relationships model the way in which the elements of a software

system connect to each other, either logically or physical .The various types
of relationships among the classes and objects
Association: When two classes are connected to each other in any way, an
association relation is established
Dependency: When a class is formed as a collection of other classes, it
is called an aggregation relationship between these classes.
Generalization: Also called an "is a" relationship, because the child class is
a type of the parent class. Generalization is the basic type of relationship
used to define reusable elements in the class diagram. Literally, the child
classes "inherit" the common functionality defined in the parent class
Realization: In a realization relationship, one entity (normally an interface) defines

a set of functionalities as a contract and the other entity (normally a class)
"realizes"
the contract by implementing the functionality defined in the contract
[16]
Basic Class Diagram Symbols and Notations

Classes represent an abstraction of entities with common
characteristics. Associations represent the relationships between
classes.
Illustrate classes with rectangles divided into compartments. Place the name of the
class in the first partition (centered, bolded, and capitalized), list the attributes in
the second partition, and write operations into the third.
Active Class
Active classes initiate and control the flow of activity, while passive classes
store data and serve other classes. Illustrate active classes with a thicker
border.
Visibility
Use visibility markers to signify who can access the information contained within
a class. Private visibility hides information from anything outside the class
partition. Public visibility allows all other classes to view the marked information.
Protected
visibility allows child classes to access information they inherited from a parent class
Association
Associations represent static relationships between classes. Place association

names above, on, or below the association line. Use a filled arrow to indicate
the direction of the relationship. Place roles near the end of an association.
Roles represent the way the two classes see each other.
Note: It's uncommon to name both the association and the class roles.
Multiplicity (Cardinality)
[17]
Pla city notations near the ends of an association. These symbols indicate the number
ce of instances of one class linked to one instance of the other class. For example,
mul one company will have one or more employees, but each employee works for one
tipli company only.
Place constraints inside curly braces {}.
Simple Cons
Composition and Aggregation

Composition is a special type of aggregation that denotes a strong ownership
between Class A, the whole, and Class B, its part. Illustrate composition with a filled
diamond. Use a hollow diamond to represent a simple aggregation relationship, in
which the "whole" class plays a more important role than the "part" class, but the
two classes are not dependent on each other. The diamond end in both a
composition
and aggregation relationship points toward the "whole" class or the aggregate.
[18]
Generalization
Generalization is another name for inheritance or an "is a" relationship. It refers to
a relationship between two classes where one class is a specialized version of
another. For example, Honda is a type of car. So the class Honda would have a
generalization relationship with the class car.
In real life coding examples, the difference between inheritance and aggregation
can be confusing. If you have an aggregation relationship, the aggregate (the whole)
can access only the PUBLIC functions of the part class. On the other hand,
inheritance allows the inheriting class to access both the PUBLIC and PROTECTED
functions of the super class.
Fig: Class Diagram

[1
9]
2.1.2 E-R Diagram:
Data models are tools used in analysis to describe the data requirement and
assumptions in the system from a top-down perspective. They also set the stage for
design of databases later on in the SDLC.
There are three basic elements in ER model:
Entities are the things about which we seek
information. Attributes are the data we collect about the
entities.
Relationships provide the structure needed to draw information from multiple entities.
Entity: It represents a collection of objects o things in the real world whose

individual members or instances have the following characteristics:
Each can be identified uniquely in some fashion.

Each plays a necessary role in the system we are
building. Each can be described by one or more data
elements.
Attributes: They express the properties of entities. Attributes having unique

values are called candidate keys (Primary key).
Relationships: They describe the association between entities. They

are characterized by cardinality as follows:
A. One-to-One relationship means an instance of the first entity is

associated with only one instance of second entity.
B. One-to-Many relationship means that one instance of the first entity is

related to many instance of second entity, while an instance of second entity
is associated with only instance of the first entity
C. Many-to-Many means that an instance of the first entity is related to many

instances of the second entity and the same is true in the reverse
direction
also.
Entity Relationship Diagram Notations

An entity is an about object or concept which you want to store information.
[20]
Weak Entity
A weak entity is an entity that must defined by a foreign key relationship with
another entity as it cannot be uniquely identified by its own attributes alone.
Key attribute
A key attribute is the unique, distinguishing characteristic of the entity. For
example, an employee's social security number might be the employee's key
attribute.
Multivalued attribute
A multivalued attribute can have more than one value. For example, an
employee entity can have multiple skill values.
Derived attribute
A derived attribute is based on another attribute. For example, an
employee's monthly salary is based on the employee's annual salary.
Relationships
Relationships illustrate how two entities share information in the database
structure. Learn how to draw relationships:
First, connect the two entities, then drop the relationship notation on the line.
Cardinality spnaecifies how many instances of an entity relate to one instance

of another entity?
Ordinarily is also closely linked to cardinality. While cardinality specifies the
occurrences of a relationship, ordinarily describes the relationship as either
mandatory or optional. In other words, cardinality specifies the maximum number
of
relationships and ordinarily specifies the absolute minimum number of relationships.
[21]
Recursive relationship
In some cases, entities can be self-linked. For example, employees can
supervise other employees.
Fig: E-R Diagram
[2
2]
2.1.3 Event table
An Event Table is a table that lists events in rows and key pieces of
information about each event in columns. An event table includes rows and
columns, representing events and their details respectively. Each row in
the event tables record information about that event. Each column in the
table represents a key piece of information about that event.
Trigger is an occurrence that tells the system that an event has occurred,
either the arrival of data needing processing or of a point in time.
Source is an external agent or actor that supplies data to the system.
Activity is a behavior that the system performs when an event occurs. Response is
an output, produced by the system that goes to a destination. Destination is an
external agent or actor that receives data from the system.
Event
Registratio n Page
Login Page
Media
Type page
Select
Radio
Form
ContactUs
Page
Update pages
Admin
Login
Admin
Radio
Page
Admin
Radio
Page
2.1.4 USE CASE DIAGRAM :
A use case diagram depicts the various operations that a system performs. It
contains use cases, actors, and their relationships. Use cases are the sequence of
actions that form a single unit of work for an actor. An actor represents a user who
is external to the system and interacts with the use case.
Elements of Use Case Diagram
A use case diagram depicts the various operations that a system performs. It
contains use cases, actors, and their relationships. Use cases are the sequence of
actions that form a single unit of work for an actor. An actor represents a user who
is external to the system and interacts with the use case.
Elements of Use Case Diagram
Actors
An actor portrays any entity (or entities) that perform certain roles in a given
system. The different roles the actor represents are the actual business roles of
users in a given system. An actor in a use case diagram interacts with a use case.
For example, for modeling a banking application, a customer entity represents an
actor in the application. Similarly, the person who provides service at the counter is
also an actor. But it is up to you to consider what actors make an impact on the
functionality that you want to model. If an entity does not affect a certain piece of
functionality that you are modeling, it makes no sense to represent it as an actor.
An actor is shown as a stick figure in a use case diagram depicted "outside" the
system boundary.
Use Cases
A use case in a use case diagram is a visual representation of distinct business

functionality in a system. The key term here is "distinct business functionality." To
choose a business process as a likely candidate for modeling as a use case, you
need to ensure that the business process is discrete in nature. As the first step in
identifying use cases, you should list the discrete business functions in your
problem statement. Each of these business functions can be classified as a
potential use case. Remember that identifying use cases is a discovery rather than
a creation. As business functionality becomes clearer, the underlying use cases
become more easily evident. A use case is shown as an ellipse in a use case
diagram.
System Boundary
A system boundary defines the scope of what a system will be. A system cannot
have infinite functionality. So, it follows that use cases also need to have
definitive limits defined. A system boundary of a use case diagram defines the
limits of the
system. The system boundary is shown as a rectangle spanning all the use cases
in the system.
Relationships: The following relationships can be established among use cases
Extends: Indicates that an existing use case is extended by additional behavior to

obtain another use case. The extend relationship exists among use cases when
the function of a use case, which is implemented in initial iterations, are enhanced
in successive iterations
Includes: Indicates that function of one use case is included in the function of
another. They include relationship exists among use cases when the function of
a
particular use case are required by another use case
Basic Use Case Diagram Symbols and Notations
System
Draw your system's boundaries using a rectangle that contains use cases.
Place actors outside the system's boundaries.
Use Case
Draw use cases using ovals. Label with ovals with verbs that represent the
system's functions.
Actors
Actors are the users of a system. When one system is the actor of another
system, label the actor system with the actor stereotype.
[25]
Relationships
Illustrate relationships between an actor and a use case with a simple line. For
relationships among use cases, use arrows labelled either "uses" or "extends."
A "uses" relationship indicates that one use case is needed by another in order
to perform a task. An "extends" relationship indicates alternative options under a
certain use case.
Learn how to draw relationships.
Fig: Use-Case Diagram
[26]
2.1.5 Interaction Diagram
2.1.5.1 Collaboration Diagram
A collaboration diagram describes interactions among objects in terms of

sequenced messages. Collaboration diagrams represent a combination of
information taken
from class, sequence, and use case diagrams describing both the static
structure and dynamic behavior of a system.
The second interaction diagram is collaboration diagram. It shows the object
organization as shown below. Here in collaboration diagram the method call
sequence is indicated by some numbering technique as shown below. The
number indicates how the methods are called one after another. We have taken
the same order management system to describe the collaboration diagram.
The method calls are similar to that of a sequence diagram. But the difference is
that the sequence diagram does not describe the object organization where as
the collaboration diagram shows the object organization.
Now to choose between these two diagrams the main emphasis is given on the type
of requirement. If the time sequence is important then sequence diagram is used
and if organization is required then collaboration diagram is used.
Basic Collaboration Diagram Symbols and Notations
Class roles
Class roles describe how objects behave. Use the UML object symbol to
illustrate class roles, but don't list object attributes.
Association roles
Association roles describe how an association will behave given a particular
situation. You can draw association roles using simple lines labeled with stereotypes.
Messages
Unlike sequence diagrams, collaboration diagrams do not have an explicit way to
denote time and instead number messages in order of execution. Sequence
numbering can become nested using the Dewey decimal system. For example,
nested messages under the first message are labelled 1.1, 1.2, 1.3, and so on.
The condition for a message is usually placed in square brackets immediately
following
[27]
the sequence number. Use a * after the sequence number to indicate a loop.
Fig: Collaboration Diagram
2.1.5.2 Sequence Diagram
Sequence diagram describe interactions among classes in terms of an

exchange of messages over time. A sequence diagram depicts the sequence of
action that occurs in a system. The invocation of methods in each object, and the
order in which the invocation occurs is captured in a sequence diagram. This makes
the sequence diagram a very useful tool to easily represent the dynamic behavior
of a system. A sequence diagram is two-dimensional in nature. On the horizontal
axis, it shows the life of the object that it represents, while on the vertical axis, it
shows the sequence of the creation or invocation of these objects.
Because it uses class name and object name references, the sequence
diagram is very useful in elaborating and detailing the dynamic design and the
sequence and origin of invocation of objects. Hence, the sequence diagram is one
of
the most widely used dynamic diagrams in UML.
Object: The primary element involved in a sequence diagram in an object-
an instance of a class. A sequence diagram consists of sequences of interaction
among
[2
8]
different objects over a period of time. An object is represented by a named

rectangle. The name to the left of the : is the object name and to its right is
the class name.
Message: The interaction between different objects in a sequence diagram is

represented as messages. A message is denoted by a directed arrow. Depending on
the type of message, the notation differs. In a sequence diagram, you can represent
simple messages, special messages to create or destroy objects, and message
responses.
Class roles: Class roles describe the way an object will behave in context. Use
the
UML object symbol to illustrate class roles, but dont list object attributes.
Activation: Activation boxes represent the time an object needs to complete a
risk.
Messages: Messages are arrows that represent communication between

objects. Use half-arrowed lines to represent asynchronous messages. Asynchronous
messages are sent from an object that will not wait for a response from the receiver
before continuing its tasks.
Lifelines: Lifelines are vertical dashed lines that indicate the objects presence over
time collaboration diagram represent interactions between objects as a series of
sequenced messages. Collaboration diagram describe both the static structure
and
the dynamic behavior of a system
Basic Sequence Diagram Symbols and Notations
Class roles
Class roles describe the way an object will behave in context. Use the UML
object symbol to illustrate class roles, but don't list object attributes
Activation
Activation boxes represent the time an object needs to complete a task.
[29]
Messages
Messages are arrows that represent communication between objects. Use half-
arrowed lines to represent asynchronous messages. Asynchronous messages
are sent from an object that will not wait for a response from the receiver before
continuing its tasks.
Lifelines
Lifelines are vertical dashed lines that indicate the object's presence over time.
[30]
Destroying Objects
Objects can be terminated early using an arrow labeled "<< destroy >>" that
points to an X.
Loops
A repetition or loop within a sequence diagram is depicted as a rectangle. Place
the condition for exiting the loop at the bottom left corner in square brackets [ ].
[31]
Fig:Sequance diagram
2.1.6 Activity Diagram
Activity diagrams illustrate the dynamic nature of a system by modeling the flow of
control from activity. An activity represents an operation on some class in the system
that results in a change in the state of the system. Typically, activity diagrams are
used to model workflow or business processes and internal operation.
Action States: Action states represent the no interruptible actions of objects. You
can draw an action state in Smart Draw using a rectangle with rounded corners.
Action Flow:Action flow arrows illustrate the relationships among action

states.
Object Flow: Object flow refers to the creation and modification of objects by
activities. An object flow arrow from an action to an object means that the action
creates or influences the object. An object flow arrow from an object to an action
indicates that the action state uses the object.
Initial State: A filled circle followed by an arrow represents the initial action
state.
Final State: An arrow pointing to a filled circle nested inside another circle
represents the final action state.
Branching: A diamond represents a decision with alternate paths. The outgoing

alternates should be labeled with a condition or guard expression. You can also
label
one of the paths else.
[32]
Synchronization: A synchronization bar helps illustrate parallel transitions.

Synchronization is also called for king and joining.
Swim lanes: Swim lanes group related activities into one column. Activity
diagrams provide another ability, to clarify which actor performs which activity.
Basic Activity Diagram Symbols and Notations
Action states
Action states represent the no interruptible actions of objects. You can draw
an action state in Smart Draw using a rectangle with rounded corners.
Action Flow
Action flow arrows illustrate the relationships among action states.
Object Flow
Object flow refers to the creation and modification of objects by activities. An
object flow arrow from an action to an object means that the action creates or
influences the object. An object flow arrow from an object to an action indicates
that the action state uses the object.
Initial State
A filled circle followed by an arrow represents the initial action state.
[33]
Final State
An arrow pointing to a filled circle nested inside another circle represents the
final action state.
Branching
A diamond represents a decision with alternate paths. The outgoing alternates
should be labelled with a condition or guard expression. You can also label one
of
the paths "else."
Synchronization
A synchronization bar helps illustrate parallel transitions. Synchronization is
also called for king and joining.
Swim lanes
Swim lanes group related activities into one column.
[34]
Online Advertising Agency (2014-15) B.Sc.IT(Semester VI)
Fig: Activity Diagram
[3
5]
2.1.7 State transition Diagram
In automata theory and sequential logic, a state transition table is a table

showing what state (or states in the case of a nondeterministic finite
automaton) a finitesemiautomaton or finite state machine will move to,
based on the current state and other inputs. A state table is essentially a
truth
table in which some of the inputs are the current state, and the outputs
include the next state, along with other outputs.
A state table is one of many ways to specify a state machine, other ways
being a state diagram, and a characteristic equation.
One-dimensional state tables

Also called characteristic tables, single-dimension state tables are much
more like truth tables than the two-dimensional versions. Inputs are usually
placed on the left, and separated from the outputs, which are on the right.
The
outputs will represent the next state of the machine. A simple example of a
state machine with two states and two combinational inputs follows:
A B Current State
0 0
0 0
0 1
0 1
1 0
1 0
Two-dimensional state tables

State transition tables are typically two-dimensional tables. There are two
common forms for arranging them.
The vertical (or horizontal) dimension indicates current states, the

horizontal (or vertical) dimension indicates events, and the cells
(row/column intersections) in the table contain the next state if an
event
happens (and possibly the action linked to this state transition).
State Transition Table
Events
State
(S: state, E: event, A: action, -: illegal transition)

The vertical (or horizontal) dimension indicates current states, the

horizontal (or vertical) dimension indicates next states, and the
row/column
intersections contain the event which will lead to a particular next state.
State Transition Table
next current
Sm
(S: state, E: event, A: action, -: impossible transition)
A state Transition diagram shows the behaviour of classes in response to
external stimuli. This diagram models the dynamic flow of control from state to
state within a system.
Basic State Transition Diagram Symbols and Notations
States
States represent situations during the life of an object. You can easily
illustrate a state in Smart Draw by using a rectangle with rounded corners.
Transition
A solid arrow represents the path between different states of an object. Label
the transition with the event that triggered it and the action that results from
it.
Initial State
A filled circle followed by an arrow represents the object's initial state.
Final State
An arrow pointing to a filled circle nested inside another circle represents
the object's final state.
Synchronization and Splitting of Control

A short heavy bar with two transitions entering it represents a
synchronization of control. A short heavy bar with two transitions leaving it
represents a splitting of control that creates multiple states.
Elements of a state diagram:
Initial state:
This shows the starting point or first activity of the flow. Denoted by a
solid circle. This is also called as a Pseudo state where the state has no
variables describing it further and no activities.
State:
Represents the state of object at an instant of time. In a state diagram,

there will be multiple of such symbols, one for each state of the object we are
discussing. Denoted by a rectangle with rounded corners and compartments

(such as a class with rounded corners to denote an object).
Event and Action:
A trigger that causes a transition to occur is called as an event or action.

Every transition need not occur due to the occurrence of an event or action
directly related to the state that transitioned from one state to another. As
described above, an event/action is written above a transition that it causes.
Final state:
The end of the state diagram is shown by a bulls eye symbol, also
called a final state. A final state is another example of a pseudo state because
it does not have any variable or action described.
[39]
2.2 Physical Design

2.2.1 System flowchart:
System flowchart is the graphical representation of the flow of data in the

system, and represents the work process of the system. Various symbols are
used in the flowchart to designate specific actions.
P a ra lle lo g ra m
Parallelogram is used to represent input and output of the system.
Rectangle
Rectangle represents the process that needs to be carried out in the
system flowchart
Diamond
Diamond indicates the decision to be performed in the flowchart.
Oval
The oval shape signifies the start and end of the program in the
system flowchart.
Flow Line
Flow line, a line with an arrowhead, is used to indicate the flow of data or
logic in the system flowchart.
[40]
START
SYSTEM FLOW FOR ADMIN:
User ID/Password for LOGIN
VALID
NO
Activate Registration
YES
[41]
Update User
Update AD
Delete AD
Update Price
END
[42]
SYSTEM FLOW FOR User/Client:
START
Registered Registration
User ID/Password for

LOGIN
Valid
NO
YES
Active Registration
[43]
Update Information
Apply for Advertisement

END
[44]
IMPLEMENTATION
PHASE
[45]
3.1 Coding
3.1.1 Screen Layouts:-
1 - Welcome Page:-
2 - AboutUs Page:-
[46]
3 - ContactUs Page:-
4 - Registration Page:-
[47]
5 - SignIn Page:-
6 - RadioForm Page:-
[48]
7 - NewsPaper Form Page:-

8 - TelevisionForm Page:-
[49]
9 - BannerForm Page:-
10 - InternetForm Page:-
[50]
11 - MagazineForm Page:-
6 - Detail Update Page:-
[51]
3.1.2 Deployment:-
Software deployment is all of the activities that make
a software system available for use.
The general deployment process consists of several
interrelated activities with possible transitions between
them. These activities can occur at the producer side
or at the consumer side or both. Because every
software system is unique, the
precise processes or procedures within each activity
can hardly be defined.
Therefore, "deployment" should be interpreted as
a general process that has to be customized according to
specific requirements or characteristics. A brief
description of each activity will be presented later.
Deployment activities
Release
The release activity follows from the completed development process.

It includes all the operations to prepare a system for assembly
and transfer to the customer site. Therefore, it must determine
the resources required to operate at the customer site and
collect information for carrying out subsequent activities of
deployment process.
Adapt
The adaptation activity is also a process to modify a software
system that has been previously installed.
It differs from updating in that adaptations are initiated by local
events such as changing the environment of customer site, while
updating is mostly started from remote software producer.
Update
The update process replaces an earlier version of all or part of a
software system with a newer release.
Built-In
Mechanisms for installing updates are built into some software systems.
Automation of these update processes ranges from fully automatic to
user initiated and controlled
Version tracking
Version tracking systems help the user find and install updates to
software systems installed on PCs and local networks.
Web based version tracking systems notify the user when updates
are available for software systems installed on a local system. For
example:VersionTracker Pro checks software versions on a user's
computer and then queries its database to see if any updates are
available.
[52]
Local version tracking system notifies the user when updates are
available for software systems installed on a local system.
Retire
Ultimately, a software system is marked as obsolete and support by the
producers is withdrawn. It is the end of the life cycle of a software
product.
3.2 Testing Phase
3.2.1 Testing and it Types: -

Software testing is an investigation conducted to provide stakeholders
[
with information about the quality of the product or service -under test.
Software testing can also provide an objective, independent view of the software to
allow the Business to appreciate and understand the risks of software
implementation.
Test techniques include, but are not limited to, the process of executing a program
or application with the intent of finding software bugs
Testing Type
[53]
There are different Modules of testing. On the basis of testing methods there are two
types of testing:
1. White-box testing.
2. Black-box testing.
1). WHITE-BOX TESTING
White-box testing sometimes called Glass-Box Testing, is a test case

design methods that users the control structure of the procedural design to drive the
test case.
Logical errors and incorrect assumption are inversely proportional to the probability that
a program will be executed. Errors tend to creep into our work we design and
implement function; condition that is out of the mainstream tends to be well
understood.
We often believe that a logical path is not likely to be executed when in fact it may be
executed on a regular basis. The logical flow of a program times counter intuitive.
2).BLACK-BOX TESTING:
For our system periodically we have tested our website using black-box testing.
Thinking as a client we have evaluated the website for its easy going and
convenience.
Unit testing:
During the programming stages each and every form, modules and class
treated unit has been put into the test data. Every module is tested
independently. The steps are follows.
1. Manually code is tested like spelling checkes, logics and errors.
2. Once the manual checking is over the complication has been done.
Syntactical errors if any have to be corrected.
3. After the clean completion the program, some dummy data, as

specification, has been used for testing of the module to see if it works as
specified.
[54]
Integration testing:
After the individuals modules were tested out we go the integrated to create a
complete system. This integration process involves building the system and
testing the resultant system for problems that arise from component interaction.
Performance testing
Performance testing is designed to test the runtime performance of the system within
the system context of the system. These tests were performed as module level
as well as system level. Individual modules were tested for required performance.
Interface testing:
Interface sting is integral part of integration. We examined the code to be tested and
explicitly list each call to an external component. Performance testing is the test case
design method that exercises the logical conditions. int the system standards tests for
GUIs have been performed, which are as follows:
The position and related for all controls were checked.

Validations for all inputs were done.
Pull down controls was verified for proper functionality.
Whether the non-editable text controls disabling and it was also verified that it
doesnt exceed the maximum allowed length.
Condition testing:
Performance testing is the test case design method that exercises the logical
conditions.
3.2.2 Methodology adopted for testing:
3.2.2.1 White Box Testing:
o White-box testing is a method of testing software that tests
internal structures or workings of an application, as opposed to its
functionality.
o In white-box testing an internal perspective of the system, as well
as programming skills, are used to design test cases.
o The tester chooses inputs to exercise paths through the code
and determine the appropriate outputs. This is analogous to testing
nodes in a circuit, e.g. in-circuit testing
o In this method of testing the test cases are calculated based on
analysis internal structure of the system based on Code coverage,
[5
5]
branches coverage, paths coverage, condition Coverage etc.
Advantages:
Side effects of having the knowledge of the source code are beneficial to
thorough testing.
Optimization of code by revealing hidden errors and being able to remove
these possible defects.
Gives the programmer introspection because developers carefully
describe any new implementation.
Forces test developer to reason carefully about implementation.
Approximates the portioning done by execution equivalence.
White box tests are easy to automate.
White box testing give clear, engineering-based, rules for when to
stop testing.
3.2.2.2 Blackbox testing:-

Black-box testing is a method of software testing that examines the
functionality of an application without peering into its internal structures or
workings. This method of test can be applied to virtually every level of software
testing: unit, integration, system and acceptance. It typically comprises most if
not all higher level testing, but can also dominate unit testing as well.
Black-box testing treats the software as a "black box", examining functionality
without any knowledge of internal implementation. The testers are only aware
of what the software is supposed to do, not how it does it. Black-box testing
methods include: equivalence partitioning, boundary value analysis, all-pairs
testing, state transition tables, table testing, fuzz testing, model-based
testing, use case testing, exploratory testing and specification-based testing.
Specification-based testing aims to test the functionality of software according to
the applicable requirements. This level of testing usually requires thorough test
to be provided to the tester, who then can simply verify that for a given input, the
output value (or behaviour), either "is" or "is not" the same as the expected value
specified in the test case. Test cases are built around specifications and
requirements, i.e., what the application is supposed to do. It uses external
descriptions of the software, including specifications, requirements, and designs
to derive test cases. These tests can be functional or non-functional, though
usually functional.
Specification-based testing may be necessary to assure correct functionality,
but it is insufficient to guard against complex or high-risk situations.
One advantage of the black box technique is that no programming knowledge is
required. Whatever biases the programmers may have had, the tester likely has
a different set and may emphasize different areas of functionality. On the other
hand, black-box testing has been said to be "like a walk in a dark labyrinth
without a flashlight." Because they do not examine the source code, there are
situations when a tester writes many test cases to check something that could
[56]
have been tested by only one test case, or leaves some parts of the
program untested.
3.2.2.3 BOUNDARY VALUE ANALYSIS:
Boundary Value Analysis (BVA)-A Black Box Testing Technique
This Black Box testing technique believes and extends the concept that the density
of defect is more towards the boundaries. This is done due to the following
reasons
a) Usually the programmers are not able to decide whether they have to use <=
operator or < operator when trying to make comparisons.
b) DifferentTerminating conditions of For-loops, While loops and Repeat
loops may cause defects to move around the boundary conditions.
c) The requirements themselves may not be clearly understood, especially

around the boundaries, thus causing even the correctly coded program to
not perform the correct way
The basic idea of BVA is to use input variable values at their minimum, just
above the minimum, a nominal value, just below their maximum and at their
maximum. Meaning thereby (min, min+, nom, max-, max)
BVA is based upon a critical assumption that is known as Single fault assumption
theory. According to this assumption, we derive the test cases on the basis of the
fact that failures are not due to simultaneous occurrence of two (or more) faults.
So, we derive test cases by holding the values of all but one variable at their
nominal values and allowing that variable assume its extreme values.
If we have a function of n-variables, we hold all but one at the nominal values and
let the remaining variable assume the min, min+, nom, max-and max values,
repeating this for each variable. Thus, for a function of n variables, BVA yields (4n +
1) test cases.
3.2.2.4 EQUIVALENCE CLASS PARTIONING:
Equivalence partitioning (also called Equivalence Class Partitioning or ECP):-It is a

software testing technique that divides the input data of a software unit into
partitions of equivalent data from which test cases can be derived. In principle, test
cases are designed to cover each partition at least once. This technique tries to
define test cases that uncover classes of errors, thereby reducing the total number
of test cases that must be developed. An advantage of this approach is reduction in
the time required for testing software due to lesser number of test cases.
Equivalence partitioning is typically applied to the inputs of a tested
component, but may be applied to the outputs in rare cases. The equivalence
partitions are usually derived from the requirements specification for input
attributes that influence the processing of the test object.
[5
7]
The fundamental concept of ECP comes from equivalence class which in
turn comes from equivalence relation. A software system is in effect a
computable function implemented as an algorithm in some implementation
programming language. Given an input test vector some instructions of that
algorithm get covered, ( see code coverage for details ) others do not .
Equivalence partitioning is not a standalone method to determine test cases.

It has to be supplemented by boundary value analysis. Having determined
the partitions of possible inputs the method of boundary value analysis has
to be
applied to select the most effective test cases out of these partitions.
1. Login Page:
Boundary Value Analysis for Login Page:
Case Reference No.
1
Equivalence Class Partitioning for Login Page:
Password
<6 Digits
A to Z, a to z
Invalid part
Test Case for Login Page:
Test Reference No.
2. Registration Page:
Boundary Value Analysis for Login Page:
Test Reference No.
1
5
Equivalence Class Partitioning for Login Page:
UserNAme
<6 Digits
A to Z, a to z
Invalid part
Password
<6 Digits
A to Z, a to z
Invalid part
E-mail
<6 Digits
A to Z, a to z
Invalid part
Mobile No.
<6 Digits
A to Z, a to z
Invalid part
Phone No.
<6 Digits
A to Z, a to z
Invalid part
[6
0]
Test Case for Login Page:
Test Reference No.

1
6
7
9
10
11
12
13
&
PHASE
EVOLUTION
MAINTAINANE
4.1 System Maintenance / Future Enhancement:-
AS the number of computer based systems, grieve libraries of computer

software began to expand. In house developed projects produced tones of
thousand soft program source statements. Software products purchased
from the outside added hundreds of thousands of new statements. A dark
cloud appeared on the horizon. All of these programs, all of those source
statements-had to be corrected when false were detected, modified as
user requirements changed, or adapted to new hardware that was
purchased. These activities were collectively called software
Maintenance.
The maintenance phase focuses on change that is associated with
error correction, adaptations required as the software's environment
evolves, and changes due to enhancements brought about by changing
customer requirements. Four types of changes are encountered during
the maintenance phase.
Correction
Adaptation
Enhancement
Prevention
Correction:
Even with the best quality assurance activities is lightly that the
customer will uncover defects in the software. Corrective maintenance
changes the software to correct defects.
Maintenance is a set of software Engineering activities that occur

after software has been delivered to the customer and put into operation.
Software configuration management is a set of tracking and control
activities that began when a software project begins and terminates only
when the software is taken out of the operation.
We may define maintenance by describing four activities that
are undertaken after a program is released for use:
Corrective Maintenance
Adaptive Maintenance
Perfective Maintenance or Enhancement
Preventive Maintenance or reengineering
Only about 20 percent of all maintenance work are spent "fixing mistakes".
The remaining 80 percent are spent adapting existing systems to changes
in their external environment, making enhancements requested by users,
and reengineering an application for use.
[63]
ADAPTATION:
Over time, the original environment (E>G., CPU, operating
system, business rules, external product characteristics) for which the
software was developed is likely to change. Adaptive maintenance results
in modification to the software to accommodate change to its external
environment.
ENHANCEMENT:
As software is used, the customer/user will recognize additional
functions that will provide benefit. Perceptive maintenance extends the
software beyond its original function requirements.
PREVENTION:
Computer software deteriorates due to change, and because of this,
preventive maintenance, often called software re engineering, must be
conducted to enable the software to serve the needs of its end users. In
essence, preventive maintenance makes changes to computer programs
so that they can be more easily corrected, adapted, and enhanced.
Software configuration management (SCM) is an umbrella activity that is
applied throughout the software process.
Future:
This application avoids the manual work and the problems concern with it.
It is an easy way to obtain the information regarding the various products
information that is present in the markets.
Well I and my team members have worked hard
in order to present an improved website better than the existing ones
regarding the information about the various activities. Still, we found out
that the project can be done in a better way. Primarily, when we request
information about a particular Ad it just shows the company, seller details
and no. of quantities available. So, after getting the information
4.2 User Manual:-

1 First login to account, if you are not logged-in then please click on
register button and get registered.
2 After login, now you can choose media channel from multiple channel.
3 Once you have chosen the channel, For example. You have
selected radio channel.
4 Fill out the radio form and upload the content(Radio channel)
5 After completing then you can logout
6 You will get reponse soon via mail from admin regarding your posted Ad.
[64]
[65]
[66]
[67]
[6
8]
ANNEXURE
As the current system is totally manual.
Due to manually process is requires more time for
Completion of any work.
Existing system is manual.so it increases the chances of
errors. Lots of consumed for each report generation.
More man power is require and timely updating complicated.
1) Data Dictionary:-
A Data Dictionary or metadata repository is defined as a centralized repository
of information about data such as meaning, relationships to other
data,origin,usage and format. The term may have one of several closely
related meanings pertaining to database and database management system.
1)Data Dictionary of Database
1-Registration :
Sr. no Field Name
1 C_id
2 Email
3 User_name
4 Pass_word
5 Name
6 Address
7 mobile
8 Phone
9 designation
2 Login
Sr.no Field Name
1 uname
2 Password
3 Radio
Sr No. Field Name
1 id
2 from
3 to
4 program
5 Broad_time
6 repeat
7 Ad_duration
8 Pro_duration
9 Station
10 Price
11 Upload_file
12 By
4 television
Sr No. Field Name
1 id
2 from
[7
0]
3 to
4 program
5 Telecasting_time
6 repeat
7 Ad_duration
8 Pro_duration
9 channel
10 Price
11 Upload_file
12 By
5 Internet
Sr No. Field Name
1 id
2 dfrom
3 dto
4 size
5 Webname
6 pattern
7 Price
8 Upload_file
9 By
6 Magazine
Sr No. Field Name
1 id
2 dfrom
3 dto
4 Mname
5 adpage
6 size
7 pattern
8 Price
9 Upload_file
10 By
7-Banner
Sr No. Field Name
1 id
2 dfrom
3 dto
4 state
5 Location
6 size
7 Banner_type
8 Price
9 Upload_file
10 By
8-NewsPaper
Sr No. Field Name
1 id
2 dfrom
3 dto
4 Papername
5 advertisingpage
6 Paperedition
7 size
8 Issue
9 pattern
10 Price
11 Upload_file
12 By
9-Banner1
Sr No. Field Name
1 id
2 state
3 Location
4 Place
10-Radio1
Sr No. Field Name
1 id
2 Stn_list
3 Pro_list
4 Pduration
5 Pro_duration
11-Television1
Sr No. Field Name
1 id
2 Channel
3 Program
4 Tel_time
5 Pro_duration
2) List of Abbreviations:
PHP: Hypertext Preprocessor.
ID:- Identity
ER:- Entity Relationship
BVA:-Boundary Value Analysis
ECP:-Equivalence Class Partitioning
i.e.:-that is
PERT:-Project Evolution and Review Technique
SDLC:- Software Development Life Cycle
URL:-Uniform Resource Locator
3) Reference Bibliography and Website used
WEBSITES:
www.google.com
www.wikipedia.com
www.w3school.com
[76]

Online Advertismnet System (Ad Agency) Report

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Online Advertismnet System (Ad Agency) Report

Enviado por

Direitos autorais:

Formatos disponíveis

B.Sc.

1.1- Requirement Gathering

Here we are try to developed such type of system is provide the

For example any customer wants to register in listed newspaper from

1.1.2 Fact Finding Technique:

Today, with great diversity of goods and services, competition, advertising

Advertising helps the user to choose a product, encourages buyers to

In the absence of advertising, we could not possibly know about many

1.1.3 Objective and scope of the project:

An advertising agency or ad agency is a service business

An ad agency is independent from the client and provides an

1.1.4 Problem with existing system:

If an agency does not communicate or relay its clients goals and

1.1.5 Advantage of proposed system:

In order to avoid the above problem this project is to provide

advertisement details like advertisement cost in various

1.2 Feasibility Study

study of this project such as Technical, Economical and

1.2.1 Operational feasibility:

1.2.2 Technical Feasibility:

A study of resource availability that may affect the ability to achieve an

Front-end and back-end selection

7. Operating System compatible.

Linux (Apache), Windows (Apache/IIS)

The following Xampp settings

1.2.3 Economical/Behavioral Feasibility:

The cost to conduct a full system investigation.

1.2.4 Cost benefit analysis:

1.3 Requirement Specification

Available Various forms: - The system allows the user or member to

Add station/channel/location form:- The Admin rights to add station/channel and

1.3.2 Technical Requirement:

Xampp Server(For Window)

The main aim of this project is to provide advertisement details like

Here we are try to developed such type of system is provide the

System own information storage:- .

Major transactions to be provided by the system are:-

The main function of system:-

The advantage of waterfall development is that it allows for

1.4 Tools And Technologies

HARDWARE REQUIREMENT FOR DEVLOPEMENT:-

Linux (Apache), Windows (Apache/IIS)

-> Platform support:

In this module, personal information is arranged in a place and user can

access the information .

a) Microsoft Word Professional Plus 2013:-

Microsoft Word is word processor tool developed by Microsoft.

Chart and Diagram:-

Open software model format

True MDA Support

Applicability of methodologies and platforms

Software model verification Function

2.1 Detailed life Cycle of Project (logical design):

2.1.1 Class Diagram:

A class diagram is a diagram showing a collection of classes and interfaces,

A class diagram is a pictorial representation of the detailed system design. Design

UML provides a class notation to represent classes in class diagram. The

The first compartments depict the name of the class.

The second compartments depicts the attributes of the class

The third compartments depicts the operations of the class

Representing Relationships in class diagram

In UML relationships model the way in which the elements of a software

Realization: In a realization relationship, one entity (normally an interface) defines