Organization management system

7/29/2019 Organization management system

1/159

Showroom Organization Management System

Jain University, School of Graduate Studies

PROJECT NAME


(Submitted in the Partial fulfillment of the requirements of the Degree of

Bachelor of Computer Applications (BCA) Jain University)

By

Supriya B S (09BCA10064)

Sneha Sridhar B (09BCA10078)

2011-2012



2/159



J. C. Road, Bangalore-560 027

1Jain University, School of Graduate Studies

J. C. Road, Bangalore - 560 027

This is to certify that, is a bona fide student of Jain University, School of Graduate Studies and

has carried out a project entitled Showroom organization management system, under my

guidance. This project report has been submitted during the academic year 2011 2012 in

partial fulfillment of the requirements of the Degree ofBachelor of Computer Applications

(BCA)of Jain University.

Guide: Sonali jain Coordinator:Manjunath

Lecturer JU, School of Graduate Studies, Bangalore

JU, School of Graduate Studies, Bangalore

Date:

Place: JU, School of Graduate Studies, Bangalore.

External Examiners:


3/159



1. _________________________

2. _________________________


4/159



Declaration

We, Supriya B S and Sneha Sridhar B do hereby declare that the project work entitled

Showroom Organization Management System, is bona fide work carried out by me under

the guidance of. This project, as presented in this report, is my original work and has not been

presented for any other University award. This project has been submitted as part fulfillment of

requirements for Degree ofBachelor of Computer Applications of Jain University.

Place:

Date:


5/159



PREFACE


6/159



PREFACE

In order to equip the computer science students with more knowledge, the B.C.A course of Jain

University makes it compulsory for the sixth semester students to undertake a project.

Its an exercise, which is instilled into the course to give an opportunity to the students to have

an experience of their corporate environment.

This project was developed at Jain University, School of Graduate Studies Bangalore.


7/159




8/159



ACKNOWLEDGEMENT


9/159



ACKNOWLEDGEMENT

This project has given us the opportunity to put our theoretical knowledge into practical use.

This experience has given us a chance to increase our knowledge in the related areas of

computer science.

We thank every individual for his valuable support during the development of this project. I

would like to express my gratitude to a lot of people for their support and assistance in

developing this project I would like to thank Sonali JainJain University, School of Graduate

Studies for his valuable encouragement during the process.

It gives us the immense pleasure in regarding my deep sense of gratitude and sincere thanks to

Department of BCAJain University, School of Graduate Studies, for allowing us to work in a

flexible manner, giving us necessary direction to carry out the study and suggesting

modification in my approach so as to make the study more meaningful. They have been very


10/159



easily accessible and willing to provide help whenever required.

I would also like to thank all the staff members of the Department of Bachelor Of Computer

Applications for their inspiration and kind cooperation in completing the project.


11/159




12/159



TABLE OF CONTENTS

1. INTRODUCTION

2. OBJECTIVES OF THE PROJECT

3. SYNOPSIS

4. FEATURES OF EXISTING SOFTWARE

5. FEATURES IMPLEMENTING IN NEW SOFTWARE

6. FRONT END LANGUAGES AND VERSION

7. BACK END TOOLS AND VERSION

8. GRAPHIC DESIGNING TOOLS

9. E-R DIAGRAM


13/159



10. DATA FLOW DIAGRAM

11. TABLE DESIGN

12. TABLE RELATIONS/CONSTRAINTS

13. SCREEN SHOT

14. CODING

15. TEST CASE

16. REPORTS

17. CONCLUSION

18. BIBLIOGRAPHY

INTRODUCTION


14/159



This is an OMS (showroom organization management system) based Application cum

office administration package which deals with the handling of all the affairs of an organization. This

application is dealing with all the office work of originations. It maintains a relationship between

employees and HR. also maintains a relation between admin with the customer and suppliers. An

employee who in new to the company for its employees id and password deal with the hr, also for leave

approval is puts the application to the hr. if he approves then only the employees can take leave. In case

of admin he can approve new customer and new suppliers and deal with all the work of suppliers and

customer.

MODULE DESCRIPTION:

The system has four major modules:

1. Employee module

2. Human Resource module

3. Administrator module

4. Customer

The welcome form of the project displays the options to a person. It has options for him to post his/her

resume (added new employ), view the present career options of the organization or if he/she is an

employee they can go to the sign-in form. The sign-in form is the entry point of an employee to the

organization through he/she has to login everyday. Whenever the employee logs in the system takes

care of logging him in if the user id and the password are entered correctly. The system also has the

feature of showing the employee his/her own user form based on the employee type.

EMPLOYEE MODULE :


15/159



This module focuses on the basic employee. Each employee is given a user id and password, which

identifies him uniquely. The employee is given a login form wherein he enters the login details user id

and password. The system on employee logging will automatically mark him present and update his

attendance accordingly. As he is a basic employee the system shows his form with his/her select

options. The options given to a basic employee are

1. Apply for leave and check status

2. Logout

Whenever a user wants to change his / her password he can select the change

password option in employee details form. The employee id for retrieving the details from the

database is brought through the session, whichis maintained using cookies in theform. This

removes the burden on user in typing user id again and also maintains security by not allowing one

