Index

1. Abstract 2. About Organization 3. Project Synopsis 4. Feasibility Report 5. Analysis Report 6. Design Document 7. Client/Server Technologies 8. Coding 9. Installation and Screens 10. Testing and Debugging Strategies 11. Conclusions and Recommendations 12. References -Bibliography

About the Organization

Graben is founded by a group of dynamic technocrats and is complemented by professionals renowned for their multidisciplinary experience in Geo -Spatial and Engineering fields. Graben has made remarkable strides and deservedly carved a niche for itself in the fields of Geographical Information Systems (GIS), Engineering Design, Remote Sensing Applications, e-Publishing, Software development, and Corporate Training & Consultancy. Our phenomenal growth is due to our un wavering faith in our people and process as also our total commitment to excellence. Graben was awarded ISO 9001:2000 in recognition of its high standards in Geo -spatial and Engineering services and training. With the state-of-the-art technology, Graben provides the best services to its customers with primary focus on quality, cost-effective solutions and timely delivery that delights its customers. We constantly keep ourselves abreast with the changing and latest

technologies and developments and accordingly impart training to our people who matter. This helps us acquire expertise and specialization in our fields that enables us to handle and execute prestigious projects for our national, international clients all over. Our Mission To set the highest standards in our field by optimally utilizing the latest tools and techniques. Consistently strive for empowerment of our people and to offer our best in terms of quality to our clients always remains our primary concern.

A b s t r a c t
This project deals with huge amount of files that are maintained by government departments .The project will help all government departments to keep track of the files. Handling thousands of files is great problem in every government departments; moreover volume of files increases substantially. Every department follows a process for processing and every file has to be routed through many government officers like Officer of Superintendent (OS), Under Secretary Administration, Deputy Secretary, Additional Secretary and again back in same way. Or other side it may have to be routed through Assistant Engineer, Deputy Engineer, Superintendent Engineer, and Additional Chief Eng ineer and then to Secretary. Sometimes files are received from other departments and returned back after processing.

Existing System:In existing scenario, handling thousands of files is great problem in every government department; moreover volume of files increases substantially. Every department follows a process of processing and every file has to be routed through many govt. officers like Officer of Superintendent, Under Secretary Administration, Deputy Secretary, and Additional Secretary and again back in same way. Some times files are received from other departments and returned back after processing.

The problems with the existing system are

y y y y y y

Processing of documents would take about 15-20 days Tracing files became difficult after it was forwarded by a particular official Huge time delays when needed to refer to last references of letters, as Searching a particular mail was time consuming Huge cost of storage and maintenance of communication/ letters Dependency on peons/ clerks for fetchin g files

Proposed System:Our System is designed for Automation of Department of Industries. In this System, We need to process files in Hierarchy and proper action should be taken and necessary permissions are given for the requested Files. Sometimes we have to take concern of different departments into consideration. The new File Tracking System offers benefits like Easy File Tracking: At any point of time, the status of a pending file can be traced for a proponent. Restricted Access: Only authorized users have access. Person Independent Processes: Even if a person is away you can take action on any file. Senior Management Control: Senior Staff members can use the system to monitor and review the assignment of tasks, disposal of mails/documents. Web Access Manager: This is a feature whereby the documents can be referred to from any location, by any of the officials working on them.

P r o j e c t
This Project has six modules. Module 1: Administrator Module

S y n o p s i s

In this module Administrator will initiate the file and dispatch to any department .He can check exact status of the files and he receives completed files from other departments. Administrator can delete the files from database after processing of files. Administrator ca n see the pending files list. Module 2: Officer of Superintendent Officer of Superintendent receives the files from other departments to be processed. He can accept or reject the files from other departments. In this module he can also initialize the file, after completion of process he dispatches the file to any other department or directly to administrator. Module 3: Under Secretary Administration In this module, Under Secretary Administration department can initialize the file with details. This department can reject or accept the file which comes from other departments. Once file process completed then the department can send the files to any other department including administrator and the status of file is automatically updated. Module 4: Deputy Secretary Deputy Secretary can receive the files from other departments, he can process the files or reject the received files and he can see the processing files list. He can also initiate the files, and send the completed files to other departments for further processing or directly to the administrator. Module 5: Additional Secretary Additional Secretary can initiate the files with details, and he can receive the files from other departments to be processed .He can accept the files to process or reject the files. Once

