Free Student Projects

Matrimonial Agency Software SRS

Matrimonial Agency Software SRS

The project “Matrimonial System” is built to find a fit between the bride and groom according to their age, faith, or caste. The basic purpose of the SRS is to explain the full actions of the proposed program. It’s like an arrangement between the customer and the developer. The software system quickly understands and resolves any problems when the SRS is generated. Unique and extra emphasis is assigned to defining what the system wants, not how the system can function and accomplish its target. The final aim is to deliver a reliable and high-quality SRS.

INTENDED USERS AND READING SUGGESTIONS:

This Software Requirements document is intended for:

SCOPE: This project aims to computerize planned meetings, create tickets and pay for each user.

 

DEFINITIONS, ACRONYMS, AND ABBREVIATIONS:

OSOperating System

VB.NetVisual Basic.Net

GUIGraphical User Interface

PCPersonal Computer

MBMegaBytes

RAMRandom Access Memory

SQLStructured Query Language

REFERENCES:

OVERVIEW:

This paper offers a description of the features of the framework. SRS is like an arrangement between the developer and the customer about how to create the “MS” program. The right interpretation of the SRS encourages us to do the correct program which can be helpful for the growth of the project in the future. This system lets us handle all ticket sales in a quickly sorted manner. The project “Matrimonial System” is built to find a fit between the bride and groom according to their age, faith, or caste.

OVERALL DESCRIPTION

 PRODUCT PERSPECTIVE:

For more than one person, a database is used in the MS system. Each user has a special master key that can uniquely open a database for each user. Admin offers separate usernames and passwords for each account.

This involves a broad variety of promotional operations. This program aims to sell tickets for each passenger and therefore to minimize paperwork. It also produces regular updates to keep track of all sales operations.

USER CHARACTERISTICS:

OPERATING ENVIRONMENT

ASSUMPTIONS AND DEPENDENCIES:

FUNCTIONAL REQUIREMENT:

Login Module:

Registration module:

Report Module:

View module:

Match module:

EXTERNAL INTERFACE REQUIREMENT:

USER INTERFACES:

-GUI is provided by a self-explanatory program.

-User-friendly shapes, menus, and options are included in the app.

-The design of the product must be researched by the manufacturer.

-Technology provides alerts to clients for the support they need.

HARDWARE INTERFACES:

SOFTWARE INTERFACES:

OTHER NONFUNCTIONAL REQUIREMENT:

PERFORMANCE REQUIREMENT:

SAFETY REQUIREMENT:

SECURITY REQUIREMENT:

SOFTWARE QUALITY ATTRIBUTES:

PORTABILITY:

FLEXIBILITY:

 MAINTAINABILITY:

TIMELINESS:

RELIABILITY:

OTHER REQUIREMENTS:

None

 

DOWNLOAD NOW
Exit mobile version