CHAPTER 5 WEB APPLICATION OF SECURE AND TRUSTED MATRIMONIAL SYSTEM

Chapter 5
Details of Project Design, Working & Processes

5.1 Project Design

5.1.1 E-R Diagram
An entity–relationship model is usually the result of systematic analysis to define and
describe what is important to processes in an area of a business. It does not define the
business processes; it only presents a business data schema in graphical form. It is usually
drawn in a graphical form as boxes (entities) that are connected by lines (relationships) which
express the associations and dependencies between entities.
An ER model is typically implemented as a database. In a simple relational database
implementation, each row of a table represents one instance of an entity type, and each field
in a table represents an attribute type. In a relational database a relationship between entities
is implemented by storing the primary key of one entity as a pointer or "foreign key" in the
table of another entity.

Fig 5.1.1: E-R Diagram

SAMARTH POLYTECHNIC, BELHE ( COMPUTER ENGG.) Page 16

 CHAPTER 5 WEB APPLICATION OF SECURE AND TRUSTED MATRIMONIAL SYSTEM

.
5.1.2 Data Flow Diagram

A data flow diagram (DFD) is a graphical representation of the "flow" of data through
an information system, modelling its process aspects. A DFD is often used as a preliminary
step to create an overview of the system without going into great detail, which can later be
elaborated. DFDs can also be used for the visualization of data processing (structured
design). A DFD shows what kind of information will be input to and output from the system,
how the data will advance through the system, and where the data will be stored. It does not
show information about process timing or whether processes will operate in sequence or in
parallel, unlike a traditional structured flowchart which focuses on control flow, or a UML
activity workflow diagram, which presents both control and data, flows as a unified model.
In proposed system DFD diagram shows the first step to create a project overview. In
DFD diagram there are two entities such as Admin and user. Admin is internal entity it login
to system and get conformation also admin add, update and delete various profiles & manage
accounts of users. User is a external entity it login to system and also update their profile.

5.1.2.1 DFD Level 0

USER SEARCH WEBSITE

Fig 5.1.2.1: DFD Level 0

5.1.2.2 DFD Level 1

SAMARTH POLYTECHNIC, BELHE ( COMPUTER ENGG.) Page 17

CHAPTER 5 WEB APPLICATION OF SECURE AND TRUSTED MATRIMONIAL SYSTEM

Fig 5.1.2.2: DFD Level 1

5.1.2.3 DFD Level 2

Fig 5.1.2.3: DFD Level 2

SAMARTH POLYTECHNIC, BELHE ( COMPUTER ENGG.) Page 18

CHAPTER 5 WEB APPLICATION OF SECURE AND TRUSTED MATRIMONIAL SYSTEM

5.1.3 Use Case Diagram

Use cases can be defined as system functionalities written in an orderly or organized
manner. Use case diagrams are pictorial representation of use cases. These diagrams show a
set of use cases and relationships. An actor is a special kind of class. Al application of use
cases diagrams is to illustrate the static use case view of a system. These diagrams are
exclusively important in organizing and modelling the behaviour of system. A use case
diagram views a set of use cases and actors. Use case diagrams are vital as they are used for
visualizing, specifying, and documenting the behaviour of an element.
In Use Case diagram there are two actors first is admin and second is user. Both are
referred as users of a system. Admin and user are using the some use cases. Admin use login,
eligibility, modifying profiles and also observe the launched profiles and user uses the login,
view others profiles, send interest to profile and report use cases.

Fig 5.1.3: Use Case Diagram

SAMARTH POLYTECHNIC, BELHE ( COMPUTER ENGG.) Page 19

CHAPTER 5 WEB APPLICATION OF SECURE AND TRUSTED MATRIMONIAL SYSTEM

5.1.4 Activity Diagram

The basic purposes of activity diagrams are similar to other four diagrams. It captures
the dynamic behavior of the system. Other four diagrams are used to show the message flow
from one object to another but activity diagram is used to show message flow from one
activity to Activity is a particular operation of the system. Activity diagrams are not only
used for visualizing the dynamic nature of a system, but they are also used to construct the
executable system by using forward and reverse engineering techniques. The only missing
thing in the activity diagram is the message part. It does not show any message flow from one
activity to another. Activity diagram is sometimes considered as the flowchart. Although the
diagrams look like a flowchart, they are not. It shows different flows such as parallel,
branched, concurrent, and single.
The purpose of an activity diagram can be described as −
 Draw the activity flow of a system.
 Describe the sequence from one activity to another.
 Describe the parallel, branched and concurrent flow of the system