the process n of the files completed then he can dispatch files to other departments for further processin or to the administrator directly. He can see the total pendin files list.

Module 6 Client

Client can check the exact status of the file in which department it is processin . If the file is rejected he can see the reason for the rejection. Client can reapply. These are the functions of six modules. This project will help people to keep track and to know exact status of their files through web. It will also help government officials to see the list of files pending with them.

Required Hardware

1. Pentium IV processes architecture 2. 128 MB RAM. 3. 20 MB Hard Disk Space 4. Ethernet card with an Internet or Internet zero.

Required Software

1. Windows 2000 Professional operating system. 2. Internet explorer 5.0 or Netscape navigation 3. Oracle 8i. 4. TCP/IP Protocol Suite. 5. Windows Based JVM. 6. Java, Servlets, JSP, Tomcat Server and Struts.

Feasibility:Technical Feasibility The system is self-explanatory and does not need any extra sophisticated training. As the system has been built by concentrating on the Graphical User Interface Concepts, the application can also be handled very easily with a nowise User. The overall time that is required to trains the users upon the system is less than half an hour. The system has been added with features of menu driven and button interaction methods, which makes the user the master as be starts working through the environment. The softwares that were used to develop the market. The net time the customer should concentrate is on the installation time. Financial Feasibility Time Based: If the administrator or the subjective manager has to know about the whe re about of the scheduled tasks, then in the manual system a concentrated search has to be applied through many registers or ledgers, which is time consuming .If within the system some data has to be registered then all the referential registers have to be filled sequentially which is a redundant process. With the designed database all these overheads are eliminated, making the actual system more faster in scheduling which keeps the system in pace with the associated trends and technologies. Cost Based: Within the manual system a perennial amount of finances are incurred continuously upon the extra staff for all the date integrated jobs. The information has to pan through many hands at proper time to apply the consistency standards which is the backbone for any organization, this application consistency is increased with the designed software which eliminates the actual investment upon the employees salaries increase the profits. The system over installed and configured makes the overall system to be intact with respect to required data exchange, on long term this effects the organization in controlling its costs and thereby increasing in its profits.

Oracle Introduction to Oracle

OR AC LE i s a co mp r eh en s i ve o p er at i n g en vi r o n men t t h at p acks t h e p o we r o f a mai n f r a me s y s t e m i n t o u s er mi c r o co mp u t er . I t pr o vi d e s a s et o f f u n ct i o n al p r o gr ams t h at u s er can u s e as t o o l s to b u i l d s t r u ct u r es an d p er f o r m t as ks . B ec au s e ap p l i cat i o n d e vel o p ed o n o r acl e ar e co mp l et el y p o r t ab l e t o en vi r o n men t an d t h en mo ve i t i n t o a mu l t i u s er p l at f o r m. Us e r s d o n o t h ave t o b e an exp e r t t o ap p r eci at e OR AC LE , b u t t h e b et t er u s er u n d er s t an d s t h e p r o gr a mmer , t h e mo r e p r o d u ct i vi t y an d cr eat i vi t y yo u wi l l u s e t h e to o l s i t p r o vi d es . What is a Relational Database Management System A r el at i o n al d at ab as e man ag e men t s y s t em ( R DBMS ) c an p er f o r m a wi d e ar r ay o f t as ks . I t act s a s a t r an s p ar e n t i n t er f ace b et ween t h e p h y s i ca l s t o r age an d a l o gi cal p r es en t at i o n o f dat a. I t p r o vi d es a s et o f mo r e o r l es s f l exi b l e an d s o p h i s t i cat es t o o l s f o r h an d l i n g i n f o r m at i o n . Us er can u s e t h i s t oo l t o :
 Define a database  Query the database  Add, edit and delete data  Modify the structure of database  Secure data from public access  Communicate within the networks  Export and Import data

