This action might not be possible to undo. Are you sure you want to continue?
Online Matrimonial Application System
SOFTWARE REQUIREMENT SPECIFICATION SUBMITTED TO MANIPAL UNIVERSITY, MANIPAL (A Deemed University)
FOR THE PARTIAL FULLFILLMENT OF THE DEGREE OF MASTER OF COMPUTER APPLICATION By Prakash.A 080919055 Gopal Krishna 080919081 Sushant Kumar Das 070919058
Guided By: Tojo Thomas Poornima
Software Requirements Specifications Documen
4.2 Table of Contents Purpose Scope Definitions.4 Security 3.5 Overview 2. Acronyms. and Abbreviations. The Overall Description 2. The document is developed after a number of consultations with the client and considering the complete requirement specifications of the given Project.3 Availability 3.6 Portability 2 3 3 4 4 4 4 5 5 5 5 5 6 6 6 8 8 8 8 9 1 Introduction Purpose The main objective of this document is to illustrate the requirements of the project Online Matrimonial Applicaton System(OMAS).1.5 Assumptions and Dependencies: 3.1. Software Requirements Specifications Documen .4 References 1. Specific Requirements 3.2 Hardware Interfaces 3.4.1 External Interfaces 3.4. 1.3 Software Interfaces Functional Requirement 3.3 User Characteristics: 2. The document gives detailed description of the both functional and non functional requirements proposed by the client.1 User Interfaces 3.4 Software System Attributes 3.4.1 Usability 3.1. The final product of the team will be meeting the requirements of this document.1 Product Perspective: 2.
• • • Software Requirements Specifications Documen . RAM . Date : 09-09-2010 Prepared By : Prakash. User tracking 3. Acronyms. Title : ONLINE MATRIMONIAL APPLICATION Definitions. in the event that a component fails. Users will get a notification mail to remind them in case their matches in the site.design documents.Random Access Memory. GUI-Graphical User Interface. capturing the benefits and meet the requirements of the users. Gopal krishna. Fault Tolerance –Fault-tolerant describes a computer system or component designed so that. Product Characteristics and Requirements : 1.they will get the mail from our operator. Chating feature 5. a backup component or procedure can immediately take its place with no loss of service. 2.is the ease and speed with which any maintenance activity can be carried out on an item of equipment. Maintainability .Sushant Project Justification: This project is basically about the website where in users can get online information about life partner. Secured database. Project Management Deliverables: Project plan. ORE-Online Matrimonial Application System. SRS : Software Requirement Specification.This organization is in business of matchmaking for individuals looking for their life partner. Agent: Registered Users. software code.3 Scope Project SYSTEM. Search feature 4. test plan Project Success Criteria: Our main goal is to complete this project within allotted dead line. Training manuals Product-related deliverables : Research reports . Project charter. and Abbreviations. Scope statement.
operate.1 Product Perspective: The proposed Online Matrimonial Application System(OMAS) which is being developed is a System that will provide a information about person nothing but life partner. 1.effort required to learn.assumptions and dependencies are described in this section.5 Overview The SRS will provide a detailed description of the Online Matrimonial Application System.Pankaj Jalote http://www.com/ 1.height. The Software Requirements Specifications Documen . 2.cast and second marriage. 1. product function. and interpret output.DFD. user characteristics. • Usability . The Overall Description 2. overview of the characteristics and constraints of the system.trulia.5.2 Product Functions: The OMAS System real time information about life partner in the site. 1.zillow. This document will provide the outline of the requirements.Schema diagram.3 Section 4: This section of the SRS contains ER diagram. The Product functions are more or less the same as described in the product perspective.He/She can find his/her life partner based on his/her qualification.2 Section 3: This section of SRS contains all the software requirements mentioned in section 2 in detail sufficient enough to enable designers to design the system to satisfy the requirements and testers to test if the system satisfies those requirements. 1.1 Section 2: This section of the SRS will provide the general factors that affect the product and its requirements.5.is the task of doing any work necessary to make the computer program run in the new environment. • Reliability .4 References The SRS document uses the following documents and web sites as references: -An Integrated Approach To Software Engineering . prepare input. The items such as product perspective. 2. It provides the background for those requirements.extent to which program performs with required precision.com/ http://www.4 • Portability.5.
3. • The Operator should be provide the updated information about person who are register to this site.1 User Interfaces GUI (Graphical User Interface) : This section should include a set of Msg Box to guide the users in order to illustrate User interface features.1. • The customer can get the information about person thats matches to his/her profile.5 Assumptions and Dependencies: • • • • The users have sufficient knowledge of computers. Software Requirements Specifications Documen . • Customer : Users can send mail about their requirnments.4 Design and Implementation constraints: Each customer must keep their password as confidential. More over the customer must have individual user names for creating a login in the OMAS system. 2. • Provisions for the users to set previlages.3 User Characteristics: There are basically 3 types of users: • Administrator: Administrator will be able to do anything they want like adding new agents/users to the system and Permit them with proper access rights. The users know the English language. Only Administrator can control customer addition and deletion in the system. • The website provides login facility to the users.5 functions of the system include the system providing different type of services based on the type of users. • Operator: They are the core users and are able to update the user details according to the plot/s or building/s that they buy or registered.1 External Interfaces 3. 2. Specific Requirements 3.He/She can fix priorities also for his searching. 2. as the user interface will be provided in English Each User must have a User Id and password There is only one Administrator.User id and password is given to the agent by administrator.
3 Software Interfaces • • • • • • Front End : Net Beans 6. Input: User id/username. user password and other personal details.2. 3.4 Search Process: Introduction: Search on cast.0 Web Browsers: Mozilla firefox/Internet Explorer Functional Requirement 3.1.2. Input: User id and user password. Processing: It will verify the User id and password from the User database.qualification.height and second marriage etc.1. Input: User id. Input: Search option. Software Requirements Specifications Documen . 3.6 3.3 Deleting User: Introduction: Delete Existing User.0 and above. Output: Appropriate Msg displayed telling account created. Processing: It will store the User id and password if appropriate in the User database. Processing: Deletion of existing User. Output: Existing user deleted from Database.2 Hardware Interfaces • • • Any processor above 2.4 GHz Hard Disk : 40 GB Or Above RAM : 512 MB Or Above 3.2 User verification: Introduction: This process will verify the user id and password.9 Back End : My sql 5. Output: Appropriate Msg displayed based on Verification of User id and password 3. Operating System : Windows 2000/Windows XP/Windows Vista Platform: J2EE Web Servers: Tomcat 6.2.1 Creation of new User: Introduction: This process will provide a user account.2.
They are: 3.3 Performance Requirements: It specifies the performance constraints on the software system. Output: New Information gets stored in the Database. Administrator : Access both the above modules. There are 2 types of performance requirements. 3.password and customer details with attractive photo.1 Static Requirements: No of Users: • • • Customer: has access to browse and find his/her life partner. Software Requirements Specifications Documen . While performing the search operation any of the criteria must be specified user’s account must be updated accordingly.3.2. Processing: Insertion of new customer details in the database. Operator: has access to post advertisements. password and requirements. Input:Username.2.6 paid user registration: Introduction: Allows the users to finalise their choice as per their budget. Processing: Search and mailing. Input: User Id.5 Add New Customer: Introduction:Introducing a new customer.9 Following Constraints must be satisfied to meet the Functional Requirements • • • • A customer can access profile only which meets his/her requirments . Output: Availability and locality with its complete details 3. An one operator can maintain only 10 person not more then that. 3. Output: update availability in database. 3.7 Processing: Search based on criteria in database.2.match the profile.
4 Security •The system shall check all user-supplied input for malicious content (e. • • Access shall be controlled with usernames and passwords.g. with built in error checking and correction facilties. 3.4 Software System Attributes 3. • The system is user friendly and self-explanatory. • 3. • System is reliable for giving correct search results about the books to the users.4.4.1 Usability Since all users are familiar with the general usage of GUI.4.2 Reliability and Fault Tolerance: Requirements about system behavior in the face of certain kinds of faults is specified.4.3.4. 3. escape characters. The system shall be operational 10 hours a day and 7 days a week.8 3. no specific training is required.5 Maintainability A new developer shall reasonably be able to understand all internal logic of Component name within 3days Software Requirements Specifications Documen . and buffer overflow attacks).3 Availability The system is available 100% for the user and is used 10 hrs a day and 345 days a year. • It is fault tolerant because if the system does not find the requested books an appropriate message is displayed to the users on the screen. Passwords shall be checked for quality.2 • times • Dynamic Requirements: Response time of the search operation should be less then Five second 90% of the The performance of the overall system should be fast and error free.. 3. inappropriate markup. 3.
Implementation starts from the top of the hierarchy and proceeds to the bottom of the hierarchy.4.4 GHz Hard Disk : 40 GB Or Above RAM : 512 MB Or Above System must be installed with Net Beans 6.6 Portability Library Circulation And Management System is potable to system that supports following • • • • Any processor above 2. 3.This approach requires that the specifications and requirements of the system are clear and everything is known in advance.The requirements and specifications are well-defined. In this approach hierarchical structure is followed so the complexity is divided into different modules. subtotals and date picker 3.5 Design Constraints: 184.108.40.206 3.7 Development Approach: We used Top Down Approach for the developement of our project.So the process model we thought to follow is Heirarchical Model. 3. summaries.Tomcat server. 3.1 Standard Compliance: This specifies the requirements for the standards the system must follow • Crystal reports must be produced to the users. thus imposing restrictions on the design • • • System must support Windows 98 or higher version operating system System must have minimum of 512 MB RAM & above.6 Process Model: The project undertaken by us is been done under supervision. 3.9 and Mysql. System must have hard disk of 40 GB memory .8 Team Structure: Software Requirements Specifications Documen .2 Hardware Compliance: The software may have to operate on some existing or predetermined hardware. • Reports must include database field. formula field.
A Data flow diagram: Use case diagram: Software Requirements Specifications Documen . gathering other requirements and testing will be handled by Sushant Kumnar das. Operator Module : The task of registering Users on a paid service base and Coding shall be handled by Gopal Krishna. 3.Detailed designing will be done by Prakash.e.9 Role Of Team Members User Module: The management of customer details. Administrator Module: Testing of both user and operator Module. no one is above or below from any team member.10 The team structure chose by us is egoless team structure as all team members are in one level i. This type of team structure has the advantage that there is free flow of information between all programmers and personal factors are less so every one is concerned only about the successful completion of the project on time.
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue listening from where you left off, or restart the preview.