Index Content

 PROJECT PROFILE
 INTRODUCTION
 OBJECTIVE
 PURPOSE
 SDLC
 SYSTEM ANALYSIS
 FEASIBILITY
 SPIRAL MODEL
 REQUIREMENT SPECIFICATION
 HARDWARE/SOFTWARE
 FRONT END
 BACK END
 DESIGN
 DFD
 CONTEXT DIAGRAM
 E-R DIAGRAM
 DATADICTIONARY
 FORMS
 DATA REPORT
 CODING
 TESTING
 IMPLEMENTATION
 FUTURE SCOPE
 CONCLUSION
 BIBLOGRAPHY
 Project Profile

Project Title “NEWSPAPER AGENCY

MANAGEMENT SYSTEM”

Project definition NEWSPAPER AGENCY

MANAGEMENT SYSTEM a paper
that printed and distributed usually
daily and weekly and that
contains news, articles of opinion
features and advertising.

Developed for Newspaper management

Internal project guide Ms. RADHIKA SAHU

Team Size 1 (individual project)

Developer ROSHNI SONI

Hardware configuration Processor :-Intel Core Processor

above Pentium IV

Ram :-512 MB

Hard Disk:- 1 GB

Front end VISUAL BASIC 6.0

Back end MS ACCESS

Operating system WINDOWS XP/7/2000

 INTRODUCTION TO NEWSPAPER
MANAGEMENT SYSTEM

My project title is newspaper management system .A

newspaper printed on paper and issued regularly,
usually once a day or once a week it gives information
and opinion about current events and news usually
people like to read them to stay informed about their
local city, state or country. Printed media usually
distributed weekly or daily in the form of a folded book
papers. The publication is tropically sectioned off
based on subject and content. The most important
and interesting news will be displayed on the front
page of publication. Newspaper may also include
advertisement, opinions, entertainment and other
general interest news. Some of the most popular
newspaper is the wall street journal, the Washington
post, and the India newspaper printed media usually
distributed weekly or daily in the form of a folded book
of paper. The publication is tropically sectioned off
based on subjects and content. The most important or
interesting news will be displayed on the front page of
the publication.
 OBJECTIVE
During the past several decades personnel function has been
transformed from a relatively obscure record keeping staff to central
and top level management functions. There are many factors that
have influenced this transformation like technological advances,
professionalism, and general recognition of human beings as most
important resources.

 A computer based management system is designed to handle

all the primary information required to calculate monthly
statements.

 Separate database is Maintained to handle all the details

required for the correct statement calculation and generation.

 This project intends to introduce more user friendliness in the

various activities such as record updation ,maintenance, and
searching.

 The searching of record has been made quite simple as all the
details of the customer can be obtained by simply keying in the
identification of that customer.

 Similarly, record maintenance and updation can also be

accomplished by using the identification of the customer with all
the details being automatically generated. These details are
also being promptly automatically updated in the master file
thus keeping the record absolutely up-to-date.

 The entire information has maintained in the database or Files

and whoever wants to retrieve can’t retrieve, only authorization
user can retrieve the necessary information which can be easily
be accessible from the file.


The main objective of the entire activity is to automate the process of

day to day.

Activities like:

 Selling activities,
 Admission of a New Customer,
 Provide Stock according to customer’s demand,
 Checkout of a computer and releasing the papers availability
 Finally compute the bill etc.
 Stock information
 Advance online bookings.
 List of Regular customers.
 Email facility.
 Feedbacks.
 PURPOSE
I have designed the given proposed system in the VB to automate the
process of papers. This project is useful for the authorities which keep track
of all the users registered in a particular state .The authority can add paper
name, paper details, availability of stock, magazines etc.

The following steps that give the detailed information of the need of
proposed system are:

Performance: During past several decades, the records are supposed to be

manually handled for all activities. The manual handling of the record is
time consuming and highly prone to error.

To improve the performance of the newspaper Management System, the

computerized system is to be undertaken. This project is fully computerized
and user friendly even that any of the members can see the report and status
of the company.

Efficiency: The basic need of this website is efficiency. The website

should be efficient so that whenever a new user submits his/her details the
website is updated automatically. This record will be useful for other users
instantly.

Control: The complete control of the project is under the hands of

authorized person who has the password to access this project and illegal
access is not supposed to deal with. All the control is under the administrator
and the other members have the rights to just see the records not to change
any transaction or entry.

