Mario Cardinal explains how to use agile practices to incrementally introduce non-functional requirements into the architecture in order to reduce the complexity of the solution.
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.
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.
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.
Gojko Adzic has written the book Specification by Example, explaining the set of techniques for describing the functional and behavioural aspects of a computer system in a way that they are useful to the development team (expressed ideally as executable tests), understandable by non-technical stakeholders and maintainable to remain relevant despite changing customer demands.
The line between development and architecture is tricky. Some say it's fake, that architecture is an extension of the design process undertaken by developers; others say it's a chasm that can only be crossed by lofty developers who believe you must abstract your abstractions and not worry about implementation details. There's a balance in the middle, but how do you move from one to the other?
Traditional thinking says the more critical the application, the more tightly its development must be planned, staged and controlled. The truth is, a flexible culture is stronger, safer and more robust. This talk gives practical tips for adopting an agile approach to planning, team interactions and risk management. When the culture shifts, teams achieve goals sooner and safety is greatly enhanced.
Successful architectures evolve over time to meet the needs of changing business requirements. In this talk, Luke Hohmann presents how to collaborate with key members of your business, including product management, product marketing, and product owners, to manage architectural changes that promote quality, using techniques and language that they will understand and support.
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.
