Project Report Transactions Monitoring System

CONTENTS

1) INTRODUCTION

 ABSTRACT
 INTRODUCTION TO Transactions Monitoring System
 PURPOSE OF THE PROJECT
 PROBLEM IN EXISTING SYSTEM
 SOLUTION OF THESE PROBLEMS

2) PROJECT ANALYSIS
 STUDY OF THE SYSTEM
 HARDWARE & SOFTWARE SPECIFICATIONS
 INPUT & OUTPUT
 PROCESS MODELS USED WITH JUSTIFICATION

3) SELECTED SOFTWARE

4) SOFTWARE REQUIRMENT SPECIFICATION

 FUNCIONAL REQUIREMENTS
 PERFORMANCE REQUIREMENTS

5) PROJECT DESIGN
 NEW SYSTEM DESIGN
 DATA FLOW DIAGRAMS

6) OUTPUT SCREENS

7) PROJECT TESTING
 COMPILING TEST
 EXECUTION TEST
 OUTPUT TEST

7) FUTURE IMPROVEMENT

9) CONCLUSION

10) BIBLOGRAPHY

1
Project Report Transactions Monitoring System

INTRODUCTON

2
Project Report Transactions Monitoring System

1.1 ORGANISATIONAL PROFILE:

Meeting the critical needs of companies worldwide for realistic software

services is INFOKEY's mandate. INFOKEY has demonstrated its capabilities to deliver
high levels of quality and productivity leading to unmatched values in software services.
Empowering the IT initiatives of organizations in Japan and the world over.

INFOKEY brings to software services the collective experience of working on

global projects across hardware platforms, operating systems, development tools and
emerging technologies.

Global Outlook:

We have constantly refined our project management capabilities to match the

business processes of the established names in the retail, manufacturing, services and
financial sectors.
Today our customers include companies like Denso Corporation, Nagoya;
NEC, Chubu; Central Computer Services, Tokyo; SeigyaJoho, Tokyo.

Global Presence:
Expect INFOKEY to take on your most challenging software services
requirement, no matter where you are. INFOKEY has software development centers at
Bangalore, India and Nagoya, Japan.
And you can access our expertise through business partners in USA, UK and
the Far_ East.

3
Project Report Transactions Monitoring System

The Right Partner For Your Internet-Initiatives:

Internet is redefining the way companies interact with customers, employees
and vendors. More importantly, the Internet has triggered the need to maximize
efficiencies through company's intranet, extranet and entire digital information decision
support systems. INFOKEY works with companies to implement comprehensive IT
initiatives that can bring unmatched efficiencies in the business operations boost the
service levels and dramatically increase the productivity. Reducing the costs, all along
the value chain.

INFOKEY's through understanding of global standards in quality, project

management and delivery have met the expectations of Japanese industry majors,
among others. A combination of ready-to-deploy skills processes and focused project
orientation ensures that our services are operational when you need them.

Realizing the Clicks and Mortar Paradigm:

It means a whole range of web orientations at various levels,in various
phases.INFOKEY has a solid understanding of business processes in the light of web
technologies. Our services range from developing web applications to implementing a
complete Internet strategy.

The Web-Services include:

Website Design,Development and Hosting
Interactive Websites with Database Integration
E-Commerce Enabled Websites
Web-enabling Existing Application
Innovative Web Applications

4
Project Report Transactions Monitoring System

Software Development Services:

INFOKEY ensures higher productivity and minimal improvement of your
resources through its dedicated software development centers.Monitoring through high
speed communication links and comprehensive testing methodology,ensure alignment
with the project objectives.

IT-enabled Services:
Working across time-zones enables 24 hour,7 day production and
support.INFOKEY can work out the right outsourcing strategy to realize this.And bring
about significant savings on the internal data-processing costs.

Professional IT-Services:
Professionals at INFOKEY offer specialized services from on-site
consulting,process-analysis and technical support to Internet based application
development.

Porting and Maintenance Services:

INFOKEY offers services on porting projects and databases and legacy-
applications maintenance.

Business on the Internet:

Building a competitive Internet position calls for wide range of skills that can
accelerate your Internet responsiveness.INFOKEY's skill-set enables you to implement
an Internet-strategy in compressed time-frames on a continuos basis. Be it multimedia
intensive application or transaction intensive database management.While a company
can focus on finding new ways to provide value and service to their
customers,INFOKEY brings the domain knowledge and technical experience to put the
power of the Internet on your IT initiative.

5
Project Report Transactions Monitoring System

PROBLEM ANALYSIS

6
Project Report Transactions Monitoring System

Objective

The proposed Sales information System is totally focusing on cement production

units.The main objective of this system is to provide ease system to the end user by
which there will be timely delivery of goods to the customer, sales analysis can be easily
done.

Document Scope

The scope of this document is to present the detailed description of the project with the
objectives, this document covers all the requirements of a sales information system
typically in a cement production units.

Problem Overview

This describes about the problem when this system doesn’t exists, each and every
process such as order entry, order approval, sending of orders to branches, Invoice
Generation & Dispatching of goods, Calculation of profit and stock maintenance. All the
mentioned processes should be done manually. To overcome these problems a web-
based solution for sales information system is proposed by which all the manual
process can be automated.

System Overview

To overcome the above problem and to provide a better solution for the same, this sales
information system is proposed, this system is a web-based and centralized by which
entire information regarding Corporate, Regional office & Branch offices Plants, stock
point office (SPO) can be accessed from anywhere.
This application basically covers Order Fulfillment, Stock Maintenance and
Pricing, Invoicing functionalities and Access Control Levels.

7
Project Report Transactions Monitoring System

Order fulfillment this function will provide options for entering orders &
Dispatching the orders.

Stock Maintenance this function looks after the stock, updates stock depending
on plants production, stock at stock point office, stock adjustments due to various
reasons such as damage in goods sent etc.

Pricing & Invoicing in this function preparation of invoice from either plant / stock
point offices. Here all options for generating invoices such as Price, Freight,
Handling Charges … etc., are provided.

Access control level function will control the entire application by restricting access to

unauthorized users and maintains security to the system.

REQUIREMENTS ANALYSIS DOCUMENT

Hierarchy of Organization accessing Sales Information System

The following figure shows a hierarchical structure of the industry

and the flow in sales information system. This figure also represents the Access
Controls at each level. Under a corporate office there will be different regional
offices. Under each regional office there are some branches where in the orders
are processed at this level as well as regional office level.

8
Project Report Transactions Monitoring System

Corporate Office

Regional Office 1 Regional Office 2 Regional Office 3

Branch Office 1 Branch Office 2 Branch Office 3

District 1 District 2

Stockist/Customer Stockist/Customer

Hierarchy of Organization accessing sales information system

Context Flow of Sales Information System

The following figure represents context flow of sales information system,

Computerization of the system up to Branches i.e., only the functionalities represented
with computer picture are presently proposed for Automation. The initial start up of the
sales information system depends on the orders, which are brought by the sales
representatives in the corresponding districts. The system starts with the entry of order
details.

Marketing persons will get orders or Customer might request for goods, all the
orders from marketing will be sent to corresponding branch offices for approval,

9
Project Report Transactions Monitoring System

in branches all the verification process will be carried out and the orders will be
approved or Unapproved or sent to Regional office for approval. Dispatch of
goods will be done on approved orders either from Plant or Stock Point Office
(SPO).

Get orders
M arketing/Sales
Customer/Stockist
Representative
Request for
goods
Invoice
generation &
despatch

PLANT / DEPOT Branch Office

Approved
Orders

Approved by
RO
Regional Office

Proposed Automation of the System

Context Flow of Sales Information System

The functionalities included in the Sales Information System
1. Order Fulfillment Process:
Orders will be taken by Sales representatives from Stockiest /Customer in their
corresponding districts and they will send the orders to Branch offices. In Branch office
the orders will be accepted basing on the previous details of the customer/ stockist, i.e.,
there will be some credit limits for each customer/stockist and while order acceptance
credit limit will be checked if the amount for the ordered quantity exceeds the limit given
to customer/stockist then that order will be sent to Regional office otherwise the order
will be sent to Plant Or SPO for dispatch.
The orders from Regional office can be either approved or can be rejected, all the
approved orders will be sent to Plant Or SPO for dispatch.

10
Project Report Transactions Monitoring System

SOFTWARE REQUIREMENT
SPECIFICATION

11
Project Report Transactions Monitoring System

INTRODUCTION

Purpose: The main purpose for preparing this document is to give a general insight into
the analysis and requirements of the existing system or situation and for determining the
operating characteristics of the system.

Scope: This Document plays a vital role in the development life cycle (SDLC)
As it describes the complete requirement of the system. It is meant for use by the
developers and will be the basic during testing phase. Any changes made to the
requirements in the future will have to go through formal change approval process.

Developers Responsibilities Overview:

The developer is responsible for:

1) Developing the system, which meets the SRS and solving all the requirements of the
system?

2) Demonstrating the system and installing the system at client's location after the
acceptance testing is successful.

3) Submitting the required user manual describing the system interfaces to work on it
and also the documents of the system.

4) Conducting any user training that might be needed for using the system.

5) Maintaining the system for a period of one year after installation.

12
Project Report Transactions Monitoring System

OUTPUT DESIGN

Outputs from computer systems are required primarily to communicate the

