Foundry Management System Desktop Application

82
Sr.N o Table Contents 1 Introduction Company Profile Existing System and Need for System Operating Environment – Hardware and Software Detail Description of technology used 2 Designing DFD ERD 3 Data Dictionary 4 User Interface Design 5 Reporting 6 Conclusion 7 Biblography INDEX

Transcript of Foundry Management System Desktop Application

Page 1: Foundry Management System Desktop Application

Sr.No Table Contents1 Introduction

Company Profile Existing System and Need for System Operating Environment – Hardware and Software Detail Description of technology used

2 DesigningDFDERD

3 Data Dictionary4 User Interface Design

5 Reporting6 Conclusion

7 Biblography

INDEX

Page 2: Foundry Management System Desktop Application

Introduction

Page 3: Foundry Management System Desktop Application

INTRODUCTION

COMPANY PROFILE

Company Introduction:

Kadam Softwares and Services is a technology company at the forefront of

global solution developments. Kadam Softwares and Services has been

developing effective real-time and internet / intranet solutions. Kadam

Softwares and Services uses innovative and reliable technology to provide its

customers with the advantage they seek to succeed over their competitors.

From simple smart web service projects to intranet applications, Kadam

Softwares and Services aims for leading-edge yet practical solutions.

The company’s predictive modeling, decision analysis,

intelligence management, and decision management systems power billions

of mission-critical customer decisions. Kadam Softwares and Services Founded

in 2001 and works on the platform VB.Net which acquire customers more

efficiently, increase customer value and enter new markets more profitably.

PROFESSIONALSERVICES:

Kadam Softwares a has a team of skilled professionals to provide

consulting and software engineering services in these areas:

   Enterprise applications:

The rapid penetration of n-tier architectures into corporate IT systems has

created demand for skilled engineers that can design and build .Net

applications. Our database SQL Server, Oracle, combined with project

Page 4: Foundry Management System Desktop Application

management skills means Kadam Softwares is ideally placed to meet your

needs.

   High performance applications:

ASP, Visual Basic, C++ and Java remains the languages of choice for

building applications where performance is critical. Aadhar Nursing Home,

Saroj Iron, Sound Castings are few of our high profile clients that have

benefited from our ERP implementation abilities.

PRODUCTS:

We are specialized in custom ERP development and implementation for

diverse industry segments. The typical features include -

1. Cost effective environment as Windows Small Business Server / MS SQL 2003/2005 server.

2. ERP solution is developed as WEB application providing global connectivity.

3. Being a WEB application enables single point maintenance. 4. Custom solution allowing direct involvement of the user in

development cycle. 5. Report generation consistent with ISO/QS format as per the

requirement.

Page 5: Foundry Management System Desktop Application

EXISTING SYSTEM AND NEED FOR SYSTEMExisting System

The existing system is manual & also very difficult to manage and

provide information regarding the system to the various managerial level

time to time.

Also it is very difficult to maintain the Daily Transactions.

The system thus should be automated and should be able to manage and

provide information to managerial level time to time.

Need for System

Aviation Industry wants to grow the business.

It wants to save the decision time.

Provide user friendly interface

Increase the speed of processes by automation and use of advance

technology

Generate accurate & exact report.

Page 6: Foundry Management System Desktop Application

OPERATING ENVIRONMENT

HARDWARE REQUIREMENTS :

Pentium IV – 1.8GHz, 1GB Ram, 80GB Hard Drive

LAN   : 100 MBPS for optimal performance

Printers  : As per the requirement

SOFTWARE REQUIREMENTS :

Operating System : Windows 2000 & above version.

Front-End Tool : VB.net

Back-End Tool : SQL-Server 2005

IDE:Microsoft Visual Studio 2008

Page 7: Foundry Management System Desktop Application

DETAIL DESCRIPTION OF TECHNOLOGY USED

Technology

This product consists of three-tier scalable state of the art architecture

using leading edge technology:

VB.NET

SQL Server 2005

Features and Applications of VB.NET:-

