ADVERTISEMENT MANAGEMENT SYSTEM PROJECT REPORT
ADVERTISEMENT MANAGEMENT SYSTEM PROJECT REPORT
ADVERTISEMENT MANAGEMENT SYSTEM PROJECT SOURCE CODE
ABSTRACT
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.
Here the total front end is developed using Asp.Net and backend is developed
using SQL server.
If an agency
does not communicate or relay its client’s 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. How ever 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
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.
Modules: ADVERTISEMENT MANAGEMENT SYSTEM PROJECT
This project involved mainly Four modules.
Registration
Administrator
Budget
Budget List
Modules Description:
Registration:
In this module he/she has to
register himself/herself with the personal details and get the Login id. After
getting the login id he/she has to specify Ad. Requirements of the kind of Ad he/she has to advertise on behalf of
his/her company
Administrator:
Administrator
should be able to block fraudulent users from using the system. Admin should be
able to add more categories and merge categories.
Normal User:
In this Module
users can enter into different channels of packages like short time period or
long time. They can enter into new schemes provided by ad agency. Also they can
upload the videos of their company for advertising.
Budget:
New user’s budget is registered here. They can Budget on the
advertising ad with the ad agency in this module.
Budgets List:
According to budget the
advertisements are allotted for specific period.
Here time period
the agency will follow up their product is specified.
INDEX
S. No Contents
1. Introduction
2. Analysis
2.1 System Analysis
2.2 System Specification
3. Design
Approach
3.1 Introduction to Design
3.2 UML Diagrams
3.3 Dataflow Diagrams
3.4 E-R Diagrams
4. Project
Modules
5. Implementation
5.1 Concepts and Technologies
5.2 Testing
5.2.1 Test Cases
6. Output
Screens
7. Conclusion
8. Future
Enhancements
9. Bibliography
INTRODUCTION - ADVERTISEMENT MANAGEMENT SYSTEM PROJECT
We don’t sell a
‘boxed’ product. Each system we create for our clients is driven by their exact
specifications and internal processes. Too often, agencies change their creative
flow and processes to fit technology. We believe it should be the other way
around.
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.
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. Here the total front end is developed using Asp.Net and backend
is developed using Sql server.
ANALYSIS -ADVERTISEMENT MANAGEMENT SYSTEM PROJECT
System
Analysis:
Existing
System:
If an agency does not
communicate or relay its client’s 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. How
ever 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.
Proposed System - ADVERTISEMENT MANAGEMENT SYSTEM PROJECT
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. Here the total front end is developed using Asp.Net and backend
is developed using SQL server.
Objective
of the System:
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.
System Specifications:
Hardware Requirements
·
Pentium-IV (Processor).
·
256 MB or 512 MB Ram
·
512 KB Cache Memory
·
Hard disk 10 GB
·
Microsoft Compatible 101 or
more Key Board
Software Requirements
·
Web Technologies : ASP.NET 2.0
·
Language : C#
·
Database : SQL SERVER 2005
·
Web Server : IIS
·
Operating System : WINDOWS XP
DESIGN - ADVERTISEMENT MANAGEMENT SYSTEM PROJECT
Introduction:
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.
Once
the software requirements have been analyzed and specified the software design
involves three technical activities - design, coding, implementation and
testing that are required to build and verify the software.
The design activities
are of main importance in this phase, because in this activity, decisions
ultimately affecting the success of the software implementation and its ease of
maintenance are made. These decisions have the final bearing upon reliability
and maintainability of the system. Design is the only way to accurately
translate the customer’s requirements into finished software or a system.
Design is the place where quality is
fostered in development. Software design is a process through which
requirements are translated into a representation of software. Software design
is conducted in two steps. Preliminary design is concerned with the
transformation of requirements into data.
UML Diagrams:
Actor:
A coherent set of roles that users of use cases play when interacting with the use `cases.
A coherent set of roles that users of use cases play when interacting with the use `cases.
Use case:
A description of
sequence of actions, including variants, that a system performs that yields an
observable result of value of an actor.
UML stands for
Unified Modeling Language. UML is a language for specifying, visualizing and
documenting the system. This is the step while developing any product after
analysis. The goal from this is to produce a model of the entities involved in
the project which later need to be built. The representation of the entities
that are to be used in the product being developed need to be designed.
There are various
kinds of methods in software design:
They are as
follows:
ØUse case Diagram
ØSequence Diagram
ØCollaboration Diagram
ØActivity Diagram
ØState chat Diagram
Use
case Diagrams:
Use case diagrams
model behavior within a system and helps the developers understand of what the
user require. The stick man represents what’s called an actor.
Use case diagram can be useful
for getting an overall view of the system and clarifying that can do and more
importantly what they can’t do.
Use case diagram
consists of use cases and actors and shows the interaction between the use case
and actors.
Ø
The purpose is to show the
interactions between the use case and actor.
Ø
To represent the system
requirements from user’s perspective.
Ø
An actor could be the end-user
of the system or an external system.
Use case Diagram
A Use case is a
description of set of sequence of actions.
Graphically it is rendered as an ellipse with solid line including only
its name. Use case diagram is a behavioral
diagram that shows a set of use cases and actors and their relationship. It is an association between the use cases
and actors. An actor represents a
real-world object. Primary Actor –
Sender, Secondary Actor Receiver.
Sequence Diagram
Sequence diagram
and collaboration diagram are called INTERACTION DIAGRAMS. An interaction
diagram shows an interaction, consisting of set of objects and their
relationship including the messages that may be dispatched among them.
A sequence diagram
is an introduction that empathizes the time ordering of messages. Graphically a
sequence diagram is a table that shows objects arranged along the X-axis and
messages ordered in increasing time along the Y-axis.
DATA FLOW DIAGRAMS: ADVERTISEMENT MANAGEMENT SYSTEM PROJECT
The DFD takes an input-process-output view of
a system i.e. data objects flow into the software, are transformed by
processing elements, and resultant data objects flow out of the software.
Data objects represented by
labeled arrows and transformation are represented by circles also called as
bubbles. DFD is presented in a hierarchical fashion i.e. the first data flow
model represents the system as a whole. Subsequent DFD refine the context
diagram (level 0 DFD), providing increasing details with each subsequent
level.
The DFD enables the software
engineer to develop models of the information domain & functional domain at
the same time. As the DFD is refined into greater levels of details, the
analyst performs an implicit functional decomposition of the system. At the
same time, the DFD refinement results in a corresponding refinement of the data
as it moves through the processes that embody the applications.
A context-level DFD for the system
the primary external entities produce information for use by the system and
consume information generated by the system. The labeled arrow represents data
objects or object hierarchy.
RULES FOR DFD:
·
Fix the scope of the system by means of context diagrams.
·
Organize the DFD so that the main sequence of the actions
·
Reads left to right and top to bottom.
·
Identify all inputs and outputs.
·
Identify and label each process internal to the system with
Rounded circles.
·
A process is required for all the data transformation and Transfers.
Therefore, never connect a data store to a data Source or the destinations or
another data store with just a Data flow arrow.
·
Do not indicate hardware and ignore control information.
·
Make sure the names of the processes accurately convey everything the
process is done.
·
There must not be unnamed process.
·
Indicate external sources and destinations of the data, with Squares.
·
Number each occurrence of repeated external entities.
·
Identify all data flows for each process step, except simple Record
retrievals.
·
Label data flow on each arrow.
·
Use details flow on each arrow.
·
Use the details flow arrow to indicate data movements.
E-R Diagrams:
The Entity-Relationship (ER)
model was originally proposed by Peter in 1976 [Chen76] as a way to unify the
network and relational database views. Simply stated the ER model is a
conceptual data model that views the real world as entities and relationships.
A basic component of the model is the Entity-Relationship diagram which is used
to visually represent data objects. Since Chen wrote his paper the model has
been extended and today it is commonly used for database design For the
database designer, the utility of the ER model is:
·
It maps well to the
relational model. The constructs used in the ER model can easily be transformed
into relational tables.
·
It is simple and easy to
understand with a minimum of training. Therefore, the model can be used by the
database designer to communicate the design to the end user.
·
In addition, the model can
be used as a design plan by the database developer to implement a data model in
specific database management software.
Connectivity
and Cardinality
The basic types of
connectivity for relations are: one-to-one, one-to-many, and many-to-many. A one-to-one
(1:1) relationship is when at most one instance of a entity A is associated
with one instance of entity B. For example, "employees in the company are
each assigned their own office. For each employee there exists a unique office
and for each office there exists a unique employee.
A one-to-many (1:N)
relationships is when for one instance of entity A, there are zero, one, or
many instances of entity B, but for one instance of entity B, there is only one
instance of entity A. An example of a 1:N relationships is
a department has
many employees
Each employee is
assigned to one department
A many-to-many (M:N)
relationship, sometimes called non-specific, is when for one instance of entity
A, there are zero, one, or many instances of entity B and for one instance of
entity B there are zero, one, or many instances of entity A. The connectivity
of a relationship describes the mapping of associated
ER - DIAGRAM Notation
There is no standard for
representing data objects in ER diagrams. Each modeling methodology uses its
own notation. The original notation used by Chen is widely used in academics
texts and journals but rarely seen in either CASE tools or publications by
non-academics. Today, there are a number of notations used; among the more
common are Bachman, crow's foot, and IDEFIX.
All notational styles represent
entities as rectangular boxes and relationships as lines connecting boxes. Each
style uses a special set of symbols to represent the cardinality of a
connection. The notation used in this document is from Martin. The symbols used
for the basic ER constructs are:
·
Entities are represented by labeled
rectangles. The label is the name of the entity. Entity names should be
singular nouns.
·
Relationships are represented by a solid line
connecting two entities. The name of the relationship is written above the
line. Relationship names should be verbs
·
Attributes, when included, are listed inside
the entity rectangle. Attributes which are identifiers are underlined.
Attribute names should be singular nouns.
·
Cardinality of many is represented by a line
ending in a crow's foot. If the crow's foot is omitted, the cardinality is one.
·
Existence is represented by placing a circle
or a perpendicular bar on the line. Mandatory existence is shown by the bar
(looks like a 1) next to the entity for an instance is required. Optional
existence is shown by placing a circle next to the entity that is optional
PROJECT MODULES - ADVERTISEMENT MANAGEMENT SYSTEM PROJECT
·
Administrator
·
Registration
·
Budget
·
Budget List
MODULE DESCRIPTION
Name
of the module – 1:
Administrator
Description:
Administrator
should be able to block fraudulent users from using the system. Admin should be
able to add more channels and timing’s.
Sub modules:
Ø Login
page
Ø Change
password
Registration
Page:
In this sub module we add
the details of the user like user name, contact no, email id, password and
report by taking the primary constraint user id. And it also adds these details
in database.
Login Page:
In this sub
module the user gives his login and password to enter. If he is valid he enters
into resume wizard. If he is not valid he it wants valid.
Forgot Password:
If the user
forgot his password, he enter into forget password page there by giving details
he get his password.
Change Password:
If the user
wants to change his password he can change his password by giving some details
Admin has the rights to see users
and their ad’s and has a right to accept or reject it.
He
see the timing that user had requested to show his ad according to the channel.
He can check the user details if
he want.
He can download and view the
video’s that user added to show in channel
Name of the module -2: User
Description:
When
the user login type’s of ads appear he can choose this type. Then he gets new
ad information form. He fills that form and chooses the budget and timing’s
Sub modules:
Ø
Slides
Ø Animation
Ø
Video’s
Name of the module -3: BUDGET
Description:
New user’s budget is
registered here. They can Budget on the advertising ad with the ad agency in
this module.
Name of the module -4: Budget List
Description:
According to budget the
advertisements are allotted for specific period.Here time period the agency
will follow up their product is specified
DATABASE TABLES: ADVERTISEMENT MANAGEMENT SYSTEM PROJECT
Admin Register Table:
|
Name
|
Null/Not Null
|
Type
|
Key
|
|
uid
|
Not Null
|
int
|
Identity(1000,1)
|
|
name
|
Null
|
varchar(40)
|
|
|
pwd
|
Null
|
varchar(40)
|
|
|
cpwd
|
Null
|
varchar(50)
|
|
|
phone
|
Null
|
varchar(20)
|
|
|
email
|
Null
|
varchar(50)
|
Primary Key
|
|
address
|
Null
|
varchar(50)
|
|
|
city
|
Null
|
varchar(50)
|
|
|
petsname
|
Not Null
|
varchar(30)
|
|
|
groupname
|
Null
|
varchar(30)
|
|
User Registration Table
|
Name
|
Null/Not Null
|
Type
|
Key
|
|
uid
|
Not Null
|
int
|
Identity(1000,1)
|
|
name
|
Null
|
varchar(40)
|
|
|
pwd
|
Null
|
varchar(40)
|
|
|
cpwd
|
Null
|
varchar(50)
|
|
|
phone
|
Null
|
varchar(20)
|
|
|
email
|
Null
|
varchar(50)
|
Primary Key
|
|
address
|
Null
|
varchar(50)
|
|
|
city
|
Null
|
varchar(50)
|
|
|
petsname
|
Not Null
|
varchar(30)
|
|
|
groupname
|
Null
|
varchar(30)
|
|
Budget Video’s Table
|
Name
|
Null/Not Null
|
Type
|
Key
|
|
channel_name
|
Null
|
varchar(50)
|
|
|
category
|
Null
|
varchar(50)
|
|
|
ad_span
|
Null
|
varchar(50)
|
|
|
timea
|
Null
|
varchar(50)
|
|
|
timeb
|
Null
|
varchar(50)
|
|
|
timec
|
Null
|
varchar(50)
|
|
|
timed
|
Null
|
varchar(50)
|
|
|
timee
|
Null
|
varchar(50)
|
|
Budget Animated Table
|
Name
|
Null/Not Null
|
Type
|
Key
|
|
channel_name
|
Null
|
varchar(50)
|
|
|
category
|
Null
|
varchar(50)
|
|
|
ad_span
|
Null
|
varchar(50)
|
|
|
timea
|
Null
|
varchar(50)
|
|
|
timeb
|
Null
|
varchar(50)
|
|
|
timec
|
Null
|
varchar(50)
|
|
|
timed
|
Null
|
varchar(50)
|
|
|
timee
|
Null
|
varchar(50)
|
|
Budget Slides Table
|
Name
|
Null/Not Null
|
Type
|
Key
|
|
channel_name
|
Null
|
varchar(50)
|
|
|
category
|
Null
|
varchar(50)
|
|
|
ad_span
|
Null
|
varchar(50)
|
|
|
timea
|
Null
|
varchar(50)
|
|
|
timeb
|
Null
|
varchar(50)
|
|
|
timec
|
Null
|
varchar(50)
|
|
|
timed
|
Null
|
varchar(50)
|
|
|
timee
|
Null
|
varchar(50)
|
|
Channel Time Table
|
Name
|
Null/Not Null
|
Type
|
Key
|
|
uid
|
Null
|
int
|
|
|
name
|
Null
|
varchar(20)
|
|
|
adname
|
Null
|
varchar(100)
|
|
|
channel
|
Null
|
varchar(20)
|
|
|
timings
|
Null
|
varchar(100)
|
|
User New AD’s Table
|
Name
|
Null/Not Null
|
Type
|
Key
|
|
uid
|
Null
|
int
|
|
|
name
|
Null
|
varchar(20)
|
|
|
email
|
Null
|
varchar(50)
|
|
|
adname
|
Null
|
varchar(100)
|
|
|
rdate
|
Null
|
varchar(20)
|
|
|
censor
|
Null
|
varchar(20)
|
|
|
director
|
Null
|
varchar(20)
|
|
|
address
|
Null
|
varchar(20)
|
|
|
video
|
Not Null
|
varchar(100)
|
|
Subject s Table
|
Name
|
Null/Not Null
|
Type
|
Key
|
|
Subjectid
|
Null
|
int
|
Primary Key
|
|
Subjectname
|
Null
|
varchar(20)
|
|
|
Country
|
Null
|
varchar(20)
|
|
|
State
|
Null
|
varchar(20)
|
|
|
location
|
Null
|
varchar(20)
|
|
View Video’s Table
|
Name
|
Null/Not Null
|
Type
|
Key
|
|
uid
|
Null
|
int
|
|
|
name
|
Null
|
varchar(20)
|
|
|
email
|
Null
|
varchar(50)
|
|
|
adname
|
Null
|
varchar(100)
|
|
|
rdate
|
Null
|
varchar(20)
|
|
|
censor
|
Null
|
varchar(20)
|
|
|
permission
|
Null
|
varchar(20)
|
|
FEASIBILITY STUDY: ADVERTISEMENT MANAGEMENT SYSTEM PROJECT
Feasibility study is conducted once
the problem is clearly understood.
Feasibility study is a high level capsule version of the entire system
analysis and design process. The objective
is to determine quickly at a minimum expense how to solve a problem. The purpose of feasibility is not to solve
the problem but to determine if the problem is worth solving.
The system has been tested for feasibility in the following points.
1. Technical Feasibility
2. Economical Feasibility
3. Operational Feasibility.
Technical Feasibility
The project entitles "Courier Service System” is technically
feasibility because of the below mentioned feature. The project was developed in Java which Graphical
User Interface.
It
provides the high level of reliability, availability and compatibility. All these make Java an appropriate language
for this project. Thus the existing
software Java is a powerful language.
Economical
Feasibility
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.
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.
Implementation:
Implementation is the stage where the theoretical design is turned into
a working system. The most crucial stage in achieving a new successful system
and in giving confidence on the new system for the users that it will work
efficiently and effectively.
The system can be implemented only after thorough
testing is done and if it is found to work according to the specification.
It involves careful planning, investigation of
the current system and its constraints on implementation, design of methods to
achieve the change over and an evaluation of change over methods a part from
planning. Two major tasks of preparing the implementation are education and
training of the users and testing of the system.
The more
complex the system being implemented, the more involved will be the systems
analysis and design effort required just for implementation.
The
implementation phase comprises of several activities. The required hardware and
software acquisition is carried out. The system may require some software to be
developed. For this, programs are written and tested. The user then changes
over to his new fully tested system and the old system is discontinued.
TESTING:
The testing phase is an important part of software development. It is
the computerized system will help in automate process of finding errors and missing
operations and also a complete verification to determine whether the objectives
are met and the user requirements are satisfied.
Software testing is carried out in three steps:
1.
The first includes unit testing, where in each module is tested to
provide its correctness, validity and also determine any missing operations and
to verify whether the objectives have been met. Errors are noted down and
corrected immediately. Unit testing is the important and major part of the
project. So errors are rectified easily in particular module and program
clarity is increased. In this project entire system is divided into several
modules and is developed individually.
So unit testing is conducted to individual modules.
2.
The second step includes
Integration testing. It need not be the case, the software whose modules when
run individually and showing perfect results, will also show perfect results
when run as a whole. The individual modules are clipped under this major module
and tested again and verified the results. This is due to poor interfacing,
which may results in data being lost across an interface. A module can have
inadvertent, adverse effect on any other or on the global data structures,
causing serious problems.
3. The final step involves
validation and testing which determines which the software functions as the
user expected. Here also some modifications were. In the completion of the
project it is satisfied fully by the end user.
Maintenance and environment:
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.
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.
SOFTWARE METHODOLOGY - ADVERTISEMENT MANAGEMENT SYSTEM PROJECT
The software methodology followed in
this project includes the object-oriented methodology and the application
system development methodologies. The description of these methodologies is
given below.
Application System Development – A
Life cycle Approach
Although there are a growing number of applications (such as decision
support systems) that should be developed using an experimental process
strategy such as prototyping, a significant amount of new development work
continue to involve major operational applications of broad scope. The
application systems are large highly structured. User task comprehension and
developer task proficiency is usually high. These factors suggest a linear or
iterative assurance strategy. The most common method for this stage class of
problems is a system development life cycle modal in which each stage of
development is well defined and has straightforward requirements for
deliverables, feedback and sign off. The system development life cycle is
described in detail since it continues to be an appropriate methodology for a
significant part of new development work.
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. In order to manage and control the development
effort, it is necessary to know what should have been done, what has been done,
and what has yet to be accomplished. The phrases in the system development life
cycle provide a basis for management and control because they define segments
of the flow of work, which can be identified for managerial purposes and
specifies the documents or other deliverables to be produced in each phase.
The phases in the life cycle for
information system development are described differently by different writers,
but the differences are primarily in the amount of necessity and manner of
categorization. There is a general agreement on the flow of development steps
and the necessity for control procedures at each stage.
The information
system development cycle for an application consists of three major stages.
Definition.
Development.
Installation and operation.
The first stage of
the process, which defines the
information requirements for a feasible cost effective system. The requirements
are then translated into a physical system of forms, procedures, programs etc.,
by the system design, computer programming and procedure development. The
resulting system is test and put into operation. No system is perfect so there
is always a need for maintenance changes. To complete the cycle, there should
be a post audit of the system to evaluate how well it performs and how well it
meets the cost and performance specifications. The stages of definition,
development and installation and operation can therefore be divided into
smaller steps or phrases as follows.
Definition
Proposed
definition : preparation of
request for proposed applications.
Feasibility
assessment: evaluation of feasibility
and cost benefit of proposed system.
Information
requirement analysis: determination of information needed.
Design
Conceptual
design : User-oriented design of application
development.
Physical system
design: Detailed design of flows and
processes in applications processing system and preparation of program
specification.
Development
Program
development : coding and testing of computer programs.
Procedure
development : design of procedures and
preparation of user instructions.
Installation and operation
Conversion : final system test and conversion.
Operation and maintenance: Month to month operation and maintenance
Post audit : Evaluation of development process,
application system and results of use at the completion of the each phase,
formal approval sign-off is required from the users as well as from the manager
of the project development.
Testing - ADVERTISEMENT MANAGEMENT SYSTEM PROJECT
Testing is a process of executing
a program with the indent of finding an error. Testing is a crucial element of
software quality assurance and presents ultimate review of specification,
design and coding.
System Testing is an
important phase. Testing represents an interesting anomaly for the
software. Thus a series of testing are
performed for the proposed system before the system is ready for user
acceptance testing.
A good test case is one that
has a high probability of finding an as undiscovered error. A successful test
is one that uncovers an as undiscovered error.
Testing Objectives:
1. Testing
is a process of executing a program with the intent of finding an error
2. A good
test case is one that has a probability of finding an as yet undiscovered error
3. A
successful test is one that uncovers an undiscovered error
Testing Principles:
·
All tests should be traceable to end user requirements
·
Tests should be planned long before testing begins
·
Testing should begin on a small scale and progress
towards testing in large
·
Exhaustive testing is not possible
·
To be most effective testing should be conducted by a
independent third party
The primary objective for test case design is to derive a set of
tests that has the highest livelihood for uncovering defects in software. To
accomplish this objective two different categories of test case design
techniques are used. They are
·
White box testing.
·
Black box testing.
White-box testing:
White
box testing focus on the program control structure. Test cases are derived to
ensure that all statements in the program have been executed at least once
during testing and that all logical conditions have been executed.
Block-box testing:
Black box testing is
designed to validate functional requirements without regard to the internal
workings of a program. Black box testing mainly focuses on the information
domain of the software, deriving test cases by partitioning input and output in
a manner that provides through test coverage. Incorrect and missing functions,
interface errors, errors in data structures, error in functional logic are the
errors falling in this category.
Testing strategies:
A
strategy for software testing must accommodate low-level tests that are
necessary to verify that all small source code segment has been correctly
implemented as well as high-level tests that validate major system functions
against customer requirements.
Testing fundamentals:
Testing is a process of
executing program with the intent of finding error. A good test case is one
that has high probability of finding an undiscovered error. If testing is
conducted successfully it uncovers the errors in the software. Testing cannot
show the absence of defects, it can only show that software defects present.
Testing Information flow:
Information flow for testing
flows the pattern. Two class of input provided to test the process. The
software configuration includes a software requirements specification, a design
specification and source code.
Test configuration includes
test plan and test cases and test tools. Tests are conducted and all the
results are evaluated. That is test results are compared with expected results.
When erroneous data are uncovered, an error is implied and debugging commences.
Unit testing:
Unit testing is essential
for the verification of the code produced during the coding phase and hence the
goal is to test the internal logic of the modules. Using the detailed design description as a
guide, important paths are tested to uncover errors with in the boundary of the
modules. These tests were carried out
during the programming stage itself. All units of Vienna SQL were successfully tested.
Integration testing:
Integration testing focuses
on unit tested modules and build the program structure that is dictated by the
design phase.
System testing:
System testing tests the
integration of each module in the system. It also tests to find discrepancies
between the system and it’s original objective, current specification and
system documentation. The primary concern is the compatibility of individual
modules. Entire system is working
properly or not will be tested here, and specified path ODBC connection will
correct or not, and giving output or not are tested here these verifications
and validations are done by giving input values to the system and by comparing
with expected output. Top-down testing
implementing here.
Acceptance
Testing:
This testing is
done to verify the readiness of the system for the implementation. Acceptance
testing begins when the system is complete. Its purpose is to provide the end
user with the confidence that the system is ready for use. It involves planning
and execution of functional tests, performance tests and stress tests in order
to demonstrate that the implemented system satisfies its requirements.
Tools to special importance
during acceptance testing include:
Test coverage Analyzer –
records the control paths followed for each test case.
Timing Analyzer – also
called a profiler, reports the time spent in various regions of the code are
areas to concentrate on to improve system performance.
Coding standards –
static analyzers and standard checkers are used to inspect code for deviations
from standards and guidelines.
Test Cases:
Test cases are derived to
ensure that all statements in the program have been executed at least once
during testing and that all logical conditions have been executed.
Using White-Box testing
methods, the software engineer can drive test cases that
·
Guarantee that logical decisions on their true and
false sides.
·
Exercise all logical decisions on their true and false
sides.
·
Execute all loops at their boundaries and with in
their operational bounds.
·
Exercise internal data structure to assure their
validity.
The test case specification
for system testing has to be submitted for review before system testing
commences.
Conclusion
The package was designed in such a way that future
modifications can be done easily. The
following conclusions can be deduced from the development of the project.
Ø
Automation of the entire
system improves the efficiency
Ø
It provides a friendly
graphical user interface which proves to be better when compared to the
existing system.
Ø
It gives appropriate access
to the authorized users depending on their permissions.
Ø
It effectively overcomes
the delay in communications.
Ø
Updating of information
becomes so easier.
Ø
System security, data
security and reliability are the striking features.
Ø
The System has adequate
scope for modification in future if it is necessary.
Future Enhancements: ADVERTISEMENT MANAGEMENT SYSTEM PROJECT
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 one’s 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
No comments:
Post a Comment