The purpose of this guide is to: - Define a new language, RCL, for the IT Requirements capture. - Enable auto sizing of requirements after the capture is over using Function Point sizing technique. - Show that the "e;Tree Structure"e; based requirements capture is better fit for the purpose of IT requirements capture as it is closer to how the world is structured around us and hence the need for a new language. - Standardize the Tree Structure such that it is Function Point compliant, meaning, it should be possible to apply Function Point technique on the Tree elements when the requirements capture is over. - Enable the capture of Functional as well as Non Functional Requirements within the language structure. - Enable system dynamics capture as Events and Logic elements within the tree itself. - Enable swift impact analysis and hence quick and correct decision making. - Enable versioning of requirements as the capture progresses as a tree structure itself. - Enable translation of RCL to other standards such as UML diagrams. - Ensure that the requirements tree structure is future proofed in a way such that it could be easily enhanced later to include the capture of requirements within a full enterprise (non IT as well as IT requirements). In future, the language is intended to be enhanced to be able to capture right from the business motivation, business opportunities and threats, decisions, premise view, people hierarchies, IT systems (current scope), manual processes, events and all other requirements that may possibly arise within an enterprise.This guide applies to all scenarios where: - IT requirements need to be captured for creating or maintaining a software based system. - Swift, smooth, complete and clear business perspective transfer is needed between business groups and IT departments and / or IT Services companies. - IT requirements need to be automatically sized after requirements capture is over, using Function Points sizing technique, thus, enabling agility in sizing and estimation processes at the start of the lifecycle.
Sponsor: C/S2ESC - Software & Systems Engineering Standards Committee
Get Involved In The Development Of This Standard
Contact the IEEE-SA Liaison Simply click here to voice your interest. Malia Zaman Learn More About Standards ParticipationAnyone can participate, there are a variety of programs and services to
facilitate the involvement of industry and the public. More Become a Member and Ballot on this StandardMembership empowers you to participate & lead in the development of
standards. Tell Me More