Applications:-

The following are different types of application that can

be developed in .NET.

1) Powerful windows-based Application:-

Visual basic.NET comes with features such as a

powerful new forms designer, an in-place menu editor, and

automatic control anchoring and docking. Visual Basic.NET

delivers new productivity features for building more robust

application easily and quickly. With an improved integrated

development environment (IDE) and a significantly reduced

Page 8: Foundry Management System Desktop Application

startup time, Visual Basic.NET offers fast, automatic

formatting of code as you type, improved IntelliSense, an

enhanced object browser and xml designer, and much more.

2) Building Web-based Application:-

With Visual Basic.NET we are create Web applications

using the shared Web Forms Designer and familiar “drag and

drop” feature. You can double-click and write code to

respond to events. Visual Basic .NET2003 comes with an

enhanced HTML editor for working with complex Web pages.

We can also use Intelligence technology and tag completion,

or choose the wysiwyg editor for visual authoring of

interactive Web applications.

3) Simplified Deployment:-

With visual basic >NET we can build application more

rapidly and deploy and maintain them with efficiency. Visual

Basic.NET framework 1.1 makes “DLL Hell” thing of the past.

Side-by-side versioning enables multiple version of the same

component to live safely on the same machine so that

application can use a specific version of a component.

XCOPY-deployment and Web auto-download of page

deployment and maintenance with the power of

rich ,responsive Windows-based applications.

4) Powerful, Flexible, Simplified Data Access:-

Page 9: Foundry Management System Desktop Application

You can tackle any data access scenario easily with

ADO.NET and ADO data access. The flexibility of ADO.NET

enables data binding to any database, as well as classes,

collection, and arrays, and provides true XML representation

of data. Seamless access to ADO enables simple data access

for connected data binding scenarios. Using ADO.NET, Visual

Basic .NET can gain high-speed access to MS SQL Server ,

Oracle, DB2 ,Microsoft Access , and more.

5) Improved Coding:-

You can code faster and effectively. A multitude of

enhancements to the code editor , including enhanced

IntelliSense ,smart listing of code for greater readability and

a background compiler for real-time notification of syntax

errors transforms into a rapid application development

(rad)coding machine.

6) Direct Access to the platform:-

Visual Basic developers can have full access to the

capabilities available in .NET Framework 1.1 Developers can

easily program system services including the event log,

performance counters and file system. The new Windows

service template enables to build real Microsoft Windows NT

Services. Programming against windows services and

creating new Windows Services is not available in Visual

Basic. NET Standard, it requires Visual Studio 2003

Professional, or higher.

Page 10: Foundry Management System Desktop Application

7) Full Object Constructs:-

You can create reusable, enterprise-class code using

full object-oriented constructs. Language features include

full implementation inheritance, encapsulation, and

polymorphism. Structured exception handling provides a

global error handler and eliminates spaghetti code.

8) XML Web Services:-

XML Web service enables you to call component

running on any platform using open Internet protocols.

Working with XML Web services is easier where

enhancements simplify the discovery and consumption of

XML Web services that are located within any firewall.XML

Web services can be built as easily you would build any class

in Visual Basic 6.0.the XML Web service project template

builds all underlying Web services infrastructure.

9) Mobile Applications:-

Visual Basic.NET 2003 and the .NET framework 1.1

offer integrated support for developing mobile Web

application for more than 200 Internet-enabled mobile

devices. These new features give developers a single,

mobile Web interface and programming model to support a

broad range of Web devices, including WML 1.1 for WAP-

enabled cellular phones. Compact HTML for I-mode phones ,

and HTML for pocket PC, handheld devices, and pagers.

Page 11: Foundry Management System Desktop Application

Please note, Pocket PC programming is not available in

Visual Basic.NET standard ,it requires Visual Studio 2003

Professional ,or higher.

10) COM Interoperability:-

You can maintain your existing code without the

need to recode.COM interoperability enables you to leverage

your existing code assets and offers seamless bi-directional

communication between Visual Basic 6.0 and Visual

