REQUIREMENT GATHERING

1. The web page (e.g. User detail page, Selected item page , etc.) will be generated
automatically according to the data in database.
2. A way in which different accounts, different proses operates in one web application.
3. A way in which the users can login to the system to perform different operation.
4. A way in which the user can modify at their data.
5. A way in which the user can generate report in same application.
6. A way in which the admin can use the system to update data to the database.
7. The system can verify the data before transaction.
8. The system can generate the new product price automatically after the price is set by the
admin or user.
9. The system can generate some statistic information according of product.

Page 1
 FEASIBILITY STUDY
Feasibility study is that phase which helps in deciding whether it would be convenient for
the client as well as the programmer to deploy the project successfully, taking into consideration
the following factors:

• OPERATIONAL FEASIBILITY:
The Website would be user friendly. It is Windows based application and hence it
becomes easy for the user to understand the functionality of the system. Also, the user
would become well suited to the system as users are highly trained computer professionals.

Visual Studio 2010 is being used for this web application. As the client is having the
knowledge to operate this, it is feasible for them.

Microsoft SQL Server 2008 is used to maintain database. Thus the user can maintain the
database as the SQL is well known to the user. Thus the software is feasible for the
operation. Thus the project is operationally feasible.

Page 2
 EXISTING SYSTEM
The existing system is manual system. Needs to be converted into automated system. Risk of
mismanagement of data. Less Security. No proper coordination between different Applications
and Users. Fewer Users - Friendly. Accuracy not guaranteed. Not in reach of distant users.
Communication between users through phone or manually.

PROPOSED SYSTEM
Motivation

Small and Medium enterprises use legacy applications to accomplish their organizational
processes. Although it costs less to them but they have some limitations. Due to cost factor Small
and Medium enterprises do not opt for ERP Systems.
The solution to overcome this problem is to implement ERP systems which would be based on
open source technologies and cost less to user. Small and medium businesses have the flexibility
to use only the required modules from ERP system.

Scope of the project

Small and medium enterprises opt for low cost systems to manage their organizational processes
but it results in mismanagement. As for small and medium enterprises cost factor affects a lot;
ERP systems are found to be a good option for them to do many functionalities such as business
planning, inventory management, information management etc. very effectively. Interface for ERP
system is also a simple and efficient which would be user friendly. Most important feature of ERP
system is; according to the organizations need modules can be added into the system. Each module
is authenticated, so security is improved. Five different modules are implemented like HR, Sales,
Purchase, Accounts and Store. Each of these modules is having different functionality. Working
of each department is independent. HR module is implemented to maintain employee record and
send attendance to accounts for salary calculations. Record modification is possible in this system
but only to the authorized person. System can generate salary slip for each employee according to
their attendance, and can generate payment slip for customers. Sales module maintains record for
sales and Purchase department is for maintaining record for purchase items like Kurtis, shirts,
jeans, jackets etc.

Page 3
 • TECHNICAL FEASIBILITY:
Technical feasibility includes the following:

▪ Hardware specification:

✓ RAM - 256MB
✓ Operating System – WINDOWS XP/WINDOWS 7
✓ Hard disk – 20 GB
✓ Processor Pentium 4 or newer versions
▪ Software specification:
✓ VISUAL STUDIO 2010 as front end
✓ SQL SERVER as back end

• ECONOMICAL FEASIBILITY:

Economic analysis is the most frequently used method for evaluating the effectiveness of a new
system. More commonly known as cost/benefit analysis, the procedure is to determine the benefits
and savings that are expected from a candidate system and compare them with costs. If benefits
outweigh costs, then the decision is made to design and implement the system. An entrepreneur
must accurately weigh the cost versus benefits before taking an action.

Cost-based study: It is important to identify cost and benefit factors, which can be categorized as
follows: 1. Development costs; and 2. Operating costs. This is an analysis of the costs to be
incurred in the system and the benefits derivable out of the system.

Time-based study: This is an analysis of the time required to achieve a return on investments.
The future value of a project is also a factor.

• COST FEASIBILITY:
The project is economical to develop, as all the technology used is open source. Also the
hardware and software required are available easily and cheaply.

Page 4
 REVIEW OF LITERATURE
.Net Framework

The .NET Framework is an environment for building, deploying, and running XML Web services
and other applications. It is the infrastructure for the overall .NET platform. The .NET Framework
consists of three main parts: the common language runtime, the class libraries, and ASP.NET. The
common language runtime and class libraries, including Windows Forms, ADO.NET, and
ASP.NET, combine to provide services and solutions that can be easily integrated within and
across a variety of systems. The .NET Framework provides a fully managed, protected, and feature
rich application execution environment, simplified development and deployment, and seamless
integration with a wide variety of languages.

