E. Dubois, E. Yu, and M. Petit. From early to late formal requirements: A process-control case study. In 9th International Workshop on Software Specification and Design, pages 34--42, Ise-Shima (Isobe), Japan, April 16-18 1998. IEEE Computer Society Press.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....investigating the concepts related to agile methods, we may also consider some research topics that have a positive impact on development time. 6.1. 1 Domain and organisational models Organisational models have been used as software analysis devices, to build models of the system being developed [10]. Their use in system development should help the acquisition and analysis of the domain, environmental, social, and other organisational related requirements. This requires an effort that may not be appropriate for situations where time tomarket is the prominent requirement. I believe that the ....

E. Dubois, E. Yu, and M. Petit. From early to late formal requirements: A process-control case study. In 9th International Workshop on Software Specification and Design, pages 34--42, Ise-Shima (Isobe), Japan, April 16-18 1998. IEEE Computer Society Press.

.... into one single goal model (see Section 3) Last but not least, goals drive the identification of requirements to support them; they have been shown to be among the basic driving forces, together with scenarios, for a systematic requirements elaboration process [Din91, Rub92, Din93, Ant98, Dub98, Kai00, Lam00c] We will come back to this in Sections 5 and 6. Where are goals coming from Goal identification is not necessarily an easy task [Lam95, Ant98, Hau98, Ro198] Sometimes they are explicitly stated by stakehokders or in preliminary material available to requirements engineers. ....

....approaches is that they are inherently top down; this is by no means the case as it should hopefully be clear now from the discussion above. When shotfid goals be made explicit It is generally argued that goal models are built during the early phases of the RE process [Dar93, Yu97, Dub98] The basis for the argument is the driving role played by goals in that process; the soonest a goal is identified and validated, the best. This does not imply any sort of waterfall like requirements elaboration process, however. As requirements implement goals much the same way as programs ....

E. Dubois, E. Yu and M. Petit, "From Early to Late Formal Requirements: A Process-Control Case Study", Proc. 1WSSD'98 - 9th International Workshop on Software Specification and Design, Isobe, IEEE CS Press, April 1998, 34-42.

....fine grained representation of properties in a conceptual model is not a topic of this paper as well. For this, we rely on other research and, in particular, to what is reported in [7] More specifically, if the target model is to be written using the Albert II language (see Sect. 4. 1) we refer to [9]. The requirements engineering process however, is not as streamlined as described so far. Rather, during elicitation the requirements engineering team has, for example, the desire to animate parts of the current state model to check and improve the accuracy of the abstractions. During ....

Eric Dubois, Eric Yu, Michael Petit. From Early to Late Formal Requirements: a Process-Control Case Study. In Proc. of IWSSD9, Isobe, Japan. April 1998. An Integration of Scenario-Based Requirements Elicitation and Validation Techniques Haumer, Heymans, Pohl -- 15 --

....is at a very abstract level without the influence of users or domain experts. On the other hand, when using the elicitation technique described in 2 How goal operationalisation actually takes place is not a topic of the paper. For this, we rely on other research and, in particular, on [6] and [8]. Sect. 2.1 to involve stakeholders, communicate is limited to the captured scenes of the existing system. Solution. The animator simulates usage situation of either the existing or the desired system. Interrelating goals with their operationalisations in the specification enables stakeholders ....

....real world scenes. They also have no formal semantics and no conflict modelling. Nis ##### # # ### ## # # # # # # # # # # sen et al. 24] provide an approach for cooperation modelling and scenarios including conflicts, but provide only informal representation for the scenarios. Dubois and Yu [8] support formal specifications and goals of the past and the future, but do not consider scenarios. Potts and Anton [1] 28] integrate scenarios and goals of the past for managing the evolution and surfacing requirements for the future system, but only in a static manner and do not capture scenes ....

E. Dubois, E. Yu, M. Petit, "From Early to Late Formal Requirements: A Process-Control Case Study", Proc. of IWSSD9, Isobe, Japan. April 1998.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC