Scribd
Upload
50 views19 pages

Chapter 1: Introduction: Metadata Utility Tool

The document describes a proposed metadata utility tool. The tool aims to automate the manual process currently used to enter new data into metadata by allowing users to input minimal data which would then be processed and stored across multiple tables. This is needed because the existing manual process is prone to errors, requires the same steps to be repeated for each environment, and only allows developers to enter data. The tool will have two modules - one for entering new CPE model data and one for service brand data. It will map and store the input data across various metadata tables.

Uploaded by

manoj22490
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 DOCX, PDF, TXT or read online on Scribd
50 views19 pages

Chapter 1: Introduction: Metadata Utility Tool

The document describes a proposed metadata utility tool. The tool aims to automate the manual process currently used to enter new data into metadata by allowing users to input minimal data which would then be processed and stored across multiple tables. This is needed because the existing manual process is prone to errors, requires the same steps to be repeated for each environment, and only allows developers to enter data. The tool will have two modules - one for entering new CPE model data and one for service brand data. It will map and store the input data across various metadata tables.

Uploaded by

manoj22490
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 DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 19

Metadata Utility Tool

CHAPTER 1: INTRODUCTION

1 | Page

Metadata Utility Tool

1.2
EXISTING SYSTEM AND NEED FOR PROPOSED SYSTEM Existing System:

Before invention of this system all the process is done manually by the people. The people want to insert new set of data for the orders have to insert manually. The data is manually entered in a excel sheet and then the query is generated manually. After the manual generation of the query then the query is executed after that the new data is inserted into the metadata. After storing in the metadata those data are used into different applications of Megapath
The data need to be stored in the metadata is stored manually. This is stored in the excel sheet manually. After the storage of the data in the excel sheet, query is created

with the required data.


Then the created query is executed and the data is stored in the

metadata. This procedure has to be perform repeatedly for each table and environment for each new set of data

2 | Page

Metadata Utility Tool

Need for the System:

The existing system suffers from the following drawbacks:

The existing system has huge load of manual work. There can be error occurs through manual work which leads to

wrong data input in the metadata.


The generated query needs to be executed in each environment. The developer only eligible to store the data in the metadata.

Where as if the system is developed any one can store the data through the system user interface

3 | Page

Metadata Utility Tool

1.3 SCOPE OF WORK

The main scope of work is divided into 2 modules-

Module 1:

Whenever a new CPE model is generated the data about the CPE model such as name of the CPE model, which vendor provides that, should it be offered by COVAD or not, number of slots and ports, fixed asset of customer or not etc such data are taken and processed and stored into the metadata.

Module 2:

In this module the data about the service brand such as service brand name, description of the service brand, current maximum upstream and downstream, number of voice lines, access only or not etc such data are taken into consider. Those are data are

4 | Page

Metadata Utility Tool

processed and stored in the metadata.

The data which are inserted in CPE Model and Service Brand are mapped and simultaneously stored in different tables such as-

CPE_Model Service_Brand Service_Brand_Type_Meta Dslam_Card_Wiring_Priority CPE_Service_Brand_Preference CPE_Dslam_Compatibility Kit_Sku Kit_Sku_CPE_Mapping Billing_Profile

5 | Page

Metadata Utility Tool

1.4 OPERATING ENVOIRNMENT- HARDWARE AND SOFTWARE

Hardware Requirements:

For Server:

Processor P IV 3.0 Ghz

RAM : 2 GB

Hard Disk 80 GB

Standard Keyboard

Standard Monitor

Modem/Network Adapter

For Client

6 | Page

Metadata Utility Tool

Processor P III 1.0 Ghz

RAM 512 MB

Hard Disk 40 GB

Standard Monitor

Standard Keyboard

Modem/ Network Adapter

Dedicated and secured connection to Internet.

Software Requirements

For Server:

Front End: JSP

7 | Page

Metadata Utility Tool

Business Logic: Servlet

Back End: Oracle

Middleware: Apache Tomcat 7.0

Operating System: Windows 2000

For Client:

Operating System : Windows XP and above

Browsers: Internet Explorer 6/ Google Chrome/ Mozilla

8 | Page

Metadata Utility Tool

CHAPTER 2: PROPOSED SYSTEM

9 | Page

Metadata Utility Tool

2.1 PROPOSED SYSTEM

The main objective of the proposed system is easy handling of

large volume of data.


The processing of data is to be done in a organized manner. The data will be stored according to the transaction rules. No data will have to be entered multiple time.

10 | P a g e

Metadata Utility Tool

2.3 USER REQUIREMENTS

The main requirement of the user is to automate the manual

system.
The user required a utility tool which stores data into the

metadata.
The user required minimal input and to process those inputs

internally and map those inputs into different tables through proper transaction.
The tool should display few reports so that it can be verified that

the data store perfectly in the database.


The tool must provide certain verification of data before it is

stored into the metadata as because to avoid storing redundant and duplicate data.

11 | P a g e

Metadata Utility Tool

CHAPTER 3: ANALYSIS AND DESIGN

12 | P a g e

Metadata Utility Tool

3.1 OBJECT DIAGRAM

13 | P a g e

Metadata Utility Tool

3.2 CLASS DIAGRAM

14 | P a g e

Metadata Utility Tool

3.3 USE CASE DIAGRAM

15 | P a g e

Metadata Utility Tool

16 | P a g e

Metadata Utility Tool

3.4 SEQUENCE DIAGRAM

17 | P a g e

Metadata Utility Tool

3.5 ACTIVITY DIAGRAM

18 | P a g e

Metadata Utility Tool

19 | P a g e

You might also like