online mat

ONLINE MATRIMONIAL SYSTEM (SHADI.COM)

1

Mini project report

On

ONLINE MATRIMONIAL SYSTEM

In the partial fu lfillm ent of

4 th sem ester of

MCA

Submitted By: BIKASH CHANDRA KUMBHAKAR

Regno.95580007

DEPARTMENT OF COMPUTER APPLICATIONS COCHIN UNIVERSITY OF SCIENCE AND TECHNOLOGY

KOCHI-22


2

Acknowledgements The satisfaction and euphoria that accompany the successful completion of any task would be incomplete without mentioning the names of people who made it possible, whose constant guidance and encouragement crowns all efforts with our success. I extend my gratitude to Dr. K.V. Pramod, Head- Department of Computer Applications, Cochin University of Science and Technology, Kochi, Kerala for providing me with excellent infrastructure and awesome environment that laid potentially strong foundation for my professional life. I would like to express my profound thanks to Dr.B.Kannan, Dr. A. SreeKumar, and Mrs. S. Malathi and for their help and guidance throughout my project future. Finally. I also wish to thank all guest faculties and non-teaching staffs for supporting me during my whole project work.

BIKASH CHANDRA KUMBHAKAR

SEM-IV, MCA

DCA CUSAT

Regd.9558007


3

Cochin University of Science and Technology

CERTIFICATE

This is to certify that the project titled “ONLINE MATRIMONIAL SYSTEM”

submitted to Cochin University of Science and Technology in partial

fulfillment of the requirements for the award of the degree of Master of

Computer Applications is the bonafide record of the project work

done by Mr. Bikash Chandra Kumbhakar in the year of 2010 under our

supervision and guidance during.

Examiner

DCA, CUSAT Date:

Cochin-22


4

DECLARATION

I hereby declare the project entitled “ONLINE MATRIMONIAL

SYSTEM” has been carried out by me and the contents have been submitted

to Department of Computer Applications, for the partial fulfillment of the

degree of Master of Computer Applications under Cochin University of

Science and Technology, Cochin-22.

Signature:

Place:

Date:


5

Synopsis

Title of project : ONLINE MATRIMONIAL SYSTEM

Name of Students : BIKASH CHANDRA KUMBHAKAR

Venue of the Project : DCA, CUSAT

Duration : 3 months

Platform : Windows XP

Application Software

Front End : JSP, HTML, JAVA SCRIPT

Back End : MYSQL, Apache Tomcat


6

Contents

1. Introduction

2. System Study

Existing System……………………………………………

Drawbacks in the Existing System.........................

3. System Analysis

Proposed System………………………………………….

Need for the Proposed System…………………………

Feasibility Study…………………………………………..

a. Technical Feasibility…………………………

b. Financial Feasibility…………………………

c. Operational Feasibility………………………

Overview of D.B.M.S……………………………………..

An Introduction to MYSQL……………………………….

An Introduction to JSP…………………………………..

An Introduction to JavaScript…………………………….

An introduction to Apache Tomcat……………………..

4. Requirement Analysis

Requirement Engineering…………………………………

Requirement Definition……………………………………

Requirement Specification………………………………..

Functional Requirement…………………………………..

List of Input…………………………………………………

List of Output……………………………………………….

Performance Requirement

a. Security………………………………………


7

b. Availability……………………………………

c. Capacity………………………………………

d. Response Time………………………………

e. User Characteristics……………………………

f. Interface Requirement..............................

5. Database Design

Database Tables...............................................

Data Flow Diagrams..........................................

6. Output Screen

Output of Pages…………………………………………

7. SQA Plan

Purpose …………………………………………………

Scope ……………………………………………………

Reference ………………………………………………

Documentation ………………………………………..

Standards, Practices, Conventions and Metrics ..

Reviews and audits …………………………………..

Problem reporting ……………………………………

Tools, Techniques and Methodologies ……………

Media control ………………………………………….

