Stéphane Faulkner

Learn More
In their seminal paper in the ACM Transactions on Software Engineering and Methodology, Zave and Jackson established a core ontology for Requirements Engineering (RE) and used it to formulate the “requirements problem”, thereby defining what it means to successfully complete RE. Given that stakeholders of the system-to-be communicate the information needed(More)
In their seminal paper (ACM T. Softw. Eng. Methodol., 6(1) (1997), 1–30), Zave and Jackson established a core ontology for Requirements Engineering (RE) and used it to formulate the “requirements problem”, thereby defining what it means to successfully complete RE. Starting from the premise that the stakeholders of the system-to-be communicate to the(More)
Representation and reasoning about goals of an information system unavoidably involve the transformation of unclear stakeholder requirements into an instance of a goal model. If the requirements engineer does not justify why one clear form of requirements is chosen over others, the subsequent modeling decisions cannot be justified either. If arguments for(More)
In a service-oriented system (SoS) service requests define tasks to execute and quality of service (QoS) criteria to optimize. A service request is submitted to an automated service selector in the SoS, which allocates tasks to those service that, together, can "best" satisfy the given QoS criteria. When the selector cannot optimize simultaneously the given(More)
During these last years, many researchers have proposed new alternatives for early interface design based on hand-sketch. But these new alternatives seem to be dedicated to obsolescence as they only offer the possibility to generate user interfaces for a single platform in a unique language. Indeed, in a context where the number of computing-platforms and(More)
In a service-oriented system, a quality (or Quality of Service) model is used (i) by service requesters to specify the expected quality levels of service delivery; (ii) by service providers to advertise quality levels that their services achieve; and (iii) by service composers when selecting among alternative services those that are to participate in a(More)
Multi-Agent Systems (MAS) architectures are gaining popularity over traditional ones for building open, distributed, and evolving software required by today’s corporate IT applications such as eBusiness systems, web services or enterprise knowledge bases. Since the fundamental concepts of multi-agent systems are social and intentional rather than object,(More)
In a Service-Oriented System (SOS), service requesters specify tasks that need to be executed and the quality levels to meet, whereas service providers advertise their services’ capabilities and the quality levels they can reach. Service selectors then match to the relevant tasks, the candidate services that can perform these tasks to the most desirable(More)
Multi-agent systems are now being considered a promising architectural approach for building Internet-based applications. One of the most critical and important aspects of software deployed on the web has always been the security of their architectures. However, despite considerable work in software architecture during the last decade, few research efforts(More)