CONTENTS

1. 2. ABSTRACT INTRODUCTION 1.1 1.2 INTRODUCTION TO ORGANISATION INTRODUCTION TO ENVIRONMENT 2.2.1. 2.2.2. 3. SOFTWARE USED ( FEATURES ) HARDWARE USED

(SERVER SIDE /CLIENT SIDE FULL SPECIFICATIONS ) REQUIREMENTS ANALYSIS 1.3 PROBLEM ANALYSIS 1.3.1 3.1.2 3.1.3 3.1.4 1.4.1 1.4.2 1.4.3 FUNCTIONAL REQUIREMENTS NON FUNCTIONAL REQUIREMENTS SCENARIOS USECASES TECHNICAL FEASIBILITY OPERATIONAL FEASIBILITY ECONOMICAL FEASIBILITY 1.4.3.1.1 COST BENEFIT ANALYSIS 3.3 PROPOSED SYSTEM 3.4 PREPARATION OF REQUIREMENT SPECIFICATIONS 3.4.1 SOFTWARE REQUIREMENT SPECIFICATION 4. SOFTWARE DESIGN 4.1 OBJECT ORIENTED DESIGN METHODOLOGY 4.1.1 4.1.2 INTRODUCTION DESIGN TOOLS UTILISED 4.1.2.1 ACTIVITY DIAGRAMS 4.1.2.2 SEQUENCE DIAGRAMS 4.1.2.3 CLASS DIAGRAMS 4.1.2.4 OBJECT DIAGRAMS 4.1.2.5 STATE TRANSITION DIAGRAMS 5. DATABASE DESIGN 1.5 INTRODUCTION 1.6 E - R DIAGRAMS 1.7 NORMAL FORMS IMPLEMENTED 1.8 TABLE DESCRIPTIONS 6. TESTING 1.9 STRUCTURAL TESTING ( WHITE BOX )

1.4 FEASIBILITY STUDY

1.9.1 1.9.2 1.10.1 1.10.2 7.

INTRODUCTION LIST OF TEST CASES PREPARED INTRODUCTION LIST OF TEST CASES PREPARED

1.10 FUNCTIONAL TESTING ( BLACK BOX )

FORMS DESIGN 1.11 INPUT FORMS DESIGN ( MANUAL ) 1.12 OUTPUT FORMS DESIGN ( MANUAL )

8. 9.

IMPLEMENTATION / USER INTERFACE 1.13 ALGORITHMICS / NAVIGATIONAL DESCRIPTION CONCLUSION

10. BIBILIOGRAPHY 11. APPENDIX 1.14 ANNEXTURE - I ( SCREEN LAYOUTS ) 1.15 ANNEXTURE - II ( SAMPLE CODE ) 1.16 ANNEXTURE - III ( REPORTS ) 1.17 ANNEXTURE - IV (GLOSSARY )

1.ABSTRACT
The system deals with providing online support to the people who are facing problems with various software technologies. Problems with the current system, there is a communication gap between the customer and the organizations. People generally dont know the name of the sites of all organizations to post their problem.

Customer usually face some problem while posting the bugs occurred in different softwares as they have to post their bugs to different sites individually and there is no surety of quick response from the organization. Few organizations may not be interested in responding to the customer problems. So in order to overcome all these limitations and to meet all their requirements, the current process is replaced with this application.

2. INTRODUCTION
2.1 INTRODUCTION TO ORGANIZATION

CMC Limited is Indias largest one point computer support company providing a complete range of services. CMC has executed a large number of turnkey IT projects the like the world over Passenger Railway Reservation System for Indian Railways,Ship Planning

Systems for various ports in Europe, Traffic Management System of Bhilai Steel Plant and Scheduling for London Underground. CMCs Education& Training Programme includes short term introductory level courses of one to three weeks duration for all ranges of users & IT professionals and long term certificate / diploma courses for both beginners& IT professionals.
CMC Limited offers a wide range of Education & training Services both in India and abroad. CMC took the lead in this field in 1978, when the first training programme was held. CMC, in fact, is one of the first companies in Information Technology to offer such a programme.

The excellence of CMCs training programmes has the participants from

been

acknowledged by

COMMON WEALTH Secretariat, various UNITED NATIONs

Agencies , the WORLD BANK , Ministry of EXTERNAL AFFAIRS , Department of PERSONNEL , Members of PARLIAMENT , Officers of the INDIAN ADMINISTRATIVE ,FOREIGN & POLICE SERVICES , & participants from the Ministry of ENVIRONMENT & FORESTS & INDIAN BANKS.

THE BEGINNINGS:CMC Limited , Indias leading Information Technology Company , offers users both in India & Abroad a range of services& solutions in areas like Systems Design &Development ,Systems Engineering , Multivendor networking , consultancy , installation, training , maintenance & total facilities management .

CMC has extensive & continually updated expertise in real - time , on-line systems , process control image processing , data communication ,networking , parallel architectures , etc.. with this horizontal expertise in Information Technology , is CMCs vertical Integrated

expertise in a whole range of industries both in infra structure industries like power , coal ,oil, & transportation , as well as service industries such as Banking ,Law & order & education . It is this totality of expertise that has enabled CMC to develop a variety of superior IT products & to execute a number of complex and challenging projects not only in India but also in Europe ,America ,Africa the Middle East & South- East Asia .

FIRST CHALLENGE :CMC Limited commenced operation as COMPUTER MAINTENCE CORPORATIONS in October 1976 . The first challenge came just one year later in November 1977 . IBM announced that it would cease its maintenance and support Indian Computer Community, the Operations in India from June ,1978 . The entire

majority of whom had IBM equipment was thrown into confusion. It was at the juncture that

CMC took a bold decision: It offered to provide maintenance services to all users of IBM equipment in India , regardless of the type , age , size or location of their machines machines. The task was truly a staggering one but CMC faced it with confidence. Exactly six months later , CMC stepped into IBM shoes and took over the maintenance of over 800 IBM installations without any dislocation .

FURTHER AFIELD:Even as the maintenance operations for IBM equipment were established , the Corporation began looking further a field. While maintenance activities attention to other areas of computer progressed apace , C M C turned its

support . Computer centers were set up in different cities and a whole range of consultancy services were offered . Computer education & training programs were started. The R &D center pioneering at hyderabad undertook projects in the areas of contemporary technology , software India s first

developments in data communications &database management became one of the Corporations fastest growing activities. And INDONET National Computer Network began taking shape.

RE-DIFINING PRIORITIES :It soon became evident that calling CMC a maintenance corporation did not reflect the wide scoped the fact of its that activities and services .it was in reorganization of in August ,1984 , COMPUTER

MAINTENANCE CORPORATION became CMC Limited .

CMC TODAY:While hardware maintenance continues to play a major role, CMCs activities have advanced in many new directions. CMC is one of the leading System Integrators in the country with multi faceted expertise in Information Technology. As a part of the

Globalization activity, CMC has acquired a Subsidary Company in the U.S.A , there by expanding its International activities. In the light Of the growth of the communication sector and its importance to the liberalized economy, CMC revamped its communication network NDONET, in terms of new Protocols ,communication equipment as well as host systems. The need for highly specialized s/w engineering skills in the coming years has triggered increased education & Training activities .

In order to give focus to the above mentioned business areas, , five Strategic Business Units ( SBUs) have been formed , namely Customer Services Systems Integration, International Operations, INDONET & Education &Training. Each of the vertical units in the CMCs line of business will operate as a profit centers with increased overall productivity & accountability. This will also help to gauge the performance of various business activities in terms of

contribution & other measures of excellence to achieve industry standards and ultimately result in greater customer satisfaction. With 18 offices in India , a subsidiary company in U.S.A , 760 software engineers , 800 hardware engineers , CMC cates to the IT requirements of the customers from varied fields , spread over a vast global area.

2.2 INTRODUCTION TO ENVIRONMENT

In order to design an efficient system the appropriate hardware and software requirements for this application are as follows :

2.2.1 SOFTWARE USED

O/S Microsoft Windows 2000