Bec au s e i t gi ve s s o mu ch co n t r o l o ver d a t a, a r el at i o n al DB MS can al s o s av e a s t h e f o u n d at i o n f o r p r o d u ct s t h at gen er at e ap p l i cat i o n an d ext r a ct d at a. A Dat ab as e Man ag e men t s ys t e m ma y b e cal l ed f u l l y r el at i o n al i f i t supports: 1. Relational Databases and 2. A language that is at least as powerful as the relational algebra Dr. E.F.CODDSS RULES E.F.Codd specified a set of rules that an RDBMS has to do following 12 rules

1. Information rule: All information in a relational database including table names, column names, and domain names is represented explicitly by values in tables. With this design speed and productivity will be improved. 2. Guaranteed access rule: using a combination of table name, a primary key value and a column name can access Every piece of data in a relational database. With this productivity is improved since there is no need to resort to using physical pointers of address and provides data independence. 3. Systematic treatment of null values: The RDBMS distinguishes between blanks nulls in records and handles such values in consistent manner that produces correct answers on comparison and calculations. With these users can distinguish results of queries/operations that involve nulls, zeroes and blanks. 4. Active on-line catalog based on the relational model: The description of a database and its contents are database tables and therefore can be queried on-line via the database language. With this the DBAs productivity is improved since the changes are common in catalog to all tables for all queries and reports. 5. Comprehensive data sub-language rule: An RDBMS language supports definitions of tables/views. Query and update data, integrity constraints, authorizations, definitions of transactions. With this user productivity is improved since there is a single approach for all database operations. 6. View updating rule: Any view that is theoretically updateable can be updated using RDBMS. With this data consistency is ensured since changes in the underlying tables are transmitted to the view their support. 7. High-level insert, update and delete: The RDBMS supports insertion, updating deletion at al table level. With this the performance is improved by optimizing the path for execution. 8. Physical data independence: The execution of adhoc requests and application programs are not affected by the changes in the physical data access methods. With this DBA can make changes in application programs or adhoc requests. 9. Logical data independence: Logical changes in tables and views do not require changes in the application programs or in the format of adhoc req uests. With this databases can change and grow without changes in applications. 10. Integrity independence: Since constraints are stored in system catalog, they can be changed without changing application program. With this maintenance costs are reduced since only system catalog need to be changed.

11. Distribution independence: Application programs and adhoc requests are not affected by changes in the distribution of physical data. With this system reliability will be improved since application programs will work even if the programs and dare are shifted. 12. Non-Subversion rule: If the RDBMS has languages that access a record of a time it cannot be used to bypass integrity. With this data integrity is achieved since the system catalog is musts a. Code defined a relationally complete set of operations taking one or more relation as their operands. The operators are two groups: the traditional set of operators union, intersection, difference and Cartesian product and the special operators selection, projection, join and division. b. A fully relational DBMS has to support the above operations.

About Java
In my project, I have chosen Java language for developing the code. Initially the language was called as oak but it was renamed as Java in 1995. The primary motivation of this language was the need for a platform-independent (i.e., architecture neutral) language that could be used to create software to be embedded in various consumer electronic devices.
 Java is a programmers language.  Java is cohesive and consistent.  Except for those constraints imposed by the Internet environment, Java gives the

programmer, full control. Finally, Java is to Internet programming where C was to system programming. Java, Virtual Machine (JVM) Beyond the language, there is the Java virtual machine. The Java virtual machine is an important element of the Java technology. The virtual machine can be embedded within a web browser or an operating system. Once a piece of Java code is loaded onto a machine, it is verified. As part of the loading process, a class loader is invoked and does byte code verification makes sure that the code thats has been generated by the compiler will not corrupt the machine that its loaded on. Byte code verification take s place at the end of the compilation process to make sure that is all accurate and correct. So byte code verification is integral to the compiling and executing of Java code. Overall Description

Java Source

Java byte code

Java

.Class
Picture showing the development process of JAVA Program

