...

1. “Biye Shaadi”
A Matrimony Website
Lamia Binta Latif(366)
Snigdha Rahman(360)
Choyon Sarker (392)
Suraiya Mahmuda (364)
Prepared by

2. Contents
 1. Overview of the proposed project
 2. Use case diagram
 3. User story
 4. Extended use case
 5. Sequence diagram
 6. State chart diagram
 7. Class diagram
 8. Database schema

3.  Purpose: “Biye Saadi” a matrimony website serves as an online platform designed to
help individuals find potential life partners for marriage. The primary purpose of a
purpose of a matrimony website is to facilitate the process of matchmaking and
and connect people who are seeking committed relationships and marriage.
 Intended audience: The intended audience of our website primarily consists of
individuals who are seeking a life partner for the purpose of marriage. The website
website caters to people of marriageable age and those who are ready to enter into a
enter into a committed relationship leading to matrimony.
Project Proposal

4.  “Biye Shaadi” is an online matrimonial website designed to help
individuals find their life partners. It provides a platform where,
 users can create profiles, manage profiles, search for compatible
matches, visit the site, search others profile and interact with
 Visitors also visit and they only search users profile and view
profiles.
 and Admin can handle users profile, make announcement and
verify users profile.

5. Use case diagram
 Use case diagram is the primary form of system/software requirements for a
new software program underdeveloped.
 Use cases specify the expected behavior (what), and not the exact method
of making it happen (how).
 A key concept of use case modeling is that it helps us design a system from
the end user's perspective.
• It only summarizes some of the relationships between use cases, actors, and
systems.
• Use cases represent only the functional requirements of a system.
 The use case diagram of our website describes that in the system there will
be only 3 actor( user, view and admin). And all the functional requirements.

6. Use case diagram

7. User Story
 A User Story is a requirement expressed from the perspective of an end-user goal.
• A short description of the behaviour of the system
• The entire system is specified through stories
• Users tell the stories, and developers listen, ask questions to understand context
• Each story is short, goal oriented – testable
• Generally implementation issues are not discussed
 User Stories are often deemed to comprise three elements - the 3C’s
• Card
• Conversation
• Confirmation

8. User Story
 View Profile
 Card
• As an user or a visitor, I want to view any profile in this website.
 Conversation
• he/she has to register themselves first.
• Users can see all informations but visitors can’t see all regarding informations. For this purpose
he/she has to register themselves first
 Confirmation
1. Success – You must be a valid internet user.
• For user the desired profile will be shown.
• Visitor can’t see all regarding information of that user. He/she can see some specific information.
• 2. Failure – display message:
• Incorrect information(Incorrect First Name, Incorrect Last Name, Invalid Email address provided here),
here),
please try again.
• Service unavailable – please try again later.
• The server may be down.
• There may not be any internet connection.
.

9. User Story
 Delete Account
 Card
• As an user , I want to delete my account.
 Conversation
• I can delete my account anytime
• I have to choose a valid reason for deleting my account
 Confirmation
1. Success – Valid user logged in and referred to the home page.
• A confirmation message “Your account successfully deleted” will be provided.
2. Failure – display message:
• Incorrect information(Incorrect First Name, Incorrect Last Name, Invalid Email address provided here),
here),
please try again.
• Service unavailable – please try again later.
• Account has expired – refer to the account renewal page
• The server may be down.
• There may not be any internet connection.
.

10. Extended user story/ Use case specification
 A Use Case Specification is a textual description of the functionality provided by the system.
 It captures actor-system interaction.
 It specifies how a user interacts with a system and how the system responds to the user actions
 A typical Use Case Specification is structured as
 Use Case ID
 Use Case Name
 Actors:
 Description
 Preconditions
 Postconditions
 Exception

11. Extended user story/ Use case specification
Use case ID: UC003
Use case Name: Reset password
Actor: User
Description:
1. A user can reset password through a link named “Reset password” send to
. his/her email or what’s app
Exception:
1.Page not found.
2.No database connection.
Precondition:
1.User must have an account.
Postcondition:
1. Successful – Display message “Password have been updated” .
2.Unsuccessful – Display message “Wrong password/email”
– Display message “Service unavailable – please try again later”
– Display message “There may not be any internet connection”
3. Exception - Stay in same page if possible.

