Modeling architectural non functional requirements: From use case to control case

While the functional requirements of a system can be effectively modeled through the Use Case driven approach, there is no standard or de facto method for modeling non-functional requirements of the system architecture. Often such requirements are dealt with in a reactive manner rather than proactively. Yet increasingly a contributing factor in project difficulty and failure are the non-functional requirements imposed on the solution architecture. This paper proposes a Control Case approach to record and model non-functional requirements. This technique enables the control case to represent the nonfunctional requirements from different perspectives, most typically the various operating conditions. Furthermore, we propose an extension to the “4+1" view model for depicting software architecture by adding the control case view. The combination of both the use case and control case views thus reflects the complete requirements across the collective system life cycle views: design, process, implementation and deployment

Efficient Batch Signature Generation using Tree Structures

E-mail: fpavlovsk, [email protected] Abstract We propose an efficient batch signature generationscheme for signing multiple messages simultaneously. The scheme can be based on any signature scheme with ap-pendix and resultant signatures preserve the property of independent verification by different recipients. The scheme isshown to be of almost constant complexity for both generation and verification as the number of messages increaseswhile the size of the signature increases only logarithmically with the number of messages in the batch. It is demon-strated that the security of the batch signature is equivalent to the security of the underlying signature mechanisms

A Disclosure framework for service accountability in SOA

Accountability has become a key concern for management in recent years since the collapse of several large corporations in energy, communications and financial consulting industries. Traditionally, accountability has not been a significant concern in the IT literature. Recently, some protocols, models and frameworks that address certain aspects of accountability have emerged. However, an architecture framework that addresses the overall accountability requirements is nonetheless missing in a service-oriented computing environment. In this paper, we review the accountability literature in an IT context and argue that disclosure, as a crucial requirement of accountability, has been largely ignored in the current literature. Based on this proposition, we propose a new architectural framework to address the important disclosure requirement that extends and integrates the existing architecture models. The proposed framework can be used to build SOA solutions that support the key accountability requirements.6 page(s

A Quantitative service accountability model

Recently, several global institutions have fallen victim to concerns regarding disclosure and accountability. The most poignant examples are the recent US Wall Street collapse due to the burgeoning effect of Collateralized Debt Obligations (CDO). The key concern for consumers of these services are transparency, disclosure, and trust of the product/services. These are elementary attributes of accountability and in the online world of trading goods and services. Information technology provides the SOA foundation for executing these global transactions. This paper presents a quantitative model to measure and assess accountability in SOA. The proposed model may be applied in practice to assess accountability of a service or process, assisting to strengthen accountability in SOA and general information and communication technology (ICT) solutions that support transactions globally.6 page(s