Training …………………………………………………

Risk Management ……………………………………

8. Testing

9. Conclusion

Scope for further development……………………

10. Bibliography


8

Introduction

The Basic problem in searching a good life partner in this world is the times

spending and the travelling cost effective. This project (Online Matrimonial System)

is a useful website for a person of any religion who wishes to find a suitable life

partner for himself\herself.

This website is very useful as it provides a fast searching of numerous

suitable profiles. He/she can create his/her profile and can communicate with the

existing members of site . Also since it will be available through internet it will be

possible for the user to see their profile anywhere.

The System Administrator can also update the data through internet. The

Administrator can delete those members account who wants to delete there

account. The Administrator can send perfect match to the member who submit the

request for life partner.


9

System Study

The ONLINE MATRIMONIAL SYSTEM are growing as the internet

emerges as the best Technology which provides a fast and efficient access

to any information about anything. Difficulty in Keeping the details of

each user and their partners, delay in sending messages to them and

spending so much money for finding a good life partner causes the

appearance of this website.

The Project concentrates on to surmount these difficulties.

Existing System

The existing system was an automated system but It was

found to be inefficient in meeting the growing demands of population

and different online matrimonial take a lot of time and money for

searching a suitable match. But still they are not able to provide a good

life partner of any country, religion, caste and profession.

Drawbacks in the existing system

The existing system is not user-friendly system.

Disadvantage of the existing system is that for creating a profile it takes a

lot of time and money. For searching a good life partner according to

your search criteria some time takes a lot of time and sometimes there

are no profile according to your.

Lack of security of the existing system was found to be

another drawback. The existing system does not implement restriction for

users to access the data.


10

1. INTRODUCTION:

1.1 PURPOSE:

The purpose of this document is to describe the design of the

project named ONLINE MATRIMONIAL SYSTEM .The purpose of

design documentation is to express the vision for the project, describe

the contents, and present a plan for implementation.

A design document is a bible from which the producer preaches the

goal, through which the designers champion their ideas, and from

which the artists and programmers get their instructions and express

their expertise.

1.2 SCOPE: The scope of this document is to design all the functionality which

is provided by the project.

1.3 INTENDED AUDIENCE: This document is useful for the customer to understand all the

requirements of the system which he/she want to be automated. This

document will help customer to see whether all the requirements he/she

wants is designed or not?

This document is also useful for the developer of the project to

understand the system will work?

1.4 IDENTIFY THE SYSTEM/ PRODUCT USING ANY APPLICABLE NAMES AND/OR VERSION NUMBERS

Name of this website is ONLINE MATRIMONIAL SYSTEM.

This website is providing matrimonial services which are provided

by the other websites but it includes some extra features which are not

provided by most of the matrimonial websites.


11

1.5 REFERENCES FOR ANY OTHER PERTINENT DOCUMENTS

1.5.1 RELATED AND/OR COMPANION DOCUMENTS

The documents required for this document include the

requirement document of the project.

1.5.2 PREREQUISITE DOCUMENTS

This document requires all the documents needed for a

matrimonial service.

1.5.3 DOCUMENTS WHICH PROVIDE BACKGROUND AND/OR CONTEXT FOR THIS DOCUMENT

Design document of this project requires all the documents

related to the matrimonial and law about the matrimonial. Documents

required for the creation of forms and guideline for design.

1.5.4 DOCUMENTS THAT RESULT FROM THIS DOCUMENT

The result of design documentation will give a platform for the

creation of the software. It gives a plan for implementation.

1.6 IMPORTANT TERMS, ACRONYMS,OR ABBREVIATION

Admin Administrator

HTML Hyper text markup language

HDD Hard disk

HTTP Hypertext transfer protocol

JSP Java Server Page

RAM Random access memory

1.7 OVERVIEW

This document deals with the design of the website. The design document provides the design of the forms and tables.


12

2 SYSTEM OVERVIEW:

2.1 ACTUAL SYSTEM: In the actual system when a person want to search suitable life

partner he may have to visit matrimonial agencies .The agencies may

provide them several photos of girls/boys and biodata who are

searching for life partner. It takes so much time and money but still not

able to get good partner.

2.1 PROPOSED SYSTEM: This project is designed so that a person can free register as a

member for some days. After paying the money he/she will become a

permanent member of this website. It also provides fast searching for a

life partner and sending his/her contact or communicates with the

existing members.

As both the members will agree they meet together for the marriage.

When the marriage will over the bride and groom can share their

successful marriage story on this website. A person can search for a

bride or a groom of any religion of any caste and of any country. 2.2 MODULES: There are two modules in this project.

2.3 ADMINISTRATOR MODULE: If any person wants to register for a membership the

administrator can allow for free registration and save all the

information as given by the user in a separate space and keep it secure.

He may also allow to user to send request for life partner match. He

updates the database as the profile is updated by the user.

The Administrator every time send a perfect match to requested users.


13

2.4 USER MODULE:

The user is usually a person who wishes to register as a member

he/she may login with his/her id and can search for a life partner.

He/she may also be able to read stories related to the marriage of

married person who found their partner through this website. He/She

create his/her own profile. She/he may use all the services provided on

this website.

Architectural Diagram:

User Registration Admin.

Takes

Informed

Database

Manipulate Store

Interact


14

3. DESIGN CONSIDERATIONS

This section describes many of the issues which need to be

addressed or resolved before attempting to devise a complete design

solution

3.1 ASSUMPTIONS AND DEPENDENCIES

This section describes any assumptions or dependencies

regarding the software and its use. These may concern such issues as:

3.1.1 RELATED SOFTWARE OR HARDWARE

Overview of DBMS:--

Database system provides the centralized control of its

operational data that is one of its most valuable assets. In any

enterprise with a database system there will be someone identifiable

person who has this central responsibility for the operational data

and is known as DATABASE ADMINISTRATOR.

The advantages of having centralized control of the data

are—

1. Redundancy can be eliminated:

In non-database system each application has its own private file. This

can often lead to considerable redundancy in stored data, with

resultant waste of storage space. These private files can be

eliminated, if the DBA has the necessary overall control on the

database system.


15

2. Inconsistency can be avoided:

Suppose that a student from the department SMS has taken a paper

from DCA then these two values will be in two tables in the database

of both the department. Then there will be some occasion on which

the two entries will not agree. At this stage the database is said to be

inconsistence.

The database system could guarantee that the system is not

inconsistence by ensuring that any change made to either of any two

entries is automatically made to the other. This process is known as

propagation updates.

3. The data can be shared:

The data can be shared among different application if we are using

a database system.

Types of data model

A data model is a collection of conceptual tools for describing

data; data relationships, data semantics, and data constraints, there

are number of different data models that have been proposed. These

are partitioned into different groups.

1. Object –based logical models:

They are used in describing data at the conceptual and view

levels. They are characterized by the fact that they provide fairly

flexible structuring capabilities and allow one to specify data

constraints explicitly.

2. Relationship models:

The relationship approach is based on mathematical theory of

relations. According to this approach, all database tables, files can be


16

represented as rectangular tables, where columns represent the

attributes and rows corresponding to tuples.

3. Relational models:

In relation system, data reliability is provided by the

ability to construct new relations from existing relation by the use of

relational operators. The existence, construction and maintenance of

access paths are hidden from the use and their implementation is one

of the hardest design problems in relational system.

Advantage of Relational Models over other Models:

• Simplicity and ease of use:

• Data Independence:

• Symmetry:

• Good Theoretical Foundation:

An Introduction to the MYSQL

MYSQL is a high performance, relational database server based on

MYSQL. It is built on CLIENT/SERVER architecture, which means a front-

end or client component, and a back end, or server component. MYSQL

server forms the back-end component in this architecture and is responsible

