EASY XML EDITOR VB.Net Project

PROJECT DESCRIPTION

The project “EASY XML EDITOR” is designed for the purpose of creating XML pages in an easy way.

The project contains the following menus:

File

New,   Open,

Save,   Save As,

Page Setup, Print

Exit

The new option is used to create a new file. During this option, if the current file is not saved, then a message box will appear to save the current file and the new file is created. It contains the XML file header information.

The open option is used to open the file. During this option, if the current file is not saved, then a message box will appear to save the current file and the selected file is opened.

The save option is used to save the file. During this option, if the current file is not saved, then a message box will appear to save the current file and is saved with the given name.

The save option is used to save the file. During this option, then a message box will appear to save the current file and is saved with the given name.

Edit

      • Cut,     Copy, Paste
      • Delete
      • Select All
      • Find,    Replace

This is same as normal operation.

      • Insert node

A node name is typed to insert the node.

View

  • Code

The default coding view is displayed.

  • Design

The output of the XML file is displayed in the browser.

  • Print Node

All the node details are listed out.

Format

  • Font
  • Background,   Foreground
  • Tag, Attribute, Values, Punctuation
  • Reset

Font, as well as color, can be selected for individual tokens. The reset option will set the colors back to the default.

Check

  • Reformat

This is used to change the color values if the tags are not well-formed.

  • Syntax Verification

All the error situations are identified here and reported. At any time, only one error is displayed.

EXISTING SYSTEM

In the existing system, editors such as notepad are used for XML file creation. Otherwise, we go for .Net environment, which is costlier. In addition, in that editors, the error checking may not be possible. Moreover, only during runtime, the error is displayed in the browser.

PROPOSED SYSTEM

To avoid the drawbacks of the existing system, an enhanced editor is developed. The editor is particularly designed for XML code generation. With less effort, a maximum of coding lines can be prepared. The new system is having the following advantages.

HARDWARE CONFIGURATION

The hardware used for the development of the project is: 

PROCESSOR:           Latest

RAM:           128 MD SD RAM

MONITOR:           15” COLOR

HARD DISK:           20 GB

CD DRIVE:           LG 52X

KEYBOARD:           STANDARD 102 KEYS

MOUSE:           3 BUTTONS

SOFTWARE CONFIGURATION:

The software used for the development of the project is:

OPERATING SYSTEM:           Latest OS

ENVIRONMENT:           Visual Studio

LANGUAGE:           Visual Basic.NET

Limitations :

  1. Tags with the different case may not be identified.
  2. Syntax checking is not present.
  3. XML data cannot be viewed in tabular form in some editors.
  4. Individual colors separation and fonts are not possible for tags, attributes, and values.

Advantages :

  1. Automatic Ending tags are provided.
  2. Case Sensitive tag checking is possible.
  3. Syntax checking and Error notification at design time.
  4. The output can be quickly viewed.
  5. Individual colors separation for tags, attributes and values are given.
  6. Colors as well as fonts can be selected for individual tokens as well as background and the data.
  7. XML Data can be viewed in tabular form so that easy interpretation of data is possible.
  8. Easy interpretation of coding.

Pollution Control Board Administration Project

INTRODUCTION:

The project entitled Pollution Control Board Administration is developed as part of the final year RDBMS package project for the partial fulfillment of the BTech.

PROJECT:

Pollution Control Board Administration is software applications maintain all the day to day activities of the pollution control department, the software provides options to enter employee details, monthly salary generation, company registration, receipt from companies, company inspection etc., This project will help them to digitalize all the activities in the department.

OBJECTIVE:

The main objective of the application is to automate the existing system of manually maintaining the records of the company registration, accepting the payment, Industrial company inspection etc., The other main objective of this application is to manage all employee details and their monthly salaries.

SCOPE:

This application is developed for one branch of the pollution control board. After successful implementation of this project in one branch, this can be used in all other branches of the department. Later can be extended all other states.

Modules:

• Login
• MDI Form
• Employee Registration
• Monthly salary Generation
• Company Registration
• Receipt from Companies
• Company Inspection
• All Brach details
• Reports

Hardware Requirement

Processor: Intel Core Duo 2.0 GHz
RAM: 1 GB or More
Harddisk : 80GB or more
Monitor : 15” CRT, or LCD monitor
Keyboard : Normal or Multimedia
Mouse : Compatible mouse

