No full-text available
To read the full-text of this research,
you can request a copy directly from the authors.
A Rigorous Approach to IT Architecture
Abstract
A precise definition of IT architecture and its relationship to engineering is described. The components used to define architecture are generically defined along with relationships among these components. These concepts are then used, along with a particular architecture viewpoint and system context to document an example of architecture components using structural and behavioural signatures to express form and function. The end result is a well defined approach for the documentation of IT architectures, based upon a concise definition of architecture, the components used to describe the architecture, and the relationships and structures among these components.
ResearchGate has not been able to resolve any citations for this publication.
The terms architecture, design, and implementation are typically used informally in partitioning software specifications into three coarse strata of abstraction. Yet these strata are not well-defined in either research or practice, causing miscommunication and needless debate. To remedy this problem we formalize the Intension and the Locality criteria, which imply that the distinction between architecture, design, and implementation is qualitative and not merely quantitative. We demonstrate that architectural styles are intensional and non-local; that design patterns are intensional and local; and that implementations are extensional and local.
This paper defines an enterprise security model that provides a cohesive structure for the definition and implementation of security services. The complete framework is described, but with a focus on subjects, and protected objects and how access is controlled. Multiple layers of security are defined, building upon the “defence in depth” concept, augmented with “domain” and “zone” concepts and associated protections. The dynamic use of roles is described, a concept that along with user self–service provides a practical approach for the management and use of roles for access control. This model may also be used as a reference architecture for the definition and integration of a set of security services that permit multiple vendor implementations to work together, and to establish the level of compliance of specific systems.
A domain analysis of dynamic system reconfiguration is presented in this paper. The intent is to provide a comprehensive conceptual
framework within which to systematically and consistently address problems and solutions related to dynamically reconfigurable
systems. The analysis identifies and categorizes the various types of change that may be required, the relationship between
those types, and the system integrity characteristics that need to be considered when such changes take place. A system model
is employed to describe each change type using examples of global and local properties in the context of a financial analysis
system. A rigorous formal methodology, based on the Alloy language and tools, is employed to specify precisely and formally
the detailed relationships between various parts of the model. Based upon these descriptions, the types of change of dynamic
system reconfiguration are presented as a series of UML class models.
In this paper, a domain model of dynamic system reconfiguration is presented. The intent of this model is to provide a comprehensive
conceptual framework within which to address problems and solutions related to dynamically reconfigurable systems in a systematic
and consistent manner. The model identifies and categorizes the various types of change that may be required, the relationship
between those types, and the key factors that need to be considered and actions to be performed when such changes take place.
A rigorous formal methodology, based on the Alloy language and tools, is employed to specify precisely and formally the detailed
relationships between various parts of the model.
Object-oriented approaches have been widely applied in enhancing
reusability for software implementation. However, identifying
reusability potential during analysis phases is not a trivial task. This
paper proposes a methodology for analyzing business domains. These
domains are built in the form of reusable business objects. The
methodology consists of three phases: domain context modeling; domain
semantic modeling; and domain reuse modeling. A domain repository system
is developed to help analysts use the methodology for reuse support in a
systematic way. To demonstrate the usefulness of the methodology, a
real-life example is illustrated
Security techniques — Security information objects for access control
- Iso Iec
ISO/IEC 15816:2002, Security techniques — Security information objects for access control.
Form follows function
- Wikipedia Wikipedia Online
Published Software Architecture Definitions
- Sei Online
A Practical Guide to IT Architecture
- D W Enstrom