In activity diagram there are two modules admin and user. In system both admin and
user will login then our system authenticates validity. If login is valid then user can view
profiles also can edit profile and can view reports. In profile details user can apply for new
profiles and also check details of new launched profiles. In my account user can change
password or can edit profile and also can view reports of applied profiles. If user login is
invalid or authentication failure then user again performed login activity. Then the second
module of our system is admin. Admin also have some activities like add new profile, update
those profile and delete profile. Admin also can change password and edit profile and admin
can also view report profile wise can also check status of mail.

SAMARTH POLYTECHNIC, BELHE ( COMPUTER ENGG.) Page 20

CHAPTER 5 WEB APPLICATION OF SECURE AND TRUSTED MATRIMONIAL SYSTEM

START

ENTER URL

VIEW WEBSITE

HOME ABOUT US EVENTS CONTACT US PROFILES

ABOUT IMAGES REGISTR GOOGLE OTHERS CONT

COMPANY EVENTS -ATION MAP FORM ACT

MAIL PERSONA OTHERS

L DETAIL DETAILS

EXIT

Fig 5.1.4: Activity Diagram

SAMARTH POLYTECHNIC, BELHE ( COMPUTER ENGG.) Page 21

CHAPTER 5 WEB APPLICATION OF SECURE AND TRUSTED MATRIMONIAL SYSTEM

5.1.5 Sequence Diagram

A sequence diagram shows object interactions arranged in time sequence. It depicts
the objects and classes involved in the scenario and the sequence of messages exchanged
between the objects needed to carry out the functionality of the scenario. Sequence diagrams
are typically associated with use case realizations in the Logical View of the system under
development. Sequence diagrams are sometimes called event diagrams or event scenarios. A
sequence diagram shows, as parallel vertical lines (lifelines), different processes or objects
that live simultaneously, and, as horizontal arrows, the messages exchanged between them, in
the order in which they occur. Solid arrow heads represent synchronous calls, open arrow
heads represent asynchronous messages, and dashed lines represent reply messages.
If a caller sends a synchronous message, it must wait until the message is done, such
as invoking a subroutine. If a caller sends an asynchronous message, it can continue
processing and doesn’t have to wait for a response. Asynchronous calls are present in
multithreaded applications, event-driven applications and in message-oriented middleware.
In sequence diagram there are three participants as user, admin and database. User
and admin both are performed login with database. If login is valid then database will send
acknowledgment to user or admin. Admin can add new profile, update their profile and delete
the scheme and can check eligibility of user from database. If user got SMS of eligibility then
user can apply for that profile. When user can apply for any profile, user can get
acknowledgement.

SAMARTH POLYTECHNIC, BELHE ( COMPUTER ENGG.) Page 22

CHAPTER 5 WEB APPLICATION OF SECURE AND TRUSTED MATRIMONIAL SYSTEM

Fig 5.1.5: Sequence Diagram

SAMARTH POLYTECHNIC, BELHE ( COMPUTER ENGG.) Page 23

CHAPTER 5 WEB APPLICATION OF SECURE AND TRUSTED MATRIMONIAL SYSTEM

5.2 Project Planning

5.2.1 Efforts
Various Efforts in the Deployment of Our Project Are As Follows-
1. Finding project topic
2. Finding Existing System and disadvantages
3. Collecting information
4. Project Proposal
5. Execution of plan in fifth semester
5.1 Requirement Gathering- SRS
5.2 Analysis- Scope & Feasibility Study
5.3 Design – Algorithm, Architecture, Detail Working, ERD, DFD, UML.
5.4 Planning & Scheduling – efforts, Time & cost Estimation, WBS, Team
Structure, Timeline Chart
6. Fifth Semester Project Report
7. Planning of sixth semester
7.1 Implementing proposed system
7.2 Developing GUI
7.3 Dynamic programming
7.4 Testing of project
8. Sixth Semester Project Report
9. Deployment
10. Maintenance

5.2.2 Time Estimation

Table 5.2.2: Time Estimation
Work Week

Requirement Gathering 1 Week

Literature Survey 1 Week

Analysis 1 Week

Proposal 2 Weeks

SAMARTH POLYTECHNIC, BELHE ( COMPUTER ENGG.) Page 24

CHAPTER 5 WEB APPLICATION OF SECURE AND TRUSTED MATRIMONIAL SYSTEM

Design 3 Weeks

Planning & Scheduling 4 weeks

Report Writing 2 weeks

GUI 2 Weeks

Coding/Implementation 5 Weeks

Testing 3 Weeks

Final Documentation 2 Weeks

When you have a detailed list of all the tasks that you must achieve to complete the
project then you can begin to estimate how long each will take. Make sure that you also allow
time for project management administration, detailed project, liaison with outside bodies’
resources and authorities, meetings, quality assurance developing supporting documentation
or procedures necessary, and training.

