Security is often compromised by exploiting vulnerabilities in the interface between the organization and the information systems that support it. This reveals the necessity of modeling and analyzing information systems together with the organizational setting where they will operate. In this chapter we address this problem by presenting a modeling language tailored to analyze the problem of security at an organizational level. This language proposes a set of concepts founded on the notions of permission, delegation, and trust. The chapter also presents a semantics for these concepts, based on Datalog. A case study from the bank domain is employed to illustrate the proposed language.

Rapid development of a distributed shop floor control system from an XML model-based control software specification

Syntax Notation One. An ISO standard (DIS 8824 and DIS 8825) that specifies a canonical method of data encoding. This standard is an extension of CCITT Standard X.409. Aspect -- 1. An appearance; air, an element; facet, a position or side facing a given direction. 2. Those views of the world which enable the observer to attribute meaning to what is observed. It can be lik- 9-11 ened to a filter in the head of an observer which has been formed and is continually modeled by experience, personality, politics, society, and the situation. [WG1] Assembly -- The act of assembling or the state of being assembled; the putting together of parts to make a completed product, a set of parts so assembled: the steering assembly of a truck, the signal calling troops to assemble. Assembly Specification -- The assembly specification establishes detailed assembly procedures for any combination of parts, subassemblies, etc., that perform a specific function [SAMA]. Assess -- To evaluate. Assign -- To sp...

In this paper we investigate essential properties of virtual enterprises and the consequent modelling requirements. Apart from that, we define agent’s autonomy. As agents in AI (Artificial Intelligence), virtual enterprises are treated as autonomous entities. Requirements are derived from two types of virtual enterprises, a repetitive and a one-of-akind production or service enterprise. A virtual enterprise model should represent properties which include the dynamics of decision-making, the negotiations among participants for the definition of autonomy, authority, beliefs and responsibilities, the mapping of organisational entities to decisional roles, the ability to identify and analyse a variety of conflict types and the existence of conflict resolution paths. These properties have to be analysed by matching enterprise-engineering tools. An ontological theory is also needed to systematise the concepts that must be supported by the protocol languages for parallel distributed planning, scheduling and control algorithms in the virtual enterprise. We are presenting an approach to this problem using systemic methodologies such as TSI (Total Systems Intervention), SAST (Strategic Assumption Surfacing & Testing), SSM (Soft Systems Methodology), and PSM (Problem Structuring Methodology) in order to decompose the enterprise to autonomous entities – and trace possible problems- and solve participants disagreements in an edifying, for the enterprise, way. A useful trial example to implement and comprehend the above methodologies is that of the virtual team of an enterprise, which offers management services to hospitals and health centers in Greece. Keywords:

Abstract. System architectures are described in abstract terms, often using Design Patterns. Actual reuse based on such descriptions requires that each development project derive a concrete architecture from the chosen Patterns, and then implement it in code. This paper describes a case study of an industrial development project that adopted a reference application as a starting point, in order to avoid the need to design a complete architecture. Reference applications are usually made by platform or component vendors. Such applications are used to provide executable examples of best practices, for a particular platform, component set, or other technology. In this case study, the Pet Store application for the J2EE platform was chosen. Pet Store is documented by Design Patterns and is also available as source code. The development consisted of replacing the application logic, while keeping the architecture intact. The project was thus transformed from an ab initio development project into a major reuse/modification project. This development project was part of a software process improvement effort looking at processes for and with reuse. Our results indicate that this approach works well, provided that the functional and non-functional requirements of the project match those of the reference application. The development time was shortened by approximately one third relative to the original estimate, and a well-designed application was produced despite lack of experience with the platform and n-layer architectures. Surprisingly, the production deployment to a different application server was still problematic, even though the original reference application was available as a sample for that server. 1

This paper describes PERA (the Purdue Enterprise Reference Architecture) and shows its relationships to GERAM (the Generalized Enterprise Reference Architecture and Methodology). PERA was developed at Purdue University during the period 1989-91. GERAM was developed by the IFAC/IFIP Task Force to illustrate that all “complete ” enterprise reference architectures should map together and have comparable characteristics and capabilities.