AHMEDABAD INSTITUTE OF TECHNOLOGY

PROJECT NAME: shaadi.com

MEMBERS: Abhishek Patel Jitesh Patel

ROLL NO : 09/CE/126 09/CE/121

CERTIFICATE

Table

of

Contents

Descripition

1.0 Introduction 1.1 1.2 1.3 1.4 1.5 1.6 Purpose Scope Definition, Acronyms, and Abbreviations References Technologies to be used Overview

2.0 Overall Description 2.1 2.2 2.3 2.4 2.5 Product Perspective Software Interface Hardware Interface Product Function User Characteristics

Constraints Architecture Design Use Case Model Description Class diagram Sequence diagrams.. Database design 2.11.1 ER diagram 2.11.2 Schema .. 2.12 Assumptions and Dependencies 3.0 Specific Requirements 3.1 Use Case Reports 3.2 Supplementary Requirements

2.6 2.7 2.8 2.9 2.10 2.11

Introduction In these Project we basically focus on all the world of people who want to find there life partener. Our site made for connect all these from all over the world. In this website we matrimonial section, Education section & also gave all the information about acivities like events, cultural activities, Social activities and all. Here we provide other facilities like News & also upcoming events.

PUROSE

The purpose of this project is providing a platform to people for connecting from
world wide. Still there is no any platform for connect on internet through the website. We are providing these facilities for people and they can find easily information & news related the different religions. At these time people want information for anykind of thing & here people can also find upcoming events.

SCOPE

Our website provides free services to all people. In this website provide
matrimonial section where people can register him/her profile and easily find life partner & also you can see news, events and also connecting to different people to latest information & news.

Methodoloogy

1. Feasibility study

Its

ma in a im is to deter mine whethe r it is phys ica lly a nd t e c h n i c a l l y fe a s i b l e o r no t . I t i n v o l v e s a na l y s i s o f p r o b l e ms a n d c o l l e c t i o n o f a l l relevant information. Collected data are analyzed to arrive at following. - an abstract problem definition-format of different strategies for solving problem. - evaluation of different solution strategies. Thus during this phase very high level decisions are made.

2. Requirement Analysis
Its aim is to understand exact requirement of customer and to document them properly. There are two activities involved here. i. Require ment gathering &analysis First requirements are gathered and then analyzed. All relevant information is then collected from customers to clearly understand needs. Then analysis is done to remove incompleteness and inconsistency. ii. Requirement specification Requirements from above stage are organized into software requirement specification document (SRS). SRS to be reviewed and approved by customer. It forms basis of all carrying out all development activities.

3. Design
Its goa l is to tra ns for m re quire me nt s pec ifie d in SR S i n t o structure suitable for implementation in programming language. In traditional design approach there are two activities. i . St r uc t u re a na l y s i s p re p a re s d e t a i l a n a l ys i s o f d if fe re n t fu n c t i o n t o b e s u p p o rt e d by system and identification of data flow. Each function is sub divided and decomposed into sub function. i i . St r uc t u re d e s i g n c o ns is t s o f a rc h i t e c t u ra l d e s i g n. W he r e s ys t e m is d e c o mp o s e d into modules data structure & algorithms are designed and documented.

4. Coding & testing

a i m is t o t ra ns l a t e s o ft w a re d e s i g n i n t o s o u rc e c o d e . To write good programs coding standards are formulated. It indicates standard ways of laying out program codes, communicating naming conventions, templates for function and modules etc. So each component is implemented as a program module. - ne x t e a c h mo d u l e is u n i t t e s t e d . Ea c h mo d u l e is t e s t e d fr o m is o la t i o n o f o t he r modules then debugging and documenting it. The correct working of each module is determined individually.

Its

5. Integration &System testing

D i ffe re n t mo d u l e s a re i n t e g ra t e d i n p la n n e d ma n n e r. T h i s is d o n e i n c re me n t a l l y o v e r n u mb e r o f s t e p s . D u r i n g e a c h s t e p s p re v i o us l y p la n n e d modules are added to partially integrated system. It includes 3 kinds of activities i. testing : performed by development team. ii. testing : done by friendly set of customers. iii. Acceptance testing : done by customer himself

6. Maintance
It involves performing following activities. i. Corrective maintenance Correcting errors not discovered during developing product. ii. Perfective maintenance Improving the implementation and enhance the functionality of the system as per customer needs. iii. Adaptive maintenance Required for parting the software to work in new environment.

Functional Requirements View of Database

This system provides the view of the entire database, or partial view
based on the level of the user in the hierarchy. Depending on the database that is selected, the in-built queries might vary. So accordingly the system supports number of reports, graphical analysis, based on the user s requirement which will be generally needed to check the trend analysis by the product group.

Search Depending on the database that is selected, the user can search for
specific information regarding a particular entity i.e. this entity could be a BE s progress report database or any internal user for user details database. Accordingly there is a facility through which the different parameter values can be searched for a particular entity.

Add

Depending on the database that is selected, the user can add

information of a new entity. Accordingly the system allows for the creation of new entity and takes up relevant related information and save it into the appropriate database.

Update

Depending on the database that is selected, the user can modify some
details under certain parameters for an existing entity. Accordingly the system allows for modifying the details of a certain parameter related to an existing entity in a database.