Page no

introduction 2

Agile methodology 4

uml diagram 6

functional point technique 10

Unit, integration,system testing 13

output 16

PRABAVATHI T(20MA32)
M.TECH IT
 MATRIMONIAL SITE

In this fast era all are familiar with matrimonial website concept. It is very hard to
physically find life partner as per our choice or like even it is impossible now. For getting best
life partner as per our need we have to contact marriage broker to find life partner. A
matrimonial site helps to both groom and bride to find their life partner as per their criteria and
choice without contact broker.

At time of registration we need to fill up our all detail along with life partner detail, so the
matrimonial site can automatically filers and matches find as per your life partner detail and give
you best matches result. You can also use search facility which helps groom and bride to get best
partner to make matrimonial easier.

After becoming a member of this site you can get alert for best match for your profile and also
can send/receive messages, get contact detail and make online chat with other members. We also
provide advance search facility for our members.

Admin Module

Admin is a owner of website who are responsible to run whole website. Admin is a person who
can activate and deactivate members account. Admin can watch all activities done by members
and take action against mischief activities of members.

Admin Activities

• Login

• Activate Member Account/Deactivate Member Account

PRABAVATHI T(20MA32)
M.TECH IT
Member Module

Members are register users of our website. For becoming a member of site user need to fill up
registration forms with all detail. Member has to also fill up partner detail so we can give best
result as their partner detail. Members have to fill up life partner detail at the registration time so
based on detail we can give best match partner.

After login to site members can get advanced search facility to easily find life partner. They also
check profile of other member and send messages and using online chat facility.

⚫ Add profile

⚫ Edit profile

⚫ Delete profile

PRABAVATHI T(20MA32)
M.TECH IT
 1. AGILE METHODOLOGY FOR MATRIMONIAL SITE:

AGILE MODEL:
It is a software development model.When compare to waterfall model the software
quality is high.

Product:Online matrimony site

Features:This prescribed system will help to register in matrimony site and then they have to
pay and find the partner and also chat with them.
Duration:7 months

An Agile team works in iterations to deliver user stories where each iteration is of 10 to 15 days.
Each user story is planned based on its backlog prioritization and size. The team uses its capacity
− how many hours are available with team to work on tasks − to decide how much scope they
have to plan.

Scrum Master

A Scrum Master is a team leader and facilitator who helps the team members to follow agile
practices so that they can meet their commitments. The responsibilities of a scrum master are as
follows −

⚫ To enable close co-operation between all roles and functions.

⚫ To remove any blocks.

⚫ To shield the team from any disturbances.

⚫ To work with the organization to track the progress and processes of the company.

⚫ To ensure that Agile Inspect & Adapt processes are leveraged properly which includes

• Daily stand-ups,

• Planned meetings,

• Demo,
PRABAVATHI T(20MA32)
M.TECH IT
 • Review,

• Retrospective Meetings, and

• To facilitate team meetings and decision-making process.

Product Owner

A Product Owner is the one who drives the product from business perspective. The
responsibilities or a Product Owner are as follows −

• To define the requirements and prioritize their values.

• To determine the release date and contents.

• To take an active role in iteration planning and release planning meetings.

• To ensure that team is working on the most valued requirement.

• To represent the voice of the customer.

• To accept the user stories that meet the definition of done and defined acceptance criteria.

Iteration 1:Register

Iteration 2:Login

Iteration 3:create profile

Iteration 4:personal details

Iteration 5:payment

Iteration 6partner alert

Iteration 7:chat

Iteration 8:feedback /comments

PRABAVATHI T(20MA32)
M.TECH IT
 2.UML DIAGRAMS

CLASS DIAGRAM:

Class diagram is a static diagram and it is used to model the static view of a system. The
static view describes the vocabulary of the system.Class diagram is also considered as the
foundation for component and deployment diagrams. Class diagrams are not only used to
visualize the static view of the system but they are also used to construct the executable code for
forward and reverse engineering of any systemI.n a class diagram, it is necessary that there
exists a relationship between the classes. The similarity of various relationships often makes it
difficult to understand it. Below are the relationships which exist in a class diagram.

