Project Report On

PRODUCTION MANAGEMENT SYSTEM

A Project report submitted in partial fulfillment for the award of the
requirements for the award of the degree of

BACHELOR OF COMPUTER APPLICATIONS

Submitted By

R.CHITRA
(Reg.No:15CA0205)
M.VALLI
(Reg.No:15CA0228)
P.NARMATHA
(Reg.No:15CA0215)

Under the guidance of

Mrs. J.VIJAYA BARATHY M.Sc.(C.S), MCA., M.Phil.,

(Assistant Professor in Computer Applications)
Perunthalaivar Kamarajar Arts College

DEPARTMENT OF COMPUTER APPLICATIONS

PERUNTHALAIVAR KAMARAJAR ARTS COLLEGE

KALITHEERTHALKUPPAM,
PUDUCHERRY – 605 107.
APRIL- 2018.
 PERUNTHALAIVAR KAMARAJAR ARTS COLLEGE
(Affiliated to Pondicherry University)
Kalitheerthalkuppam,Puducherry-605107,
Website:www.pkartscollege.org

DEPARTMENT OF COMPUTER APPLICATIONS

BONAFIDE CERTIFICATE

This is to certify that this project work entitled “PRODUCTION MANAGEMENT SYSTEM”
is a bonafide record of work done by R.CHITRA(15CA0205), M.VALLI (Reg.No:15CA0228)
and P.NARMATHA(15CA0215) of III year/VI semester during the Academic year 2017-18 in
partial fulfillment for the award of degree of Bachelor of Computer Applications of the Pondicherry
University.
This work hasn’t been submitted elsewhere for the award of any other degree to the best of our
knowledge.

PROJECT CO-ORDINATOR HEAD OF THE DEPARTMENT

Mrs. J.VIJAYA BARATHY M.Sc. (C.S), Mr. R.VAITTILINGAME M.C.A.,
MCA., M.Phil., . M.Phil.,B.L.I.S.,NET.

Assistant Professor in Computer Applications, Assistant Professor &

Perunthalaivar Kamarajar Arts College. Head of the Department
in Computer Applications,
Perunthalaivar Kamarajar Arts College.

Submitted for the University Examination held on --------------------------

INTERNAL EXAMINER EXTERNAL EXAMINER

CERTIFICATE
ACKNOWLEDGEMENT
 ACKNOWLEDGEMENT

We would like to express our sincere thanks and praise, to the Almighty who
heave showering his/her grave all through our way in completing the project. It is with great
pleasure, deep satisfaction and gratitude that we acknowledge the contribution of several
individuals towards the successful completion of this project
First of all express our deep senses of gratitude to our respected Principal
Dr.W.V.BALAJI,Ph.D., for their kind constant and cheerful encouragement throughout the
course.
We express our profound gratitude to Mr. R.Vaittilingame M.C.A.,
M.Phil.,B.L.I.S.,NET Head of the Department of Computer Application, who has always been a
source of inspiration.
We would like to extend our sincere heartfelt thanks to my internal guide,
Mrs. J. Vijaya Barathy, M.Sc.(C.S)., M.C.A., M.Phil., Department of Computer Applications
for her enthusiastic encouragement, motivation and valuable suggestion throughout the study of
phase, implementation phase and preparation of project report.
We take this opportunity to thank all the staff members of the Department of
Computer Applications for their motivation, co-operation and tremendous guidance to make this
project a success.
We whole-heartedly thank our beloved friends for their suggestions and timely
help throughout our project work. Finally, we thank our parents for their moral support and
encouragement, without whom successful completion of this project would not have been
possible.
R.CHITRA
M.VALLI
P.NARMATHA
ABSTRACT
ABSTRACT
Production Management System is developed for the Appasamy Ocular Devices (P) Ltd, Our
company is one of the leading manufacturers of Surgical instruments and Contact lenses. Our
company will manufacture products based on orders received by dealers. Dealers are located at
different places to sell product to customers and companies require suppliers who can supply raw
material in short time. In order to manage these three areas in parallel, We need a software
application which will reflect stock details with orders and raw material requirement and inform
officials to product stock.

The Production Management System includes several modules. They are described below
as follows,

 LOGIN MODULE
 PURCHASE MODULE
 SALES MODULE
 CUSTOMER RELATIONSHIP MODULE
 HUMAN RESOURCE MODULE
 REPORT GENERATION MODULE

Chapte Description Page no.