Security: Security is the main criteria for the proposed system. Since
illegal access may corrupt the database. So security has to be given in this
project.

PROJECT CATEGORY
This Project is coupled with material on how to use the various tool, sub sets
available in VB AND MS-Access.
SOFTWARE DEVELOPMENT LIFE CYCLE
(SDLC)

The ultimate objective of software engineering is to produce good quality

maintainable software within reasonable time frame and at affordable cost.
This is achievable only if we have matured processes to produce it. For a
mature process, it should be possible to determine in advance how much
time, cost and effort will be required to produce the final product. This can
only be done using data from past experience, which requires that we must
measure the software process.

A key component of any software development process is the life cycle

model on which the process is based. Life cycle of the software starts from
concept exploration and ends at the retirement of the software.

The system life cycle is:

The period of time that starts when a software product is conceived and ends
when the product is no longer available for use. The software life cycle
typically includes a requirement phase, design phase, implementation phase,
test phase, installation and check out phase, operation and maintenance
phase, and sometimes retirement phase.

In this project the Spiral Model has been used

REQUIREMENT ANALYSIS & FEASIBILITY
STUDY

When we receive a request for a new software project from the customer,
first of all, we would like to understand the requirements of the project.
Requirement analysis is very important and essential activity. We analyze,
refine the gathered requirements in order to make consistent and
unambiguous requirements.

In spite of understanding the project we would also analyses whether it is

feasible in terms of cost, technical and market. If it is not feasible in any
term it will not be fruitful to develop such a project.
Initially it should also be analyzed whether the requirements for the project
(hardware and software) are affordable or feasible.

So before preceding further to the design issues here we will discuss in some
what detail the requirement analysis and the feasibility study of the project.

REQUIREMENT ANALYSIS
Requirements analysis in and software engineering, encompasses those tasks
that determines the needs or conditions to meet for a new or altered product,
taking account of the possibly conflicting requirements of the various
stakeholders, such as beneficiaries or users.

Requirements analysis is critical to the success of a development project.

Requirements must be documented, actionable, measurable, testable, related
to identified business needs or opportunities, and defined to a level of detail
sufficient for system design. Requirements can be architectural, structural,
behavioral, functional, and non-functional.

Conceptually, requirements analysis includes three types of activity:

 Eliciting requirements: the task of communicating with customers and

users to determine what their requirements are. This is sometimes also
called requirements gathering.
 Analyzing requirements: determining whether the stated requirements
are unclear, incomplete, ambiguous, or contradictory, and then
resolving these issues.
 Recording requirements: Requirements might be documented in
various forms, such as natural-language documents, use cases, user
stories, or process specifications.

FIG 3.1: REQUIREMENT ANALYSIS

 Draw the context diagram:

The context diagram is a simple model that defines the boundaries and
interfaces of the proposed system with the external world. It identifies
the entities outside the proposed system that interact with the system.

 Development of a prototype:

One effective way to find out what the customer really wants is to
construct a prototype. Prototype helps the client to visualize the
proposed system and increase the understanding of requirements.

 Model the requirements:

This process is usually consisting of various graphical representations
of the functions data entries external entities and relationship between
them. This will help us to find the incorrect inconsistent missing
requirements.

 Finalize the requirement:

After modeling the requirements now we finalize the analyzed

requirements and next step is to document these requirements.
 FEASIBILITY STUDY
A feasibility study is conducted to select the best system that meets
performance requirement. This entails an identification description, an
evaluation of candidate system and the selection of best system for the job.
The system required performance is defined by a statement of constraints,
the identification of specific system objective and a description of outputs.

The key considerations in feasibility analysis are:

1. Economic Feasibility
2. Technical Feasibility

3. Operational Feasibility

Economical Feasibility:-
It looks at the financial aspect of the project. It determines whether the
management has enough resources and budget to invest in the proposed

system and the estimated time for the recovery of cost incurred. It also
determines whether it is worthwhile to invest the money in the proposed
project. Economic feasibility is determines by the means of cost benefit
analysis. The proposed system is economically feasible because the cost
involved in purchasing the hardware and the software are within
approachable. The personal cost like salaries of employees hired are also
nominal, because working in this system need not required a highly qualified
professional. The operating-environment costs are marginal. The less time
involved also helped in its economical feasibility
Technical Feasibility:-
It is a measure of the practically of specific technical solution and the
availability of technical resources and expertise.

 The proposed system uses VISUAL BASIC 6.0as front-end and MS