5.2.3 Cost Estimation

Cost estimate is the approximation of the cost of a program, project, or operation. The
cost estimate is the product of the cost estimating process. The cost estimate has a single total
value and may have identifiable component values. A problem with a cost overrun can be
avoided with a credible, reliable, and accurate cost estimate.
The Constructive Cost Model (COCOMO) is a procedural software cost estimation
model developed by Barry W. Boehm in 1981. It is an algorithmic approach to estimating the
cost of a software project. By using COCOMO you can calculate the amount of effort and the
time schedule for projects. From these calculations you can then find out how much staffing is
required to complete a project on time. COCOMO's main metric used for calculating these
values is lines of code (denoted KLOC for COCOMO II, or KDSI for COCOMO 81 and
measured in thousands), function points (FP), or object points (OP).
COCOMO 81 has three different models that can be used throughout a projects life
cycle.

SAMARTH POLYTECHNIC, BELHE ( COMPUTER ENGG.) Page 25

CHAPTER 5 WEB APPLICATION OF SECURE AND TRUSTED MATRIMONIAL SYSTEM

 Basic Model – this model would be applied early in a projects development. It

will provide a rough estimate early on that should be refined later on with one
of the other models.
 Intermediate Model – this model would be used after you have more detailed
requirements for a project.
 Advanced Model – when your design for a project is complete you can apply
this model to further refine your estimate.
Within each of these models there are also three different modes. The mode you choose
will depend on your work environment, and the size and constraints of the project itself. The
modes are:

COCOMO applies to three classes of software projects:

1) Organic- this mode is used for “relativity small software teams developing
software in a highly familiar, in-house environment”.
2) Semi-detached- an intermediate stage somewhere in between organic and
embedded. Projects are usually of moderate size of up to 300,000 lines of
code.
3) Embedded- operating within tight constraints where the product is strongly
tied to a “complex of hardware, software, regulations and operational
procedures”.

Table 5.2.3: Cost Estimation

Model A B C D
Organic 2.4 1.05 2.5 0.38
Semi-detached 3.0 1.12 2.5 0.35
Embedded 3.6 1.20 2.5 0.32
Here we used organic model in our project because line of code in our project is near about
15000.
Total line of code is 14668 line. Then we calculate the effort for using following formula:
E=a (KLOC) b
Where
E is the Effort in staff months
a (14.66) and b(1.05) are coefficients to be determined
KLOC is thousands of lines of code

SAMARTH POLYTECHNIC, BELHE ( COMPUTER ENGG.) Page 26

CHAPTER 5 WEB APPLICATION OF SECURE AND TRUSTED MATRIMONIAL SYSTEM

Here KLOC is the line of code in thousand then 14.66 is the KLOC of our
project
a=24 & b=1.05(Both are the constants value)
KLOC=2.3
E=?
E=a(KLOC)b
E=2.4(2.3)1.052
E= 6 staff-months

 Project Duration
We used following formula to calculate the project duration
TDEV =c(E)d
Where,
TDEV is a time for development
c(2.5) and d(0.38) are constants to be determined
E is the efforts
a=2.5 & d=0.38(Both are the constants value)
E=6
TDEV= c(E)d
TDEV= 2.5(6)0.38
TDEV= 5 months

Using COCOMO model we calculate the efforts, duration for our project,
To calculate efforts, Duration we, required the staff and months for the project.
We have,
E=6 staff months
TDEV=5 months

 Project Cost
Using this, we can calculate Project Cost for staff
Cost = (E*salary)*TDEV
= (6*1000)*5
= 30,000.

SAMARTH POLYTECHNIC, BELHE ( COMPUTER ENGG.) Page 27

CHAPTER 5 WEB APPLICATION OF SECURE AND TRUSTED MATRIMONIAL SYSTEM

In Navjeevan Vivah Sanstha project 6 staffs are required for 5 months, Hence we have to give
salary 5,000 to each staff per month

5.3 Project Schedule

5.3.1 Project Work Breakdown Structure

Fig 5.3.1: Project Work Breakdown Structure

We can use Waterfall model, which are as following:

5.3.1.1 Requirement gathering and Analysis.

This is the first phase of waterfall model which includes a meeting with the customer to
understand his requirements. The software definition must be detailed and accurate with no
ambiguities. It is very important to understand the customer requirements and expectations so
that the end product meets his specifications. Requirement gathering and Analysis phase the
basic requirements of the system must be understood by software engineer, who is also called
ANALYST. All this requirements are then well documented and discussed further with the
customer for reviewing.

5.3.1.2 Design.

