I ACKNOWLEDGEMENT

I ACKNOWLEDGEMENT

II SYNOPSIS

1. INTRODUCTION

OVERVIEW

NEEW FOR THE SYSTEM

2. ORGANIZATION PROFILE

3. BACKGROUND STUDY

EXISTING SYSTEM

PROPOSED SYSTEM

4. SYSTEM STUDY AND PROBLEM FORMULATION

MAIN OBJECTIVE

PLATFORM SELECTION

HARDWARE SPECIFICATION

SOFTWARE SPECIFICATION

4.3. REASONS FOR SELECTING PLATFORM

5. SYSTEM ANALYSIS

FEASIBILITY STUDY

TECHNICAL FEASIBILITY

ECONOMICAL FEASIBILITY

OPERATIONAL FEASIBILITY

6. SYSTEM DESIGN

INPUT DESIGN

OUTPUT DESIGN

CODE DESIGN

DATABASE DESIGN

VALIDATION CHECKS

7. SYSTEM TESTING

TESTING

UNIT TESTING

INTEGRATION TESTING

SYSTEM TESTING

8. SYSTEM IMPLEMENTATION

9. SYSTEM SECURITY10. CONCLUSION AND SCOPE FOR FUTURE ENHANCEMENTS

11. BIBLIOGRAPHY

APPENDICES

A. ACTIVITY DIAGRAMB. USE CASE DIAGRAM

C. DATA FLOW DIAGRAM

D. E-R DIAGRAM

E. SCREEN SHOTS

F. REPORT

SYSNOPSIS

The project deals with automation of some of the steps involved in inspection process. As mentioned earlier, inspection is carried out in all major phases of SDLC (software development life cycle) to ensure the reliability and credibility of software. In this era of software revolution, inspection plays a significant role. All the software development firms follow their own stringent policies to ensure software reliability. Hence, there occur a necessity for such a software to reduce the burden of handling software development in a more easy and user friendly way.

The software is used to meet the requirements of Client in software development. The software is an intranet application which can be extended to the Internet with a very few modifications. The employees are provided with a well-defined GUI to carry out their operations irrespective of their location along with a greater security and ease.

Thus, the software monitors the software development at various phases of SDLC. Each user deals with his own duties to accomplish the tedious task of software development in a simple manner, which is the main goal achieved through the software.

Various processes such as selection of members for inspection, conducting meetings, sending and receiving important informations, operations performed by various personnels are automated in the course of this project. Other minute informations of great consideration to the project leaders such as project status, Inspection dates, employee details etc. can be retrieved easily through this intranet site. These are the main objectives attained through this project.Organizations wishing to optimize their inspection processes should consider this type of estimation tool. Inspections are still the most cost-effective way to detect defects in software

After the inspectors enter the inspection data into the tool, the output is the number of defects remaining in the inspected software (assuming all defects already detected will be fixed). The estimate adjusts for bad fixes.The tool also provides a recommendation as whether the software module should be reinserted or not based on the desired quality levels of the organization

1. INTRODUCTION

1.1. OVER VIEW OF INSPECTION TOOL:

This software achieves the following:

Verifies that the software element(s) satisfies its specification & applicable standards.

Identifies deviation from standards and specifications.

Collects Software Engineering data regarding the Process towards improving the process itself.

Identifies the bugs earliest in the software cycle.

It is a static technique (verification) compared to testing, which is a dynamic technique (validation) involving actual execution of the implemented code.

My project comprises of eight modules. They are

Login.

Administration

Creation of Inspection Team & Record

Existing Inspection Record

Modify an Existing Inspection Record

Meeting through Group Conferencing

Mail System

MODULE DESCRIPTION:

LOGIN:

A well-design login takes care of the authenticated users by providing different views. When a user logs in, his role is verified. If he is an administrator he is personal with an administrator view to achieve his personal tasks. If he logs in as any other user then he is prompted for a project code. The project code uniquely identifies the role of the user with in the software.

ADMINISTRATION:

Here Administrator plays a vital role in this tool. He is the person responsible for creating or removing authenticated users on demand. He is also responsible to add/remove projects and to enter author details for a project. He is provided with a well defined graphical interface to achieve these tasks.

CREATION OF INSPECTION TEAM & RECORD:

Here Moderator plays a vital role in this tool. He is provided with his personal view after login. The tasks performed by the moderator include

Selections of Inspection Team & Cross check Team.

Creating Inspection master plan template for various phases.

Viewing documents such as inspection master plan template, cross check defect logging sheet, defect logging sheet & inspection issues log.

Conduct various meeting such as kick-off meeting, logging meeting & brainstorming.

To set status of the project to currently running phase.

View employee details.

EXISTING INSPECTION RECORD:

Here Inspector plays a vital role in this tool. He is provided with a view that is of relevance to him. He deals with the following functions.

View the document to be inspected.

Inspecting the document and entering the defects in the defect logging sheet.

Defect details like number of Major, Minor and Observations from the Inspectors before starting the logging. Defects are logged page wise or section wise as per the identified sequence.

Attend meetings.

MODIFY AN EXISTING INSPECTION RECORD:

Here Author & Inspector plays vital roles in this tool. The author deals with the following functions.

Enter the documents to the server.

Incorporate comments if he feels that the comments are relevant.

Attend Meetings.

MEETING THROUGH GROUP CONFERENCING:

Here Moderator, Author, Inspector play vital roles in this tool. Moderator conducts various meeting such as kick-off meeting, logging meeting & brainstorming.

This module deals with following functions.

In Kick-off meeting, on completion of Cross Check and verification of entry criteria by the moderator Kickoff meeting for inspection of the document is convened. In the kickoff meeting the assumptions made and expectations out of the review is briefed to the inspection team by the author.

In Logging meeting, as per the agreed schedule Inspectors assemble for the logging of defects. Inspection comments are logged in the Inspection Issues log as per the sequence identified by the moderator. Author shall incorporate all the comments and any rejected comments will have to be justified by the author. Moderator will verify the incorporation of Inspection comments. Moderator feels that the review expectations are not met the document will have to be re-inspected again. The scribe logs accepted comments.

Brainstorm on improving the inspection process with all the reviewers .Moderator will verify the incorporation of Inspection comments. Moderator feels that the review expectations are not met the document will have to be re-inspected again.

MAIL SYSTEM:

