Internal Operator Management System

8/3/2019 Internal Operator Management System

http://slidepdf.com/reader/full/internal-operator-management-system 1/31

PROJECT REPORT

ON

INTERNAL OPERATOR MANAGEMENT

SYSTEM

By

Patel Mohit

DEPARTMENT OF COMPUTER ENGINEERING

L.J.POLYTECHNIC, AHMEDABAD2011-2012



CERTIFICATE

This is to certify that Mr. Patel Harsh, Ummati Mehndi Hasan, Chauhan

Devendrasingh having Enrolment No: 096330307120, 096330307134,

096330307098 has completed Part-I IDP Project work having title Internal

Operator Management System. He has undergone the process of shodh yatra,

literature survey and problem Definition. He is supposed to carry out the

residue IDP Part-II work on same Problem during Semester-VI for the final

fulfillment of the IDP work which is Prerequisite to complete Diploma

Engineering.

Guide ± IDP Head of Department



ACKNOWLEDGEMENT

I would like to thank my project guide and team leader Mr.varun sir &

Mr. Shyju sir (Project Manager) at L J Polytechnic for their support at each

and every step during the project. We are also thankful to them for providing a

vision about the system, their patience and suggestions on improved our skill

set through their constant guidance during this project. We have greatly

benefited from their regular critical reviews and inspiration through the work.

We would also like to thank the entire CE team for the unfailing

cooperation and sparing the valuable time and knowledge to assist us in our work and to help us in our work and to help us when needed.

Last but not the least I would like to mention here that I am greatly

indebted to each and everybody who has been associated with my project at

any stage but whose name does not find a place in this acknowledgment. We

also thankful to the all our friends for providing us useful information that was

needed in the project would not been up to the mark.

Last but not the least we would thank to all those persons who helped us

directly or indirectly throughout my project work.

Patel Mohit



PAGE INDEX

Topic Page no.

Abstract1. THEORY

1.1 NEED OF SYSTEM

1.2 ANALYSIS

1.2.1 REQUIREMENT ANALYSIS

1.3 DESIGN

1.3.1 SOFTWARE REQUIREMENT SPECIFICATION

1.4 SYSTEM MODELING

1.4.1 DATABASE DESIGN

1.5 CODING

1.5.1 HARDWARE SPECIFICATION

1.5.2 PLATFORM

1.5.3 PROGRAMMING LANGUAGE USED

1.5.4 SOFTWARE TOOL USED

1.5.5 CODING STYLE FOLLOWED

1.6 CONCLUSION

2. BIBLIOGRAPHY

3. THE OUTLINE OF WORK TO BE CARRIED OUT IN

SEM- VI DURING Part-II

4. SELF OPERISAL FORM



TABLE INDEX

Table Page no.

Login Master

Accessories Master

Dealer Master

Purchase Order Purchase Line Order

Payment Details

Employee Master

Leave Details Master

Salary Master



FIGURE INDEX

Figure Page no.

Model diagram

0-Level DFD

1-Level DFD

2-Level DFD

E-R Diagram



ABSTRACT

INTERNEL ORGANIZATION MANAGEMENT SYSTEM

This portion provides details about the entire Software Requirement

Specification for the Internal Organization Management System. This is

Software which has mainly made for management of a Company. The project

Internal organization Management and maintains the record of row material

company, Category, purchase, sales, client, dealer, stock etc. This Internal

organization Management System is used to keep the stock, sales, purchase,

clients, dealer, and etc detail for a long time without any problem and safe.

The software internal organization Management System also maintains the

employees¶ details. The Internal organization Management System is true

business relates as operated application. Hence, Microsoft Visual Studio 2008.

Which is enriched with much wide integrated development environment is use

to develop it. The Front end interface is much important when designing a

business oriented application, with the help of vb.net language.



CHAPTER 1

INTRODUCTION

1.1 Need of system

This system is needed for saving the man power because the current

system is totally dependent on paper work only. Due to every detail about the

raw material, employee and etc are kept on paper. And every detail and all is

kept on paper so lose of data can be possible due to the natural disaster which

can destroy the data. For maintaining the data appropriable. If the data is lose

due to all this problem there for there is no way of recovering the data so this

