RUBBER PRODUCTS MANAGEMENT SYSTEMpratimainfosys.weebly.com/uploads/1/0/4/4/10441765/ty… · Web viewThe release also provides enhanced integration with the Oracle WebLogic server,

RUBBER PRODUCTS MANAGEMENT SYSTEM 2012

RUBBER PRODUCTSMANAGEMENT SYSTEM

PROJECT REPORT

MAJOR PROJECT REPORT SUBMITTED BY

Anilkumar Harihar Panda

Seat No. : 2527

Under The Guidance of

Prof. Shaila Sunder

Department Of B.Sc.IT NAGINDAS KHANDWALA COLLEGE OF

SCIENCE

PRATIMA ENTERPRISES Pratima Enterprises

MFG. of Rubber Products

43 | P a g e


A/2, Laxmi Nagar, Link Road, Behind KaaliMata Mandir, Goregaon (W), Mumbai - 400090.

Date:25/04/2012

This is to certify that ANILKUMAR HARIHAR PANDA Student of Third year

B.Sc.(IT) (Bachelor of Science Information Technology) of NAGINDAS KHANDWALA

COLLEGE OF COMMERCE,ARTS & MANAGEMENT STUDIES & SHANTABEN

NAGINDAS KHANDWALA COLLEGE OF SCIENCE (University of Mumbai) have

successfully completed their project entitled “RUBBER PRODUCTS MANAGEMENT

SYSTEM” for PRATIMA ENTERPRISES during in year 2011-12 using NetBeans

7.0.1(JAVA) and MICROSOFT SQL Server 2005.

Place : Mumbai

Company Stamp Pramod Sahu (Proprietor)

ACKNOWLEDGEMENT

It is nearly impossible to thank everyone who is involved in the process of taking theconcept of the ‘Rubber Products Management System’ to a live running project of the same. This book is the direct result of the help of all the people who directly or indirectly helped us in making the project successful.

First of all I would like to thank GOD for providing me with the potential and rightdecision power on right time to make this project possible.

43 | P a g e


The satisfactory completion of this project is not merely due to my efforts but also due to valuable guidance recommended by our internal guides and the requisite infrastructure and facilities made available by our college.

I also express our sincere thanks to the staff of ‘NAGINDAS KANDWALA COLLEGE’ , our project guide ‘Prof. Shaila Sunder’ and ‘Prof. Kiran Raorane’ for their unstinted co-operation and support, which resulted in successful completion of the project.

We wish to express my gratitude to Pratima Enterprises for allowing us to carry out this project. It's really a great pleasure to work for such an organization.

At last I would like to thank my friends who encouraged me and shown a great interest in my work to make me confident about my work and hence getting the great potential to workahead.

iNDEXSr.No. Title Page No. 4.6 Structure Chart Diagram 68-69 1.2 Description Of System 8 1.3 Present System 9 1.4 Limitations of the present system 10 1.5 Proposed system and its advantages 11 1.6 Feasibility Study 12-13 1.7 About The Technology 14-17 1.8 Database (MS SQL) - An Overview 18 1.9 Stakeholders 19 1.10 Gantt Chart 20

43 | P a g e


2 Software Process 21 2.1 Software Development Process Model(Spiral) 22-23 3 System Analysis 24 3.1 Fact Finding Techniques 25-26 3.2 Screen Layouts & Report Layouts 27-36 3.3 Event Table 37-39 3.4 Use Case Diagram and Use Case Description 40-43 3.5 Entity Relationship Diagram 44-46 3.6 Activity Diagram 47-48 3.7 Class Diagram 49 3.8 Object Diagram 50 3.9 Sequence Diagram 51 3.10 Collaboration Diagram 52 3.11 State Chart Diagram 53-54 3.12 Data Flow Diagram(DFD) 55-58 4 System Design 59 4.1 Converting ERD to Tables 60-61 4.2 Component Diagram 62 4.3 Package Diagram 63-64 4.4 Deployment Diagram 65 4.5 System Flow Chart 66-67 4.6 Structure Chart Diagram 68-69

Sr.No. Title Page No. 5 System Coding 70 5.1 Menu Tree 71-72 5.2 List of tables with attributes and constraints 73-76 5.3 Program Description 77 6 System Testing 78-80 6.1 Test Cases 81 6.2 Validations 82-87 7 Cross-platform Java executable wrapper(Launch 4j) 88 8 Future Enhancement 89-91 9 Conclusion 92-93 10 References and Bibliography 94

43 | P a g e


PRELIMINARY43 | P a g e


INVESTIGATION

1. Preliminary Investigation

1.1 Organizational Overview:We are pleased to introduce ourselves as a manufacturer of 'Rubber Parts'. From the

humble beginning as a manufacturer, 'Pratima Enterprises' has come a long way in a short span of time,

in being one of the premier manufacturer and exporter, it has built up its image which symbolizes com-

mitment, quality and class.

Our focus remains on innovation and offers the consistent quality at a price which gives

the best value for money and is constantly adapted to meet the need of the customers. Our company

believes in Quality Service and long term Relationship. We are into business since last three years. No

wonder that every designer front guard or carrier is a work of art, an expression of emotion that has

been honed to perfection.

We always believe innovative in developing ideas and supplying best rubber product

items in the closest possible partnership for creating mutual trust and growth.

43 | P a g e


The diverse range of rubber product we provide is used for several purpose throughout

the world. Countries spanning all continents have acknowledged and appreciated our rubber product

and our services.

Now by the use of Rubber Products Management System provided by the students of

NAGINDAS KANDWALA COLLEGE Mr. Anil Panda. We look forward to enter the global market

in a more systematic manner. Moreover it would be of great help as it automates our current system of

handling and storing records.

1.2 DESCRIPTION OF THE SYSTEM:

My system is based on NetBeans IDE 7.0.1. It is a Rubber Products Management System where the administrator can work on it different processes like Order, Production, Salary, etc. The database lan-guage used is Microsoft SQL Server 2005.Through this system the admin or the user can easily per-form their work. So to make the work run comfortably and to save time and energy this software is being implemented. The administrator can get the record of any at whatever time he needs using this system.

Introduction to the Project:

The main aim of developing Rubber Products Management System is to build a user

friendly, efficient and robust system that will handle all operations related to the company. Here, we

have build a management system to automate the working of the organization. We provide our cus-

tomer’s customer secure access to their own personal information. All the information will be stored in

consistent and structured format which will allow easier retrieval of data. The system is Management

Oriented.

Our application is build to eradicate present file system used by the organization to store

43 | P a g e


and maintain records. The data is stored in a structured and consistent format which can be used by the

organization to generate reports.

The project aims to develop software which will store data about their different Cus-

tomers, Products and Orders. There are different types of services provided by this project like Sales,

Purchasing and Other services. This system provides Various Report Facility That can give a view of

Summary Account with Graphics User Interface (GUI).

Objectives: The objective of the project is to create a system that:

Provides Secure Login.

Provides GUI to user for Data Entry

Handles and store data in consistent and structured format.

Provide user to retrieve and edit data on a click

Less prone to errors

Efficient data storage that will reduce the redundancy of data

Less chances of information Leakage

1.3 PRESENT SYSTEM: In the current system, the company work done is totally manual. First of all the manage-

ment has to manually keep all the information regarding the Stock, Supplier and Customer, etc,

Whenever a Customer enquiries or Order for any product, the management quotation for

that product. The information regarding the quotation is kept in the files. The management the calcu-

lates and make an order form mentioning the amount of raw materials required in regards with the cus-

tomer’s order which is again stored in files for future reference. Before making the order form the sup-

plier details are checked from the files. If for a particular Customer order, the required product is con-

sumed then the remaining product information must be updated in the respective files. When certain

products are purchased then that again must be updated in files. Moreover while delivery of finished

products customer make an Invoice manually.

So, in the current system all business transactions are made manually and many files and

register are maintained and written work is more.

43 | P a g e


1.4 LIMITATION OF THE PRESENT SYSTEM:In the Companies most of the work is done manually.

This involves many limitations such as:

Increases the paper work

The time to access the data increases

Frequent visit by customer for their product query and enquiry

Chances of Information Leakage or Loss of Information increases

Maintaining records is not Integrated

Duplication of data is possible

Transaction’s is very much costly and Insecure

43 | P a g e


1.5 Proposed System and its Advantages:

Proposed System: The proposed system helps the administrator or the user to enter the data very fast and with

greater security. To overcome the difficulties and constraints that are in the present manual system, one can say

that the computerized system can solve many problems to a certain extent. Hence, my project

serves in interacting with many of the work process that is taking place in the company. The

computerization of the inventory control system is more users friendly and reliable.

The project will convert the legacy system used currently by the organization into an automated

system. It will help them in saving all the required data into one organized database System.

Our project will help to generate reports which will help the company to have an overview on

their loss or profit by using the data in the database.

Different modules included in this system are as follows:1. Login form module,2. Order module,3. Production module,

43 | P a g e


4. Inventory module,5. Summary Account module,6. Backup Connection module,7. Payment module, etc.

Advantages of the Proposed System: Computerizing will automate the Order Processing System (OPS).

The system also maintains the description of the suppliers along with its products that they sell.

This will decrease a lot of time in identifying the details of the suppliers

The system gives customer and supplier a unique identity so that they can be easily identified.

Automated computerized system will decrease manual work to some extent and improve work

performance.

There is also a provision for producing reports that management needs for planning and control

which can be then exported to Excel sheets.

Last but not the Least our software allows the management to backup and restore the database.

In Order to be sure that there is least data loss even if the is a database failure or the system

crashes.

I provide many of the features like Notepad, Calculator, Calendar and Time.

1.6 FEASIBILITY STUDY:To fulfill the requirement of the organization, acceptance criteria are needed. The user

specifies all the needs that they want in their system by giving necessary data. When the developer de-

velops the system he has to take all points into consideration and proceed accordingly. Once, when the

system is completed the developer needs to check whether it fulfills the criteria of the user. If it is ful -

filled then the user accepts the system. This acceptance criteria depends not only on the designing but

