Group items tagged

TDD34-8£60,000-6,064 (6.48%)1,470

BDD109-29£60,000+3.44%2,823 (3.02%)607

User Experience43+8£55,000-5,279 (5.65%)1,045

Onder meer hebben wij totaaloverzicht en verschillenanalyse van alle gangbare Requirements Management tools

Bovendien zijn wij specifiek vertegenwoordiger van Enterprise Architect.

Agile Software Development21+4£45,000-10114 (8.23 %)

Scrum35+10£47,500-6778 (5.51 %)

Mega has a clear identification and understanding of stakeholder expectations across the entire organization

Web-based integrated platform that includes EA, GRC, and application portfolio management, and delivers an integrated set of solutions that deliver operational excellence for organizations facing complex integration issues with business and technology

Mega consistently integrates industry best practices in many aspects of its product offering. One example is the Object Management Group's Meta Object Facility (OMG MoF 2)-compliant repository

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.

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)