Organization Management System

Showroom Organization Management System
PROJECT NAME Showroom Organization Management System

(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
Jain University, School of Graduate Studies

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 of Bachelor of Computer Applications (BCA)of Jain University.
Guide: Sonali jain
Coordinator:Manjunath
Lecturer JU, School of Graduate Studies, Bangalore Date: Place: JU, School of Graduate Studies, Bangalore. External Examiners:
JU, School of Graduate Studies, Bangalore
1. _________________________ 2. _________________________
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 of Bachelor of Computer Applications of Jain University.
Place: Date:
PREFACE
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.
ACKNOWLEDGEMENT
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
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.
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
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
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. 2. 3. 4. Employee module Human Resource module Administrator module 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 :
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. 2. Apply for leave and check status 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. 2. 3. 4. Approval for leave Assign salary Employee designation 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.
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. 2. 3. Check the suppliers and their details Check product and their details 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.
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 username and 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
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. 2. 3. 4. 5. 6. 7.
8.
Very fast database engine Open source Written in Java Supports standard SQL, JDBC API Embedded and Server mode, Clustering support Strong security features The PostgreSQL ODBC driver can be used Multi version concurrency
Client side scripting language: Visual Studio .Net(asp with c#)
Server side scripting language: Asp.net

Database Server with version:Sql server2008
Web server with Version:Internet Information Server 5.0 (IIS)
Graphic Designing Tools: Html
Conclusion:
1. 2. 3. 4. 5. Easy to work No much of manual work Reduces use of paper work Works faster Provides regular updates about the product
FEATURES OF EXISTING SOFTWARE

1. 2. 3. 4. 5. 6. 7.
8.
Cannot Upload and Download the latest updates. Risk of mismanagement and of data when the project is under development. No proper coordination between different Applications and Users. Fewer Users - Friendly. Manual system need man power a lot. Communication between customer and owner is not directly. The complete hierarchy is doesnt implemented in manually. 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. 2. 3. 4. 5. 6.
7.
Minimizing the manual records kept at different locations. There will be more data integrity. Facilitating desired information display, very quickly, by retrieving information from users. Facilitating various statistical information which helps in decision-making? To reduce manual efforts in activities that involved repetitive work. Updating and deletion of such a huge amount of data will become easier. No need to maintain more man power.
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 Jain University, School of Graduate Studies
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
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 fileaccess 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 featuring rich.
The runtime also enforces code robustness by implementing a strict type- and codeverification 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.
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-intime (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, thirdparty 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: Jain University, School of Graduate Studies
1. 2. 3. 4. 5. 6.
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. 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.
1.
2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. ASP.NET Server Application Development
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, serverside 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. Jain University, School of Graduate Studies
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 the SDK 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.
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 SERVER
A 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,
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
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.
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
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. 5. 6. 7. 8. 9. 10. 11. Very fast database engine Open source Written in Java Supports standard SQL, JDBC API Embedded and Server mode, Clustering support Strong security features The PostgreSQL ODBC driver can be used Multi version concurrency
E-R DIAGRAM
Phone Password Email UserID LeaveType Approval

One Many
LeaveID
EmpID
EmpID
Employee s
for
Empleaves
DesgID Netsalary Salarydid Salaryaid DesgName
Has Has
EmpID
Empid
One
Salary
Desgination
Total Others Basic
Empid
Content Content
Tax Others Total
One One
Empid
Saladdition
Saldeductions
ProductQuantity Companynmae ProductName Productname
Price
Supplierid
ProductID
Many One
Email
Product
Has
Supplier
Handeledby Productinfo Password Personalname ProductNam e Email

Many One
CustID Description Name
Customercod e
Customer_quer y
For
Customers
DesignationName FromUser DesignationId ToUser
Mailid
Cdate
Mast_design
Tbl_mail
TABLE DESIGN
TABLE NAME: EMPLOYEES

S.NO 1. 2. 3. 4. 5. 6. 7. FIELDNAME EmpID Name Password UserID Addresss Phone Email DATATYPE Varchar Varchar Varchar Varchar Varchar Numeric Varchar 150 SIZE 50 50 50 50 50 CONSTRAINTS Primary key
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

S.NO FIELDNAME 1. LeaveID 2. EmpID DATATYPE Varchar Varchar SIZE 50 50 CONSTRAINTS Primary key
3. Name 4. LeaveType 5. From_date

6. To_date 7. approval
Varchar Varchar Datetime

Datetime Varchar
50 50
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

S.NO FIELDNAME 1. CustID 2. Name 3. Password 4. Address 5. ProductName 6. Email 7. Phone DATATYPE Varchar Varchar Varchar Varchar Varchar Varchar Numeric SIZE 50 50 50 50 50 150 CONSTRAINTS Primary key
Description:
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

S.NO FIELDNAME 1. SupplierID 2. password 3. CompanyName 4. ContactPerson 5. Addresss 6. email 7. Phone 8. productname DATATYPE Varchar Varchar Varchar Varchar Varchar Varchar Numeric Varchar SIZE 50 50 100 50 50 150 20 100 CONSTRAINTS Primary key
Description:
After login administrator will add the supplier in this company. That supplier details will maintain the supplier table
TABLE NAME: Salary

S.NO FIELDNAME 1. SalaryID 2. EmpID 3. SalaryAID 4. SalaryDID 5. TotalSalary 6. NetSalary DATATYPE varchar varchar float float float float SIZE 50 50 CONSTRAINTS
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

S.NO FIELDNAME 1. empid 2. Basic 3. DA 4. HRA 5. Others 6. Total DATATYPE varchar float float float float float SIZE 50 CONSTRAINTS Primary key
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

S.NO FIELDNAME 1. empid 2. Tax 3. PT 4. Leaveamount 5. Others 6. Total DATATYPE varchar float float float float float SIZE 50 CONSTRAINTS
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

S.NO FIELDNAME 1. ProductID 2. ProductName DATATYPE varchar varchar SIZE 50 200 CONSTRAINTS Primary key
3. ProductQuantity 4. ProductDesc 5. Price
int varcahr float
4 200
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

S.NO FIELDNAME 1. DesignationId 2. DesignationName DATATYPE Int Varchar SIZE 4 50 CONSTRAINTS Primary key
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

S.NO FIELDNAME DATATYPE SIZE CONSTRAINTS
1. DesgID 2. DesgName 3. EmpID 4. Responsibilities 5. Others
varchar varchar varchar varchar varchar
50 50 50 50 50
Description:When hr will create the employee desgination those employee desgination will
loaded here.
TABLE NAME: tbl_mail

S.NO FIELDNAME 1. mailid 2. FromUser 3. ToUser 4. Subject 5. Attachment 6. contents 7. cdate DATATYPE int varchar varchar varchar varchar varchar datetime SIZE 4 50 50 50 50 500 CONSTRAINTS Primary key
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
TABLE NAME: sentmail

S.NO FIELDNAME 1. mailid 2. FromUser 3. ToUser 4. Subject 5. Attachment 6. contents 7. cdate DATATYPE int varchar varchar varchar varchar varchar datetime SIZE 4 50 50 50 50 500 CONSTRAINTS Primary key
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
S.NO
FIELDNAME 1. Customercode 2. PersonalName 3. ProductInfo 4. HandledBy 5. Description
DATATYPE varchar varchar varchar varchar varchar
SIZE 50 50 50 50 500
CONSTRAINTS
Description:
After login the customer will purchase some product in the company. The data will maintain in the customer query
SCREEN SHOTS
CODING
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) { } }
AdminLogin
using System; using System.Data; using System.Configuration; using System.Collections; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Web.UI.HtmlControls; publicpartialclassADMLOGIN : System.Web.UI.Page { protectedvoid Page_Load(object sender, EventArgs e) { } protectedvoid Button1_Click(object sender, EventArgs e) { if (TextBox1.Text == ""&& TextBox2.Text == "") { Response.Write("<script>alert('not allowed to put the boxes blank')</script>");
} elseif (TextBox1.Text == "") { Response.Write("<script> alert('must fill the user id');</script>"); } elseif (TextBox1.Text != ""&& TextBox2.Text == "") { Response.Write("<script> alert('must fill the user password');</script>"); } elseif (TextBox1.Text == "admin"&& TextBox2.Text == "admin") { Response.Redirect("~/admwelcome.aspx"); } else { Response.Write("<script>alert('sorry wrong user id and passwrod')</script>"); } } }
Product_mgmt
using System; using System.Data; using System.Configuration; using System.Collections; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Web.UI.HtmlControls; using System.Data.SqlClient;
publicpartialclassproduct_mgmt : System.Web.UI.Page { Class1 obj = newClass1(); protectedvoid Page_Load(object sender, EventArgs e) { 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 ();
obj.con.Close(); } }
AddProduct
using System; using System.Data; using System.Configuration; using System.Collections; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Web.UI.HtmlControls; using System.Data.SqlClient; publicpartialclassAddProduct : System.Web.UI.Page
{ Class1 obj = newClass1(); protectedvoid Page_Load(object sender, EventArgs e)

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(); } protectedvoid Button2_Click(object sender, EventArgs e) { obj.con.Open(); obj.cmd = newSqlCommand(" insert into Product values( '" + Label2.Text + "','" + TextBox1.Text + "', " + TextBox2.Text + " , '" + TextBox4.Text + "', " + TextBox3.Text + " )", obj.con); try
{ int i = int.Parse(obj.cmd.ExecuteNonQuery().ToString()); if (i == 1) { Response.Write("<script>alert('Inserted.....')</script>"); } else { Response.Write("<script>alert('Enter values..... ')</script>"); } obj.con.Close(); } catch { Response.Write("<script>alert('Enter values.....')</script>"); } } }
Product details
using System;
using System.Data; using System.Configuration; using System.Collections; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Web.UI.HtmlControls; using System.Data.SqlClient; publicpartialclassPROD_DETAILS : System.Web.UI.Page { Class1 obj = newClass1(); protectedvoid Page_Load(object sender, EventArgs e) { 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();
obj.cmd.CommandText = "select productid from product"; obj.cmd.Connection = obj.con; obj.dr = obj.cmd.ExecuteReader(); while(obj.dr.Read()) { if (!IsPostBack) { DropDownList1.Items.Add(obj.dr[0].ToString()); } } obj.con.Close(); obj.dr.Close(); } protectedvoid Button2_Click(object sender, EventArgs e) { } protectedvoid DropDownList1_SelectedIndexChanged(object sender, EventArgs e) { obj.da = newSqlDataAdapter("select * from product where productid='" + DropDownList1.SelectedItem.Text+ "'", obj.con); obj.ds = newDataSet(); obj.da.Fill(obj.ds, "product"); GridView1.DataSource = obj.ds;
GridView1.DataBind(); } protectedvoid Button1_Click(object sender, EventArgs e) { } }
AdmRemoveProduct
publicpartialclassADMremoveproduct : System.Web.UI.Page { Class1 obj = newClass1(); protectedvoid Page_Load(object sender, EventArgs e) { obj.con.Open(); obj.cmd.CommandText = "select productid from product "; obj.cmd.Connection = obj.con; obj.dr = obj.cmd.ExecuteReader(); while (obj.dr.Read()) { if (!IsPostBack) { DropDownList1.Items.Add(obj.dr[0].ToString()); } } obj.dr.Close(); obj.con.Close(); } protectedvoid DropDownList1_SelectedIndexChanged(object sender, EventArgs e) { } protectedvoid Button1_Click(object sender, EventArgs e)
{ Response.Redirect("~/admwelcome.aspx"); } protectedvoid Button3_Click(object sender, EventArgs e) { obj.con.Open(); obj.cmd = newSqlCommand("select * from product where productID='" + DropDownList1.SelectedItem.Text + "'", obj.con); obj.dr = obj.cmd.ExecuteReader(); if (obj.dr.Read()) { TextBox1.Text = obj.dr[1].ToString(); TextBox2.Text = obj.dr[2].ToString(); TextBox3.Text = obj.dr[3].ToString(); TextBox4.Text = obj.dr[4].ToString(); } else { Response.Write("<script>alert('entry has no designation')</script>"); } obj.con.Close(); } protectedvoid Button2_Click(object sender, EventArgs e)
{ obj.con.Close(); { obj.con.Open(); obj.cmd = newSqlCommand(" delete from product where productID='"+DropDownList1.SelectedItem.Text+"'",obj.con); obj.cmd.ExecuteNonQuery(); Response.Write("<script>alert('remove successfuly......')</script>"); obj.con.Close(); } } }
AdmSupplier
using System; using System.Data; using System.Configuration; using System.Collections; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls; using System.Data.SqlClient; publicpartialclassADMsupplier : System.Web.UI.Page { Class1 obj = newClass1(); protectedvoid Page_Load(object sender, EventArgs e) { 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.Configuration; using System.Collections; using System.Web;
using System.Web.Security; using System.Web.UI; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Web.UI.HtmlControls; using System.Data.SqlClient; publicpartialclassSupplier_detail : System.Web.UI.Page { Class1 obj = newClass1();
protectedvoid Page_Load(object sender, EventArgs e) { obj.con.Open(); obj.da = newSqlDataAdapter("select * from supplier", obj.con); obj.ds = newDataSet(); obj.da.Fill(obj.ds, "supplier"); GridView1.DataSource = obj.ds; GridView1.DataBind(); obj.con.Close(); obj.con.Open(); obj.cmd.CommandText = "select supplierid from supplier"; obj.cmd.Connection = obj.con; obj.dr = obj.cmd.ExecuteReader();
while (obj.dr.Read()) { if (!IsPostBack) { DropDownList1.Items.Add(obj.dr[0].ToString()); } } obj.con.Close(); obj.dr.Close(); } protectedvoid Button1_Click(object sender, EventArgs e) { } protectedvoid DropDownList1_SelectedIndexChanged(object sender, EventArgs e) { obj.da = newSqlDataAdapter("select * from supplier where supplierid='" + DropDownList1.SelectedItem.Text + "'", obj.con); obj.ds = newDataSet(); obj.da.Fill(obj.ds, "supplier"); GridView1.DataSource = obj.ds; GridView1.DataBind(); } }
Addnewsupplier
using System; using System.Data; using System.Configuration; using System.Collections; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Web.UI.HtmlControls; using System.Data.SqlClient; publicpartialclassADDNEWSUPPLIER : System.Web.UI.Page { Class1 obj = newClass1(); protectedvoid Page_Load(object sender, EventArgs e) { obj.con.Open(); obj.cmd = newSqlCommand("select 'SUP00'+ cast(max(substring(SupplierID,4,4)+1) as varchar(20)) from supplier", obj.con); obj.dr = obj.cmd.ExecuteReader();
obj.dr.Read(); if (obj.dr.IsDBNull(0)) { TextBox9.Text = "SUP001"; } else { TextBox9.Text = obj.dr[0].ToString(); } obj.con.Close(); } protectedvoid Button1_Click(object sender, EventArgs e) { 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) {
Response.Write("<script>alert('Submitted successfuly......')</script>"); } else { Response.Write("<script>alert('Enter values.....')</script>"); } obj.con.Close(); } catch { Response.Write("<script>alert('Enter values.....')</script>"); } } }
Emplogin
using System; using System.Data; using System.Configuration; using System.Collections; using System.Web; using System.Web.Security;
using System.Web.UI; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Web.UI.HtmlControls; using System.Data.SqlClient; publicpartialclassemplogin : System.Web.UI.Page { Class1 obj=newClass1 (); protectedvoid Page_Load(object sender, EventArgs e) { } protectedvoid Button1_Click(object sender, EventArgs e) { int i; if (TextBox1.Text == ""&& TextBox2.Text == "") { Response.Write("<script>alert('not allowed to put the boxes blank')</script>"); } elseif (TextBox1.Text == "") { Response.Write("<script> alert('must fill the user id');</script>"); } elseif (TextBox1.Text != ""&& TextBox2.Text == "")
{ Response.Write("<script> alert('must fill the user password');</script>"); } else {
obj.con.Open(); obj.cmd = newSqlCommand("select count(*) from employees where EmpID='" + TextBox1.Text + "' and password='" + TextBox2.Text + "'", obj.con); i = int.Parse(obj.cmd.ExecuteScalar().ToString()); if (i == 1) { Session["EmpID"] = TextBox1.Text; Response.Redirect ("~/empdetail1.aspx"); } else { Response.Write("<script>alert('sorry wrong user id and passwrod')</script>"); } } } }
Emp sal details
using System; using System.Data; using System.Configuration; using System.Collections; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Web.UI.HtmlControls; using System.Data.SqlClient; publicpartialclassempsaldetail : System.Web.UI.Page { Class1 obj = newClass1(); protectedvoid Page_Load(object sender, EventArgs e) { obj.da = newSqlDataAdapter("select * from salary where empid='" + Session["EmpID"].ToString() + "'", obj.con); obj.ds = newDataSet(); obj.da.Fill(obj.ds, "salary"); GridView1.DataSource = obj.ds.Tables[0];
GridView1.DataBind(); } protectedvoid GridView1_SelectedIndexChanged(object sender, EventArgs e) { } }
Emp mailhome
publicpartialclassEmpMailHome : System.Web.UI.Page { Class1 obj = newClass1(); protectedvoid Page_Load(object sender, EventArgs e) { 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); i = int.Parse(obj.cmd.ExecuteScalar().ToString()); HyperLink1.Text = i.ToString(); if (i != 0) { HyperLink1.NavigateUrl = "empMailBox.aspx"; } else { HyperLink1.NavigateUrl = "EmpMailHome.aspx"; } obj.con.Close(); } }
Emp mailsend
using System; using System.Data; using System.Configuration; using System.Collections; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Web.UI.HtmlControls; publicpartialclassempmailsend : System.Web.UI.Page { Class1 obj = newClass1(); protectedvoid Page_Load(object sender, EventArgs e) { if (!IsPostBack) { obj.con.Open(); obj.cmd.CommandText = "select mailid,touser,subject,attachment,contents,cdate from sentmail where
fromuser=(select email from employees where empid='" + Session["EmpID"].ToString() + "' )"; obj.cmd.Connection = obj.con; obj.da.SelectCommand = obj.cmd; obj.da.Fill(obj.ds, "tbl_mail1"); GridView1.DataSource = obj.ds; GridView1.DataBind(); 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) {
select(true); } else { select(false); } } publicvoid delete(string str) { obj.con.Open(); obj.cmd.CommandText = "delete sentmail where mailid in (" + str + ")"; obj.cmd.Connection = obj.con; try { obj.cmd.ExecuteNonQuery(); } catch { } obj.con.Close(); } protectedvoid Button1_Click(object sender, EventArgs e) {
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("<meta http-equiv='refresh' } } } content='0.1'/>");
Emp leave details
using System;
using System.Data; using System.Configuration; using System.Collections; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Web.UI.HtmlControls; publicpartialclassempleavedeatail : System.Web.UI.Page { protectedvoid Page_Load(object sender, EventArgs e) { }
} Leave status
using System; using System.Data; using System.Configuration; using System.Collections; using System.Web; using System.Web.Security;
using System.Web.UI; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Web.UI.HtmlControls; using System.Data.SqlClient; publicpartialclassleave_status : System.Web.UI.Page { Class1 obj = newClass1(); protectedvoid Page_Load(object sender, EventArgs e) { obj.con.Open(); if (!IsPostBack) { obj.cmd = newSqlCommand("select max(leaveid) from Empleaves where empid='" + Session["EmpID"].ToString() + "'", obj.con); obj.dr = obj.cmd.ExecuteReader(); obj.dr.Read(); TextBox1.Text = obj.dr[0].ToString(); TextBox1.Enabled = false; obj.con.Close(); } } protectedvoid Button1_Click(object sender, EventArgs e)
{ obj.cmd = newSqlCommand("select approval from empleaves where leaveid='" + TextBox1.Text + "' and empid='" + Session["EmpID"].ToString() + "' and approval='No'", obj.con); obj.dr = obj.cmd.ExecuteReader(); if (obj.dr.Read() == true) { Response.Write("<script>alert('SORRY! Your Leave is not approved wait for approval')</script>"); } elseif (TextBox1.Text == "") { Response.Write("<script>alert('Your did not apply Leave')</script>"); } else { Response.Write("<script>alert('Your Leave is approved')</script>"); } } }
HR login
using System; using System.Data; using System.Configuration; using System.Collections; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Web.UI.HtmlControls; publicpartialclassHRLogin : System.Web.UI.Page { protectedvoid Page_Load(object sender, EventArgs e) { } protectedvoid Button1_Click(object sender, EventArgs e) { if (TextBox1.Text == ""&& TextBox2.Text == "") { Response.Write("<script>alert('not allowed to put the boxes blank')</script>"); }
elseif (TextBox1.Text == "") { Response.Write("<script> alert('must fill the user id');</script>"); } elseif (TextBox1.Text != ""&& TextBox2.Text == "") { Response.Write("<script> alert('must fill the user password');</script>"); } elseif (TextBox1.Text == "hr"&& TextBox2.Text == "hr") { Session["hruser"] = TextBox1.Text; Response.Redirect("~/HRHome.aspx"); } else { Response.Write("<script>alert('sorry wrong user id and passwrod')</script>"); } } }
HR home
using System; using System.Data;
using System.Configuration; using System.Collections; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Web.UI.HtmlControls; using System.Data.SqlClient; publicpartialclassHRHome : System.Web.UI.Page { Class1 obj = newClass1(); protectedvoid Page_Load(object sender, EventArgs e) { 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(); } }
Salary
using System; using System.Data; using System.Configuration; using System.Collections; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Web.UI.HtmlControls; using System.Data.SqlClient; publicpartialclassSALARY : System.Web.UI.Page { Class1 obj = newClass1(); protectedvoid Page_Load(object sender, EventArgs e) { int i, j; obj.con.Open(); obj.cmd = newSqlCommand("select count(salaryID) from salary", obj.con); obj.dr = obj.cmd.ExecuteReader(); obj.dr.Read();
if (obj.dr.IsDBNull(0)) { 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); obj.dr = obj.cmd.ExecuteReader(); while (obj.dr.Read() == true) { if (!IsPostBack) { DropDownList1.Items.Add (obj.dr[0].ToString ()); } } obj.con.Close(); obj.dr.Close();
obj.cmd.Dispose(); obj.con.Open(); } protectedvoid Button2_Click(object sender, EventArgs e) { Response.Redirect("~/SALARY.aspx"); } protectedvoid Button1_Click(object sender, EventArgs e) { obj.con.Close(); obj.con.Open(); obj.cmd = newSqlCommand("select count(*) from SALARY where empid='" + DropDownList1.SelectedItem.Text + "'", obj.con); 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());
if (x == 1) { Response.Write("<script>alert('Submitted successfuly......')</script>"); } else { Response.Write("<script>alert('Enter values.....')</script>"); } } catch { Response.Write("<script>alert('Enter values.....')</script>"); } obj.con.Close(); } else { try { obj.con.Close(); obj.con.Open(); obj.cmd = newSqlCommand("update SALARY set SalaryAID=" + TextBox7.Text + ",SalaryDID=" + TextBox8.Text + ",TotalSalary=" +
TextBox9.Text + ",NetSalary=" + TextBox10.Text + " where empid='" + DropDownList1.SelectedItem.Text + "'", obj.con); obj.cmd.ExecuteNonQuery(); Response.Write("<script>alert('Updated sucessesfuly.....')</script>"); obj.con.Close(); } catch(Exception ex) { Response.Write("<script>alert('" + ex.Message + "')</script>"); } } } 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;
TextBox10.Text = net.ToString(); } else { TextBox10.Text = total.ToString(); } } catch (Exception ex) { Response.Write("<script>alert('" + ex.Message + "')</script>"); } } protectedvoid Button3_Click(object sender, EventArgs e) { obj.con.Close(); obj.con.Open(); obj.cmd = newSqlCommand("select * from SalAdditions where empid='" + DropDownList1.SelectedItem.Text + "' ", obj.con); obj.dr = obj.cmd.ExecuteReader(); if (obj.dr.Read() == true) { TextBox7.Text = obj.dr[5].ToString(); }
else { TextBox7.Text = ""; Response.Write("<script>alert('First fix saladdition')</script>"); } obj.con.Close(); } protectedvoid Button4_Click(object sender, EventArgs e) { obj.con.Close(); obj.con.Open(); obj.cmd = newSqlCommand("select * from SalDeductions where empid='" + DropDownList1.SelectedItem.Text + "' ", obj.con); obj.dr = obj.cmd.ExecuteReader(); if (obj.dr.Read() == true) { TextBox8.Text = obj.dr[5].ToString(); } else { TextBox8.Text = ""; Response.Write("<script>alert('First fix saladeduction')</script>"); }
obj.con.Close(); } }
HR leave approval
using System; using System.Data; using System.Configuration; using System.Collections; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Web.UI.HtmlControls; using System.Data.SqlClient; publicpartialclassHRleaveApproval : System.Web.UI.Page { Class1 obj = newClass1(); publicvoid filldata() {
obj.da = newSqlDataAdapter("select * from empleaves", obj.con); obj.ds = newDataSet(); obj.da.Fill(obj.ds, "empleaves"); GridView1.DataSource = obj.ds.Tables[0]; GridView1.DataBind(); } protectedvoid Page_Load(object sender, EventArgs e) { if (Page.IsPostBack == false) { filldata(); } } protectedvoid GridView1_RowEditing(object sender, GridViewEditEventArgs e) { GridView1.EditIndex = e.NewEditIndex; filldata(); } protectedvoid GridView1_RowCancelingEdit(object sender, GridViewCancelEditEventArgs e) { GridView1.EditIndex = -1; filldata(); }
protectedvoid GridView1_RowUpdating(object sender, GridViewUpdateEventArgs e) { string uid; TextBox t, t1,t2,t3; t1 = (TextBox)GridView1.Rows[e.RowIndex].Cells[1].Controls[0]; t2 = (TextBox)GridView1.Rows[e.RowIndex].Cells[5].Controls[0]; t3 = (TextBox)GridView1.Rows[e.RowIndex].Cells[6].Controls[0]; t = (TextBox)GridView1.Rows[e.RowIndex].Cells[7].Controls[0]; string str = t.Text; string str1,str2; str1 = t2.Text; str2 = t3.Text; uid = t1.Text; obj.con.Open (); obj.cmd = newSqlCommand("update empleaves set approval='" + str + "',From_date='"+str1+"',to_date='"+str2+"' where leaveId='" + uid + "'",obj.con ); obj.cmd.ExecuteNonQuery(); obj.con.Close(); GridView1.EditIndex = -1; filldata(); } protectedvoid GridView1_PageIndexChanging(object sender, GridViewPageEventArgs e) {
GridView1.PageIndex = e.NewPageIndex; filldata(); } }
HR mail
using System; using System.Data; using System.Configuration; using System.Collections; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Web.UI.HtmlControls; publicpartialclassHRmail : System.Web.UI.Page { protectedvoid Page_Load(object sender, EventArgs e) {
} }
Customer login
using System; using System.Data; using System.Configuration; using System.Collections; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Web.UI.HtmlControls; using System.Data.SqlClient; publicpartialclassCUSTOMERLOGIN : System.Web.UI.Page { Class1 obj = newClass1(); protectedvoid Page_Load(object sender, EventArgs e) {
} protectedvoid Button1_Click(object sender, EventArgs e) {

int i;
if (TextBox1.Text == ""&& TextBox2.Text == "") { Response.Write("<script>alert('not allowed to put the boxes blank')</script>"); } elseif (TextBox1.Text == "") { Response.Write("<script> alert('must fill the user id');</script>"); } elseif (TextBox1.Text != ""&& TextBox2.Text == "") { Response.Write("<script> alert('must fill the user password');</script>"); } else { obj.con.Open(); obj.cmd = newSqlCommand("select count(*) from customers where custID='" + TextBox1.Text + "' and password='" + TextBox2.Text + "'", obj.con); i = int.Parse(obj.cmd.ExecuteScalar().ToString()); if (i == 1) { Session["custid"] = TextBox1.Text;
Response.Redirect ("~/CUSTOMERMAIN.aspx"); }
else { Response.Write("<script>alert('sorry wrong user id and passwrod')</script>"); } } } }
Customer main
using System; using System.Data; using System.Configuration; using System.Collections; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Web.UI.HtmlControls;
publicpartialclassCUSTOMERMAIN : System.Web.UI.Page { protectedvoid Page_Load(object sender, EventArgs e) { } } Customer query
using System; using System.Data; using System.Configuration; using System.Collections; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Web.UI.HtmlControls; using System.Data.SqlClient; publicpartialclassCUSTOMER_QUERY : System.Web.UI.Page { Class1 obj = newClass1(); protectedvoid Page_Load(object sender, EventArgs e)
{ obj.con.Open(); if (!IsPostBack) { obj.cmd = newSqlCommand("select * from Customers where custid='" + Session["custID"].ToString() + "'", obj.con); obj.dr = obj.cmd.ExecuteReader(); obj.dr.Read(); TextBox1.Text = obj.dr[0].ToString(); TextBox1.Enabled = false; obj.con.Close(); } } protectedvoid Button5_Click(object sender, EventArgs e) { obj.cmd = newSqlCommand(" insert into customer_query values( '" + TextBox1.Text + "','" + TextBox2.Text + "', '" + TextBox3.Text + " ', '" + TextBox4.Text + "', '" + TextBox5.Text + " ')", obj.con); try { int x = int.Parse(obj.cmd.ExecuteNonQuery().ToString()); if (x == 1) {
Response.Write("<script>alert('Submitted successfuly......')</script>"); } else { Response.Write("<script>alert('Enter values.....')</script>"); } } catch { Response.Write("<script>alert('Enter values.....')</script>"); } obj.con.Close(); } protectedvoid Btnclear_Click(object sender, EventArgs e) { TextBox2.Text = ""; TextBox3.Text = ""; TextBox4.Text = ""; TextBox5.Text = ""; } protectedvoid Btndelete_Click(object sender, EventArgs e) {
try { obj.cmd = newSqlCommand(" delete from customer_query where customercode ='" + TextBox1.Text + " '", obj.con); obj.cmd.ExecuteNonQuery(); obj.con.Close(); } catch { Response.Write("<script>alert('Enter correct customercode')</script>"); } } }
New customer entry
using System; using System.Data; using System.Configuration; using System.Collections; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts; using System.Web.UI.HtmlControls; using System.Data.SqlClient; publicpartialclassnewCustoEntry : System.Web.UI.Page { Class1 obj = newClass1(); protectedvoid Page_Load(object sender, EventArgs e) { int i, j; obj.con.Open(); obj.cmd = newSqlCommand("select count(CustID) from Customers", obj.con); obj.dr = obj.cmd.ExecuteReader(); obj.dr.Read(); if (obj.dr.IsDBNull(0)) { Label8.Text = "cust001"; } else { i = int.Parse(obj.dr[0].ToString()); j = i + 1; Label8.Text = "cust00" + j.ToString(); }
obj.con.Close(); } protectedvoid Button2_Click(object sender, EventArgs e) { try { obj.con.Open(); obj.cmd = newSqlCommand(" insert into customers values( '" + Label8.Text + "','" + TextBox2.Text + "', '" + TextBox3.Text + " ', '" + TextBox4.Text + "', '" + TextBox5.Text + "','" + TextBox6.Text + "','" + TextBox7.Text + "')", obj.con); obj.cmd.ExecuteNonQuery(); Response.Write("<script>alert('ragister sucessesfuly.....')</script>"); obj.con.Close(); } catch { Response.Write("<script>alert('Enter correct value')</script>"); } } protectedvoid Button1_Click(object sender, EventArgs e) { TextBox2.Text = ""; TextBox3.Text = "";
TextBox4.Text = ""; TextBox5.Text = ""; TextBox6.Text =""; TextBox7.Text = ""; } } Customerinbox using System; using System.Data; using System.Configuration; using System.Collections; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Web.UI.HtmlControls; using System.Data.SqlClient; publicpartialclassCUSTOMERINBOX : System.Web.UI.Page { Class1 obj = newClass1(); protectedvoid Page_Load(object sender, EventArgs e) {
if (!IsPostBack) { obj.con.Open(); obj.cmd.CommandText = "select mailid,fromuser,subject,attachment,contents,cdate from tbl_mail where touser=(select email from customers where custid='" + Session["custid"].ToString() + "' )"; obj.cmd.Connection = obj.con; obj.da.SelectCommand = obj.cmd; obj.da.Fill(obj.ds, "tbl_mail"); GridView1.DataSource = obj.ds; GridView1.DataBind(); obj.con.Close(); } } publicvoid chsel(bool aa) { foreach (GridViewRow row in GridView1.Rows) { CheckBox ch = newCheckBox(); ch = (CheckBox)row.FindControl("CheckBox2"); ch.Checked = aa; } }
protectedvoid Button1_Click(object sender, EventArgs e) { Label1.Text = ""; string str; msg.Text = ""; for (int i = 0; i < GridView1.Rows.Count; i++) { CheckBox ch = (CheckBox)GridView1.Rows[i].FindControl("CheckBox2");
if (ch.Checked == true) { str = GridView1.Rows[i].Cells[1].Text;
if (i != int.Parse(str.ToString())) { string ww = msg.Text += string.Concat(",", str); Label1.Text = ww.Remove(0, 1); } else { msg.Text = null; } }
del(Label1.Text); Label1.Text = ""; Response.Write("<meta http-equiv='refresh' content ='0.1'/>"); } } publicvoid del(string str) { obj.con.Close(); obj.con.Open(); obj.cmd = newSqlCommand("delete from tbl_mail where mailid in(" + str + ") ", obj.con); try { obj.cmd.ExecuteNonQuery(); Response.Write("<script>alert('deleted sucsessfuly')</script>"); } catch { Response.Write("<script>alert('sorry ! u didn't select any row')</script>"); } obj.con.Close(); } protectedvoid CheckBox1_CheckedChanged(object sender, EventArgs e)
{ if (CheckBox1.Checked == true) { chsel(true); } else { chsel(false); } } } Custsentitems
using System; using System.Data; using System.Configuration; using System.Collections; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Web.UI.HtmlControls;
publicpartialclassCustSentitems : System.Web.UI.Page { Class1 obj = newClass1(); protectedvoid Page_Load(object sender, EventArgs e) { if (!IsPostBack) { obj.con.Open(); obj.cmd.CommandText = "select mailid,touser,subject,attachment,contents,cdate from sentmail where fromuser=(select email from customers where custid='" + Session["custID"].ToString() + "' )"; obj.cmd.Connection = obj.con; obj.da.SelectCommand = obj.cmd; obj.da.Fill(obj.ds, "tbl_mail1"); GridView1.DataSource = obj.ds; GridView1.DataBind(); 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) { select(true); } else { select(false); } } publicvoid delete(string str) { obj.con.Open(); obj.cmd.CommandText = "delete sentmail where mailid in (" + str + ")"; obj.cmd.Connection = obj.con; try {
obj.cmd.ExecuteNonQuery(); } catch { } obj.con.Close(); } protectedvoid Button1_Click(object sender, EventArgs e) { 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("<meta http-equiv='refresh' content='0.1'/>"); } } }
TEST CASE
1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21. 22. 23.
24. 25. 26. 27. 28. 29.
30. Testing levels