Interface Tools :FRONT END PROGRAMMING LANGUAGES HTML , Style Sheets Java , Servlets , JDBC

SCRIPTING TOOLS BACK END SERVER

Java Script Oracle 8i Tomcat 4.0

2.2.2 HARDWARE USED

Server side: PROCESSOR SPEED RAM HARDDISK FDD INTEL PENTIUM PROCESSOR 933 MHz 256 MB 40 GB 3.5 Inch floppy drive that possess enough backup capacity to maintain in case of system crash 512 KB. 32 bit.

CACHE MEMORY MEMORY

Input Devices:
KEYBOARD MOUSE 101 Keys Samsung

Output Devices:
PRINTER MONITOR TVS Zenith

Client side :-

PROCESSOR

INTEL PENTIUM PROCESSOR

SPEED

933 MHz

RAM HARDDISK FDD CACHE MEMORY MEMORY

128 MB or above 10.3 GB or above 1.44 MB Floppy Disk Drive 512 KB. 32 bit.

Input Devices:
KEYBOARD MOUSE 121 Keys Intel

Output Devices:
MONITOR

Intel

INTRODUCTION TO J2EE

Internet, the world wide network of computers , connects together thousands of computers all over the world. The number of computers connected to the net is increasing at a rapid rate . The amount of traffic on the net is increasing at an alarming rate . Computers connected to the net are from many different manufacturers, running different operating systems & they differ in architecture , computing power and capacity. The developers at Sun Microsystems felt the need for a new programming language suitable for this heterogeneous environment and Java was the solution. Todays serve complex world of computing needs distributed applications to

enterprises spread around the globe. The J2EE blueprint proposes the solution of

distributed multi tired application model for

enterprise applications not

only become tied to the

compatible with all operating systems and types of computers but also are not products and application programming interfaces of any one vendor.

The Java TM 2 Platform, Enterprise Edition(J2EETM) provides a component based approach to the design , development ,assembly, and deployment of enterprise applications. The J2EE services support through platform offers a multitired distributed application data interchange on Extensible Markup model, reusable components, a unified security model, flexible transaction control , and Web integrated Language(XML)-based open standards and protocols. Not only can you deliver innovative business solutions to market Faster than ever, but also your platform-independent J2EE component-based solutions are not tied to the products and application programming interfaces (APIs) of any one vendor. Vendors and customers enjoy the freedom to choose the products and components that best meet their business and technological requirements.

J2EE Components:
The J2EE platform uses a distributed multitired application
model for enterprise applications. Application logic is divided into components according to function, and the various application components that make up a J2EE application are

installed on different t machines depending on the tier environment to which the application component belongs.

in the

multi tired J2EE

Although J2EE Application can consist of the 3 or 4 tiers,J2EE multi tired applications are generally considered to be 3-tiered applications because they are distributed over three locations : client machines, the J2EE server machine, and the database or legacy machines at the backend. Three-tiered application that run in this way extends the standard two-tiered client and server model by placing a multithreaded application server between the client application and back-end storage.

J2EE applications are made up of components. A J2EE component is a self - contained functional s/w unit that is assembled into a J2EE application with its related classes and files that communicates with other components.

The J2EE specification defines the following J2EE components: 1 Application clients and applets are components that run on the client Java servlet and Java Server PagesTM (JSPTM ) technology components are web components that run on the server. Enterprise Java BeansTM (EJBTM ) components (enterprise beans) are business components that run on the server.

2 3

J2EE CONTAINERS:
Normally , thin-client multitiered applications are hard to write because they involve many lines of intricate code to handle transaction and state management, multi threading , resource pooling , and other complex low level details . The component - based and platform - independent J2EE architecture makes J2EE applications easy to write because business logic is organized into reusable components. In addition the J2EE server provides underline services in the form of a container for every component type because you do not have to develop these services yourself , you re free to concentrate on solving the business problem at hand.

CONTAINER SERVICES :Containers are the interface between a component and the low - level platform specific functionality that support the component . Before a Web , enterprise bean , or application client component can be executed , it must be assembled into a J2EE module and deployed into its container.

The assembly process involves specifying container settings for each component in the J2EE application and for the J2EE application itself. Container settings customize the underlying support provided by the J2EE server, including services such as security , transaction Management , Java Naming & Directory interface TM (JNDI) lookups , and remote connectivity . Here are some of the high-lights :

1 2

The J2EE security model lets you configurate Web-Component or enterprise bean so that system resources are accessed only by authorized users. The J2EE transaction model lets you specify the relationships among methods that make up a single transaction so that all methods in one transaction are treated as a single unit.

JNDI lookup services provide a unified interface to multiple naming and Directory services in enterprise so that application components can access Naming and Directory services.

The J2EE remote connectivity model manages low level communication between clients and enterprise beans. After an enterprise bean is created , a client invokes methods on it as if it were in the same virtual machine .

CONTAINER TYPES :J2EE Server : It is the run time portion of a J2EE product. A J2EE server provides EJB & Web containers. Enterprise Java Beans (EJB) Container :
Manages the execution of Enterprise beans for J2EE applications

Enterprise Beans & their container run on the J2EE server.

Web Container: Manages the execution of JSP page and Servlet components for J2EE applications. Web components and their container run on the J2EE server.

Application Client Container : Manages the execution of application client components .Application clients and their container run on the client. Applet Container : Manages the execution of applet. Consists of a web browser and a Java plug-in running on the client together.

INTRODUCTION TO JDBC
JDBC is a java API for executing SQL statements. JDBC is often thought of as standing for Java Database Connectivity. It consists of a set of classes and interfaces written in the Java programming language. JDBC provides standard API tool/database developers and makes it possible to write database application using a pure Java API. Using JDBC, it is easy to send SQL statements to virtually any relation database. One can write a single program using the JDBC API, and the program will be able to send SQL statements to the appropriate database. The combination of Java and JDBC lets a programmer to write it once and run it anywhere. Java being robust, secure, easy to understand and automatically downloadable on a network, is an excellent language basis for database applications. A programmer can write or update once, put it on the server, and everybody has access to the latest version. JDBC makes it possible to do three things:
1 2 3 Establishes a connection with a database. Send SQL statements. Process the results.

INTRODUCTION TO JSP
Java Server Pages (JSP) lets you separate the dynamic part of your pages from the static HTML. You simply write the regular HTML in the normal manner, using whatever Web-page- building tools you normally use. You then enclose the code or the dynamic parts in special tags, most of which start with "<%" and end with %>".

We normally give the file a .jsp extension, and typically install it in any place you could place a normal Web page. Although what you write often looks more like a regular HTML file than a servlet, behind the scenes, the JSP page just gets converted to a normal servlet, with the static HTML simply being printed to the output stream associated with the servlet's service method. This is normally done the first time the page is requested, and developers can simply request the page themselves when first installing it if they want to be sure that the first real user doesn't get a momentary delay when the JSP page is translated to a servlet and the servlet is compiled and loaded. Note also that many Web servers let you define aliases that so that a URL that appears to reference an HTML file really points to a servlet or JSP page.

Aside from the regular HTML, there are three main types of JSP constructs that you embed in a page: scripting elements, directives, and actions. Scripting elements let you specify Java code that will become part of the resultant servlet, directives let you control the overall structure of the servlet, and actions let you specify existing components that should be used, and otherwise control the behavior of the JSP engine.

Syntax Summary
JSP Element Syntax Interpretation Notes

Expression is JSP Expression

</jsp:expression>. Predefined
variables are request, response, out,

<%= expression %>

evaluated and placed in output.

session, application, config, and page Context Code </jsp:scriptlet>.

Code is inserted JSP Script let

<% code %>

in service method. Code is inserted in body of servlet

Declaration

<%! code %>

class, outside of

Code </jsp: declaration>.

Legal attributes, with default values in bold, are:

service
method.

1 import="package.class" 2 content Type="MIME-Type" 3 isThreadSafe="true |false"

Directions to the JSP page Directive

4 session="true |false" 5 buffer="sizekb|none" 6 autoflush="true|false" 7 extends="package.class" 8 info="message" 9 errorPage="url" 10 isErrorPage="true|false" 11 language="java"

<%@ Page att="val" %>

servlet engine about general setup.

JSP include Directive

<%@ include file="url" %> A file on the

local system to

The URL must be a relative one. Use the

jsp:include action to include a file at be included when request time instead of translation time.
the JSP page is

translated into a servlet. If you want to include the file at the time the page is translated, use the page directive

The jsp:include Action

<jsp:include page="relative URL" flush="true"/>

Includes a file at

the time the page with the include attribute instead. Warning: on some servers, the included file must be an is requested. HTML file or JSP file, as determined by the server (usually based on the file extension). Possible attributes are:

<jsp:useBean att=val */> or

The

1 id="name" 2 scope="page|request|session|
Find or build a Java Bean. application"

jsp:useBean
Action

<jsp:useBean att=val *> ... </jsp:useBean>

3 class="package.class" 4 type="package.class" 5 beanName="package.class"

Set bean properties, either

The Legal attributes are

explicitly or that value comes from a request parameter.

1 name="beanName" 2 property="propertyName|*" 3 param="parameterName" 4 value="val"

jsp:setPropert <jsp:setProperty att=val*/> by designating y Action

The

<jsp:getProperty

Retrieve and output bean properties. Forwards request to another page.

jsp:getPropert name="propertyName" y Action value="val"/> The jsp:forward <jsp:forward

Action

page="relative URL"/>

HYPER-TEXT MARKUP LANGUAGE Introduction

Hyper Text Markup Language is a structural markup language used to create and format a web document. A markup language such as HTML is simply a collection of codes, called Elements that are used to indicate the structure and format of a document. A user agent, usually a web browser that renders the document, interprets the meaning of these codes to figure how to structure or display a document. HTML is not invention but it is an improved version of Standard Generalized Markup Language (SGML).

HTML in the following four stages: Level-0 included only the basic structural elements and assured that all browsers supported all features. Level-1 advanced features included highlighted text and graphics that were supported depending on the browser capability. Level 2 introduced the World Wide Web as an interactive medium and the feature of fill out forms on the Internet. Level-3 introduced frames, inline, video, sound, etc.

Importance of HTML HTML can be used to display any type of document on the host computer, which can be geographical at a different location. It is a versatile language and can be used on any platform or desktop.

The appearance of a Web page is important, and HTML provides tags to make the document look attractive. Using graphics, fonts, different sizes, color, etc. can enhance the presentation of the document.

Functionality of HTML in the project: As we know this is purely web-based project. This helps to embed Java Server Pages within the page using some simple tags. Used to design the forms. User can communicate easily with server.

ABOUT ORACLE
ORACLE 9.0: Oracle is an object Relational Database Management Systems (ORDBMS) KEY FEATURES: Operating with in the framework of the Network Computing Architecture(NCA), oracle provides: Maximum performance and scalability through its unique design with the Windows NT multi-threaded architecture. In addition, oracle8 for Windows NT has been optimized to take full capabilities. Integration with the performance Monitor, Event Viewer, Registry and Security system Central easy-touse Graphical User Interface distributed database management using oracle Enterprise Manager

DATABASE OBJECTS:

Some thing created and stored in a database tables, viewers synonyms, indexes, sequences, clusters, and columns are all examples of database objects
TABLE:

The basic unit of storage in a relational database management system. A table represents entities and relationships and consists of each or more units or information each of which consists the same kinds of values. Each may be represented by the data type as in DATE. Once a table is created, valid rows of data can be inserted into it. Table information can then be queried, deleted or updated. To enforce defined business rules on a tables data registry constraints and triggers can also be defined for a table.

CLUSTER:

Clusters are optional method of storing table data. A cluster is group of tables that share the same data blocks because they share common columns and are often used together.

INDEX:

Indexes are optional structures associated with tables and clusters. You can create indexes explicitly to speed SQL statement execution on a table. An Oracle index provides a faster access path to table data. Indexes are the primary means of traducing disk I/O when properly used.

SYNONYM:

A synonyms is an alias for any table, view, snapshot, sequence, procedure, functions, or package. Because synonym is simply an alias, it requires no storage other than its definition in the data dictionary.

SQL OVERVIEW:

SQL is a very simple, yet powerful, database accesses language. SQL is a non-procedural language, used to describe in SQL. What they want to be done and the SQL language compiler automatically generates and perform the desired task. IBM Research development and defined SQL and ANSI/ISO have refined SQL as the standard language for relational database management systems. The SQL implemented by Oracle Corporation for Oracle is 100% complaints at the Entry Level with ANSI/ISO 9002 standard SQL data language.

SQL STATEMENTS:

All operations performed on the information in an oracle database are executed using SQL statements. A SQL statement is a specific instance of valid SQL command. A statement consists of partially of SQL reserved words, which have special meaning in SQL and cannot be used for any other purpose. Oracle SQL statements are divided into the following categories: Data Manipulation Language Statements(DML) Data Definition Language(DDL) Transaction Control Statements Session Control Statements System Control Statements Embedded SQL Statements PL/SQL

PL/SQL is oracles procedural language extension to SQL.PL/QSL enables you. To mix SQL statements with procedural constructs, with PL/SQL, program units such as procedures, functions and packages. PL/SQL program units generally are categorized as anonymous blacks and stored Procedures. Any anonymous block is a PL/SQL block that appears within your applications and it is not named or stored in the database. In many applications, PL/SQL blocks can appears wherever SQL statements can appear. A stored procedure is a PL/SQL block that oracle stores in the database and can be called by name from an application. When you create a stored procedure oracle passes the procedure and stores its passed representation in the database. Oracle also allows you to create and store functions.

STORED PROCEDURES:

ORACLE allows you to create and call store procedures. If your applications call a stored procedure is retrieved from the database and processed by the PL/SQL engine in Oracle. You can call stored procedures from applications developed using these tools: Oracle pre compilers Oracle call interface SQL*Module2 SQL* Plus Server Manager

ORACLE ENTERPRISE MANAGER:

You can also call stored procedures from another PL/SQL block, either an anonymous block or another stored procedure.
EXTERNAL PROCEDURES:

PL/SQL procedures executing on an Oracle server call external procedures of function that is written in the c Programming Language and stored in a shared library. The C routine executes in a separate address space from that of Oracle server.
PACAKAGES:

PL/SQL lets you bundle logically related types, program objects and sub programs into a package. Packages can be complied and stored in an oracle8 database, where their contents can be shared by multiple applications.
TRIGGERS:

Oracle allows you to define procedures that are implicitly executed when an INSERT, UPDATE, or DELETE statement is issued against the associated table. These procedures are called database triggers. A trigger can include SQL and PL/SQL statements to execute as a unit and can invoke stored procedures. The market-leading DBMS in use today is Oracle Corporations Oracle Server, also known simple as ORACLE. With the introduction of several new Oracle 9 features. Oracle Server can now be considered as a powerful Object Relational Database Management System(ORDBMS). ORACLE provides efficient and effective solutions for the major database features.
Large database:

ORACLE supports the largest of databases, space management control potentially hundreds of gega bytes in size. To make efficient use of expensive hardware devices it allows full control of space usage.
Many concurrent database users:

Concurrent database users mean many users operating a variety of database

Applications

simultaneously on the same data. By managing concurrent minimizes data contention and guarantees data

database users Oracle concurrency.

High transaction processing performance: A transaction is a set of instructions, which have to be executed at one instance. Oracle maintains the preceding features with a high degree of overall system performance. Database users do not suffer from slow processing performance.

High availability: At some sites, Oracle works 24 hours a day with no down limit to limit database throughput. Normal system operations such as database backup and partial computer system failures do not interrupt database use.

Controlled availability: Oracle can selectively control the availability of data at the database level and sub database level.

Portability: Oracle software is ported to work under different operating systems and is the same on all systems. Applications developed for Oracle can be ported to any operating system with little modification.

Compatibility: Oracle software allows different types of computers and operating systems to share information across networks.

Manageable security: To protect against unauthorized database access and use , Oracle provides fail-safe security features to limit and monitor data access. These features make it easy to manage even the most complex design for data access.

Database enforced integrity:

Oracle enforces data integrity, business rules that dictate the standards for acceptable data. As a result, the costs of coding and managing checks in many database applications are eliminated. Distributed database systems: For computing environments that are connected via networks, Oracle combines the data physically located on different computers into one logical database that can be accessed by all network users. Distributed systems have the same degree of user transparency and data consistency as non-distributed systems, yet receive the advantages of local database

3. REQUIREMENT ANALYSIS
The analysis is the process of understanding the system at a greater depth , identifying the missing functions with an intention to improve it through better methods and procedures . The Requirement analysis is done in order to understand the problem the Software system is to solve. Requirements analysis is on identifying what is needed from the system, not how the system will achieve its goals . A client and a developer A communication gap The goal of requirements specification phase is to produce the software requirements specification document ( RAD ) .The person responsible for the requirements analysis is often called the analyst.

In this phase we study the system and observe the problem of existing system and think how to cover the problems ( problem analysis ) . There are two major activities in this phase Problem understanding or analysis Requirement specification The requirement document must specify all the functional and performance requirements ,the formats of inputs and outputs and all design constraints that exist due to political, economic, environment and security reasons. The phase ends with validation of the requirements specified in the document validation is often done through requirement review , in which a group of people including ,representatives of the client critically review the requirements specifications.

3.1 PROBLEM ANALYSIS

CURRENT SYSTEM
Now a days, almost everyone is using computers. Some people use it for writing letters, sending mails etc. Few people use it for developing applications and few people use it for entertainment purpose. Like this computers are useful for almost everyone in something or the other way.

When people are working with computers, they may or may not be aware of computers and more importantly when they are using the software products of different vendors, they may face some problems. If such is the case, the users may not get a proper solution immediately and sometimes it would also take a very long time to get a solution for his/her problem.

For getting proper solutions, the users have to contact the concerned organization that has provided the software and tell their problem. The concerned organization will then provide a solution for his/her problem within a period of time. Problems with the Current System 1 2 3 There is a communication gap between the customer and organizations. People generally dont know the sites of all the organizations to post their bugs. Customer face problem while posting their bugs occurred in different software as they have to post their bugs to different sites individually. 4 5 There is no surety of quick response from the organization. Few organizations may not be interested in responding to the customers. So in order to overcome all these limitations and to meet all their requirements the current process is replaced with this application. Abstract: The system deals with providing online support to the people who are facing problems with various s/w technologies. Problems with the current system there is a communication gap between the customer and the organizations. People generally dont know the name of the sites of all organizations to post their problem. Customer usually face some problem while posting the bugs occurred in different s/w as they have to post their bugs to different sites individually there is no surety of quick response from the organization .Few organizations may not be interested in responding to the customer problems .So in order to overcome all these limitations and to meet all their requirements , the current process is replaced with this application

Purpose :

The purpose of this document is to display all the external requirements for the 24X7 FIRMWARE SERVICESES . It also describes the system .The main objective of preparing this will be a guide in the other phase. The purpose of 24X7 FIRMWARE SERVICES to provide the solution for the bug posted by the customer within no time. The manager should be able to organize the entire bug efficiently and assign the bug to the concerned technical person. The system should provide the solution to the customer in possible proposed date. Scope :
This document is the only one that describes the requirements of the system. It is meant validating the for use by the developers and will be the basis for

interfaces of the detailed

document

is

to give a

description of the analysis and requirements for the system to be automated and this

final delivered system. Any changes made to the requirements in the future will have to go through a formal change approval process. The developer is responsible for asking for clarifications where permission of the client. Definitions & Abbrevations:
Not applicable

necessary

and will not

make any alterations without the

References :
Not applicable

Developers Responsibilities Overview:

1 2 3 Developing the System Testing the product at developers and users place Installing the software

4 5 6 7

Conducting the users training Maintaining the System Listening the Clients periodically to know the status of the product Any changes thereafter should be followed by testing and implementation

3.1.1 FUNCTIONAL REQUIREMENTS

General Description Of Inputs & Outputs:

The system will be getting input from registered users from various locations. The technical services status will be displayed at client station when the user supplies valid user name and password.

Requirements:
1. Every registered user will be allotted with a user name and password.

2. Customers,Managers,Administrators,Technicalpersons,Bugs,Solutions, Products information will be maintained. 3. Solutions are provided as online basis.

Administrative Module
The system should accept the following as input from Administration organization for successful login. Valid username Password After successful login, the administrator is provided with the following options, which require some data entry 1 2 3 4 To add a new Product. To add a new Manager. To add a new Technical person under Manager. To view Reports. The administrator has to register the details of products, managers and technical persons. For every product there will be a concerned manager who will take care of posting the problem to the concerned technical person. of

Manager Registration- This takes the following as Input

Manager Name Password Address Phone Email

After submitting all the details, a unique ID is generated to uniquely identify that particular manager.

Technical Person Registration- This takes the following as Input

Technical person Name Password Address Phone Email Manager-id Status After submitting all the details, a unique ID is generated to uniquely identify that

particular technical person.

Product Registration- This takes the following as Input

Product name Version Vendor name Manager-id After submitting all the details, ID will be generated which is given to the

products.

Customer Module Customer Login- This module takes the following details as Input
Customer name Password It validates all the above fields and if the input given is valid then the customer is allowed to enter to customer page. It is not validate all the above fields then the customer is allowed to enter to customer registration page.

Posting of Bugs - This module takes the following from customer as Input. CID Product Name Severity Priority Summary Details OS_Using Software_List File name Post_Date After submitting all the details, ID will be generated which is given to the bugs.

Manager Module

Manager Login- This module takes the following details as input manager
username.

Password
It validates all the above fields and if the input given is valid then the manager is allowed to enter to manager page.

Assigning Bugs to technical person:- This module takes the following. Details as Input BID CID TID Assignment_Date Expected_Date

Technical person Module

Technical person Login-This module takes the following details as Input Username Password It system validates all the above fields and if the input given is valid ones then the technical persons are allowed to enter to technical person page.

Writing solutions - This module takes the following input. BID TID Solution_Desc Solution_Date Priority

After submitting all the details, ID will be generated which is given to the solutions.

3.1.2 NONFUNCTIONAL REQUIREMENTS

Non functional requirements describe aspects of the system that are not directly related to the functional behavior of the system. On functional requirements include aboard variety of requirements that apply to many different aspects of the system. My system requirements. Performance requirements are concerned with quantifiable attributes of the system, such as RESPONSE TIME (how quickly the system reacts to a user input), THROUGHT PUT (how much work the system can accomplish within provides the following categories of non functional

a Specified amount of time) AVAILABILITY (the degree to which the system is accessible when required for use) Non-functional requirements describe user-visible aspects of the system that are not directly related to functionality of the system. User Interface A menu interface has been provided to the client to be user friendly. Documentation The client is provided with an introductory help about the client interface and the user documentation has been developed through help hyperlink. Performance Constraints 1 2 Requests should be processed within no time. Users should be authenticated for accessing the requested data

Error Handling and Extreme Conditions

In case of User Error, the System should display a meaningful error message to the user, such that the user can correct his Error. The high level components in proposed system should handle exceptions that occur while connecting to database server, IOExceptions etc. Quality Issues Quality issues refer to how reliable, available and robust should the system be? While developing the proposed system the developer must be able to guarantee the reliability transactions so that they will be processed completely and accurately.

The ability of system to detect failures and recovery from those failures refers to the availability of system. Robustness of system refers to the capability of system providing information when concurrent users requesting for information.

3.1.3 SCENERIOS

A use case is an abstraction that describes all possible scenarios involved actions . Scenarios are used as examples for illustrating common We describe a scenario using a template with three fields: 1 2 3 The name of the scenario enables us to refer to it unambiguously. The name of the scenario is underlined to indicate that it is an instance. The participating actor instances field indicates which actor instances are involved in this scenario. Actor instances also have underlined names. 4 The flow of events of a scenario describes the sequence of events step by step. 5 The entry and exit conditions are abstractions that enable developer to describe a range of conditions under which a use case is invoked. 6 The quality requirements are requirements that are not related to the functionality of the system.

