A. Finkelstein and H. Fuks, Multiparty Specification, Proc. 5th Intl. Wkshop, Softw. Spec. and Design, p. 185-195, ACM SIGSOFT 1989.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....in their currently used methods both in an economic and a cognitive sense that they are reluctant to give up. Recently multiple viewed approaches have been proposed, such as Software Through Pictures [10] DARWIN [11] the Composite Specification Method [12] and the multiparty approach [13]. Their main drawback is the lack of a formal basis from which to automatically analyze the resulting multiple viewed requirements. This work attempts to overcome that lack in existing methods, while still supporting their use. Existing methods have inherent limitations. Software Through Pictures ....

....that multiple views increase understanding of software requirements. There are, however, no formal methods given for transforming between views or for combining views. Also, the three viewpoints are pre determined; no additional viewpoints are easily included. The multiparty specification method [13] presents a formal model of the dialogue between viewpoints. Although its motivation is similar to this work s, its authors acknowledge that the knowledge in each viewpoint is not yet formally represented. This paper presents a general framework for capturing knowledge in several requirements ....

[Article contains additional citation context not shown here]

A. Finkelstein and H. Fuks, Multiparty Specification, Proc. 5th Intl. Wkshop, Softw. Spec. and Design, p. 185-195, ACM SIGSOFT 1989.