also the study of feasibility. So it is necessary to study the feasibility of the system. Feasibility study is

to determine whether the solution is feasible (achievable).

Three major areas of feasibility are –

SCHEDULE FEASIBILITY:

Schedule feasibility involves completion of different states of the project in thegiven time.

As my software will be completed in the given time period only, it is feasible forthe client. Also in between, different phase completion will be shown to the client whichensures that the project is being made for them.

43 | P a g e


OPERATIONAL FEASIBILITY:

Operational feasibility includes whether the software is feasible for the operationby the client. The client is having the ability to do the operation of different softwaresused for the system.

Visual Studio 2008 is being used for this software. As the client is having theknowledge to operate this, it is feasible for them.

Microsoft SQL Server 2005 is used to maintain database. Thus the user canmaintain the database as the SQL is well known to the user.

Thus the software is feasible for the operation. Thus the project is operationally feasible.

Sources of information:

Information is gathered from the owner of Pratima Enterprises and available Reports.

Economic feasibility:

Since the project is being pursued as a course assignment, the main costs associated

with it are training materials and computing resources. And as the organization has shown faith in us

and given us a chance to develop a system for them we will cost them only some of their precious time

and some companies resources like their reports.

TECHNICAL FEASIBILITY:

Technical Feasibility involves different requirements for the system. Different hardware and software requirements are specified below as per the system.

HARDWARE & SOFTWARE SPECIFICATION

1: Hardware specification: Our System Required: • 15GB of Hard Disk • 512MB RAM (minimum) • Processor Pentium 4 or newer versions • Printer

2: Software Specification: Our System Required: • Operating System: – Windows XP or higher version

• Java Runtime Environment (Version 1.1 to 7.0) • Front end:- NetBeans IDE 7.0.1 • Back end:- Microsoft SQL Server 2005

Thus the system software is technically feasible for the admin or the user to use it.

43 | P a g e


1.7 ABOUT THE TECHNOLOGY:

JAVA

Java Runtime System:

43 | P a g e

Source Code Compiler .Class file

JVM

Java Interpreter

Java Runtime Environment


Java is a high-level programming language developed by Sun Microsystems. Java was originally called OAK, and was designed for handheld devices and set-top boxes. Oak was unsuccessful so in 1995 Sun changed the name to Java and modified the language to take advantage of the burgeoning World Wide Web.

Java is an object-oriented language similar to C++, but simplified to eliminate language features that cause common programming errors. Java source code files (files with a .java extension) are compiled into a format called byte code (files with a .class extension), which can then be executed by a Java in-terpreter. Compiled Java code can run on most computers because Java interpreters and runtime envir-onments, known as Java Virtual Machines (VMs), exist for most operating systems, including UNIX, the Macintosh OS, and Windows. Byte code can also be converted directly into machine language in-structions by a just-in-time compiler (JIT). Java is a general purpose programming language with a number of features that make the language well suited for use on the World Wide Web.

Principles

There were five primary goals in the creation of the Java language :

1. It should be "simple, object-oriented and familiar"2. It should be "robust and secure"3. It should be "architecture-neutral and portable"4. It should execute with "high performance"5. It should be "interpreted, threaded, and dynamic"

43 | P a g e

http://www.webopedia.com/TERM/J/JIT.html

http://www.webopedia.com/TERM/M/machine_language.html

http://www.webopedia.com/TERM/W/Windows.html

http://www.webopedia.com/TERM/M/Macintosh_computer.html

http://www.webopedia.com/TERM/U/UNIX.html

http://www.webopedia.com/TERM/O/operating_system.html

http://www.webopedia.com/TERM/I/interpreter.html

http://www.webopedia.com/TERM/I/interpreter.html

http://www.webopedia.com/TERM/C/compile.html

http://www.webopedia.com/TERM/S/source_code.html

http://www.webopedia.com/TERM/C/C_plus_plus.html

http://www.webopedia.com/TERM/O/object_oriented_programming_OOP.html

http://www.webopedia.com/TERM/W/World_Wide_Web.html

http://www.webopedia.com/TERM/W/World_Wide_Web.html

http://www.webopedia.com/TERM/S/Sun_Microsystems.html

http://www.webopedia.com/TERM/H/high_level_language.html


NetBeans IDE 7.0.1 Release InformationThe NetBeans IDE is an award-winning integrated development environment available for Windows, Mac, Linux, and Solaris. The NetBeans project consists of an open-source IDE and an application platform that enable developers to rapidly create web, enterprise, desk-top, and mobile applications using the Java platform, as well as PHP, JavaScript and Ajax, Groovy and Grails, and C/C++. The NetBeans project is supported by a vibrant developer community and offers extensive documentation and training resources as well as a diverse selection of third-party plug-in.

Release OverviewNetBeans IDE 7.0 introduces language support for development to the Java SE 7 specifi-cation with JDK 7 language features. The release also provides enhanced integration with the Oracle WebLogic server, as well as support for Oracle Database and GlassFish 3.1. Additional highlights include Maven 3 and HTML5 editing support; a new GridBagLay-out designer for improved Swing GUI development; enhancements to the Java editor, and more.NetBeans IDE 7.0 is available in English, Brazilian Portuguese, Japanese, Russian, and Simplified Chinese.

NetBeans IDE 7.0.1 includes the following notable changes:

Full JDK 7 support: Running NetBeans IDE on top of JDK 7 and support for the final version of the JDK 7 language features

Integration of the recent patches Performance improvements

Feature Highlights

JDK 7

Project Coin support Editor enhancements: Code completion, hints

WebLogic Server

Streamlined and faster deployment to We-bLogic

New server runtime node displaying deployed applications and resources

43 | P a g e


JSF integration with server libraries

Oracle Database

Simplified connection wizard Guided installation to JDBC driver Editing and deployment of stored procedures

GlassFish

GlassFish 3.1 support Domain restart and log viewer for remote

GlassFish Enable and disable deployed applications

Java

Maven 3 support JUnit 4.8.2 integration and various JUnit im-

provements Remote HTTP URLs supported for Javadoc in

libraries and Java platforms New improved visual customizer for Grid-

BagLayout

Java EE

Improved support for CDI, REST services and Java Persistence

New support for Bean Validation Support for JSF component libraries, including

bundled PrimeFaces library Improved editing for Expression Language in

JSF, including code completion, refactoring and hints

Web Languages

HTML5 editing support JSON formatter

PHP

Generate PhpDoc Rename refactoring, Safe Delete Refactoring

43 | P a g e


PHP 5.3 - Support for aliases

C/C++

Easy import of project from user's existing binary

New Project type where user's source files are located on remote system

NetBeans Platform

Annotations for generating Action registrations in the layer

Performance enhancements & tight integration with Profiler

Additional NetBeans API changes

General

Word wrap in Editor Enhanced Profiler integration Less intrusive checking for external changes

when switching between the IDE and other programs.

43 | P a g e


1.8 Database (MS SQL) - An Overview:

A Database is a single organized collection of structured data stored with a minimum of duplication of

data items so as to provide a consistent and controlled pool of data. This data is common to all users of

the system but is independent of programswhich use the data. The independence of database and

programs using it means that they can be changed without changing the other. The users of the data-base

may find it convenient to imagine that they are using integrated file system.

RDBMS

RDBMS is an acronym for relational database management system and can be defined as data pro-

gram

for general purpose data storage and retrieval that organized data into table consisting the same set of

data items(columns). The data is stored in the Kernel to maintain data security. RDBMS is the data-

base

in which multiple tables can be associated or related to one another based on common data items or

files

within the tables. RDBMS provides a way of doing tasks in an understandable and reasonably

uncomplicated manner.

For Example, a name and address file might columns for name, street, city, state, pin and phone num-ber.A record can be created for each person by filling each field. An another table consists of the name, employer’s name and dept. The two tables holds a relationship where each person has an entity.One of the major features of RDBMS is the ability to generate a new file with data from two related files.

Functions of RDBMS : The most important functions of RDBMS are as mentioned below:

Defines database

43 | P a g e


Modifies structure of database Queries the database Adds and deletes the database Controls the database Secure Access from public users Communicate within network Export and import of data.

1.9 STACKHOLDERS:Stackholders are those persons who are successfully involved in completion of the project at the specified time period. Different stackholders included in the completion of the project are :

The Client or Administrator :

He is the one for whom the project is being made. He is successfully engaged for the completion of the software as soon as possible.

The Technical Staff:

They are the people who provides guidance in area of programming language to the programmer. The guidance is given to the student or the programmer so that he can complete the given project properly.

The Creator or Programmer:

The student itself is the programmer who wants the project to be completed in the specified time. He is the main stackholder for the project.

43 | P a g e


10.10 Gantt chart: GANTT CHARTSr.No.

Processes Expected (days)

Completion(days)

Start date End date Dec Jan Feb Mar

Apr

1. System Feasibility

11 10 10/12/2011

20/12/2011

2. Requirements Analysis and Project Planning

20 21 21/12/2011

09/01/2012

3. System Design 20 22 10/01/2012

02/02/2012

4. Coding 45 45 03/02/2012

18/03/2012

5. Testing and Integration

10 8 19/03/2012

27/03/2012

6. Installation, Operations and Maintenance

6 5 20/04/2012

24/04/2012

Completion Period Expected Period

43 | P a g e


SOFTWARE PROCESS

43 | P a g e


2. Software Process

A software process is a set of activities, together with ordering constraints among them, such that if the activities are performed properly and in accordance with the ordering constraints, the desired result is produced.

2.1 Software Development Process Model:

• In the software development process I focus on the activity directly related to production of the software , for example, design, coding, testing.• As the development process specifies the major development and quality control activities that need to be performed in the project, the development process really forms the core of the software process.• The management process is decided based on the development process.• Due to the importance of the development process, the spiral model hava been proposed. Spiral Model

Figure:

43 | P a g e


Introduction:

• The spiral model is another iterative model that has been proposed.• As the name suggests, the activities in this model can be organized like a spiral that has many cycles as shown in Figure.• Each cycle in the spiral begins with the identification of objectives for that cycle, the different alternatives that are possible for achieving the objectives and the constraints that exist.• The next step in the cycle is to evaluate these different alternatives based on the objectives and constraints.• The focus of evaluation in this step is based on the risk perception for the project.• The next step is to develop strategies that resolve the uncertainties and risks. This step may in- volve activities such as benchmarking, simulation, and prototyping.• Next, the software is developed, keeping in mind the risks.• Finally the next stage is planned. Generally, a version of the product is released that contains some capability.• The first version contains some core capability and more features are added to later versions.

Use:

• One effective use of the spiral model is often seen in product development, in which the developers themselves provide the specifications and therefore hava a lot of control on which specifications go

43 | P a g e


in the system and which stay out.

The main reason:

• As businesses are changing very rapidly today, they never really know the complete requirements for the software and there is a need to constantly add new capabilities to the software to adapt the business to changing situations.• Furthermore, customers do not want to invest too much for a long time without seeing returns.• In the current business scenario, it is preferable to see returns continuously of the investment made. The spiral (another iterative) model permits this after each iteration some working software is delivered. This approach to software development is now widely used.

Weaknesses:

• It can have planning overhead.• Cost may increase as work done in one iteration may have to be undone later.• System architecture and structure may suffer as frequent changes are made.

Types of project:

• In a customized software development, where the client has to provide and approve the specific -ations, this process model is becoming extremely popular.

SYSTEM ANALYSIS43 | P a g e


3. SYSTEM ANALYSIS

3.1 Fact finding techniques:

Interview and Questionnaire The first step in developing a database system is to clearly define the mission statement. For

the database project, which defines the major aims of the database system? Once the mission statement is defined, the next activity involves identifying the mission Objectives, which should identify the par-ticular tasks that the database must support.

We started the Interview with the manager of the organization Pratima Enterprises. Following is some part of important conversation between us:

What is the purpose of your company? We offer a wide range of high quality products i.e Rubber Products to clients in India.

Our ability to offer quality products, of course, depends upon the services we provide to our customers.

Why do you feel that you need a database?

43 | P a g e


With the increasing business the level and volume of data is also increasing. As a result it very difficult to handle this huge data in files. Hence we feel a need for a computer system that could handle our data.Moreover it is very hard and time consuming to retrieve data from files.

What kinds of tasks does your company perform in a typical day? Our company is a manufacturer of Rubber Products. We get Orders from our customers

which we then process and if requires, we create a purchase form for the supplier as soon as the supplier delivers the raw materials we send them for production or products which is then packed in our company and finally it then reaches our customer.

What kinds of data do you work with? We mostly have to maintain the orders from the customer. Our main data involves the

sales and the purchase which has to be maintained carefully as it is very important. Last we also have data about our employees, customer, suppliers and products.

What types of reports do you use? Mainly, we generate Account Summary reports.

• Is it a trust based institution? Yes

• Does any operator uses the system? Yes

• How many employees are there in the institution? Less than 50

• At present how the work is maintained in the institution? FILES

• Does the institution give Salary through Cheque / DD also? No

• Do you want any software that maintains your daily work very easily and without any stress?

Yes

43 | P a g e


3.2 SCREEN LAYOUTS & REPORT LAYOUTS:

1. Loading-Rubber Products Management System:

2. Login-Rubber Products Management System:

43 | P a g e


3. Rubber Products Management System (RPMS):

43 | P a g e


4. BackUp Connection:

5. Change User Id and Password:

6. Customer

43 | P a g e


7. Supplier

8. Plant Maintenance and Other Cost:

43 | P a g e


9. RowMaterial:

10.Product:

43 | P a g e


11. Inventory:

12. Order:

43 | P a g e


13. Payment:

14. Salary:

43 | P a g e


15. Employee:

16.Operator:

43 | P a g e


17. Summary Account:

18. Help:

43 | P a g e


19. Notepad:

20. Calculator:

43 | P a g e


21. Calculator:

22. Time:

23. Table(in Plant Maintenance and Other Cost):

3.3 Event Table:

43 | P a g e


● It is implementing system (one or more) event in a tabular format.● Event table consists of following columns: - Event - Trigger - Source - Use Case - Response - Destination

● Event: - It is action affecting the system. Or - It is one that causes the system to do some thing. - Events are external, temporal and state event. - For example : Customer now an item, Customer order an item, etc.

● Trigger: - How the system know that the system occurs? - For example : Item enquiry, New order, etc.

● Source: - How is initiating that event (always external)? - For example : Customer, Operator, Administrator, etc.

● Use Case: - What does the system do that system occurs? - For example : Look up item availability, Place new order, etc.

● Response: - It is availability output. - For example : Item details, Invoice, etc.

● Destination: - Whom that going? - For example : Customer, Operator, Administrator, etc.

Rubber Products Management System Event Table:43 | P a g e


Sr. No. Events Trigger Source Use Case Response Destination

1. Plant maintenance and other cost

Inspection/Investigation

Management Place costdetails

Cost details Data BaseSystem

2. Employeedetails

Employee Management Requires employee details

Employee details

Managementand Data Base System

3. Valuableproduct

Productdemand

Management Place productdetails

Productdetails

Data BaseSystem

4. Administra-tion interaction

Sign In Administrator Collects Process details

Data Data BaseSystem

5. Operatorinteraction

Sign In Operator Data Process Item details Data Basesystem

6. Customer now an item

Item enquiry Customer Look up item availability

Item details Customer

7. Customerorders an item

New order Customer Place new order

Order details Managementand Data Basesystem

8. Check availa -ble (Produc- ts/Row -mate-rials) stock

Stock status Operator Check (Prod-ucts/ Row -materials) stock status

Status details Management

9. Order row-materials

New order Management Create new order

Order details Data BaseSystem

10. Payment tosupplier

Payment Management Enter paymentdetails

Paymentdetails

Data BaseSystem

11. Productproduction

Production Employee Place produc-tion details

Productiondetails

Data BaseSystem

12. Customergive payment

Payment Customer Enter paymentdetails

Payment details

Data BaseSystem

13. Customerorder status

Order status Operator Check orderstatus

Order status Customer

14. Managementorder status

Order status Supplier Check orderstatus

Order status Management

15. Customercancels theorder

Cancel order Customer Cancel order Cancel details Data BaseSystem

Rubber Products Management System Event Table continue:43 | P a g e


Sr. No. Events Trigger Source Use Case Response Destination

16. Managementcancels theorder

Cancel order Management Cancel order Cancel details Data BaseSystem

17. Customer replaces order

Replaceorder

Customer Modify orderdetails

New details Data BaseSystem

18. Managementreplace order

Replaceorder

Management Modify orderdetails

New details Data BaseSystem

19. Managementwants accountdetails

Account System Combine alldetails

Accountdetails

Management

20. Generate Account Report

Report Admin / Operator

GenerateAccountReport

Report Admin / Operator

21. Administratorsign out thesystem

Sign Out Administrator Click button Sign Out Data BaseSystem

22. Operator sign out the system

Sign Out Operator Click button Sign Out Data BaseSystem

3.4 USECASE DIAGRAM:43 | P a g e


• Use Case Diagrams model the functionality of system by using Actors and Use Cases: • Actor is a user of the system. • Use cases are services or functions provided by the system to its users.

• Actor: • An Actor can be described as follows: • Actor is any entity that is external to the system and directly interacts with the system, thus deriving some benefit from the interaction. • Actor can be a human being, a machine, or a software. • Actor is a role that a particular user plays while interacting with the system. • Examples of Actors are End-user (roles), External systems, and External passive objects (entities).

• Use Case: • An Use Case can be defined as a set of activities performed within a system by a User. • Each Use Case: • describes one logical interaction between the Actor and the system. • defines what has changed by the interaction.

• A Use Case diagram has the following elements: • Stick figure: representing an Actor • Oval: representing a Use Case • Association lines: representing communication between Actors and Use Cases

Types of relationships between Use Cases are: • Include • Extend

Include relationship: • «include» stereotype indicates that one use case “includes” the contents of another use case. • Include relationship enables factoring out frequent, common behaviour.

• Extend relationship: • «extend» stereotype indicates that one Use Case is “extended” by another Use Case. • Extend relationship enables factoring out infrequent behaviour or error conditions. • Extend relationship represents optional behavior for a Use Case which will be required only under certain conditions.

UseCase Diagram of Rubber Products Management System:

43 | P a g e


Rubber Products Management System

Rubber Products Management System43 | P a g e


USE CASE DESCRIPTION:43 | P a g e


Use case name Generate Account Report.Scenario Administrator or Operator selects Account report to generate.Triggering event Select Account report.Brief Description When the Administrator wants to generate report, a report is created as per the

details.Actors AdministratorRelated Use Case NoneStack holder StudentPre-Condition At least enter data related to account calculationPost-Condition The account report is generated.Flow of Activity Actor

1. The Administrator wants to generate report.Exception None

NetBeans IDE 7.0.1

23. NAME: LOAD:

OUTPUT: RPMS(MAIN SYSTEM)

43 | P a g e


Use case name Collect Process DetailsScenario Administrator Collect Process DetailsTriggering event Collect Process DetailsBrief Description When the Administrator wants the details, it collects from database through

Data sourceActors AdministratorRelated Use Case NoneStack holder StudentPre-Condition At least enter data related to data collectionPost-Condition Require data collectsFlow of Activity Actor

1. The Administrator wants to collect process detailsException None

Use case name Data Process Scenario Operator processes dataTriggering event Data ProcessBrief Description When the Operator wants the data process, it processes the data in softwareActors OperatorRelated Use Case NoneStack holder StudentPre-Condition At least data which is processingPost-Condition Data processFlow of Activity Actor

1. The Operator wants to process dataException None

Use case name Combine all detailsScenario System combines all detailsTriggering event Combine all detailsBrief Description When the system wants, it combines all detailsActors SystemRelated Use Case NoneStack holder StudentPre-Condition At least data which is combinesPost-Condition Combines all detailsFlow of Activity Actor