results of processing to users. They are also used to provides a permanent copy of the
results for later consultation. The various types of outputs in general are:

 . External Outputs, whose destination is outside the organisation.

 . Internal Outputs whose destination is with in organisation and they are the
 user’s main interface with the computer.
 . operational outputs whose use is purely with in the computer department.
 . Interface outputs, which involve the user in communicating directly with

Output Definition

The outputs should be defined in terms of the following points:

. Type of the output

. Content of the output
. Format of the output
Location of the output
.Frequency of the output
.Volume of the output
.Sequence of the output

It is not always desirable to print or display data as it is held on a

computer. It should be decided as which form of the output is the most suitable.

For Example
. Will decimal points need to be inserted
. should leading zeros be suppressed.

13
Project Report Transactions Monitoring System

Output Media:

In the next stage it is to be decided that which medium is the most appropriate
for the output. The main considerations when decideing about the output media are:

.The suitability for the device to the particular application.

.The need for a hard copy.
.The response time required.
.The location of the users
.The software and hardware available.
The cost.

Keeping in view the above description the project is to have outputs

mainly coming under the category of internal outputs. The main outputs desired
according to the requirement specification are:

The outputs were needed to be generated as a hot copy and as well as queries to be
viewed on the screen. Keeping in view these outputs, the format for the output is taken
from the outputs, which are currently beeing obtained after manual processing. The
standard printer is to be used as output media for hard copies.

INPUT DESIGN

Input design is a part of overall system design. The main objective during the input
desing is as given below:

 To produce a cost-effective method of input.

 To achive the highest possible level of accuracy.
 To ensure that the input is acceptable and understood by the user.

14
Project Report Transactions Monitoring System

INPUT STAGES:

The main input stages can be listed as below:

 Data recording
 Data transcription
 Data conversion
 Data verification
 Data control
 Data transmission
 Data validation
 Data correction

15
 Project Report Transactions Monitoring System

TRANSACTION MONITORING
SYSTEM

DATA DICTIONARY

Table: USERS

COLUMN NAME DATA TYPE CONSTRAINT

ID NUMBER PRIMARY KEY
LOGINID VARCHAR2(20) UNIQUE
PASSWORD VARCHAR2(20) NOT NULL
PERSONNAME VARCHAR2(40)
TYPE VARCHAR2(22)
LINKID NUMBER NOT NULL

Table: STATES

COLUMN NAME DATA TYPE CONSTRAINT

STATEID NUMBER PRIMARY KEY
NAME VARCHAR2(30) UNIQUE

Table: BRANCHES

COLUMN NAME DATA TYPE CONSTRAINT

BRANCHID NUMBER PRIMARY KEY
NAME VARCHAR2(30) UNIQUE
STATEID NUMBER REFERENCES STATES(STATEID)
ADDRESS VARCHAR2(200)
PIN VARCHAR2(6)
PHONE VARCHAR2(18)
EMAIL VARCHAR2(50)

16
 Project Report Transactions Monitoring System

Table: COMPANIES

COLUMN NAME DATA TYPE CONSTRAINT

COMPANYID NUMBER PRIMARY KEY
NAME VARCHAR2(30) UNIQUE
TYPE VARCHAR2(10)
ADDRESS VARCHAR2(400)
STATEID NUMBER REFERENCES STATES(STATEID)
PINZIP VARCHAR2(15)
PHONE VARCHAR2(18)

Table: CUSTOMERS

COLUMN NAME DATA TYPE CONSTRAINT

CUSTOMERID NUMBER PRIMARY KEY
NAME VARCHAR2(30) UNIQUE
ADDRESS VARCHAR2(500)
STATE VARCHAR2(30)
PINZIP VARCHAR2(30)
LANDPHONE VARCHAR2(30)
CELLPHONE VARCHAR2(20)
FAX VARCHAR2(30)
EMAIL VARCHAR2(50)

Table: SPO

COLUMN NAME DATA TYPE CONSTRAINT

SPOID NUMBER PRIMARY KEY
NAME VARCHAR2(30) UNIQUE
ADDRESS VARCHAR2(300)
PHONE VARCHAR2(18)

17
 Project Report Transactions Monitoring System

Table: PRODUCTS

COLUMN NAME DATA TYPE CONSTRAINT

PRODUCTID NUMBER PRIMARY KEY
NAME VARCHAR2(30) UNIQUE
BRAND VARCHAR2(30)
GRADE VARCHAR2(25)
PRICE NUMBER(17,2)

Table: SALESREP

COLUMN NAME DATA TYPE CONSTRAINT

SALREPID NUMBER PRIMARY KEY
NAME VARCHAR2(30) UNIQUE
COMPANYID NUMBER REFERENCES COMPANIES(COMPANYID)
ADDRESS VARCHAR2(400)
LANDPHONE VARCHAR2(20)
CELLPHONE VARCHAR2(12)
EMAIL VARCHAR2(100)

Table: FREIGHT

COLUMN NAME DATA TYPE CONSTRAINT

FREIGHTID NUMBER PRIMARY KEY
NAME VARCHAR2(30) UNIQUE
CHARGES NUMBER(17,2)

Table: ORDERS

COLUMN NAME DATA TYPE CONSTRAINT

ORDERID NUMBER PRIMARY KEY
BRANCHID NUMBER REFERENCES BRANCHES(BRANCHID)
PRODUCTID NUMBER REFERENCES PRODUCTS(PRODUCTID)
SALREPID NUMBER REFERENCES SALESREP(SALREPID)
CUSTOMERID NUMBER REFERENCES CUSTOMERS(CUSTOMERID)
ORDERDATE DATE
STATUS VARCHAR2(30)
QUANTITY NUMBER(17,2)
PRICE NUMBER(17,2)
TOTALAMOUNT NUMBER(17,2)

18
 Project Report Transactions Monitoring System

Table: DELIVERYSCHEDULES

COLUMN NAME DATA TYPE CONSTRAINT

ORDERID NUMBER
FREIGHTID NUMBER REFERENCES FREIGHT(FREIGHTID)
ADDRESS VARCHAR2(500)
QUANTITY NUMBER(17,2)
PRICE NUMBER(17,2)
TOTAL NUMBER(17,2)
DELIVERYDATE VARCHAR2(14)
ISDELIVERED VARCHAR2(5)

Table: DELIVERY

COLUMN NAME DATA TYPE CONSTRAINT

ORDERID NUMBER UNIQUE
DELIVERYDATE DATE
HANDLINGCHARGES NUMBER(17,2)
DISCOUNT NUMBER(17,2)
SALESTAX NUMBER(17,2)
EXCISEDUTY NUMBER(17,2)
SPOID NUMBER REFERENCES SPO(SPOID)

Table: STOCKLOSS

COLUMN NAME DATA TYPE CONSTRAINT

ID NUMBER PRIMARY KEY
SALREPID NUMBER REFERENCES SALESREP(SALREPID)
PRODUCTID NUMBER REFERENCES PRODUCTS(PRODUCTID)
BRANCHID NUMBER REFERENCES BRANCHES(BRANCHID)
LOSSDATE DATE
QUANTITY NUMBER(17,2) NOT NULL
NOTES VARCHAR2(400)
STATUS VARCHAR2(20)

19
 Project Report Transactions Monitoring System

Table: PRODUCTION

COLUMN NAME DATA TYPE CONSTRAINT

SPOID NUMBER REFERENCES SPO(SPOID)
PRODUCTID NUMBER REFERENCES PRODUCTS(PRODUCTID)
QUANTITY NUMBER(17,2)
PRODUCTIONDATE DATE

Table: SPOTRANSFER

COLUMN NAME DATA TYPE CONSTRAINT

SOURCESPOID NUMBER REFERENCES SPO(SPOID)
DESTINATIONSPOID NUMBER REFERENCES SPO(SPOID)
PRODUCTID NUMBER REFERENCES PRODUCTS(PRODUCTID)
TRANSFERDATE DATE
QUANTITY NUMBER(17,2)

INPUT TYPES;

It is necessary to determine the various types of inputs. Inputs can be categorised

as follows :

 External inputs, which are prime inputs for the system.

 Internal inputs, which are user communications with the system.
 Operational, which are computer department’s communications to the
system.
 Interactive, which are inputs entered during a dialogue.

20
Project Report Transactions Monitoring System

INPUT MEDIA :

At this stage choice has to be made about the input media. To conclude about the
input media consideration has to be given to;

 Type of input
 Flexibility of format
 Speed
 Accuracy
 Verification methods
 Rejection rates
 Ease of correction
 Storage and handling requirements
 Security
 Easy to use
 Portabilility

Keeping in view tha baove description of the input types and input media, it can
be said that most of the inputs are of the form of internal and interactive. As
Input data is to be the directly keyed in by the user, the keyboard can be considered to
be the most suitable input device.

ERROR AVOIDANCE

At this stage care is to be taken to ensure that input data remains accurate form
the stage at which it is recorded upto the stage in which the data is accepted by the
system. This can be achieved only by means of careful control each time the data is
handled.

21
Project Report Transactions Monitoring System

SELECTED SOFTWARE

22
Project Report Transactions Monitoring System

Microsoft.NET Framework
The .NET Framework is a new computing platform that simplifies application
development in the highly distributed environment ofthe Internet. The .NET Framework
is designed to fulfill the following objectives:

 To provide a consistent object-oriented programming environment whether object