.... [15] Because dialogues conducted according to these games are rule governed, they have been of particular interest to computer scientists, for modeling human computer interaction [7] for modeling complex reasoning, such as that in legal domains [24] and for the task of software specification [10]. Recently, dialogue game formalisms have been proposed as protocols for interaction between autonomous software agents. In this domain, such protocols have been proposed for agent dialogues involving: persuasion [1, 8, 9] joint inquiry [18] negotiations over the division of scarce resources [4, ....

A. Finkelstein and H. Fuks. Multi-party specification. In Proceedings of the Fifth International Workshop on Software Specification and Design, Pittsburgh, PA, USA, 1989. ACM Sigsoft Engineering Notes.

.... to understand fallacious arguments [27, 41] and to provide a game theoretic semantics for formal logical systems [38] Over the last decade they have been applied in various areas of computer science and artificial intelligence: for the specification of software systems with multiple stakeholders [16]; for the design of man machine interfaces [8, 30] for the analysis of complex human reasoning [54] and for the design of interaction protocols for autonomous software agents [4, 12, 42] A dialogue game may be specified by listing the legal locutions, together with the rules which govern ....

A. Finkelstein and H. Fuks. Multi-party specification. In Proceedings of the Fifth International Workshop on Software Specification and Design, Pittsburgh, PA, USA, 1989. ACM Sigsoft Engineering Notes.

.... [24, 56, 57, 77] However, even with these modifications, approaches based on classical decision theory will still assume that utilities of different outcomes are comparable and may Dialogue games have also been applied to problems in legal reasoning [8, 59] in software specification [20] and in automated software design [68] These are instances of a Game Theoretic semantics in the sense of Jaako Hintikka [35] be partially ordered [25] As our discussion in the section above made clear, these assumptions are not necessarily appropriate in the domain of risk regulation. ....

A. Finkelstein and H. Fuks. Multi-party specification. In Proceedings of the Fifth International Workshop on Software Specification and Design, Pittsburgh, PA, USA, 1989. ACM Sigsoft Engineering Notes.

.... [14] Because dialogues conducted according to these games are rulegoverned, they have been of particular interest to computer scientists, for modeling human computer interaction [6] for modeling complex reasoning, such as that in legal domains [21] and for the task of software specification [9]. Recently, dialogue game formalisms have been proposed as protocols for interaction between autonomous software agents. In this domain, such protocols have been proposed for agent dialogues involving: persuasion [1, 7, 8] joint inquiry [17] negotiations over the division of scarce resources [4, ....

A. Finkelstein and H. Fuks. Multi-party specification. In Proceedings of the Fifth International Workshop on Software Specification and Design, Pittsburgh, PA, USA, 1989. ACM Sigsoft Engineering Notes.

....reasoning [20, 28] and as a gametheoretic semantics for intuitionistic, classical [27] and quantum [37] logic. Within Artificial Intelligence they have been applied to: modeling complex reasoning, e.g. in legal domains [6] human computer interaction [5] designing software development processes [12]; and for the design of computational protocols for autonomous agent interactions. Examples of dialogue game agent protocols include systems for: teamformation [9] information seeking dialogues, where one agent seeks the answer to a question from others believed to know it [23] persuasion ....

A. Finkelstein and H. Fuks. Multi-party specification. In Proc. 5th Intern. Workshop on Software Specification and Design, Pittsburgh, PA, USA, 1989. ACM Sigsoft Engineering Notes.

....the creation of a good requirements specification. 5.5. 1 Multi party Specification In the multi party specification approach the requirements associated with each different perspective in the real world are represented by a computer based agent as a set of requirements in a logic [Finkelstein 1989]. An automated dialogue is allowed to take place between 20 the software agents currently the research has been confined to two agents. The dialogue consists of assertions about requirements, questions about assertions, withdrawals of assertions, denials of assertions, explanations of chains of ....

FINKELSTEIN, A. 1989. Multi-party Specification. In Proceedings of the 5th International Workshop on Software Specification and Design, IEEE, Pittsburgh, pp 185 - 195.

....features of the actual interface; a poor mismatch here is also indicative of a flowed interface design. 6 Relations with work in HCI There are similarities between the games metaphor described here and the earlier proposals of, amongst others, Bench Capon et al. [24, 25] and Finkelstein and Fuks [5] to base interface construction on dialogue games . The similarity is that these proposals also view interaction as a form of rule governed activity. The difference is that those proposals place no emphasis on compound games and coordination of moves in sub games. It is also not clear to us ....

Finkelstein A. and Fuks Y. Multi--party Specification. In Proceedings of the 5th International Workshop on Software Specification and Design. ACM Sigart, 1989.

....representation of viewpoint analysis of a system 3 Viewpoint Analysis 3.1 Description of Viewpoint Analysis In order to identify all aspects of a system, the system will need to be considered from multiple viewpoints. This is shown (using a graphical analogy) in figure 2. Viewpoint analysis [5] recognises that at every decomposition step in analysing a system, the system can be viewed from different viewpoints. Typical viewpoints for a computer system might be the users of the system, other computer systems interfacing to the system, constraints placed on the system, the designers of ....

....etc. Typically there will exist two main types of viewpoint; user viewpoints and methodological viewpoints. The first step in traditional viewpoint analysis is to identify the possible viewpoint of the system. This is often represented using a viewpoint bubble diagram or viewpoint hierarchy [5, 4]. This is essentially simply a collection of viewpoint names. No structure is imposed on the analysis or representation of the viewpoints at this stage. It is important however to recognise all possible viewpoints, as their may be aspects of the system which are only identifiable from a single or ....

A. Finklestein and S. Fuks, "Multi-party specification, " in Proceedings of the 5th International Workshop on Software Specification and Design: Pittsburgh, PA, pp. 185--195, 1989.

....by analysts. It is unlikely that the full range of these skills can be automated. 2.3.1 Framework Rather than a rigid formal process, the analyst needs a framework which can guide his or her expertise. This framework must support the creative input and interpretive skills of the analyst. Finkelstein Fuks [1989] suggest that such a framework be: flexible; empirical (in that the model maps onto the results of observational studies) enactable; co operative; and that it should be able to handle conflict. However, in order to facilitate some automation, a degree of structuring must be introduced. An ....

....a person may have several areas of concern) and also for one viewpoint to represent several people (where people share an area of concern) The notion of viewpoint provides a useful context in which to study conflict. As Robbins [1974] points out, many conflicts are communicational in nature. Finkelstein Fuks [1989] use the viewpoint as a basis for a study of some of the communicational problems surrounding conflict. They describe a formal model of dialogue between two agents, which allows agents to share knowledge and detect inconsistencies between their knowledge. The dialogue takes the form of a game, in ....

[Article contains additional citation context not shown here]

Finkelstein, A. C. W., and Fuks H., 1989, "Multi-Party Specification", Proceedings, Fifth IEEE International Workshop on Software Specification and Design, pp185-195.

....the specification developed, and its current status. This model abstracts away from the people involved, allowing one person to have several viewpoints (as a person may have several areas of concern) and also for one viewpoint to represent several people (where people share an area of concern) Finkelstein Fuks [1989] use the viewpoint as a basis for a study of some of the communicational problems surrounding conflict. They describe a formal model of dialogue between two agents, which allows agents to share knowledge and detect inconsistencies between their knowledge. The dialogue consists of speech acts, such ....

....arguing over trivial details can be counter productive, and so a balance must be struck between encouraging communication and devoting appropriate amounts of effort to resolution of particular differences. 3.1.1. Specification Context We use a notion similar to the viewpoints proposed by Finkelstein et al. 1989] as a basis for our model of the specification process. Viewpoints allow the expression of conflict by providing alternative descriptions, while individually, each viewpoint remains consistent. Because viewpoints do not correspond to people, conflicts between a single person s roles can be ....

