Workflow management systems (WfMSs) have been used to support various types of business processes for more than a decade now. In workflows for e-commerce and Web-services applications, suppliers and customers define a binding agreement or contract between the two parties, specifying Quality of Service (QoS) items such as products or services to be delivered, deadlines, quality of products, and cost of services. The management of QoS metrics directly impacts the success of organizations participating in e-commerce. Therefore, when services or products are created or managed using workflows, the underlying workflow system must accept the specifications and be able to estimate, monitor, and control the QoS rendered to customers. In this paper, we present a predictive QoS model that makes it possible to compute the quality of service for workflows automatically based on atomic task QoS attributes. To this end, we present a model that specifies QoS and describe an algorithm and a simulation system in order to compute, analyze and monitor workflow QoS metrics. 1

Abstract: Software engineering researchers and practitioners have long had an uncertain and uneasy relationship with design. It is acknowledged that software design is critical and major strides have been made in advancing the discipline, but we all are keenly aware that something “just is not quite right ” and that design remains one of the least-understood aspects of software engineering. This paper contributes the DESIGN DIAMOND, a new framework that examines software design from the novel perspective of the individual software designer. Taking this perspective turns the DESIGN DIAMOND into an unbiased instrument to view software design and allows us to compare the ways in which software design is typically positioned, evaluate the field’s contributions to date in supporting the practice of software design, and lay out a comprehensive research agenda for improving the state of the art.

Software engineering researchers and practitioners have long had an uncertain and uneasy relationship with design. It is acknowledged that software design is critical and major strides have been made in advancing the discipline, but we all are keenly aware that something “just is not quite right ” and that design remains one of the least-understood aspects of software engineering. This paper contributes the DESIGN DIAMOND, a new framework that examines software design from the novel perspective of the individual software designer. Taking this perspective turns the DESIGN DIAMOND into an unbiased instrument to view software design and allows us to compare the ways in which software design is typically positioned, evaluate the field’s contributions to date in supporting the practice of software design, and lay out a comprehensive research agenda for improving the state of the art.

Lero-TR-2009-00-20090727.docx 1//i Contact Address..

If you’re going to read only one book on software architecture, start with this one. Just Enough Software Architecture covers the essential concepts of software architecture that everyone — programmers, developers, testers, architects, and managers — needs to know, and it provides pragmatic advice that can be put into practice within hours of reading. —Michael Keeling, professional software engineer This book reflects the author’s rare mix of deep knowledge of software architecture concepts and extensive industry experience as a developer. If you’re an architect, you will want the developers in your organization to read this book. If you’re a developer, do read it. The book is about architecture in real (not ideal) software projects. It describes a context that you’ll recognize and then it shows you how to improve your design practice in that context. —Paulo Merson, practicing software architect and Visiting Scientist at the Software Engineering Institute Fairbanks ’ focus on “just enough ” architecture should appeal to any developers trying to work out how to make the architecting process tractable. This focus is made accessible through detailed examples and advice that illustrate how an understanding of risk can be used to manage architecture development and scope. At the same time, Fairbanks provides detail on the more academic aspects of software architecture, which should help developers who are interested in understanding the broader theory and practice to apply these concepts to their projects.