code is stored and executed locally, executed locally but Internet-distributed, or
executed remotely.
 To provide a code-execution environment that minimizes software deployment
and versioning conflicts.
 To provide a code-execution environment that guarantees safe execution of
code, including code created by an unknown or semi-trusted third party.
 To provide a code-execution environment that eliminates the performance
problems of scripted or interpreted environments.
 To make the developer experience consistent across widely varying types of
applications, such as Windows-based applications and Web-based applications.
 To build all communication on industry standards to ensure that code based on
the .NET Framework can integrate with any other code.

The .NET Framework has two main components: the common language runtime and
the .NET Framework class library. The common language runtime is the foundation of
the .NET Framework. You can think of the runtime as an agent that manages code at
execution time, providing core services such as memory management, thread
management, and remoting, while also enforcing strict type safety and other forms of
code accuracy that ensure security and robustness. In fact, the concept of code
management is a fundamental principle of the runtime. Code that targets the runtime is
known as managed code, while code that does not target the runtime is known as
unmanaged code. The class library, the other main component of the .NET Framework,
is a comprehensive, object-oriented collection of reusable types that you can use to
develop applications ranging from traditional command-line or graphical user interface

23
Project Report Transactions Monitoring System

(GUI) applications to applications based on the latest innovations provided by

ASP.NET, such as Web Forms and XML Web services.

The .NET Framework can be hosted by unmanaged components that load the common
language runtime into their processes and initiate the execution of managed code,
thereby creating a software environment that can exploit both managed and
unmanaged features. The .NET Framework not only provides several runtime hosts, but
also supports the development of third-party runtime hosts.

For example, ASP.NET hosts the runtime to provide a scalable, server-side

environment for managed code. ASP.NET works directly with the runtime to enable
Web Forms applications and XML Web services, both of which are discussed later in
this topic.

Internet Explorer is an example of an unmanaged application that hosts the runtime (in
the form of a MIME type extension). Using Internet Explorer to host the runtime enables
you to embed managed components or Windows Forms controls in HTML documents.
Hosting the runtime in this way makes managed mobile code (similar to Microsoft®
ActiveX® controls) possible, but with significant improvements that only managed code
can offer, such as semi-trusted execution and secure isolated file storage.

The following illustration shows the relationship of the common language runtime and
the class library to your applications and to the overall system. The illustration also
shows how managed code operates within a larger architecture.

Features of the Common Language Runtime

The common language runtime manages memory, thread execution, code execution,
code safety verification, compilation, and other system services. These features are
intrinsic to the managed code that runs on the common language runtime.

With regards to security, managed components are awarded varying degrees of trust,
depending on a number of factors that include their origin (such as the Internet,

24
Project Report Transactions Monitoring System

enterprise network, or local computer). This means that a managed component might or
might not be able to perform file-access operations, registry-access operations, or other
sensitive functions, even if it is being used in the same active application.

The runtime enforces code access security. For example, users can trust that an
executable embedded in a Web page can play an animation on screen or sing a song,
but cannot access their personal data, file system, or network. The security features of
the runtime thus enable legitimate Internet-deployed software to be exceptionally
feature rich.

The runtime also enforces code robustness by implementing a strict type- and code-
verification infrastructure called the common type system (CTS). The CTS ensures that
all managed code is self-describing. The various Microsoft and third-party language
compilers

Generate managed code that conforms to the CTS. This means that managed code can
consume other managed types and instances, while strictly enforcing type fidelity and
type safety.

In addition, the managed environment of the runtime eliminates many common software
issues. For example, the runtime automatically handles object layout and manages
references to objects, releasing them when they are no longer being used. This
automatic memory management resolves the two most common application errors,
memory leaks and invalid memory references.

The runtime also accelerates developer productivity. For example, programmers can
write applications in their development language of choice, yet take full advantage of the
runtime, the class library, and components written in other languages by other
developers. Any compiler vendor who chooses to target the runtime can do so.
Language compilers that target the .NET Framework make the features of the .NET
Framework available to existing code written in that language, greatly easing the
migration process for existing applications.

25
Project Report Transactions Monitoring System

While the runtime is designed for the software of the future, it also supports software of
today and yesterday. Interoperability between managed and unmanaged code enables
developers to continue to use necessary COM components and DLLs.

The runtime is designed to enhance performance. Although the common language

runtime provides many standard runtime services, managed code is never interpreted.
A feature called just-in-time (JIT) compiling enables all managed code to run in the
native machine language of the system on which it is executing. Meanwhile, the
memory manager removes the possibilities of fragmented memory and increases
memory locality-of-reference to further increase performance.

Finally, the runtime can be hosted by high-performance, server-side applications, such

as Microsoft® SQL Server™ and Internet Information Services (IIS). This infrastructure
enables you to use managed code to write your business logic, while still enjoying the
superior performance of the industry's best enterprise servers that support runtime
hosting.

.NET Framework Class Library

The .NET Framework class library is a collection of reusable types that tightly integrate
with the common language runtime. The class library is object oriented, providing types
from which your own managed code can derive functionality. This not only makes the
.NET Framework types easy to use, but also reduces the time associated with learning
new

features of the .NET Framework. In addition, third-party components can integrate

seamlessly with classes in the .NET Framework.

For example, the .NET Framework collection classes implement a set of interfaces that
you can use to develop your own collection classes. Your collection classes will blend
seamlessly with the classes in the .NET Framework.

26
Project Report Transactions Monitoring System

As you would expect from an object-oriented class library, the .NET Framework types
enable you to accomplish a range of common programming tasks, including tasks such
as string management, data collection, database connectivity, and file access. In
addition to these common tasks, the class library includes types that support a variety of
specialized development scenarios. For example, you can use the .NET Framework to
develop the following types of applications and services:

 Console applications.
 Scripted or hosted applications.
 Windows GUI applications (Windows Forms).
 ASP.NET applications.
 XML Web services.
 Windows services.

For example, the Windows Forms classes are a comprehensive set of reusable types
that vastly simplify Windows GUI development. If you write an ASP.NET Web Form
application, you can use the Web Forms classes.

Client Application Development

Client applications are the closest to a traditional style of application in Windows-based

programming. These are the types of applications that display windows or forms on the
desktop, enabling a user to perform a task. Client applications include applications such
as word processors and spreadsheets, as well as custom business applications such as
data-entry tools, reporting tools, and so on. Client applications usually employ windows,
menus, buttons, and other GUI elements, and they likely access local resources such
as the file system and peripherals such as printers.

Another kind of client application is the traditional ActiveX control (now replaced by the
managed Windows Forms control) deployed over the Internet as a Web page. This
application is much like other client applications: it is executed natively, has access to
local resources, and includes graphical elements.

27
Project Report Transactions Monitoring System

In the past, developers created such applications using C/C++ in conjunction with the
Microsoft Foundation Classes (MFC) or with a rapid application development (RAD)
environment such as Microsoft® Visual Basic®. The .NET Framework incorporates
aspects of these existing products into a single, consistent development environment
that drastically simplifies the development of client applications.

The Windows Forms classes contained in the .NET Framework are designed to be used
for GUI development. You can easily create command windows, buttons, menus,
toolbars, and other screen elements with the flexibility necessary to accommodate
shifting business needs.

For example, the .NET Framework provides simple properties to adjust visual attributes
associated with forms. In some cases the underlying operating system does not support
changing these attributes directly, and in these cases the .NET Framework
automatically recreates the forms. This is one of many ways in which the .NET
Framework integrates the developer interface, making coding simpler and more
consistent.

Unlike ActiveX controls, Windows Forms controls have semi-trusted access to a user's
computer. This means that binary or natively executing code can access some of the
resources on the user's system (such as GUI elements and limited file access) without
being able to access or compromise other resources. Because of code access security,
many applications that once needed to be installed on a user's system can now be
safely deployed through the Web. Your applications can implement the features of a
local application while being deployed like a Web page.

Introduction to Windows Forms (C#.NET)

Windows Forms is the new platform for Microsoft Windows application development,
based on the .NET Framework. This framework provides a clear, object-oriented,
extensible set of classes that enable you to develop rich Windows applications.
Additionally, Windows Forms can act as the local user interface in a multi-tier distributed
solution. Windows Forms is a framework for building Windows client applications that

28
Project Report Transactions Monitoring System

utilize the common language runtime. Windows Forms applications can be written in
any language that the common language runtime supports.

What Is a Form?

A form is a bit of screen real estate, usually rectangular, that you can use to present
information to the user and to accept input from the user. Forms can be standard
windows, multiple document interface (MDI) windows, dialog boxes, or display surfaces
for graphical routines. The easiest way to define the user interface for a form is to place
controls on its surface. Forms are objects that expose properties, which define their
appearance, methods, which define their behavior, and events, which define their
interaction with the user. By setting the properties of the form and writing code to
respond to its events, you customize the object to meet the requirements of your
application.

As with all objects in the .NET Framework, forms are instances of classes. The form you
create with the Windows Forms Designer is a class, and when you display an instance
of the form at run time, this class is the template used to create the form. The
framework also allows you to inherit from existing forms to add functionality or modify
existing behavior. When you add a form to your project, you can choose whether it
inherits from the Form class provided by the framework, or from a form you have
previously created.

Additionally, forms are controls, because they inherit from the Control class.

Within a Windows Forms project, the form is the primary vehicle for user interaction. By
combining different sets of controls and writing code, you can elicit information from the
user and respond to it, work with existing stores of data, and query and write back to the
file system and registry on the user's local computer.

Although the form can be created entirely in the Code Editor, it is easier to use the
Windows Forms Designer to create and modify forms.

29
Project Report Transactions Monitoring System

Some of the advantages of using Windows Forms include the following:

 Simplicity and power: Windows Forms is a programming model for

developing Windows applications that combines the simplicity of the Visual
Basic 6.0 programming model with the power and flexibility of the common
language runtime.
 Lower total cost of ownership: Windows Forms takes advantage of the
versioning and deployment features of the common language runtime to offer
reduced deployment costs and higher application robustness over time. This
significantly lowers the maintenance costs (TCO) for applications written in
Windows Forms.
 Architecture for controls: Windows Forms offers an architecture for controls
and control containers that is based on concrete implementation of the control
and container classes. This significantly reduces control-container
interoperability issues.
 Security: Windows Forms takes full advantage of the security features of the
common language runtime. This means that Windows Forms can be used
implement everything from an untrusted control running in the browser to a
fully trusted application installed on a user's hard disk.
 XML Web services support: Windows Forms offers full support for quickly
and easily connecting to XML Web services.
 Rich graphics: Windows Forms is one of the first ship vehicles for GDI+, a
new version of the Windows Graphical Device Interface (GDI) that supports
alpha blending, texture brushes, advanced transforms, rich text support, and
more.
 Flexible controls: Windows Forms offers a rich set of controls that
encompass all of the controls offered by Windows. These controls also offer
new features, such as "flat look" styles for buttons, radio buttons, and check
boxes.
 Data awareness: Windows Forms offers full support for the ADO data model.

30
Project Report Transactions Monitoring System

 ActiveX control support: Windows Forms offers full support for ActiveX
controls. You can easily host ActiveX controls in a Windows Forms
application. You can also host a Windows Forms control as an ActiveX
control.
 Licensing: Windows Forms takes advantage of the common language
runtime enhanced licensing model.
 Printing: Windows Forms offers a printing framework that enables
applications to provide comprehensive reports.
 Accessibility: Windows Forms controls implement the interfaces defined by
Microsoft Active Accessibility (MSAA), which make it simple to build
applications that support accessibility aids, such as screen readers.
 Design-time support: Windows Forms takes full advantage of the meta-data
and component model features offered by the common language runtime to
provide thorough design-time support for both control users and control
implementers.

ACTIVE X DATA OBJECTS.NET

ADO.NET Overview

ADO.NET is an evolution of the ADO data access model that directly addresses user
requirements for developing scalable applications. It was designed specifically for the
web with scalability, statelessness, and XML in mind.

ADO.NET uses some ADO objects, such as the Connection and Command objects,
and also introduces new objects. Key new ADO.NET objects include the DataSet,
DataReader, and DataAdapter.

The important distinction between this evolved stage of ADO.NET and previous data
architectures is that there exists an object -- the DataSet -- that is separate and distinct
from any data stores. Because of that, the DataSet functions as a standalone entity.
You can think of the DataSet as an always disconnected recordset that knows nothing

31
Project Report Transactions Monitoring System

about the source or destination of the data it contains. Inside a DataSet, much like in a
database, there are tables, columns, relationships, constraints, views, and so forth.

A DataAdapter is the object that connects to the database to fill the DataSet. Then, it
connects back to the database to update the data there, based on operations performed
while the DataSet held the data. In the past, data processing has been primarily
connection-based. Now, in an effort to make multi-tiered apps more efficient, data
processing is turning to a message-based approach that revolves around chunks of
information. At the center of this approach is the DataAdapter, which provides a bridge
to retrieve and save data between a DataSet and its source data store. It accomplishes
this by means of requests to the appropriate SQL commands made against the data
store.

The XML-based DataSet object provides a consistent programming model that works
with all models of data storage: flat, relational, and hierarchical. It does this by having no
'knowledge' of the source of its data, and by representing the data that it holds as
collections and data types. No matter what the source of the data within the DataSet is,
it is manipulated through the same set of standard APIs exposed through the DataSet
and its subordinate objects.

While the DataSet has no knowledge of the source of its data, the managed provider
has detailed and specific information. The role of the managed provider is to connect,
fill, and persist the DataSet to and from data stores. The OLE DB and SQL Server .NET
Data Providers (System.Data.OleDb and System.Data.SqlClient) that are part of the
.Net Framework provide four basic objects: the Command, Connection, DataReader
and DataAdapter. In the remaining sections of this document, we'll walk through each
part of the DataSet and the OLE DB/SQL Server .NET Data Providers explaining what
they are, and how to program against them.

The following sections will introduce you to some objects that have evolved, and some
that are new. These objects are:

32
Project Report Transactions Monitoring System

 Connections. For connection to and managing transactions against a

database.
 Commands. For issuing SQL commands against a database.
 DataReaders. For reading a forward-only stream of data records from a SQL
Server data source.
 DataSets. For storing, remoting and programming against flat data, XML data
and relational data.
 DataAdapters. For pushing data into a DataSet, and reconciling data against
a database.

When dealing with connections to a database, there are two different options: SQL
Server .NET Data Provider (System.Data.SqlClient) and OLE DB .NET Data Provider
(System.Data.OleDb). In these samples we will use the SQL Server .NET Data
Provider. These are written to talk directly to Microsoft SQL Server. The OLE DB .NET
Data Provider is used to talk to any OLE DB provider (as it uses OLE DB underneath).

Connections

Connections are used to 'talk to' databases, and are respresented by provider-specific
classes such as SQLConnection. Commands travel over connections and resultsets
are returned in the form of streams, which can be read by a DataReader object, or
pushed into a DataSet object.

Commands

Commands contain the information that is submitted to a database, and are represented
by provider-specific classes such as SQLCommand. A command can be a stored
procedure call, an UPDATE statement, or a statement that returns results. You can also
use input and output parameters, and return values as part of your command syntax.
The example below shows how to issue an INSERT statement against the Northwind
database.

33
Project Report Transactions Monitoring System

DataReaders

The DataReader object is somewhat synonymous with a read-only/forward-only cursor

over data. The DataReader API supports flat as well as hierarchical data. A
DataReader object is returned after executing a command against a database. The
format of the returned DataReader object is different from a recordset. For example,
you might use the DataReader to show the results of a search list in a web page.

DataSets and DataAdapters

DataSets
The DataSet object is similar to the ADO Recordset object, but more powerful, and
with one other important distinction: the DataSet is always disconnected. The DataSet
object represents a cache of data, with database-like structures such as tables,
columns, relationships, and constraints. However, though a DataSet can and does
behave much like a database, it is important to remember that DataSet objects do not
interact directly with databases, or other source data. This allows the developer to work
with a programming model that is always consistent, regardless of where the source
data resides. Data coming from a database, an XML file, from code, or user input can all
be placed into DataSet objects. Then, as changes are made to the DataSet they can be
tracked and verified before updating the source data. The GetChanges method of the
DataSet object actually creates a second DatSet that contains only the changes to the
data. This DataSet is then used by a DataAdapter (or other objects) to update the
original data source.

The DataSet has many XML characteristics, including the ability to produce and
consume XML data and XML schemas. XML schemas can be used to describe
schemas interchanged via Web Services. In fact, a DataSet with a schema can actually
be compiled for type safety and statement completion.

34
Project Report Transactions Monitoring System

Data Adapters (OLEDB/SQL)

The DataAdapter object works as a bridge between the DataSet and the source data.
Using the provider-specific SqlDataAdapter (along with its associated SqlCommand
and SqlConnection) can increase overall performance when working with a Microsoft
SQL Server databases. For other OLE DB-supported databases, you would use the
OleDbDataAdapter object and its associated OleDbCommand and OleDbConnection
objects.

The DataAdapter object uses commands to update the data source after changes have
been made to the DataSet. Using the Fill method of the DataAdapter calls the
SELECT command; using the Update method calls the INSERT, UPDATE or DELETE
command for each changed row. You can explicitly set these commands in order to
control the statements used at runtime to resolve changes, including the use of stored
procedures. For ad-hoc scenarios, a CommandBuilder object can generate these at
run-time based upon a select statement. However, this run-time generation requires an
extra round-trip to the server in order to gather required metadata, so explicitly providing
the INSERT, UPDATE, and DELETE commands at design time will result in better run-
time performance.

1. ADO.NET is the next evolution of ADO for the .Net Framework.

2. ADO.NET was created with n-Tier, statelessness and XML in the forefront.
Two new objects, the DataSet and DataAdapter, are provided for these
scenarios.
3. ADO.NET can be used to get data from a stream, or to store data in a cache
for updates.
4. There is a lot more information about ADO.NET in the documentation.
5. Remember, you can execute a command directly against the database in order
to do inserts, updates, and deletes. You don't need to first put data into a
DataSet in order to insert, update, or delete it.
6. Also, you can use a DataSet to bind to the data, move through the data, and
navigate data relationships

35
Project Report Transactions Monitoring System

PROJECT DESIGN

36
Project Report Transactions Monitoring System

Design Document
System Design Document

SCOPE
A multi step process that focusses on the data structures, software
architecture, interface representation and procedural details of the project.

OBJECTIVE
To translate the requirements into a representation of the software that can be
accessed for quality before code generation begins.

ENVIRONMENT DESIGN

ASSUMPTIONS

For system deveopment the following hardware/software setups should be

avaliable.

Hard ware Configurations

 Two computer with pentium 3 and min. 128 RAM for client
(development)
 One machine for server (pentium 3 with min 256 RAM)

Software configurations for server machine

 .Net 2003
 Sql Server 2000
 IIS(Web Browser)

Software configurations for client machines

 .Net FrameWork 1.1
 Sql Server 2000 Client

HARDWARE/SOFTWARE DETAILS

Hard ware Configurations

 Two computer with pentium 3 and min. 128 RAM for client
(development)
 One machine for server (pentium 3 with min 128 RAM)

37
Project Report Transactions Monitoring System

Software configurations for client machine

 Sql Server 2000 Client

Software configurations for server machine

 .Net 2003
 Sql Server 2000
 IIS(Web Browser)

APPLICATION SECURITY

 Options should be given to only authorized users.

 Data access to the screen should depend on the user logged into the
system.
 Data Access should depend on the ACL functionality mentioned above.

38
Project Report Transactions Monitoring System

FUNCTIONAL DESIGN

FUNCTIONAL HIERARCHY
Orders from customers
to sales
representatives/
Order Entry marketing,
Stock Transfer from
SPO

Order Approval

Order Stock
Processing Management

Customer request for

Goods, SPO request for
Goods Transfer , Stock
Order Dispatch & Adjustments
Invoice

Order fulfillment this function will provide options for entering orders &
Dispatching the orders.

Stock Maintenance this function looks after the stock, updates stock depending
on plants production, stock at stock point office, stock adjustments due to various
reasons such as damage in goods sent etc.

Pricing & Invoicing in this function preparation of invoice from either plant / stock
point offices. Here all options for generating invoices such as Price, Freight,
Handling Charges … etc., are provided.

39
Project Report Transactions Monitoring System

APPLICATION ARCHITECTURE

Basing on the above details the application will be developed using the 3-tier
architecture, the following figure shows an overview of the application architecture

Client Tier Domain Server Database Server

Oracle
Database

Shared
Component
JSP, Oracle
Inte r tired Servlet & Application
EJB server
Intra tired

Application architecture of SIS

DEPENDENCIES AND CONSTRAINTS

The order entries will be input for Branch Logistics in DSS, order processing &
source for dispatch will be identified here in DSS.

DSS system depends on this system (SIS) for Orders. And SIS depends on DSS
at Order processing functionality.

40
Project Report Transactions Monitoring System

Data Base Design

Master Tables
LOCATIONS (DESTINATION/CUSTOMER) TABLE

TABLE NAME: -CUSTOMER_DETAILS

# FIELD NAME DATA TYPE LENGTH COMMENTS
1 CUST_ ID VARCHAR2 10 PRIMARY KEY
2 CUST_NAME VARCHAR2 80 NOT NULL
3 CUST_ADDR VARCHAR2 500 NOT NULL
4 STATE VARCHAR2 20 NOT NULL
5 GSTNO VARCHAR2 25
6 CSTNO VARCHAR2 25
7 APPTDT DATE
8 CANCDT DATE
9 DOCKETNO VARCHAR2 15
10 CREDIT_LIMIT NUMBER
11 SD_BAL NUMBER 12,2
12 PIN_ZIP VARCHAR2 25
13 CONTACT_NUMBER VARCHAR2 50
14 FAX VARCHAR2 25
15 EMAIL VARCHAR2 50
PRIMARY KEY: - CUST_ID

TABLE NAME: - PROD_DETAILS

# FIELD NAME DATA TYPE LENGTH COMMENTS
1 PROD_CODE NUMBER 2 NOT NULL
2 PROD_NAME VARCHAR2 10 NOT NULL
3 BRAND_CODE NUMBER 2 NOT NULL
4 BRAND_NAME VARCHAR2 25 NOT NULL
5 GRADE_CODE NUMBER 2 NOT NULL
6 PACK_CODE NUMBER 2 NOT NULL
7 PRICE NUMBER 30 NOT NULL

PRIMARY KEY: - PROD_CODE

STATES TABLE

TABLE NAME: - STATE_REC

# FIELD NAME DATA TYPE LENGTH COMMENTS
1 S TATE _CODE NUMBER 2 NOT NULL
2 STATE_NAME VARCHAR2 20 NOT NULL
PRIMARY KEY: - STATE_CODE

41
Project Report Transactions Monitoring System

BRANCHES TABLE

TABLE NAME: - BRANCH_REC

# FIELD NAME DATA TYPE LENGTH COMMENTS
1 BRANCH_CODE NUMBER 2 NOT NULL
2 BRANCH_NAME VARCHAR2 30
3 BRANCH_ADD1 VARCHAR2 30
4 BRANCH_ADD2 VARCHAR2 30
5 BRANCH_ADD3 VARCHAR2 30
6 PIN_CODE NUMBER 6
7 PHONE NUMBER 12
PRIMARY KEY: - BRANCH_CODE

TABLE NAME: COMPANY_DETAILS

# FIELD NAME DATA TYPE LENGTH COMMENTS
1 COMP_ID NUMBER 2 NOT NULL
2 NAME VARCHAR2 30
3 TYPE CHAR 1 CHECK TYPE IN (‘R’,’B’,’P’)
4 ADDRESS VARCHAR2 30
5 STATE VARCHAR2 30 FK REF STATE(STATE_REC)
6 PIN_CODE NUMBER 6
7 PHONE NUMBER 12
PRIMARY KEY: - COMP_ID

SPO MASTER TABLE

TABLE NAME: - SPO_REC

# FIELD NAME DATA TYPE LENGTH COMMENTS
1 SPO_CODE NUMBER 2 NOT NULL
2 SPO_NAME VARCHAR2 30
3 SPO_ADD1 VARCHAR2 30
4 SPO_ADD2 VARCHAR2 30
5 SPO_ADD3 VARCHAR2 30
6 PIN_CODE NUMBER 6
7 PHONE NUMBER 12
PRIMARY KEY: - SPO_CODE

TABLE NAME: - CUST_REC

# FIELD NAME DATA TYPE Length COMMENTS
1 CUSTCODE NUMBER 38 NOT NULL
2 CUSTNAME VARCHAR2 50 NOT NULL
3 CUSTSTAT CHAR 1
4 GSTNO VARCHAR2 25
5 CSTNO VARCHAR2 25
6 APPTDT DATE

42
Project Report Transactions Monitoring System

7 CANCDT DATE
8 DOCKETNO VARCHAR2 15
9 CREDIT_LIMIT NUMBER
10 CREDIT_DAYS NUMBER 3
11 SD_BAL NUMBER 12,2
12 CUST_FLAG CHAR 1
13 PIN_ZIP VARCHAR2 25
17 CONTACT_NUMBER VARCHAR2 50
18 FAX VARCHAR2 25
19 EMAIL VARCHAR2 50
PRIMARY KEY:- CUSTCLS, CUSTCODE

Sales Representatives

TABLE NAME: - SALES_REP_REC

# FIELD NAME DATA TYPE LENGTH COMMENTS
1 SALES_REP_CODE VARCHAR2 5 NOT NULL
2 SALES_REP_NAME VARCHAR2 40 NOT NULL
3 DIST_CODE NUMBER 4 NOT NULL FK REF
DIST_CODE(COMP_ DETAILS)
4 ORIGIN NUMBER 1 NOT NULL
5 STREET VARCHAR2 50
6 ADDRESS1 VARCHAR2 50
7 ADDRESS2 VARCHAR2 50
8 PIN_ZIP VARCHAR2 25
9 CONTACT_NO VARCHAR2 50
10 FAX VARCHAR2 25
11 EMAIL VARCHAR2 50

PRIMARY KEY:- SALES_REP_CODE

Valid Users

TABLE NAME: - PASSWORD_MASTER

# FIELD NAME DATA TYPE LENGTH COMMENTS
1 USER_ID CHAR 6 NOT NULL
2 USER_NAME VARCHAR2 40 NOT NULL
3 PASSWORD VARCHAR2 12 NOT NULL
4 EFFECT_DATE DATE NOT NULL
5 OFFICE CHAR 3 NOT NULL (C, B, R, S, P)
6 ACCESS CHAR 1 (Y/N)
PRIMARY KEY:- USER_ID

43
Project Report Transactions Monitoring System

TABLE NAME: - FREIGHT_DETAILS

# FIELD NAME DATA TYPE LENGTH COMMENTS
1 DIST_CODE NUMBER 4 UNIQUE FK REF
DIST_CODE(CUST_DETAILS)
2 F_TYPE CHAR 2 CHECK IN (‘R’,’T’,’O’)
2 FROM_SOURCE CHAR 3 NOT NULL
3 MKT_FRT NUMBER 9,2 NOT NULL
4 MKT_FRT_CHANGES NUMBER 9,2 NOT NULL
5 EFF_DATE DATE NOT NULL
6 TO_EFFDT DATE NOT NULL
PRIMARY KEY:- DIST_CODE

SALES TAX TABLE

TABLE NAME: - GST_REC

# FIELD NAME DATA TYPE LENGTH COMMENTS
1 TAX_CODE NUMBER 2 NOT NULL
2 TAX_NAME VARCHAR2 30 NOT NULL
3 TAX_TYPE CHAR 1 NOT NULL
4 TAX_VALUE NUMBER 5,2 NOT NULL
5 FROM_EFFDT DATE NOT NULL
6 TO_EFFDT DATE NOT NULL
7 STATE_CODE NUMBER 2 NOT NULL
PRIMARY KEY:- TAX_CODE, STATE_CODE, TAX_TYPE, FROM_EFFDT, TO_EFFDT

EXCISE DUTY TABLE

TABLE NAME: - ED_REC

# FIELD NAME DATA TYPE LENGTH COMMENTS
1 ED_CODE NUMBER 2 NOT NULL
2 ED_NAME VARCHAR2 30 NOT NULL
3 ED_TYPE CHAR 1 NOT NULL
4 ED_VALUE NUMBER 5,2 NOT NULL
5 FROM_EFFDT DATE NOT NULL
6 TO_EFFDT DATE NOT NULL
PRIMARY KEY :- ED_CODE
CASH DISCOUNT TABLE

TABLE NAME: - CASH_DISCOUNT_PROVN

# FIELD NAME DATA TYPE LENGTH COMMENTS
1 DIST_CODE NUMBER 4 NOT NULL
2 BRAND_CODE NUMBER 2 NOT NULL
3 FROM_DATE DATE NOT NULL
4 TO_DATE DATE NOT NULL
5 DISC_PER_BAG NUMBER 9,2 NOT NULL
PRIMARY KEY :- DIST_CODE, BRAND_CODE, FROM_DATE, TO_DATE

44
Project Report Transactions Monitoring System

GENERAL DISCOUNT TABLE

TABLE NAME: - GENERAL_DISCOUNT_PROVN
# FIELD NAME DATA TYPE LENGTH COMMENTS
1 DIST_CODE NUMBER 4 NOT NULL
2 BRAND_CODE NUMBER 2 NOT NULL
3 FROM_DATE DATE NOT NULL
4 TO_DATE DATE NOT NULL
5 DISC_PER_BAG NUMBER 9,2 NOT NULL
PRIMARY KEY :- DIST_CODE, BRAND_CODE, FROM_DATE, TO_DATE
INCENTIVE DISCOUNT TABLE

TABLE NAME: - INCENTIVE_PROVN

# FIELD NAME DATA TYPE LENGTH COMMENTS
1 DIST_CODE NUMBER 4 NOT NULL
2 BRAND_CODE NUMBER 2 NOT NULL
3 FROM_DATE DATE NOT NULL
4 TO_DATE DATE NOT NULL
5 INC_PER_BAG NUMBER 9,2 NOT NULL
PRIMARY KEY :- DIST_CODE, BRAND_CODE, FROM_DATE, TO_DATE

PRICE DIFFERENCE DISCOUNT TABLE

TABLE NAME: - PRICE_DIFF_PROVN

# FIELD NAME DATA TYPE LENGTH COMMENTS
1 DIST_CODE NUMBER 4 NOT NULL
2 FROM_DATE DATE NOT NULL
3 TO_DATE DATE NOT NULL
4 PD_PER_BAG NUMBER 9,2 NOT NULL
5 BRAND_CODE NUMBER 2 NOT NULL
PRIMARY KEY :- DIST_CODE

HANDLING CHARGES TABLE

TABLE NAME: - SPO_HANDLING_DIVERSION

# FIELD NAME Data Type LENGTH COMMENTS
1 SPO_CODE NUMBER 3 NOT NULL
2 FROM_DATE DATE NOT NULL
3 TO_DATE DATE
4 ROAD_EXP NUMBER 9,2
5 RAIL_EXP NUMBER 9,2
6 ROAD_DIV NUMBER 9,2
7 RAIL_DIV NUMBER 9,2
PRIMARY KEY :- SPO_CODE

45
Project Report Transactions Monitoring System

ORDER ENTRY TABLE

TABLE NAME: - ORDER_REC

# Field name DATA TYPE LENGTH COMMENTS
1 ORDER_NO NUMBER 7 NOT NULL
2 BRANCH_CODE NUMBER 2 NOT NULL FK REF
BRANCH_CODE(BANCH_REC)
3 ORDER_DATE DATE NOT NULL
4 CUSTCLS NUMBER 2 NOT NULL
5 CUSTCODE NUMBER 5 NOT NULL
6 DEPO_CODE NUMBER 2 NOT NULL
7 PROD_CODE NUMBER 2 NOT NULL
8 PACK_CODE NUMBER 2 NOT NULL
9 BRAND_CODE NUMBER 2 NOT NULL
10 GRADE_CODE NUMBER 2 NOT NULL
11 SALES_REP_CODE VARCHAR2 5 NOT NULL
12 ORDER_REF VARCHAR2 25
13 ORDER_REF_DT DATE
14 ORD_QTY NUMBER 12,2
15 ALTD_QTY NUMBER 9,3
16 DESP_QTY NUMBER 9,3
17 RATE_MT NUMBER 9,3
18 ORD_STATUS NUMBER 2
19 BL_ASSIGNED_QTY NUMBER 9,3
20 CANCEL_DATE DATE
PRIMARY KEY:- ORDER_NO

TABLE NAME: - ORDER_REC_DELIVERY_SCHEDULE

# FIELD NAME DATA TYPE Length COMMENTS
1 BRANCH_CODE NUMBER 2 NOT NULL FK REF
BRANCH_CODE(BANCH_REC)
2 ORDER_NO NUMBER 7 NOT NULL FK REF
ORDER_NO(ORDER_REC)
3 ORDER_DATE DATE NOT NULL
4 DELIVERY_SCH_NO NUMBER 7 NOT NULL
5 DELIVERY_NAME VARCHAR2 50
6 DELIVERY_ADD1 VARCHAR2 50
7 DELIVERY_DESTINATIO NUMBER 6 NOT NULL
8 DELIVERY_DISTRICT NUMBER 4 NOT NULL
9 DELIVERY_QTY NUMBER 9,3 NOT NULL
10 DELIVERY_SCHEDULE_ DATE NOT NULL
DATE
11 BL_ASSIGN_FLAG CHAR 1
PRIMARY KEY:- DELIVERY_SCH_NO

46
Project Report Transactions Monitoring System

BRANCH LOGISTICS

TABLE NAME: - BRANCH_LOGISTICS_ASSIGNMENT

# FIELD NAME DATA TYPE Length COMMENTS
1 BRANCH_CODE NUMBER 2 UNIQUE,FK REF
BRANC_CODE(BRANCH_REC)
2 ORDER_NO NUMBER 7 NOT NULL FK REF
ORDER_NO(ORDER_REC)
3 ORDER_DATE DATE NOT NULL
4 DELIVERY_SCH_NO NUMBER 7 NOT NULL
5 ASSIGNMENT_NO NUMBER 7 NOT NULL
6 ASSIGNMENT_DATE DATE NOT NULL
7 PLANT_SPO_FLAG CHAR 1 NOT NULL
8 PLANT_SPO_CODE NUMBER 2 NOT NULL
9 ASSIGNMENT_QTY NUMBER 9,3 NOT NULL
10 ASSIGNMENT_MODE NUMBER 1 NOT NULL
11 DISPATCH_DATE DATE NOT NULL
12 DELIVERY_SCH_DATE DATE
13 PL_ASSIGNMENT_QTY NUMBER 9,3
14 RELMEMO_FLAG CHAR 1
15 BOOKED_TIME CHAR 8
16 CONT_CODE NUMBER 3
PRIMARY KEY:- BRANCH_CODE

SPO STOCK CALCULATION

TABLE NAME: - INVENTORY_DETAILS

# FIELD NAME DATA TYPE LENGTH COMMENTS
1 PRODUCT_ ID VARCHAR 20 FK PROD_CODE(PRODUCT_DETAILS)
2 DATE DATE
3 OPENING_STOCK NUMBER 80
4 STOCK_OUTWARD NUMBER 80
5 CLOSING_STOCK NUMBSER 80
6 SPO_CODE NUMBER 3 NOT NULL
7 PLANT_SPO_FLAG CHAR 1 P/S
8 FROM_PLANT_SPO NUMBER 2 NOT NULL
9 RECEIPT_NO NUMBER 6
10 RECEIPT_DATE DATE
11 RECEIVED_QTY NUMBER 9,3
12 SOUND NUMBER 9,3
13 DAMAGED NUMBER 9,3
14 LOSSIN_TRANSIT NUMBER 9,3
15 MODE NUMBER 1 1 ROAD, 2 RAIL

47
Project Report Transactions Monitoring System

INVOICE DETAILS

TABLE NAME: - INVOICE_DETAILS

# FIELD NAME DATA TYPE LENGTH COMMENTS
1 INVOICE_NO NUMBER 6 NOT NULL
2 ORDER_NO NUMBER 7 NOT NULL FK REF
ORDER_NO(ORDER_REC)
3 CUSTCLS NUMBER 1
4 CUST_CODE NUMBER 3
5 DIST_CODE NUMBER 4
6 DEST_CODE NUMBER 6
7 BRANCH_CODE NUMBER 2 FK REF BRANCH_CODE(COMP_ DETAILS)
8 INVOICE_DATE DATE
9 QTY NUMBER 10,2
10 PLANT_CODE NUMBER 2
11 SPO_CODE NUMBER 2
12 INVOICE_AMOUNT NUMBER 10,2
PRIMARY KEY:- INVOICE_NO, ORDER_NO

PROD_DATE
CUSTOMER PAYMENT DETAILS

TABLE NAME: - CUST_PAYMENTS

# FIELD NAME DATA TYPE LENGTH COMMENTS
1 CUST_CODE NUMBER 80 UNIQUE FK REF
CUST_ID(CUST_DETAILS)
2 INVOICE_NO NUMBER 7
3 AMOUNT_PAID NUMBER 10,2
4 PAYMENT_DATE DATE
5 CHEQUE_NO NUMBER 7
6 BANK_NAME VARCHAR2 25

48
Project Report Transactions Monitoring System

Introduction
The proposed Sales information System is totally focusing on cement
production units.The main objective of this system is to provide ease system to
the end user by which there will be timely delivery of goods to the customer,
sales analysis can be easily done.

Document Scope
The scope of this document is to present the detailed description of the
project with the objectives, this document covers all the requirements of a sales
information system typically in a cement production units.

Problem Overview
This describes about the problem when this system doesn’t exists, each
and every process such as order entry, order approval, sending of orders to
branches, Invoice Generation & Dispatching of goods, Calculation of profit and
stock maintenance. All the mentioned processes should be done manually. To
overcome these problems a web-based solution for sales information system is
proposed by which all the manual process can be automated.

System Overview
To overcome the above-mentioned problem and to provide a better
solution for the same, this sales information system is proposed, this
system is a web-based and centralized by which entire information
regarding Corporate, Regional office & Branch offices Plants, stock point
office (SPO) can be accessed from anywhere.
This application basically covers Order Fulfillment, Stock Maintenance and
Pricing, Invoicing functionalities and Access Control Levels.

49
Project Report Transactions Monitoring System

Context Diagram

The following figure represents context flow of sales information system,

Computerization of the system up to Branches i.e., only the functionalities
represented with computer picture are presently proposed for Automation.
The initial start up of the sales information system depends on the orders, which
are brought by the sales representatives in the corresponding districts. The
system starts with the entry of order details.

Marketing persons will get orders or Customer might request for goods, all
the orders from marketing will be sent to corresponding branch offices for
approval, in branches all the verification process will be carried out and the
orders will be approved or Unapproved or sent to Regional office for
approval. Dispatch of goods will be done on approved orders either from
Plant or Stock Point Office (SPO).

Get orders
M arketing/Sales
Customer/Stockist
Representative
Request for
goods
Invoice
generation &
despatch

PLANT / DEPOT Branch Office

Approved
Orders

Approved by
RO
Regional Office

Proposed Automation of the System

Context Flow of Sales Information System

50
Project Report Transactions Monitoring System

Business Flow Diagram

1. Order Fulfillment Process:

Orders will be taken by Sales representatives from Stockiest /Customer in their

corresponding districts and they will send the orders to Branch offices. In Branch office
the orders will be accepted basing on the previous details of the customer/ stockiest,
i.e., there will be some credit limits for each customer/stockiest and while order
acceptance credit limit will be checked if the amount for the ordered quantity exceeds
the limit given to customer/stockiest then that order will be sent to Regional office
otherwise the order will be sent to Plant Or SPO for dispatch.
The orders from Regional office can be either approved or can be rejected, all the

approved orders will be sent to Plant Or SPO for dispatch.

All the approved orders will be delivered by keeping track of the Vehicle details &
generating gate passes.
For this order fulfillment, information on various kinds to be maintained such as Plants,
districts, Branches, products, states, regions and etc., to fulfill this the system needs to
provide facilities to enter & stores information. And the user should be allowed to modify
the information.

The following figure shows a flow diagram for order fulfillment.

Orders from
customers to sales
representatives/
marketing

Order entry Order Approval

Stock
Transfer from
SPO

51
Project Report Transactions Monitoring System

Business Flow diagram for Order Fulfillment process

In order fulfillment two departments play a major role they are

1) Marketing
2) Branch logistics