1. System combines all dataException None

43 | P a g e


Use case name Place Cost DetailsScenario Management Collect Cost DetailsTriggering event Collect Cost DetailsBrief Description When the Administrator wants to place the cost details, it will place the cost

detailsActors ManagementRelated Use Case NoneStack holder StudentPre-Condition At least cost detailsPost-Condition Place cost detailsFlow of Activity Actor

1. The Management wants to place cost detailsException None

Use case name Place Production detailsScenario Employee place production detailsTriggering event Production detailsBrief Description Employee will place the production details to the databaseActors EmployeeRelated Use Case NoneStack holder StudentPre-Condition At least production detailPost-Condition Place production detailsFlow of Activity Actor

1. Employee will place production detailsException None

Use case name Check Stock StatusScenario Operator check statusTriggering event Stock statusBrief Description Operator will check the stock status for order processActors OperatorRelated Use Case NoneStack holder StudentPre-Condition Stock in companyPost-Condition Check stock statusFlow of Activity Actor

1. Operator will check the stock statusException None

43 | P a g e


3.5 ENTITY RELATIONSHIP (ER) DIAGRAM:

An ER-Diagram (Entity Relationship Diagram) is a graphical model of the data needed by a

system. This included the entities about which information is stored and the relationship among them.

It is produced in structured analysis methods.

An entity is a “thing” or “object” in the real world that is distinguishable from all set of objects.

An entity set is a set of the same type that share same properties, or attributes.E-R diagram consists of

the following major components:

43 | P a g e


The traditional approach to system development places a great deal of emphasis on data storage re-

quirements for the new system. Data storage requirements include the data entities, their attributes, and

the relationships among the data entities. The model used to define the data storage requirements is

called the Entity-Relationship Diagram.

On the Entity-Relationship Diagram:

Rectangles represent data entities

Lines connecting the rectangles show the relationships among data entities.

Ellipse represents the attributes of the entity.

The traditional approach to system development places a great deal of emphasis on data storage

requirements for the new system. Data storage requirements include the data entities, their attributes,

and the relationships among the data entities. The model used to define the data storage requirements

is called the Entity-Relationship Diagram.

43 | P a g e


E-R Diagram of Rubber Products Management System:

43 | P a g e


3.6 ACTIVITY DIAGRAM

43 | P a g e


• An Activity Diagram has the following features: • It resembles a flow chart. • It illustrates the dynamic nature of a system by modeling the flow of control from activity to actiity. • An activity can represent an operation on some class in the system that results in a change in the state of the system.• Activity Diagrams are used: • to model business processes. • to model internal operation of a Use Case / method. • to model work flows and computations.• Notations for Activity Diagrams include: • Activity (State) • Name • Sub-states • State - Sub state relationship • Actions • Entry Action • Exit Action • Transition • Start and End States • Event and Guard Condition • Internal activity • In addition, there are notations for: • Alternate Paths (Branching and Merging) • Parallel Paths (Fork and Join) • Swim lanes• Alternate Paths: • Alternate Paths are shown with the following notations: • Diamond representing a decision with alternate paths • Guard conditions used to label the alternatesParallel Paths are:• Fork represents splitting of a single flow of control into two or more concurrent flows of control.• Join represents the synchronization of two or more flows of control into one sequential flow of control.• Swim lanes: • Swim lanes are used for grouping the related activities into columns.• Each column or “Swim lane” denotes distribution of responsibilities to be handled by different actors / parts of system.

Activity Diagram for Rubber Products Management System:

43 | P a g e


3.7 CLASS DIAGRAM:

43 | P a g e


• Class diagrams define the basic building blocks of a model, namely types, classes, and general material used to construct the full model.• Class diagrams have the following functions:• They describe the static structure of a system.• They show the existence of classes and their relationships.• Classes represent an abstraction of entities with common characteristics.• Relationships may be Generalization, Association, Aggregation, Composition, or Dependency.• Typical uses of Class diagrams are: • To model vocabulary of the system, in terms of system’s abstractions • To model collaborations between classes • To model logical database schema (blueprint for conceptual design of database)

Class diagram of Rubber Products Management System:

3.8 Object Diagrams:

43 | P a g e


• Object Diagrams describe the “static structure” of a system at a particular time.• Objects and Links are the constituents of Object Diagrams.• Object Diagrams are different from Class Diagrams• This is because many objects of same class may exist in the Object Diagram.• Object Diagrams can be used: • to test Class Diagrams for accuracy • to verify system performance at given instance • to optimize performance (especially useful for server objects)

Object Diagram of Rubber Products Management System:

3.9 SEQUENCE DIAGRAM:

43 | P a g e


• Sequence Diagram: • A Sequence diagram describes interactions among classes in terms of an “exchange of messages over time”.• Some of the facts related to Sequence Diagrams are: • Sequence Diagrams are used to depict the time sequence of messages exchanged between objects. • Messages can correspond to operation on class or a event trigger.• Notations of a Sequence diagram include: • LifeLine: It is a vertical dashed line that represents the “lifetime” of an object. • Arrows: They indicate flow of messages between objects. • Activation: It is a thin rectangle showing period of time, during which an object is performing an action.• Direction of arrows: • Direction indicates which object’s method is being called by whom. • A circulating arrow on the Object Lifeline is for a self method – called within the object by itself.• Branch Conditions: • Branch Conditions are depicted as “Guard Conditions” within Square Brackets. • Repetition or Looping depicted as a rectangle, with condition for exiting the loop placed at the bottom left corner.

Sequence Diagram of Rubber Products Management System:

3.10 COLLABORATION DIAGRAM:

43 | P a g e


• A Collaboration Diagram describes interactions among objects in terms of messages.• A Collaboration Diagram: • Emphasizes on the organization of the objects that participate in the interaction. • Is semantically similar to Sequence Diagram. • While Sequence Diagrams show exchange of messages based on time, Collaboration Diagrams are spatial representations. • Sequence Numbers can be used for numbering messages to indicate their time ordering.

Collaboration Diagram of Rubber Products Management System:

3.11 STATE CHART DIAGRAM:

43 | P a g e


• A State Chart Diagram describes the dynamic behaviour of a system in response to external stimuli.• A State Chart Diagram helps: • to model dynamic behaviour of objects based on states. • to model reactive objects, whose states are triggered by specific events. • to describe passive objects, which go through several distinct phases during their life time.• State Chart Diagrams describe how the objects work: • Each object is in a given initial state when it is created • Object may change states (transition) to other states based on some stimuli • State is the condition of an object • Transitions indicate relation between the conditions• Parts of a State are: • Name: Unique name identifying the state • Sub-states: Set of “disjoint sub-states” or “concurrent sub-states”. • State – Sub-state relationship: Useful to understand the modelling of complex behaviours. • Entry action: An action that happens as a result of transition into a state. • Exit action: An action that has to happen immediately before a state change. • Internal activity: Activities that occur within an object while it is in a particular state.• There are some pseudo-states that are used in a State Chart Diagram: • Start State: • It is the default start point for an object state. • Each State Chart Diagram should have exactly one Start State.

• End State: • It indicates Completion State. • It may or may not exist for a State Chart Diagram. • When an object is destroyed, the state is no longer considered. • Transition includes: • Event: The “trigger” • Guard: A logical condition which returns true or false. It is evaluated at the time of event triggering. • Action: Gets executed when transition is fired.

Event [Guard]/ Action

State chart diagram of Rubber Products Management System:

43 | P a g e


3.12 Data Flow Diagram:

43 | P a g e


A data flow diagram (DFD) is a graphical representation of the "flow" of data

through an information system. A data flow diagram can also be used for the visualization of data pro-

cessing (structured design). It is common practice for a designer to draw a context-level DFD first

which shows the interaction between the system and outside entities. This context-level DFD is then

"exploded" to show more detail of the system being modeled.

Data flow diagrams (DFDs) are one of the three essential perspectives of SSADM.

With a dataflow diagram, users are able to visualize how the system will operate, what the system will

accomplish and how the system will be implemented. Old system dataflow diagrams can be drawn up

and compared with the new systems dataflow diagrams to draw comparisons to implement a more effi-

cient system. Dataflow diagrams can be used to provide the end user with a physical idea of where the

data they input, ultimately has an effect upon the structure of the whole system from order to dispatch

to restock how any system is developed can be determined through a dataflow diagram.

There are several common modeling rules that I follow when creating DFDs:

1. All processes must have at least one data flow in and one data flow out.

2. All processes should modify the incoming data, producing new forms of outgoing data.

3. Each data store must be involved with at least one data flow.

4. Each external entity must be involved with at least one data flow.

5. A data flow must be attached to at least one process

Data flow diagram notation:

6. External Entities/Terminators are outside of the system being modeled. Terminators represent

where information comes from and where it goes.

Processes modify the inputs in the process of generating the outputs Data Stores represent a

place in the process where data comes to rest. A DFD does not say anything about the relative

timing of the processes, so a data store might be a place to accumulate data over a year for the

annual accounting process. Data Flows are how data moves between terminators, processes, and

data stores (those that cross the system boundary are known as IO or Input Output Discretions).

7. A data flow diagram (DFD) is a graphical system model that shows all of the main requirements

43 | P a g e


for an information system in one diagram: inputs and outputs, processes, and data storage. Ev-

eryone working on a development project can see all aspects of the system working together at

once with DFD. That is one reason for its popularity. The DFD is also easy to read because it

is graphical model.

8. End Users, management, and all information systems workers typically can read and

interpret the DFD with minimal training.

The four components of a data flow diagram (DFD) are

Context Diagram

A DFD (Data Flow Diagram) that summarizes all processing activity within the system

in a single process symbol is called Context Diagram. A context Diagram is a DFD that describes the

highest-level view of a system are shown in own diagram, with the whole system represented as one

process.

The context diagram provides a good overview of the scope of the system, showing the

system in “context” but it does not show any detail about the processing that takes place inside the sys-

tem. The context diagram for the security company management system is shown below. The inputs &