A simple mailing subsystem deals with the mails within the software. A user can register him self to receive or send the mails. A well-defined graphical user interface is provided for these tasks. A user is informed during all the important stages in the inspection process through this mail address.

NEED FOR THE SYSTEM:

Necessity of the system is to do automatically from previous system done such of completely manual technique for finding and correcting errors, An unprepared reviewer can sit quietly and say nothing, Lack of resources Previous bad experience, Big egos, Time.

Thus this Tool is used to overcome all the drawbacks that were used previously so that all activities and tasks are carried through automation. So complete manual task was isolated and provides easy way to carry out the tasks.

2. ORGANIZATIONAL PROFILE

SDSOFT Solutions (India) Pvt. LtdSDSOFT Solutions (India) Pvt. Ltd. is a leading edge technology and IT consulting firm focused on delivering the best quality and most cost-effective solutions to our clients. SDSOFT consider IT as the backbone of a business efficiency eco-system and we provide complete solutions to address all aspects of your business, and across the entire chain - from conceptualization to implementation and actually running the process for you. Office in Bangalore, India.

SDSOFT is one of the few companies in the world to integrate technology and operations with a global services model. We provide highly customized application development, integration, internet services and maintenance for a wide range of businesses.

SDSOFT want our clients to focus on what they do best while we took care of the rest, by innovating and adding value. Outsourcing to SDSOFT gives you more time and resources to concentrate on your core competencies. Our range includes out- of-the-box solutions, technology consulting, customization and maintenance of applications, enterprise application integration, prototyping and architecture frame working. SDSOFT Company offers a complete range of the consulting, technology, operations and process outsourcing value chain. We develop competent solutions in the fields of website and application design and development, spanning a range of industries including but not limited to

1 E-learning

2 Financial Services

3 E-business

4 Application Engineering

5 Publishing, Media and Technology

6 Healthcare

Total Quality

We make sure that all products and services we deliver pass through the most stringent testing and review process and that they are 100% defect free. We wont stop at good enough because GOOD is not enough for our customers, and we wont stop at anything less than BEST for our customers. At SDSOFT, Quality is not just about implementing a system or working towards a set of standards. It is an attitude, a way of working, which not only improves businesses but the way people work and live. We strive to facilitate and promote the use of quality to add value to our customers and enhance the standing of quality professionals. It shows our clients that quality forms an integral part of everything we do. This makes sure those high quality standards that not only meet, but consistently exceed our client's expectations.

We believe that the success of any solution depends heavily on quick wins for the business. SDSOFT delivers on our promise through a mature global delivery service approach, which enables reduced time to market, provides access to world class technology talent, and delivers a quality product at a very competitive price point.

We believe that the success of any solution depends heavily on quick wins for the business. SDSOFT delivers on our promise through a mature global delivery service approach, which enables reduced time to market, provides access to world class technology talent, and delivers a quality product at a very competitive price point.

Application and Product Development

SDSOFT develops and designs state-of-the-art web page applications on new age technologies for its clients. All these applications have been critically acclaimed globally and have created a benchmark in their respective fields. The credit for all this goes to our highly specialized software development team who through their time tested development technology deliver all the projects in time and according to the budget. All the activities in business analysis, design, development and testing are conducted through the flexible and module based approach which ensures minimum client risk and also implementation of clients' requirements as per accepted international standards. Thus, we comply best with our committed deliverables and provide the best solution to our clients.

3. BACKGROUND STUDY

3.1. EXISTING SYSTEM

In the Existing system the process is done by only through manual. So the time consumption is high. The process such as defect bugs and in turn all the process involved in inspecting the product makes more complex. The conference of every task is difficult

to make the product robustness.

LIMITATIONS OF EXISTING SYSTEM

The limitations of the existing system are

Time Consumption. High Human Resource. No powerful Decision tool. A completely manual technique for finding and correcting errors

Observation: An unprepared reviewer can sit quietly and say nothing.

Previous bad experience

3.2. PROPOSED SYSTEM

A powerful statistical engine to estimate the number of defects in a software module during software inspections. A combination of techniques and data collected from the software inspection process itself are used to estimate quality.

After the inspectors enter the inspection data into the tool, the output is the number of defects remaining in the inspected software (assuming all defects already detected will be fixed). The estimate adjusts for bad fixes.The tool also provides a recommendation as to whether the software module should be re-inspected or not based on the desired quality levels of the organization.

Organizations wishing to optimize their inspection processes should consider this type of estimation tool. Inspections are still the most cost-effective way to detect defects in software.

ADVANTAGES OF PROPOSED SYSTEM

Advantages of the proposed system are

High Response Time. Group Conference [Chatting].

Automation Process between Author, Moderator, Inspector & Team Members.

Prevent introduction of defects - cheaper than repair.

Better understanding of software quality control.

Reduce effort expended on defect repair.

Reduce costs due to defects.

Improved product quality.

4. PROBLEM FORMULATION

4.1. MAIN OBJECTIVE: The system study is use of the users to do more flops of data entry, modification, deletions and report preparation. This makes each and every data with more functionally and security.

As mentioned in the SDLC concepts, the first step is to study the existing system and to confirm whether the proposed system is feasible. We studied the system closely, thus performing the function of an analyst. We sorted out different functions performed by different people in the system.

We studied the whole activities related to the inspection process carried out at each phase of SDLC. We thought of the possibilities of automation to be brought out in the new system and its feasibility concerns. Various activities performed, personnels involved, the steps involved and responsibilities of various persons in the inspection process in the existing system are as follows

Cross Check

After completion of document the author sends the document for cross check to the identified crosscheck team. Cross check team should not exceed maximum of three members with a minimum of one member. Defect logging sheet dully filled is sent to the reviewers along with document.

The purpose of cross check is to identify obvious defects, defects related to documentation, formatting and template related defects. Cross check team members log their comments in the defect-logging sheet and send it to the author. The author incorporates comments and the same is informed to moderator. Moderator verifies whether all cross check comments have been incorporated and entry criteria for inspection is satisfied. If any Cross Check comments are not incorporated justification has to be provided by the author.

Identification of Inspection Team

Inspection team identification and planning for each deliverable is done during project planning phase by the Project Manager as per Organizational norms defined in Metrics Process. Inspection team should not exceed six members with a minimum of three members. Schedule of inspection is reflected in SDP of the respective project.

Kickoff Meeting