Marketing: Marketing people will bring orders from stockiest/customers.

Order Entry: Here marketing department enters the details of orders. Here the system
allows multiple delivery locations for one single order.

Integration part with DSS: The order entries will be input for Branch Logistics in DSS,
order processing & source for dispatch will be identified here. Once this order is
processed & approved.
All the orders processed & approved will be input for sales information system,
i.e., the dispatch for these orders will be made from this sales information system

Plant/SPO: If the order is assigned to plant all the details of vehicles carrying the goods
are registered and gate/in pass is generated. If the order is assigned to SPO, only the
lorry number and contractor name are registered then the gate pass is generated.

Invoice: Finally plant distributor will generate the Invoice. This invoice generation will
depend on the pricing structure.

2. Stocks Maintenance

This function will keep track on the stock, provides options to record the
stock produced by a particular plant, also provides options to record stock at
Stock Point Office and regular updates on dispatch either from Plant or Stock
Point Office. The following are the functionalities

52
Project Report Transactions Monitoring System

Customer
request for
Goods

Stock
SPO request for
Updation Stock In Hand
Goods Transfer
Process

Stock
Adjustments

Business Flow for Stock Maintenance

Transfer of Goods: This is a kind of Order where the goods will be transferred from
place to Stock Point Office, here the request for transfer will between from
 Plant to Stock Point Office.
 Stock Point Office to Stock Point Office.
 Stock Point Office to stockiest.
 Plant to stockiest.