Software Requirement

Front End :

Visual Basic 2005 Express edition
With Sql Server Compact Edition
Microsoft SDK 2.0 Or Visual Basic 2008 Express edition
With Sql Server Compact Edition
Microsoft SDK 3.0

Back End : MS Sql Server

Operation System : Windows XP with server pack 3 Or Windows 7

Share Market System VB Project

The Share Market System project training in a student’s life is like a live experience in the industry. So it is very essential part of the educational qualification. Post Graduation Diploma in Computer Application is the course offering me a unique change to find the place of utilizing computer in meaningful way. It provides me all the theoretical aspects with practical knowledge.

Screen shots

The project training in the 2nd Semester of the course gives me the exposure to the real world. The aim of the project training, by understanding a live project, is to have practical experience of the real world. It also clears the picture of practical field to prompt the students to develop their qualities talents, etc. So that I can expand our view about the implications of the theoretical knowledge in the practical field. we had the opportunity for the same at various Home appliances firm. The period of the trainings would be around one and half month.

Operating System    :  Window XP Service Pack-2
Language    :  Visual Basic 6.0
Backhand Tools    :  Microsoft Access 2k

SOFTWARE DEVELOPMENT -:: LIFE CYCLE ::-

Feasibility Study:-

The main aim of the feasibility study is to determine whether developing the product is financial and technically feasible. The feasibility study involves analysis of the problem and collection of the data which would be input to the system, the processing required to be carried out on these data, the output data required to be produced by the system, as well as study of various constraints on the behaviour of the system.

Requirement analysis and Specification:-

The goal of the requirement analysis and specification phases to clearly understand the exact requirement of proprietor and to systematically organise these requirement into a specification document.

Requirement analysis involve obtaining a clear and through understanding of the developed, with view to removing all ambiguities and inconsistencies from the initial client perception of the problem.

reports

1.    Functional Requirements

The functional requirements of the system documented in the SRS document should Cleary described each function which the system would support along with the corresponding input and output data set.

2.    Non Functional Requirements

The non-functional requirements deal with the characteristics of the system that cannot be expressed as function.

It includes aspects concerning maintainability, portability and usability and also includes reliability issues, accuracy of results, human computer interface and constraints on the system implementation.

The Goal of Implementation :-

The goal of implementations a part of SRS documents gives some general suggestion regarding developments.

Design :

The goal of the design phase is to transform the requirement specification into a structure that is suitable for implementation. In some programming language. Through the design phase we can derive the software architecture from the SRS documents.

Coding and Unit Testing:

The purpose of these phase software development. During the implementation phase, each component of the design is implemented as a program module, and each of these program modules is unit tested, debugged and documented.

Integration and Testing: During this phase the different modules are integrated in a planned manner. The different modules making up a system are almost never integrated in a single shot.

Maintenance:-

Correct errors that were not discovered during the product development phase. This is called corrective maintenance.

Improving the implementation of the system and enhancing the functionalities of the system according to the Client’s requirement.

Porting the software to a new environment, e.g. to a new computer or a to new operating system.

Introduction:

It took us great to develop this software in Visual Basic as Front end and Access as Back end interface. This software is duly tested on different environment of hardware and software. The data security of this software is great as the data stored in various tables with unreadable characters.

This software provide various data such as Stock market Business, Stock information, the Balance details of the firm, Client personal Information, Script detail etc. It also provides data such as various Companies along with its Shares with specific code and type of the category.

Inventory Control System VB.Net Project

The project titled “Inventory Control System” is to control the general stores department. Hindustan Shipyard Limited is an automation of issuing an item to different departments inside the organization, returning back the item to the stores if the department doesn’t have any need with the item or if the stock is full, issuing the receipt to the department to whom the item is being issued, checking the balance of the stock of each item, making a new purchase of an item if the store doesn’t contains the stock of that particular item.

The purchase of an item is indifferent modes i.e., local abroad and indigenous. If the item is purchased locally then it is said to be local. If the item is imported from other countries then it is said to be imported. If the item is purchased from any department inside the organization then it is said to be indigenous.

Inventory Control System purchase order form

The project contains five modules:

Issue Module, Returns Module, Receipts Module, Balance Module and Purchase Module.

The Issue Module contains the information about the item are issued by the department to various other department in the organization. This module contains the following fields as card code, item code, department code, work order number, document number, transaction date, rate of the item, quantity of the item to be issued, its value.