ACCESS as back-end tool.
 MS ACCESS is a popular tool used to design and develop database
objects such as table views, indexes.
 The above tools are readily available, easy to work with and widely
used for developing commercial application.

Operational Feasibility:-

The system will be used if it is developed well then be resistance for users
that undetermined:
 No major training and new skills are required as it is based on
SPIRAL model.
 It will help in the time saving and fast processing and dispersal of user
request and application.
 New product will provide all the benefits of present system with better
performance.
 User involvement in the building of present system is sought to keep
in mind the user specific requirement and needs.
 User will have control over there own information. Important
information such as pay slip can be generated at the click of a button.
 Faster and systematic processing of user application approval,
allocation of IDs payments, etc. used had greater chances of error due
to wrong information entered mistake.
 SUMMARY
Here we have dealt with the requirement analysis and the feasibility study
which gives the better understanding of the project.

Requirement analysis determines the needs to be fulfilled and what the

prepared document should do after completion. For the better understanding
of the requirements we will draw the context diagram then build a prototype,
analyze the requirements and lastly finalize them.

In feasibility we analyze the feasibility of the project in terms of economic

feasibility, technical feasibility and operational feasibility.

Spiral Model:
The problem with traditional software process models is that they do not deal
sufficiently with the uncertainty, which is inherent to software project.
Important software projects have failed because project risks were neglected
and nobody was prepared when something unforeseen happened. Barry
Boehm recognized this and tried to incorporate the “Project Risk” factor into
a life cycle mode. The result is the spiral model, which was presented in
1986 [BOEH86].

The radial dimension of the model represents the cumulative costs. Each
path around the spiral is indicative of increased costs. The angular
dimension represents the progress made in completing each cycle. Each
loop of the spiral from X-axis clockwise through 360 degree represents one
phase. One phase is split roughly into four sectors of major activities:
 Planning: Determination of objectives, alternatives and constraints.
 Risk analysis: analyze alternatives and attempts to identify and resolve
the risks involved.
 Development: Product development and testing product.
 Assessment: Customer evaluation.

An important feature of the spiral model is that each phase is completed with
a review by the people concerned with the project designers and
programmers. This review consists of a review of all the products developed
up to that point and includes the plans for the next cycle. These plans may
include a partition of the product in smaller portions for development or
components plan for the development fails, and then the spiral is terminated.
Otherwise with the initiation of new or modified software.
The advantage of this model is the wide range of option to accommodate the
good features of other life cycle models. It become equivalent to another life
cycle model in appropriate situations. It also incorporates software quality
objectives into software development. The risk analysis and validation steps
eliminate errors in the early phases of development.

The spiral model has some difficulties that need to be resolved before it can
be a universally applied life cycle model. These difficulties include lack of
explicit process guidance in determining objectives, constraints, alternatives;
relying on risk assessment expertise; and providing more flexibility than
required for many applications.

SUMMARY:
 This deal with developing good quality software with affordable
time and reasonable cost.

 We have to take a mature process to determine time and cost

required to produce the project.

 Software development life cycle is the key component of any

software development process. This encopresis a requirement phase,
design phase, implementation phase, test phase, installation and
check out phase, operation and maintenance phase and sometimes
retirement phase.

 Here Spiral Model has been used because it includes the Risk
Management along with other phases used with other traditional
software.

 Each phase of Spiral model consists of Planning, Risk analysis,

Development, Assessment sectors.

 The problem with this model includes lack of explicit process

guidance in determining objectives, constraints, relying on risk
management expertise.
REQUIREMENT SPECIFICATION

HARDWARE: - Processor (Intel core processor above Pentium IV)

RAM (512 MB)
HARD DISK (1GB)

SOFTWARE: - WINDOWS 7

FRONT END: - VISUAL BASIC 6.0

BACK END: - MS ACCESS

 FRONT END

WHAT IS VISUAL BASIC 6.0?

Visual Basic is a generation event and integrated development
environment (IDE) from Microsoft for its COM programming
model first released in 1991 and declared legacy in 2008. Microsoft
intended Visual Basic to be relatively easy to learn and use. Visual
Basic was derived from BASIC and enables the rapid application
development (RAD) of graphical user interface (GUI) applications,
access to databases using Data Access Objects,, Remote Data
Objects, or ActiveX Data Objects, and creation of ActiveX controls
and objects.