outputs of the store are shown in the fig. The diagram shows the external entities of the system & how

the data that flows through the system. This helps in determining the basic functionalities.

A context diagram is a top level (also known as Level 0) data flow diagram. It only contains

one process node (process 0) that generalizes the function of the entire system in relationship to exter-

nal entities.

43 | P a g e

http://en.wikipedia.org/wiki/Image:DataFlowDiagram_Notation.png


Context Level Diagram of Rubber Products Management System:

43 | P a g e


1st Level Data Flow Diagram for Rubber Products Management System:

43 | P a g e


SYSTEMDESIGN

43 | P a g e


4. SYSTEM DESIGN

4.1 CONVERTING ERD TO TABLES:

• Customer:

Cus-tomer_Id

Customer_Name

Age Gender MobileNo TelNo Email Office_Add

PINOffice_Add

OfficeTelNo ParmanentAdd

PINParmanent_Add

C101 Ram 35 Male 9876543210

02225786543 [email protected] Mum-bai

400007 02225342278 Mumbai 400008

C102 Suraj 40 Male 8765432198

01125643789 [email protected]

Delhi 111111 01126879800 Delhi 111118

• Supplier:

Supplier_Id

Supplier_Name

Age Gender MobileNo TelNo Email Office_Add

PINOffice_Add

OfficeTelNo ParmanentAdd

PINParmanent_Add

S101 Raj 25 Male 9800543210

02225780043 [email protected] Mumbai 400017 02225342998 Mumbai 400009

S102 Sunder 41 Male 8711432198

01125648889 [email protected] Delhi 111221 01126879810 Delhi 111100

• Employee:

Em-ployee_Id

Em-ployee_Name

DOB Gender

MobileNo TelNo Email JoinDate Local_Add

PIN-Local_Add

ParmaNent_Add

PINParmanent_Add

E101 Raja 1988/07/07

Male 8800543210

02225780041

[email protected] 2010/04/23

Mum-bai

400001 Mum-bai

400001

E102 Rohit 1989/05/04

Male 9711432198

02225648880

[email protected]

2010/04/11

Mum-bai

400000 Mum-bai

400000

Salary Employee_Position15000 Admin10000 Operator

Calendar:• Product:

Product_Id Name PricePerPiece ColorP101 Jar pad 0.80 BlackP102 Summit Ring 5.0 Red

• PlantMaintenanceOtherCost:

SerialNo Description DateTime Cost101 Electricity 2010/05/03 12:12:12 5000102 Transport 2010/04/12 11:01:08 500

• RowMaterial:

RowMaterial_Id Supplier_Id RowMaterial_Name Quantity(Kg.) Color PriceRM1001 S101 001 50 Black 1500RM1002 S101 Silicon Rubber 80 Orange 3000

• ProductionDetails:43 | P a g e


Productionl_Id Product_Id RowMaterial_Id Employee_Id DateTime QuantityPN1001 P101 RM1001 E102 2010/04/23 20:09:09 1500PN1002 P102 RM1001 E102 2010/04/11 20:09:09 300

• SalaryDetails:

Salary_Id DateTime Employee_Id TotalSalarySL101 2010/05/10 12:02:02 E102 8000SL102 2010/06/10 12:00:00 E102 8500

• Operator:

DateTime Employee_Id2010/06/22 10:08:40 E1022010/06/22 11:45:40 E102

• Inventory_Product:

Storage_Id Product_Id Quantity DateTimeSP101 P101 2000 2010/05/10 11:02:02SP102 P102 1000 2010/06/10 13:00:00

• Inventory_RowMaterial:

Storage_Id RowMaterial_Id Quantity(Kg.) DateTimeSP101 RM1001 200 2010/05/10 11:22:02SP102 RM1002 100 2010/06/10 13:30:00

• RecieveOrder:

OrderId Customer_Id Product_Id DataTime QuantityOR101 C101 P102 2010/05/10 11:22:02 2000OR102 C102 P102 2010/05/10 11:23:04 1500

• GiveOrder:

OrderId Supplier_Id RowMaterial_Id DataTime QuantityOG101 S101 RM1001 2010/05/10 11:32:02 200OG102 S102 RM1002 2010/05/10 11:33:04 150

• RecievePayment:

Payment_Id Order_Id Customer_Id DataTime RupeesPR101 OR101 C101 2010/05/10 11:22:02 3000PR101 OR102 C102 2010/05/10 11:23:04 2000

• GivePayment:

Payment_Id Order_Id Supplier_Id DataTime RupeesPG101 OG101 S101 2010/05/10 11:22:02 3000PG101 OG102 S102 2010/05/10 11:23:04 2000

43 | P a g e


4.2 COMPONENT DIAGRAM:

• Component Diagrams describe the organization of components, including source code, run-time (binary) code, and executables.• Component Diagrams: • give the physical view of the system in terms of implementation aspect. • This is important for reusability and performance purpose. • constitute the Components, their interfaces and realizations, and dependencies between components.• Component Diagrams are used: • to depict organizations and dependencies among Component type. • to show allocation of “classes” and “objects” to Components (also referred to as modules) in the physical design of the system. • to indicate the “physical layering” and “partitioning” of the system architecture (during development / implementation phases).• A “Component” is a physical, replaceable part of a system. • A Component packages the implementation, and provides “realization” to a set of “interfaces”. • Component operations can be used only through the Component interface. • A Component typically encompasses • structure and behavior of a “collaboration • of classes” from the system design.• Interfaces: • Interfaces describe a group of operations implemented by Components.• Realization: • Realization is the relationship between an “interface” and the “class” that provides the interface’s services.

Component diagram of Rubber Products Management System:

43 | P a g e


4.3 PACKAGE DIAGRAM:

• A package diagram in the Unified Modeling Language depicts the dependencies between the packages that make up a model.• In addition to the standard UML Dependency relationship, there are two special types of dependencies defined between packages: • package import • package merge• A package import is "a relationship between an importing namespace and a package, indicating that the importing namespace adds the names of the members of the package to its own namespace. By default, an unlabeled dependency between two packages is interpreted as a package import relationship. In this relationship elements within the target package will be imported in source package. A package merge is "a directed relationship between two packages, that indicates that the contents of the two packages are to be combined. It is very similar to Generalization in the sense that the source element conceptually adds the charac- terristics of the target element to its own characteristics resulting in an element that combines the characteristics of both.• Packages containing use cases.• In this relationship if an element exists within source element's definition and target also then the source element's definition's will be expanded to include target element's definitions.• It's different from a class diagram.• Package: It is a general purpose mechanism for organizing model elements & diagrams into groups. It provides an encapsulated namespace within which all the names must be unique. It is used to group semantically related elements. It is a namespace as well as an element that can be contained in other package's namespaces.• Class: It is a representation of objects, that reflects their structure and behavior within the system. It is a template from which actually running instances are created. Classes usually describe logical structure of system.

43 | P a g e


• Interface: It is a specification of behavior. Implementing classes of an interface class are required to support the behavior.• Object: It is an instance of class. It is often used in analysis to represent numerous artifacts and items that exist.• Table: It is a stereotyped class.• Package diagrams can use packages containing use cases to illustrate the functionality of a software system.• Package diagrams can use packages that represent the different layers of a software system to illustrate the layered architecture of a software system. The dependencies between these packages can be adorned with labels / stereotypes to indicate the communication mechanism between the layers.

Package diagram of Rubber Products Management System:

43 | P a g e


4.4 DEPLOYMENT DIAGRAM:

• Deployment Diagrams depict the physical resources in a system including nodes, components, and connections.• Deployment Diagrams help to: • capture the hardware topology. • model the distributed systems.• Node: • A Node represents: • a computational resource • a physical resource that executes code components• A set of components are allocated to a Node.• Communication Path represents physical connections between nodes.

Deployment Diagram of Rubber Products Management System:

43 | P a g e


4.5 SYSTEM FLOW CHART:

• A flowchart is a type of diagram that represents an algorithm or process, showing the steps as boxes of various kinds, and their order by connecting these with arrows. • This diagrammatic representation can give a step-by-step solution to a given problem. • Process operations are represented in boxes, and arrows connecting them represent flow of control. • Data flows are not typically represented in a flowchart, in contrast with data flow diagrams; rather, they are implied by the sequencing of operations. • Flowcharts are used in analyzing, designing, documenting or managing a process or program in various fields.• Flowcharts are used in designing and documenting complex processes. • Like other types of diagram, they help visualize what is going on and thereby help the viewer to un-derstand a process, and perhaps also find flaws, bottlenecks, and other less-obvious features within it. • There are many different types of flowcharts, and each type has its own repertoire of boxes and nota- tional conventions. • The two most common types of boxes in a flowchart are: • a processing step, usually called activity, and denoted as a rectangular box • a decision, usually denoted as a diamond.• A flowchart is described as "cross-functional" when the page is divided into different swimlanes de- scribing the control of different organizational units. • A symbol appearing in a particular "lane" is within the control of that organizational unit. This tech- nique allows the author to locate the responsibility for performing an action or making a decision correctly, showing the responsibility of each organizational unit for different parts of a single process.• Flowcharts depict certain aspects of processes and they are usually complemented by other types of diagram. For instance, Kaoru Ishikawa defined the flowchart as one of the seven basic tools of quality 43 | P a g e


control, next to the histogram, Pareto chart, check sheet, control chart, cause-and-effect diagram, and the scatter diagram. Similarly, in UML, a standard concept-modeling notation used in software devel opment, the activity diagram, which is a type of flowchart, is just one of many different diagram types.• Nassi-Shneiderman diagrams are an alternative notation for process flow.• Common alternate names include: flowchart, process flow chart, functional flow chart, process map, process chart, functional process chart, business process model, process model, process flow diagram, work flow diagram, business flow diagram.

System Flow Chart diagram for Rubber Products Management System:

43 | P a g e


43 | P a g e