Finkelstein, A. C. W., and Fuks H. (1989) Multi-Party Specification, Proceedings, Fifth IEEE International Workshop on Software Specification and Design, pp185-195.

....than the syntax of notations would be more effective. For even more general semantics, domain models are needed, in conjunction with method models to provide guidance. These points of view are supported by the later work in the same group on TARA [Fin88] and then on IC DC and its successors [FF89] FKG90] In the latter a requirements specification is developed as a tool supported dialogue between viewpoints, in which the viewpoints negotiate to establish commitments and responsibilities. This method is supported by monitoring for illegality in dialogues, with dialogues explained and ....

A. Finkelstein and H. Fuks. Multi-party specification. In Proceedings of the Fifth International Workshop on Software Specification and Design. IEEE Computer Society Press, 1989.

....by analysts. It is unlikely that the full range of these skills can be automated. 5.1. Framework Rather than a rigid formal process, the analyst needs a framework which can guide his or her expertise. This framework must support the creative input and interpretative skills of the analyst. Finkelstein Fuks (1989) suggest that such a framework should be: flexible; empirical (in that the model maps onto the results of observational studies) enactable; cooperative; and that it should be able to handle conflict. However, in order to facilitate management of the process and provide a support environment, a ....

Finkelstein, A. C. W., & H., F. (1989). Multi-Party Specification. In Proceedings, Fifth IEEE International Workshop on Software Specification and Design, (pp. 185-195).

....specification as natural language comments or links in hyperdocuments. see eg 7] It is also the case that descriptive textual and graphical material greatly assists human understanding, not least when it provides an alternative viewpoint on a formal specification as advocated by Finkelstein [6]. Textual material from the early phases of a project, when suitably tagged and indexed, can provide the background information and contextual clues that a human developer or maintainer requires so as to understand the design goals and decisions implicit in the finished system [14] 5. NLP in ....

A Finkelstein, "Multi-party Specifications", Proceedings of 5th International Workshop on Software Specification and Design", IEEE Pittsburg.

....in their currently used methods both in an economic and a cognitive sense that they are reluctant to give up. Recently multiple viewed approaches have been proposed, such as Software Through Pictures [10] DARWIN [11] the Composite Specification Method [12] and the multiparty approach [13]. Their main drawback is the lack of a formal basis from which to automatically analyze the resulting multiple viewed requirements. This work attempts to overcome that lack in existing methods, while still supporting their use. Existing methods have inherent limitations. Software Through Pictures ....

