Name of the project : 4
Objective /Vision
User of the system
Functional Requirements
Non-Functional Requirements i.
ii.
iii.
Optional Features
User Interface Priorities
Matrimonial matching bride and groom.
To provide suitable match for brides and grooms for RURAL
India. No payments to be made by anyone for use of
application. Payment to be made to person assisting if so
required.
1. Average parent or family member.
2. Assisted by a computer operator.
3. Administration by public provider of the application with
paper trail of usage.
Consumer:
1. User and candidate registration including good
qualifiers / quantifiers for categorization.
2. Good quality matching of candidates.
3. Appropriate suggestions for activities associated with
weddings.
4. Non-commercial functions designed to provide good
matches like a service provided by a NGO.
5. Mandatory feedback from users or disqualification from
further use.
6. Feedback from users on quality of assistance.
Assistant / Assister:
1. Log in with personal id.
2. Provide id of person(s) being assisted.
3. Document user request before executing it.
4. Assist in all functions.
5. Paper trail of functions used and print out of that users’
request with actions taken.
6. Mandatory feedback from users or disqualification from
further use.
Administration:
1. Typical queries made.
2. Number of successful matches made.
3. Mandatory feedback from users or disqualification from
further use.
4. Efficiency and feedback from users on assistants.
5. Some demographics on users criterion for making final
selections especially controversial items like caste.
Secure access of confidential data (user’s details).
SSL can be used.
24 X 7 availability
Better component design to get better performance at
peak time
Flexible service based architecture will be highly desirable for
future extension
1. Security for users as related to the authentication of
named candidates.
2. Interface to mobile device for primary user.
3. Suggest a hardware device (such a smart card) to
ensure consumers can consent only when they want.
A. Professional look and feel
 B. Use of AJAX atleast with all registration forms
C. Browser testing and support for IE, NN, Mozila, and
Firefox.
D. Use of Graphical tool like JASPER to show strategic
data to admin
E. Reports exportable in .XLS, .PDF or any other desirable
format
Reports
Other Important Issues
Team Size 2 – 4 members
Technologies to be used UML, J2EE, XML, e-Forms, AJAX, Web 2.0, Web-services,
SOA
Tools to be used • ROSE/RSA / WebSphere Modeler
• Eclipse/ RAD / Lotus Forms Designer / Portlet Factory
• WebSphere Portal/ WAS/ WAS CE / WPS
• DB2 Express – ‘C’ or DB2 UDB
• Tivoli CDP/TSM / Tivoli Directory Server
Linux will be the preferred OS.
Final deliverables must include A. Online or offline help to above said users, Application
deployment executive and developer
B. Application archive ( .war/.ear ) with source code
C. Database backup and DDL Script
D. Complete Source code
Documents