Unit Testing
Unit testing focuses verification effort on the smallest unit of software design, the module. The unit testing we have is white box oriented and some modules the steps are conducted in parallel.
1.
WHITE BOX TESTING
This type of testing ensures that 1. 2. 3. 4. All independent paths have been exercised at least once All logical decisions have been exercised on their true and false sides All loops are executed at their boundaries and within their operational bounds All internal data structures have been exercised to assure their validity.
To follow the concept of white box testing we have tested each form .we have created independently to verify that Data flow is correct, All conditions are exercised to check their validity, All loops are executed on their boundaries. 2. BASIC PATH TESTING
Established technique of flow graph with Cyclomatic complexity was used to derive test cases for all the functions. The main steps in deriving test cases were: Use the design of the code and draw correspondent flow graph. Determine the Cyclomatic complexity of resultant flow graph, using formula: V(G)=E-N+2 or V(G)=P+1 or V(G)=Number Of Regions Where V(G) is Cyclomatic complexity, E is the number of edges, N is the number of flow graph nodes, P is the number of predicate nodes.
Determine the basis of set of linearly independent paths.
3. CONDITIONAL TESTING In this part of the testing each of the conditions were tested to both true and false aspects. And all the resulting paths were tested. So that each path that may be generate on particular condition is traced to uncover any possible errors. 4. DATA FLOW TESTING This type of testing selects the path of the program according to the location of definition and use of variables. This kind of testing was used only when some local variable were declared. The definition-use chain method was used in this type of testing. These were particularly useful in nested statements. 5. LOOP TESTING
In this type of testing all the loops are tested to all the limits possible. The following exercise was adopted for all loops:
1. 2. 3. 4.
All the loops were tested at their limits, just above them and just below them. All the loops were skipped at least once. For nested loops test the inner most loop first and then work outwards. For concatenated loops the values of dependent loops were set with the help of connected loop.
5.
Unstructured loops were resolved into nested loops or concatenated loops and tested as above.
1.
2.
Testing Scenarios/ Test case Reports
TEST CASE Test case 1