for providing all the standard DBMS functions. The client component, for

which there are many different possibilities, is responsible for providing all

of the user interface and application-processing function. The language used

to communicate between clients and MySQL.


17

A database system must provide the following features:

• A variety of user interfaces

• Physical data independence

• Logical data independence

• Query optimization

• Data integrity

• Concurrency control

• Backup and recovery

• Security and authorization

SQL Server 2000 is a Relational Database Management System.

An Introduction to JSP JSP technology is the interface between HTML and JAVA .The JSP

tech. provides a seem less connection with JAVA and presents easy to

use.java like programming construct that can be scripting with HTML

files. This technology provides dynamic way to construct web pages.

A JSP page contains standard markup language elements,

such as HTML tags, just like a regular web page. A JSP page also

contains special JSP elements that allow the server to insert dynamic

content in the web page.

ADVANTAGES OF JSP � JSP supports both scripting and element-based dynamic content.

� Allows developing custom tag libraries.

� JSP pages are precompiled for efficient server processing.

� JSP pages can be used in combination with servlets that handle the business logic.


18

� High Security.

� Can run on any J2EE compatible web Server.

� It can run on any OS that have J2EE compatible web server.

� JSP separates the dynamic and static parts.

� High Quality tool supports.

� JSP supports N tier Application.

� Write Once, Run Everywhere.

� JSP is vender Neutral.

OVERVIEW OF JAVA SCRIPT

Java script is a general purpose, prototype based, object oriented scripting

language developed jointly by sun and Netscape and is meant for the WWW. Java

script borrows most of its syntax from java but also inherits from awk and perl,

with some indirect influence from self in its object prototype system.

Java Script is almost as easy to learn as HTML and it can be included directly in

HTML documents. Java Script was developed independently of java. Java script is

a high level scripting language that does not depend on or expose particular

machine representations or operating system services.

FEATURES: • Java script is embedded into HTML documents and is executed with in

them.

• Java script is browser dependent.

• JavaScript is an interpreted language that can be interpreted by the browser

at run time.

• Java script is loosely typed language


19

• Java script is an object-based language.

• Java script is an Event-Driven language and supports event handlers to

specify the functionality of a button.

The Struts framework provides the flexibility to develop the much less coupled

applications. It generalizes and strictly implements MVC-model View Controller

Architecture. That is the basic need of our architecture.

ADVANCED FEATURE:::

New development environment provides a new concept for validation is by

using Gen validator 31 .Having some in built functionality which help you in quick

validation. In the function of genValidator we make an object of any form which is

the name of form. Then use File GenValidator having a lot of predefined function

for different type of constraints.

About Apache Tomcat:

Apache Tomcat is a servlet container developed by the Apache Software Foundation (ASF). Tomcat implements the Java Servlet and the Java Server Pages (JSP) specifications from Sun Microsystems, and provides a "pure Java" HTTP web Server environment for Java code to run. Tomcat should not be confused with the Apache web server, which is a C Implementation of an HTTP web server; these two web servers are not bundled together. Apache Tomcat includes tools for configuration and management, but can also be configured by editing XML configuration files.

Components Tomcat version 4.x was released with Jasper (a redesigned JSP engine), Catalina (a redesigned servlet container) and Coyote (an HTTP connector).


20

Catalina Catalina is Tomcat's servlet container. Catalina implements Sun Microsystems' Specifications for servlet and Java Server Pages (JSP). The architect for Catalina Was Craig McClanahan.

HARDWARE:

Processor - INTEL Pentium and followers(X86)

Clock Speed - 1000MHz

Memory - 512 MB

HDD - 80 GB

3.1.2 OPERATING SYSTEMS

Windows xp

3.1.3 END USER CHARACTERISTICS

The End user in this system has to register in the first step.

Then he can login to the web page. There he/she can search a partner

and send messages to his/her. He/she has to first enter the details for

his/her life partner to whom he/she is searching. Then a suitable