Basic>NET applications.

11) Reuse Existing Investments:-

You can reuse all your existing ActiveX controls.

Windows forms in Visual Basic .Net 2003 Provide a robust

container for existing for existing Active X controls .In

addition, full support for existing ADO code and data binding

enable a smooth transition to Visual Basic.NET2003.

12) Upgrade Wizard:-

You upgrade your code to receive all of the

benefits of Visual Basic.NET2003. The Visual Basic.NET

upgrade Wizard, available in Visual Basic.NET2003 Standard

Edition , and higher, upgrade up to 95 percent of existing

Visual Basic code and forms to Visual Basic.NET with new

support for Web classes and User controls.

Page 12: Foundry Management System Desktop Application

Features of .NET:-

The following are major features of.NET. We will

use these features throughout out journey. Here is just a

bCrief introduction to all key features of .NET.

1) Assemblies:-

An assembly is either a .DLL or .EXE that forms a part of

an application. It contains MSIL code that is executed by LR.

The following are other important related to an

assembly:

1. It is the unit on which permissions are granted.

2. Every assembly contains a version

3. Assemblies contain interfaces and classes. They may also

Contain other resources such as bitmaps ,file etc.

4. Every assembly contains assembly metadata, which

contain information about assembly.CLR uses this

information at the time of executing assembly.

5. Assemblies may be either private, which are used only by

the application to which they belong or Global assemblies ,

which are used by any application in the system.

6.Two assemblies of the same name but with different

versions can run side-by-side allowing application that

depend on a specific version to use assembly of that version.

The four of an assembly are:

1. Assembly Manifest:-

Contains name ,version ,culture ,and information

about referenced assemblies.

Page 13: Foundry Management System Desktop Application

2. Type metadata:-

Contains information about types defined in the

assembly.

3. MSIL:-

MSIL code.

4. Resources:-

Files such as BMP or JPG file or any other files

required by application.(Assembly that contains only

resources is called as Satellite assembly)

2) Common Type System:-

Common Type System (CTS) specifies the rules

related to data types that languages must follow. As

programs written in all Languages are ultimately converted

to MSIL, data types in all languages must be convertible to

certain standard data types.

CTS are apart of cross-languages integration,

which allows classes written in one languages to be used

and extended by another languages.

3) Cross-languages Interoperability:-

NET provides support for languages

interoperability. However, it doesn’t mean every program

written in languages can be used by another languages. To

enable a program to be used with other languages, it must

be created by following a set of rules called Cross Languages

Specifications (CLS).

Page 14: Foundry Management System Desktop Application

Cross-languages inheritance is the ability to create

a class in C# from a class created in VB.NET.

When an exception is raised by a program written

in C#, the exception can be handled by VB.NET .this kind of

exception handling is called cross-languages exception

handling.

.NET has brought a set of new features which are

to be understood by every programmer developing

application for Windows. There is no way Windows

programmer can ignore.Net, unless he is desperate to be

outdated. Microsoft will provide .NET as part of it’s O.S. in

future releases. It is the platform for programmers. It is not

new O.S. from Microsoft or new languages. It is the

environment for which you develop application . It is rich in

terms of features. Believe me, programming using VB.NET is

fun and it is more productive than VB6.0.

.NET Architecture-

Page 15: Foundry Management System Desktop Application

Microsoft SQL Server 2005Microsoft SQL Server 2005 represents the completion of

Microsoft SQL Server’s transformation into a leading database management system. The changes are extensive, completing the capabilities required for the most demanding enterprise applications and introducing a new application paradigm that affectshow many new SQL Server applications will be implemented and deployed. A major upgrade such as SQL Server 2005 brings many benefits to

VB.NET C# Jscript.NET More NET Languages

COMMON LANGUAGE SPECIFICATION

COMMON TYPES SYSTEM (CTS)

.NET FRAMEWORK CLASS LIBRARY

ASP.NET: Web Forms, XML Web Services Windows Forms Console

ADO.NET .NET REMOTING