Java Architecture Java architecture provides a portable, robust, high performing environment for development. Java provides portability by compiling the byte codes for the Java Virtual Machine, which is then interpreted on each platform by the run -time environment. Java is a dynamic system, able to load code when needed from a machine in the same room or across the planet. SERVLETS Introduction The Java web server is JavaSoft's own web Server. The Java web server is just a part of a larger framework, intended to provide you not just with a web server, but also with tools. To build customized network servers for any Internet or Intranet client/server system. Servlets are to a web server, how applets are to the browser. About Servlets Servlets provide a Java-based solution used to address the problems currently associated with doing server-side programming, including inextensible scripting solutions, platform -specific APIs, and incomplete interfaces. Servlets are objects that conform to a specific interface that can be plugged into a Java-based server. Servlets are to the server-side what applets are to the client-side - object byte codes that can be dynamically loaded off the net. They differ from applets in that they are faceless objects (without graphics or a GUI component). They serve as platform independent, dynamically loadable, plugable helper byte code objects on the server side that can be used to dynamically extend server-side functionality. For example, an HTTP Servlets can be used to generate dynamic HTML content. When you use Servlets to do dynamic content you get the following advantages:
  

Theyre faster and cleaner than CGI scripts They use a standard API (the Servlets API) They provide all the advantages of Java (run on a variety of servers without needing to be rewritten).

Attractiveness of Servlets There are many features of Servlets that make them easy and attractive to use. These include:
  

Easily configured using the GUI-based Admin tool Can be loaded and invoked from a local disk or remotely across the network. Can be linked together, or chained, so that one Servlets can call another Servlets, or several Servlets in sequence. Can be called dynamically from within HTML pages, using server-side include tags. Are secure - even when downloading across the network, the Servlets security model and Servlets sandbox protect your system from unfriendly behavior.

A d v a n t a g e s

o f

t h e

S e r v l e t

A P I

One of the great advantages of the Servlet API is protocol independence. It assumes nothing about:
  

The protocol being used to transmit on the net How it is loaded The server environment it will be running in

These qualities are important, because it allows the Servlet API to be embedded in many different kinds of servers. There are other advantages to the Servlet API as well. These include:


Its extensible - you can inherit all your functionality from the base classes made available to you. Its simple, small, and easy to use. o f S e r v l e t s

F e a t u r e s


Servlets are persistent. Servlet are loaded only by the web server and can maintain services between requests. Servlets are fast. Since Servlets only need to be loaded once, they offer much better performance over their CGI counterparts. Servlets are platform independent. Servlets are extensible. Java is a robust, object-oriented programming language, which easily can be extended to suit your needs Servlets are secure. Servlets can be used with a variety of clients.

 

 

L o a d i n g

S e r v l e t s

Servlets can be loaded from three places From a directory that is on the CLASSPATH. The CLASSPATH of includes service root/classes/ which is where the system classes reside. From the <SERVICE_ROOT /Servlets/ directory. This is *not* in the server's classpath. A class loader is used to create Servlets from this directory. New Servlets can be added - existing Servlets can be recompiled and the server will notice these changes. From a remote location. For this a code base like http: // nine.eng / classes / foo / is required in addition to the Servlets class name. Refer to the admin GUI docs on Servlet section to see how to set this up. L o a d i n g R e m o t e S e r v l e t s the JavaWebServer

Remote Servlets can be loaded by: 1. Configuring the Admin Tool to setup automatic loading of remote Servlets 2. Setting up server side include tags in .shtml files 3. Defining a filter chain configuration I n v o k i n g S e r v l e t s

A Servlet invoker is a Servlet that invokes the "service" method on a named Servlet. If the Servlet is not loaded in the server, then the invoker first loads the Servlet (either from local disk or from the network) and the then invokes the "service" method. Also like applets, local Ser vlets in the server can be identified by just the class name. In other words, if a Servlet name is not absolute, it is treated as local. A client can invoke Servlets in the following ways:
 

The client can ask for a document that is served by the Servlet. The client (browser) can invoke the Servlet directly using a URL, once it has been mapped using the Servlet Aliases section of the admin GUI. The Servlet can be invoked through server side include tags. The Servlet can be invoked by placing it in the Servlets/ directory. The Servlet can be invoked by using it in a filter chain.

  

Data Flow Diagrams

y

This Diagram serves two purpose. Provides an indication of how date is transformed as it system. Disputes the functions and sub functions that transforms the dataflow. moves through the

The Data flow diagram provides additional information that is used during the analysis of the information domain, and ser ver as a basis for the modeling of functions.

The description of each function presented in the DFD is contained is a process specifications called as PSPEC

ER-Diagrams
y