match list will be displayed and then he/she has to send a message to

his/her suitable match.

The user only needs to know English language and how to

browse a website. Thereby he\she can simply do the whole things.

3.1.4 POSSIBLE AND/OR PROBABLE CHANGES IN FUNCTIONALITY


21

3.2 GENERAL CONSTRAINTS

3.2.1 HARDWARE OR SOFTWARE ENVIRONMENT

The essential things that are needed for this project are JSP,

JAVA in which we are DESIGNING THE WEBSITE. Then we need

MYSQL for the DATABSE

3.2.2 END-USER ENVIRONMENT

In the case of contacting with the member the administrator has

to ensure that the user is an active member and he/she has submitted

the fee require for that. For that Administrator has to ask to the user

to pay small money in advance by sending a cheque number or DD

number .The use of debit card will become a hard problem because

he has to check a large number of algorithms.

3.2.3 AVAILABILITY OR VOLATILITY OF RESOURCES

The resources required for the project must be available.

3.2.4 STANDARDS COMPLIANCE

The project is designed on some standard basis.

3.2.5 INTEROPERABILITY REQUIREMENTS

The project is designed so that all the forms can operate with

each other. 3.2.6 INTERFACE/PROTOCOL REQUIREMENTS

HTTP

FTP

SMTP

3.2.7 DATA REPOSITORY AND DISTRIBUTION REQUIREMENTS


22

MySQL is the database used for storing the details of the user and the marriage story.

3.2.8 SECURITY REQUIREMENTS

Administrator is responsible for all the accesses to the existing

contacts. The information given by the users are secure. 3.2.9 MEMORY AND OTHER CAPACITY LIMITATIONS

Memory - 1 GB

HDD - 80 GB

3.2.10 PERFORMANCE REQUIREMENTS The system is designed so that it will achieve its performance requirements.

3.2.11 VERIFICATION AND VALIDATION REQUIREMENTS

The project is designed so that it satisfy all the verification and

validation requirements.

3.2.12 OTHER MEANS OF ADDRESSING QUALITY GOALS

The system is designed so that it achieves its quality goals.

3.2.13 OTHER REQUIREMENTS DESCRIBED IN THE REQUIREMENTS SPECIFICATION

The project is designed so that it will fulfill all the other requirements

described in the SRS


23

1. DESIGN DETAILS:

Normalization

Normalization provides for table optimization through the investigation of

entity relationships. Main purpose of normalization is to avoid Data redundancy

and some unforeseen scalability factors. Normalization is done to remove

Insertion, Updating and Modification anomalies and redundancy of data. A certain

level of normalization of tables in database gives a particular normal form based of

particulars steps followed. Database can be normalized up to any defined normal

forms according as the need of application and its effectiveness.

Database of Sales Tracking system is normalized up to Third Normal Form.

Further normalization of database was not considered taking into account the need

of application and ease of working with database. The database is in First Normal

Form as all the fields of all tables are atomic. There is no multi valued field in any

table.

� The database is in Second Normal Form as it satisfies the constraint of full

functional dependency. All the fields of all tables are fully functional

dependent on the primary key.

� The database is in Third Normal Form as all its tables satisfy the

� Constraint that there should be no transitive dependency. No field has

� Transitive dependency on the key field. Thus database also satisfies the

� Constraints of third normal form.


24

Database Tables: Table :login

NAME DATA TYPE SIZE CONSTRAINT DESCRIPTION

UserID Varchar 50 Primary key Refernces Foreign key

Id of the User

Password Varchar 50 Password of the User

Type Varchar 50 Type of user

Table:loagin1



Id of the User

UserName Varchar 50 UserName

Marital Status

Varchar 10 Unmarried, widow/widower,divorced,separated

Height Varchar 3 Not more than 46 Height

Year Varchar 7 Year

Month Varchar 18 Month

Day Varchar 18 Day

Mothertongue

Varchar 20

Country