The final release was version 6 in 1998 (now known simply as

Visual Basic). On April 8, 2008 Microsoft stopped supporting
Visual Basic 6.0 IDE. The Microsoft Visual Basic team still
maintains compatibility for Visual Basic 6.0 applications on
Windows Vista, Windows Server 2008 including R2, Windows 7,
Windows 8, Windows 8.1, Windows Server 2012 and Windows 10
through its "It Just Works" program. In 2014 there were tens of
thousands of developers who still prefer Visual Basic 6.0 over
Visual Basic .NET. In 2014 some developers lobbied for a new
version of Visual Basic 6.0. A dialect of Visual Basic, Visual Basic
for Applications (VBA), is used as a macro or scripting language
within several Microsoft applications.
 BACK-END

WHAT IS MS- ACCESS?

Microsoft Access is a DBMS (also known as Database

Management System) from Microsoft that combines the relational
Microsoft with a graphical user interface and software-
development tools. It is a member of the Microsoft Office suite of
applications, included in the Professional and higher editions or
sold separately.

Microsoft Access stores data in its own format based on the Access
Jet Database Engine. It can also import or link directly to data
stored in other applications and databases.

Software developers and data architects can use Microsoft Access

to develop application software, and "power users" can use it to
build software

applications. The Microsoft® Access Database is made up of 7

major components:
 Tables
 Relationships
 Queries
 Forms
 Reports
 Macros
 SYSTEM DESIGN :-

After gathering the requirements and determining that the proposed system is
technically feasible, we will move further towards the designing issues.
Here the main goal is to transform the requirements specification into a
structure that is suitable for implementation in some programming language.
Here we determine the individual’s constraints to be used further as per
requirements. These constraints are than mapped into Data Flow diagrams
(DFD) & Entity Relationship Diagram(ER-Diagram).

Data Flow Diagram:-

A data-flow diagram (DFD) is a graphical representation of the "flow"

of data through an information system. DFDs can also be used for the
visualization of data processing (structured design).
Data flow diagrams (DFDs) are the method of choice over technical
descriptions for three principal reasons.

(1)DFDs are easier to understand by technical and nontechnical

audiences.

(2) DFDs can provide a high level system overview, complete

with boundaries and connections to other systems.

(3) DFDs can provide a detailed representation of system components.

DFDs help system designers and others during initial analysis stages
visualize a current system or one that may be necessary to meet new
requirements. Systems analysts prefer working with DFDs, particularly
when they require a clear understanding of the boundary between
existing systems and postulated systems. DFDs represent the following:

1. External devices sending and receiving data

2. Processes that change that data
3. Data flows themselves
4. Data storage locations
0 Level DFD: A level 0 DFD, also called a fundamental system model or
context diagram represents the entire software element as a single bubble
with input and output data indicated by incoming and outgoing arrows,
respectively.

 A data flow diagram shows the logical flows of data through a

transaction processing system of an organization.

 They are primarily used in the systems development process as a too

for analyzing an existing system.

(1)Level DFD: This level of DFD provides more detailed structure. It

provides a detailed view of requirements and flow of data from 1 bubble to
another.

Data Flow:-

 Data move in specific direction from an origin to a destination in the

form of a document.

Process:-
 Procedures or devices that use or transform data.
Source or Destination of Data:-
 Source or Destination of data, which may be people, organization or
other entities, interact with the system but are outside its boundary.

Data Store:-
 A Data Store referenced by a process in the system.
 Context Diagram

O-LEVEL :-

NEWSPAPER
USER management DATABASE
system
 DFD diagram for NEWSPAPER
management
I-LEVEL :-

ENTITY RELATIONSHIP DIAGRAM:-

NEWSPAPER
MANAGENT
ID
USER
ID/PASSWORD ID/PASSWORD
SYSTEM
ID/PASSWORD
MDI
password

S
FORMS

PAPER DETAIL

MAGAZINE DETAIL

CUSTOMER DETAIL REPORT

SALES DETAIL

BILL RECEIPT
ENTITY RELATIONSHIP DIAGRAM:-

The entity relationship model is a high level data model. It is based on a

perception of a real world that consists of a collection of basic objects, called
entities, and of relationship among these objects. It was developed to
facilitate database design by allowing specification of an enterprise schema,
which represent the overall logical structure of a database.