Module: Admin
Expected: When the Admin logs into the system, the system should check whether the Admin is providing the valid login id or not. If the Admin is not providing the valid id and password, it should not allow the access to the application. If the Admin is providing the valid id and password, it should provide the access to the application. Then admin will add the product in the company and add new supplier also.
Test case 2
Module: Employee Excepted: When the Employee logs into the system, the system should check whether the Employee is providing the valid login id or not. If the Employee is not providing the valid id and password, it should not allow the access to the application. If the employee is providing the valid id and password, it should provide the access to the application and should provide privileges according to the own requirement. Here employee will apply the leave in this leave
two conditions should be satisfied one is from date and another is to date. From date should be same or greater than current date and to date should be same or greater than from date. Then only leave will be applied. Actual: When a employee apply a leave, if that is not approved by HR and again same employee is apply another leave that time when employee will check the leave status, employee can get the last leave information.
Test case 3
Module: HR Excepted: When the HR logs into the system, the system should check whether the HR is providing the valid login id or not. If the HR is not providing the valid id and password, it should not allow the access to the application. If the HR is providing the valid id and password, it should provide the access to the application and should provide privileges according to the Employee requirement. Here HR will approve the leave for the employee and assign the salary for the employee.
Test Case 4
Module: Customer Expected: When the Customer logs into the system, the system should check whether the Customer is providing the valid login id or not. If the Customer is not providing the valid id and password, it should not allow the access to the application. If the Customer is providing the valid id and password, it should provide the access to the application and should provide privileges according to his/her own requirement. Here customer wills porches the product directly.
REPORTS
Salary report
Salary report will be generated by HR. To create salary here three layers is necessary. 6. Salary addition 7. salary deduction 8. total salary 9. first HR will create addition salary, in add salary HRA,DA,other like will be added. 10. Second HR will create deduction salary, in deduct salary PF,others like will be added. 11. Third part total salary will create ,addition salary deduction salary=total salary. After creating total salary employee can view his salary.
Product Details Report