will make the data backup and recovery so if any disaster happen there is a

data backup so they can¶t lose their data.

Details problem description

This portion provides details about the entire Software RequirementSpecification for the Internal Organization Management System. In a current

system, all the data are maintained manually in Paper. So they have to

maintain daily transaction in books for each and every transaction. If any

natural disaster happens than it may be a possibility of data lose. More men

power is required in the manual system. Company have problem to manage

their stock of accessories in their store. They also have the problem of

managing their employees. They also have the problem that they don¶t have

the detail about the material which they return to the dealer. They also have the

problem of losing their data about the dealers, stock and employees. They have

all their data in the books and paper that¶s way if they lose the books and paper

then they will also lose all the detail about the material and stocks. To make



the accounting easy. They also have to maintain the record about the material,

stock, sales, purchase, client, dealer, etc. for a long time. To maintain the staff.

Mainly this software is made for the Internal Organization. To Store the

records of the material for a long time and for also to maintain the records of

material stock. To make the accounting easily. To maintain the staff also. This

is Software which has mainly made for management of an Internal

Organization. The Project Internal Organization Management manages and

maintains the records of stock room in the company.



CHAPTER-2

ANALYSIS

2.1Requirement analysis

In contrast to software life cycle models, software process models often

represent a networked sequence of activities, objects, transformations, and

events that embody strategies for accomplishing software evolution. Such

models can be used to develop more precise and formalized descriptions of

software life cycle activities. Their power emerges from their utilization of a

sufficiently rich notation, syntax, or semantics, often suitable for

computational processing.

In the incremental model, there is a good chance that a requirements

error will be recognized as soon as the corresponding software is incorporated

into the system. It is then not a big deal to correct it. The waterfall model relies

on careful review of documents to avoid errors. Once a phase has been

completed, there is limited provision for stepping back. It is difficult to verify

documents precisely and this is, again, a weakness of the waterfall model.

The incremental model is an intuitive approach to the waterfall model.

Multiple development cycles take place here, making the life cycle a ³multi-

waterfall´ cycle. Cycles are divided up into smaller, more easily managed

iterations. Each iteration passes through the requirements, design,

implementation and testing phases.

A working version of software is produced during the first iteration, so you

have working software early on during the software life cycle. Subsequent

iterations build on the initial software produced during the first iteration.



2.3 DESIGN:

SOFTWARE REQUIREMENT SPECIFICTION

Platform Windows XP

Front End Microsoft visual studio 2008

Back End Microsoft access 2007

Language support VB.NET

2.4 SYSTEM MODELING:

Incremental process model:

In contrast to software life cycle models, software process

models often represent a networked sequence of activities, objects,

transformations, and events that embody strategies for accomplishing software

evolution. Such models can be used to develop more precise and formalized

descriptions of software life cycle activities. Their power emerges from their

utilization of a sufficiently rich notation, syntax, or semantics, often suitable

for computational processing. In the incremental model, there is a good chancethat a requirements error will be recognized as soon as the corresponding

software is incorporated into the system. It is then not a big deal to correct it.

The waterfall model relies on careful review of documents to avoid errors.

Once a phase has been completed, there is limited provision for stepping back.

It is difficult to verify documents precisely and this is, again, a weakness of the

waterfall model.

The incremental model is an intuitive approach to the waterfall model.

Multiple development cycles take place here, making the life cycle a ³multi-

waterfall´ cycle. Cycles are divided up into smaller, more easily managed



iterations. Each iteration passes through the requirements, design,

implementation and testing phases.

A working version of software is produced during the first iteration, so you

have working software early on during the software life cycle. Subsequent

iterations build on the initial software produced during the first iteration.

Security or advantages provided by this project:

I have designed the new proposed system to the process of Internal

Organization Management System. This will store all information about our

system. It makes all record in security way so no person can make any change

in a system. This record will be useful for other users instantly. The complete

control of the project is under the hands of authorized person who has the

password to access this project and illegal access is not supposed to deal with.

All the control is under the administrator and the other members have the

rights to just see the records not to change any transaction or entry. Admin

Capable to Create and block New User.

2.4.1 DATABASE DESIGN:

Login-Master Field name Data type Size Constraint DescriptionUser Name Varchar2 20 Primary Key Stores Enter User Name