r
1 Introduction
1.1 Organization profile
1.2 System specification
 1.2.1 Hardware requirement
1.2.2 Software requirement

2 System Analysis
2.1 Problem Definition
2.2 Existing System
2.2.1.Drawbacks In Existing System
2.3 Proposed System
2.3.1. Features Of Proposed System
3 System Design
3.1 External Design
3.1.1 Menu Layout
3.1.2 Form Layout
3.1.3 Report Layout
3.2 Internal Design
3.2.1 Data Flow Diagram
3.2.2 Use case diagram
3.2.3 Architectural design
3.2.4 Table design
3.2.5 ER diagram
3.3 System Development And Operation
3.3.1 Output Screen
3.3.2 Implementation

4 Testing
4.1.1 Black Box Testing
4.1.2 White Box Testing
4.1.3Unit Testing
4.1.4 Recovery Testing
4.1.5 Security Testing
4.1.6 Performance Testing
4.2.1Integration Testing
4.2.1 Acceptance Testing
4.3 Maintenance
5 Conclusion
6 Appendix
6.1 C#.NET
6.2 MS-SQL SERVER 2008
7 Bibliography
INTRODUCTION
1. INTRODUCTION

1.1 ORGANIZATIONAL PROFILE

Appasamy Associates and Group of companies have been leading manufacturers

and distributors of ophthalmic equipment, microscopes, lasers, IOLs, microsurgical instruments
and pharmaceuticals. Our three decades of work have been widely appreciated throughout the
world. Our dedication to support our products had become a bench mark among the community.

We have dedicated R & D team to fulfill state of the art requirements of the
ophthalmic community. More than 15% expenses are spend on development of new products.
We strive hard to make each and every modern technology and equipment within the easy reach
of ophthalmic surgeons and visions care professionals in India.

Our various manufacturing facilities at Chennai and Pondicherry have got quality
systems certifications, audited by DNV and ITC for ISO 9001 and EN ISO 13485 requirements.
The certifications bodies also provided CE marking for various products and CE compliance
certifications for Class I products. Our Slit Lamps and Keratometer had been awarded UL mark.
SYSTEM SPECIFICATION
1.2 SYSTEM SPECIFICATION

The system is advised to run under the following hardware and software specifications.

1.2.1 Hardware Requirements

Processor : Intel(R) Dual Core

Hard Disk : 20 GB

RAM : 1 GB

Monitor : 15 SVGA color Monitor

Key Board : 110 keys standard Keyboard

Mouse : Logitech

1.2.2 Software Requirements

Operating System : Microsoft Windows 8.1

Front End : Microsoft VisualStudio.Net 2008

Using C#.Net

Back End : Microsoft SQLServer-2008

SYSTEM ANALYSIS
2.2 EXISTING SYSTEM

 Appasamy company, which manufacture surgical instruments and ocular devices and sell
them through dealers.

 The details of each product include name, description, price and status and holds dealer’s
details such as Dealer Name, Address, credit limit and status.

 This company has a warehouse, which stores all the stocks, the finished goods have been
manufactured and ready for dispatch to dealers.

 Thus the cycle is repeated for every week, currently all the above activities are done
manually in this company. The process is a tedious one. And also data is gathered from
various sources because of this errors occur.

2.2.1 LIMITATIONS OF THE EXISTING SYSTEM:

 It is time consuming.

 It leads to error prone results.

 It consumes lot of manpower for better result .

 It lacks data security.

 Retrieval of data takes time.

 Accuracy is less.

 Production of reports will take time.

2.3 PROPOSED SYSTEM

The proposed system is developed in with C#.NET and SQL server as backend to overcome;
disadvantage in the existing system. The primary aim of this new system is to speed up the
transaction. The preparation of reports takes less time since the verifications. The hard copies of
only the necessary documents need to be taken.

2.3.1 FEATURES OF PROPOSED SYSTEM:

1. To generate quick reports

2. To make accurate and efficient calculations for manufacturing products

3. To provide proper information

4. To provide data security

5. To provide huge maintenance for records

6. Flexibility of transactions can be completed in time

SYSTEM DESIGN
3. SYSTEM DESIGNING

The process of design involves “conceiving and planning in the mind” and making a
drawing, pattern, as a sketch of. In software design, there are three distinct types of activities
such as external design, architectural design, and detailed design. Architecture and detailed
designs are collectively referred to as internal design.

3.1 EXTERNAL DESIGN