Page 16: Foundry Management System Desktop Application

customers. It greatly improves classic “abilities,” such as availability, scalability, reliability, and so on. It introduces powerful new application development capabilities.

Many of the rough spots in earlier versions of SQL Server have been polished. And many of the items longrequested by the SQL Server community are now provided. SQL Server 2005 has something foreveryone. With any major advance come challenges. In the case of SQL Server 2005, the challenge for a DBA is adapting to numerous changes from previous versions. Some of these changes fundamentally alterthe mechanics of how DBAs interact with SQL Server; others are features with deep, long-term impact on how database applications are built and the demands they place on DBAs.

SQL Server 2005 and Database Administrators:

Initially, many DBAs will see SQL Server 2005 as little more than an evolutionary releasewith many new features and management capabilities that they will need to master. Over time, most DBAs will come to see SQL Server 2005 as a new application platform that dramatically changes how the applications are built and how they work, as well as the skills DBAs must master to support these applications. In the following sections, we’ll look at SQL Server 2005 from the evolutionary standpoint and then concentrate on it as a revolutionary new application platform.

SQLStatements:

The SELECT Statement

In the preceding section, you saw a simple use of the SELECT statement. This is all fineand good, but on many occasions you won’t need to return all the records in a specifictable. You might be looking for a specific record or for records that fall within a givenrange. All these data query options are possible via the SELECT statement by increasingthe level of selectivity in which the statement is executed.

Page 17: Foundry Management System Desktop Application

The INSERT Statement

Although the SELECT statement is the core statement of SQL, it can take you only so far. What happens when, for example, you want to insert information into a database as itis provided by visitors to your Web site or as a result of the processing of your code? That is where the INSERT statement comes in handy.

The UPDATE Statement

The UPDATE statement is similar to the INSERT statement in that both statements alter the information in your database. However, the key difference between the two is that withUPDATE, you can make modifications to a specific record (or records) that already exist.

The DELETE Statement

So far, you’ve learned how to read, insert, and update information in a database. ThroughADO and ASP, I hope that you are finding this experience very easy and that it is givingyou ideas about how to create even more dynamic, exciting Web pages.You’ve learned a lot about basic SQL, but there is still one more fundamental statementyou need to learn. This is the DELETE statement.

Page 18: Foundry Management System Desktop Application

PROPOSED SYSTEM

PROPOSED SYSTEM

Store Module Of Foundry Management System (Purchase order,

Incoming material, Outgoing Material and Stores) application, It deals with

the various aspects of purchasing and stores beginning with the indent to

demand the material, Then the indent is approved HOD, Store Manager. if

the material is not present in the store then Purchase department purchase

Proposed System

Page 19: Foundry Management System Desktop Application

the material by vendor enquiry or by passing the Tender, Then pass the

Purchase Order against the Quotation which is finalized in the enquiry.

System also describes the stores functions of receiving, issuing and

transferring of material.

It has add information about vendor name, vendor ID ,suppliers,

agents and job workers and select material in material list .

After to create purchaseorder, approvethis order.

Finished goods and products are sold to customers

Material is purchased from suppliers as per the requirement. Also to

generate report for Incoming material, Outgoing material, Goods

ReceiptNotes (GRN).

APPLICATION OVERVIEW

The Purchase & Inventory application enables one to perform Purchase

and Inventory functions beginning with an Indent. the purchasing of five

different types of items:

Materials for consumption on the project.

Plants and Machinery Capital items.

Spares for Plant and Machinery.

Fixed Asset Capital items other than Plant & Machinery.

Purchase

The Purchase application in Store Module Of Foundry Management

System covers the requisitioning of items to order placement. The various

procedural steps supported are as under:

Indent

Page 20: Foundry Management System Desktop Application

Requisitioning of items is carried out creating an Indent. It would

normally be created by the project personnel after examining the material

requirement schedules generated by the planning application.

Enquiry

If the material is not present or in less quantity then enquiry is

arranged in two ways Direct vendor enquiry or pass the tender Enquiry can

