Scribd
Upload
1K views5 pages

BarcodeGenerator Abstract

This document describes a project to develop a barcode generator application using Java. It will allow users to input numeric or alphanumeric strings and generate barcodes as output. The project will use the Waterfall/Spiral model and include two modules - one for administrators to generate barcodes and one for customers to generate barcodes without understanding the generator. It will be a standalone Windows application using technologies like AWT, Swings and will have 8 milestones from requirements to final review.

Uploaded by

Venkata Siva Reddy
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
1K views5 pages

BarcodeGenerator Abstract

This document describes a project to develop a barcode generator application using Java. It will allow users to input numeric or alphanumeric strings and generate barcodes as output. The project will use the Waterfall/Spiral model and include two modules - one for administrators to generate barcodes and one for customers to generate barcodes without understanding the generator. It will be a standalone Windows application using technologies like AWT, Swings and will have 8 milestones from requirements to final review.

Uploaded by

Venkata Siva Reddy
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 5

Barcode Generator

Title of the Project: Barcode Generator SDLC Methodologies: Waterfall/Spiral Model


Course: Roll No: Name of the Student: Technology Used: Internal Guide: E-Mail ID: Mobile No (Student): JAVA

Abstract of the Project: Introduction:


The BARCODE GENERATOR is a windows based application. The Basic purpose of this project is to generate barcode Library using Java application. It supports number of barcode formats and this application can be used and enhanced for whatever reason you like. These barcodes contain encoded authenticated information, which gives a unique identity to any product, and provide a security labels.

Functional Requirements:
Following is a list of functionalities of the system. Functional Requirements means interface between the user and the hardware. In this project, we discuss the functionality of the each module. The functional Requirements are Barcode Symbology defines the technical details of a particular type of barcode: the width of the bars, character set, method of encoding, checksum specifications, etc. Most users are more interested in the general capabilities of a particular Symbology (how much and what kind of data can it hold, what are its common uses, etc) than in the excruciating technical details User will give the input in the form of numeric or alpha-numeric then he will get the barcode as a output.

Non-Functional Requirements:

The system should be Stand Alone Application. The system should have Role based System functions access. 24 X 7 availability Better component design to get better performance at peak time Flexible service based architecture will be highly desirable for future extension.

Existing System:
The existing system is manual and the manual system works in the following way: Disadvantages: An early storage medium made of thin cardboard stock that holds data as patterns of punched holes. Each of the 80 columns holds one character. The holes are punched by a keypunch machine or cardpunch peripheral and are fed into the computer by a card reader. From 1890 until the 1970s, they were synonymous with data processing. Concepts were simple: the database was the file cabinet; a record was a card. Processing was performed on separate machines called sorters, collators, reproducers, calculators and accounting machines.

Proposed Systems:
To overcome all the difficulties of the existing system the management has proposed automated the whole system and the development of the new automated system contains the following activities Advantages: There is no need of punched holes. Here there is no need of key punch machines. There is no need of processing the data in other machines like sorters, collators. This is cost effective process. There is no time consumption. There is no loss of data means it will provide the security.

Modules:
There are two modules in this project they are:

Admin : Admin will give the string and get the output using barcode generator Customer: Customer will give the string and get the output without knowing about barcode generator

Users of the System:


This system should be designed to support the following users: Customer

Environment:
Operating System : Microsoft Windows XP/2000 Clients: CONSOLE Development Tools: Net beans 6.8 Documentation Tools: MS Office 2003/2007 Drawing Tools: IBM Rational Rose Enterprise, MS Office Visio 2007 User Interface: AWT & SWINGS Code Behind: AWT AND SWINGS

Requirements:
Hardware Requirements:

Number 1

Description PC With Minimum 20GB Hard-Disk And 1GB RAM

Software Requirements:

Number 1 2

Description Windows XP/2000 Or Higher With MS-Office 2007/2010 AWT& SWINGS.

Milestones:

No.

Milestone Name

Milestone Description

Remarks

Requirements Specification

Complete specification of the system including defining hierarchies constitutes this milestone. A document detailing the same should be written and a presentation on that be made. Understanding of the technology needed to implement the project.

Attempt should be made to add some more relevant functionality other than those that are listed in this document.

Technology Familiarization

The presentation should be from the point of view of being able to apply it to the project, rather than from a theoretical perspective. It is important to finalize on the database at this stage itself so that development and testing can proceed with the actual database itself. The scenarios should map to the requirement specification.

Database Creation

A database of at least 10 entries of users with at least 1 should application admin.

High-level Detailed Design

and

Listing down all possible scenarios and then coming up with flow-charts or pseudo code to handle the scenario. Implementation of the main screen giving the login, screen that follows the login giving various options, screens for each of the options The front-end developed in the earlier milestone will now be able to update the database. Other features should be functional at this stage. In short, the system should be ready for integration testing. The system should be thoroughly tested by running all the test cases written for the system (from milestone 5). Issues found during the previous milestone are fixed and the system is ready for the final review.

Development of Front End Functionalities.

During this milestone period, it would be a good idea for the team to start working on a test-plan for the entire system. This test-plan can be updated as and when new scenarios come to mind.

Integrating the Front-end with the Database

Integration Testing

Another 2 weeks should be there to handle any issues found during testing of the system. After that, the final demo can be arranged. During the final review of the project, it should be checked that all the requirements specified during milestone number 1 fulfilled

Final Review

The following steps will be helpful to start of the project: Study and be comfortable with technologies such as: AWT & SWINGS. Gather some knowledge of product hierarchies and maintenance before starting the design. Create a user database with different access levels. Start with creating the login screen. Create menus for navigation and group the functionalities as sub menus. Create the help-pages of the application in the form of FAQ. This will helps user.

You might also like