Stock Adjustments: During the transfer of goods, the stock in particular locations will
be increased or reduced. These transactions will be updated into stock details and all
the adjustments will be taken care in the system.

Loss of Stock (LOS): while goods transfer and from one location to another and
at the time of unloading there may be some loss of stock such as loss due to
damage in the packing, or missing of baggage or loosely packed or Loss on
transit i.e., abnormal loss etc. This kind of loss on stock can be recorded and
adjusted in the stocks.

53
Project Report Transactions Monitoring System

Approval on LOS: This system provides options for approving the loss of stock.
After the details of the LOS are entered into the system the approving authorities
will check and approve them.

3. Pricing Structure

This is most essential process for generating invoice on the orders. This process
involves in calculating price basing on various other factors, the pricing depends on the
following

 Freight: This is the freight charge for sending the goods to the destination this
freight differs for Rail & Road. The freight for Road & Rail will again depend on
the following routes.
o Road freight from Plant to Stock Point Office, Stock Point Office to
Stockiest, Plant to stockiest will differ
o Rail this can be only from Plant to Stock Point Office
o Diversion cost.
 Handling Charges: Changes that happen while loading & unloading of goods.

 Discounts: All the discounts given on the order to the customer/stockiest, types
of discounts are Cash, Quantity, Price difference, Incentive & General.

 Variable cost: Cost to produce a product from a particular plant.

 Packing Cost: The packing cost per ton.

 Canvassing commission: This is the discount given to Non-trade Type i.e.,