SAMARTH POLYTECHNIC, BELHE ( COMPUTER ENGG.) Page 28

CHAPTER 5 WEB APPLICATION OF SECURE AND TRUSTED MATRIMONIAL SYSTEM

The customer requirements are broken down into logical modules for the ease of
implementation. Hardware and software requirements for every module are Identified and
designed accordingly. Algorithms and diagrams defining the scope and objective of each
logical model are developed. In short, this phase lays a fundamental for actual programming
and implementation. It is an intermediate step between requirements analysis and coding. The
requirements are translated in some easy to represent form using which coding can be done
effectively and efficiently. The design needs to be documented for further use.

5.3.1.3 Coding/Implementation.
Coding is a step in which design is translated into machine-readable form. If design is done in
sufficient detail then coding can be done effectively. Programs are created in this phase.In
this phase all software divided into small module then after doing coding for that small
module rather than do coding whole software.

5.3.1.4 Testing.
In this stage, both individual components and the integrated whole are methodically verified
to ensure that they are error-free and fully meet the requirements outlined in the first step. In
this phase testing whole software into two parts,
1) HARDWARE
2) SOFTWARE.
Type of testing is
1) White box testing.
2) Black box testing.

5.3.1.5 Deployment of System

Once the functional and non-functional testing is done. The product is deployed in the
customer environment or released into the market.

5.3.1.6 Maintenance
This is the final phase of the waterfall model, in which the completed software product is
handed over to the client after alpha, beta testing.After the software has been deployed on
the client site, it is the duty of the software development team to undertake routine
maintenance activities by visiting the client site. If the customer suggests changes or
enhancements the software process has to be followed all over again right from the first phase
i.e. requirement analysis.

SAMARTH POLYTECHNIC, BELHE ( COMPUTER ENGG.) Page 29

CHAPTER 5 WEB APPLICATION OF SECURE AND TRUSTED MATRIMONIAL SYSTEM

5.3.2 Team Structure

Jadhav Sakshi
Role: Leader
Task: Project
Planning,Requirementanalysis
,Design, developement, reserach
analist and develop ,requirement
specification,data collection

Shinde Sakshi
Role: Member
Task: Development coding
,implementation, Integration and
testing, installation and
acceptance,deployment

Fig 5.3.2: Team Structure

5.3.3 Tasks and Milestones

5.3.3.1 Execution of Plan in Fifth Semester (Project Planning)
T1: Problem Identification/ Problem Statement Define
T2: Project Title
T3: Industrial Survey & Literature Review
M1: Finalized Project Topic & Literature Review
T4: Requirement Gathering & Analysis
T5: Functional Requirement
T6: Hardware Requirement
T7: Software Requirement
T8: Scope Statements & Feasibility Study
T9: Project Proposal

SAMARTH POLYTECHNIC, BELHE ( COMPUTER ENGG.) Page 30

CHAPTER 5 WEB APPLICATION OF SECURE AND TRUSTED MATRIMONIAL SYSTEM

M2: Project Proposal completed

T10: Designing, Planning & Scheduling
T11: Planning
T12: Architectural Designing
T13: Modeling (DFD, UML, etc)
T14: Scheduling
M3: Execution of Plan in Fifth Semester:
Designing, Planning & Scheduling Completed
T15: Final Report Writing including Documentation
T16: Fifth semester Report writing
T17: Presentation - I
M4: Fifth Semester Final Report writing including Documentation & Presentation
Completed

5.3.3.2 Planning of Sixth Semester (Project Execution)

T18: Implementation
T19: Graphical User Interface
T20: Coding
M5: Complete Implementation of Project
T21: Project Testing
T22: Prepare Test Plan
T23: Prepare Test Cases
T24: Test Result
M6: Project Testing Completion
T25: Final Report Writing including Documentation
T26: Sixth semester Report writing
T27: Presentation - II
M7: Final Report Writing including Documentation & Presentation Completed.

SAMARTH POLYTECHNIC, BELHE ( COMPUTER ENGG.) Page 31

CHAPTER 5 WEB APPLICATION OF SECURE AND TRUSTED MATRIMONIAL SYSTEM

5.3.4 Timeline Chart

The time line chart can display into the model wise execution as:
5.3.4.1 Timeline Chart for Execution of Plan in Fifth Semester. (Project Planning)

5.3.4.2 Timeline Chart for Planning of Sixth Semester. (Project Execution)

SAMARTH POLYTECHNIC, BELHE ( COMPUTER ENGG.) Page 32

CHAPTER 5 WEB APPLICATION OF SECURE AND TRUSTED MATRIMONIAL SYSTEM

SAMARTH POLYTECHNIC, BELHE ( COMPUTER ENGG.) Page 33