in the

described functionality .A scenario is an instance of a use case describing the concrete set of cases .Their focus is on understandability. Usecases are used to describe all possible cases; their focus is on completeness.

3.1.4 USECASES

CUSTOMER

CUSTOMER 1.LOGIN/REGISTRATION

2.POST NEW BUG

3.BUGS ASSIGNED TO TECH PERSONS BY MANAGER CUSTOMER MANAGER

USECASE NAME : CUSTOMER ACTORS ACTIONS : CUSTOMER AND USER 2 :1 3

SCENARIO NAME
PARTICIPATING ACTOR FLOW OF EVENTS

CUSTOMER CUSTOMER 1.The Customer must be

MANAGER
MANAGER 1. MY PRODUCTS

2.ASSIGNED BUGS

3.BUGS TO ASSIGN

4.TECH STATUS

5.VIEW COMMENTS CUSTOMER TECHNICALPERSON

6.LOGOUT

TECHNICAL PERSON
TECHNICAL PERSON 1.PLACE THE SOLUTION

2.SOLUTIONS VERIFIED BY CUSTOMER

3.COMMENTS TECHNICAL PERSON CUSTOMER

3.2 FEASIBILITY STUDY

The feasibility study is to determine whether the system requested is feasible or not . This is to identify the objectives of a new system. Before solving a problem one must know what the problem is. This phase starts as soon as an user or a member of a particular department recognizes a problem and initiates a request to computerize the existing manual system or to modify the current computerized system. The study is carried out by a small group of people who are familiar with systems analysis and design process. Fact finding techniques are used to gather the required information. The major purposes of this study are given below : 1 Identify the responsible user and to develop an initial scope of the system. This may involve conducting a series of interviews to see which users are involved in and which users are affected by the proposed project. 2 Identify system. the current deficiencies in the users environment .This involves

preparing a list of functions that are missing or operating unacceptably in the existing

Determine added.

objectives

for

the

new

system. This involves

preparing a list of

existing functions which are to be reimplemented and new functions that are to be

Determine whether it is feasible to automate the system. This will involves some approximate estimates of the schedule and cost to build a new system.

Therefore in the preminary investigation we have observed that the automation of FIRMWARE SERVICES is feasible. The three major areas consider while determining the feasibility of the project are: Technical Feasibility

24x7

Economical Feasibility Operational Feasibility 3.2.1 TECHNICAL FEASIBILITY

In order to develop the project it requires licensed hardware and software .The analyst must find out whether current technical resources available in the organization is capable of handling the user requirements. If not ,the analyst with the help of the vendor should confirm whether the technology is available and capable of meeting the user s request and prepare a technical agreement involving these components . Technical feasibility is a study of whether we can develop the project using existing technology. As we can develop the automated24X7 FIRMWARE SERVICES using the existing technology , we can say that the system is technically feasible.

3.2.2 OPERATIONAL FEASIBILITY

Once it is determined that the system is both technical and economically feasible then it has to be seen if it is operationally feasible . Operational feasibility is dependent upon determining human recourses for the project. Alternatively , if users themselves have expressed a need for an improved system, then they will put in all efforts to see that it becomes operational.

We can achieve operational feasibility if the operator has minimum computer knowledge to operate the software .This can be easily achieved in this system. Thus this is also operationally feasible.

3.2.3 ECONOMICAL FEASIBILITY

Economic or financial feasibility is the third part of resource determination The basic resources to consider are : 1 2 3 Management time Time spent by the system analyst team Cost of doing the full systems study

4 5

Estimated cost of hardware Estimated cost of software The concerned business must be able to see the value of this investment before

committing to an entire systems study. If short term costs are not overshadowed by long term gains ,then the system is not economically feasible and the project should not proceed any further. Economical feasibility is calculating the difference between the manual system and proposed system economies. In this system , the cost of proposed system is less than the manual system.

3.2.2.1 COST BENEFIT ANALYSIS

The primary reason for cost and schedule estimation is to enable the client or developer to perform a cost benefit analysis .A more practical use of these estimates software projects, where the developers must give cost estimates to a is in bidding for potential client for the

development contract. Cost in a project is due to the requirements for software , hardware , and human resources. The bulk of the cost of software development is due to the human resources needed, and most cost estimation procedures focus on this aspect. In the dollars cost of a person month . The accuracy of the estimate will depend on the amount of reliable information we have about the final product. On the other extreme is the point when the project is being initiated or during the feasibility study. Specifications with uncertainty represent a range of possible final products, not one precisely defined product. Hence, the cost estimation based on this type of information cannot be accurate. As we specify the system more fully and accurately ,the uncertainties are reduced and more accurate cost estimates can be made. The accuracy of the actual cost estimates will depend on the effectiveness and accuracy of the cost estimation procedures or models employed on the process. Note :- This cost benefit analysis is not applicable in this project .

3.3 PROPOSED SYSTEM

To solve the above mentioned inconveniences to the registered users of our site we came with 24X7 FIRMWARE SERVICES .The main objective of the proposed system is to develop a permanent database in various tables each containing Either Customers, Administrators ,Managers, Products, Technical persons, Bugs, Solutions etc.. details .Because of , we developed these databases in RDBMS like ORACLE, data retrival will be very easy and fast and can retrieve specific data according to our choice. It also has a routine query optimizer that decides how the query can be executed in most efficient way when data base file is having too many records. The system has been proposed to be developed in ORACLE 9.0 as back end using J2EE friendly interface. as front end, which will give us user-

MAIN OBJECTIVE OF THE SYSTEM: Storing and Maintaining large amount of data in an efficient way. Avoiding unnecessary redundancy in data and eliminate inconsistency by Providing

validations. 1 2 Providing more user-friendly screens. Providing integrity constraints and validation checks during the data entry. 3 Integrating all the modules for the future implementation of the system

This package for 24X7 FIRMWARE SERVICES provides the convenient facility for the above stated process of maintaining upto date information of technical support services .With this package , the required task can be carried out easily and in less time.

Product Function Overview: This product interacts with mainly three entities i.e. Customer, Manager and Technical person. User Characteristics: The main user of the system is the Manager, even though the Administrator uses it, he will have less interaction when compared to manager. So to use the system, the manager should have the knowledge of the following topics: 1.The manager should have working knowledge on computers. 2.The manager should know how to use an operating system for running application.

3.4 PREPARATION OFREQUIREMENTSPECIFICATIONS 3.4.1 SOFTWARE REQUIREMENT SPECIFICATION

Software requirement specification (SRS) is the starting point of the software development activity. The SRS means translating the ideas in the minds of the clients (the input ) ,into a formal document ( the output of the requirements phase) .Thus the output of the phase is a set of formally specified requirements which hopefully are complete and consistent ,while the input has none of these properties. A procedure for identifying requirements can there for be at best set of guidelines. The requirements specification phase consists of two basic activities. 1. problem or requirement analysis 2. requirement specification The requirement specification phase terminates with the production of the validation software requirement specification document.

Role of SRS:Thus there are three major parties interested in a new system the client ,the users , the developer. There is a communication gap between these person. A basic purpose of SRS is to bridge this communication gap. SRS is the medium through which the client and user needs are accurately specified ;indeed SRS forms the basis of software development. An important purpose of the process of developing an SRS is helping the client to understand their own needs. A good SRS provides many benefits. Some of the goals it accomplishes are : 1. Establishing the basis for agreement between the client and supplier on what the software product will be reducing the development cost. 2. The preparation of the SRS forces rigorous specification of the requirements before the design begins. Careful development of an SRS can reveal omissions, inconsistencies and misunderstanding early in the development cycle ,which can considerably reduce cost. 3.Providing a reference for validation of the final product .The SRS assists in determining if the software meets the requirements .