On completion of Cross Check and verification of entry criteria by the moderator Kickoff meeting for inspection of the document is convened. In the kickoff meeting the assumptions made and expectations out of the review is briefed to the inspection team by the author. Logging date is agreed and a commitment from the reviewers is taken for the same. Specialization roles are assigned to the reviewers; defect rate and logging rate are also agreed upon. It is preferable to induct a new member for the Inspection and brief about the inspection process. Agreed logging date, defect rate and specialization roles are filled in the Inspection Master Plan template.

Logging Meeting

As per the agreed schedule Inspectors assemble for the logging of defects. Inspection comments are logged in the Inspection Issues log as per the sequence identified by the moderator.

The scribe logs accepted comments. If there is any repetition of the comments among the inspectors then those comments are not logged. The scribe obtains statistics like Individual Effort Spent on the inspection and defect details like number of Major, Minor and Observations from the Inspectors before starting the logging. Defects are logged page wise or section wise as per the identified sequence.

Incorporating Logging Comments

On completion of logging meeting author shall incorporate all the comments and any rejected Comments will have to be justified by the author. If any clarifications are required author will consult the Inspectors.

Follow- Up and Exit Criteria Check

Moderator will verify the incorporation of Inspection comments. Moderator will also check for the adequacy of the Inspection by verifying with the goals identified in the SDP. In Case Moderator feels that the review expectations are not met the document will have to be re-inspected again.

The study of the existing system was the base to create a new system. The main objectives for the proposed system were

To simplify and automate the present manual system.

To remove the drawbacks of the present system.

To reduce manual effort and increase efficiency.

To create an effective communication mechanism between team members.

To present the management with timely and informative reports.

4.2. PLATFORM SELECTION

4.2.1. HARDWARE SPECIFICATION

VIRTUAL MEMEORY

PROCESSOR

: 32 BIT, Pentium IV

RAM

: 256 MB

HARD DISK

: 40 GB

MONITOR

: SVGA Monitor (800 * 600 RESOLUTIONS)

CLOCK SPEED

: 266 MHz

KEYBOARD

: 101 KEYS

MOUSE

: Logitech

FLOPPYDRIVE

: 1.44 MB

4.2.2. SOFTWARE SPECIFICATION

OPERATING SYSTEM

: Windows 2000/XP.

FRONT END

: XML, HTML, DHTML

MIDDLEWARE

: J2EE

BACK END

: Oracle 8i

SERVER

: Web Logic 6.1

4.3. REASONS FOR SELECTING THE PLATFORM

Windows XP/2000 Advantages

The computing world was presented with the first release of the totally new and revolutionary operating system. Microsoft windows performance and features that previously has been accessible only on $20,000 annotations became instantly available to anyone with a high-end personal computer. Windows is now Microsoft Corporations premier operating system. Designed around a powerful and well thought software architecture, the primary features that allow Windows to use the full power of todays processors are

Scalability

The ability to run on a single pc chip with a single user up to a multi-user, microprocessor and network installation.

The Windows GUI

The familiar graphical user interfaces it presents to the world.

Technologies used:

J2EE:

J2EE introduced in 1998 defines a multi-tier architecture for Enterprise Information Systems (EIS).By defining the way in which the multi-tier application should be developed; J2EE reduces the costs, in both time and money, of developing large scale enterprise systems. The J2EE platform specifies the logical application components within a system and defines the roles played in the development process.

While developing a project, it is significant that the technologies using for development must be reliable, flexible and robust. In case of a customer support tool application like this, the matter is more important because it details with a large number of clients and handles confidential data. After comprehensive analysis, found that java and related technologies are more suitable for customer support tool applications since java has many features set that allow it to be an effective platform for customer support tool.

In addition, sun has a strong understanding of the critical business issues necessary to consider for customer tool. Another reason that java in variety of application servers. Java 2 enterprise Edition (J2EE) makes the java language an even better in the customer arena because of some key features.

J2EE makes java a fully-fledged server-side development platform.

J2EE has a solid infrastructure that provides a well-tested implementation of much common applications needs such as security and messaging.

J2EE standardizes development making it easier for companies to commit to J2EE.

Java2 Enterprise Edition or J2EE is a package of specifier aligned to enable the development of multiplier enterprise applications.

The specifications outline the various components needed within J2EE enterprise systems the technologies for accessing and providing services and even the roles played during the development, deployment and runtime lifecycle.

J2EE handles many critical tasks of customer support tool such as login maintenance and database maintenance and access.

J2EE ARCHITECTURE

Intermediate compilation

Runtime VM interpretation

Application Components

Four application components are defined in J2EE Platform .They are

Application Components(Stand alone java clients)

Applets(java code which executes within a browser)

Web Components(JSPs,Servlets)

Server Components(EJBs ,J2EE,API implementations)

Application clients

Clients are generally stand alone applications written in java. They run within a virtual machine and can use the J2EE services to access components located within another tier.

Applets

Applets are similar to application clients but execute within a web browser.

Web Components

They are server side components generally used to provide the presentation layer to be returned to a client. 2 types of web components exist : Java Server Pages (JSPs) and Java

Servlets.

Java Server Pages:

There are two ways to achieving dynamic content generation. They are,

Programmatic content generation.

Template-based content generation

Java servlets fall into the first category, while Java server pages belong to typically comprise of

Static HTML/XML components

Special JSP Tags

Optionally, snippet of code written in Java Programming Language called Scrip lets.

Unlike a plain HTML page, which contains static content that always remain the same, a jsp page can change its content based on any number of variable items, including the identify of the user, the users browser type, information provided by the user, and selections made by the user.

A jsp page contains standard markup language element such as HTML tags, just like a regular web page. A jsp element that allow the server to insert dynamic content in the page. Jsp elements can be used for a wide variety of purposes, such as retrieving user preferences.jsp pages share the Write Once, Run anywhere characteristics of Java technology. Jsp technology is a key component in the java2 platform, enterprise Edition, Suns highly scalable architecture for enterprise applications.

Jsp can use the full capability of JAVA components such as JDBC, RMI, CORBA, JMS and JNDI.Java Server Pages are built on top of Java servlets and are designed to increase the efficiency in which programmers and even non-programmers can create web content. The main advantages of using JSP are

JSP pages can be used in the combination with servlets that handle the business logic, the modal supported by Java servlets template engines.

Java Server Page Process:

JSP pages are interpreted only once; to java byte-code and reinterpreted only when the file is modified.

JSP supports both scripting based and element based dynamic content, and allows programmers to develop custom tag libraries to satisfy application-specific needs.

JSP pages are pre-compiled for efficient server processing.

JSP run on all the main web servers.

It is true that both servlets and JSP pages have many features in common and can be used for serving up dynamic web content.naturally,this may cause some confusion as to when to opt for one of the technologies over the other. Java Server Pages provide a much cleaner separation of presentation from logic, and are simpler to write. Together, JSP technology and servlets provide an attractive alternative to other types of dynamic web scripting/programming that offers platform independence, enhanced performance, and separation of logic from display, ease of administration, extensibility into the enterprise and most importantly, ease of use.

Server Components

Server components can be in form of EJBs (Enterprise Java beans). EJBs executes within a container that manages the runtime behavior of EJBs.

Working with the Model View Controller

Typically entity beans are used to provide the model logic, while a mix of entity beans and session beans are used to provide the control logic and web components are used to Implement both control and presentation logic.

The Java Beans specification allows software components to be written in java, which encapsulates the logic behind the web application and remove the bulk of the script let code that would otherwise clutter up the jsp.The result JSP code that is simpler, easier to maintain, and which is more readily accessible to non-programmers.

Java uses the beans specification to allow the creation of software components that can be used by other developers and designers to build specialist applications. Javas cross platform nature means that the same Java bean should be reusable across any machine. This really frees us from dependence on any particular platform

Database used:

Database is a major concern in a customer support tool application. Hence, made a detailed study to find the most suitable databases for the project. The result was Oracle

ORACLE:

Oracle is a trademark of Oracle Corporation and in common usage refers to the database engine (which actually looks for the data) and the range of front-end products. Oracle 8i is the largest selling SQL-based RDBMS and a most commercially useful product.

Advantage of Oracle 8i:

Portability

Oracle is ported for more platforms than any of its competitors running on more than 100 hardware platforms and 20 Networking protocols. This makes writing an Oracle application fairly safe from changes of direction in hardware and operating system and therefore a safe bet. You can develop a fairly full-featured application with little knowledge of the underlying operating system. Oracle 8i provides support for online backup and recovery and good software fault tolerance to disk failure. You can also do point-in-time recovery.

Performance

Speed of Oracle 8i database is quite well managed. Even with large database oracle 8i refers to more than 100GB databases and the performance is only raw. But includes consideration of performance with locking and transaction control.

Multiple Database Support

Oracle 8i has superior ability to manage multiple databases within the same transaction using a two-phase commit protocol. You can easily move were the data is actually stored from node-to-node in a network and have a data mirror, making it easy to optimize the location of the data from time to time.

Compatibility

Oracle 8i software is compatible with industry standard and industry standard operating systems. The applications developed can be used on any systems with little or no modification.

Connect ability

Oracle 8i software allows different computers and operating systems to share information across networks.

Security

Oracle 8i provides powerful security features to limit and monitor data access. These features make it easy to manage even the most complex design of data access.

Products of Oracle 8i

The following are some of the products of Oracle:

SQL * PLUS

SQL * DBA

SQL * FORMSSERVER SPECIFICATION:

Every inspection tool application needs an application server that provides a runtime environment for them. We also needed an application server for the successful working of our application. One reason for using J2EE as a web development tool is that various application servers support it. Hence, we have a choice to select servers such as BEA WebLogic, ATG dynamic and IBM Web Sphere. Among all these, our choice was BEA WebLogic. WebLogic is an industry-leading product that gives maximum choice and flexibility in building robust inspection tool applications that extend from web to the enterprise. It is high performance Java application server, which incorporates the most comprehensive implementation of the Java 2 Enterprise Edition (J2EE) standards.

WebLogic server provides the foundation for the rapid development of web applications and the performance and reliability required for mission-critical inspection tool sites. The reasons for choosing WebLogic in our application are,

Java Server Pages (JSPs), Java Message Services (JMS), Java Database Connectivity (JDBC) as specified by the J2EE standard.

Support for Oracle database.

Multitiered JDBC which allows a Java application to access and update database from anywhere on the network. The server includes its native JDBC driver fro leading database product and works.

Bea-Web Login Application Server Architecture

The BEA Web Logic Application Server

An integrated platform for assembling, deploying, and managing multi-tier java applications. BEA Web Logic is a Java application server for developing, integrating, deploying, and managing large-scale, distributed Web, network, and database applications. Defining the Java application server market,

BEA Web Logic:

Fully implements 10 of the 12Enterprise Java APIs, including JDBC, EJB, RMI, event management, and JNDI

Provides the most comprehensive implementation of the Enterprise JavaBeans 1.0 specification, including optional services such as session and entity beans

Provides tools to aid in the creation and management of Enterprise JavaBeans, permitting the hosting of both custom and off-the-shelf business components

Provides support for persistency to multiple databases

Deploys and manages applications to ensure scalability, availability, and security

Works easily with industry-leading databases, as well as Microsoft Visual Basic, Visual C++, Active Server Pages, and COM

Works easily with industry-leading development tools, including Visual Cafe, JBuilder, Supercede, J++, and Visual Age

BEA Server Scalability

A BEA WebLogic server scales to support many clients by carefully managing threads and connections. With BEA WebLogic, a single client/server connection is shared across all bidirectional communications, regardless of the request type and the number of remote objects being accessed.

Database connections are also shared so that the maximum number of simultaneous clients can be supported. BEA WebLogic caches database query results and can automatically update cached data in realtime as changes are made to the backing DBMS. Standard Internet Protocols Web browsers can access the BEA WebLogic application server via normal HTTP requests. Forwarding capabilities, such as HTTP proxying, enable dispatching to servers other than the original web server. For higher performance, HTTP connections are maintained across requests.

All BEA WebLogic services are also accessible via CORBA IIOP and TCP/sockets. Management BEA WebLogic provides centralized management for a potentially large distributed configuration of clients and servers through a ingle cohesive view of the overall system. Zero Administration Client (ZAC)

The BEA WebLogic application server supports the automatic distribution of Java applets, applications, or systems. With ZAC, program librarieseven a new BEA Web Logic releasecan be installed entrally by an administrator. BEA Web Logic pushes each updated component to all ppropriate Clients. The ZAC client itself has a very small footprint. Dynamic Application Partitioning the EA Web Logic application server permits online application components to be dynamically allocated across machines. Graphical Management Console