Entities-relationship analysis uses three major abstractions to

describe data.
1) Entity: An entity is an object that has its existence in the real world. It

includes all those “things” about which data is collected. An entity may be a
tangible object such as a student, a place or a part. It may also be non-
tangible such as an event, a job title or a customer account. For example, if
we say that a customer buys goods, it means customer and goods are entities.

Diagrammatically, entities are represented in rectangles

2) Attributes: Attributes are units that describe the characteristics or

properties of entities. In a database, entities are represented by tables and
attributes by columns. For example, a customer entity might have numerous
attributes such as code, name and addresses. Similarly, the goods entity may
have attributes like code and price. They are drawn in elliptical shapes along
with the entity rectangles.
3) Relationship:- Relationships illustrate how two entities share
information in the database structure.

 The diagram documents the entities and relationship involved in the

employee information and payroll system.

 It depicts the fundamental relations like recording personnel

information, paying salary and getting a loan.

 The E-R Diagram for a Employee Payroll system can

An Entity Set: It is a set of entities of the same type that share the same
properties, or attributes. The set of all persons who are customers at a given
bank, example, can be defined as the entity set customer.

ER-DIAGRAM OF NEWSPAPER MANAGEMENT

SYSTEM
 LANGUAGE
DESCRIPTION

NEWSPAPER PRICE
PRICE
COVERAGE DESCRIPTION

LANGUAGE
PAPER DETAIL CONCEPTS

MAGAZINE NAME
MAGAZINE DETAIL

CUSTOMER ID ADDRESS
PAPER NAME

CUSTOMER NAME

PHONE
CUSTOMER DETAIL

LANGUAGE DESCRIPTION
PAPER NAME

PRICE/DAY

CUSTOMER DETAIL DATE OF

SALE

SALES DETAIL
PAPER NAME BILL NO.

SIGNATURE
CUSTOMER NAME
DATE OF SALE

BILL RECEIPT TOTAL AMOUNT

FORMS

LOGIN FORM

..
PROGRESS BAR FORM
WELCOME FORM
MDI FORM
ABOUT US FORM
PAPER DETAIL FORM
MAGAZINE DETAIL FORM
CUSTOMER DETAIL FORM
SALES DETAIL FORM
BILL RECEIPT FORM
CONTACT US
EXIT FORM
PAPER DETAIL VIEW AND TABLE
MAGAZINE DETAIL VIEW AND TABLE
CUSTOMER DETAIL VIEW AND TABLE
SALES DETAIL VIEW AND TABLE

SALES DEATIL VIEW AND

TABLE

SALES DEATIL VIEW AND

TABLE

SALES DEATIL VIEW AND

TABLE
BILL RECEIPT VIEW AND TABLE
PAPER DETAIL REPORT
MAGAZINE DETAIL REPORT
CUSTOMER DETAIL REPORT
SALES DETAIL REPORT
BILL RECEIPT REPORT
CODING
 LOGIN FORM

Private Sub Command1_Click()

If Text1.Text = "ROSHNI SONI" Then

If Text2.Text = "ROS913101" Then

Form2.Show

Me.Hide

Else

MsgBox "wrong password", vbInformation, " message"

End If
 PROGRESS BAR

Private Sub Timer1_Timer()

pb1.Value = pb1.Value + 1

If pb1.Value >= 40 And pb1.Value <= 60 Then

Label1.Caption = "project is loaded....." & pb1.Value & "%"

ElseIf pb1.Value >= 60 And pb1.Value <= 80 Then

Label1.Caption = "database is connecting....." & pb1.Value & "%"

ElseIf pb1.Value >= 100 Then

Form3.Show

Unload Me

Else

Label1.Caption = pb1.Value & "%"

End If

End Sub

WELCOME TABLE

Private sub command1_click()

MDIform1.show

End Sub
 MDI FORM

Private Sub A_Click()

Form4.Show

End Sub

Private Sub B_Click()

Form5.Show

End Sub

Private Sub C_Click()

Form6.Show

End Sub

Private Sub D_Click()

Form7.Show

End Sub

Private Sub E_Click()

Form8.Show

End Sub

Private Sub F_Click()

Form9.Show

End Sub

Private Sub G_Click()

Form10.Show

End Sub

Private Sub I_Click()

Form12.Show