Password Varchar2 20 Not Null Stores Enter User Password

Sque Varchar2 20 Not Null Stores Security Question

Sans Varchar2 20 Not Null Stores security answer



Accessories Master

Field Name Data Type Size Constraint Description

AccessoryId Number 4 Primary Key Stores Accessories id

Aname Varchar2 50 Not Null Stores Accessories Name

Price Numeric (6,2) Not Null Stores Price of A

ccessories Height Numeric (6,2) Stores Height of Accessories

Width Numeric Stores Width of Accessories

Length Numeric Stores Length of Accessories

Depth Numeric Stores Depth of Accessories

Description Varchar2 100 Not Null Stores Description of

Accessories

Dealer Master


Dealer id Numeric 4 Primary Key Stores dealer id no.

Dname Varchar2 50 Not Null Stores dealer name

Address Varchar2 100 Not Null Stores dealer address

City Varchar2 50 Not Null Stores dealer city name

Phone No. Varchar2 15 Stores dealer office no.

Mobile No. Varchar2 10 Stores dealer mobile no.

Email id Varchar2 50 Stores dealer email id

Purchase-Order Master


Purchase id Numeric 4 Primary Key stores purchase id no.

Date of

purchase

Date time Not Null stores purchase of date

Dealer id Numeric 4 Foreign key Stores dealer id no.

Total Numeric (10,2) Not Null stores total amount

VAT Numeric (4,2) Not Null VAT to the bill

Grand Total Numeric (10,2) Not Null Grand total of bill

Due Numeric (10,2) Not Null



Purchase Line Details


Sr No. Number 4 Primary Key

Purchase id Number 4 Foreign key

accessory id Number 4 Foreign keyQuantity varchar2 Not Null

Price Per Unit Numeric (6,2) Not Null

Total Numeric (10,2) Not Null

Payment Details


Payment id Number 4 Primary Key Stores id

Date of

payment

date time Not Null Stores date of payment

purchase id Number 4 Foreign key Stores id of bill no

Mode of

payment

varchar2 10 Not Null Cash, cheque, DD

Amount Numeric (10,2) Not Null Stores amount of bill

Bank name varchar2 50 Name of bank

Branch varchar2 50 Branch of bank

Cheque no. Number 6 Cheque no

Cheque date date time Date of cheque

Employee Master Table


Employee id Number 4 Primary Key Stores Employee ID

Ename varchar2 50 Not Null Stores Employee name

Address varchar2 100 Not Null Stores address of employee

City varchar2 50 Stores city name

Phone no. varchar2 15 Stores phone no of employee

Mobile no varchar2 10 Stores mobile no of employee

Email id varchar2 50 Stores email id of employee

Date of Birth date time Not Null Date of birth of employee

Date of join date time Not Null Date of joining company

Destination varchar2 20 Not Null

Timing varchar2 20 Not Null Stores the timing of job

Salary Numeric (8,2) Not Null Stores salary of employee

Week off varchar2 15 Not Null week holiday for Employee



Leave Details Master

Salary Master


Salary id Number 4 Primary Key salary id no. of employee

Employee id Number 4 Composite key not null + unique Month of Salary Number 10 Composite key not null + unique

Total Leaves Number 2 not null Total no. of leave where taken

Without paid leaves Number 2 not null

Deduction Numeric (8,2) not null

Commission Numeric (8,2)

Total salary Numeric 12 not null

Salary Payment Master


Salary Payment id Number 4 Primary Key Stores salary sleep id no

Date of Payment date time not null Stores Date of payment to

employee

Salary id Number 4 Foreign key salary id list

Amount numeric (8,2) not null Amount to be paid

Mode of Payment varchar2 10 not null Mode of payment(cash ,

cheque)

Bank Name varchar2 50 Stores name of bank

Branch varchar2 50 Stores branch name of bank

Cheque no. Number 6 Stores the cheque No

Cheque date date time Stores date which is written

in cheque


Leave id Number 4 Primary Key no. of leave where given

Employee id Number 4 Foreign key Stores employee id

Date of leave Date Time Not Null from which date to which

date

Type of leave varchar2 20 Not Null (paid/without paid)



