Skip to main content

Home/ BARE+IA Requirements Engineering Information&Business Analysis/ Group items tagged wikipedia

Rss Feed Group items tagged

Peter Van der Straaten

Certified Professional for Requirements Engineering - Wikipedia, the free encyclopedia - 0 views

  • The IREB was officially founded as the International Requirements Engineering Board in Fürth (Germany) in October 2006.
Peter Van der Straaten

MKS Inc. - Wikipedia, the free encyclopedia - 0 views

  • In 2008 Forrester proclaims MKS as the leader in requirements management in the independent research report
  • MKS positioned in the 'Leaders' quadrant in Gartner's first ever Magic Quadrant for Software Change and Configuration Management (SCCM) for Distributed Platforms
  • Gartner positioned MKS as a leader in the 2009 Magic Quadrant for Software Change and Configuration Management (SCCM) for Distributed Platform
  • ...1 more annotation...
  • Forrester named MKS as a leader in Agile development management tools in Forrester Research Inc., May 2010
Peter Van der Straaten

User story - Wikipedia, the free encyclopedia - 0 views

  • Comparing with use cases
  • Kent Beck, Alistair Cockburn, Martin Fowler and others discussed this topic further on the c2.com wiki (the home of extreme programming).[16]
  • "User Story And Use Case Comparison". c2.com.
Peter Van der Straaten

Behavior-driven development - Wikipedia - 0 views

    • Peter Van der Straaten
       
      gebruikt bij EPO
  • This format is referred to as the Gherkin language, which has a syntax similar to the above example
Peter Van der Straaten

Bedrijfsobjectmodel - WILMA Wiki - 0 views

  •  
    Goede gestructureerde manier om domeinkennis vast te leggen: via semantische wiki
Peter Van der Straaten

BDD 101: Introducing BDD | Automation Panda - 0 views

  • Gherkin
  • test automation
  • The Big BDD Picture: The main goals of BDD are collaboration and automation
  • ...22 more annotations...
  • specification by example:
  •  Gherkin is one of the most popular languages for writing formal behavior specifications – it captures behaviors as “Given-When-Then” scenarios.
  • With the help of automation tools, scenarios can easily be turned into automated test cases.
  • Quick Points BDD is specification by example. When someone says “BDD”, immediately think of “Given-When-Then”. BDD focuses on behavior first. Behavior scenarios are the cornerstone of BDD. BDD is a refinement of the Agile process, not an overhaul. It formalizes acceptance criteria and test coverage. BDD is a paradigm shift. Behaviors become the team’s main focus.
  • 12 Awesome Benefits
  • Inclusion
  • Clarity
  • Streamlining
  • Artifacts
  • Shift-Left
  • Automation
  • Test­-Driven
  • Code Reuse
  • Parameterization
  • Variation
  • Momentum
  • Adaptability
  • behavior-driven development
  • Testing Recommendations
  • Since BDD focuses on actual feature behavior, behavior specs are best for higher-level, functional, black box tests. For example, BDD is great for testing APIs and web UIs.
  • Gherkin excels for acceptance testing
  • However, behavior specs would be overkill for unit tests, and it is also not a good choice for performance tests
1 - 14 of 14
Showing 20 items per page