user to change password of other accidentally. Employee can appply for leaves also view the status

.employee can send the mail to hr also customer. At the end the user is able to log out from the

system using the logout option.

HUMAN RESOURCE MODULE :

In this module HR will assign employee designation. HR will approved leaves according to the employee

requirement. HR can assign each employees salary.

1. Approval for leave

2. Assign salary

3. Employee designation

4. Logout

The HR personnel at the end of the month or at any point of the month can access this facility to

calculate the pay details of an employee.

At the end the user is able to log out from the system using the logout option.


16/159



ADMINISTRATOR MODULE :

This module focuses on the basic employee. Each employee is given a user id and password,

which identifies him uniquely. The employee is given a login form where he enters the login details user

id and password. As he is a basic employee the system shows his form with his/her select options. The

options given to a basic employee are

1. Check the suppliers and their details

2. Check product and their details

3. Logout

CUSTOMER-:

In this module first customer will register. Then he can got userid

and password. Then customer can go to login form. After then if customer

Want to purches product from company he can purches directly. If any

Problem customers fill he can go to send mail. Hear customer can send

Mail, view the send item and inbox item also.


17/159



Synopsis

Title of the project: Organization Management System

Introduction:This is a OMS (organization management system) which deals with the handling

the affairs of sales department for an organization. It maintains the relationship between

employee and supplier, supplier and show rooms. An employee will have his own usernameand password to login. They play a very important role in the organization for the sales

department.

Objectives of the project:

This project provides two major modules employee module and customer module.

Employee Module:

The module focuses on the basic employee. Each employee is given a user id and password,

which identifies him uniquely. The system on employee logging will automatically mark him

present and update his attendance accordingly. As he is a basic employee the system shows his

form with his/her select options. The options given to a basic employee are


18/159



Change Password

Checks details about customer

Give reply for query

Logout

Customer module:

This module focuses on customer. The customer can click on the link provided for the customer

and check for the availability of the product and its features. Customer can also look for the

places where the product is being sold at the nearest outlets. Customer can give feedback

about the product that he has purchased.

Features implementing in Web Page Design:

1. Very fast database engine

2. Open source

3. Written in Java

4. Supports standard SQL, JDBC API

5. Embedded and Server mode, Clustering support

6. Strong security features

7. The PostgreSQL ODBC driver can be used

8. Multi version concurrency