End Sub
Private Sub J_Click()

Datareport1.Show

End Sub

Private Sub K_Click()

Datareport2.Show

End Sub

Private Sub L_Click()

Datareport3.Show

End Sub

Private Sub M_Click()

Datareport4.Show

End Sub

Private Sub N_Click()

Datareport5.show

End Sub
 PAPER DETAIL

Private Sub Command1_Click()

Adodc1.Recordset.AddNew

End Sub

Private Sub Command2_Click()

Adodc1.Recordset.Update

End Sub

Private Sub Command3_Click()

Adodc1.Recordset.Update

End Sub

Private Sub Command4_Click()

Adodc1.Recordset.Delete

End Sub

Private Sub Command5_Click()

MDIForm1.Show

End Sub

Private Sub Command6_Click()

DataReport1.Show

End Sub
 MAGAZINE DETAIL

Private Sub Command1_Click()

Adodc1.Recordset.AddNew

End Sub

Private Sub Command2_Click()

Adodc1.Recordset.Update

End Sub

Private Sub Command3_Click()

Adodc1.Recordset.Update

End Sub

Private Sub Command4_Click()

Adodc1.Recordset.Delete

End Sub

Private Sub Command5_Click()

MDIForm2.Show

End Sub

Private Sub Command6_Click()

DataReport2.Show

End Sub
 CUSTOMER DETAIL

Private Sub Command1_Click()

Adodc1.Recordset.AddNew

End Sub

Private Sub Command2_Click()

Adodc1.Recordset.Update

End Sub

Private Sub Command3_Click()

Adodc1.Recordset.Update

End Sub

Private Sub Command4_Click()

Adodc1.Recordset.Delete

End Sub

Private Sub Command5_Click()

MDIForm3.Show

End sub

Private Sub Command6_Click()

DataReport3.Show

End Sub
 SALES DETAIL

Private Sub Command1_Click()

Adodc1.Recordset.AddNew

End Sub

Private Sub Command2_Click()

Adodc1.Recordset.Update

End Sub

Private Sub Command3_Click()

Adodc1.Recordset.Update

End Sub

Private Sub Command4_Click()

Adodc1.Recordset.Delete

End Sub

Private Sub Command5_Click()

MDIForm4.Show

End sub

Private Sub Command6_Click()

DataReport4.Show

End Sub
 BILL RECEIPT

Private Sub Command1_Click()

Adodc1.Recordset.AddNew

End Sub

Private Sub Command2_Click()

Adodc1.Recordset.Update

End Sub

Private Sub Command3_Click()

Adodc1.Recordset.Update

End Sub

Private Sub Command4_Click()

Adodc1.Recordset.Delete

End Sub

Private Sub Command5_Click()

MDIForm5.Show

End Sub

Private Sub Command6_Click()

DataReport5.Show

End Sub
 THANKYOU

Private sub command1_click()

End

End Sub
DATABASE:-

Data base is used to store the relevant information of the individuals. A

database is a collection of rows and columns in which rows indicate the tuple
and column indicates the domain of table.
In database management system, a file that defines the basic organization of
a database A data dictionary contains a list of all files in the database, the
number of records in each file, and the names and types of each fields. Most
database management systems keep the data dictionary hidden from users to
prevent them from accidentally destroying its contents.
Data Dictionary
A metadata or data dictionary is the data about the data .It is the self-
describing nature of the database that provides program-data
independence. It is also called as the SYSTEM CATALOG. It holds
the following information about each data element in the databases, it
normally include:

 Name
 Type
 Range of values
 Source
 Access authorization
 Indicates which application programs use the data so that, when
a change in a data structure is contemplated, a list of the
affected programs can be generated.

Data dictionary is used to actually control the database

operation, data integrity and accuracy. Metadata is used by
developers to develop the programs, queries, controls and
procedures to manage the data. Metadata is available to
database administrators (DBAs), designers and authorized user
as on-line system documentation. This improves the control of
database administrator (DBAs) over the information system and
the user’s understanding and use of the system. There are two
types of data dictionary:-
 ACTIVE
 PASSIVE
 DATA REPORT

Report data can come from multiple sources of data in your organization. Your
first step in designing a report is to create data sources and datasets that
represent the underlying report data. Each data source includes data
connection information. Each dataset includes a query command that defines
the set of fields to use as data from a data source. To visualize data from each
dataset, add a data region, such as a table, matrix, chart, or map. When the
report is processed, the queries run on the data source, and each data region
expands as needed to display the query results for the dataset.

Terms
 Data connection. Also known as a data source. A data connection
includes a name and connection properties that are dependent on the
connection type. By design, a data connection does not include
credentials. A data connection does not specify which data to retrieve
from the external data source. To do that, you specify a query when you
create a dataset.
 Data source definition. A file that contains the XML representation of
a report data source. When a report is published, its data sources are
saved on the report server or SharePoint site as data source definitions,
independently from the report definition. For example, a report server
administrator might update the connection string or credentials. On a
native report server, the file type is .rds. On a SharePoint site, the file
type is .rsds.
 Connection string. A connection string is a string version of the
connection properties that are needed to connect to a data source.
Connection properties differ based on data connection type. For
examples, see Data Connections, Data Sources, and Connection Strings
in Report Builder.
 Shared data source. A data source that is available on a report server
or SharePoint site to be used by multiple reports.
 Embedded data source. Also known as a report-specific data source. A
data source that is defined in a report and used only by that report.
 TESTING

Importance of software Testing

on software cannot be underestimated. Software testing is a fundamental
component of software The importance of software testing and its impact
quality assurance and represents a review of specification, design and
coding. The greater visibility of software system and the code associated
with software failure are motivating factors for planning, through testing. It
is not uncommon for a software organization to spent 40% of its efforts on
testing.

Software Testing Fundamentals

During testing the software engineering produces a series of test cases that
are used to “rip apart” the software they have produced. Testing is the one
step in the software process that can be seen by the developer as destructive
instead of constructive. Software engineers are typically constructive people
and testing requires them to overcome preconceived concepts of correctness
and deal with conflicts when errors are identified.

System Testing
System testing is the expensive and time-consuming process. There are
two strategies for testing software that we use for testing our system: Code
Testing and Specification Testing. In Code testing, we developed those cases
to execute every instructions and path in the program. In specification
testing, we examined the program specification and then wrote test data to
determine how the program operates under specified condition..
Client Acceptance
Needs Testing

Requirements System
Testing

Design Integration
Testing

Code Unit Testing

 We have tested each module separately i.e. have completed unit
testing first and system testing was done after combining /linking all
different Modules with different menus and thorough testing was done.
Testing is a very important part of SDLC and takes approximately 50%of
the time.
Once the system is a live one, Maintenance phase is important. Service
after sale is a must and users/ clients must be helped after the system is
implemented. If he/she faces any problem in using the system, one or two
trained persons from developer’s side can be deputed at the client’s site,
so as to avoid any problem and if any problem occurs immediate solution
may be provided.
OVERVIEW OF TESTING
Testing: Testing involves executing the program (or part of it) using
sample data and inferring from the output whether the software performs
correctly or not. This can be done either during module development
(unit testing) or when several modules are combined (system testing).
Defect Testing: Defect testing is testing for situation where the program
does not meet its fictional specification. Performance testing tests a
system's performance or reliability under realistic loads. This may go
some way to ensuring that the program meets its non-functional
requirements.
Debugging: Debugging is a cycle of detection, location, repair and test.
Debugging is a hypothesis testing process. When a bug is detected, the
tester must form a hypothesis about the cause and location of the bug.
Further examination of the execution of the program (possible including
many returns of it) will usually take place to confirm the hypothesis. If
the hypothesis is demonstrated to be incorrect, a new hypothesis must be
formed. Debugging
tools that show the state of the program are useful for this, but inserting
print statements is often the only approach. Experienced debuggers use
their knowledge of common and/or obscure bugs to facilitate the
hypothesis testing process. After fixing a bug, the system must be reset to
ensure that the fix has worked and that no other bugs have been
introduced. This is called regression testing. In principle, all tests should
be performed again but this is often too expensive to do.
 TEST PLANNING:
Testing needs to be planned to be cost and time effective. Planning is
setting out standards for tests. Test plans set out the context in which
individual engineers can place their own work. Typical test plan contains
Overview of testing process
>Requirements trace ability (to ensure that all requirements are tested)
>List of item to be tested
>Schedule
>Recording procedures so that test results can be audited
>Hardware and software requirement.

Black Box Testing

