The Community for Technology Leaders
2013 21st IEEE International Requirements Engineering Conference (RE) (2012)
Chicago, IL, USA USA
Sept. 24, 2012 to Sept. 28, 2012
ISSN: 1090-750X
ISBN: 978-1-4673-2783-1
pp: 273-278
Yuri Chernak , Valley Forge Consulting, Inc., USA
Aspect-oriented requirements engineering (AORE) introduced an artifact called Requirements Composition Table (RCT). RCT presents a holistic view of an application's functionality structured by core features and crosscutting concerns. This artifact can effectively support various project tasks and serve as a common frame of reference for all parties on a project team. As AORE remains little-known to most practitioners in the software development field, the purpose of this paper is to explain the RCT concept to practitioners and discuss its benefits. The RCT technique has been implemented for a number of Wall Street applications at various investment banks. RCT can help us perform important project tasks and has proven to be one of the most valuable artifacts of a software project. This paper discusses the steps to develop an RCT, provides an example of how to use it to perform change impact analysis for releases, describes experiences using RCTs in practice, and discusses lessons learned on projects implementing the RCT technique.
change impact analysis, aspect-oriented requirements engineering, crosscutting concerns, requirements composition table
Yuri Chernak, "Requirements Composition Table explained", 2013 21st IEEE International Requirements Engineering Conference (RE), vol. 00, no. , pp. 273-278, 2012, doi:10.1109/RE.2012.6345814
81 ms
(Ver 3.3 (11022016))