4.6 STRUCTURE CHART DIAGRAM:A Structure Chart (SC) in software engineering and organizational theory, is a chart which shows the breakdown of a system to its lowest manageable levels. They are used in structured programming to arrange program modules into a tree. Each module is rep-resented by a box, which contains the module's name. The tree structure visualizes the relationships between modules.A structure chart is a top-down modular design tool, constructed of squares representing the different modules in the system, and lines that connect them. The lines represent the connection and or ownership between activities and subactivities as they are used in organization charts.In structured analysis structure charts, according to Wolber (2009), “are used to specify the high-level design, or architecture, of a computer program. As a design tool, they aid the programmer in dividing and conquering a large software problem, that is, recursively breaking a problem down into parts that are small enough to be understood by a human brain. The process is called top-down design, or func-tional decomposition. Programmers use a structure chart to build a program in a manner similar to how an architect uses a blueprint to build a house. In the design stage, the chart is drawn and used as a way for the client and the various software designers to communicate. During the actual building of the pro-gram (implementation), the chart is continually referred to as "the master-plan".A structure chart depicts the size and complexity of the system, and number of readily identifiable functions and modules within each function and whether each identifiable function is a manageable entity or should be broken down into smaller components.A structure chart is also used to diagram associated elements that comprise a run stream or thread.It is often developed as a hierarchical diagram, but other representations are allowable. The representation must describe the breakdown of the configuration system into subsystems and the lowest manageable level. An accurate and complete structure chart is the key to the determination of the configuration items, and a visual representation of the configuration system and the internal interfaces among its CIs(define CI clearly). During the configuration control process, the structure chart is used to identify CIs and their associated artifacts that a proposed change may impact.

43 | P a g e


Structure Chart diagram for Rubber Products Management System:

43 | P a g e


SYSTEMCODING

5. SYSTEM CODING

43 | P a g e


5.1 MENU TREE:

1: Menu Tree

Main Module (RPMS) File Back to SingIn Exit Change SignIn Account Change SignIn Account Tools Backup Connection Employee Operator

Supplier Customer PlantMaintenance/Other Cost RawMaterial Product Inventory Order Production Payment Employee Salary Account Summary

Notepad Notepad

Calculator Calculator Help Help AboutUs AboutUs

2: Menu Tree

43 | P a g e


Notepad (in RPMS) File New

Open Save Exit

Edit Cut Copy Paste

5.2 List of Tables With Attributes & Constraints:

43 | P a g e


TABLE NAME: AdministratorAccount

COLUMN NAME DATA TYPE FIELD LENGTH CONSTRAINT Admin_Id varchar 25 Primary Key and Not Null Admin_Password varchar 25 Not Null

TABLE NAME: UserAccount

COLUMN NAME DATA TYPE FIELD LENGTH CONSTRAINT User_Id varchar 25 Primary Key and Not Null User_Password varchar 25 Not Null

TABLE NAME: TotalInvestment

COLUMN NAME DATA TYPE FIELD LENGTH CONSTRAINT Total_Inv bigint - -

TABLE NAME: Customer

COLUMN NAME DATA TYPE FIELD LENGTH CONSTRAINT Customer_Id varchar 10 Primary Key and Not Null Customer_Name varchar 15 Not Null Age int - Not Null Gender varchar 6 Not Null MobileNo varchar 10 Not Null TelNo varchar 11 Not Null Email varchar 50 Not Null OfficeAddress varchar 30 Not Null PIN_OfficeAddress int - Not Null OfficeTelNo varchar 11 Not Null ParmanentAddress varchar 30 - PIN_ParmanentAddess int - -

TABLE NAME: PlantMaintenance

COLUMN NAME DATA TYPE FIELD LENGTH CONSTRAINT SerialNo int - Primary Key and Not Null Description varchar 50 Not Null DateTime DateTime - Not Null Cost bigint - Not Null

TABLE NAME: EmployeeDetails

43 | P a g e


COLUMN NAME DATA TYPE FIELD LENGTH CONSTRAINT Employee_Id varchar 15 Primary Key and Not Null Employee_Name varchar 15 Not Null DOB varchar 14 Not Null Gender varchar 6 Not Null MobileNo varchar 10 Not Null TelNo varchar 11 Not Null Email varchar 50 Not Null JoinDate varchar 14 Not Null Address varchar 30 Not Null PINLocal_Add int - Not Null Parmanent_Add varchar 30 Not Null PINParmanent_Add int - Not Null Salary varchar 10 Not Null Employee_Position varchar 25 Not Null

TABLE NAME: Operator

COLUMN NAME DATA TYPE FIELD LENGTH CONSTRAINTDateTime - - Primary Key and Not NullEmployee_Id varchar 15 Foreign Key and Not Null

TABLE NAME: Supplier

COLUMN NAME DATA TYPE FIELD LENGTH CONSTRAINT Supplier_Id varchar 10 Primary Key and Not Null Supplier_Name varchar 15 Not Null Age int - Not Null Gender varchar 6 Not Null MobileNo varchar 10 Not Null TelNo varchar 11 - Email varchar 50 - OfficeAddress varchar 30 Not Null PIN_OfficeAddress int - Not Null OfficeTelNo varchar 11 Not Null ParmanentAddress varchar 30 - PIN_ParmanentAddess int - -

TABLE NAME: Product

43 | P a g e


COLUMN NAME DATA TYPE FIELD LENGTH CONSTRAINT Product_Id varchar 15 Primary Key and Not Null Name varchar 25 Not Null PricePerPiece float - Not Null Color varchar 25 Not Null

TABLE NAME: RowMaterial

COLUMN NAME DATA TYPE FIELD LENGTH CONSTRAINT RowMaterial_Id varchar 10 Primary Key and Not Null Supplier_Id varchar 10 Foreign Key and Not Null RowMaterial_Name varchar 15 Not Null Quantity bigint - Not Null Color varchar 15 Not Null Price varchar 7 Not Null

TABLE NAME: SalaryDetails

COLUMN NAME DATA TYPE FIELD LENGTH CONSTRAINT Salary_Id varchar 15 Primary Key and Not Null DateTime DateTime - Not Null PricePerPiece varchar 15 Foreign Key and Not Null TotalSalary bigint - Not Null

TABLE NAME: GiveOrder

COLUMN NAME DATA TYPE FIELD LENGTH CONSTRAINT OrderId varchar 100 Primary Key and Not Null Supplier_Id varchar 10 Foreign Key and Not Null RowMaterial_Id varchar 10 Foreign Key and Not Null Quantity bigint - Not Null DateTime DateTime - Not Null

TABLE NAME: RecieveOrder

COLUMN NAME DATA TYPE FIELD LENGTH CONSTRAINT OrderId varchar 100 Primary Key and Not Null Customer_Id varchar 10 Foreign Key and Not Null Product_Id varchar 15 Foreign Key and Not Null Quantity bigint - Not Null DateTime DateTime - Not Null

TABLE NAME: ProductionDetails

43 | P a g e


COLUMN NAME DATA TYPE FIELD LENGTH CONSTRAINTProduction_Id varchar 15 Primary Key and Not NullProduct_Id varchar 15 Foreign Key and Not NullRowMaterial_Id varchar 10 Foreign Key and Not NullEmployee_Id varchar 15 Foreign Key and Not NullDateTime DateTime - Not NullQuantity bigint - Not Null

TABLE NAME: Inventory_Product

COLUMN NAME DATA TYPE FIELD LENGTH CONSTRAINT Storage_Id varchar 15 Primary Key and Not Null Product_Id varchar 15 Foreign Key and Not Null Quantity bigint - Not Null DateTime DateTime - Not Null

TABLE NAME: Inventory_RowMaterial

COLUMN NAME DATA TYPE FIELD LENGTH CONSTRAINT Storage_Id varchar 15 Primary Key and Not Null RowMaterial_Id varchar 10 Foreign Key and Not Null Quantity bigint - Not Null DateTime DateTime - Not Null

TABLE NAME: GivePayment

COLUMN NAME DATA TYPE FIELD LENGTH CONSTRAINT Payment_Id varchar 100 Primary Key and Not Null OrderId varchar 100 Foreign Key and Not Null Supplier_Id varchar 10 Foreign Key and Not Null DateTime DateTime - Not Null Rupees bigint - Not Null

TABLE NAME: RecievePayment

COLUMN NAME DATA TYPE FIELD LENGTH CONSTRAINT Payment_Id varchar 100 Primary Key and Not Null OrderId varchar 100 Foreign Key and Not Null Customer_Id varchar 10 Foreign Key and Not Null DateTime DateTime - Not Null Rupees bigint - Not Null

5.3 PROGRAM DESCRIPTION:

43 | P a g e


2. NAME: CREATE USER ACCOUNT

INPUT: USERNAME AND PASSWORD OUPUT: ERROR MESSAGE OR USER ID AND PASSWORD

IF TEXTFIELDS ARE BLANK THEN GIVE ERROR MESSAGE OF BLANK FIELD ELSEIF USERNAME AND PASSWORD DOESNOT EXIT THEN CREATE USE ID AND PASSWORD ELSE GIVE ERROR MESSAGE ENDIF

3. NAME: SYSTEM LOGIN

INPUT: USERNAME AND PASSWORD OUPUT: ERROR MESSAGE OR NEXT PAGE

IF TEXTFIELDS ARE BLANK THEN GIVE ERROR MESSAGE OF BLANK FIELD ELSEIF USERNAME AND PASSWORD DOESNOT MATCH THEN GIVE ERROR MESSAGE OF INCORRECT USERNAME AND PASSWORD ELSEIF USERNAME AND PASSWORD MATCHES THEN GIVE ACCESS TO NEXT PAGE ENDIF

4. NAME: CHANGE USER ID AND PASSWORD

INPUT: CURRENT_USER ID AND PASSWORD, NEW USER ID AND PASSWORD, CONFIRM USER ID AND PASSWORD OUTPUT: ERROR MESSAGE OR USER ID AND PASSWORD CHANGE.