PRABAVATHI T(20MA32)
M.TECH IT
Association:

Between two other classes in an association relationship, an association class forms a part
of it. Additional information about the relationship could be obtained by attaching the association
relationship with the association class. Various operations, attributes, etc., are present in the
association class. Below diagram shows an association of bank and account

Association:

This is a one-directional relationship in a class diagram which ensures the flow of control from
one to another classifier. The navigability is specified by one of the association ends. The
relationship between two classifiers could be described by naming any association. The direction
of navigation is indicated by an arrow.

NEW USER

LOGIN

Aggregation:

In this type of relationship, a more complex object is created by the assembling of different
objects together. The interaction within the different group of objects is defined by Aggregation.
The integrity of the objects are protected, and the response of the assembled objects are decided
by the control object. In aggregation, the classes nurture the ‘has a’ relationship.

NEW USER LOGIN

Composition:

PRABAVATHI T(20MA32)
M.TECH IT
It is a form of an aggregation which represents the whole part relationship. Here, the part
classifier lifetime is dependent on the whole classifier lifetime. In a class, a strong life-cycle is
represented by the composition relationship. There is usually a one direction flow of data here.

USE CASE DIAGRAM:

PRABAVATHI T(20MA32)
M.TECH IT
 Use Case diagrams are essentially needed to analyze high-level requirements of the
system. Now, these requirements can be expressed with the help of different use cases. It can
say that use cases are nothing but the system functionalities written in an organized manner. The
second thing which is relevant to use cases are the actors. Actors can be defined as something
that interacts with the system. Actors can be a human user, some internal applications, or may
be some external applications.

Actors:
Actors are the users of a system. When one system is the actor of another system, label
the actor system with the actor stereotype.
Use Case:
Draw use cases using ovals. Label the ovals with verbs that represent the system's
functions.

System:
Draw your system's boundaries using a rectangle that contains use cases. Place actors
outside the system's boundaries.

Relationships:
Illustrate relationships between an actor and a use case with a simple line. For
relationships among use cases, use arrows labeled either "uses" or "extends." A "uses"
relationship indicates that one use case is needed by another in order to perform a task.

PRABAVATHI T(20MA32)
M.TECH IT
 3.FUNCTION POINT ANALYSIS

The basic and primary purpose of the functional point analysis is to measure and provide the
software application functional size to the client, customer, and the stakeholder on their request.
Further, it is used to measure the software project development along with its maintenance,
consistently throughout the project irrespective of the tools and the technologies.

Measurements Parameters Examples

1.Number of External Inputs(EI) Input screen and tables

2. Number of External Output (EO) Output screens and reports

3. Number of external inquiries (EQ) Prompts and interrupts.

4. Number of internal files (ILF) Databases and directories

5. Number of external interfaces (EIF) Shared databases and shared routines.

PRABAVATHI T(20MA32)
M.TECH IT
 name

height

Weight profile
MATRIMONIAL SITE
Caste profile image

Age

Martial status partner

Measurement Parameter Low Average High

1. Number of external inputs (EI) 7 10 15

2. Number of external outputs (EO) 5 7 10

3. Number of external inquiries (EQ) 3 4 6

4. Number of internal files (ILF) 4 5 7

5. Number of external interfaces (EIF) 3 4 6

PRABAVATHI T(20MA32)
M.TECH IT
Lets take EI=50,EO=40,EI=35,ILF=6,ELF=4

Assume all the factors as average

So ILF=7*6=42

ELF=6*6=36

EI=50*6=300\

EO=10*4=400

EI=35*15=525

TOTAL =1301

Function point=count total*0.65+0.01*total (fi)

CAF=(0.65+0.01*TOTAL (FI))