The entity Relationship Diagram (ERD) depicts the relationship between the data objects. The ERD is the notation that is used to conduct the date modeling activity the attributes of each data object noted is the ERD can be described resign a data object descriptions.

The set of primary components that are identified by the ERD are
 Data object  Attributes  Relationships  Various types of indicators

The primary purpose of the ERD is to represent data objects and their relationships.

Unified Modeling Language Diagrams

y

The unified modeling language allows the software engin eer to express an analysis model using the modeling notation that is governed by a set of syntactic semantic and pragmatic rules.

A UML system is represented using five different views that describe the system from distinctly different perspective. Each view is defined by a set of diagram, which is as follows.

User Model View i. This view represents the system from the users perspective. ii. The analysis representation describes a usage scenario from the endusers perspective.

Structural model view

 In this model the data and functionality are arrived from inside the system.  This model view models the static structures.

Behavioral Model View

 It represents the dynamic of behavioral as parts of the system, depicting the

interactions of collection between various structural elements described in the user model and structural model view. Implementation Model View


In this the structural and behavioral as parts of the system are represented as they are to be built.

Environmental Model View In this the structural and behavioral aspects of the environment in which the system is to be implemented are represented. UML is specifically constructed through two different domains they are


UML Analysis modeling, which focuses on the user model and structural model views of the system. UML design modeling, which focuses on the behavioral modeling, implementation modeling and environmental model views.

Use Case Diagrams Use cases model the system from the end users point of view, with the following objectives Use Case 1 Clerk:

Login

Add Files

Edit Files

Dispatch
Clerk

File Update

Use Case 2 : Administrator

Login

Admin

Creates Users

Maintain User Info

File Status

Administr ation

Class Diagrams Admin Initiate Action

Oninitiate bean

Accept File Action

File Status

'%7'3 '&@30A) 2 2 ( )3 %5%1) 6 2 2 8 '& )&5 '%7'3 '&@30AC ( '& @3)'& 2 2 2 2 2

'% '37'&@30A C( B1 %0)&7 2 2 2

)3 '%B1 @%))313' ) &73 @35 2

35&4 ( )5&% 38 3 %70D 2 2 9

)5&% 3835&4 &76 2 2

)3 355& &@ ) @35 ) (B) 3A@ & 9

3)% % %8 2

(@ 8 9

0) ( 35&4 &76 2

'(& 1 '& ( 2

35 @3C'(& 1 2 2

   

   

        "     "  

 

    

  

 

SEQUENCE DIAGRAMS:-

1) Admin Sequence Diagram:-

L g _J

:A

:L g A

:A

_J

  

   

 

1:

( q,

     

A m L g

      !   #

T A m ' P v g

2: v

   !

( q,

3:

()

4: G

 

5: A

7:

()

  

2) Clerk Sequence Diagram:-

    

A m A B

C k

L g _J

:A

:L g A

:N w

_J

N _J

C k B

()

6:

mC

k_J

0)

@35

0) 35&4 3

0) '& ( '&%$

1:

( q,

)3@ 3@ @3)D3 %7&5% 2

)3@ 3@ 31& @3)

C k L g

2: v