be floated to a set of vendors inviting their quotations.

Quotation and Price Comparison

Quotations received from vendors can be entered in System. These

may be against enquiries floated through the system or direct entries. For

quotations received against an enquiry, price comparison statements can be

generated for the various quotations.

Quotation Negotiation

After the step of Quotation and Price Comparison Vendors are invited

to negotiation In this the quoted values are tried to negotiate.

Purchase Order

Purchase Orders can be placed through system on various vendors.

These orders contain the item to be procured, quantities and amounts.

System also supports a wide variety of terms and conditions such as

currency options, credit period and delivery schedules.

Stores (Inventory)

The Inventory application in System revolves around stores which can

be created at various project locations. System supports the creation of stores

at project locations and central / regional stores. It provides various

documents to conduct stores transactions on a day to day basis.

Issue Note

Page 21: Foundry Management System Desktop Application

Items can be issued from the store through an Issue Note. Issues can

be done for consumption of the item in a project activity, towards plant and

machinery consumption (e.g. fuel, lubricants or spares) and towards repair

slips for plant and machinery. Entry of the issue note automatically reduces

stock.

Item Returned to Store

Surplus items can be returned back into the store through an Item

Return to Store Note. Like the issue note, items returned to store may be

against a project activity, against plant and machinery consumption (e.g.

fuel, lubricants or spares) or towards repair slips for plant and machinery.

APPLICATION PRELIMINARIES

This is deals with the prerequisites for carrying out Purchase and Store

function through the System. It provides an understanding of the

organization of information required for doing purchase and inventory

function quickly and efficiently

System Security

To conduct any transaction in System, the application user must

possess the necessary security privileges. For various users involved in the

purchase & inventory function the DBA must ensure that the necessary

security privileges pertaining to this application have been granted. This can

be done from the system administration module. Given below are some of

the checks that should be undertaken.

A user must be authorized to create purchase and stores related

documents in the system.

Grant security privileges to other users working on the application

depending on the role they are supposed to play.

Page 22: Foundry Management System Desktop Application

A user cannot delete only he/she can change the Delete flag true or

false. i.e. DBA have only authority to delete record

System keep the record of who Modify, Delete, Update of record with

date & time.

Approvals and Authority

System provides a facility of approving a document at multiple levels.

This helps to keep a proper control on any transaction. System allows users

to approve based on amounts and on multiple levels.

System provides a approval facility for following type of documents:

Indent

Purchase Order

Transport / Other Purchase Order

Masters

There are several masters which are used during the purchase and stores

function. Though it is possible to create master entries while working

through system, it is advisable that someone in the company, who has been

designated as the “owner” of the master, create an exhaustive set of data. It

may happen that at the time of creating some forms, you may not have the

requisite privileges to create master records.

OBJECTIVE OF SYSTEM

The main objective of proposed system is to provide user friendly,

reliable, error free.

High level accuracy and less response time.

Page 23: Foundry Management System Desktop Application

Effective generation of reports which would be demanded by

Administrator, Employees, Vendor etc.

Appropriate record keeping.

To save the time wasted in manual computing.

To provide durable and persistent way of data processing.

To view the status.

Page 24: Foundry Management System Desktop Application

SYSTEM ANALYSIS Preliminary Investigation

System Analysis

Page 25: Foundry Management System Desktop Application

Feasibility Study 1. Technical Feasibility :

The proposed software is technically feasible, as it needs no advanced hardware and software. But a connection – work setup is expected to run in the implementing organization. The speed of processor must meet the user requirements.

2. Economical Feasibility : As the system requirement need not require most costly hardware and software supports, the system does not spend its more cost on this part. Also the training cost incurred is negligible. But some amount of maintenance cost is involved as it is using the network setup. The system used only the normal support provided by the operating system. Hence the proposed system is economically feasible.

3. Operational Feasibility The system is totally acceptable in case of in large or small case. It can be easily implemented for variety employees for the authentication purpose to restrict the unauthorized access for the particular software. Hence the proposed system is operational feasibility.

