Group items tagged

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

Advantages & Disadvantages of ArchiMate®

One advantage of ArchiMate® is that it enables the visualization of architectures on separate layers but also allows the depiction of cross-layer relationships

Additionally, ArchiMate® provides extensive list of enterprise architecture entities, a predefined meta-model, some simplified standard views and publicly available, comprehensive documentation. Also, tool support for modeling the enterprise architecture using this architecture description language is available

SAMATE Links

DISTRIBUTEUR RAVENFLOW

De Ravenflow product portfolio richt zich op  VISUELE ondersteuning bij het opstellen van REQUIREMENTS

Engelse taalelementen worden herkend en in een activiteitenflow  gemodelleerd en gevisualiseerd.   Gebruikers , Business analisten en requirements engineers worden onmiddelllijk (real time) geattendeerd op (mogelijk) ontbrekende requirements f ontbrekende of verkeerde procesflow.

Automating Requirements Management

Software Development, July 1999

In my experience use cases are very powerful tools - their purpose is show the view from a *user's point of view*. The presented example is already very technical, and specifies a lot of details.

May I offer alternatives to the example in the article?A) A few brief classic requirements (for business) & a diagram (BPMN or UML activity diagram) (for the engineers)B) A use case with a lot less details (maybe 4-8 steps) & user interface design & a list of business rules (describing the essence of the details)C) No use case. One single sentence describing the goal & rationale ("As a user I want to have a recovery method when I forget the password because ....") & brief description of the important parts, business rules (no flow details!) & user interface design

May I offer other improvements to the "classic" use case in the example?- Instead of a summary, formulate it as a goal (remove redundancy)- Adding how frequently this is done ("Frequency: seldom, max. once per month ... once every few years")- Keep the main flow under 10 points- Remove pre-conditions and post-conditions. Keep it simple.- Integrate the alternative flows into the main flow (if possible, leave away details)

Gherkin

test automation

The Big BDD Picture: The main goals of BDD are collaboration and automation