=(0.65+0.01*13010

=13.66

FUNCTIONAL POINT (FP)=13.66

PRABAVATHI T(20MA32)
M.TECH IT
 4.Perform Unit testing, Integration testing and System testing

UNIT TESTING:

⚫ In software engineering, unit testing is a level of software testing in which individual

units/components are tested.
⚫ A unit is a smallest testable part/module of any software application. In procedural
programming, a unit is an individual program, function, procedure. In object-oriented
programming, a unit may be a method.
⚫ Unit testing of the software product is done during the software development stage saves
time and money in the end.
⚫ If unit testing is skipped by the software developers then there is higher chances of defects
during the integration, system, acceptance and also beta testing.
⚫ The goal of unit testing is to isolate each part of source code and verifies that each part
works properly as designed and to check that source code meets the requirements and gives
the expected output.
⚫ The main advantage of unit testing is that it identify the problem earlier in the application
and if any issue occurs then it can be fix before integrate the units.
⚫ In SDLC, STLC, V Model, unit testing is the first level of software testing done before
integration testing.
⚫ Unit testing is a white box testing which is performed by the software developers and in rare
cases, this testing may be done by independent software testers and quality assurance
engineers also do unit testing.

Create test cases execute

baseline Review

PRABAVATHI T(20MA32)
M.TECH IT
 Matrimonial site:

Personal details payment Chat

Create profile

Integration testing:

Upon completion of unit testing, the units or modules are to be integrated which gives raise to
integration testing. The purpose of integration testing is to verify the functional, performance,
and reliability between the modules that are integrated.

Integration Strategies:

⚫ Big-Bang Integration

⚫ Top Down Integration

⚫ Bottom Up Integration

⚫ Hybrid Integration

Big-Bang Integration Testing –

It is the simplest integration testing approach, where all the modules are combining and
verifying the functionality after the completion of individual module testing. In simple words,
all the modules of the system are simply put together and tested. This approach is practicable
only for very small systems. If once an error is found during the integration testing, it is very
difficult to localize the error as the error may potentially belong to any of the modules being
integrated.

Bottom-Up Integration Testing –

In bottom-up testing, each module at lower levels is tested with higher modules until all
modules are tested. The primary purpose of this integration testing is, each subsystem is to test
the interfaces among various modules making up the subsystem. This integration testing uses
test drivers to drive and pass appropriate data to the lower level modules.

PRABAVATHI T(20MA32)
M.TECH IT
Top-Down Integration Testing –
Top-down integration testing technique used in order to simulate the behaviour of the lower-
level modules that are not yet integrated.In this integration testing, testing takes place from top
to bottom. First high-level modules are tested and then low-level modules and finally
integrating the low-level modules to a high level to ensure the system is working as intended.

Mixed Integration Testing –

A mixed integration testing is also called sandwiched integration testing. A mixed integration
testing follows a combination of top down and bottom-up testing approaches. In top-down
approach, testing can start only after the top-level module have been coded and unit tested. In
bottom-up approach, testing can start only after the bottom level modules are ready.

System testing:

SYSTEM TESTING is a level of testing that validates the complete and fully integrated
software product. The purpose of a system test is to evaluate the end-to-end system
specifications. Usually, the software is only one element of a larger computer-based system.
Ultimately, the software is interfaced with other software/hardware systems. System Testing is
actually a series of different tests whose sole purpose is to exercise the full computer-based
system.

Types of system testing:

functionality,inter-operability,performance,scalability,stress,reliability,regression

System under test (SUT) refers to a system that is being validated by the testers. The
terminology is also known as application under test.The System Under Test (SUT) also
corresponds to a software that is matured and has gone through unit and integration testing.

PRABAVATHI T(20MA32)
M.TECH IT
5. Output

PRABAVATHI T(20MA32)
M.TECH IT
REGISTRATION:

PRABAVATHI T(20MA32)
M.TECH IT
Edit:

Edit the weight from 40 to 50

PRABAVATHI T(20MA32)
M.TECH IT
Weight 50 is edited

Delete:

There are three records .now I delete the 3rd record that is profile id 33.

PRABAVATHI T(20MA32)
M.TECH IT
Now its only 2 record.

Database:

PRABAVATHI T(20MA32)
M.TECH IT
Code:

PRABAVATHI T(20MA32)
M.TECH IT
PRABAVATHI T(20MA32)
M.TECH IT
PRABAVATHI T(20MA32)
M.TECH IT
PRABAVATHI T(20MA32)
M.TECH IT
PRABAVATHI T(20MA32)
M.TECH IT