Request Approval According to most approvals judged, the first to be accepted was to provide a WINDOWS like interface. Nextly total system working must be in well understandable form. Also the standard calculating formulas used can be changed easily so as to extend the acceptability of the system.

System :

Page 26: Foundry Management System Desktop Application

A system is a set of elements combined together to fulfill a specific job.

A system is an organized interacting; independent & integrated set of components var/parts. Any system must have an object or set of objective or hierarchical set of objects.

Characteristics of System :

1) System is usable.2) Component of system interact.3) System is goal seeking.4) System has input output.5) System transforms I/P to yield O/P.6) System must be controlled.7) System forms a hierarchy.

Page 27: Foundry Management System Desktop Application

DIAGRAMS

Page 28: Foundry Management System Desktop Application

DATA DICTIONARY

Page 29: Foundry Management System Desktop Application

Acc_Mast

Batch_Master

Catagery_Master

Grade_master

Page 30: Foundry Management System Desktop Application

Group_Master

Journal_Entry

Material_Master

Page 31: Foundry Management System Desktop Application

Material_Tran

Narration _Master

Payment

Page 32: Foundry Management System Desktop Application

Product_Info

Properties_Master

Purchase_Item_tran

Page 33: Foundry Management System Desktop Application

Purchase_tran

Transport

Page 34: Foundry Management System Desktop Application

Supplier_Customer__Info

Page 35: Foundry Management System Desktop Application

ePayroll

tblDTR

tblEmployee

tblSyslogin

Page 36: Foundry Management System Desktop Application

User Interface Design

Page 37: Foundry Management System Desktop Application
Page 38: Foundry Management System Desktop Application
Page 39: Foundry Management System Desktop Application
Page 40: Foundry Management System Desktop Application
Page 41: Foundry Management System Desktop Application
Page 42: Foundry Management System Desktop Application
Page 43: Foundry Management System Desktop Application
Page 44: Foundry Management System Desktop Application
Page 45: Foundry Management System Desktop Application
Page 46: Foundry Management System Desktop Application
Page 47: Foundry Management System Desktop Application
Page 48: Foundry Management System Desktop Application
Page 49: Foundry Management System Desktop Application
Page 50: Foundry Management System Desktop Application
Page 51: Foundry Management System Desktop Application
Page 52: Foundry Management System Desktop Application
Page 53: Foundry Management System Desktop Application
Page 54: Foundry Management System Desktop Application
Page 55: Foundry Management System Desktop Application
Page 56: Foundry Management System Desktop Application
Page 57: Foundry Management System Desktop Application
Page 58: Foundry Management System Desktop Application
Page 59: Foundry Management System Desktop Application
Page 60: Foundry Management System Desktop Application
Page 61: Foundry Management System Desktop Application
Page 62: Foundry Management System Desktop Application

REPOTR’S

Page 63: Foundry Management System Desktop Application

CONCLUSION

Page 64: Foundry Management System Desktop Application

CONCLUSION

We feel very glad to conclude this project report by expressing our deepest

gratitude to all our friends, family members, teachers & our team members for

providing constant encouragement throughout the process.

Objective of this project is to satisfy user friendly & easy to operate system

constant improvement & changes need to be made & newer version should be

released. New changes are implemented in almost any product today. This is

future all the care has been taken to provide an error free system can be perfect in

this current unstable environment.

At last we feel satisfied because our contribution will be helpful to the

company to achieve their desired objectives. We are thankful to the our college to

include this “Project Work” as a part of M.Sc. degree. This project work really

gives chance to learn out of typical reference books.

Page 65: Foundry Management System Desktop Application

Bibliography

Page 66: Foundry Management System Desktop Application

Bibliography

Visual Basic.Net Programming 2003(Black

Book).

-Steven Holzner.

Visual Basic 6.0 Database programming.

-Wayne Freeze

System Analysis and Design.

-Elias Awad.

Page 67: Foundry Management System Desktop Application