Black box testing relates to the tests that are performed at the software
interface. Although they are designed identify errors, black box tests are
used to demonstrate that software function are operational; that inputs are
correctly accepted and the output is correctly produced. A black box test
considers elements of the system with little interest in the internal logical
arrangement of the software. White box testing of the testing involve closer
examination of procedural detail. Logical paths through the software are
considered by providing test cases that exercise particular sets of conditions
and / or loops. The status of the system can be identified at diverse points to
establish if the expected status matches the actual status.
Black box testing tries to find errors in the following categories:
1. Incorrect or missing functions,
2. Interface errors,
3. Errors in data structures or external database access,
4. Performance errors, and
5. Initialization and termination errors.
White Box Testing
White box testing is a test case design approach that Users the control
architecture of the procedural design to produce test cases. Using white box
test approaches, the software engineering can produce test cases

1. Guarantee that all independent paths in a module have been exercised

at least once.

2. Exercise all logical decisions.

3. Execute all loops at their boundaries and in their operational bounds.

Exercise internal data structures to maintain their validity.
 TESTING PROCESS

Best testing process is to test each subsystem separately, as we have done in

my project. Best done during implementation. Best done after small sub-
steps of the implementation rather than large chunks. Once each lowest
level unit has been tested, units are combined with related units and retested
in combination. This proceeds hierarchically bottom-up until the entire
system is tested as a whole. Typical levels of testing:

> Unit -procedure, function, method

> Module -package, abstract data type, class

Sub-system - collection of related modules, cluster of classes, method-

message paths

> Acceptance testing - whole system with real data (involve customer,
user, etc)Alpha testing is acceptance testing with a single client (common
for bespoke systems).

Beta testing involves distributing system to potential customers to use

and provide feedback. In, this project, Beta testing has been followed
.This exposes system to situations and errors that might not be
anticipated by us.
 SYSTEM IMPLEMENTATION

The final phase of the process is the implementation of the new system. This
phase is the fulmination of the previous phase and will be performed only
after each of the phases has been successfully completed to the satisfaction
of both the users and quality assurance. The task which comprises the
implementation phase includes the installation of the hardware, proper
scheduling of the resource needed to production of a complete structure that
supports both the user and the environment and the necessary documentation
to move the program and the file in to production.

1. Hardware installation
2. Scheduling / Resources requirement
3. User instruction / Procedure
4. Turnover documentation / certification reviews.
The reviews will cover all the documentation that has been generated for the
product. In particular the review will examine the certification checklist to
ensure it has completed and will compare this checklist to project
documentation to ensure that all necessary items have been developed in
addition to the certificates checklist item, the reviewed to determine they are
correct.

1. Program names and libraries

2. Operation documentation
3. Source code documentation
4. Test results
 FUTURE SCOPE :-

It may help collecting perfect management in details. In a

very short time, the collection will be obvious, simple and
sensible. It will help a person to know the management of
passed year perfectly and vividly. It also helps in current all
works relative to NEWS. It will be also reduced the cost of
collecting management & collection procedure will go on
smoothly. The present project has been developed to meet
the aspirations indicated in the modern age. An attempt has
been made through this project to do all work ease & fast. It
provides current add, update, move next, move previous,
move last, find & delete all facilities to accomplish the
desired objectives. The facility include in this project and
the suggested activities have been organized to impart
knowledge & develop skill & attitude in the news official
work.
 CONCLUSION

THIS PROJECT IS DESIGNED TO MEET THE

REQUIREMENT NEWSPAPER MANAGEMENT
SYSTEM. NEWSPAPER HAVE A GENERAL
AND WIDE APPEAL. IT IS VERY COMMON
METHOD OF PUBLICITY. NEWSPAPER IS
FLEXIBLE AND TIMELY. REPEAT
ADVERTISING IS POSSIBLE. PERIODICAL
CHANGE IN SIZE AND CONTENTS IS ALSO
EASY. SELECTIVE ADVERTISING CAN BE
ESTIMATED BY HAVING KEYED
ADVERTISEMENT, NEWSPAPER OFFER
PROMOTIONAL ASSITANCE. COLOURED AND
ATTRACTIVE ADVERTISEMENTS ARE NOW
AVAILABLE EVEN IN NEWSPAPERS.THE ARE
BEST SOURCE OF MARKET INFORMATION.
 BIBLOGRAPHY

 Reference book(Ashish Tiwari, M.H.Hande,Pragrya)

 Website
 www.google.com
 www.wikipedia.com