External design of software involves conceiving, planning out and specifying the
externally observable characteristics of a software product. This characteristics includes user
displays and report format, external data sources and data sinks, and the functional
characteristics, performance requirements and high-level process structure for the product. It
begins during analysis phase and continues into the design phase.
3.1.1 MENU LAYOUT

HOME MENU

CUSTOMER MENU

CUSTOMER PRODUCT PURCHASE HR

Add Customer
View Customer
Request
Exit
PRODUCT MENU

CUSTOMER PRODUCT PURCHASE HR

Report
Add Product
View Product
Exit

PURCHASE MENU

CUSTOMER PRODUCT PURCHASE HR

View Product
Add Vendor
View Vendor
Request
HR MENU

CUSTOMER PRODUCT PURCHASE HR

View Product Department

Search
Employee

Salary
3.1.2 FORM LAYOUT

LOGIN FORM

USER NAME

PASSWORD

LOGIN RESET

CUSTOMER FORM

CUSTOMER ID

NAME

EMAIL
ADD
PHONE NO

CANCEL
COUNTRY

STATE

PINCODE
PRODUCT FORM

PRODUCT ID

PRODUCT NAME

DATE OF PRODUCTION
ADD
FINISHED DATE

CANCEL
STATUS

QUANTITY

TOTAL AMOUNT

VENDOR FORM

VENDOR ID

VENDOR NAME

JOIN DATE
ADD
EMAIL

CANCEL
PHONE NUMBER

ADDRESS
EMPLOYEE FORM

EMPLOYEE ID

EMPLOYEE NAME

AGE
ADD
EMAIL

CANCEL
PHONE NUMBER

ADDRESS

SALARY

DEPARTMENT

ATTENDANCE FORM

EMPLOYEE ID

EMPLOYEE NAME

DEPARTMENT
ADD
DATE

CANCEL
ATTENDANCE
SALARY FORM

EMPLOYEE ID

EMPLOYEE NAME

DEPARTMENT
ADD
DATE

CANCEL
BASIC SALARY

PF

HRA

WORK DAYS

NET SALARY

DEPARTMENT FORM

DEPARTMENT ID

DEPARTMENT

PHONE NO ADD

STRENGTH
CANCEL
3.1.3 REPORT LAYOUT

PROJECT WISE

PROJECT All

View

CUSTOMER WISE

CUSTOMER NAME All

View
EMPLOYEE WISE

EMPLOYEE NAME All

View

VENDOR WISE

VENDOR NAME All

View
3.2.2 DATA FLOW DIAGRAM

The data flow diagram describes the functional model of the system that is to be
developed. It is drawn by dividing it into many levels. Here level-0 and level-4 are given with
description about each level.

Level – 0 Login Form

Level – 1 Customer Module

INPUT PROCESS

INSERT UPDATE DELETE

PROCESSS PROCESS PROCESS

CUSTOMER DATABASE
 Level –2 Purchase Module
STOCK
DETAILS

PURCHASE
VENDOR
DETAILS

REQUEST OF
CUSTOMER

REPORT

Level –3 Product Module

ADD
PRODUCT

PRODUCT
PRODUCT
DETAILS

VIEW
PRODUCT

FINISHED
GOODS
 Level –4 Human Resource Module

PAYROLL
PROCESS

HUMAN RESOURCE
EMPLOYEE
DETAILS

DEPARTMENT
DETAILS

REPORT
 USE CASE DIAGRAM

LOGIN

CUSTOMER

EMPLOYEE

CUSTOMER

ADMIN PRODUCT

SALES
EMPLOYEE

REPORT
 ARCHITECTURAL DESIGN

LOGIN

HOME PAGE

CUSTOMERS PRODUCT PURCHASE

PRODUCTION

REPORTS

EMPLOYEE REPORT
CUSTOMER REPORT PRODUCTS REPORT

LOGOUT
TABLE DESIGN

Table No: 1

Table Name:User Primary Key:U_id

Sl.no Field Name Data Type Size Description

1 Uid Int 5 Unique number

For each record
2 Username Nvarchar 10 Name of the user

3 Password Nvarchar 10 Password of user

4 Usertype Nvarchar 10 Type of the user

Table No: 2

Table Name:Employee Primary Key:E_id

Sl no Field Name Data Type Size Description