5. SYSTEM ANALYSIS

5.1. FEASIBILITY STUDY

All the projects are feasible given unlimited resources and infinite time. Unfortunately the development of the computer based system is more likely to be played by a security of resources and difficulty delivery dates.

Feasibility and risk analysis are related in many ways. If project risk is great the feasibility of producing the quality software is reduced. During system engineering however

We concentrate our attention on four primary areas of interest.

5.1.1. Technical feasibility study

A study of function performance and constraints that may affect the ability to achieve an acceptable system to any designated order

5.1.2. Economical feasibility study

An evolution of development cost weighted against the ultimate income or benefit derived from the developed system.

5.1.3. Operational feasibility study

A determination of any infringement, violation, or liability that could result from the development of the system. An evolution of alternative approaches to the development of the system.

A feasibility study is not warranted for system in which economic justification is obvious. Technical risk is low, few legal problems are expected, and no reasonable alternative needed for the project development.

6. SYSTEM DESIGN

6.1. INPUT DESIGN

Users are prompted with specified input box to obtain prior input from the user. They are designed in such a way that the users can cope up with the outputs that has been requested.

The input design must be in such a way that it must control the amount of input, avoid delay etc. It must be simple. The input design must ensure user-friendly screens, simplicity, providing ease of viewing and entering the data. The main objective of designing input focus on

Controlling the amount of input required

Avoiding delayed response

Controlling errors

Keeping process simple

Avoiding errors

6.2. OUTPUT DESIGN

Output is the key tool evaluates the performance of the software. so the design of the output should be done with great care. To initiate clearly the user are displayed with the specified flex grid controls to list about the details specified or mentioned by the corresponding operations selected by the user.

Reports for the organization including the details of the products purchased and sold that can be brought from the respective tables. These reports are generally maintained for the future reference of the concern in a specified format. If the Unnecessary records can be deleted from corresponding tables. The records can be easily viewed by clicking the flex grids. The output design must be in such a way that users must able to understand the purpose of the outputs. In order to serve the purpose of the report, the format should consist of the following,

Name of the output

Contents

Format

Frequency

Name of the output

Based on the output that is required, a name is given to each output.

Content

The content of the output must be in such a way that it must prevent redundancy, the data produced must be accurate, reliable and the output must furnish relevant data.

Format

The format has been designed in analysis according to user need and in importing table output formats as standard.

Frequency

The frequency of the output should be maintained according to the users needs.

6.3. DATABASE DESIGN:

Data base design is concerned with the data focus from the perspective of the system designer. The end product is called a database schema, a technical blueprint of database.

Database design translates the data models that were developed for the system users during the definition phase in to data structures supported by the choosen database technology. The goals of database design are as follows

A database should provide for the efficient storage, update and retrieval of data.

A database should be reliable-the stored data should have high integrity to promote user trust in that data.

A database should be adaptable and scalable to new and unforeseen requirements and applications.

The technique used to improve a data model in preparation for database design is called data analysis. Data analysis is a process that prepares a data model for implementation as a simple, non-redundant, flexible and adaptable database. The specific technique is called NORMALISATION. Normalization is a technique that organizes data attributes such that they are grouped to form stable, flexible and adaptive entities. The tables involved in inspection process along with attributes, data type, constraint and a brief description about the fields are stated in the below mentioned tables.

CREATE_EMP

FIELDDATA TYPEDESCRIPTION

enameVarchar2(50)Employee name

empidVarchar2(5),primary keyEmployee Identification number.

emailVarchar2(30)Employee email within the Software.

specialization

Varchar2(30) Specialization of the employee.

Grade

Varchar2(3) Grade of the employee

PROJECT

FIELDDATA TYPECONSTRAINTS

proj_nameVARCHAR2(50)Name of the project

proj_idVARCHAR2(20),primary keyProject code

author_nameVARCHAR2(50)Name of the author

proj_documentVARCHAR2(50)File names for the project

INSPECTION TEAM

FIELDDATA TYPECONSTRAINTS

project_code VARCHAR2(20)Project code

project_ name VARCHAR2(30)Project name

emp_codeVARCHAR2(5)Employee Code

emp_nameVARCHAR2(30)Employee Name

email_idVARCHAR2(50)Email id of the employee

DEFECT_LOGGING

FIELDDATA TYPECONSTRAINTS

Proj_name

VARCHAR2(20)Project name

Proj_docVARCHAR2(30)Project file name

Defect_severityVARCHAR2(5)Severity of the error

Defect_classVARCHAR2(30)Where the defect occurred

Defect_rootVARCHAR2(30)Root of error in the file

Injected_phaseVARCHAR2(30)Phase name where the error occurred

Defect_stateVARCHAR2(30)Status of the defect

DescVARCHAR2(100)Suggestion for the error

MAILDETAILS

FIELDDATA TYPECONSTRAINTSDESCRIPTION

FirstnameVarchar2NotNullFirst name

LastnameVarchar2NotNullLast name

AddressVarchar2NotNullAddress

StateVarchar2NotNullState

ZipcodeVarchar2NotNullZipcode

UsernameVarchar2Primary keyMail id of user

HintqVarchar2NotNullHint question

HansVarchar2NotNullHint answer

7. SYSTEM TESTING

7.1. TESTING Testing is vital to the success of the system. System testing makes a logical assumption that if all parts of the system are correct. The goal will be successfully achieved. There are four steps with in, they are,

White-box Testing

Black-box Testing

Unit Testing

Integration Testing

Validation testing

Output Testing

7.1.1 WHITE-BOX TESTING

This is performed knowing the internal workings of a product, tests are conducted to ensure that all gears mesh, that is, that internal operation performs according to specification and all internal components have been adequately exercise. This can be done on close examination of procedural detail. Providing test cases that exercise specific set of conditions and / or loops tests logical paths through the software.

Using the white-box testing we can derive test cases that Guarantee that all independent paths within a module have been exercised at least once.

Exercise all logical decisions on their true and false sides.

Execute all loops at their boundaries and within their operational bounds and Exercise internal data structures to assure their validity.

By the test cases each of the JIS modules have executed at least once and tested for bugs. All the logic decisions on their true and false sides are executed so that the system will perform well.

7.1.2 BLACK-BOX TESTING