The Returns Module contains the information about the item are issued by the department to various other department in the organization. This module contains the same fields as in the issue module they are as follow fields card code, item code, department code, work order number, document number, rate of the item, transaction date, quantity of the item to be issued, its value.

The Receipts module contains the information about the item that are issued and address of the department to which the item was sold are the supplier details. The details contains the following fields as card code, item code, department Code, order number, document number, transaction date, rate of the item, quantity of the item to be issued, its supplier details.

Inventory Control System purchase report

The Balance module contains the information about the balance that is/was present before/after the issue of each item and about the new stock. This module contains the following fields as card code, item code, department code, rate of the item transaction code, transaction date, quantity of the item to be issued, its value.

The Purchase module contains the information about the purchase that made by the department. Whenever the department needs any new item, the value of the purchased item is calculated according to the mode of purchase i.e. local, abroad, indigenous. We can make addition of a new item, deletion, modification, etc for this file. It contains the fields such as item code, item desc, units, quality grade, item value.

Inventory control system is a client/server application.
Software requirements Visual Basic.Net front end, MS SQL Server back end.

SYSTEM REQUIREMENT SPECIFICATION

The data processing department is accepting many requests, which comes from different department. Currently the request like updates, stop details, issues, returns are done manually. So they would like to automate it.
We have to first understand this problem and produce a requirement documents based on understanding the problem.

End User: Office Staff

While studying the current system, after speaking with the director, front office staff we found the system as follows.

Whenever a new work comes, the work is divided into different parts and each part is submitted to the respective department. The respective department checks their work and the material needed for their work. If the material is sufficient for them for doing their work to carry out with it otherwise they send a request for Data Processing Department for the issue for the material. The data Processing Department then sends a request to stores department whether the mat is available or not. If the material is available they will issue it otherwise they will place as an order.
If the allocated material is more than sufficient, the respective departments will handover that extra material to Data Processing Department by a note. Then the Data Processing Department will update their respective stores. In automating the whole process we find that the inventory system consists of three main parts.

1. ISSUES:
This process is used to store the issue details of the item which is requested by the respective department.

2. RETURNS:
This process is used to store the return details of the item, which IS the respective department.

3. RECEIPTS:
This process is used to store the receipt details of the item, which is attested by the respective department.
After discussion with the staff the following decisions were taken regarding what the automated systems should do and what new environment will be.

1.    The format for each entry should be similar over currently being used.
2.    Entries might have errors, so system should be able to check for errors.
3.    Information about the items, departments, and work orders should be kept in permanent database.

Requirement Specification Document:

Introduction:

Purpose:

The purpose of this document is to describe the external requirement for the atomization of stock details. The atomization will provide management to accept item details and quality. It also describes the interface for the system.

Scope:

The document is the only one that describes the requirements of the system. It is meant for the use by and will also be the basis for validating the full system. Any change made to the requirements in future will have to go through a formal change approval process. The developer is responsible for asking for classification whenever necessary and will give any alteration without the permission of the client.

Conversion Methods:

Conversion methods are of four types these are parallel systems, direct cut over method, pilot method and phase in method. Each method has some advantages it offers and some problems that it may cause. However some situations force one method to be used over others, even though other methods may be more beneficial. In general, system conversion should be accomplished as quickly as possible. The present module contains the same fields as in the issue module they are as follows card code, item code, department code, work order number, document number, transaction date, rate of the item, quantity of the item to be issued., its value etc.,

Receipts Module:

This module contains the information about the items that are issued and their the details of the department to which the item was sold and the supplier details. This module contains the following fields as card code, item code, department code, order number, document number, transaction date, rate of the item, quantity of the item to be issued, its value, supplier details etc.

Balance Module:

This module contains the information about the balance that is/was present before/after the issue of each item and about the new stock. This module contains the following fields as card code, item code, department code, transaction date, rate of the item, quantity of the item to be issued, its value.

Purchase Order Master:

This module contains the information about the purchases that are made by the department. Whenever the department needs any new item, system is developed using ORACLE 7.3 as backend and VISUAL BASIC 6.0 as front end that helps us to create easier and flexible data entry.

The system automation that has been developed will be installed in the organization in a phased manner. This helps the end user who will be using the system in future to get a feel of the system. This also helps the end user to clarify their doubts and get rid any reservations or inhabitations that they have. The phased manner approach that the organization is implementing makes it possible systematic automated system.

