Logo
Unionpedia
Communication
Get it on Google Play
New! Download Unionpedia on your Android™ device!
Free
Faster access than browser!
 

Behavior-driven development and Object-oriented analysis and design

Shortcuts: Differences, Similarities, Jaccard Similarity Coefficient, References.

Difference between Behavior-driven development and Object-oriented analysis and design

Behavior-driven development vs. Object-oriented analysis and design

In software engineering, behavior-driven development (BDD) is a software development process that emerged from test-driven development (TDD). Object-oriented analysis and design (OOAD) is a popular technical approach for analyzing and designing an application, system, or business by applying object-oriented programming, as well as using visual modeling throughout the development life cycles to foster better stakeholder communication and product quality.

Similarities between Behavior-driven development and Object-oriented analysis and design

Behavior-driven development and Object-oriented analysis and design have 4 things in common (in Unionpedia): Domain-driven design, Domain-specific language, Software development process, Use case.

Domain-driven design

Domain-driven design (DDD) is an approach to software development for complex needs by connecting the implementation to an evolving model.

Behavior-driven development and Domain-driven design · Domain-driven design and Object-oriented analysis and design · See more »

Domain-specific language

A domain-specific language (DSL) is a computer language specialized to a particular application domain.

Behavior-driven development and Domain-specific language · Domain-specific language and Object-oriented analysis and design · See more »

Software development process

In software engineering, a software development process is the process of dividing software development work into distinct phases to improve design, product management, and project management.

Behavior-driven development and Software development process · Object-oriented analysis and design and Software development process · See more »

Use case

In software and systems engineering, a use case is a list of actions or event steps typically defining the interactions between a role (known in the Unified Modeling Language as an actor) and a system to achieve a goal.

Behavior-driven development and Use case · Object-oriented analysis and design and Use case · See more »

The list above answers the following questions

Behavior-driven development and Object-oriented analysis and design Comparison

Behavior-driven development has 33 relations, while Object-oriented analysis and design has 51. As they have in common 4, the Jaccard index is 4.76% = 4 / (33 + 51).

References

This article shows the relationship between Behavior-driven development and Object-oriented analysis and design. To access each article from which the information was extracted, please visit:

Hey! We are on Facebook now! »