Knowing the specified function that a product has been designed to perform, tests can be conducted that demonstrate each function is fully operational, at the same time searching for errors in each function. It enables us to derive sets of input conditions that will fully exercise all functional requirements for a program.

It attempts to find errors in the following categories:

Interface errors.

Errors in date structures or external database access.

Incorrect or missing functions.

Performance errors.

Initialization and termination errors.

Tests are designed to answer the following questions:

How the functional validity tested?

What classes of input will make good test cases?

Is the system particularly sensitive to certain input values?

How are boundaries of a data class isolated?

What data rates and data volume can the system tolerate?

What effect will specific combinations of data have on system operation?

All the functions in the system are tested one after another and the desired tasks are fulfilled. Input values should lie in the data values size and these must check before processing. All the boundary values are tested.

System testing strategies have the following generic characteristics:

Testing begins at the module level and works outward toward the integration of the entire computer-based system.

Different testing techniques are appropriate at different points in time.

The developer of the software and an independent test group conducts testing.

Testing and debugging are different activities, but debugging must be

Accommodated in a testing strategy.

7.1.3 UNIT TESTING

In this testing, the smaller part of the project is tested first that is modules and the sub functions present in the project. It seems to be working satisfactorily with out the errors and that shows the unit testing is successful.

4.1.4 INTEGRATION TESTING

The integration testing is a part that the software makes all functions behaviors and process required. The errors which are uncovered are integrated testing, are corrected during this phase. The collection of the functions are tested and found with errors are rectified .So that the result can be easily obtained in a successful manner.

7.1.5. VALIDATION TESTING

The validation part is very much essential for each every application projects so that each data can be validated in a good manner. In some cases the records are created according to the key of the corresponding table to which it has been referenced for data constraint for good secured database. While testing the system by using test data errors are again uncovered and corrected by using above testing steps and corrections are also noted for future use. If there is any error then it is allowed for testing from the beginning.

7.1.6. OUTPUT TESTING

The output is major required part of the development of the project. The output is tested for required format, if it does not acquire such format then the testing is done or any screen modification is alone for the further operations. The output testing is mainly for the two things they are,

On screen format

Print format

The screen is found to be correct as the format designed according to the user needs for the hard copy also; the output comes out as specified by the user. Hence output testing doesnt result in any correction in the system.

7.1.7. TEST CASE:

This product is built on GUI using JFC and networking programming. We have to test the events and in associated function by doing specified tasks. These cases are listed below.

ADMIN LOGIN

Unit Test caseDescriptionExcepted resultActual resultremarks

UT01In this login page, enter valid username and password.The Admin Homepage should be displayed.The Admin Home page will be displayed.No Remarks

UT02In this Admin Homepage all Hyperlinks are displayed on the admin Header. Click on designation link.The I designation Form should be displayed.The designation Form will be displayed.No Remarks

UT03You want to go department page, Click on department link.The department Form should be displayed.The department Form will be displayed.No Remarks

UT04You want to go user creation page, Click on user creation link.The user creation Form should be displayed.The user creation Form will be displayed.No Remarks

UT05You want to go Homepage click on Home link.

The Employee Homepage should be displayed.The Employee Homepage will be displayed.No Remarks

DESIGNATION

Unit Test CaseDescriptionExcepted ResultActual ResultRemarks

UT01In this designation page, you want to create new designation, enter new designation and click on" Create" button.The new designation should be created. The new designation should be added on the designation table in the same page.New designation will be created successfully. if the designation is already exist it shows message. No Remarks

UT02Select the checkboxes to which records, you want to delete and click on "Delete" button.Before going to delete we expect it gives an alert msg, are you sure you want to delete. You want to delete particular designation click OK button.The selected designation will be deleted successfully.No Remarks

UT03you want to go Homepage click on "Home" link.The Admin Homepage should be displayed.The Admin Homepage will be displayed.No Remarks

UT04you want to go Login page click on "Logout" link.The Login page should be displayedThe Login page will be displayedNo Remarks

DEPORTMENT

Unit Test CaseDescriptionExcepted ResultActual ResultRemarks

UT01In this department page, you want to create new department, enter department and click on "Create" button.The new department should be created. The new department should be added on the department table in the same page.New department will be created successfully. if the department is already exist it shows message.No Remarks

UT02Select the checkboxes to which records, you want to delete and click on "Delete" button.Before going to delete we expect it gives an alert msg, are you sure you want to delete. Particular department click OK button.The selected department will be deleted successfully.No Remarks

UT03You want to go Homepage click on "Home "link.The Admin Homepage should be displayed.The Admin Homepage will be displayed.No Remarks

UT04You want to go Login page click on "Logout" link.The Login page should be displayedThe Login page will be displayedNo Remarks

Unit Test CaseDescriptionExpected ResultActual ResultRemarks

UT01In this Injuries page, you want to create new Injury, enter new Injury and click on "Create" button.The new Injury should be created. The new Injury should be added on the Injuries table in the same page.New Injury will be created successfully. if the Injury is already exist it not show messageThe existing injury is no-shows the message it gives some error.

UT02Select the checkboxes to which records, you want to delete and click on "Delete" button.Before going to delete we expect it gives an alert msg, "are you sure you want to delete. You want to delete particular Injury, click "OK" button.The selected Injury will be deleted successfully.No Remarks

UT03you want to go Homepage click on" Home" link.The Admin Homepage should be displayed.The Admin Homepage will be displayed.No Remarks

UT04you want to go Login page click on "Logout "link.The Login page should be displayedThe Login page will be displayedNo Remarks

INJURY

BODY PART

Unit Test CaseDescriptionExpected ResultActual ResultRemarks

UT01In this Body part page, you want to create new Body part, enter new Body part and click on "Create" button.The new Body part should be created. The new Body part should be added on the Body part table in the same page.New Body part will be created successfully. if the Body part is already exist it shows message. No Remarks

UT02Select the checkboxes to which records, you want to delete and click on "Delete" button.Before going to delete we expect it gives an alert msg, "are you sure you want to delete. you want to delete particular body part click "OK" button.The selected Body part will be deleted successfully.No

Remarks

UT03You want to go Homepage click on "Home" link.The Admin Homepage should be displayed.The Admin Homepage will be displayed.No

Remarks

UT04you want to go Login page click on "Logout" link.The Login page should be displayedThe Login page will be displayedNo

Remarks

HOW CODE

