|
P1805 Seeking participants on the 1805 Working Group. 1805 is the Standard for the Requirements Capture Language (RCL) that is getting developed from scratch. “IT Requirements," the very word means a “pack of ambition” to own a software system that enables businesses and communities in excelling/smoothening the execution of their business / community processes with the ultimate goal towards better customer/user base retention and new base build up. IT Departments of businesses and/or IT Services companies, typically, serve as host to this ambition pack and try to ensure that the ambition is executed well and the system is in place, as desired, on time and with the acceptable quality and supported thereafter. One of the biggest challenges in becoming a host, as in the context above, is that the picture in the heads of business masters needs to be clearly copied to the heads of IT people and most of us will agree that this is not easy, if, not impossible. RCL aims to bridge this gap. 5.4 Purpose: 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 "Tree Structure" based requirements capture is a 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, e.g., 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. Here is a link to the PAR: https://development.standards.ieee.org/pub/active-pars?n=7&s=1805 If you are interested, available and knowledgeable in the development of new architecture and/or ontology, we ask that you join us. We are looking for reviewers who, perhaps due to time limitations, cannot fully participate but will be able to review and comment on the draft as it is developed. The Working Group communicates via email. Please contact Working Group chair Anusheel Tandon at anusheeltandon@econcinnity.com if you wish to participate or if you have questions.
|
|