|
IEEE P1805 - RCL (Requirements Capture Language)
Working Group
This Working Group is responsible for developing RCL
as a new language with the following under its scope and purpose.
Scope
It applies to 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.
Purpose
·
Enable auto
sizing of requirements after the capture is over using Function Point
sizing technique.
·
Show that the
"Tree Structure" 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.
Project PAR can be accessed here.
Current WG Chair can be contacted here.
Joining the group
If you are interested to join in the effort, please
send an email to the current WG Chair with the following information
·
Address Details
as per the heads below
a) Address Line 1
b) Address Line 2
c) City
d) State
e) Zip
f) Country
g) Phone
h) Fax
·
Your current
company name
·
Your role in
your current company
·
Your LinkedIn profile (if you have created it).
·
Skype ID - Kick off
meeting and all other meetings will happen over internet via Skype text or voice chat sessions (mostly on the
weekends (estimated frequency is once every 2 to 3 months)). It is
mandatory to create an Skype
account. It is free and quite easy to use. If there is a reason why this
may not be a preferred way at your end, please state your preferences for
the communication and how you would like to participate in the
meetings. Skype ID will always be
public information for the entire group.
·
Would you like
to share your email address within the group? (Y/N)
·
Would you like
to share your phone and Fax #s within the group? (Y/N)
·
Would you like
to share your address with the group? (Y/N)
·
If you would
like to be updated on IEEE Standard Development Information? (Y/N)
Working Group Procedures
Existing group members can access the most current
version of the working group procedure document here.
Public version is present here.
|
