Use cases, user stories, or backlog items already define broadly the scope of a project. Many teams consider requirements as something provided by the business users, product owners or customers. Asking business users to provide the scope is effectively relying on someone who has no experience designing software solutions to give us a high level solution design. This article explains how project teams can work together with business users to come up with the right scope. To reach this goal, you need to start with business goals, and not with user stories, and derive the scope from that.
Despites its complexity, the Unified Modeling Language (UML) is still a standard for modeling software requirements. This article presents UML best practices by discussing some presented some UML modeling anti-patterns that the authors discovered in their experience as UML consultants. They then serve as a basis for discussing Unified Modeling Language best practices that could correct them.
Methods & Tools – the free magazine for software developers, testers and project managers – has just published its Spring 2011 PDF issue with the following articles:
* Automated Acceptance Tests and Requirements Traceability
* Managing Schedule Flaws using Agile Methods
* User-Centric Design and the Power of Personas
* Complexity Theory for Software Developers
* Build Patterns to Boost your Continuous Integration
* GivWenZen – Behavior Driven Development for FitNesse
* Celoxis – Web Based Project Management
* Tellurium Automated Testing Framework
* Apache CXF
* RSpec Best Practices
* Maven Plugins