Unit Test CaseDescriptionExcepted ResultActual ResultRemarks

UT01In this How code page, you want to create new Code ,means what happens and create How, means how it happens, enter new Code, How and click on Create button.The new Code, How should be created. The new How occur should be added on the How code table in the same page.New Code, How will be created successfully. if the Code is already exist it shows message. No Remarks

UT02Select the checkboxes to which records, you want to delete and click on "Delete" button.Before going to delete we expect it gives an alert msg, "are you sure you want to delete. You want to delete particular incident click OK button.The selected incident will be deleted successfully.No Remarks

UT03you want to go Homepage click on "Home" link.The Admin Homepage should be displayed.The Admin Homepage will be displayed.No Remarks

UT04you want to go Login page click on "Logout" link.The Login page should be displayedThe Login page will be displayedNo Remarks

USER CREATION

Unit Test CaseDescriptionExcepted ResultActual ResultRemarks

UT01In this How code page, you want to create new Code, means what happens and create How, means how it happens, enter new Code, How and click on Create button.The new Code, How should be created. The new How occur should be added on the How code table in the same page.New Code, How will be created successfully. If the Code is already exist it shows message. No Remarks

UT02Select the checkboxes to which records, you want to delete and click on "Delete" button.Before going to delete we expect it gives an alert msg, "are you sure you want to delete. You want to delete particular incident click OK button.The selected incident will be deleted successfully.No Remarks

UT03You want to go Homepage click on "Home" link.The Admin Homepage should be displayed.The Admin Homepage will be displayed.No Remarks

UT04You want to go Login page click on "Logout" link.The Login page should be displayedThe Login page will be displayedNo Remarks

EMPLOYEE INJURY REGISTRATION

Unit Test CaseDescriptionExcepted ResultActual ResultRemarks

UT01In this Injury Registration page, you want to register new injury Details, fill all fields and click on "Create" button. Here some fields are existing data.The new injury details should be registered.New injury details will be registered successfully. No Remarks

UT02If you want to search any particular injury details, click on Search" link. The search will be done based on Employee/Name.Based on search, Injury details should be displayed.The injury details will be displayedNo Remarks

UT03You want to reset the values, click on "Reset" button.The form values should be clear.The form values will be cleared.No Remarks

UT04you want to go Homepage click on Home "link.The Admin Homepage should be displayed.The Admin Homepage will be displayed.No Remarks

UT05You want to go Login page click on "Logout" link.The Login page should be displayedThe Login page will be displayedNo Remarks

EMPLOYEE LOGIN

Unit Test CaseDescriptionExcepted ResultActual ResultRemarks

UT01In this login page, enter valid username and password.The Employee Homepage should be displayed.The Employee Home page will be displayed.No Remarks

UT02In this Employee Homepage all Hyperlinks are displayed on the admin Header.The Employee Homepage should be displayed.The Employee Homepage will be displayed.No Remarks

UT03You want to go Homepage click on Home link.The Employee Homepage should be displayed.The Employee Homepage will be displayed. No Remarks

UT04You want to go Login page click on Logout link.The Login page should be displayedThe Login page will be displayedNo Remarks

TIME LOST OUT

Unit Test CaseDescriptionExcepted ResultActual ResultRemarks

UT01In this Time Lost Details page, to know the how many days the respective employee left the work click on the respective "no of days return to work" text box, the respective days will be displayed.The no of days for respective employee will left the work should be displayed.The total no of days for respective employee will be displayed.No Remarks

UT02In this Time Lost Details page, to know the how many days the respective employee, return to normal duties click on the respective "no of days return to work" text box, the respective days will be displayed.The total no of days should be displayed.

The total no of days will be displayedNo Remarks

UT03In this page, if you want to investigate the respective person for more details click on the "YES" button. Its goes to the respective "investigation "pageThe respective investigation page should be displayed.The respective investigation page will be displayed.No Remarks

UT04After completion of investigation, click on the "Submit" button. The respective employee investigation details will registered in the databaseAfter completion of investigation, click on the "Submit" button. The respective employee investigation details will registered in the databaseThe respective employee investigation details will be stored in the respective tablesNo Remarks

UT05You want to clear the form values, click on "Reset" button.The few investigation details should be stored the "Time lost Details" table in the databaseThe few investigation details will be stored the"Timelost Details" table in the databaseNo Remarks

UT06You want to clear the form values, click on "Reset" button.

The form values should be clearedThe form values will be cleared.No Remarks

UT07You want to go Homepage click on "Home" link.The Admin Homepage should be displayedThe Admin Homepage will displayedNo Remarks

INCIDENT REGISTRATION

Unit Test CaseDescriptionExcepted ResultActual ResultRemarks

UT01In this Incident Registration page, you want to register new incident Details based on incident date and time, fill all fields and click on "Submit" button.The incident Details should be registered.Incident Details will be registered successfully. No Remarks

UT02If incident date and incident time matches the registered records ,the respective details will be displayed, when we click on the "YES" button which related to injury to any person field".If date and time matches, the records should be displayed. if not matches it gives the "no such records found" message. The incident details displayed in the same page.date and time are matches, the respective records will be displayed. if not matches it gives the "no such records found" message.No Remarks

UT03You want to clear the form values, click on "Reset" button.The form values should be cleared.

The form values will be cleared.No Remarks

UT04You want to go Homepage click on "Home" link.The Admin Homepage should be displayed.The Admin Homepage will be displayed.No Remarks

8. SYSTEM IMPLEMENTATION

Training the operating staff

Installing hardware

Installing terminals

Installing telecommunication network before system is up and running.

In the implementation phase, the project reached its fruition. After the development phase of the SDLC is complete, the system is implemented. The software, which was designed in design and programmed in development phase of the SDLC, was installed on all the PCs that require it. The personas using the program was trained during this phase of the SDLC. Moreover, both the hardware and software are tested. Although we found and fixed many problems, almost invariably, the users helped us to uncover problems that we were unable to simulate.

These were the main activities performed by us in the course of the project, which lead to its proper completion.

POST IMPLEMENTATON REVEIW

When computer based systems are built therefore we must develop mechanism for evaluating controlling and making modifications, maintenance issued to improve the case with which the changes can be accommodated and reduce the amount of expended on its maintenance activity occurs because it is unreasonable to assume that software testing will uncover all latest errors in a large software system. The final event in the post implementation flow is review that revalidates all elements of the system configuration and ensures correctness, after the software maintenance, software reviews is being conducted for future maintenance effort and provides feedback, which is important to effectively management of software organization.

