%0 Conference Paper %1 greenspan94 %A Greenspan, Sol %A Mylopoulos, John %A Borgida, Alex %B International conference on Software engineering %C Los Alamitos, CA, USA %D 1994 %I IEEE Computer Society Press %K seminal formal model requirements %P 135--147 %T On formal requirements modeling languages: RML revisited %U http://portal.acm.org/citation.cfm?id=257734.257754 %X Research issues related to requirements modeling are introduced and discussed through a review of the requirements modeling language RML, its peers and its successors from the time it was first proposed at the Sixth International Conference on Software Engineering (ICSE-6) to the presen~en ICSES later. We note that the central theme of “Capturing More World Knowledge� in the original RML proposal is becoming increasingly important in Requirements Engineering. The paper highlights key ideas and research issues that have driven RAIL and its peers, evaluates them retrospectively in the context of experience and more recent developments, and points out significant remaining problems and directions for requirements modeling research. %@ 081865855X

@inproceedings{greenspan94, abstract = {Research issues related to requirements modeling are introduced and discussed through a review of the requirements modeling language RML, its peers and its successors from the time it was first proposed at the Sixth International Conference on Software Engineering (ICSE-6) to the presen~en ICSES later. We note that the central theme of “Capturing More World Knowledge� in the original RML proposal is becoming increasingly important in Requirements Engineering. The paper highlights key ideas and research issues that have driven RAIL and its peers, evaluates them retrospectively in the context of experience and more recent developments, and points out significant remaining problems and directions for requirements modeling research.}, added-at = {2006-09-18T06:26:07.000+0200}, address = {Los Alamitos, CA, USA}, author = {Greenspan, Sol and Mylopoulos, John and Borgida, Alex}, biburl = {https://www.bibsonomy.org/bibtex/23d2d5160285806fd1a08b1e902047297/neilernst}, booktitle = {International conference on Software engineering}, citeulike-article-id = {679723}, comment = {- specification is prescriptive? - debate about extent to which conceptual models are indicative mood or optative mood (the way it should be). How to distinguish this? - "An explicit model is also of use in supporting continuity in the face of inevitable staff turnover and other organizational change" p. 136 any evidence for this? - is modeling req a superset of making a specification? - differentiates btw KR and CM by saying that CM is that CM has a specific interest in abstraction and large-scale models. (clearly these 2 are merging). - advantage of formal logic is that it presents one interpretation, and that reasoning, i.e. consistency checks, question answering, and simulation. - "The representation of time is essential for languages intended to model dynamic applications, if one is to prevent an implementation bias toward imperative programming style. RML assumes a linear, dense model of time points and encourages history-oriented modeling of an application, which consists of describing possible histories for an entity or activity (or assertion, for that matter). Accordingly, there is a time argument in every predicate appearing in an RML assertion. Moreover time "objects" corresponding to time intervals are constructed as specializations of RML classes." p. 138 - one problem was its restriction to modeling only entities, activities, and assertions, so they moved to TELOS with complex meta model structure. - mentions that ERAE used temporal logic operators to represent temporal information, which seem less verbose than TELOS. -}, description = {Not previously uploaded}, interhash = {e6df2d59cbee001b6021559c7c4d3c2b}, intrahash = {3d2d5160285806fd1a08b1e902047297}, isbn = {081865855X}, keywords = {seminal formal model requirements}, pages = {135--147}, priority = {0}, publisher = {IEEE Computer Society Press}, timestamp = {2006-09-18T06:26:07.000+0200}, title = {On formal requirements modeling languages: RML revisited}, url = {http://portal.acm.org/citation.cfm?id=257734.257754}, year = 1994 }