....that multiple views increase understanding of software requirements. There are, however, no formal methods given for transforming between views or for combining views. Also, the three viewpoints are pre determined; no additional viewpoints are easily included. The multiparty specification method [13] presents a formal model of the dialogue between viewpoints. Although its motivation is similar to this work s, its authors acknowledge that the knowledge in each viewpoint is not yet formally represented. This paper presents a general framework for capturing knowledge in several requirements ....

[Article contains additional citation context not shown here]

A. Finkelstein and H. Fuks, Multiparty Specification, Proc. 5th Intl. Wkshop, Softw. Spec. and Design, p. 185-195, ACM SIGSOFT 1989.

....managers and for ways of hierarchically structuring an interaction protocol. In particular the provision for structured specification has to be made (see definition of macros in [19] By using production rules the possibility of deriving commitments or abstracting plans should be easy to add [21]. Interactions based on abstraction of plans are investigated in feature interaction within intelligent telecommunication systems [22, 23] July 27, 1995 12 Conclusions The specification of an interaction protocol involving human agents must make provision for non determinism and allow high ....

A. Finkelstein and H. Fuks, "Multi-party Specification," presented at Fifth International Workshop on Software Specification and Design, Pittsburg,Pennsylvania, USA, 1989.

....resolving inconsistencies, merging redundant information, propagating changes, etc. Viewpoint capture has been advocated since the early days of requirements engineering [Ros77] Preliminary proposals for viewpoint oriented acquisition, negotiation, and cooperative modelling appeared only later [Fin89], Rob89] Pot94] Boe95] Two kinds of approaches have emerged. In a multi paradigm approach, specifications in different viewpoints can be written in different notations. Multi paradigm viewpoints are analyzed in a centralized or distributed way. Centralized viewpoints are translated into ....

A. Finkelstein and H. Fuks, "Multi-party Specification", Proceedings 5th International Workshop on Software Specification and Design (Pittsburgh, Pa.), IEEE, May 1989, 185-195.

.... recognized [Fic88] For example, requirements clich s available in domain specific libraries can be instantiated and or specialized [Reu91] Preliminary models for acquisition dialogues to support multiple viewpoints, negotiation and cooperative elaboration of requirements have also been proposed [Fin89], Rob90] In this context, we view requirements analysis as being made of two co ordinated tasks, requirements acquisition and formal specification. In requirements acquisition a preliminary model for the specification of the entire composite system is elaborated and expressed in a rich ....

A. Finkelstein and H. Fuks, "Multi-party Specification", Proceedings 5th International Workshop on Software Specification and Design (Pittsburgh, Pa.), IEEE, May 1989, 185-195.

....sund7 representation schemes, use a variety of development strategies and hold diverse domain knowledge. We have also proposed an object based framework deploying ViewPoints within which the above problems may be tackled [15] Issues relating to conflict resolution [10] negotiation and dialogue [14], configuration programming [24] and tool support [20, 21, 34] have already been examined within this framework. The term viewpoint has been defined and deployed in a variety of settings in software engineering, particularly in the domain of requirements engineering; e.g. 23] 25] 31] and ....

A. Finkelstein & H. Fuks, "Multi-party Specification", Proc. of 5th Int. Work. on Soft. Spec. and Design, Pittsburgh, USA, May 1989, IEEE CS Press, 185-195.

....and entryports. Messages are sent out via via exitports exitports and received from and received from entryports entryports . The type definitions for messages and ports are . The type definitions for messages and ports are imported from definition modules by the use clause bed alarm patient bed[5] bed[4] bed[3] bed[2] bed[1] alarm[5] alarm[4] alarm[3] alarm[2] alarm[1] nurse group module patient; group module nurse (maxbed:integer=5) use monmsg: bedtype, alarmstype; use monmsg: bedtype, alarmstype; exitport entryport alarm:alarmstype; alarm[1. maxbed] alarmstype; entryport exitport ....

....out via via exitports exitports and received from and received from entryports entryports . The type definitions for messages and ports are . The type definitions for messages and ports are imported from definition modules by the use clause bed alarm patient bed[5] bed[4] bed[3] bed[2] bed[1] alarm[5] alarm[4] alarm[3] alarm[2] alarm[1] nurse group module patient; group module nurse (maxbed:integer=5) use monmsg: bedtype, alarmstype; use monmsg: bedtype, alarmstype; exitport entryport alarm:alarmstype; alarm[1. maxbed] alarmstype; entryport exitport bed:signaltype reply bedtype; ....

[Article contains additional citation context not shown here]

A.Finkelstein and H.Fuks, "Multi-Party Specification"; Proc 5th International Workshop A.Finkelstein and H.Fuks, "Multi-Party Specification"; Proc 5th International Workshop on Software Specification & Design; pp 185-196, IEEE CS Press.

....sundry representation schemes, use a variety of development strategies and hold diverse domain knowledge. We have also proposed an object based framework deploying ViewPoints within which the above problems may be tackled [15] Issues relating to conflict resolution [10] negotiation and dialogue [14], configuration programming [24] and tool support [20, 21, 34] have already been examined within this framework. The term viewpoint has been defined and deployed in a variety of settings in software engineering, particularly in the domain of requirements engineering; e.g. 23] 25] 31] and ....

A. Finkelstein & H. Fuks, "Multi-party Specification", Proc. of 5th Int. Work. on Soft. Spec. and Design, Pittsburgh, USA, May 1989, IEEE CS Press, 185-195.

....arrows denote relationships that do not yet hold. 6. Experiences To validate and demonstrate our approach, a number of case studies and computer based tools were developed an outline description of which follows. Related issues including conflict resolution [17] negotiation and dialogue [20], and configuration programming [32] were also examined in this setting. 6.1. Tool Support A generic, computer based prototype environment called The Viewer [45] has been built in Objectworks Smalltalk, to support the ViewPoints framework. The Viewer (Fig. 14) runs on a variety of platforms ....

A. Finkelstein and H. Fuks (1989); "Multi-party Specification"; Proceedings of 5th International Workshop on Software Specification and Design (IWSSD-5), Pittsburgh, Pennsylvania, USA, 1920th May 1989, 185-195; IEEE Computer Society Press.

.... implications are, whilst examining further attributes which have an effect on change (e.g. the strength of the contribution) To provide a logical basis for this scheme, we are examining how these types of contribution can be redefined in terms of commitments (adopting the definition given in [Finkelstein Fuks, 1988]) In this way, we should be able to reason about changes to the contribution structure, and provide rules for its recomputation. In summary, what we are proposing is: to link contributors and contributions, by marking up an artifact with its contributor structure, using an underlying scheme that ....

Finkelstein, A. and Fuks, H. (1988). "Multi-Party Specification", Proceedings of the Fifth International Workshop on Software Specification and Design, (IEEE CS Press and ACM SIGSOFT Notes), pp. 185-195.

....as an active, autonomous and loosely coupled agent in the distributed artificial intelligence style. This has raised the possibility of interpreting ViewPoints as active agents. Other influences on the approach we have adopted are those of selfish views [Robinson 1989] and contexts in ERAE [Finkelstein Hagelstein 1989]. The concept of a separate, explicit structural (configuration) description for the software architecture of a system has been fully investigated in the Conic environment for developing distributed systems [Kramer et al. 89a, Magee et al. 89, Kramer 90a] It has been shown to be essential for all ....

Finkelstein A. & Fuks H. (1989); "Multi-Party Specification"; Proc 5th International Workshop on Software Specification & Design; pp 185-196, IEEE CS Press [Also ACM Software Engineering Notes May 1989].

No context found.

Finkelstein, A. and Fuks, H. (1989) "Multi-party specification." in Proc. Fifth Intl. Workshop on Software Specification and Design, May 19-20, Pittsburgh, Pennsylvania, USA #68HTDBTPAUT's##@t#I'#r+, Vol 14 No 3 (May 1989) pp. 185 195.

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