P. Harmon and M. Watson. Understanding UML. Morgan Kaufmann, Palo Alto, CA, 1998. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
Design of Collaborative Information Agents - Jonker, Klusch, Treur (2000) (2 citations) (Correct)
....representations can be used to express the same requirement or scenario, varying from informal to formal. Representations can be made, for example, in a graphical representation language, or a natural language, or in combinations of these languages, as is done in UML s use cases (cf. 18] [21]) Scenarios, for instance, can be represented using a format that supports branching points in the process, or in a language that only takes linear structures into account. user environment system Fig. 1. Overall system requirement 2.1 Requirements for the overall system At the most abstract ....
Harmon, P., and Watson, M., Understanding UML, the Developer's Guide. Morgan Kaufmann Publishers, San Francisco, 1998.
Specification of Behavioural Requirements within.. - Herlea, Jonker.. (1999) (2 citations) (Correct)
....Representations Different informal representations can be used to express the same requirement or scenario. Representations can be made, for example, in a graphical representation language, or a natural language, or in combinations of these languages, as is done in UML s use cases (cf. 12] [15]) Scenarios, for instance, can be represented using a format that supports branching points in the process, or in a language that only takes linear structures into account. For the example application, first a list of nine, rather imprecisely formulated initial requirements was elicited. As an ....
....cases are informal, and activity diagrams seem too design specific and cannot express the necessary more complex temporal dependencies relevant to both requirements and scenarios. In the development of UML different representations of behavioural requirements and scenarios was not an issue [12] [15]. In [7] 8] an approach is presented in which more complex behavioural properties can be specified. A difference to our work is that no compositionality is exploited in requirements specification and verification. In recent research in knowledge engineering, identification and formalisation of ....
Harmon, P., and Watson, M., Understanding UML, the Developer's Guide. Morgan Kaufmann Publishers, San Francisco, 1998.
An Object Based Algebra for Specifying a Fault Tolerant.. - Dragoni, Gaspari (2003) (Correct)
No context found.
P. Harmon and M. Watson. Understanding UML. Morgan Kaufmann, Palo Alto, CA, 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