D A T AFLOW DI AGRA M

0-LEVEL DFD



1-LEVEL DFD



2-LEVEL DFD



EN TI TY R EL A TIONSHIP DI AGRA M



2.5 CODING

HARDWARE SPECIFICATION:

Minimum Harddisk : 10GB

Minimum RAM : 256 MB

SOFTWARE TOOLS:

Front-End : Microsoft Visual Basic .Net 2008

Back-End : Microsoft Access 2007

Reporting Tools : Crystal Report (in built)



SCREEN SHOT:

LOGIN FOR M

MDI FOR M



M A STER MENU

PURCH A SE MENU



CH A NGE P A SSWOR D

EMPLOY EE M A STER



COMP A N Y M A STER

PR ODUC T M A STER



VENDOR M A STER

PURCH A SE DE T A IL



P A YMEN T DE T A IL

CONCLUSION

By this management system the company will easily maintain the stock of raw

material (Accessories) which they are using for developing their machines.

And also get the exact details about the stock of raw material. They also

Easily maintain the details of employee. In the system the reports are

generated dynamically so that the administrator gets the details of stock and

employee.



THE OUTLINE OF WORK TO BE CARRIED OUT IN

SEM- VI DURING Part-II

We are going to make project on ³Internal operator management system´. Inthat we are to make solution of the company named ³Hexa Plast´. They have

problems for making details of everything which are required in a one software

system. So we are going to make project on this company.

In this system we have to make all details of company in our project.

We are including company detail about raw material, Company details,

category, purchase, employ, sales, client, dealer, stock, etc« In this we are

going to make a project in details on raw material in that we are going to now

that which type of material are used in our company and also we now that how

many row material are current in our stock room. Then we have to make all

company details and about employee details as well as how many employee

details that how many employee are working in there company from that how

many employee are present in current day and about there working shift time

of all employee what time they were coming time and going means which shift

employee are coming in company and also we have to now that in which shift

how many employee are working in day from that we know how many

employee are not present for in current shift of the day And how many

employee are present in current shift of the day. There for we are going to

make details of all employee management system in our system. So from that

we now that how many employee are present in day. And also we are going to

make which employees are coming in which shift. So we can now that how

many employees are come in current month in the end of the month in details.

We have to make details about purchasing of material and other thing which

are coming in our company. So that they now have many profit and loss of

current month or in the end of the year. We have to make details about sales of



new machine that how many machine where cells in current month. From that

we now that how much stock of machine are present in current date. In our

company were making a parts of plastic testing machine. In that we going to

make different types of machine were made in our company. We are going to

give our software direct to company named ³Hexa Plast´.

In that our system we are also going to make details of all inventory

management system. In that we are going to make all details of stock are

present in our stock room. If there is low material then system will alert that

this inventory is low in our stock room. So if our company need for those

materials that make stock more in inventory department. Also we expect that

we can generate the invoice of the Raw materials which are used by the

company for developing their Product. By the help of invoice Module they

also know exact details of that Raw-material (like: - Price, Warranty).

We also expect that we can generate one database of the employees of

company. The database will generate the fields such as their name,

designation, type of work, their contact details, at which section they are

working etc. There are so many employees in different division or department

in whom are in purchase department, admin department, sales department etc.

all employees detail are maintained.

We also generate reports for Stock of Raw-material from which the employee

will dynamically know how much stock will there in their store. If some raw-

material is out of stock then automatically the report will inform the employee

that material is out of stock. Employee reports (leave note, Salary, etc.) are

also generate.



BIBLIOGRAPHY

[1] G.K.Patnaik and M. M. Gore, ³Design of Compiler for Mobile

Environment and it¶s formalization using Evolving Algebra ´, proceedings of

3rd

IEEE International Conference on Mobile Data Management, Singapore,

January 2002, PP 159-160.

[2] ³Author Guidelines´, http://.computer.org/cspress/instruct.htm

[3] William Stallings, ³Cryptography and Network Security: Principles and

Practices´, Pearson Education, Third Edition

SELF OPERISIAL FORM





Date post:	06-Apr-2018
Category:	Documents
Upload:	mohit-patel
View:	224 times
Download:	0 times

Internal Operator Management System

Documents