CONCLUSION

After completing the proposed system successfully it is worth to talk about the limitations and advantages of the system.

LIMITATIONS:

This system is capable of fulfilling the current requirements, but it is required to make modification to meet the future requirements. Disk space to increased when information increases.

ADVANTAGES:

As all the screens are self explanatory it is easy to work with the system with a little training for new operator. The system eliminated the problem of the existing system and enhances its capability.

Inventory Management System VB.Net Project

Inventory Management System is a system which is used to keep track of sales and purchase of electronic goods. Its main objective is to keep track of stocks, sales and purchase of goods, maintain staff and customer information and generate reports.

The main functionalities of this system are as follows:

  • To maintain information about current availability of stock based on which it decides whether there is a need to purchase goods, if they are out of stock.
  • To display the information about dealer and also add information about new dealer.
  • To maintain the information about staff, their personal details such as contact number, name, address, qualification, birth date, etc.
  • To maintain the information about customer who visit the store for shopping.
  • It also provides discounts to customers who frequently visit the shop and purchase goods.
  • To provide information regarding sales and purchase of goods.
  • To provide information about sales summary.
  • The system can be accessed by administrator and accounts department.
  • It provides the functionality to create new user who can access the system.
  • It also provides the records of the defective products which the customers return back to the shop for replacement.
  • It also generates the purchase bill.

Inventory Management System Use Case Diagram

Project Scope

This document covers the requirements for the Inventory Management System. This Software will provide a graphical environment in which the users of the system will be able to perform various operations that are associated with storing, marinating, updating   and retrieving Stock information. The purpose of this is to guide developers in selecting a design that will be able to accommodate the full-scale application.

Product Perspective

The product Inventory Management system, is an independent product and does not depend on any other product or system. The product will automate various tasks associated with handling stock details and better organizing the Megastore information and  optimum performance, thus helping  the manager to ensure smooth working of these processes.

Inventory Management System Login Page

Product Features

The product, IMS will automate various tasks associated with handling stock details. The software will be used by the Megastores to Megastore the details of new and existing product. Periodically it will be used by the Megastores to input the total sales and sales rate information after the month/years. His software inherently makes automatic calculations on sales rate. And all this information is accessible to administrators and manager to keep track of their selling progress of the product. Also the software has a provision that will allow administrators to print the required reports of various products .

Inventory Management System Purchase Order Enquiry

User Classes and Characteristics

This software gives access to 2 kinds of users.

Administrator: The manager and Megastore administrator will have administrator access to add, delete and modify information Megastore in the database.

Authorized User: computer operator staff will have access to only view the data Megastored in the database in the form of formatted reports.

System Features

Login

Description and Priority

The login form is used all the users. This module has the highest priority when compared to all the other modules. This model allows the the user to enter his username and password in order to make use of the software.

Inventory Management System User Page & Manage AccountsStimulus/Response Sequences

This module has text boxes where the user can enter the his username name and password. If the necessary information is not provided or if invalid inputs are given by the user then the system will pop a message box.

Functional Requirements

Only authorized users are allowed to login.. If invalid user Name or password is given by the end-users then system should inform the user. If Unauthorized   users try to access then it should not allow the user to work on the System.

Data Entry module

Description and Priority

This module is used by data entry operator who is responsible for entering the details of products. The module requests that the Data entry Operator specify the function he/she would like to perform (either Add a product, update a product, or delete a product details).

In “Update a product” Once the Data entry Operator updates the necessary information ,the system updates the product record with the updated information.

In “Delete a product” Once the Data entry operator deletes the record, the system prompt s the user to confirm the deletion of the product.

Stock Entry Module

Description and Priority

This module allows the stock entry operator to add, delete or modify the product information from the system.

Stimulus/Response Sequences

The system requests the stock entry staff to specify the function she/he would like to perform(either Add stock, Update stock, Delete stock and Generate Report)

Functional Requirements

In “Add stock” Once the stock entry clerk provide the requested information, the system saves the stock and an appropriate message is displayed.

In “Update stock” the stock entry operator makes the desired changes to the stock details and at the same time the database will save the changes that are made by the stock entry operator.

In “Delete stock” if the clerk wishes to proceed with the deletion of the record on click of this the record is deleted from the system.

In “Report generation” the computed result of a particular product is displayed.