Developer(s) : Microsoft
Initial release : 13 February 2002
Stable release : 4.0 (4.0.30319.1) / 12 April 2010; 10 months ago
Operating system : Windows 98 or later, Windows NT 4.0 or later
Type : Software framework
License : MS-EULA, BCL under Microsoft Reference Source License
Website : msdn.microsoft.com/net framework

The .NET Framework (pronounced dot net) is a software framework for Microsoft Windows
operating systems. It includes a large library, and it supports several programming languages
which allows language interoperability (each language can use code written in other languages).
The .NET library is available to all the programming languages that .NET supports

Page 5
Microsoft SQL Server:
Business today demands a different kind of data management solution. Performance, scalability,
and reliability are essential, but businesses now expect more from their key IT investment.

SQL Server 2000 exceeds dependability requirements and provides innovative capabilities that
increase employee effectiveness, integrate heterogeneous IT ecosystems, and maximize capital
and operating budgets. SQL Server 2000 provides the enterprise data management platform your
organization needs to adapt quickly in a fast-changing environment.

With the lowest implementation and maintenance cost in the industry, SQL Server 2000 delivers
repaid return on your data management investment. SQL Server 2000 supports the rapid
development of enterprise-class business application that can give your company a critical
competitive advantage. Benchmarked for scalability, speed, and performance, SQL Server 2000 is
a fully enterprise-class database product, providing core support for Extensible Markup Language
(XML) and Internet queries. SQL Server 2005 (codenamed Yukon), released in October 2005, is
the successor to SQL Server 2000. It included native support for managing XML data, in addition
to relational data. For this purpose, it defined an xml data type that could be used either as a data
type in database columns or as literals in queries. XML columns can be associated with XSD
schemas; XML data being stored is verified against the schema. XML is converted to an internal
binary data type before being stored in the database. Specialized indexing methods were made
available for XML data. XML data is queried using XQuery; Common Language Runtime (CLR)
integration was a main features with this edition, enabling one to write SQL code as Managed
Code by the CLR.

SQL Server 2005 added some extensions to the T-SQL language to allow embedding XQuery
queries in T-SQL. In addition, it also defines a new extension to XQuery, called XML DML that
allows query-based modifications to XML data. SQL Server 2005 also allows a database server
to be exposed over web services using TDS packets encapsulated within SOAP (protocol)
requests. When the data is accessed over web services, results are returned as XML

Page 6
 Process Model
The simplest process model is the waterfall model, which states that the Phases are
organized in a linear order. The model was originally proposed By Royce, though variations of the
model have evolved depending on the nature of activities and the flow of control between them.
In this model, a project begins with feasibility analysis.
Steps:-
• Requirements document
• Project plan
• Design documents (architecture, system, detailed)
• Test plan and test reports
• Final code
• Software manuals (e.g., user, installation, etc.)

Planning specifications frozen

Project planning phase

Analysis specifications frozen

Analysis phase

Design specifications frozen

Design phase

Design specifications
frozen

Implementation phase

Page 7
Gantt Chart

Page 8
PERT Chart:

The Program (or Project) Evaluation and Review Technique, commonly

abbreviated PERT, is a model for project management designed to analyze and represent
the tasks involved in completing a given project.

PERT is a method to analyze the involved tasks in completing a given project

especially the time needed to complete each task, and identifying the minimum time needed
to complete the total project.

A PERT chart is a project management tool used to schedule organize and

coordinate tasks within a project PERT stands for Program Evaluation Review Technique
a methodology developed by the U S Navy in the 1950s to manage the Polaris submarine
missile program. A similar methodology the Critical Path Method (CPM) was developed
for project management in the private sector at about the same time.

A PERT chart presents a graphic illustration of a project as a network diagram

consisting of numbered nodes (either circles or rectangles) representing events or marks in
the project. The direction of the arrows on the lines indicates the sequence of tasks.

The PERT chart is sometimes preferred over the Gantt chart another popular Project
management charting method because it clearly illustrates task dependencies. On the other
hand the PERT chart can be much more difficult to interpret especially on complex
projects. Frequently project managers use both techniques.

ADVANTAGES:

PERT chart explicitly defines and makes visible dependencies (precedence

relationships) between the WBS elements. PERT facilitates identification of the critical
path and makes this visible. PERT facilitates identification of early start, late start, and
slack for each activity.

Page 9
 PERT provides for potentially reduced project duration due to better understanding
dependencies leading to improved overlapping of activities and tasks where feasible.

The large amount of project data can be organized & presented in diagram for use
making.

Page 10
Page 11
DFD Diagrams:
Context 0th level Diagram:

Data Out Put Stage

Data Input Stage
Data Storage
ADMIN
Admin

Employee

EMPLOYEE Security

UI Screens

SECURITY Managerial

User Level
Reports
System Process

Login DFD

Login Master

Enter User User Home

Open Login Yes Yes
Name and Check User Page
form
Password

No

Validates
Data

Admin Details Data Flow : 1st level DFD

Page 12
 Manage Employees Enter First Name Enter Last Name Enter Qualification
Enter Date Of Birth

1.2.1 1.2.2 1.2.3 1.2.4

1.2.5

Varifies Data
Verifies Data Verifies Data

Enter Address
Enter Phone No Upload Image
Submit Employee
Master
1.2.5
1.2.6 1.2.7

2ndlevel DFD

Product
Master

Manage Company Enter Brand Id Enter BrandName Brand Abbrv

Brand Product ID

1.3.1 1.3.2 1.3.3 1.3.4

1.3.5

Verifies Data
Verifies Data Verifies Data

Storage
Instruction Id

Submit Company
Brand Master
1.3.6

Storage
Instruction
Master

Employee Details data flow

Page 13
 Employee Payment
Login Master
Master Details master

Open Form() Manage

Manage Payment
2.0.0 Personal Data Details

2.0.2 2.0.4

Enter Login Manage

Details Product Manage Ware
Storage house payment
2.0.1
2.0.3 2.0.5

Verifies Validates Product Payment

Data Data Storage Master Master

Manage
Product
Discharge Log out

2.0.6
Product
Discharge
Master

Security Details Data Flow

Employee Discharge
Login Master
Master Gate pass

Open Form() Checks

Manage Discharge
3.0.0 Personal Data Gate pass

3.0.2 3.0.4

Enter Login
Details Manage
Security
3.0.1
3.0.3

Verifies Validates Product

Storage Master
Data Data

Log out

Page 14
Page 15
 Activity DIAGRAMS

1. ADMIN LOGIN

STARTS

LOGIN

N IS
O VALID
OR
NOT YE
S
LOGIN SUCCESFULLY

CONFIRM ORDER AND

UPDATE PRICE OF
PRODUCT

STOP

Page 16
 2. USERS LOGIN

STARTS

NEW REGISTRATION

LOGIN

N IS
O VALID
OR
NOT YE
S
LOGGED IN

VIEW AND BUY

PRODUCT

STOP

Page 17
3. PURCHES ORDER

STARTS

LOGIN

N IS
O VALID
OR
NOT
YE
S
LOGIN SUCCESFULLY

Check the Product stock

and requirement

Add purchase order

Add purchase entry

Generate purchase invoice

STOP

Page 18
 4. SALES ORDER

STARTS

LOGIN

N IS
O VALID
OR
NOT
YE
S
LOGIN SUCCESFULLY

Check the Sales Order

Add purchase entry

Generate Sales invoice

STOP

Page 19
5. EMPLOYEE MANAGEMENT

STARTS

LOGIN

N IS
O VALID
OR
NOT
YE
S
LOGIN SUCCESFULLY

Check the Employee

record

Add Employee Attendance

Generate Employee Pay Slip

STOP

Page 20
Page 21
 USE CASE DIGRAM

Use Case for Administrator

Handle All
Department

Update, Edit and

Delete Data

Update Data and

View Reports

View Report
Administrator

View Invoice

Page 22
 Use Case for HR Employee

Employee
Attendance

Employee Leave

Update Data and

View Reports

Employee Record
HR Employee

Employee Pay
Slip

Page 23
 Use Case for Account Head

Customer
Payment

Vendor Payment

Update Data and

View Reports

Employee Salary
Account Dept.
Employee

Apply For Leave

Application

Page 24
 Use Case for Sales Head

Sales Entry

Sales Invoice

Update Data and

View Reports

Sales Order
Sales Dept.
Employee

Apply For Leave

Application

Page 25
 Use Case for Purchase Head

Purchase Entry

Purchase Invoice

Update Data and

View Reports

Purchase Order
Purchase Dept.
Employee

Apply For Leave

Application

Page 26
 Use Case for Store Head

Inward Material

Outward
Material

Update Data and

View Reports

Stock Record
Store Dept.
Employee

Scrap And Waste