Varchar 50 India

Table:login2



Id of the User

Qualification

Varchar 50 MCA, MBA…….

Occupation Varchar 50 Government, Private…

Annual Income

Varchar 10 Income

Contact

Varchar 10 Mobile No.


25

Table: login3

DATA TYPE SIZE CONSTRAINT DESCRIPTION

UserID Varchar 50 Primary key+Foreign key references user login table

Unique UserId

UserName Varchar 50 UserName

Age Varchar 10

Sex Varchar 8 Male/female

Caste Varchar 18

City

Varchar 50 Bombay, Channai, Delhi..

State

Varchar 50 Bihar,Jharkhand,Kerela

Religion Varchar 50 Hindu,Muslim,sikh,christian

Table: userimage



Id of the User

bImage Blob 50 Image of user


26

2. Data Flow Diagrams:

� DFD means data flow diagram. Before developing software,

programmer should have a clear picture of DFD.

� A DFD shows the movement of data through the different

transformations or processes in the system.

� A DFD or data flow diagram is a graphical representation that

depicts the information flow and the transformation that are

applied to data it moves from input to output.

� Data Flow Diagram (DFD) is used to define the flow of the

system and its resources such as information.

� Data Flow Diagrams are a way of expressing system

requirements in a graphical manner. DFS represents one of

the most ingenious tools used for structured analysis.

� A DFD is also known as a bubble chart. It has the purpose of

Clarifying system requirements and identifying major

transformations that will become programs in system design.

� Named circles show the processes and data named arrows

represent flows and a rectangle represents a source or sink.

The Data Flow Diagram basically serves two purposes.

1. Provide a graphical tool, which can be used effectively by the

analyst to explain the understanding of the system to the user.

2. They can be effectively converted into structured charts, which

effectively help in the designing of the system?


27

There are only five symbols that are used in the drawing of data flow

diagrams

� EXTERNAL ENTITY

An external entity is a source or destination of a data flow. Only those

entities which originate or receive data are represented on a data flow

diagram. The symbol used is an oval containing a meaningful and

unique identifier

� PROCESS

A process shows a transformation or manipulation of data flows within the system. The symbol used is a rectangular box:

� DATAFLOW

A data flow shows the flow of information from its source to its

destination. A data flow is represented by a line, with arrowheads

showing the direction of flow. Information always flows to or from a

process and may be written, verbal or electronic. Each data flow may be

referenced by the processes or data stores at its head and tail, or by a

description of its contents.

� DATA STORE

A data store is a holding place for information within the system: It is represented by an open ended narrow rectangle.

Data stores may be long-term files such as sales ledgers, or may be short-term accumulations: for example batches of documents that are waiting to be processed. Each data store should be given a reference

followed by an arbitrary number.


28

� RESOURCES FLOW

A resource flow shows the flow of any physical material from its source

to its destination. For this reason they are sometimes referred to as

physical flows.

The physical material in question should be given a meaningful name.

Resource flows are usually restricted to early, high-level diagrams and

are used when a description of the physical flow of materials is

considered to be important to help the analysis.

Example: Matrimonial System represented by DFDS

Level 0:

Context Diagram

User Registration

Admin.

Takes

Informed

Database

Manipulate Store

Interact


29

Level 1: Status informed

Admin. Login Admin. Window

Admin. Manipulations

Login Valid

Invalid

Store

Do

Login

Registration User Store Id and pwd. database

Id and pwd. database


30

Level 1.1:

REGISTRATION

USER

USER

Database

LOGIN

Database Partner partener

Context Diagram


31

Send massage

Store

From database

From

View

Admin

Login Database

Level 2.1:-

2nd Level Diagram

View Registered

user

Administrator ViewInterested user acc.del

Database

Level 2.2:-

a b c


32

Output Screens

Front Page:


33

Administrator page:


34

Registration page:


35

Partner page:

:


36

User Request for Account Deletion Page:


37

Software Quality Assurance

Purpose

The purpose of this Software Quality Assurance (SQA) Plan is to establish

the goals, processes, and responsibilities required to implement effective quality

assurance functions for the Marriage registration The Marriage Registration

Software Quality Assurance Plan provides the framework necessary to ensure a

consistent approach to software quality assurance throughout the project life cycle.

It defines the approach that will be used by the SAM and Software Quality (SQ)

personnel to monitor and assess software development processes and products to

provide objective insight into the maturity and quality of the software.

Scope

The Scope of the project is that once can purchase the goods online. It means there

is a website for the shop, user can visit the site and see all the items of the shop

with its price. If they want to purchase then they select the item after selecting the

item they can paid either by Credit card or by Bank draft. The customer fills his full

address .On the site to receive his goods. When will the shop owner get the Bank

draft Or particular amount then he will sent their ordered item to their address.

After purchasing and before payment if customer wants then they can cancel the

Items or add more quantity. This site is used such that any shop can register. The

shop owner will login on the site and they can See all the available items and all the

sold items.


38

Reference Documents

The following documents were used or referenced in the development of this plan:

• The Software quality Assurance Plan(SQAP)

• The Software Requirement Specification

• The Software Design Document(SDD)

• The Software Test Plan

• The Final Project Report

Documentation

The following documentation will be generated and updated throughout the

duration of software life cycles:

Phase I:

1.) Vision Document - provides detailed description of the entire project, goals of

the software, constraints and requirements for the software to satisfy.

2.) Project Plan - illustrates the major milestones and provides a rough timeline for

the project and estimation on the size and effort of the project.

3.) Software Quality Assurance Plan – provides plan for software quality assurance

Phase II:

1.) Formal Requirement Specification – UML/OCL methodology will be used to

produce this document.

2.) Test Plan - provides description of test cases during testing

3.) Architecture Design – Object Model and Use Cases will be produced.

4.) Formal Technical Inspection - two MSE students will participate in formal

technical inspection, and developer will also provide an inspection checklist.


39

Phase III:

1.) User Manual - instructions on how to use software

2.) Final source code - actual implemented documented source code

3.) Assessment Evaluation - assessment of reliability and performance of software

4.) Project Evaluation - review of the entire project

Standards, Practices, Conventions, and Metrics

This section of the software quality assurance plan should contain at a

minimum, the following:-

1. Documentation standards

2. Logic structure standards

3. Coding standards

Reviews and audits

This section of the software quality assurance plan will state which technical

and managerial reviews will be undertaken and how they will be carried out.

Project can separately keep a schedule of provisional dates for conducting these

reviews. The ANSI Standard suggests that the following would be a minimum set of

reviews : -

a. Software Requirements Specification Review

b. Preliminary Design Review

c. Critical Design Review

d. Software Verification Review

e. Functional Audit

f. Physical Audit

g. In-Process Audits

h. Management Reviews


40

Problem reporting

If any problems are encountered throughout the duration of the project,

the software developer can report and discuss the problems with the major

professor. If any conflict or problems are discovered by one of the committee

members during a presentation, the developer will then correct the errors.

Tools, Techniques and Methodologies

Tools - SQA software tools include, but are not limited to, operating

system utilities, debugging aids, documentation aids, checklists, structuring

preprocessors, file comparators, structure analyzers, code analyzers, standards

auditors, simulators, execution analyzers, performance monitors, statistical

analysis packages, software development folder/files, software traceability

matrices, test drivers, test case generators, static or dynamic test tools, and

information engineering CASE tools.

Techniques - techniques include review of the use of standards, software

inspections, requirements tracing, requirements and design verification, reliability

measurements and assessments, and rigorous or formal logic analysis.

Methodologies - methodologies are an integrated set of the above tools and

techniques. The methodologies should be well documented for accomplishing the

task or activity and provide a description of the process to be used. Where

applicable, SQA will use SEPO organizational processes and tailor the processes

