Group items tagged

IIBA Lidmaatschap

Webinars, BABOK, de laatste ontwikkelingen, book reviews en vele andere voordelen

establish a methodology for evaluating software assurance tools

Source Code Security Analyzers – This class of software tools examines source code files for security weaknesses and potential vulnerabilities

Web Application Vulnerability Scanners – These tools crawl a web application’s pages and search the application for vulnerabilities by simulating attacks on it

MKS Named a Leader in Forrester’s Analysis of Agile Development Management Tools

MKS is pleased to offer you a complimentary copy of this independent research

Welkom bij het DREAM Event Atos Origin organiseert op dinsdag 9 maart 2010 voor de tweede keer het Dutch Requirements Engineering and Management event. Het event is open voor de gehele Requirements community; voor iedereen die werkt met specificaties.

Hartelijk welkom op de website van DREAM (Dutch Requirements Engineering And Management). In 2014 is al voor de 5de maal het DREAM event succesvol georganiseerd (zie hier een terugblik op de afgelopen events). We willen ook de komende jaren een bijdrage blijven leveren aan het verder verspreiden van de kennis en het begrip betreffende alles wat te maken heeft met requirements; van business rules tot en met user stories, van functioneel ontwerp tot en met modellen van bedrijfsprocessen.

The only use cases that should be left over should be cases that describe situations that are not fully covered by the BPMN.

shed some light on the difference between process maps and use cases.

different techniques and basically the result is the same

if you’re more comfortable with use cases then stick to them or if you’re more familiar with process maps then draw a map

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)

This course will teach you the very basics and foundation of BDD along with examples & workflow

You will learn and witness how BDD starts in an Organization along with a BDD Workshop

What are the different phases of BDD, BDD in Sprints and Agile Teams, BDD Roles and Responsibilities