Material Details

Page 27
Page 28
E-R DIAGRAM
DESCRIPTION:

A conceptual ER model may be used as the foundation for one or more logical data models. The
purpose of the conceptual ER model is then to establish structural metadata commonality for the
master data entities between the set of logical ER models. The conceptual data model may be
used to form commonality relationships between ER models as a basis for data model
integration.

• A Relationship is an association among several Entities.

• The set of Entities of the same type are called as Entity Set.
• The set of Relationships of same type are called as Relationship Set

It represents entity set

It represents attributes

It represents relationship

Page 29
 User name Password
Password User name

Ad_id

D-id
ADMIN Multiple
Department Users

Has

Has Has

Has

Has

R_id
M_id

Genera

Multiple Data As te Report and

per Department Invoice
View
Purchase
Employee Invoice
Store
Departm Price Report
Purchase
ent Departmen
Stock Sales
HR t
Report Invoice
Department
Accounts
Departmen
Sales
t
Departmen
t Generate Report G_id
and Invoice

Page 30
Page 31
CLASS DIAGRAM :
Class Diagram:

➢ Class diagrams define the basic building blocks of a model, namely types, classes, and
general material used to construct the full model.
➢ Class diagrams have the following functions:
➢ They describe the static structure of a system.
➢ They show the existence of classes and their relationships.
o Classes represent an abstraction of entities with common characteristics.
o Relationships may be Generalization, Association, Aggregation, Composition, or
Dependency.
➢ Typical uses of Class diagrams are:
o To model vocabulary of the system, in terms of system’s abstractions
o To model collaborations between classes
o To model logical database schema (blueprint for conceptual design of database)
➢ Class may be represented in any of the following ways:
In Association:

o Name indicates relationship between classes.

o Role represents the way classes see each other.

o Aggregation is indicated by hollow diamond.

o Composition is indicated by filled diamond.
o Diamond points toward the “whole” class or the aggregate.

Page 32
Class Diagram:

➢ Class diagrams define the basic building blocks of a model, namely types, classes, and
general material used to construct the full model.
➢ Class diagrams have the following functions:
➢ They describe the static structure of a system.
➢ They show the existence of classes and their relationships.
o Classes represent an abstraction of entities with common characteristics.
o Relationships may be Generalization, Association, Aggregation, Composition, or
Dependency.
➢ Typical uses of Class diagrams are:
o To model vocabulary of the system, in terms of system’s abstractions
o To model collaborations between classes
o To model logical database schema (blueprint for conceptual design of database)
➢ Class may be represented in any of the following ways:
In Association:

o Name indicates relationship between classes.

o Role represents the way classes see each other.

o Aggregation is indicated by hollow diamond.

o Composition is indicated by filled diamond.
o Diamond points toward the “whole” class or the aggregate.

Page 33
Class Diagram :

Page 34
Page 35
EVENT TABLE

Event Trigger Source Use case Response Destination

Checks for If the login id

Admin wants Login Admin valid user-id and password is Admin
to login and password correct then
further access is
granted
HR wants to Checks for If the login id
login valid user-id and password is
Login HR and password correct then HR
further access is
granted
Account Dept. Checks for If the login id
User wants to Login Accounts valid user-id and password is Accounts
login and password correct then
further access is
granted
Sales Dept. Checks for If the login id
User wants to Login Sales valid user-id and password is Sales
login and password correct then
further access is
granted
Store Dept. Checks for If the login id
User wants to Login Store valid user-id and password is Store
login and password correct then
further access is
granted
Purchase Dept. Checks for If the login id
User wants to Login Purchase valid user-id and password is
login and password correct then Purchase
further access is
granted
User wants to Check All Data Insert in
add data Add data User Fields Database User

User wants to Edit User Select and Edit Data Edited in User
Edit data Field Database

Page 36
User wants to Delete User Select Data Data Delete User
Delete data from Database

User wants to Report User Select Data Report Generate User

Generate Successfully
Report
User wants
to Logout Logout User Logout Logout User

Page 37
Page 38
SEQUENCEDIAGRAM

User Admin

Register

Add, Remove Car

Details

Login

View Car Details

Refers
Add, Remove Car
Details

Page 39
 BIBLIOGRAPHY
The books referred are:
• Complete reference of ASP.NET
• ASP.NET Black Book Programming
• Complete Reference of SQL

The various sites referred are as follows:

• www.dotnetdeveloper.com
• www.roseindia.com
• www.codeproject.com
• www.tatamcgrawhill.com
• www.encyclopedia.com

Page 40