12. Extended user story/ Use case specification
Use case ID: UC005
Use case Name: Delete Account
Actor: User
Description:
1. A user can delete account anytime.
Exception:
1.Page not found.
2.No database connection.
Precondition:
1.User must have an account.
2.User must login to the account.
Postcondition:
1. Successful – Display message “Account has been deleted” .
2. Unsuccessful – Display message “Wrong password/email”
– Display message “Service unavailable – please try again later”
– Display message “There may not be any internet connection”
3. Exception - No database connection.

13. Sequence diagram
 Sequence diagram is a behavioral diagram.
 It represents the dynamic aspects of the system
 In the sequence diagram,
• It has multiple objects, interaction among the objects through messages,and it must be
in timely ordered .thats mean time passes from top to bottom.
 Purpose of Sequence Diagram:
• To model high-level interaction among active objects within a system.
 Sequence diagram key elements are :
• actor , Lifeline , Activations ,time,Call Message, Return Message, Self Message, Note etc.

14. Sequence diagram for User & Visitor
InvalidLogged in
Log in Details
Sequence Diagram for User
Registration Details
Verify Log in Details
Successfully Logged In
Update Profile
Updated successfully
search Profile verify details
If [yes] Result Found
Send message/Email
Done successfully
User Web Interface Database
Else
Result not found
Logout Request
Successfully logged out
Visitor
Visit the website
Enter Registration Details
Error Message
Registration Approval

15. Log in Detail
Invalid Log in
verify login detail
Successfully logged in
Handle Profile
Updated successfully
verify User
If [Yes]
Add New User
Registration successful
Admin web Interface Database
Else
Registration Failed
Delete/Deactive selected user
Deleted/Deactived successfully
Make announcement
Update Application
Update done successfully
Logout Request
Logged out successfully
Sequence diagram for Admin

16. State Chart diagram
 A State Chart Diagram (also known as a State Machine Diagram) represents
the various states that an object can be in and the transitions between
those states in response to events.
 It is particularly useful for modeling the lifecycle of an object or the
behavior of a system with distinct states.
 Purpose of State chart diagram:
• To describe different states of an object during its life time.
 State Chart Diagrams consist of states, transitions, events, and actions
associated with those states and transitions

17. Edit Account
Edit Account
Update necessary
information
Update profile
Delete or Deactive
account
or upload photo
close
valid information
invalid information
State chart diagram for Edit account

18. Search
search for matches Read notification
view profile or
send message
Close
if matches
End
No matches
State diagram for Search

19. UML Class diagram
 A UML class diagram is a type of static structure diagram in the Unified Modeling
Language (UML) that describes the structure of a system by showing the system's classes,
their attributes, operations and the relationships among objects.
 Purpose of UML class diagram
• To visualize and document of the structure of a system and system design
• To communicate the system design to stakeholders
• To identify, resolve design errors to generate code, which can save time, money
and effort as well as To improve the maintainability and extensibility of a system
 The UML Class Diagram of our Matrimony website describes it’s three actors ( visitor
,admin , user ) and the attributes, operations of a class, relationships between the
entities(Association, Aggregation, Composition, Generalization, Dependency) and the
constraints imposed on the system.

20. Class diagram for “Biye Shaadi”

21.  Database Schema refers to a structure that represents relationships among data and
defines how information is stored in a database.
 Database Schemas are essential to do the following:
• Consistent formatting
• Maintaining unique primary and foreign keys
 Our Database Schema describes:
• How data is organized within a relational database; this is inclusive of logical constraints
constraints such as, table names, fields, data types, and the relationships between these
these entities information
• Clears the way to faster and easier creation of Reports and Dashboards.
• Used to specify data items in both data sources and data warehouses in the Data Analytics
Analytics field.
 Database Schema tables can then be converted into SQL code by developers and
developers and database administrators.
Database Schema

22. Database Schema for “Biye Shaadi”

23. Conclusion
 Matrimony Website is to provide Grooms and Brides with excellent matchmaking
experience by exploring the opportunities and resources to meet true potential partner
through online .
 There are different sectors like Registration ,Personalinfo , Login, SearchProfile from
various purposes like userID, usernName ,userGender , UserReligion ,Commucating
through Message etc. So the Bride/Groom can get their interest for find their partner.
Bride/Groom can directly search Partner according to their required criteria.
 Also provide facility like quick tour.
 This is a complete module that contains the flow of the website.

24. Tools & Referanches
 Tools
• Visual Paradigm
• Draw.io
• Lucid Chart
• Creatively
 References
• www.google.com
• www.wikipedia.com
• www.shaadi.com
• www.simplymarry.com
• www.matrimonial.com