The Bridge process model is the modern process Model which has becoming a trend in the Process of Software Development.

2. Introduction
 Computers run with special purpose application
software that are being used as an extensive aid to
solve complex problems.
 Developing such complex software is not easy
task.
 A software process model is a description of the
sequence of activities carried out in an Software
Engineering project, and the relative order of these
activities.

3. Software Process Models

4. Characteristics of Good Software
Process Model
 The project goal reflection.
 Predictability.
 Support testability and maintainability.
 Support change.
 Early Defect Removal.
 Process improvement and feedback.
 Quantitative progress measurements.
 Support of process tailoring.

5. BRIDGE: The Proposed Model for
Modern Software Development Process
 After analysing the importance of all the recent
software development trends, the BRIDGE
process model is developed.
 Unlike the other process models, the BRIDGE
model consists of several phases with
distinguished objectives.
 There are 13 phases in all.

7. 1. Requirement
Requirement Analysis, Verification and
Specification.
 The objective of this phase is to identify the
exact requirements from the client using
different techniques.
 The gathered requirements are then analysed
by the Analyst who extracts the requirements
from the client
 The verified requirements are to be specified in
a document called Software Requirements
Specification (SRS)

8. 2. Feasibility & Risk
Feasibility Analysis, Risk Analysis, Verification
and Specification
 The objective of this phase is to analyze the
suitability of the project in respect to different
project attributes
 Beside feasibility analysis, the different
project risks also has to be identified,
analyzed and specified in the risk
specification document.

9. 3. Architecture
Software Architecture Design, Verification and
Specification
 The objective of software architecture design is
to identify the subsystems, building blocks or the
components of the system
 It should reflect the requirements specified in the
SRS document.
 The verified software architecture design is
specified in a software architecture design
document (SADD).

10. 4. Design
Detailed Software Design, Verification and
Specification
 In this phase, the detailed design of the system
has to be prepared conforming the software
architecture designed during the last phase.
 The verified software design is specified in a
document named as software design document
(SDD) that will be used in the other development
activities later.

11. 5. Patterns & Component
Patterns Identification, Component Search,
Verification and Specification
 The objective of this phase is to identify the
patterns (some components common in different
projects) and then it must be searched in the
component library to find a suitable component
match.
 The verified component is specified in a
document called component specification
document (CSD) for future use.

12. 6. Coding
Standard Coding, Unit Testing, Verification
and Specification
 The objective of this phase is to write
program code for the unmatched
components.
 These newly developed components must be
tested thoroughly to be used in several
systems at different times. Such testing is
called unit or component testing.

13. 7. Building
Component Integration, System Testing,
Verification and Specification
 The individual components are gathered &
integrated to build the whole system by the
bottom up approach & tested thoroughly.
 The corresponding test report is prepared for
use during system validation and
maintenance activities

14. 8.Validation
System Validation, Verification and
Specification
 The objective of this phase is to check
whether all the functional requirements
specified in the SRS document are in the
system or not .
 There must be relation between the
functions in the SRS document and function
supported by the system. Performing this
activity is called system validation.

15. 9. Deployment
System Deployment, Implementation and
Specification
 The time to deliver the system to the client
and implement the system at client site.
 The user must understand and feel
comfortable to use. So, the objective of this
phase is to deliver, implement the system at
client’s work-site and train the users, if
necessary.

16. 10. On Site Testing
On Site System Testing Verification, and
Specification
 The objective of this phase is to check the
system performance at work-site.
 Although, system testing is completed prior
to system implementation, but due to some
reasons, the system may not function
correctly at the work-site.

17. 11. Maintenance
System Maintenance, Verification and
Specification
 The objective of this phase is to provide the
post delivery services to the system for its
desirable functioning.
 Software Maintenance denotes any changes
made to a software product after it has been
delivered to the client.

18. 12. Configuration Management
 The means by which the process of software
development and maintenance is controlled
is called configuration management
 The objective of this phase is the
development of procedures and standards
for cost effective managing and controlling
the changes in the evolving software.

19. 13. Project Management
 The project management activity is carried
out in parallel with all the other software
development phases as described earlier.
 The objective of this phase is to perform the
project management activities including
project planning, monitoring, controlling,
directing, motivating and coordinating.

20. Limitations of the BRIDGE Model
 Abstracts the different techniques to be used
in different phases.
 Required to be validated by industrial
practice.
 It doesn’t consider professionals skill level.
 The BRIDGE model seems to be complex.

21. Conclusion
 BRIDGE model can be followed for any
software project development.
 Most of the software crisis can be overcome
up to great extent, delivering the fully
functional system with better quality within
time and budget achieving the true goal of
any software project development.