We all are aware about power of SDLC to execute project with quality output. Majority companies use to follow waterfall, Agile or V-shape SDLC to manage their ongoing projects, however I suggest to my clients to design one model for their process base upon available SDLC philosophies by creating hybrid model.

Advantage of Hybrid Model of SDLC Philosophies :

– Model will suit the project size and type.
– It will match company environment for development
– Model will control the entire process base upon priority and importance.
– Suits more to client psychology as its tailor-made for his/her project.
– Easy to adopt due to flexibility of synchronization.
– Development will be smooth and quick as we follow only relevant process cycles

Points to analyze Hybrid Model :

– Analyze the project : We can start analyzing project with these points

A: Size and Technology type of project
B: Probable changes during development phase
C: Enhancement required to the scope base upon trend changes during the development span.

– Analyze the client’s philosophy towards changes during project execution:

A: Client’s vision towards project for short span future enhancement
B: Changes client suggest during the requirement gathering phase
C: Change you can suggest to client during development to compete with trend / other vendors.

Design Hybrid Model : Now base upon the analysis you can chose suitable model and design the best one:

A1: More changes and long term project + other factors
B1: More changes and mid term project + other factors
C1: More changes and short term project + other factors

A2: Average changes and long term project + other factors
B2: Average changes and mid term project + other factors
C2: Average changes and short term project + other factors

A3: Less changes and long term project + other factors
B3: Less changes and mid term project + other factors
C3: Less changes and short term project + other factors

A4: Zero changes and long term project + other factors
B4: Zero changes and mid term project + other factors
C4: Zero changes and short term project + other factors

Now base upon A1,A2,A3 and A4 you can chose or design model from List of the most popular 61 Software Development Life Cycle Model / Philosophy : You can check more about these all models in my coming posts, google or wikipedia.

A:
– Agent-oriented programming
– Agile software development
– Agile Unified Process (AUP)
– Aspect-oriented Programming
B:
– Behavior Driven Development (BDD)
– Big Design Up Front (BDUF)
– Blind Men And Elephant Approach (BMAEA)
C:
– Code and fix
– Cone of Uncertainty
– Constructionist design methodology (CDM)
– Continuous integration
– Control tables
– Cowboy coding
– Crystal Clear
D:
– Dependency injection
– Design-driven development (D3)
– Design Driven Testing (DDT)
– Domain-Driven Design (DDD)
– Don’t repeat yourself (DRY) or Duplication is Evil (DIE) or Once and Only Once (OAOO), Single Point of Truth (SPoT), Single Source Of Truth (SSOT)
– Dynamic Systems Development Method (DSDM)
E:
– Easier to Ask Forgiveness than Permission (EAFP)
– Evolutionary prototyping
– Extreme Programming (XP)
F:
– Feature Driven Development
– Free software license
G:
– Good Enough For Now (GEFN)
I:
– Inversion of control
– Iterative and incremental development
J:
– Joint application design, aka JAD or “Joint Application Development”
K:
– KISS principle original (Keep It Simple and Stupid), derogatory (Keep It Simple, Stupid!)
L:
– Lean software development
– Literate Programming
M:
– Microsoft Solutions Framework (MSF)
– Model-driven architecture (MDA)
– MoSCoW Method
O:
– Open Unified Process
Q:
– Quick-and-dirty
R:
– Rapid application development (RAD)
– Rational Unified Process (RUP)
– Release early, release often (see also The Cathedral and the Bazaar)
– Responsibility-driven design (RDD)
S:
– Scrum
– Separation of concerns (SoC)
– Service-oriented modeling
– Software Craftsmanship
– Software System Safety
– Solid (object-oriented design)
– Spiral model
– Structured Systems Analysis and Design Method (SSADM)
– SUMMIT Ascendant (now IBM Rational SUMMIT Ascendant)
T:
– Team Software Process (TSP)
– Test-driven development (TDD)
– Two Tracks Unified Process (2TUP)
U:
– Ubuntu philosophy
– Unified Process (UP)
– Unix philosophy
V:
– V-Model
W:
– Waterfall model
– Wheel and spoke model
– When it’s ready model
Y:
– You Ain’t Gonna Need It (YAGNI)

These are the key models we can use to design hybrid model of software development life cycle.

Success,

Vision Raval