( q,

3:

N w

()

8 ( '& 8E35&4 @3)'& 2 2

35&4 3 77%

35&4 @( 8E3A &'A 93 %@3'3 2

C k' P v g

5:

7:

()

4:

() 6: B

8:

8:

'& ( @35

f PI XI c iU di Rdq cUPG I Iaa G P I id XPI S x S S Q S S

iU di Rd qcUPGI Iaa G g R UY XIa x S S Q t S

d cIb G X cIU df d UaY S S h

X cIU dfd cIb Ia` y S S

Xd cIb dI u w Xdi diid Xd UaI cU w S

Xdi did RI id X w YXW VPIHGFPIUT

d XUsU Uf S

YXW V iU di Rdq x S x rYdfpGi g R UY XIf S h S

Y XW VGedc Ib Ia` S

Y XW Vd cIb Ydfidg S S

PGI R P IHGF S Q

d c idqPGI R S w S Q

f PI XIc iU UdiRdq rYdf G PI idXPI xS S x S S S

iU diRdq rYdfG gR UYXIa x S xS t S

dcIb G XcIU df d UaY S S h

XcIU dfdcIb Ia` y S S

XdcIb dI u w Xdi diidXd UaIcU w S

Xdi didRI idX w YXW VPIHGFPIUT

dXUsU Uf S

YXW V PUaPd PIidYrq S S pGi gR UYXIf h S

YXW VGedcIb Ia` S

YXW VdcIb Ydfidg S S

PGI R PIHGF S Q

dc idqPGI R S w S Q

3) Superintendent Sequence Diagram:-

f pGi XIF dcIb adgR UYXIf Rdcdq S S hS

4) Deputy Ministry Sequence Diagram:-

PUaPd PIidYrX S S G Xd UcURX` S S

XdHPUgR iUXXdRdP X Iad x S PUaPd PIidYrq S S

idcR pGi ad UcURX`h S XdcIb UcYXIf x

XdHdccI Iiv w XP S U PdaPIidYrq S X GgX dri I u th

PIHGF P S U PdaPIidYrq S

'

f pGi XIF d cIb adg R UYX If Rdcd q S S hS

XdHd ccI Iiv w X iU di Rdq x S rYdf xS X Gg X d r i I u th

'

:O

:O

iU di Rd qcUPGI Iaa x S S Q G Xd UcU R X` S S XdHPUg R i U X Xd RdP X Iad x S iU di Rdq rYdf x S xS PUaPd P IidYrq S S pGi ad UcU R X` S h Xd cIb U cYX If x

PIHGF iU x S di Rdq rYdf xS

C o d i n g Coding for accept file action: package action; import javax.servlet.http.*; import org.apache.struts.action.*; import java.sql.*; import java.util.*; //import actionform.*; import Bean.*; public class acceptfileAction extends Action { public ActionForward execute(ActionMapping mapping,ActionForm form,HttpServletRequest request,HttpServletResponse response) throws Exception { String fno=""; Connection con=null;Statement st =null; HttpSession session=request.getSession(true); String empname=(String)session.getAttribute("empname"); System.out.println("Execute acceptfileaction"+empname); String fnoo=""; String dept=(String)session.getAttribute("dept"); java.util.Date d=new java.util.Date(); int da=d.getDate(); String dat=String.valueOf(da); int mo=d.getMonth()+1; String mon=String.valueOf(mo); int y=d.getYear()+1900; String year=String.valueOf(y); String ron=mon+"/"+dat+"/"+year; System.out.println("date"+ron); sendtobean ob=new sendtobean();

String a[]=request.getParameterValues("accept"); String b[]=request.getParameterValues("reject"); int sta=0; int len=0;int len1=0; try { Class.forName("oracle.jdbc.driver.OracleDriver"); on=DriverManager.getConnection("jdbc:oracle:thin:@localhost:1521:ORACLE","scott","tiger"); st =con.createStatement(); len=a.length; System.out.println("length of a = "+len); } catch(NullPointerException e) { System.out.println("Null length"); len = 0; //res.sendRedirect("message?msg="+"Values not selected."); } try { len1=b.length; } catch(NullPointerException e) { System.out.println("Null length FOR B"); len1=0; } if((len == 0)&&(len1==0)) return mapping.findForward("failure"); else { try { for(int i=0;i<len;i++)

System.out.println("department name"+dept); fnoo=a[i]; System.out.println("in for loop for a"+fnoo); int p=1; int j=st.executeUpdate("update filetrack set status="+p+",ron='"+ron+"', empname='"+empname+"' where fno='"+fnoo+"' and deptname='"+dept+"'"); } for(int i=0;i<len1;i++) { fno=b[i]; System.out.println("in for loop b"+fnoo); int q=3; System.out.println("department name"+dept); PreparedStatement ps=con.prepareStatement("delete from filetrack where fno='"+fno+"' and deptname='"+dept+"' "); ps.executeUpdate(); PreparedStatement ps1=con.prepareStatement("update filedetails set status="+q+" where fno='"+fno+"' "); ps1.executeUpdate(); } } catch(Exception e){System.out.println(e);} return mapping.findForward("success"); } } }

S c r e e n s