specific to the project.

CODE CONTROL

Code control includes the items listed below:

Identifying, labeling, and cataloging the software to be controlled

• Identifying the physical location of the software under control


41

• Identifying the location, maintenance, and use of backup copies

• Distributing copies of the code

• Identifying the documentation that is affected by a change

• Establishing a new version

• Regulating user access to the code.

MEDIA CONTROL

The purpose of this section is to state the methods and facilities to be used,

and whose proper use is to be verified by SQA, to identify the media for each

computer product and the documentation required to store the media, including

the copy and restore process, and to protect the computer program physical media

from unauthorized access or inadvertent damage or degradation during all phases

of the software life cycle. This may be provided as a part of reference (f). If so, an

appropriate reference should be made.

Media control includes the items listed below:

a. Regularly scheduled backup of the media.

b. Labeled and inventoried media filed in a storage area in accordance with

security requirements and in a controlled environment that prevents

degradation or damage to the media.

c. Adequate protection from unauthorized access.

The software media control methods and facilities are described in reference (f).

SQA will conduct ongoing evaluations of the software media control process to

verify that the process of controlling the software media is effective and in

compliance.


42

Training

SQ personnel shall have fundamental knowledge in the following areas/disciplines

through prior experience, training, or certification in methodologies, processes,

and standards:

• Software Quality Assurance:

• Audits and Reviews

• Risk Management

• Configuration Management

• Software Safety

• Contracts/Contractor Surveillance

• CMMI

• ISO 9001

• Project-specific Training

It is the responsibility of the SQ personnel to acquire the necessary skills or

knowledge in each of the above disciplines. An SQ Training log has been prepared

that specifies the type of training and/or on-the-job experience that has been

completed, along with the source of the training, and the date of completion.

RISK MANAGEMENT

Specify the methods and procedures employed to identify, assess, monitor, and

control areas of risk arising during the portion of the software life cycle covered by

the SQA Plan.

SQA will review and evaluate the technical risk analysis and any risk reduction

plan. SQA reporting will confirm that the identified risks are managed in

accordance with the provisions of the project’s risk management plans, and that

associated action items are reported, managed, and followed through to closure.


43

Testing For testing our software we test each and every path that user can go at any point

in the lifetime of the system to ensure that the system is fool proof.

VVVVarious Tests:arious Tests:arious Tests:arious Tests:

1. Unit Testing

In unit testing we had tested every single part that is the

forms of the software. We do this simultaneously while the project is being

built. For each part various inputs are given based on the fields of those

particular forms and match with the possible outputs and its acceptable

ranges are retrieved. Then the various sets of input values are devised with

various combinations of inputs being out of range. These bring out the

behavior of software in case of inputs being out of range.

2. Module Testing

Software is written in JSP , so it is a collection of pages.

So we tested each and every page carefully with various sets of input values

with various combinations of inputs being out of range. And we found all the

components in the module are working perfectly. These bring out the

behavior of software in case of inputs being out of range.

3. System Testing

This phase of testing is done by evaluating the software

performance by putting into test more than one forms hence the system.

Then the software’s performance is evaluated and checked. Various sets of

input values are devised with various combinations of inputs being out of

range.

These bring out the behavior of software in case of inputs being out of range.


44

Conclusion It has helped us in gaining valuable information on the web page

design principle, handling the user interface in powerful way to

access the various pages across the application.

More than anything this project has given us great satisfaction

in having designed an application, which processes information from

departments to the students and vice-versa, As well to the

administration. And in one place, which saves precious time and

transfers the user’s needs into a software solution.

Scope for further Development:

There is a scope for further development in our project in

terms of functionality for student in which they can choose their

elective paper through internet and also from other department’s

paper if not available in their department.

Bibliography


45

1. Software Engineering (6-th edition) Ian Summerville

2. DATABASE SYSTEM C.J.DATE

3. Java Server Pages (Nick Todd) Developer’s Handbook