BT
rss

Applying Use Cases in Agile: Use Case 2.0, Slicing and Laminating

by Ben Linders on  Feb 13, 2014 1

To incrementally develop and deliver products using agile software development, requirements are gathered and organized into a product backlog. A requirement technique that is used in agile software development is use cases. Some techniques to apply use cases for managing product requirements in agile are use case 2.0, slicing and laminating.

Behaviour-Driven Development: Value through Collaboration

by Jan Stenberg on  Dec 30, 2013

The goal of a software project is to deliver value to stakeholders and Behaviour-Driven Development, (BDD), is designed for that, Viktor Farcic, a software developer working on transitions from waterfall to agile processes, states in the first of four blog posts describing his view on BDD.

IRQA - A Requirements Definition and Management Solution for Systems Engineering Projects

by Michael Stal on  Jan 27, 2012 5

Visure Solutions recently announced the availability of IRQA which denotes a solution for requirements definition and management (RDM). A sound process using professional tools is important for ensuring the quality of product and solution development with respect to the requirements specification.

Jolt Award 2011 for Design, Planning, and Architecture Tools

by Michael Stal on  Nov 02, 2011

On October 26th, The Jolt Judges announced the awards for 2011 in the category “Design, Planning, and Architecture Tools”. In detail, the Jolt hall of fame now includes the products Paradigm for UML, Restructure 101, and Requirements Center 2010.

Application Lifecycle Management in Team Foundation Server 11

by Jonathan Allen on  Sep 15, 2011 1

Team Foundation Server 11 has added many features in the area of Application Lifecycle Management. Some of the highlights include support for code reviews, iterations/sprints, resource allocation, third part testing frameworks, and a much more capable dependency graph.

Proposal for Eclipse-based Requirement Modeling Framework Released

by Michael Stal on  Jul 15, 2011 1

Recently, a proposal for the Requirements Modeling Framework (RMF) has been officially released by eclipse.org. Vision is to have at least one clean-room implementation of the OMG ReqIF standard in form of an EMF model and some rudimentary tooling to edit these models.

Nailing Down Non-Functional Requirements

by Vikas Hazrati on  Jun 22, 2011 6

Non-Functional requirements are often associated with the state of the system and not with the functionality that the system has to offer. General 'ilities' of the system such as scalability, interoperability, maintainability, portability, performance and security fall under this umbrella. Agile teams usually struggle with defining and estimating the non-functional requirements in their projects.

New Books on Software Architecture

by Michael Stal on  Jun 17, 2011 4

Software Architecture is one of the important topics for software engineers, because many failures of software development projects are caused by inadequate design. Thus, it is essential to learn more about architectural issues in theory and practice. Interesting new books that have been published recently or in the near future could be very helpful

The Further Value of Collapse

by Liz Keogh on  Mar 03, 2011 1

Mike Burrows started a discussion on the Kanbandev group which has led the community to explore the Expand / Collapse pattern. The discussion was covered elsewhere on InfoQ, in an article which followed the viewpoints of many practitioners who see more value in expansion than collapse. However, many people found both aspects of the pattern useful.

The Value of Collapse?

by Dan Puckett on  Mar 01, 2011 21

Agile methods recommend decomposing ("expanding") features into many small user stories. After the code has been written, however, should we collapse these small stories back into the original feature so we can deal with them all as a unit? Are there any advantages in doing that collapse, and if so, what are they?

Do Use Cases Have a Place In Scrum?

by Dan Puckett on  Nov 15, 2010 8

In Scrum, requirements are commonly expressed as user stories. But is it OK to also make use of use cases in Scrum? And, if so, under what circumstances should you do so?

Visualize First. Build Later.

by Dave West on  Jun 28, 2010 16

A Computerworld article and webinar announcement, both featuring the use of iRise, to visually capture business application requirements calls attention to this growing product segment.

WPF vs. Silverlight: Choosing the Right Technology for a Project

by Abel Avram on  Jun 02, 2010 7

There is some confusion about when to use WPF and when to use Silverlight. Choosing the right technology for a project depends on precise requirements the application has and the differences between WPF and Silverlight’s capabilities.

Presentation: Do The Hustle

by Werner Schuster on  Aug 19, 2008 8

In this presentation at RubyFringe, Obie Fernandez shares his experience selling consulting services for both Thoughtworks and Hashrocket and gives advice on how developers/consultants can deal with clients by setting minimal requirements, saying "No" and how to choose hourly rates and much more.

Presentation: Natural Laws of Software Development - Deriving Agile Practices

by Abel Avram on  Aug 17, 2008 3

In this presentation filmed during Agile 2008, Ron Jeffries and Chet Hendrickson derive Agile practices from the natural laws of software development. They don't just say "Be Agile!", but they explain why Agile practices make perfect sense in the software development world.

General Feedback
Bugs
Advertising
Editorial
InfoQ.com and all content copyright © 2006-2013 C4Media Inc. InfoQ.com hosted at Contegix, the best ISP we've ever worked with.
Privacy policy
BT