| 1. |
- Brazier, Frances, et al.
(författare)
-
Compositional verification of a multi-agent system for one-to-many negotiation
- 2004
-
Ingår i: Applied intelligence (Boston). - DORDRECHT : KLUWER ACADEMIC PUBL. - 0924-669X .- 1573-7497. ; 20:2, s. 95-117
-
Tidskriftsartikel (refereegranskat)abstract
- Verification of multi-agent systems hardly occurs in design practice. One of the difficulties is that required properties for a multi-agent system usually refer to multi-agent behaviour which has nontrivial dynamics. To constrain these multi-agent behavioural dynamics, often a form of organisational structure is used, for example, for negotiating agents, by following strict protocols. The claim is that these negotiation protocols entail a structured process that is manageable with respect to analysis, design and execution of such a multi-agent system. In this paper this is shown by a case study: verification of a multi-agent system for one-to-many negotiation in the domain of load balancing of electricity use. A compositional verification method for multi-agent systems is applied that allows to (1) logically relate dynamic properties of the multi-agent system as a whole to dynamic properties of agents, and (2) logically relate dynamic properties of agents to properties of their subcomponents. Given that properties of these subcomponents can be verified by more standard methods, these logical relationships provide proofs of the dynamic properties of the multi-agent system as a whole.
|
|
| 2. |
- Dittrich, Yvonne, et al.
(författare)
-
Can Software Development be too Use Oriented? Going Native as an issue in Participatory Design.
- 2001
-
Konferensbidrag (refereegranskat)abstract
- In participatory design there is a risk that the emphasis on the co-operation with future users let the developers forget to step back and reflect on what they learned. In this article we report about a case study of a software project and the resulting system. In spite of a user oriented way of developing the system, problems showed up both when using the software and when the developers later tried to modify it. Part of the reason for the problems was the (lack of) structure in the system. We use the 'going native' - a well discussed methodological issue in ethnography - as a metaphor. The ethnographer have to both 'go native' to be able to understand the culture studied but also step back and reflect. In the same way the software developer has to 'step back' and reflect and form their own conceptual model.
|
|
| 3. |
- Dittrich, Yvonne, et al.
(författare)
-
Design for Change
- 2001
-
Rapport (övrigt vetenskapligt/konstnärligt)abstract
- The report summarises the first year of the research project 'Design for Design in Use of Database Applications'. It focuses on end user tailoring and adaptable systems.
|
|
| 4. |
|
|
| 5. |
|
|
| 6. |
- Dittrich, Yvonne, et al.
(författare)
-
How use-oriented development can take place
- 2004
-
Ingår i: Information and Software Technology. - : Elsevier. - 0950-5849 .- 1873-6025. ; 46:9, s. 603-617
-
Tidskriftsartikel (refereegranskat)abstract
- Usability is still a problem for software development. As the introduced software changes the use context, use qualities cannot be fully anticipated. Close co-operation between users and developers during development has been proposed as a remedy. Others fear such involvement of users as it might jeopardize planning and control. Based on the observation of an industrial project, we show how user participation and control can be achieved at the same time. The present article discusses the specific measures that allowed for co-operation between users and developers in an industrial context. It indicates measures to improve software development by focusing on use-orientation, i.e. allowing for user-developer co-operation.
|
|
| 7. |
|
|
| 8. |
- Eriksson, Jeanette, et al.
(författare)
-
Leaving Variability Management to the End User; A Comparison Between Different Tailoring Approaches
- 2003
-
Rapport (övrigt vetenskapligt/konstnärligt)abstract
- To enable software to fulfill user requirements over time and meet changes in, for example, business environments, software variability is needed. One way to achieve variability is through tailoring. However, some kind of variability management is needed in order to take advantage of variability. With a tailorable system we mean a system that is designable when it is in use. This means that some design decisions are postponed until the system is up and running. It is the end-user who will adjust the program to fit altered requirements through, for example, run-time configuration. In other words, tailoring requires that the variability management of the system is left to the end user. In this article we present three different examples of tailoring and in the form of a comparison between the three approaches we identify and discuss some issues which must be considered when variability management is left to the end user.
|
|
| 9. |
|
|
| 10. |
|
|