1. 2. 3. Add Product Remove Product Product list
4.
First Admin will create Product Details like Product_id , password , email_id etc and also can remove the Product.
Product_id P001 P002
Product_name Dvd Micro processor
Product_qnty 5 4
Prod_desc Dvd
price 1400
It a micro 3400 processor chip Cpu processor 4200
P003
Dell Processor
CONCLUSION
It has been a great pleasure for me to work on this exciting and challenging project. This project proved good for me as it provided practical knowledge of not only programming in ASP.NET and VB.NET web based application and some extent Windows Application and SQL Server, but also about all handling procedure related with Organization Management System. It also provides knowledge about the latest technology used in developing web enabled application and client server technology that will be great demand in future. This will provide better opportunities and guidance in future in developing projects independently. Jain University, School of Graduate Studies
BENEFITS:
The project is identified by the merits of the system offered to the user. The merits of this project are as follows: 1. 2. Its a web-enabled project. This project offers user to enter the data through simple and interactive forms. This is very helpful for the client to enter the desired information through so much simplicity. 3. The user is mainly more concerned about the validity of the data, whatever he is entering. There are checks on every stages of any new creation, data entry or updating so that the user cannot enter the invalid data, which can create problems at later date. 4. Sometimes the user finds in the later stages of using project that he needs to update some of the information that he entered earlier. There are options for him by which he can update the records. Moreover there is restriction for his that he cannot change the primary data field. This keeps the validity of the data to longer extent. 5. User is provided the option of monitoring the records he entered earlier. He can see the desired records with the variety of options provided by him. 6. From every part of the project the user is provided with the links through framing so that he can go from one option of the project to other as per the requirement. This is bound to be simple and very friendly as per the user is concerned. That is, we can sat that the project is user friendly which is one of the primary concerns of any good project.
BIBLIOGRAPHY
1. FOR .NET INSTALLATION
1. Wrox publication (Thearon Willis )
1.
FOR SQL
1. Beginning Microsoft sqlserver 2005.
2.
1.
FOR ASP.NET
Asp.net for developer.(OReilly) 2. 3. 4. 5. 6. Oreilly - asp.net in a nutshell. Beginning asp.net 3.5 with c#.(Novice) Pro Ado.net 3.5 export voice.(sahil malik) Microsoft ado.net. Pro asp.net 3.5 in c# 2008.

Organization Management System

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Organization Management System

Uploaded by

Copyright:

Available Formats

Showroom Organization Management System

PROJECT NAME Showroom Organization Management System

By Supriya B S (09BCA10064) Sneha Sridhar B (09BCA10078)

Jain University, School of Graduate Studies

Showroom Organization Management System

J. C. Road, Bangalore-560 027

1Jain University, School of Graduate Studies

Guide: Sonali jain

JU, School of Graduate Studies, Bangalore

Showroom Organization Management System

Jain University, School of Graduate Studies

Showroom Organization Management System

Jain University, School of Graduate Studies

Showroom Organization Management System

Jain University, School of Graduate Studies

Showroom Organization Management System

Jain University, School of Graduate Studies

Showroom Organization Management System

Jain University, School of Graduate Studies

Showroom Organization Management System

Jain University, School of Graduate Studies

Showroom Organization Management System

Jain University, School of Graduate Studies

Showroom Organization Management System

easily accessible and willing to provide help whenever required.

Jain University, School of Graduate Studies

Showroom Organization Management System

Jain University, School of Graduate Studies

Showroom Organization Management System

2. OBJECTIVES OF THE PROJECT

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

Jain University, School of Graduate Studies

Showroom Organization Management System

10. DATA FLOW DIAGRAM

11. TABLE DESIGN

12. TABLE RELATIONS/CONSTRAINTS

13. SCREEN SHOT

15. TEST CASE

Showroom Organization Management System

Showroom Organization Management System

HUMAN RESOURCE MODULE :

Jain University, School of Graduate Studies

Showroom Organization Management System

Jain University, School of Graduate Studies

Showroom Organization Management System

Title of the project: Organization Management System

Objectives of the project:

Showroom Organization Management System

Features implementing in Web Page Design:

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

Server side scripting language: Asp.net

Showroom Organization Management System

Database Server with version:Sql server2008

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

Graphic Designing Tools: Html

Jain University, School of Graduate Studies

Showroom Organization Management System

FEATURES OF EXISTING SOFTWARE

FEATURES IMPLEMENTING IN NEW SOFTWARE