Well Structured Requirements Knowledge: the Foundation for Reuse |
 |
|
Date: Thursday, October 30, 2008 Software development organizations today are looking for new ways to create efficiencies and discover new ideas as they attempt to stay ahead of the competition. The ability to reuse work frees resources to make early, innovative improvements and implement them quickly. Reuse has traditionally been a concept reserved for code and software components largely because code is often the first consistently recognisable element of knowledge. However, organizations who can recognise other existing elements of knowledge - like requirements - can reap the benefits of reuse early in the development lifecycle. This realization identifies a need to be able to make requirements knowledge consistent and hence reusable. Join Suzanne Robertson, originator of the Volere requirements techniques and a founder of The Atlantic Systems Guild, for a lesson in how a well-defined requirements knowledge structure is key to implementing a requirements reuse strategy. Suzanne will outline a structure for building traceable connections between high-level business or domain requirements, atomic requirements and all the levels in between like systems analysis models/deliverables, design models/components, code and testing, thus laying the foundation for reuse. The resulting requirements knowledge model is a framework that you can use to manage requirements knowledge regardless of modelling notation, methodology, degree of agility, or tool usage. Doug Akers, Director of Product Management for MKS, will illustrate the advantages of strategic reuse through automated lifecycle traceability with MKS Integrity for Requirements Management - a solution designed specifically to enable easy reuse of requirements and deliver rapid results than can be easily sustained.
Key items in this presentation:
Set as favorite
Bookmark
Email this
Hits: 2144 Trackback(0)Comments (0)
|
TrackBack URI for this entry
Subscribe to this comment's feed