T e s t i n g
Test Plan Contents The objective of a Test Plan is to establish a strategy for testing. This should include the traceability information also so as to trace the requirements/specs from FS/Design/PS documents to system/Integration/Unit level test plans. The information should be filled up in such a way that the locations of features/items to be tested in test plan are mapped to the corresponding locations of the appropriate documents from which the plans are derived. GUI Unit Testing Guidelines for GUI Unit Testing Following points should be covered during testing: GUI Application

Items Tested

to

be Functionality / Features to be Tested

Functionality / Features not to be Tested

Graphical User Interface

5.Alignment and size of all controls on the screen should be checked. 6.Screens should be positioned at the center of the display. 7.Spelling and abbreviation of all labels along with size, font and color as per standards. 8.Controls/Screen properties should be uniform in the entire application. 9.All operations should be possible without using the mouse (using the accelerators and access keys) 10.Mouse interface / Keyboard interface: Check GUI with respect to all standard Screen Resolutions.

Screen

1.

The screen flow should be checked. Return

Navigation

from the screens should lead to the screen from which it was opened. 2. All child forms are opened as Model windows, except the Main form.

Validations

3.

Check for field / screen level validations of all Field level validations performance reasons,

fields on the screen when a save is performed (like can be skipped for dates, integer limits, etc.) various modes (Add and Modify) 4. Check for Enabling/Disabling of buttons in however relevant fields should be checked at screen level Database Updates Referential Integrity 5. Check for all fields if they are updated

and properly in the database. This can be done either by retrieving the records back in view mode or by directly executing SQL commands using a database utility 6. Check for database updates of non-display fields like "updated time", "updated by" etc. in the database

Functionality

Check all screens to ensure : 7. 9. Business Rules are met. 8. Logic is met. Correctness of all Computations. On Wrong / Bad field inputs, the behavior of Wordings of the

Error Handling 10. and Handling

Disaster the routine. The legibility and meaningfulness of the displayed displayed messages 11. Exception handling

messages

need not be stressed for they are taken from a user editable file / table.

Coding Discipline

Check for the following: 12. Unreachable code 13. Non terminating loops 14. Calls to subordinate units with invalid data

No special load testing shall be done for each unity unless for exceptional cases

15. Correct usage of data - length, types and storage classes. Watch for delays at any point during the execution of the unit test. Since unit testing is done on a local LAN, split second response is generally expected unless in exceptional cases. Multi-user environment Is multi-user situation handled ? Like multiple users making call to the routine, and the routine performing database updates / reads etc. Check if the behavior of routine in such cases acceptable. Like the rollback and commit to the database done properly with complete transactions in the database.

Stored Procedures Following points should be covered during testing of the stored procedures.

Items to be Functionality / Features to be Tested Tested

Functionality Tested

Features not to be

Functionality Routine / SP delivers expected functionality Error Handling The routines / stored procedures must not hang and should have graceful exit each time it fails for any reason like interface files missing, table not found etc.

C o n c l u s i o n
Conclusions and Recommendations The entire project has been developed and deployed as per the requirements stated by the user, it is found to be bug free as per the testing standards that are implemented. Any specification-untraced errors will be concentrated in the coming versions, which are planned to be developed in near future. The system needs more elaborative technicality for its inception and evolution. This System is designed in a sophisticated manner and it is very ease to make re-engineering and Future enhancements. Scope of Usage Computer systems are always prone to the latest changes in technology and mankind. Any system designed today has chances to become obsolete the very next day. A system should always be designed in such a way so as to incorporate the future requirements and enhancements. The system should be easily updateable without going for a new system.

B ib liog raphy

R ef er en ce s f o r t h e P r o j ect Dev el o p me n t wer e t a ken f r o m t h e f o l l o wi n g Bo o ks an d Web S i t es . Oracle PL/SQL Programming by Scott Urman SQL complete reference by Livion JAVA Technologies JAVA Complete Reference Java Script Programming by Yehuda Shiran Mastering JAVA Security JAVA2 Networking by Pistoria JAVA Security by Scotl oaks Head First EJB Sierra Bates J2EE Professional by Shadab siddiqui JAVA server pages by Larne Pekowsley JAVA Server pages by Nick Todd HTML HTML Black Book by Holzner JDBC Java Database Programming with JDBC by Patel moss. Software Engineering Software Engineering by Roger Pressman