1 Eid Nvarchar 5 Unique number for each record
2 Name Nvarchar 10 Name of the employee
3 Age Nvarchar 5 Age of the employee
4 Email Nvarchar 20 Mail ID of the Employee
5 Phone Int 10 Phone number of the employee
6 Address Nvarchar 20 Address of the Employee
7 Salary Int 20 Salary of the Employee
8 Department Nvarchar 10 Department of the employee

Table No: 3

Table Name: Department Primary Key:D_id

 Sl no Field Name Data Type Size Description

1 Did nvarchar 10 Unique number for each record

2 DepartmentName nvarchar 10 Name of the department

3 Phone nvarchar 10 Phone number of each department

4 Strength nvarchar 10 Total employee strength
5 ManagerName nvarchar 10 Name of the manager
Table No: 4

Table Name: Request Primary Key:R_id

Sl no Field Name Data Type Size Description

1 Rid Int 5 Unique number for each record

2 CustomerName nvarchar 10 Name of the Customer

3 DateOfRequest DateTime 10 Request date of customer
4 ProductName nvarchar 10 Name of the requested product
5 Quantity Int 5 Quantity of the requested product
6 Status nvarchar 10 Status of the requested product

Table No: 5

Table Name: Customer Registration Primary Key:R_id

Sl no Field Name Data Type Size Description
 1 Cid nvarchar 5 Unique number for each record

2 Name nvarchar 10 Name of the customer

3 Email nvarchar 20 Mail Id of the Customer

4 Phone Int 10 Phone no of the Customer

5 Country nvarchar 10 Country Of The customer

6 State nvarchar 10 State of the Customer

7 Pincode nvarchar 10 Pincode of the State

8 RequestMode nvarchar 5 Mode of request of customer

9 Payment nvarchar 10 Payment type of Customer

10 ProductStatus nvarchar 10 Status of the product

11 DeliveredDate DateTime 10 Delivery date of the product

Table No: 6

Table Name: Product Primary Key:P_id

Sl no Field Name Data Type Size Description

1 Pid nvarchar 5 Unique number for each record

 2 ProductName nvarchar 10 Name of the product

3 DateOfProduction DateTime 10 Production date of the product

4 DateOfFinished DateTime 10 Finished date of the product

5 State nvarchar 10 State of the product to be sold

6 Quantity nvarchar 10 Quantity of the product

7 TotalCost nvarchar 10 Total cost of the Product

Table No: 7

Table Name: Vendor Primary Key:V_id

Sl no Field Name Data Type Size Description

1 Vid Int 10 Unique number of each record

2 Name nvarchar 10 Name of the vendor

3 JoinDate DateTime 10 Date of joining of the vendor
4 Email nvarchar 20 Mail ID of the vendor
5 Phone Int 10 Phone number of the vendor

6 Address nvarchar 10 Address of the vendor

Table No: 8

Table Name: Sales Primary Key:S_id

Sl no Field Name Data Type Size Description

1 Sid Int 10 Unique number for each record
2 ProductName nvarchar 10 Name of the product
3 No of Goods Int 10 No of available goods
 4 Quantity nvarchar 10 No of quantity of goods
5 Amount nvarchar 10 Total price of Goods

Table No: 9

Table Name: Salary Primary Key:S_id

Sl no Field Name Data Type Size Description

1 SalaryID Int 10 Unique number for each Record

2 Name nvarchar 10 Name of the employee

3 Work_Days nvarchar 5 working days of the employee
4 Total nvarchar 10 Total working days of the Employee

5 Department nvarchar 10 Department of the Empolyee

6 Date DateTime 10 Date of joining of the employee

7 Pf nvarchar 10 Provident fund of the employee

8 Ta nvarchar 10 Travel Allowance of the Employee

3.3.1 SYSTEM DEVELOPMENT AND OPERATION

SAMPLE OUTPUT

Login Page
 Home page

HR Details Page
Add Employee Page

Add Department Page

Salary Calculation Page

Product Purchase Page

Adding Dealer

Product Details Page

Finished Goods View

Customer Relationship
Searching Customer

Customer Request Page

3.3.2 IMPLEMENTATION
Modules:

 USER

 SALES

 PURCHASE

 HUMAN RESOURCE

 CUSTOMER RELATIONSHIP

 REPORT GENERATION

User:

As name indicates, user module defines ,the authenticated persons to use the software. It is
used to provide rights like delete and edit permissions to access page with limited rights.

Sales:

Typical sales process includes processes like Sales, quotation drafting, accepting sales orders,
drafting sales invoices , dispatch of material , tracking pending sales order .

