Free Student Projects

Follow

Advertisement

Matrimonial Agency Software SRS

Share

Matrimonial Agency Software SRS

The project “Matrimonial System” is developed to find the match between bride/groom according to their age, religion or caste. The basic purpose of SRS is to describe the complete behaviour of the software proposed. It is like an agreement between client and the developer. Software system easily understands and solves any problem if the SRS is produced. The special and the extra importance are given to identify what is required from the system, not how the system will work and achieve its goal. The final goal is to produce a stable and a high quality SRS.

INTENDED USERS AND READING SUGGESTIONS:

This Software Requirements document is intended for:

Advertisement

SCOPE: This project is helpful to computerize the scheduled events, generation of tickets and payment for each user.

DEFINATIONS, ACRONYMS AND ABBREVIATIONS:

OS

  • operating  System

VB.Net

Visual Basic.Net

GUI

Graphical User Interface

PC

Personal Computer

MB

Mega Bytes

RAM

Random Access Memory

SQL

Structured Query Language

REFERENCES:

OVERVIEW:

This document provides an overview of the system functionality. SRS is like an agreement between the developer and the client of how the software “MS” is to be constructed. The correct understanding of the SRS enables us to do correct software and will be useful in future stages for the development of the project. This system helps us to manage all the ticket transactions in an easily sorted manner. The project “Matrimonial System” is developed to find the match between bride/groom according to their age, religion or caste

OVERALL DESCRIPTION

 PRODUCT PERSPECTIVE:

A Database is included for more than one user in the MS system. Every user has a unique master key and it will uniquely open the database for each user. Admin provides different username and password for each user.

Advertisement

This includes a wide range of sales activities. This software aims at the sales of ticket for each passenger and hence reducing paper work. It also provides day by day reports to keep track of all the sales activities.

USER CHARACTERISTICS:

OPERATING ENVIRONMENT

ASSUMPTIONS AND DEPENDANCIES:

FUNCTIONAL REQUIREMENT:

Login Module:

Introduction: Authorized users are allowed to access.

Advertisement

Input: User enters the User type, Username and password.

Process Definition: Checks User type, Username and password is valid or not.

Output: User is directed to next page or shows the message box “Login Failed”.

Registration module:

Introduction: Only Admin can access the page.

Input: Admin has the authority to provide username and password for new users

Process Definition: Checks same username and password exists or not and also checks whether all the fields are entered.

Output: Employee gets the username and password.

Report Module:

Introduction: Only Admin can access the page and check the report.

Advertisement

Input: Bride/groom

Process Definition: It retrieve’s all the information stored from different tables.

Output: Requested report is generated.

View module:

Input: bride/groom name, DOB, age, religion caste, contact, address

Process Definition: In the view module the user can view bride/grooms information which has already been saved. The user can also add new information or edit the present information.

Output: New bride/grooms information is added to the table.

Match module:

Input: type, bride/grooms name

Process Definition: the user can enter bride/grooms information and on a single click can find the perfect match to the corresponding bride/groom.

Advertisement

Output: The match can be found or not.

EXTERNAL INTERFACE REQUIREMENT:

USER INTERFACES:

– GUI is provided by the software which is self-explanatory.

–  User friendly forms, menus and options is contained by the software.

– Designing of the product have to be studied by the developer.

– Software gives warnings with necessary assistance to the clients.

HARDWARE INTERFACES:

SOFTWARE INTERFACES:

Advertisement

OTHER NONFUNCTIONAL REQUIREMENT:

PERFORMANCE REQUIREMENT:

SAFETY REQUIREMENT:

SECURITY REQUIREMENT:

SOFTWARE QUALITY ATTRIBUTES:

PORTABILITY:

Advertisement

FLEXIBILITY:

 MAINTAINABILITY:

In this stage, validation will be referred from the given SRS

TIMELINESS:

RELIABILITY:

OTHER REQUIREMENTS:

None

Project synopsis: Click here>> 

Download this project code:

downloadlink
Advertisement

Share

Related

Advertisement

Latest

Advertisement