Site Sponsor
Go WordPress
Site Sponsor
Best modeling notation for Requirements Engineering – Competition at RE’09
There IS a huge NUMBER OF different notations/approaches FOR modeling stakeholders’ requirements such as: plain text specifications, structured text templates, goal-oriented requirement approaches (e.g. using the i* notation ), User Requirements Notation or the UML.
That’s the reason why IN the NEXT Requirements Engineering conference , Orlena Gotel AND Jane Huang have planned a competition WHERE “Teams of modelers will
be challenged to illustrate the power and
flexibility of their favorite approach for
requirements modeling, while conference
participants will act as the ultimate judges as
they vote approaches off the panel
round-by-round” . ALL teams will be given the same initial problem description AND asked TO express their understanding OF the problem USING their modeling approach.
Of course, nobody expects TO “leave the arena” WITH a clear winner notation (AS I always say there IS NO best notation IN general, notation must be chosen considering the complexity OF the problem AND the SIZE AND skills OF the development team among several other factors) but I think this IS a very interesting a proposal that AT least should shed SOME light ON the strengths AND limitations OF the different notations.
If you enjoyed this post you can subscribe TO this Software Modeling blog AND/OR follow me ON twitter OR through the portal’s mailing list . And if you really liked it help me pass it on to others by bookmarking and sharing the post using the links below:
What were the results? (Greg W.)