Purchase:

As name indicates, purchase modules take care of all the processes that are part of procurement
of items or raw materials that are required for organization.

Purchase module consist of functionalities like vendor listing, receiving & recording quotations,
preparing purchase orders, tracking the purchase items, updating stocks & various reports .

Customer Relationship :

This module helps to boost the sales performance through better customer service & establishing
the healthy relationship with customers. All the stored details of customer is available in CRM
module.
It helps to manage & track detailed information of the customer like communication
history,calls, meetings, details of purchases made by customer etc.
Human Resource:

Human Resource module helps to HR team for efficient management of human resources.

HR module helps to manage employee information, department details, time & attendance
tracking.

One of the important process in HR module is Payroll System which helps to manage salaries,
payment reports etc.

Report:

Employee reports, Salary bill reports, Customer request reports, Finished goods
Reports, available stock reports.
TESTING
TESTING

4.1 About Testing

Testing involves operation of a system or application under controlled conditions and

evaluating the results (eg, 'if the user is in interface A of the application while using hardware B,
and does C, then D should happen'). The controlled conditions should include both normal and
abnormal conditions. Testing should intentionally attempt to make things go wrong to determine
if things happen when they shouldn't or things don't happen when they should. It is oriented to
'detection'.

Organizations vary considerably in how they assign responsibility for QA and testing.
Sometimes they're the combined responsibility of one group or individual. Also common are
project teams that include a mix of testers and developers who work closely together, with
overall QA processes monitored by project managers. It will depend on what best fits an
organization's size and business structure.

TYPES OF TESTING DONE:

4.1.1 BLACK BOX TESTING

Testing software without any knowledge of the inner workings, structure or language of
the module being tested. Black box tests, as most other kinds of tests, must be written from a
definitive source document, such as a specification or requirements document.

Black Box Testing is testing without knowledge of the internal workings of the item
being tested. For example, when black box testing is applied to software engineering, the tester
would only know the "legal" inputs and what the expected outputs should be, but not how the
program actually arrives at those outputs. It is because of this that black box testing can be
considered testing with respect to the specifications, no other knowledge of the program is
necessary. For this reason, the tester and the programmer can be independent of one another,
avoiding programmer bias toward his own work. For this testing, test groups are often used,
"Test groups are sometimes called professional idiots...people who are good at designing
incorrect data." 1 Also, do to the nature of black box testing, the test planning can begin as soon
as the specifications are written. The opposite of this would be glass box testing, where test data
are derived from direct examination of the code to be tested. For glass box testing, the test
cases cannot be determined until the code has actually been written. Both of these testing
techniques have advantages and disadvantages, but when combined, they help to ensure thorough
testing of the product.

Advantages of Black Box Testing

 More effective on larger units of code than glass box testing

 Tester needs no knowledge of implementation, including specific programming

languages

 Tester and programmer are independent of each other

 Tests are done from a user's point of view

 Will help to expose any ambiguities or inconsistencies in the specifications

 Test cases can be designed as soon as the specifications are complete

4.1.2 WHITE BOX TESTING

White box testing strategy deals with the internal logic and structure of the code. White
box testing is also called as glass, structural, open box or clears box testing. The tests written
based on the white box testing strategy incorporate coverage of the code written branches paths
statement.
In order to implement white box testing, the tester has to deal with the code and hence is
needed to possess knowledge of coding and logic i.e. internal working of the code. White box
test also needs the tester to look into the code and find out which unit/statement/chunk of the
code is malfunctioning And internal logic of the code etc
Advantages of White box testing are:

o As the knowledge of internal coding structure is prerequisite, it becomes very easy to find
out which type of input/data can help in testing the application effectively.
o The other advantage of white box testing is that it helps in optimizing the code
o It helps in removing the extra lines of code, which can bring in hidden defects.

4.1.3 UNIT TESTING

Unit testing deals with testing a unit as a whole. This would test the interaction of
many functions but confine the test within one unit. The exact scope of a unit is left to
interpretation. Supporting test code, sometimes called scaffolding, may be necessary to support
an individual test. This type of testing is driven by the architecture and implementation
teams. This focus is also called black-box testing because only the details of the interface are
visible to the test. Limits that are global to a unit are tested here.

Unit test is designed to ensure that each unit works on its own and that the purpose for
which it was designed for is fulfilled. Each and every module was tested individually with the
test data and error message were displayed for incorrect and sufficient data for entry works. All
validation was tested to correctness. Test data were fed in and results were checked for the
maintenance module, to ensure that all the tables created contained nothing but valid data.
Reverential integrity constraints specified as part of the table definition was also tested.

4.1.4 RECOVERY TESTING

 Many computer-based systems must recover from faults and resume processing within
pre-specified time. In some cases a system must be fault tolerant, i.e. processing faults must not
cause overall system must not cause overall system function to cease. In the cases, a system
failure must be corrected within a specified period of time or severe economic damage will
occur.

4.1.5 SECURITY TESTING

Any computer-based system that manages sensitive information or causes that can
improperly harm individual is a tablet for improper or illegal penetration.
Security testing attempts to verify that protection mechanisms built into a system will, in
facts protect it from improper penetration. During security testing, the tester plays the role of the
individual who desire to penetrate the system. The tester may attempt to acquire passwords
through external clerical means; may attack the system with custom software designed to
break down any defenses that have been construct; may overwhelm the system, thereby denying
services to others, may through insecure data, hoping to find the key system entry.

4.1.6 PERFORMANCE TESTING

For real time and embedded system, software that provides required functions but not
confirm to performances requirements is unacceptable. Performances testing are designed to test
the run-time performance of software within the context of an integrated system. Performance
testing occurs throughout all steps in the testing process. Even at until level, the performances of
an individual module may be accessed as white box test re-conducted. However, it is not unit all
system elements are sully integrated that true performance of a system can be ascertained.

Performance test are sometimes coupled with stress testing and often required other
hardware and software instrumentation. It is often necessary to measure resource utilization. By
incrementing a system, the tester can uncover situations that lead to degradation and possible
system failure.
4.2.1 INTEGRATION TESTING

Software integration testing is the incremental integration testing of two or more

integrated software components on a single platform to produce failures caused by interface
defects.
The task of the integration test is to check that components or software applications, e.g.
components in a software system or – one step up – software applications at the company level –
interact without error.

Test Results: All the test cases mentioned above passed successfully. No defects encountered.

4.8 ACCEPTANCE TESTING

User Acceptance Testing is a critical phase of any project and requires significant
participation by the end user. It also ensures that the system meets the functional requirements.

Test Results: All the test cases mentioned above passed successfully. No defects encountered.
CONCLUSION
5.CONCLUSION

So far the life cycle of the project right from the initialization to its implementation has
been described. This need not mean that the project as reached its ultimate end. The maintanence
of the software developed occupies a very important part in the life of a software product. The
software development can be introduced to the user in the phased manner. Usability of the
system is assured and the performance is better than that of the existing system. Changes is
inevitable when computer based system are built. So the least technology development
forevaluation controlling and making modification can be carried out.

In Our Project, we have a new system is used to reduce the time and cost of the project
the services are to be provided in an efficient, cost effective manner, with the goal of reducing
the time and resources currently required for such tasks. The main function of the system is to
reduce the time estimation and cost estimation, profit of project and measure the billable and
non-billable hours of the working employee.

The result has come up to the level of satisfaction of concerned people. Provisions are
available for easy conversion and modification of information. The system has security
equivalence and itis tamper proof.
APPENDIX
C#.NET

6.1 Features OF. Net

Microsoft .NET is a set of Microsoft software technologies for rapidly building

and integrating XML Web services, Microsoft Windows-based applications, and Web solutions.
The .NET Framework is a language-neutral platform for writing programs that can easily and
securely interoperate. There’s no language barrier with .NET: there are numerous languages
available to the developer including Managed C++, C#, Visual Basic and Java Script. The .NET
framework provides the foundation for components to interact seamlessly, whether locally or
remotely on different platforms. It standardizes common data types and communications
protocols so that components created in different languages can easily interoperate.

“.NET” is also the collective name given to various software components built
upon the .NET platform. These will be both products (Visual Studio.NET and Windows.NET
Server, for instance) and services (like Passport, .NET My Services, and so on).

THE .NET FRAMEWORK

The .NET Framework has two main parts:

1. The Common Language Runtime (CLR).
2. A hierarchical set of class libraries.

The CLR is described as the “execution engine” of .NET. It provides the environment within
which programs run. The most important features are

 Conversion from a low-level assembler-style language, called Intermediate

Language (IL), into code native to the platform being executed on.
 Memory management, notably including garbage collection.
 Checking and enforcing security restrictions on the running code.
 Loading and executing programs, with version control and other such features.
 The following features of the .NET framework are also worth description:
Managed Code

The code that targets .NET, and which contains certain extra Information - “metadata” -
to describe itself. While both managed and unmanaged code can run in the runtime, only
managed code contains the information that allows the CLR to guarantee, for instance, safe
execution and interoperability.

Managed Data

With Managed Code comes Managed Data. CLR provides memory allocation and Deal
location facilities, and garbage collection. Some .NET languages use Managed Data by default,
such as C#, Visual Basic.NET and JScript.NET, whereas others, namely C++, do not. Targeting
CLR can, depending on the language you’re using, impose certain constraints on the features
available. As with managed and unmanaged code, one can have both managed and unmanaged
data in .NET applications - data that doesn’t get garbage collected but instead is looked after by
unmanaged code.

Common Type System

The CLR uses something called the Common Type System (CTS) to strictly enforce type-
safety. This ensures that all classes are compatible with each other, by describing types in a
common way. CTS define how types work within the runtime, which enables types in one
language to interoperate with types in another language, including cross-language exception
handling. As well as ensuring that types are only used in appropriate ways, the runtime also
ensures that code doesn’t attempt to access memory that hasn’t been allocated to it.

Common Language Specification

The CLR provides built-in support for language interoperability. To ensure that you can
develop managed code that can be fully used by developers using any programming language, a
set of language features and rules for using them called the Common Language Specification
(CLS) has been defined. Components that follow these rules and expose only CLS features are
considered CLS-compliant.
THE CLASS LIBRARY

.NET provides a single-rooted hierarchy of classes, containing over 7000 types.

The root of the namespace is called System; this contains basic types like Byte, Double, Boolean,
and String, as well as Object. All objects derive from System. Object. As well as objects, there
are value types. Value types can be allocated on the stack, which can provide useful flexibility.
There are also efficient means of converting value types to object types if and when necessary.

The set of classes is pretty comprehensive, providing collections, file, screen, and
network I/O, threading, and so on, as well as XML and database connectivity.The class library is
subdivided into a number of sets (or namespaces), each providing distinct areas of functionality,
with dependencies between the namespaces kept to a minimum.

LANGUAGES SUPPORTED BY .NET

The multi-language capability of the .NET Framework and Visual Studio .NET
enables developers to use their existing programming skills to build all types of applications and
XML Web services. The .NET framework supports new versions of Microsoft’s old favorites
Visual Basic and C++ (as VB.NET and Managed C++), but there are also a number of new
additions to the family.

Visual Basic .NET has been updated to include many new and improved language
features that make it a powerful object-oriented programming language. These features include
inheritance, interfaces, and overloading, among others. Visual Basic also now supports structured
exception handling, custom attributes and also supports multi-threading.
 Visual Basic .NET is also CLS compliant, which means that any CLS-compliant
language can use the classes, objects, and components you create in Visual Basic .NET.

Managed Extensions for C++ and attributed programming are just some of the
enhancements made to the C++ language. Managed Extensions simplify the task of migrating
existing C++ applications to the new .NET Framework.

C# is Microsoft’s new language. It’s a C-style language that is essentially “C++

for Rapid Application Development”. Unlike other languages, its specification is just the
grammar of the language. It has no standard library of its own, and instead has been designed
with the intention of using the .NET libraries as its own.

Microsoft Visual J# .NET provides the easiest transition for Java-language

developers into the world of XML Web Services and dramatically improves the interoperability
of Java-language programs with existing software written in a variety of other programming
languages.
Active State has created Visual Perl and Visual Python, which enable .NET-aware
applications to be built in either Perl or Python. Both products can be integrated into the Visual
Studio .NET environment. Visual Perl includes support for Active State’s Perl Dev Kit.

Other languages for which .NET compilers are available include

 FORTRAN
 COBOL
 Eiffel
Fig1 .Net Framework

ASP.NET Windows Forms

XML WEB SERVICES

Base Class Libraries
Common Language Runtime
Operating System

C#.NET is also compliant with CLS (Common Language Specification) and supports
structured exception handling. CLS is set of rules and constructs that are supported by the
CLR (Common Language Runtime). CLR is the runtime environment provided by the .NET
Framework; it manages the execution of the code and also makes the development process
easier by providing services.

C#.NET is a CLS-compliant language. Any objects, classes, or components that created in

C#.NET can be used in any other CLS-compliant language. In addition, we can use objects,
classes, and components created in other CLS-compliant languages in C#.NET .The use of
CLS ensures complete interoperability among applications, regardless of the languages used
to create the application.

CONSTRUCTORS AND DESTRUCTORS:

Constructors are used to initialize objects, whereas destructors are used to destroy them.
In other words, destructors are used to release the resources allocated to the object. In
C#.NET the sub finalize procedure is available. The sub finalize procedure is used to
complete the tasks that must be performed when an object is destroyed. The sub finalize
procedure is called automatically when an object is destroyed. In addition, the sub finalize
procedure can be called only from the class it belongs to or from derived classes.
 GARBAGE COLLECTION

Garbage Collection is another new feature in C#.NET. The .NET Framework monitors
allocated resources, such as objects and variables. In addition, the .NET Framework
automatically releases memory for reuse by destroying objects that are no longer in use.

In C#.NET, the garbage collector checks for the objects that are not currently in use by
applications. When the garbage collector comes across an object that is marked for garbage
collection, it releases the memory occupied by the object.

OVERLOADING

Overloading is another feature in C#. Overloading enables us to define multiple procedures

with the same name, where each procedure has a different set of arguments. Besides using
overloading for procedures, we can use it for constructors and properties in a class.

MULTITHREADING:

C#.NET also supports multithreading. An application that supports multithreading can handle
multiple tasks simultaneously, we can use multithreading to decrease the time taken by an
application to respond to user interaction

STRUCTURED EXCEPTION HANDLING

C#.NET supports structured handling, which enables us to detect and remove errors at
runtime. In C#.NET, we need to use Try…Catch…Finally statements to create exception
handlers. Using Try…Catch…Finally statements, we can create robust and effective
exception handlers to improve the performance of our application.

THE .NET FRAMEWORK

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

OBJECTIVES OF . NET FRAMEWORK

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

stored and executed locally on Internet-distributed, or executed remotely.

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

guarantees safe execution of code.

3. Eliminates the performance problems.

There are different types of application, such as Windows-based applications and Web-based
applications.

MICROSOFT SQL SERVER - 2008

6.2 Features of SQL-SERVER

This is a client/server system that consists of a multi-threaded SQL

server that supports different back ends, several different client programs and libraries,
administrative tools, and a wide range of programming interfaces . We also provide SQL Server
as a multi-threaded library which you can link into your application to get a smaller, faster,
easier-to-manage product. There is a large amount of contributed MSSQL software available. It
is very likely that you will find that your favorite application or language already supports the
SQL Server.

TABLE:
A database is a collection of data about a specific topic.

VIEWS OF TABLE:
We can work with a table in two types,

1. Design View
2. Datasheet View

Design View
To build or modify the structure of a table we work in the table design view.
We can specify what kind of data will be hold.

Datasheet View
To add, edit or analyses the data itself we work in tables datasheet view
mode.

QUERY:
 A query is a question that has to be asked the data. Access gathers data that answers the
question from one or more table. The data that make up the answer is either dynaset (if you edit
it) or a snapshot (it cannot be edited).Each time we run query, we get latest information in the
dynaset. Access either displays the dynaset or snapshot for us to view or perform an action on it,
such as deleting or updating.
 BIBLOGRAPHY

7.BIBLIOGRAPHY
 The following books have been referred during the project work and have been
recommended for future reading:

BOOKS

• Beginning ASP.NET 4.5: in C# and VB-by Imar Spaanjaars

• Professional ASP.NET 4.5 in C# and VB - by Jason N. Gaylord, Christian Wenz, Pranav
Rastogi, Todd Miranda, Scott Hanselman
• Robert J.Oberg, ‘Introduction to C# using .NET, PHI, 2002. [Page Nos. 23-44, 134-156].
• Andrew W. Troelsen, ‘Pro C# 2010 and the .NET 4 Platform’, 5 th Edition. [Page Nos. 53-
70,290-313,770-797,].
• Roger S.Pressman(2005), ‘Software Engineering-A Practitioner’s
approach, Sixth Edition, McGRAW Hill International Edition., New York. [Page Nos. 26-39,
365-420, 477-498].

WEBSITES

• http://en.wikipedia.org/wiki/C#.NET
• http://www.csharp-station.com/Tutorial.aspx
• http://www.dotnetspider.com/tutorials
• http://csharp.net-tutorials.com
• http://www.learnvisualstudio.net
• http://www.csharp-station.com/Tutorial.aspx