Client side scripting language: Visual Studio .Net(asp with c#)

Server side scripting language: Asp.net


19/159



Database Server with version:Sql server2008

Web server with Version:Internet Information Server 5.0 (IIS)

Graphic Designing Tools: Html

Conclusion:

1. Easy to work

2. No much of manual work

3. Reduces use of paper work

4. Works faster

5. Provides regular updates about the product


20/159



FEATURES OF EXISTING SOFTWARE1. Cannot Upload and Download the latest updates.

2. Risk of mismanagement and of data when the project is under development.

3. No proper coordination between different Applications and Users.

4. Fewer Users - Friendly.

5. Manual system need man power a lot.

6. Communication between customer and owner is not directly.

7. The complete hierarchy is doesnt implemented in manually.

8. Here to purchase the product customer will take some problem.

FEATURES IMPLEMENTING IN NEW SOFTWARE

We all know the importance of computerization. The world is moving ahead at

lightening speed and every one is running short of time. One always wants to get the

information and perform a task he/she/they desire(s) within a short period of time and too with

amount of efficiency and accuracy. The application areas for the computerization have been

selected on the basis of following factors:

1. Minimizing the manual records kept at different locations.

2. There will be more data integrity.

3. Facilitating desired information display, very quickly, by retrieving information from users.

4. Facilitating various statistical information which helps in decision-making?

5. To reduce manual efforts in activities that involved repetitive work.

6. Updating and deletion of such a huge amount of data will become easier.

7. No need to maintain more man power.


21/159



FRONT END LANGUAGES AND VERSION:

Visual Studio .Net 2010(asp.net with c#.net)

INTRODUCTION TO .NET Framework

The .NET Framework is a new computing platform that simplifies application development in the highly

distributed environment of the Internet. The .NET Framework is designed to fulfill the following

objectives:

1. To provide a consistent object-oriented programming environment whether object code is

stored and executed locally, executed locally but Internet-distributed, or executed

remotely.

2. To provide a code-execution environment that minimizes software deployment and

versioning conflicts.

3. To provide a code-execution environment that guarantees safe execution of code, including

code created by an unknown or semi-trusted third party.

4. To provide a code-execution environment that eliminates the performance problems of

scripted or interpreted environments.

5. To make the developer experience consistent across widely varying types of applications,

such as Windows-based applications and Web-based applications.

6. 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


22/159



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 (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


23/159



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, 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 legitimateInternet-deployed software to be exceptionally featuring 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.


24/159



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 asMicrosoft 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.

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:


25/159



1. Console applications.

2. Scripted or hosted applications.

3. Windows GUI applications (Windows Forms).

4. ASP.NET applications.

5. XML Web services.

6. 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.

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.


26/159



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 otherresources. 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.

1.2.3.4.5.6.7.8.9.10.11.12.13.

14. ASP.NETServer Application Development


27/159



Server-side applications in the managed world are implemented through runtime hosts.

Unmanaged applications host the common language runtime, which allows your custom managed code

to control the behavior of the server. This model provides you with all the features of the common

language runtime and class library while gaining the performance and scalability of the host server.

The following illustration shows a basic network schema with managed code running in different

server environments. Servers such as IIS and SQL Server can perform standard operations while your

application logic executes through the managed code.

Server-Side Managed Code

ASP.NET is the hosting environment that enables developers to use the .NET Framework to

target Web-based applications. However, ASP.NET is more than just a runtime host; it is a complete

architecture for developing Web sites and Internet-distributed objects using managed code. Both Web

Forms and XML Web services use IIS and ASP.NET as the publishing mechanism for applications, and

both have a collection of supporting classes in the .NET Framework.

XML Web services, an important evolution in Web-based technology, are distributed, server-

side application components similar to common Web sites. However, unlike Web-based applications,

XML Web services components have no UI and are not targeted for browsers such as Internet Explorer

and Netscape Navigator. Instead, XML Web services consist of reusable software components designed

to be consumed by other applications, such as traditional client applications, Web-based applications, or

even other XML Web services. As a result, XML Web services technology is rapidly moving application

development and deployment into the highly distributed environment of the Internet.

If you have used earlier versions of ASP technology, you will immediately notice the

improvements that ASP.NET and Web Forms offers. For example, you can develop Web Forms pages in

any language that supports the .NET Framework. In addition, your code no longer needs to share the

same file with your HTTP text (although it can continue to do so if you prefer). Web Forms pages

execute in native machine language because, like any other managed application, they take full

advantage of the runtime. In contrast, unmanaged ASP pages are always scripted and interpreted.

ASP.NET pages are faster, more functional, and easier to develop than unmanaged ASP pages because

they interact with the runtime like any managed application.


28/159



The .NET Framework also provides a collection of classes and tools to aid in development and

consumption of XML Web services applications. XML Web services are built on standards such as SOAP

(a remote procedure-call protocol), XML (an extensible data format), and WSDL ( the Web Services

Description Language). The .NET Framework is built on these standards to promote interoperability with

non-Microsoft solutions.

For example, the Web Services Description Language tool included with the .NET Framework

SDK can query an XML Web service published on the Web, parse its WSDL description, and produce C#

or Visual Basic source code that your application can use to become a client of the XML Web service.

The source code can create classes derived from classes in the class library that handle all the underlying

communication using SOAP and XML parsing. Although you can use the class library to consume XML

Web services directly, the Web Services Description Language tool and the other tools contained in theSDK facilitate your development efforts with the .NET Framework.

If you develop and publish your own XML Web service, the .NET Framework provides a set of

classes that conform to all the underlying communication standards, such as SOAP, WSDL, and XML.

Using those classes enables you to focus on the logic of your service, without concerning yourself with

the communications infrastructure required by distributed software development.

Finally, like Web Forms pages in the managed environment, your XML Web service will run with the

speed of native machine language using the scalable communication of IIS.

WHAT IS ASP.NET WEB FORMS?

The ASP.NET Web Forms page framework is a scalable common language runtime programming

model that can be used on the server to dynamically generate Web pages.

Intended as a logical evolution of ASP (ASP.NET provides syntax compatibility with existing

pages), the ASP.NET Web Forms framework has been specifically designed to address a number of key

deficiencies in the previous model. In particular, it provides:

1. The ability to create and use reusable UI controls that can encapsulate common

functionality and thus reduce the amount of code that a page developer has to write.


29/159



2. The ability for developers to cleanly structure their page logic in an orderly fashion (not

"spaghetti code").

3. The ability for development tools to provide strong WYSIWYG design support for pages

(existing ASP code is opaque to tools).

ASP.NET Web Forms pages are text files with an .aspx file name extension. They can be

deployed throughout an IIS virtual root directory tree. When a browser client requests .aspx resources,

the ASP.NET runtime parses and compiles the target file into a .NET Framework class. This class can then

be used to dynamically process incoming requests. (Note that the .aspx file is compiled only the first

time it is accessed; the compiled type instance is then reused across multiple requests).

An ASP.NET page can be created simply by taking an existing HTML file and changing its file

name extension to .aspx (no modification of code is required). For example, the following sample

demonstrates a simple HTML page that collects a user's name and category preference and then

performs a form postback to the originating page when a button is clicked:

ASP.NET provides syntax compatibility with existing ASP pages. This includes support for

code render blocks that can be intermixed with HTML content within an .aspx file. These

code blocks execute in a top-down manner at page render time.

BACK END TOOLS AND VERSION

Visual Studio .Net Framework (Minimal for Deployment)

SQL Server 2010 Enterprise Edition

1. SQL SERVERA database management, or DBMS, gives the user access to their data and helps them

transform the data into information. Such database management systems include dBase,


30/159



paradox, IMS, SQL Server and SQL Server. These systems allow users to create, update and

extract information from their database.

A database is a structured collection of data. Data refers to the characteristics of

people, things and events. SQL Server stores each data item in its own fields. In SQL Server,

the fields relating to a particular person, thing or event are bundled together to form a single

complete unit of data, called a record (it can also be referred to as raw or an occurrence). Each

record is made up of a number of fields. No two fields in a record can have the same field

name.

During an SQL Server Database design project, the analysis of your business needs

identifies all the fields or attributes of interest. If your business needs change over time, you

define any additional fields or change the definition of existing fields.

SQL SERVER TABLES

SQL Server stores records relating to each other in a table. Different tables are created

for the various groups of information. Related tables are grouped together to form a database.

PRIMARY KEY

Every table in SQL Server has a field or a combination of fields that uniquely identifies

each record in the table. The Unique identifier is called the Primary Key, or simply the Key. The

primary key provides the means to distinguish one record from all other in a table. It allows the

user and the database system to identify, locate and refer to one particular record in the

database.

RELATIONAL DATABASE

Sometimes all the information of interest to a business operation can be stored in one

table. SQL Server makes it very easy to link the data in multiple tables. Matching an employee

to the department in which they work is one example. This is what makes SQL Server a


31/159



relational database management system, or RDBMS. It stores data in two or more tables and

enables you to define relationships between the table and enables you to define relationships

between the tables.

FOREIGN KEY

When a field is one table matches the primary key of another field is referred to as a

foreign key. A foreign key is a field or a group of fields in one table whose values match those

of the primary key of another table.

REFERENTIAL INTEGRITY

Not only does SQL Server allow you to link multiple tables, it also maintains consistency

between them. Ensuring that the data among related tables is correctly matched is referred to

as maintaining referential integrity.

DATA ABSTRACTION

A major purpose of a database system is to provide users with an abstract view of the

data. This system hides certain details of how the data is stored and maintained. Data

abstraction is divided into three levels.

Physical level: This is the lowest level of abstraction at which one describes how the data are

actually stored.

Conceptual Level: At this level of database abstraction all the attributed and what data are

actually stored is described and entries and relationship among them.

View level: This is the highest level of abstraction at which one describes only part of the

database.


32/159



FEATURES OF SQL SERVER (RDBMS)

SQL SERVER is one of the leading database management systems (DBMS) because it is

the only Database that meets the uncompromising requirements of todays most demanding

information systems. From complex decision support systems (DSS) to the most rigorous online

transaction processing (OLTP) application, even application that require simultaneous DSS and

OLTP access to the same critical data, SQL Server leads the industry in both performance and

capability

SQL SERVER is a truly portable, distributed, and open DBMS that delivers unmatched

performance, continuous operation and support for every database.

SQL SERVER RDBMS is high performance fault tolerant DBMS which is specially designed for

online transactions processing and for handling large database application.

SQL SERVER with transactions processing option offers two features which contribute to very

high level of transaction processing throughput, which are

ENTERPRISE WIDE DATA SHARING

The unrivaled portability and connectivity of the SQL SERVER DBMS enables all the

systems in the organization to be linked into a singular, integrated computing resource.

PORTABILITY

SQL SERVER is fully portable to more than 80 distinct hardware and operating systems

platforms, including UNIX, MSDOS, OS/2, Macintosh and dozens of proprietary platforms. This

portability gives complete freedom to choose the database sever platform that meets the

system requirements.

OPEN SYSTEMS


33/159



SQL SERVER offers a leading implementation of industry standard SQL. SQL Servers

open architecture integrates SQL SERVER and non SQL SERVER DBMS with industries most

comprehensive collection of tools, application, and third party software products SQL Servers

Open architecture provides transparent access to data from other relational database and even

non-relational database.

GRAPHIC DESIGNING TOOLS: HTML

FEATURES OF WEB DESIGN TOOL:

4. Very fast database engine

5. Open source

6. Written in Java

7. Supports standard SQL, JDBC API

8. Embedded and Server mode, Clustering support

9. Strong security features

10. The PostgreSQL ODBC driver can be used

11. Multi version concurrency


34/159



E-R DIAGRAM


35/159



Employee

EmpID

UserID

Password

Phone

Email

Empleaves

LeaveIDEmpID

LeaveType

Approval

Salary

Empid

Salaryaid

Salarydid

Netsalary

Saldeductions

Empid

Tax

Others

Total

Saladdition

Empid

Basic

Others

Total

for

One Many

Has

One

Content

Content

One

Desgination

DesgID

DesgName

EmpID

One

Has


36/159




37/159



Product

ProductID

ProductName

ProductQuantityPrice

Supplier

Supplierid

Companynmae

Productname

Email

Customers

CustID

Name

Password

ProductNam

Email

Mast_design

DesignationId

DesignationName

Customer_quer

Customercod

Personalname

Productinfo

Handeledby

Description

Has

OneMany

For

Many One

Tbl_mail

Mailid

FromUser

ToUser

Cdate


38/159



TABLE DESIGN


39/159



TABLE NAME: EMPLOYEES

S.NO FIELDNAME DATATYPE SIZE CONSTRAINTS

1. EmpID Varchar 50 Primary key

2. Name Varchar 50

3. Password Varchar 50

4. UserID Varchar 50

5. Addresss Varchar 50

6. Phone Numeric

7. Email Varchar 150

Description:

First employee has to register after registration data will be maintain in employee table. He\she

can go to the login page. Then he will enter the user id and password. That user id and

password will retrieve from the employee table.

TABLE NAME: EMPLOYEE LEAVES


1. LeaveID Varchar 50 Primary key

2. EmpID Varchar 50


40/159



3. Name Varchar 50

4. LeaveType Varchar 50

5. From_date Datetime

6. To_date Datetime

7. approval Varchar 50

Description:

After login employee will apply the leave. Then data will be maintain in the employee

leave table. Then HR will search the leave and approve the leave. Then employee can search

the leave status.

TABLE NAME: Customers


1. CustID Varchar 50 Primary key

2. Name Varchar 50

3. Password Varchar 50

4. Address Varchar 50

5. ProductName Varchar 50

6. Email Varchar 150

7. Phone Numeric

Description:


41/159



To purchase some products from company he \she should register first. The data will be

maintain in the customer table then only he\she can go to the login page. The user id &

password will be taken from the customer table.

TABLE NAME: Supplier


1. SupplierID Varchar 50 Primary key

2. password Varchar 50

3. CompanyName Varchar 100

4. ContactPerson Varchar 50

5. Addresss Varchar 50

6. email Varchar 150

7. Phone Numeric 20

8. productname Varchar 100

Description:

After login administrator will add the supplier in this company. That supplier details will

maintain the supplier table


42/159



TABLE NAME: Salary


1. SalaryID varchar 50

2. EmpID varchar 50

3. SalaryAID float

4. SalaryDID float

5. TotalSalary float

6. NetSalary float

Description:

To create the salary for employee, HR will first fix salary addition and salary deduction then he

will fix the total salary. The total salary maintained in the salary table.

TABLE NAME: SalAddition


1. empid varchar 50 Primary key

2. Basic float

3. DA float

4. HRA float

5. Others float

6. Total float


43/159



Description:

Before creating total salary HR will add the salary in salary addition table. In this table he will

enter the basic salary. Then automatically HRA,DA,OTHERS,TOTAL will be loaded. The data will

be loaded. The data will be maintained in the salary addition table.

TABLE NAME: SalDeduction


1. empid varchar 50

2. Tax float

3. PT float

4. Leaveamount float

5. Others float

6. Total float

Description:

Before deciding salary deduction HR should maintained first salary addition. When u select the

empid that time salary addition will be come automatically. Also PF and OTHERS like all field

will be come automatically .

TABLE NAME: Product


1. ProductID varchar 50 Primary key

2. ProductName varchar 200


44/159



3. ProductQuantity int 4

4. ProductDesc varcahr 200

5. Price float

Description:

How many product will be added in the company administrator will decide that one. Then he

will enter about the product details then that data will be maintain in the product table.

TABLE NAME: Mast_Design


1. DesignationId Int 4 Primary key

2. DesignationName Varchar 50

Description:

When employee will register that time hr will create the destination for employee. There

desgination id and desgination name is needed that two fields are retrieve from this table. Here

manually data will be loaded.

TABLE NAME : Designation



45/159



1. DesgID varchar 50

2. DesgName varchar 50

3. EmpID varchar 50

4. Responsibilities varchar 50

5. Others varchar 50

Description:When hr will create the employee desgination those employee desgination will

loaded here.

TABLE NAME: tbl_mail


1. mailid int 4 Primary key

2. FromUser varchar 50

3. ToUser varchar 50

4. Subject varchar 50

5. Attachment varchar 50

6. contents varchar 500

7. cdate datetime

Description:

When any one compose the mail to you that time that mail information will be maintain

TBL_MAIL table. When you open inbox item then the data will be ret rive from this table only


46/159



TABLE NAME: sentmail


1. mailid int 4 Primary key

2. FromUser varchar 50

3. ToUser varchar 50

4. Subject varchar 50

5. Attachment varchar 50

6. contents varchar 500

7. cdate datetime

Description:

In this table employee, customer ,HR will be interact when they compose mail. That time the

description will maintain in mail sent table. if he want see the composing mail he can retrieve

from this table only.

TABLE NAME: customer_query


47/159




1. Customercode varchar 50

2. PersonalName varchar 50

3. ProductInfo varchar 50

4. HandledBy varchar 50

5. Description varchar 500

Description:

After login the customer will purchase some product in the company. The data will maintain in

the customer query


48/159



SCREEN SHOTS


49/159




50/159




51/159




52/159




53/159




54/159




55/159




56/159




57/159




58/159




59/159




60/159




61/159




62/159




63/159




64/159




65/159




66/159




67/159




68/159




69/159




70/159




71/159




72/159




73/159




74/159




75/159




76/159




77/159




78/159




79/159




80/159




81/159




82/159




83/159




84/159




85/159




86/159



CODING


87/159



Home

using System;

using System.Collections;

using System.Configuration;

using System.Data;

using System.Linq;

using System.Web;

using System.Web.Security;

using System.Web.UI;

using System.Web.UI.HtmlControls;

using System.Web.UI.WebControls;

using System.Web.UI.WebControls.WebParts;

using System.Xml.Linq;

publicpartialclass_Default : System.Web.UI.Page

{

protectedvoid Page_Load(object sender, EventArgs e)

{

}

}


88/159



AdminLogin

using System;

using System.Data;



using System.Web;






publicpartialclassADMLOGIN : System.Web.UI.Page

{


{

}

protectedvoid Button1_Click(object sender, EventArgs e)

{

if(TextBox1.Text == ""&& TextBox2.Text == "")

{

Response.Write("alert('not allowed to put the boxes blank')");


89/159



}

elseif(TextBox1.Text == "")

{

Response.Write(" alert('must fill the user id');");

}

elseif(TextBox1.Text != ""&& TextBox2.Text == "")

{

Response.Write(" alert('must fill the user password');");

}

elseif(TextBox1.Text == "admin"&& TextBox2.Text == "admin")

{

Response.Redirect("~/admwelcome.aspx");

}

else

{

Response.Write("alert('sorry wrong user id and passwrod')");

}

}

}

Product_mgmt


90/159



using System;

using System.Data;



using System.Web;






using System.Data.SqlClient;

publicpartialclassproduct_mgmt : System.Web.UI.Page

{

Class1 obj = newClass1();


{

int i;

obj.con.Open();

obj.cmd = newSqlCommand("select count(PRODUCTid) from PRODUCT",obj.con);

i=int.Parse (obj.cmd.ExecuteScalar ().ToString ());

Label4.Text=i.ToString ();


91/159



obj.con.Close();

}

}

AddProduct

using System;

using System.Data;



using System.Web;







publicpartialclassAddProduct : System.Web.UI.Page

{




92/159



{

obj.con.Open();

obj.cmd = newSqlCommand("select 'P00'+ cast(max(substring(productID,4,4)+1) as

varchar(20)) from product", obj.con);

obj.dr = obj.cmd.ExecuteReader();

obj.dr.Read();

if(obj.dr.IsDBNull(0))

{

Label2.Text = "P001";

}

else

{

Label2.Text = obj.dr[0].ToString();

}

obj.con.Close();

}


{

obj.con.Open();

obj.cmd = newSqlCommand(" insert into Product values( '" + Label2.Text + "','" +

TextBox1.Text + "', " + TextBox2.Text + " , '" + TextBox4.Text + "', " +

TextBox3.Text + " )", obj.con);

try


93/159



{

int i = int.Parse(obj.cmd.ExecuteNonQuery().ToString());

if(i == 1)

{

Response.Write("alert('Inserted.....')");

}

else

{

Response.Write("alert('Enter values..... ')");

}

obj.con.Close();

}

catch

{

Response.Write("alert('Enter values.....')");

}

}

}

Product details

using System;


94/159



using System.Data;



using System.Web;







publicpartialclassPROD_DETAILS : System.Web.UI.Page

{



{

obj.con.Open();

obj.da = newSqlDataAdapter("select * from product",obj.con);

obj.ds = newDataSet();

obj.da.Fill(obj.ds, "product");

GridView1.DataSource = obj.ds;

GridView1.DataBind();

obj.con.Close();

obj.con.Open();


95/159



obj.cmd.CommandText = "select productid from product";

obj.cmd.Connection = obj.con;


while(obj.dr.Read())

{

if(!IsPostBack)

{

DropDownList1.Items.Add(obj.dr[0].ToString());

}

}

obj.con.Close();

obj.dr.Close();

}


{

}

protectedvoid DropDownList1_SelectedIndexChanged(object sender, EventArgs e)

{

obj.da = newSqlDataAdapter("select * from product where productid='" +

DropDownList1.SelectedItem.Text+ "'", obj.con);


obj.da.Fill(obj.ds, "product");



96/159




}


{

}

}

AdmRemoveProduct

using System;

using System.Data;



using System.Web;








97/159



publicpartialclassADMremoveproduct : System.Web.UI.Page

{



{

obj.con.Open();

obj.cmd.CommandText = "select productid from product ";



while (obj.dr.Read())

{

if(!IsPostBack)

{


}

}

obj.dr.Close();

obj.con.Close();

}


{

}



98/159



{

Response.Redirect("~/admwelcome.aspx");

}


{

obj.con.Open();

obj.cmd = newSqlCommand("select * from product where productID='" +

DropDownList1.SelectedItem.Text + "'", obj.con);


if(obj.dr.Read())

{

TextBox1.Text = obj.dr[1].ToString();




}

else

{

Response.Write("alert('entry has no designation')");

}

obj.con.Close();

}



99/159



{

obj.con.Close();

{

obj.con.Open();

obj.cmd = newSqlCommand(" delete from product where

productID='"+DropDownList1.SelectedItem.Text+"'",obj.con);

obj.cmd.ExecuteNonQuery();

Response.Write("alert('remove successfuly......')");

obj.con.Close();

}

}

}

AdmSupplier

using System;

using System.Data;



using System.Web;






100/159





publicpartialclassADMsupplier : System.Web.UI.Page

{



{

int i;

obj.con.Open();

obj.cmd = newSqlCommand("select count(SUPPLIERID) from Supplier", obj.con);

i = int.Parse(obj.cmd.ExecuteScalar().ToString());

Label4.Text = i.ToString();

obj.con.Close();

}

}

Supplier details

using System;

using System.Data;



using System.Web;


101/159









publicpartialclassSupplier_detail : System.Web.UI.Page

{



{

obj.con.Open();

obj.da = newSqlDataAdapter("select * from supplier", obj.con);


obj.da.Fill(obj.ds, "supplier");



obj.con.Close();

obj.con.Open();

obj.cmd.CommandText = "select supplierid from supplier";




102/159



while (obj.dr.Read())

{

if(!IsPostBack)

{


}

}

obj.con.Close();

obj.dr.Close();

}


{

}


{

obj.da = newSqlDataAdapter("select * from supplier where supplierid='" +



obj.da.Fill(obj.ds, "supplier");



}

}


103/159



Addnewsupplier

using System;

using System.Data;



using System.Web;







publicpartialclassADDNEWSUPPLIER : System.Web.UI.Page

{



{

obj.con.Open();

obj.cmd = newSqlCommand("select 'SUP00'+

cast(max(substring(SupplierID,4,4)+1) as varchar(20)) from supplier", obj.con);



104/159



obj.dr.Read();


{

TextBox9.Text = "SUP001";

}

else

{


}

obj.con.Close();

}


{

try

{

obj.con.Open();

obj.cmd = newSqlCommand(" insert into supplier values( '" + TextBox9.Text +

"','" + TextBox8.Text + "', '" + TextBox7.Text + "' , '" + TextBox6.Text + "', '" +

TextBox5.Text + "','" + TextBox4.Text + "','" + TextBox1.Text + "','" +

DropDownList1.SelectedItem.Text + "' )", obj.con);

int x = int.Parse(obj.cmd.ExecuteNonQuery().ToString());

if(x == 1)

{


105/159



Response.Write("alert('Submitted

successfuly......')");

}

else

{


}

obj.con.Close();

}

catch

{


}

}

}

Emplogin

using System;

using System.Data;



using System.Web;



106/159








publicpartialclassemplogin : System.Web.UI.Page

{

Class1 obj=newClass1 ();


{

}


{

int i;


{


}


{


}



107/159



{


}

else

{

obj.con.Open();

obj.cmd = newSqlCommand("select count(*) from employees where EmpID='" +

TextBox1.Text + "' and password='" + TextBox2.Text + "'", obj.con);


if(i == 1)

{

Session["EmpID"] = TextBox1.Text;

Response.Redirect ("~/empdetail1.aspx");

}

else

{

Response.Write("alert('sorry wrong user id and

passwrod')");

}

}

}

}


108/159



Emp sal details

using System;

using System.Data;



using System.Web;







publicpartialclassempsaldetail : System.Web.UI.Page

{



{

obj.da = newSqlDataAdapter("select * from salary where empid='" +

Session["EmpID"].ToString() + "'", obj.con);


obj.da.Fill(obj.ds, "salary");

GridView1.DataSource = obj.ds.Tables[0];


109/159




}

protectedvoid GridView1_SelectedIndexChanged(object sender, EventArgs e)

{

}

}

Emp mailhome

using System;

using System.Data;



using System.Web;








110/159



publicpartialclassEmpMailHome : System.Web.UI.Page

{



{

int i;

obj.con.Open();

obj.cmd = newSqlCommand("select count(*) from tbl_mail where touser=(select

email from employees where empid='" + Session["EmpID"].ToString() + "' )",obj.con);


HyperLink1.Text = i.ToString();

if(i != 0)

{

HyperLink1.NavigateUrl = "empMailBox.aspx";

}

else

{

HyperLink1.NavigateUrl = "EmpMailHome.aspx";

}

obj.con.Close();

}

}


111/159



Emp mailsend

using System;

using System.Data;



using System.Web;






publicpartialclassempmailsend : System.Web.UI.Page

{



{

if(!IsPostBack)

{

obj.con.Open();

obj.cmd.CommandText = "select

mailid,touser,subject,attachment,contents,cdate from sentmail where


112/159



fromuser=(select email from employees where empid='" +

Session["EmpID"].ToString() + "' )";


obj.da.SelectCommand = obj.cmd;

obj.da.Fill(obj.ds, "tbl_mail1");



obj.con.Close();

}

}

publicvoid select(bool aa)

{

foreach (GridViewRow row in GridView1.Rows)

{

CheckBox ch = newCheckBox();

ch = (CheckBox)row.FindControl("c1");

ch.Checked = aa;

}

}

protectedvoid CheckBox1_CheckedChanged( object sender, EventArgs e)

{

if(CheckBox1.Checked == true)

{


113/159



select(true);

}

else

{

select(false);

}

}

publicvoid delete(string str)

{

obj.con.Open();

obj.cmd.CommandText = "delete sentmail where mailid in (" + str + ")";


try

{


}

catch

{

}

obj.con.Close();

}


{


114/159



string str;

string str1 = "";

string str2 = "";

for (int i = 0; i < GridView1.Rows.Count; i++)

{

CheckBox ch = newCheckBox();

ch = (CheckBox)GridView1.Rows[i].FindControl("c1");

if(ch.Checked == true)

{

str = GridView1.Rows[i].Cells[1].Text;

str1 = string.Concat("," + str);

str2 = str1.Remove(0, 1);

}

delete(str2);

str2 = "";

Response.Write("");

}

}

}

Emp leave details

using System;


115/159



using System.Data;



using System.Web;






publicpartialclassempleavedeatail : System.Web.UI.Page

{


{

}

}

Leave status

using System;

using System.Data;



using System.Web;



116/159








publicpartialclassleave_status : System.Web.UI.Page

{



{

obj.con.Open();

if(!IsPostBack)

{

obj.cmd = newSqlCommand("select max(leaveid) from Empleaves where

empid='" + Session["EmpID"].ToString() + "'", obj.con);


obj.dr.Read();


TextBox1.Enabled = false;

obj.con.Close();

}

}



117/159



{

obj.cmd = newSqlCommand("select approval from empleaves where leaveid='" +

TextBox1.Text + "' and empid='" + Session["EmpID"].ToString() + "' and approval='No'",

obj.con);


if(obj.dr.Read() == true)

{

Response.Write("alert('SORRY! Your Leave is not approved wait for

approval')");

}


{

Response.Write("alert('Your did not apply Leave')");

}

else

{

Response.Write("alert('Your Leave is approved')");

}

}

}


118/159



HR login

using System;

using System.Data;



using System.Web;






publicpartialclassHRLogin : System.Web.UI.Page

{


{

}


{


{


}


119/159




{


}


{


}

elseif(TextBox1.Text == "hr"&& TextBox2.Text == "hr")

{

Session["hruser"] = TextBox1.Text;

Response.Redirect("~/HRHome.aspx");

}

else

{

Response.Write("alert('sorry wrong user id and passwrod')");

}

}

}

HR home

using System;

using System.Data;


120/159





using System.Web;







publicpartialclassHRHome : System.Web.UI.Page

{



{

int i;

obj.con.Open();

obj.cmd = newSqlCommand("select count(*) from empleaves", obj.con);

i=int.Parse (obj.cmd.ExecuteScalar().ToString ());

Label1.Text = i.ToString();

}

}


121/159



Salary

using System;

using System.Data;



using System.Web;







publicpartialclassSALARY : System.Web.UI.Page

{



{

int i, j;

obj.con.Open();

obj.cmd = newSqlCommand("select count(salaryID) from salary", obj.con);


obj.dr.Read();


122/159




{

Label1.Text = "SAL001";

}

else

{

i = int.Parse(obj.dr[0].ToString());

j = i + 1;

Label1.Text = "SAL00" + j.ToString();

}

obj.con.Close();

obj.con.Open();

obj.cmd = newSqlCommand("select * from employees", obj.con);


while (obj.dr.Read() == true)

{

if(!IsPostBack)

{

DropDownList1.Items.Add (obj.dr[0].ToString ());

}

}

obj.con.Close();

obj.dr.Close();


123/159



obj.cmd.Dispose();

obj.con.Open();

}


{

Response.Redirect("~/SALARY.aspx");

}


{

obj.con.Close();

obj.con.Open();

obj.cmd = newSqlCommand("select count(*) from SALARY where empid='" +


int i = int.Parse(obj.cmd.ExecuteScalar().ToString());

if(i == 0)

{

obj.con.Close();

obj.con.Open();

obj.cmd = newSqlCommand(" insert into SALARY values( '" + Label1.Text + "','" +

DropDownList1.SelectedItem.Text + "', " + TextBox7.Text + " , " + TextBox8.Text + "," +

TextBox9.Text + " ," + TextBox10.Text + ")", obj.con);

try

{

int x = int.Parse(obj.cmd.ExecuteNonQuery().ToString());


124/159



if(x == 1)

{

Response.Write("alert('Submitted successfuly......')");

}

else

{


}

}

catch

{


}

obj.con.Close();

}

else

{

try

{

obj.con.Close();

obj.con.Open();

obj.cmd = newSqlCommand("update SALARY set SalaryAID=" +

TextBox7.Text + ",SalaryDID=" + TextBox8.Text + ",TotalSalary=" +


125/159



TextBox9.Text + ",NetSalary=" + TextBox10.Text + " where empid='" +



Response.Write("alert('Updated sucessesfuly.....')");

obj.con.Close();

}

catch(Exception ex)

{

Response.Write("alert('" + ex.Message + "')");

}

}

}

protectedvoid Search_Click(object sender, EventArgs e)

{

try

{

float total, deduct, net;

total = float.Parse(TextBox7.Text) - float.Parse(TextBox8.Text);

TextBox9.Text = total.ToString();

if(total > 3000)

{

deduct = (total * 1) / 100;

net = float.Parse(TextBox9.Text) - deduct;


126/159



TextBox10.Text = net.ToString();

}

else

{

TextBox10.Text = total.ToString();

}

}

catch (Exception ex)

{

Response.Write("alert('" + ex.Message + "')");

}

}


{

obj.con.Close();

obj.con.Open();

obj.cmd = newSqlCommand("select * from SalAdditions where empid='" +

DropDownList1.SelectedItem.Text + "' ", obj.con);

Organization management system

Documents