9. SYSTEM SECURITY

An important feature that has been to be implemented in any project is the security that has been offered by restricting the access of the information by the third persons, Since my software deals with recording the transactions between company to the customer through the intermediatories dealers and retailers and preparation of financial statements that is accessible only for the determination of company financial position.

In the company only the administrator must have the rights to view the financial statements of the firm. The operator or employees should not be informed about the financial position of the firm. To administrate such details they are created separate accounts i.e. administrator has given full rights to access the project details. The operator only has restricted information to be accessed.

The administrator has full rights to monitor the transactions details and preparation of financial statements. The database access is also limited i.e. a database is stored in separate root directory where it is hidden without inferring to the user.

Most primarily it does not access or manipulate any secured data or database which is the key necessary to have the security. Hence here it does not take control of all such activities, so it does have no requirement to have one. The only file, which is used by this system, is the assignment of client id, which is created by the server. Even this file has to be accessed by the entire client it does not require any security norms. Hence no client validation was carried during such process was being carried.

Even the message queue, which is handled by this system, is not a secured data and the simulation should be open to the entire user to understand this simulation process. Hence for all these reason no security was imposed even on such data also.

10. CONCLUSION AND FUTURE ENHANCEMENTS

Thus the successful design, development and implementation of this message monitoring were done. This was highlighted through all these above-mentioned analysis, development, testing, post and pre implementation process.

Since this was a message process there was only a little analysis with in the process. In the Introduction, details about the organization and the Infrastructural Resources such as the Hardware, Software available there along with the address is given. Then the abstract about the project and the necessity of the system have been touched upon. It gives a smooth opening on a window which later pairs with brilliant light of several processes involved in simulation of token ring in process. In the 2nd chapter title System study and problem formulation a broad look of the existing system, the limitations of the existing system, about the proposed system and its advantages with the feasibility study has been illustrated.

Chapter titled System specification gives into account the necessary hardware and software requirements with a minimum need and the features of the software is described in detail. Chapter 4 titled System design and implementation that follows brings to our knowledge the details of the system, the data flow diagrams with description, the modules involved and its design, the Input/output design along with the code design. The chapter 5 which deals with System Testing and Implementation gives the complete testing that have been adopted and the system implementation and the post implementation review. Finally the chapter 6 that follows brings to our knowledge the details of the security methods and the measures that are involved in this project.

The project may be complete and satisfactory with all the necessary enhancements. The new ideas can be taken in to account and the code is capable of being altered so as to enhance the project. Thus this project brings out the complete analysis of the token ring and the complete design, development, testing and implementation of the project. I hope that the analysis will be useful to others those who read them in future.

11. BIBLIOGRAPHY

BOOKS

Java Server Pages

-James Goodwill, BPB Publications, I Edition.

Software Engineering

- Rogers Pressman, Mc Graw Hill Publications

Java2 complete reference

-Herbert Schildt

Oracle SQL * Plus

Jonathan Gennick (OReilly)

The Programming Language Of ORACLE

- Ivan Bay Ross, II Edition.

JavaScript

- David Flanagan (OReilly)

ONLINE SUPPORT www.sun.com www.apache.com www.openbravo.com www.google.com www.wikipedia.comAPPENDICES

A. ACTIVITY DIAGRAM

ADMINISTRATOR:

MODERATOR:

DATAFLOW DIAGRAM

LEVEL 0:

LEVEL 1:

LEVEL 2:

C. USE-CASE DIAGRAM:

ER-DIAGRAM:

SCREEN LAYOUT

HOME PAGE-login

Top of Form

Inspection Tool

HOME PAGELogin:

User Id: Password: Help

Bottom of Form

ADMINISTRATOR PAGE

USER-SIGNUP

CREATE USER

CREATE PROJECT

CROSS CHECK TEAM

VIEW CROSS CHECK TEAM

CREATE INSPECTION TEAM

VIEW INSPECTION TEAM

USER DETAILS

PROJECT DETAILS

DOCUMENTS OF THE PROJECT

INSPECTION SCHEDULE

RAISE EXCEPTION

DEFECT LOGGING SHEET

LOG SUGGESTION

LOG VIEW

REMOVE USER

REMOVE PROJECT

JAVA CODE

JAVA BYTE

CODE

Solaris

HP-VX

WIN32

Register

Login

Change

Password

Create

EMP

Remove

EMP

Logout

Fail

Success

Add Project

Remove Project

Register

Login

View

Emp details

Selecting

Team

Creating

Master plan

Logout

Fail

Success

View

Doc, Proj status

Conducting

Meetings

ADMINISTARTOR

INSPECTION TOOL

AUTHOR

MODERATOR

INSPECTOR

ADMINISTRATOR

E PROJECT

CREATE EMP & PROJECT

DOC

EVENT

AUTHOR

MODERATOR

INSPECTOR

CHAT

EMP PROJECT

REMOVE EMP & PROJECT

CHAT

CHAT

CHAT

INSPECTOR

ADMINISTRATOR

SELECT TEAM

CREATE

EMP & PROJECT

INSPECT DOC

DEFECT LOGGING SHEET

DOC

MODERATOR

SCRIBE

MEETING

AUTHOR

Login

Remove project

Add project

Remove

Emp

Created Emp

Logout

Change password

Admin

Moderator

View profile

View proj Status

Selecting inspection team

Creating master plan

View doocs

Conduct meetings

Login

View emp details

Logout

Rel-01

Login

Login

ADMI N I STRATOR

Foreign_key_Index Create_Emp_tab

INSPECT_TEAM_TAB

EMPID

Proj_Name

Proj_code

Emp_Name

E-mail

PROJECT_TAB

Proj_ID

Proj_Name

Author_Name

Proj_Doc

CREATE_EMP_TAB

EMPID

Name

E-mail

Specialization

Grade

LOGIN_TAB

ID

Password

view

view

Rel-03

Rel-02

Foreign_key_Index Project_Tab

DEFECT_LOGGING

Proj_Name

Proj_doc

Defect_Severity

Defect_Class

Defect_root

Injected_phase

Defect_status

Desc

View

View

Rel-01

_1383755661.unknown

_1383755662.unknown

_1383755660.unknown

_1383755659.unknown