4. SOFTWARE DESIGN
It is a process of planning the new or modified system. Analysis specifies what a new or modified system do. Design specifies how to accomplish the same. Design is essentially a bridge between requirements specification and the final solution satisfying the requirements. The design of a system is essentially a blue print or a plan for a solution for the system. The Design process for software systems has two levels. At the first level the focus is on depending which modules are needed for the system, the specifications of the of these modules and how the modules should be interconnected. This is what is called system design or top-level design. In the second level, the internal design of the modules , or how the specifications of the module can be satisfied is described upon. This design level is often called detailed design or logic design. The First level produces the system design , which defines the components needed for the system, how the components interact with each other. It focus is on depending which modules are needed for the system, the specifications of the of these modules and how the modules should be interconnected.

CONTEXT LEVEL DIAGRAM

UserName,Password,Registration Details PostNewBug,Solution of the Bug ,Comments Details

UserName,Password Details Bugs and Assignment ,Viewproducts, Techstatus,comments Details

Customers Report UserName,Password Handled Solutions,View Products Manager Report

Technicalperson Report Product Report New Products,managers,Technicalperson Details,View Reports Solution Report

CUSTOMER LEVEL DFD

CUSTOMER Update Details

S
SOLUTION BUG Update Details New/Registered

Customers
Details

Update

Details

MGR Assignment Of Bug Details ADMIN New Details Update Details Update Details Update Details PRODUCT

Providing Solution For bugs UpdateDetails Solutions Update Details Solutions Product Report Solution Report customer Report Manager Report Technical person Report

CUSTOMER LEVEL DFD

EXPANSION OF PROCESS - 2

BUG

New Details

Update Details

Customer name,

Password Valid BID

SOLUTION

Getting Details

COMMENTS

New Details

Update Details

ADMINISTRATOR LEVEL DFD

EXPANSION OF PROCESS - 5

Product New Details Update Details

Adname, Password Valid New Details

MGR

Getting Details

TECH_PER

New Details

Update Details

4.1 OBJECT

ORIENTED DESIGN METHODOLOGY 4.1.1 INTRODUCTION

Design Goals The definition of design goals is the first step of system design. In our proposed system the goals identified are reliability, fault tolerance, security and modifiability. 24X7 FIRMWARE SERVICES should be reliable; fault tolerant to loss of connectivity of server as well as it should be secure and can be modified later by any software developers. Performance Criteria

The proposed system 24X7 FIRMWARE SERVICES should have fast response while customers are posting their bugs, managers should be able to handle the bugs in an efficient manner and provide the response as quickly as possible. There should be no loss of information given by the customer regarding their bugs. Dependency Criteria The proposed system must handle both low level and high-level exceptions with appropriate alert messages. Cost Criteria It includes development cost, deployment cost, maintenance cost and administration cost. As the proposed system will be developed using software, which is free ware, hence it can be developed with minimum costs. As the proposed system is 24X7 FIRMWARE SERVICES, deployment of it requires certain amount. Maintenance costs required performing enhancements to the system. Administration costs are required to administrate the system.

Maintenance Criteria The proposed system is extensible i.e., new features can be added to the system and also it is easily modifiable and portable i.e. it is possible to adapt software developed for this system to different platforms. End User Criteria The proposed system supports the work of all the customers throughout the world. Hence it should be kept into the consideration that every customer can easily interact with the system. SUBSYSTEM DECOMPOSITION The developed system can be divided into following modules Customers:

1 2 3 4 5 Managers: 6 7 8 9 10 11

Customers Registration Customer Login Posting their bugs Viewing Solutions Writing Comments

Manager Registration Manager Login Viewing Assigned bugs Assigning Bugs to Technical Persons Viewing Comments Viewing Technical Persons Status.

Technical Persons: 12 13 14 15 Technical Person Registration Technical Person Login Viewing Bugs Writing Solutions for the Bugs

Subsystem Services Customers

Customer Registration - The aim of this module is to provide all the details of the customers so that by providing all the details, he can get registered with this web site. After registering, the customer will be getting a unique id. Using that unique id the customer can logon to this web site. Customer Login - The aim of this module is that the customers with their login ID and password can now logon to the Systems and use the service. Posting Bugs - The aim of this module is to provide all the details of the occurred bugs by the customer and post the complete details to the manager. Viewing Bug solutions - The aim of this module is to provide an interface to the customer to view the solutions of his posted bugs. Writing comments - The aim of this module is to provide an interface to the customer to comment on the given solution provided by the technical person. Managers Manager Registration - The aim of this module is to provide all the details of the managers so that by providing all the details, the Administrator can register the manager and after registering each manager provided with a unique ID. Manager Login - The aim of this module is that the managers with their login ID and password can now logon to the System and use the services provided to him. Viewing Bugs - The aim of this module is to provide an interface to the manager to view the bugs along with the details posted by the customers. Assigning Bugs to Technical Person - The aim of this module is to provide an interface to the manager to assign the bugs posted by the customers to the concerned technical person who are working under him. Manager should also confirm that the technical person should be free, before assigning to him. Viewing Comments - The aim of this module is to provide an interface to the manager to View the comments posted by the customers on the specific solution. This will be useful for the manager to know whether the bug was rectified by the given solution.

Viewing Technical Person Status - The aim of this module is to provide an interface to the manager to View the present status (i.e. FREE or BUSY) of all the technical persons who are working under him. Technical persons Technical Person Registration - The aim of this module is to provide all the details of the technical person so that by providing all the details, the Administrator can register the technical person and after registering, each technical person is provided with unique ID. Technical Person Login - The aim of this module is that the technical person with his login ID and password can now logon to the System and use the services provided to him. Viewing Bugs- The aim of this module is to provide an interface to the technical person to view the bugs along with the details assigned by his manager. Writing Solutions for the Bugs - The aim of this module is to provide an interface to the technical person to write the solution for the specific bug along with the priority. Access Control and Security The proposed system should perform the required authentication mechanisms and also provide security by using server side validations for login and also by handling exceptions. Boundary Conditions To decide how the system is started, initialized, and shut down and we need to define how we deal with major failures, such as data corruption, whether they are caused by a software error or a power outage we need to examine the boundary conditions.

4.1.2 DESIGN TOOLS UTILISED

The goal of UML is to provide a standardized notation that can be used by all object oriented methods and to select and integrate the best elements of precursor notations. The system development focuses on 3 different models of the system.

1) FUNCTIONAL MODEL: - represented in UML with use case diagrams

describes the functionality of the system from the user point of view.

2) OBJECT MODEL:-represented in the UML with class diagrams describes the structure of the system in terms of objects, attributes, associations & operations. 3) DYNAMIC MODEL: - represented in UML with sequence diagrams, state chart diagrams & activity diagrams describe the internal behavior of the system..
Sequence diagrams describes behavior as a sequence of messages Exchanged among a set of objects, where as state chart diagrams describes behavior in terms of states of an individual object & the possible transactions between the states.

FUNCTIONAL MODEL (USE CASE DIAGRAMS) (Functionality of the System) UML OBJECT ORIENTED DIAGRAMS (CLASS DIAGRAMS) (Structure of the system interms of objects)

DYNAMIC MODEL SEQUENCE DIAGRAM STATECHART DIAGRAM ACITIVITY DIAGRAM

4.1.2.1 ACTIVITY DIAGRAMS

An activity diagram describes the system in terms of activities. Activities are states that represent the execution of set of operations .The completion of these operations trigger a transition to another activity. In order to solve a particular problem what are the resources required and the order in which they are arranged to perform that activity. Activity diagrams are used to represent control flow and data flow. They are similar to flow charts.

ACTIVITIES

TRANSITION BETWEEN ACTIVITIES SYNCHRONISATION OF THE CONTROL FLOW

4.1.2.2 SEQUENCE DIAGRAMS

Sequence diagrams are used to formulate the behaviour of a system and visualize communication among objects. They are useful for identifying additional objects that Participate in the usecases. We call objects involved in the usecases as participating Objects. These represent the interaction that take place among objects. Each column represents the objects that participate in the interaction Labels on solid arrow represent message names and may contain arguments. Actor initiating the process is shown in left column.

If new cases are added they are represented in the right column showing Receiving the messages.

MESSAGES ACTIVATIONS / EXECUTING METHODS

4.1.2.3 CLASS DIAGRAMS

