Beruflich Dokumente
Kultur Dokumente
Submitted By
R.CHITRA
(Reg.No:15CA0205)
M.VALLI
(Reg.No:15CA0228)
P.NARMATHA
(Reg.No:15CA0215)
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.
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
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
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.
Hard Disk : 20 GB
RAM : 1 GB
Mouse : Logitech
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.
It is time consuming.
Accuracy is less.
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.
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.
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
Add Customer
View Customer
Request
Exit
PRODUCT MENU
PURCHASE MENU
View Product
Add Vendor
View Vendor
Request
HR MENU
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
View
EMPLOYEE WISE
View
VENDOR WISE
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.
INPUT PROCESS
CUSTOMER DATABASE
Level –2 Purchase Module
STOCK
DETAILS
PURCHASE
VENDOR
DETAILS
REQUEST OF
CUSTOMER
REPORT
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
PRODUCTION
REPORTS
EMPLOYEE REPORT
CUSTOMER REPORT PRODUCTS REPORT
LOGOUT
TABLE DESIGN
Table No: 1
Table No: 2
Table No: 3
Table No: 5
Table No: 6
Table No: 7
Table No: 8
Table No: 9
SAMPLE OUTPUT
Login Page
Home page
HR Details Page
Add Employee Page
Customer Relationship
Searching Customer
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
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.
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.
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.
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.
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
Test Results: All the test cases mentioned above passed successfully. No defects encountered.
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
“.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 CLR is described as the “execution engine” of .NET. It provides the environment within
which programs run. The most important features are
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.
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.
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
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.
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.
FORTRAN
COBOL
Eiffel
Fig1 .Net Framework
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.
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
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
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.
There are different types of application, such as Windows-based applications and Web-based
applications.
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
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