IF TEXTFIELDS ARE BLANK THEN GIVE ERROR MESSAGE OF BLANK FIELD ELSEIF CURRENT_PASSWORD DOESNOT MATCH THEN GIVE ERROR MESSAGE OF CURRENT_PASWORD ELSEIF NEW_PASSWORD IS NOT CONFIRMED AGAIN THEN GIVE ERROR MESSAGE OF NEW_PASSWORD MISMATCH ELSE ALL FIELDS ARE PROPERLY FILLED AND MATCHED THEN CHANGE USER ID AND PASSWORD ENDIF

24. NAME: CUSTOMER:

INPUT: CUSTOMER ID, NAME, AGE, GENDER, MOBILE NO, TEL NO, EMAIL, OFFICE ADDRESS, PIN OFFICE ADDRESS, OFFICE

43 | P a g e


TEL, PARMANENT ADDRESS, PIN PARMANENT ADDRESS OUPUT: ADD, REMOVE, MODIFY, SHOW, SEARCH, FIRST, NEXT, PREVIOUS, LASTIF TEXTFIELDS ARE BLANK THEN GIVE ERROR MESSAGE OF BLANK FIELDELSEIF ENTER DUPLICATES PRIMARY CONSTAINT GIVE ERROR MESSAGE OF DUPLICATE CONSTRAINTELSEIF CONNECTION FAIL GIVE CONNECTION ERRORELSE CUSTOMER DETAILS ADD, REMOVE, MODIFY, SHOW, SEARCH, FIRST, NEXT, PREVIOUS, LASTENDIF

25. NAME: SUPPLIER:

INPUT: SUPPLIER ID, NAME, AGE, GENDER, MOBILE NO, TEL NO, EMAIL, OFFICE ADDRESS, PIN OFFICE ADDRESS, OFFICE TEL, PARMANENT ADDRESS, PIN PARMANENT ADDRESS OUPUT: ADD, REMOVE, MODIFY, SHOW,SEARCH, FIRST, NEXT, PREVIOUS, LASTIF TEXTFIELDS ARE BLANK THEN GIVE ERROR MESSAGE OF BLANK FIELDELSEIF ENTER DUPLICATES PRIMARY CONSTAINT GIVE ERROR MESSAGE OF DUPLICATE CONSTRAINTELSEIF CONNECTION FAIL GIVE CONNECTION ERRORELSE SUPPLIER DETAILS ADD, REMOVE, MODIFY, SHOW, SEARCH, FIRST, NEXT, PREVIOUS, LASTENDIF

26. NAME: EMPLOYEE:

INPUT: EMPLOYEE ID, NAME, DOB, GENDER, MOBILE NO, TEL NO, EMAIL, JOIN DATE, LOCAL ADDRESS, PIN LOCAL AD-DRESS, PARMANENT ADDRESS, PIN PARMANENT ADDRESS, BASIC SALARY, POSITION OUPUT: ADD, REMOVE, MODIFY, SHOW, SEARCH, FIRST, NEXT, PREVIOUS, LASTIF TEXTFIELDS ARE BLANK THEN GIVE ERROR MESSAGE OF BLANK FIELDELSEIF ENTER DUPLICATES PRIMARY CONSTAINT GIVE ERROR MESSAGE OF DUPLICATE CONSTRAINTELSEIF CONNECTION FAIL GIVE CONNECTION ERRORELSE EMPLOYEE DETAILS ADD, REMOVE, MODIFY, SHOW, SEARCH, FIRST, NEXT, PREVIOUS, LASTENDIF

27. NAME: PRODUCT:

INPUT: PRODUCT ID, NAME, PRICE PER PIECE, COLOROUPUT: ADD, REMOVE, MODIFY, SHOW, SEARCH, FIRST, NEXT, PREVIOUS, LASTIF TEXTFIELDS ARE BLANK THEN GIVE ERROR MESSAGE OF BLANK FIELDELSEIF ENTER DUPLICATES PRIMARY CONSTAINT GIVE ERROR MESSAGE OF DUPLICATE CONSTRAINTELSEIF CONNECTION FAIL GIVE CONNECTION ERRORELSE PRODUCT DETAILS ADD, REMOVE, MODIFY, SHOW, SEARCH, FIRST, NEXT, PREVIOUS, LASTENDIF

28. NAME: PLANT MAINTENANCE OTHER COST:

INPUT: SERIAL NO, DESCRIPTION, DATETIMEOUPUT: ADD, REMOVE, MODIFY, SHOW, SEARCH, FIRST, NEXT, PREVIOUS, LASTIF TEXTFIELDS ARE BLANK THEN GIVE ERROR MESSAGE OF BLANK FIELDELSEIF ENTER DUPLICATES PRIMARY CONSTAINT GIVE ERROR MESSAGE OF DUPLICATE CONSTRAINTELSEIF DATETIME FORMATE INCORECT THEN GIVE ERROR MESSAGE OF INCORECT DATETIMEELSEIF CONNECTION FAIL GIVE CONNECTION ERRORELSE PLANT MAINTENANCE OTHER COST DETAILS ADD, REMOVE, MODIFY, SHOW, SEARCH, FIRST, NEXT, PREVIOUS, LASTENDIF

29. NAME: SALARY:

INPUT: SALARY ID, DATETIME, EMPLOYEE ID,TOTAL SALARYOUPUT: ADD, REMOVE, MODIFY, SHOW, SEARCH, FIRST, NEXT, PREVIOUS, LASTIF TEXTFIELDS ARE BLANK THEN GIVE ERROR MESSAGE OF BLANK FIELDELSEIF ENTER DUPLICATES PRIMARY CONSTAINT GIVE ERROR MESSAGE OF DUPLICATE CONSTRAINTELSEIF DATETIME FORMATE INCORECT THEN GIVE ERROR MESSAGE OF INCORECT DATETIMEELSEIF CONNECTION FAIL GIVE CONNECTION ERRORELSE PRODUCT DETAILS ADD, REMOVE, MODIFY, SHOW, SEARCH, FIRST, NEXT, PREVIOUS, LASTENDIF

30. NAME: PRODUCTION:

INPUT: PRODUCTION ID, PRODUCT ID,ROW MATERIAL ID, EMPLOYEE ID, DATETIME, QUANTITYOUPUT: ADD, REMOVE, MODIFY, SHOW, SEARCH, FIRST, NEXT, PREVIOUS, LASTIF TEXTFIELDS ARE BLANK THEN GIVE ERROR MESSAGE OF BLANK FIELDELSEIF ENTER DUPLICATES PRIMARY CONSTAINT GIVE ERROR MESSAGE OF DUPLICATE CONSTRAINTELSEIF CONNECTION FAIL GIVE CONNECTION ERRORELSE PRODUCT ION DETAILS ADD, REMOVE, MODIFY, SHOW, SEARCH, FIRST, NEXT, PREVIOUS, LASTENDIF

31. NAME: ROW MATERIAL:

INPUT: ROW MATERIAL ID, SUPPLIER ID, ROW MATERIAL NAME, QUANTITY, COLOR, PRICEOUPUT: ADD, REMOVE, MODIFY, SHOW, SEARCH, FIRST, NEXT, PREVIOUS, LASTIF TEXTFIELDS ARE BLANK THEN GIVE ERROR MESSAGE OF BLANK FIELDELSEIF ENTER DUPLICATES PRIMARY CONSTAINT GIVE ERROR MESSAGE OF DUPLICATE CONSTRAINT

43 | P a g e


ELSEIF CONNECTION FAIL GIVE CONNECTION ERRORELSE ROW MATERIAL ADD, REMOVE, MODIFY, SHOW, SEARCH, FIRST, NEXT, PREVIOUS, LASTENDIF

32. NAME: OPERATOR:

INPUT: DATETIME, EMPLOYEE IDOUPUT: ADD, REMOVE, MODIFY, SHOW, SEARCH, FIRST, NEXT, PREVIOUS, LASTIF TEXTFIELDS ARE BLANK THEN GIVE ERROR MESSAGE OF BLANK FIELDELSEIF ENTER DUPLICATES PRIMARY CONSTAINT GIVE ERROR MESSAGE OF DUPLICATE CONSTRAINTELSEIF DATETIME FORMATE INCORECT THEN GIVE ERROR MESSAGE OF INCORECT DATETIMEELSEIF CONNECTION FAIL GIVE CONNECTION ERRORELSE OPERATOR DETAILS ADD, REMOVE, MODIFY, SHOW, SEARCH, FIRST, NEXT, PREVIOUS, LAST, AVILABLE TOOLSENDIF

33. NAME:INVENTORY:

INPUT: STORAGE ID, PRODUCT ID, QUANTITY, DATETIMEOUPUT: ADD, REMOVE, MODIFY, SHOW, SEARCH, FIRST, NEXT, PREVIOUS, LASTIF TEXTFIELDS ARE BLANK THEN GIVE ERROR MESSAGE OF BLANK FIELDELSEIF ENTER DUPLICATES PRIMARY CONSTAINT GIVE ERROR MESSAGE OF DUPLICATE CONSTRAINTELSEIF DATETIME FORMATE INCORECT THEN GIVE ERROR MESSAGE OF INCORECT DATETIMEELSEIF CONNECTION FAIL GIVE CONNECTION ERRORELSE INVENTORY ADD, REMOVE, MODIFY, SHOW, SEARCH, FIRST, NEXT, PREVIOUS, LASTENDIF

34. NAME:ORDER:

INPUT: ORDER ID, CUSTOMER ID / SUPPLIER ID, PRODUCT ID / ROW MATERIAL ID, DATETIME, QUANTITYOUPUT: ADD, REMOVE, MODIFY, SHOW, SEARCH, FIRST, NEXT, PREVIOUS, LASTIF TEXTFIELDS ARE BLANK THEN GIVE ERROR MESSAGE OF BLANK FIELDELSEIF ENTER DUPLICATES PRIMARY CONSTAINT THEN GIVE ERROR MESSAGE OF DUPLICATE CONSTRAINTELSEIF DATETIME FORMATE INCORECT THEN GIVE ERROR MESSAGE OF INCORECT DATETIMEELSEIF CONNECTION FAIL GIVE CONNECTION ERRORELSE ORDER ADD, REMOVE, MODIFY, SHOW, SEARCH, FIRST, NEXT, PREVIOUS, LASTENDIF