We use class diagrams to describe the structure of the system in terms of classes and objects. Developers are mainly responsible for performing any modifications .This is a tool used for structured system design the output of structured system design is system design document (SDD) which specifies the models of different classes and the modules involved and the relationship among the modules . Classes are the abstraction that Specifies the common structure and behavior of the set of objects. Class diagram Describe the system in terms of objects, classes, attributes, operations, association and Links, roles, multiplicity and aggregation. CLASS:A class is nothing but a collection of objects that shares a set of attributes and functions. Classes are abstracting that specifies the attributes and the behavior of set of Objects. Classes are represents by a rectangle. In this developed system the different classes we identified are: EMPLOYEE EDUCATION EXPERIENCE

PASSPORT PROJECTS

OBJECTS:Objects are entities that encapsulate state and behaviour.

OPERATIONS:Operations are specified what are the actions that are being performed in the System. In this system the operations are

4 5 6 7 8

Adding a new record Deleting the existing record Updating the existing record Viewing the related record

(ADD) (DELETE) (UPDATE) (VIEW)

Clear the records to enter a new record (CLEAR)

LINK:The link represents the connection between two objects. These links are established between different classes in the system. The link is represented by a straight line. ( ________ ) ASSOCIATIONS:Associations are the relationship between classes and represents groups of links. Associations is similar to classes in that they can have attributes and operations attached to them. Such an association is called an association class and is depicted by a Class symbol that

contains the attributes and operations and is connected to the Association symbol with a dashed line. ( ----------)

MULTIPLICITY: - (*) Each end of an association can be labeled by a set of integers indicating number of links that can legitimately originate from the instance of the class connected to the association end. This set of integers is called multiplicity of different types of associations such as : ONE TO ONE ASSOCIATION ONE TO MUCH ASSOCIATION MANY TO MUCH ASSOCIATION association end. The multiplicity supports

ROLE:Each end of the association can be labeled by a string called role. Role clarifies The purpose of association. Labelling the end of associations with roles allows us to distinguish among the multiple associations originating from a class. The roles are represents by strict figures.

In this system the identified roles are: USER /CUSTOMER MANAGER TECHNICAL PERSON ADMINISTRATOR

AGGREGATION:UML provides a concept of aggregation denoted by a simple line with a diamond at the end of the association.

1...............*

1..*

1*

11

4.1.2.4 OBJECT DIAGRAMS

4.1.2.5 STATE TRANSITION DIAGRAMS

5. DATABASE DESIGN 5.1 INTRODUCTION

Data Base: A database is a collection of data with some inherent meaning, designed, built and populated with data for a specific purpose. A database management system provides flexibility in the storage and retrieval of data. The DBMS is a bridge between the application program, which determines what data are needed and how they are processed, and the operating system of the computer, which is responsible for placing data on the magnetic storage devices. A schema defines the database and a subschema defines the portion of the database that a specific program will use. Characteristics: 1 2 3 Represents complex relationships between data. Keeps control on data redundancy. Keeps a centralized data dictionary for the storage of information retaining to data and its manipulation. 4 5 Enforces data access authorization. Has automatic intelligent backup and recovery Procedure for data.

Database Administrator: A database administrator is a block of code loaded into memory, which organizes all information (database) between the users. The DBA takes care of the following things: Updating database Retrieving the data Accepting the queries Enforces security Enforces data integrity specifications

Managing data sharing Optimizing queries Managing system catalogs

Representing of Null Values: The database management system has a consistent method for representing null values. For example, null values for numeric data must be distinct from the zero or any other numeric value for character data it must be different from string of blanks or any other character value. Catalog Facility: A logical description of a relational database represented in the same manner as pre ordinary data. This is done so that facilities of the relational management system itself can be used to maintain database description. Data language: A relational database management may support many types of languages for describing data and accessing the database. However there must be at least one language that was ordinary character strings to support the definition of data, the definition of views, the manipulation of data, constraints of data integrity information concerning authorization and the boundaries for recovery of units. View Updatability: Any view that can be defined using combination of base tables that are theoretically updateable is capable being updated by the relational database management system.

Insert, Update, Delete: Any operand that describes the results of a single retrieval operation is capable of being changes to be made to application program.

Logical Data Independency: Changes made to table the so not modify and data stored in the table do not require changes to be made to application program

5.DATABASE DESIGN 5.1 INTRODUCTION 5.2 E-R DIAGRAM

5.3 NORMAL FORMS IMPLEMENTED

Normalization :It is the process of splitting the database into some more desirable form by reducing the redundancy. .Advantages of normalization:1.To reduce the redundancy 2.To increase the access specification and storage structure. First Normal Form :A relation or a table is said to be in first normal form if and only if all the underlying domains contain at least atomic values.

Second Normal Form :A relation or a table is said to be in second normal form if and only if it is in first normal form and every non-key attribute is fully dependent on the primary key of the relation.

Third normal Form :A relation or a table is said to be in third Normal form if it is in second normal form and every non key attribute is transitively dependent on the primary key of the relation.

Boyce-codd Normal Form:A table is in BCNF iff the only determinants are candidate keys. A table is in BCNF iff every non trivial left irreducible FD has a candidate key as its determinant. NOTE:-

From the above considered definitions, on thorough study of our project we acquired that it has reduced and we eliminated the redundancy upto 2nd normal form.

5.4 TABLE DESCRIPTIONS

DATA DICTIONARY

CUST_REGI FIELD NAME CID CNAME PASSWORD ADDRESS PHONE EMAIL DATA TYPE NUMBER (4) VARCHAR2 (15) VARCHAR2 (15) VARCHAR2 (20) VARCHAR2 (15) VARCHAR2 (20) CONSTRAINT PRIMARYKEY

ADMIN FIELD NAME ANAME PASSWORD ADDRESS PHONE EMAIL DATA TYPE VARCHAR2(15) VARCHAR2(15) VARCHAR2(20) VARCHAR2(15) VARCHAR2(20) CONSTRAINT

MANAGER FIELD NAME MID MGRNAME PASSWORD ADDRESS PHONE EMAIL DATA TYPE NUMBER (4) VARCHAR2 (15) VARCHAR2 (15) VARCHAR2 (20) VARCHAR2 (15) VARCHAR2 (20) CONSTRAINT PRIMARYKEY

PRODUCT FIELD NAME PID PNAME VERSION VENDOR_NAME MID DATATYPE NUMBER(4) VARCHAR2(15) VARCHAR2(15) VARCHAR2(15) NUMBER(4) CONSTRAINT PRIMARY KEY

FOREIGN KEY

TECH_PER FIELD NAME TID TECH NAME PASSWORD ADDRESS PHONE EMAIL MID STATUS DATA TYPE NUMBER(4) VARCHAR2(15) VARCHAR2(15) VARCHAR2(20) VARCHAR2(15) VARCHAR2(20) NUMBER(4) VARCHAR2(6) CONSTRAINT PRIMARY KEY

FOREIGN KEY

BUG FIELD NAME BID CID PNAME PID SEVERITY PRIORITY SUMMARY DETAILS OS_USING SOFTWARE_LIST FILENAME POST_DATE ASSIGNED DATA TYPE NUMBER(4) NUMBER(4) VARCHAR2(15) NUMBER(4) VARCHAR2(30) VARCHAR2(6) VARCHAR2(30) VARCHAR2(30) VARCHAR2(15) VARCHAR2(15) VARCHAR2(15) DATE VARCHAR2(4) CONSTRAINT PRIMARY KEY FOREIGN KEY FOREIGN KEY

ASSIGN FIELD NAME BID CID TID ASSIGNMENT_DATE EXPECTED_DATE DATA TYPE NUMBER(4) NUMBER(4) NUMBER(4) DATE DATE CONSTRAINT PRIMARY KEY FOREIGN KEY FOREIGN KEY

SOLUTION FIELD NAME SID BID TID SOLUTION_DESC SOLUTION_DATE PRIORITY COMMENTS1 FIELD NAME BID COMMENTS DATA TYPE NUMBER(4) VARCHAR2(50) CONSTRAINT FOREIGN KEY DATA TYPE NUMBER(4) NUMBER(4) NUMBER(4) VARCHAR2(50) DATE VARCHAR2(6) CONSTRAINT PRIMARY KEY FOREIGN KEY FOREIGN KEY