discounts on Public Parties.

 Sales Tax: This depends on the state to state.

 Excise Duty: Excise duty on the goods.

54
Project Report Transactions Monitoring System

Price for each ton will be calculated depending on the above values and the invoice
will be prepared for the dispatched goods.

Freight, Handling
Charges, Diversion
cost,Discount, Packing
Cost, Variable
Cost, Canvassing
commission, Sales Tax,
Excise Duty
(X)
Calculation Contribution /
(Y-X) Profit

Price
(Y)

Business Flow diagram for Pricing Structure

4.The Access Control Levels (ACL)

Access Control Levels, this system has total control over the options and limited access
to the options by the end users, by implementing ACL in the system no unauthorized
access can be done on the system.
There are various types of users who will access the system from various locations, to
control the access restriction for each user the system will maintain each option with a
unique identification, and each user logs into the system will be given only those options
he is allowed to access.

55
Project Report Transactions Monitoring System

SCREENS

56
Project Report Transactions Monitoring System

57
Project Report Transactions Monitoring System

58
Project Report Transactions Monitoring System

59
Project Report Transactions Monitoring System

TESTING

60
Project Report Transactions Monitoring System

TESTING

5.1 Test Plans

Testing means quality test. Testing is a process of executing a program with the intent
of finding an error. A good test case is one that has a high probability of finding an as
yet undiscovered error. Objective should be to design test that systematically uncover
different classes of error. And to do with a minimum amount of time and effort .Testing
cannot show the absence of Defects, it can only show that soft wear defects are
present. It is important to keep this statement in one of these ways knowing the specific
function that a product has been designed to perform, test can be conducted that
demonstrate each function is fully operational. This approach is called ‘blackboxtesting’.
Knowing the internal working of the product, test can be conducted to ensure that “all
gears mesh” that internal operation of the product performs according to specification
and all internal components have been adequately exercised. This Approach is call
“white box testing”.

Unit Testing:
A program unit is usually small enough that the programmer who developed it
can test it in grate detail than will be possible when the unit is integrated into an
evolving soft wear product.

Functional testing:
Specifies the operating condition, input values and expected result., The
function should be designed to take care of the situation. Performance testes-
should be designed to verify response time, execution time, throughput and
Secondary memory utilization.
Stress testing is designed to overload a system in various ways. The purpose of
the stress test is to determine the limitation of the system. Structural stress are
conducted with examining the internal processing logic of the Software system.

61
Project Report Transactions Monitoring System

System testing:

A system is tested for online responses, volume of transactions, stress Recover from
failure and usability. System testing involves two kinds of activities integration
testing and acceptance testing.

Integrated testing:

Bottom –up integration is the traditional strategy used to integrate the components of
software system into a functional who. Bottom-up integration consist of unit
testing followed by sub system testing of entire system. Unit testing has the goal
of discovering Errors in the gal of discovering errors in the individual modules fo
the systems. The primary purpose of subsystems testing is to verify operation of
the interfaces between modules in the system. System testing is concerned with
the design logic, control flow, recovery procedures, and throughput, capacity and
timing characteristics of the Entire structure.
Top-down integration starts with the main routine and or low immediate subordinated
routines in the systems structure.
System integration is distributed throughout the implementation phases:
Modules are integrated as they are developed.
Top_level interfaces are tested first.
The top-level routing provides a natural harness for low-level routines.
Errors are localized to the new modules and interfaces that are being added.
It involves planning and execution of functional tests, performance tests and

Stress tests in order to demonstrate that implemented systems satisfies its

requirements.

62
Project Report Transactions Monitoring System

Testing Types:

Black box Testing focuses on the input/output behaviour of the component. Black
box tests do not deal with the internal aspects of the component nor with the
behaviour or the structure of the component.

White box Testing focus on the internal structure of the component. A white box
test makes sure that every state in the dynamic model of the object and
interactions among the objects are tested.

Client Needs Acceptance Testing

Requirements System Testing

Design Integration Testing

Code Unit Testing

63
Project Report Transactions Monitoring System

Issues in Testing Classes:

Testing classes brings in some new issues that are not present in testing
functions. First, a class can’t be tested directly; only an instance of a class can be
tested. This means that we at least a class indirectly by testing its instances, of
the class and list them to test the class.

In Object Oriented programs, control flow is characterized by message passing

among object, and the control flow switches from one object to another by inter
object communication. Consequently there is no sequential control flow with in a
class like in functions. This lack of sequential control flow with ina class requires
different approaches for testing.

Thirdly, new issues are introduced due to inheritance. There are basically tow
reasons for problems that arise from inheritance. The structure of inheritance
hierarchy and the kind of inheritance.

Overall, testing of objects can be defined as the process of exercising the

routines provided by an object with the goal of uncovering error in the
implementation of the routines or state of the object or both.To test an object, we
have to test the interaction between the methods provided on the object. For
this, the problem for finding the patterns of method invocation of the object under
test with different arguments, which will yield errors. In some sense, by executing
various patterns, we are testing the communication between the different
methods of the object.

The state based testing approach that tests for interactions by changing that
state of the object under which the methods are tested.

64
Project Report Transactions Monitoring System

StatebasedTesting:

It is a technique to test whether or into the methods of classes interact

correctly among themselves by monitoring the data members of the class. The
testing technique is to test all the methods of a class, one bye one, against the
set of states that the object can take. If any of the features does not change the
state of the object in the expected way, then that method is declared as
containing errors.

In the state-based technique, all methods of an object are tested on at a time. A

method is invoked in all possible states that the object can assume, and after
each invocation the resulting state is checked to see whether or not the method
takes the object under atleast to the expected state.

The overall process of generating the test cases using this approach is
1.For each data member of the class under test, decide on the special value and
general value groups to specify
the domain values to be used for testing.
2.Dtermine the data scenarios for the class.
3.Augment the domain using data scenarios.
4.Add operations to set and test state values.
5.For each operation, determine which of the sates form valid inputs. There states are
to be used for testing the operations.
6.Start by testing operations at the bottom of the call graph. Each operation is tested.
7.For each state in which an operation is to be tested, determines all significant values
that an be passed as parameters. The operation is tested with each of these
parameters.

65
Project Report Transactions Monitoring System

Incremental Testing for Subclasses:

Testing each class individually when the class is part of a class hierarchy can
be wasteful as there might be an operation in a subclass that is the same as the
base class and hence might not require any testing if the base class has been
tested. In other words when testing class hierarchies, it can be wasteful to test
each class individually and separately. When a class inherits from a base class
that has been tested, testing of the sub class requires testing only some feature.
For some features no testing might be needed. It will clearly reduce the testing
effect if what features need to be tested can be clearly identified and for what
features need to be tested can be clearly identified and for what features
previous testing is sufficient i.e., just like a subclass inherits features from base
classes. It should also inherit some test history of the base class, leading to
reuse of testing history of the base class. One approach for incremental
approach of subclasses there are tow aspects to incremental testing. First is
which features of a the sub classes need to be tested and which don’t need to be
tested. The aim of the Second aspect is to reduce the effort required in selecting
test cases. It does not reduce the other activities of testing.

Testing process:
Test plan:
Testing commences with a test plan and terminated with acceptance
testing. A test plan is a general document for the entire project that defines the
scope and approach to be taken, and schedule of testing as well as identifies the
test items for the entire testing process and the personal responsible for the
different activities. Test planning can be done well before the actual testing
commences and can be done in parallel with the coding and the design phases.
The inputs for forming the test plan are

1.project plan
2.requiremetns document

66
Project Report Transactions Monitoring System

A test should contain the following:

Test unit specification: A test unit is a set of one or more modules together with
associated data, that are from a single computer program and that are the object
of testing. A test unit may be a module, a few modules or a complete system. In
this project we will perform tests on the following units.
1.Connecting to Web server.
2.Selecting the Examination.
2Validation of the Hall Ticket number
4.Selecting the Exam Marks.
5.Disconnect.

Features to be Tested:
This includes all software features and combinations of features that should be
tested. A soft features is a software characteristic specified or implied by the
requirements or design documents. These may include functionality,
performance, design constraints and attributes. In this project all the functional
features specified in the requirements documents will be tested.

67
Project Report Transactions Monitoring System

MANUAL FOR INSTALLATION OF

TRANSACTION MONITORING SYSTEM

Web Project

1. Copy “G:\Transaction Monitoring\”  “transaction” Folder into

“C:\Inetpub\wwwroot” folder.

2. Copy “G:\Transacion Monitoring\”  “transaction.dmp” file into

“C:\Oracle\Ora81\Bin” directory.

3. Create the user of oracle

 Open “SQL * Plus”

 And Enter the following commands

SQL> connect system/manager;

SQL> create user transaction identified by transactions;
SQL> grant connect, resource to transaction;

4. Import the Oracle Tables:

 Open “C:\Oracle\ora81\bin” folder through

“My Computer”
 Double Click on “IMP.EXE”
 And enter the username and password

User Name: transaction

Password: transactions

 Import File Name: transaction.dmp

 Insert buffer Size: 30000
 List contents of Import file: no
 Create error due to object existence: no

68
Project Report Transactions Monitoring System

 Import grants: yes

 Import Table data: yes
 Import Export file: yes

Note: - If there is any error in Importing the dump file, Create all the
tables manually by observing the Data Dictionary, under the following
Oracle user.

User Name: transaction

Password: transactions

5. Register the Project in IIS Server

 Click Start – Run

 Type inetmgr and press Enter
 Double Click on Computer Name (localhost)
 Double Click on Web Sites
 Double Click on “Default Web Site”
 Select the Folder “transaction”
 Right Click on “transaction” and select “Properties”.
 Click on “Create”
 Click OK.

6. Invoke the “Home Page” through Browser

 Open “Microsoft Internet Explorer” Browser.

 Type the URL

http://localhost/transaction/home.aspx

69
Project Report Transactions Monitoring System

5.2 Test Cases

Project: Sales Information Systems

Test Objective: Branches test case

S.No Test Steps Expected Results Actual Results

1 Select the region. Click All fields will be added to . All fields will be
on add button. database. added to database.

2 Select the region. Click Control goes to home Control in home

on exit button. page. page.
3 Select the region. Click Control goes to packs Control in packs
on go button. form, display the final stock form.
report.

Project: Sales Information Systems

Test Objective: Regions testcase

S.No Test Steps Expected Results Actual Results

1 Select the region. Click All fields will be added to . All fields will be
on add button. database. added to
database.
2 Select the region. Click Control goes to home Control in home
on exit button. page. page.
3 Select the region. Click Control goes to branches Control in branch
on go button. form. form.

70
Project Report Transactions Monitoring System

Project: Sales Information Systems

TestCase:Production PlantSystem

S.No Test steps Expected Results Actual Results

1 Homepage Home pagebe

Enter ValidUserid should be displayed
Valid Password.Click on displayed
submitbutton.

2 It has to show Message box

Enter valid Userid error message as appeared
Invalid Password. Click invalid password
on submitbutton.

3 New window Message box

Enter invalidUserid showing appeared
Valid password. Click on Username
submitbutton.

4 New window Message box

Enter invalid Userid showing appeared
Invalid password. Click Username
on submitbutton.

71
Project Report Transactions Monitoring System

CONCLUSION

 All the users in the organization have appreciated the project.

 It is easy to use, since it uses the GUI provided in the user dialog.
 User-friendly screens are provided.
 The usage of software increases the efficiency, decreases the effort.
 It has been thoroughly tested and implemented.
 Any endeavor is incomplete without the spirit of teamwork and the transactions
monitoring system is no different. I could not only muster up support for hosting
and fostering this project. But also gather up the enthusiastic team.

72
Project Report Transactions Monitoring System

BIBLIOGRAPHY

SOFTWARE ENGINEERING
By Roger.S. Pressman

C#. NET Black Book

By Evangeleous Petereous

MSDN 2002
By Microsoft

73