35. NAME:PAYMENT:

INPUT: PAYMENT ID, ORDER ID, CUSTOMER ID / SUPPLIER ID DATETIME, RUPEESOUPUT: ADD, REMOVE, MODIFY, SHOW, SEARCH, FIRST, NEXT, PREVIOUS, LASTIF TEXTFIELDS ARE BLANK THEN GIVE ERROR MESSAGE OF BLANK FIELDELSEIF ENTER DUPLICATES PRIMARY CONSTAINT GIVE ERROR MESSAGE OF DUPLICATE CONSTRAINTELSEIF DATETIME FORMATE INCORECT THEN GIVE ERROR MESSAGE OF INCORECT DATETIMEELSEIF CONNECTION FAIL GIVE CONNECTION ERRORELSE PAYMENT ADD, REMOVE, MODIFY, SHOW, SEARCH, FIRST, NEXT, PREVIOUS, LASTENDIF

36. NAME: ACCOUNT:

INPUT: PLANT MAINTENENCE AND OTHER COST, EMPLOYEE SALARY, PAYMENTOUPUT: SHOW SUMMARY ACCOUNTIF CONNECTION FAIL GIVE CONNECTION ERRORENDIF

37. NAME: HELP:

INPUT: HELP COMMANDOUPUT: SHOW HELP

38. NAME: RPMS:

INPUT: TOOLOUPUT: SHOW RELATED WINDOW

39. NAME: CALCULATOR:

INPUT: OPERAND, OPERATOROUPUT: SHOW RESULT

40. NAME: CALENDAR:

INPUT: DAY, MONTH, YEAROUPUT: SHOW CALENDAR

41. NAME: TIME:

INPUT: HOURS, MINUTE, SECONDOUPUT: SHOW TIME

42. NAME: REPORT:

43 | P a g e


INPUT: REPORT ATTRIBUTESOUPUT: SHOW REPORT

43 | P a g e


SYSTEM TESTING

6. SYSTEM TESTING

Testing plays a critical role in quality assurance for software. Due to the limitations of 43 | P a g e


the verification methods for the previous phases, design and requirements faults also appear in the

code. Testing is used to detect these errors, in addition to the errors introduced during the coding

phase.

Testing is a dynamic method for verification and validation, where the system to be

tested is executed and the behavior of the system is observed. Due to This, testing observes the fail -

ure of the system, from which the presence of faults can be deduced. However, separate activities

have to be performed to identify the faults.

Approaches:

Black-Box Testing

In the black-box testing, the internal logic of the system under testing is not consid-

ered and the test cases are decided from the specification or the requirements. It is often called func-

tional testing. Equivalence class partitioning, boundary value analysis, and cause effecting graphing are

examples of methods for selecting test cases for black-box testing. State–based testing is another ap-

proach in which the system is modeled as a state machine and then this model is used to select test

cases using some transition or path based coverage criteria. State–based testing can also be viewed as

grey-box testing in that it often requires more information than just the requirements.

White-Box Testing

In white-box testing, the test cases are decided entirely on the internal logic of the pro-

gram or module being tested. The external specifications are not considered. Often a criterion is speci-

fied, but the procedure for selecting test case is left to the tester. The most common control flow-based

criteria are statement coverage and branch coverage, and the common data flow-based criteria are All-

doffs and all-uses. Mutation testing is another approach for the white-box testing that creates mutants

of the original program by changing the original program. The testing criterion is to kill all the mutants

by having the mutant generate a different output from the original program.

Validation Testing

Checking to verify that appropriate values have been entered for a text box is called

43 | P a g e


Validation. In this test, if user is trying to enter the invalid data in any field than it will prompt an Mes-

sage Box showing the “ERROR”

There are following types of error :-

java.sql.SQlException:[Microsoft][ODBC Driver Manager] Data Source name not found

and no default driver specified,

Please, enter create User Id and Password,

Please, enter all fields, etc.

Authentication Testing

It is use to test that a login user is authorized or not. If a user is not authorizes than it

throw an error i.e.” Invalid User”. If user is authorized then system is allow that user to access the sys-

tem.

Integrated Testing

In integrated testing each form is connected to respective program, then each program

is connected to its respective menu and the entire system is tested form the top level.

6.1 Test Cases: Test Cases Expected Results43 | P a g e


Field empty

Error message shown excludes Backup Connection

“Please, enter all fields”Or

Error message display For Backup Connection

“Sorry Connection Failed”Or

Appropriate error message shown(if search text empty)

Duplicate Primary Key field detail enter Error message shown

(Conflict error will shown)

User type is not selected Error message shown “Select User type”

Backup (Database) Connection is not established and related Button Click

Error message shown “java.sql.SQlException:[Microsoft][ODBC Driver

Manager] Data Source name not found and no

default driver specified”

Created User Id and Password is not entered

Error message shown “Please, enter create User Id

and Password”

Date Format wrongError message shown

“java.sql.SQLException:[Microsoft][SQL Natinve

Client][SQL Server]Conversion failed when con-

verting datetime from character string”

Enter field length is less than minimum or greater than maximum

Error message shown(related length information shown)

Not enter integer value in text Field

Error message shown “java.sql.SQLException;[Microsoft][SQL Native Client][SQL Server]Conversion failed when con-

verting the varchar value xxx to data type int” Save details

Alert message shown “java.sql.SQLException: No ResultSet was

produced”

6.2 Validations:1. Create Account Error:43 | P a g e


2. Connection Error:

3. Login Error:

43 | P a g e


4. Conversion Error (from varchar value to data type integer):

5. Data Source Error:

43 | P a g e


6. Conversion Error (from character string to datetime):

7. Data Field Length Error:

43 | P a g e


8. Duplicate Key Error:

9. Empty Field Error:

43 | P a g e


10. Password Confirm Error:

11. Empty Field for search Error:

43 | P a g e


43 | P a g e


CROSS-PLATFORM JAVA EXECUTABLE WRAPPER

7. Cross-platform Java executable wrapper Launch 4j:

43 | P a g e


Launch4j is a cross-platform tool for wrapping Java applications distributed as jars in lightweight Win-dows native executables. The executable can be configured to search for a certain JRE version or use a bundled one, and it's possible to set runtime options, like the initial/max heap size. The wrapper also provides better user experience through an application icon, a native pre-JRE splash screen, a custom process name, and a Java download page in case the appropriate JRE cannot be found.

Features

Launch4j wraps jars in Windows native executables and allows to run them like a regular Win-dows program. It's possible to wrap applications on Windows, Linux, Mac OS X and Solaris!

Also creates launchers for jars and class files without wrapping. Supports executable jars and dynamic classpath resolution using environment variables and

wildcards. Doesn't extract the jar from the executable. Custom application icon with multiple resolutions and color depths. Native pre-JRE splash screen in BMP format shown until the Java application starts. Process name as the executable filename to easily identify your application, initial priority

and single application instance features.

43 | P a g e


Works with a bundled JRE or searches for newest Sun or IBM JRE / JDK in given version range.

Opens Java download page if an appropriate Java version cannot be found or a support web-site in case of an error.

Supports GUI and console apps. Supports Vista manifests and XP visual style manifests. Passes command line arguments, also supports constant arguments. Allows to set the initial/max heap size also dynamically in percent of free memory. JVM options: set system properties, tweak the garbage collection... Runtime JVM options from an .l4j.ini file. Runtime command line switches to change the compiled options. Access to environment variables, the registry and executable file path through system proper-

ties. Set environment variables. Option to change current directory to the executable location. The JRE's bin directory is appended to the Path environment variable. Custom version information shown by Windows Explorer. GUI and command line interface. Build integration through an Ant task and a Maven Plugin. Lightweight: 26 KB! It's free and may be used for commercial purposes. Includes a sample application and Ant script that automates the build process from Java

sources to native executable. The wrapped program works on all Windows platforms (98/Me/NT/2K/XP/Vista), Launch4j

works on NT/2K/XP/Vista, Linux, Mac OS X (build on 10.4) and Sparc Solaris 8-10.

License

This program is free software licensed under the BSD license, the head subproject (the code which is attached to the wrapped jars) is licensed under the MIT license. Launch4j may be used for wrapping closed source, commercial applications.

43 | P a g e


8. FUTURE ENHANCEMENTS

There is a huge scope of enhancement in the project by adding functionalities to the system. The pro-ject can be enhanced in the near future by adding more modules and can be implemented for more bet-ter use. History of all can be maintained and can be retrieved whenever requires. Progress report can be generated. This all can be modified and can be implemented in the near future.

43 | P a g e


9. CONCLUSIONWhile developing the system a conscious effort has been made to create and develop a software pack-age, making use of available tools, techniques and resources – that would generate a proper Technical Institute Support System.

While making the system, an eye has been kept on making it as user-friendly, as cost-effective and as flexible as possible. As such one may hope that the system will be acceptable to any user and will ade-quately meet his/her needs.

As in case of any system development process where there are a number of shortcomings, there has been some shortcomings in the development of this system also. These have been mentioned in details under the topic Limitations and Future Scope of the System

43 | P a g e


10. REFERENCES AND BIBLOGRAPHY

Sr. No. Book Author Publication1. An Integrated Approach to

Software EngineeringPankaj Jalote Narosa Publishing House

2. Java 2: The Complete Reference(J2SE)

Herbert Schildt Tata McGraw-Hill Publish-ing Company Limited

3. Advanced Java(B.Sc. (IT)) Rupal M. Shah Vipul Prakashan

4. The Complete Reference SQL James R. Groff and Paul N. Weinberg TMG

Tata McGraw-Hill Publish-ing Company Limited

Also:

• http://www.google.com • http://www.uml.org/

43 | P a g e

http://www.google.com/


43 | P a g e

Documents

RUBBER PRODUCTS MANAGEMENT SYSTEMpratimainfosys.weebly.com/uploads/1/0/4/4/10441765/ty… · Web viewThe release also provides enhanced integration with the Oracle WebLogic server,