6.TESTING

Testing is the phase where the errors remaining from all the previous phases must be detected. Hence, testing performs a very critical role for Quality assurance and for ensuring the reliability of software. Error: - It refers to the discrepancy between a computed, observed. It refers to the difference between actual output of the software and the correct output. Fault: - Fault is a condition that causes a system to fail in performing its required function. Failure: - Failure is the inability of a system or component to perform a required function according to its specification.

Levels of Testing:Client Needs Requirements Design Code Acceptance Testing System Testing Integration Testing Unit Testing

Software Testing:Testing is the process of executing the software with intent to detect and finding errors. Testing is classified into mainly two categories. 1) White Box (Glass Box or Structural) Testing. 2) Black Box (Functional) Testing.

6.1 STRUCTURAL TESTING ( WHITE BOX )

It focuses on logic and control structures of the module. Structural Testing is concerned with testing the implementation of the program. 1) Coverage criteria i) Statement coverage ii) Brach coverage (branch testing) iii) Path testing. (Loops can have an infinite number

Of possible paths). 2) Test Case Generation (Tool Support) 3) Instrumentation for Structural Testing.

Testing Strategies:1. Unit Testing (module wise testing) 2. Integration Testing (To check whether it gives the required output or not). 3. Validation Testing (To check whether it gives required output or not). 4. System Testing (To run the software developed by you in the client side. It defines the architecture of the system.)

Unit Testing:It is carried out on individual modules of the system. -"Drivers" is a dummy main program -"Stub" is a subprogram (or) a function i) Module interface is tested to see whether information is following correctly. ii) Local data structures are examined. iii) Boundary conditions are tested. iv) All the independent paths are tested to examine to ensure that all statements are executed at least once. Integration Testing:- It involves combining the modules and testing the problem. 1) Non Incremental Integration (Big Bang Test) All the modules are considered at a time and tested. This is to take, in case if no. Of modules are less, otherwise error correcting is complex. 2) Incremental Integration i) Top down integration 1. DFS integration.

2. BFS integration. ii) Bottom Up integration. Top down integration:1. The main module is tested first by adding the stubs 2. Depending on the integration approach (BFS, DFS) stubs are replaced one at a time with actual modules and testing is repeated. Regression Testing: It is performed to ensure that new errors are not introduced (conducting the previous test cases). Bottom - Up integration:1. All the low level modules are combined into clusters. 2. A driver is added to test the cluster. 3. Drivers are replaced by original modules. Validation Testing:1. Configuration review (Software and Hardware aviding) 2.Alpha, Beta Testing Configuration review:This is to inspect whether the software is satisfying all the requirements of the user and also to inspect the documentation. Alpha Testing:-

It is done under controlled environment of the client at the developers side It as an official release of the Software. Beta Testing:The clients in the absence of the developer do it at parallel sides. Once the beta testing is complete the developer am ounces an official release of the Software.

3. System Testing: 1. Recovery Testing. 2. Security Testing. 3. Stress Testing. 4. Performance Testing. Recovery Testing:It is a technique that forces the software to fail. If the software recovers back automatically (or) it recovers back with minimum human intension, then the software is said to be acceptable limits. Security Testing:This technique verifies the protection mechanisms of the software and decide whether the software developed can (dishonest people) Stress Testing: This technique performs the software Testing under abnormal situations Ex:- Stack Overflow, division by Zero etc.. protect in proper access by the hackers

Performance Testing:This is to determine whether the software is satisfying the runtime needs of the user. Test unit specification 4. Testing Process:1. Test Plans Features to be tested Approach for testing Test deliverables Schedule, personnel alloc. 2. Test Case Specification 3. Test Case execution and Analysis.

Quality Assurance Plans:To ensure that final product produced is of high Quality. Some Quality control activities must be performed throughout the development. The purpose of the software Quality assurance plans is to specify all the work products that need to be produced during the project, activities that need to be performed for checking the Quality of each of the work products, and the tools and methods that may be used for the SQA activities. Main task is "High Quality of a Software with low cost"

6.1.1 INTRODUCTION

6.1.2 LIST OF TESTCASES PREPARED

This document describes the plan for testing the course scheduling software. All major testing activities are specified here.
TEST CASES:

A test case is a set of input data and expected results that exercises the component with the purpose of causing failures and detecting faults. Test cases are classified into black box test and white box test. Black box test focus on input/output behavior of the component. White box test focus on internal structure of the components.

TEST CASE EXECUTION AND ANALYSIS:

Customer Module:
Test Case Condition Being Checked

Expected Output Displays oracle error message

Form submission

Checking connection

Invalid user name

Read Password Read Password

Redirect to Login page Redirect to customer page to Customer

Valid Password

Invalid Password Password length <3 Any compulsory field not selected

Check the validity of the Redirect password Read Password When submitting details Login page

Displays error message Displays message to

select particular field

Manager Module:
Test Case Condition Being Checked

Expected Output Displays oracle error message Redirect to Login page Redirect to Manager page to Manager

Form submission

Checking connection Read Password Read Password

Invalid user name

Valid Password

Invalid Password Password length <3 Any compulsory field not selected Technical Person:

Check the validity of the Redirect password Read Password When submitting details Login page

Displays error message Displays message to

select particular field

Test Case

Condition Being Checked

Expected Output Displays oracle error message Redirect to Login page Redirect to to Technical Technical

Form submission Invalid user name Valid Password Invalid Password Password length <3 Any compulsory field not selected

Checking connection Read Password Read Password

Person page Check the validity of the Redirect password Read Password When submitting details Person Login page Displays error message Displays message to

select particular field

6.2 FUNCTIONAL TESTING ( BLACK BOX )

It focuses on functional requirements of the module. In functional Testing the structure of the program is not considered. Test cases are decided slowly on the basis of the requirements or specifications of the program or module, and the internals of the module or the program are not considered for selections of the test cases. Some of the Techniques that are used for Functional Testing is: 1. Equivalence class partitioning. 2. Cause Effect Graphing. 3. Boundary value analysis.

6.2.1 INTRODUCTION
6.2.2 LIST OF TESTCASES PREPARED

7. FORMS DESIGN 7.1 INPUT FORMS DESIGN

7.2 OUTPUT FORMS DESIGN

8. IMPLEMENTATION / USER INTERFACE

The user interface is a user manual specifying the overall system in a very clear manner for any user to understand . User is promoted for input data at the required fields . This is one of the important phases of system development life cycle (SDLC). It includes all those activities that take place to convert the old traditional system to take new system. Proper implementation is essential to provide a reliable system to meet organizational needs / requirements .

8.1 ALGORITHMIC / NAVIGATIONAL DESCRIPTION

9. CONCLUSION

This software presents the part of an organization work as per the requirements, specifications and conditions mentioned in the user manual. This application s/w has been developed and completed successfully and also tests successfully by taking Test Cases. It is user friendly and has all the needed menu options, which can be utilized by the user to perform the desired operations. Moreover help messages are provided which will help any authorized user from using the system without trouble.

10 . BIBILIOGRAPHY

1.

AN INTEGRATED APPROACH TO SOFTWARE ENGINEERING By Pankaj Jalote Narosa Publications

2.

SOFTWARE ENGINEERING An Engineering Approach By Peters Pedrycz Wiely Publications

3.

COMPLETE REFERENCE

By Herbert Schield 4. 5. PROGRAMMING IN JDBC Oreally publications AN INTRODUCTION TO DATABASE MANAGEMENT SYSTEM C.J.Date Manual, Microsoft Press 6. MASTERING JAVASCRIPT & JSCRIPT James Jaworski 7. DEVELOPING JAVA SERVLETS James GoodWill

11.APPENDIX 11.1 ANNEXURE I (SCREEN LAYOUTS)

11.2 ANNEXURE II (SAMPLE CODE)

11.3 ANNEXURE - III (REPORTS)

11.3 ANNEXURE - IV (GLOSSARY)