• Refine Query
  • Source
  • Publication year
  • to
  • Language
  • 6
  • 3
  • 1
  • Tagged with
  • 18
  • 18
  • 18
  • 10
  • 9
  • 9
  • 7
  • 7
  • 7
  • 7
  • 7
  • 7
  • 7
  • 7
  • 7
  • About
  • The Global ETD Search service is a free service for researchers to find electronic theses and dissertations. This service is provided by the Networked Digital Library of Theses and Dissertations.
    Our metadata is collected from universities around the world. If you manage a university/consortium/country archive and want to be added, details can be found on the NDLTD website.
11

Viable Software: the Intelligent Control Paradigm for Adaptable and Adaptive Architecture

Herring, Charles Edward Unknown Date (has links)
The Intelligent Control Paradigm for software architecture is the result of this work. The Viable Software Approach is developed as an instance of the paradigm. The approach uses the Viable System Model as the basis for software system architecture. The result is a model-based architecture and approach for developing software systems by piecemeal adaptation with the goal that they become adaptive systems at runtime. Software built in this manner is called Viable Software. Viable Software represents a unifying class of self-controlling software that is an “intelligent” control system. Cybernetics, Control Theory, and Complexity Theory are the background for this work, and aspects relevant to this work are presented. These results are related to software architecture and software engineering. Rationale for the selection of the Viable System Model as a basis for software systems is given. The Viable System Model is described. The model is restated as an Alexanderian “pattern language” to make it more accessible to software engineering. A Viable Software Approach is proposed and expressed in the form of a Product Line Architecture that arranges the Viable System Model, the Viable Software Architecture, a Viable Component Framework, and a Component Transfer Protocol into a system for generative programming. An important result is the formalisation of the pattern of the Viable System into the interface specifications of the Viable Component. Three case studies illustrate the approach. The first is an analysis and extension of the Groove collaboration system. This study shows how the approach is used to map an existing system into the Viable Software Architecture and add fuzzy-adaptive user interface controllers. The second study presents the design and detailed software construction of an adaptive camera controller as part of a smart environment. The final study shows how a Business-to-Business e-Commerce system can be evolved and an expert system-based controller developed to implement business contracts.
12

Viable Software: the Intelligent Control Paradigm for Adaptable and Adaptive Architecture

Herring, Charles Edward Unknown Date (has links)
The Intelligent Control Paradigm for software architecture is the result of this work. The Viable Software Approach is developed as an instance of the paradigm. The approach uses the Viable System Model as the basis for software system architecture. The result is a model-based architecture and approach for developing software systems by piecemeal adaptation with the goal that they become adaptive systems at runtime. Software built in this manner is called Viable Software. Viable Software represents a unifying class of self-controlling software that is an “intelligent” control system. Cybernetics, Control Theory, and Complexity Theory are the background for this work, and aspects relevant to this work are presented. These results are related to software architecture and software engineering. Rationale for the selection of the Viable System Model as a basis for software systems is given. The Viable System Model is described. The model is restated as an Alexanderian “pattern language” to make it more accessible to software engineering. A Viable Software Approach is proposed and expressed in the form of a Product Line Architecture that arranges the Viable System Model, the Viable Software Architecture, a Viable Component Framework, and a Component Transfer Protocol into a system for generative programming. An important result is the formalisation of the pattern of the Viable System into the interface specifications of the Viable Component. Three case studies illustrate the approach. The first is an analysis and extension of the Groove collaboration system. This study shows how the approach is used to map an existing system into the Viable Software Architecture and add fuzzy-adaptive user interface controllers. The second study presents the design and detailed software construction of an adaptive camera controller as part of a smart environment. The final study shows how a Business-to-Business e-Commerce system can be evolved and an expert system-based controller developed to implement business contracts.
13

Viable Software: the Intelligent Control Paradigm for Adaptable and Adaptive Architecture

Herring, Charles Edward Unknown Date (has links)
The Intelligent Control Paradigm for software architecture is the result of this work. The Viable Software Approach is developed as an instance of the paradigm. The approach uses the Viable System Model as the basis for software system architecture. The result is a model-based architecture and approach for developing software systems by piecemeal adaptation with the goal that they become adaptive systems at runtime. Software built in this manner is called Viable Software. Viable Software represents a unifying class of self-controlling software that is an “intelligent” control system. Cybernetics, Control Theory, and Complexity Theory are the background for this work, and aspects relevant to this work are presented. These results are related to software architecture and software engineering. Rationale for the selection of the Viable System Model as a basis for software systems is given. The Viable System Model is described. The model is restated as an Alexanderian “pattern language” to make it more accessible to software engineering. A Viable Software Approach is proposed and expressed in the form of a Product Line Architecture that arranges the Viable System Model, the Viable Software Architecture, a Viable Component Framework, and a Component Transfer Protocol into a system for generative programming. An important result is the formalisation of the pattern of the Viable System into the interface specifications of the Viable Component. Three case studies illustrate the approach. The first is an analysis and extension of the Groove collaboration system. This study shows how the approach is used to map an existing system into the Viable Software Architecture and add fuzzy-adaptive user interface controllers. The second study presents the design and detailed software construction of an adaptive camera controller as part of a smart environment. The final study shows how a Business-to-Business e-Commerce system can be evolved and an expert system-based controller developed to implement business contracts.
14

Viable Software: the Intelligent Control Paradigm for Adaptable and Adaptive Architecture

Herring, Charles Edward Unknown Date (has links)
The Intelligent Control Paradigm for software architecture is the result of this work. The Viable Software Approach is developed as an instance of the paradigm. The approach uses the Viable System Model as the basis for software system architecture. The result is a model-based architecture and approach for developing software systems by piecemeal adaptation with the goal that they become adaptive systems at runtime. Software built in this manner is called Viable Software. Viable Software represents a unifying class of self-controlling software that is an “intelligent” control system. Cybernetics, Control Theory, and Complexity Theory are the background for this work, and aspects relevant to this work are presented. These results are related to software architecture and software engineering. Rationale for the selection of the Viable System Model as a basis for software systems is given. The Viable System Model is described. The model is restated as an Alexanderian “pattern language” to make it more accessible to software engineering. A Viable Software Approach is proposed and expressed in the form of a Product Line Architecture that arranges the Viable System Model, the Viable Software Architecture, a Viable Component Framework, and a Component Transfer Protocol into a system for generative programming. An important result is the formalisation of the pattern of the Viable System into the interface specifications of the Viable Component. Three case studies illustrate the approach. The first is an analysis and extension of the Groove collaboration system. This study shows how the approach is used to map an existing system into the Viable Software Architecture and add fuzzy-adaptive user interface controllers. The second study presents the design and detailed software construction of an adaptive camera controller as part of a smart environment. The final study shows how a Business-to-Business e-Commerce system can be evolved and an expert system-based controller developed to implement business contracts.
15

Viable Software: the Intelligent Control Paradigm for Adaptable and Adaptive Architecture

Herring, Charles Edward Unknown Date (has links)
The Intelligent Control Paradigm for software architecture is the result of this work. The Viable Software Approach is developed as an instance of the paradigm. The approach uses the Viable System Model as the basis for software system architecture. The result is a model-based architecture and approach for developing software systems by piecemeal adaptation with the goal that they become adaptive systems at runtime. Software built in this manner is called Viable Software. Viable Software represents a unifying class of self-controlling software that is an “intelligent” control system. Cybernetics, Control Theory, and Complexity Theory are the background for this work, and aspects relevant to this work are presented. These results are related to software architecture and software engineering. Rationale for the selection of the Viable System Model as a basis for software systems is given. The Viable System Model is described. The model is restated as an Alexanderian “pattern language” to make it more accessible to software engineering. A Viable Software Approach is proposed and expressed in the form of a Product Line Architecture that arranges the Viable System Model, the Viable Software Architecture, a Viable Component Framework, and a Component Transfer Protocol into a system for generative programming. An important result is the formalisation of the pattern of the Viable System into the interface specifications of the Viable Component. Three case studies illustrate the approach. The first is an analysis and extension of the Groove collaboration system. This study shows how the approach is used to map an existing system into the Viable Software Architecture and add fuzzy-adaptive user interface controllers. The second study presents the design and detailed software construction of an adaptive camera controller as part of a smart environment. The final study shows how a Business-to-Business e-Commerce system can be evolved and an expert system-based controller developed to implement business contracts.
16

Viable Software: the Intelligent Control Paradigm for Adaptable and Adaptive Architecture

Herring, Charles Edward Unknown Date (has links)
The Intelligent Control Paradigm for software architecture is the result of this work. The Viable Software Approach is developed as an instance of the paradigm. The approach uses the Viable System Model as the basis for software system architecture. The result is a model-based architecture and approach for developing software systems by piecemeal adaptation with the goal that they become adaptive systems at runtime. Software built in this manner is called Viable Software. Viable Software represents a unifying class of self-controlling software that is an “intelligent” control system. Cybernetics, Control Theory, and Complexity Theory are the background for this work, and aspects relevant to this work are presented. These results are related to software architecture and software engineering. Rationale for the selection of the Viable System Model as a basis for software systems is given. The Viable System Model is described. The model is restated as an Alexanderian “pattern language” to make it more accessible to software engineering. A Viable Software Approach is proposed and expressed in the form of a Product Line Architecture that arranges the Viable System Model, the Viable Software Architecture, a Viable Component Framework, and a Component Transfer Protocol into a system for generative programming. An important result is the formalisation of the pattern of the Viable System into the interface specifications of the Viable Component. Three case studies illustrate the approach. The first is an analysis and extension of the Groove collaboration system. This study shows how the approach is used to map an existing system into the Viable Software Architecture and add fuzzy-adaptive user interface controllers. The second study presents the design and detailed software construction of an adaptive camera controller as part of a smart environment. The final study shows how a Business-to-Business e-Commerce system can be evolved and an expert system-based controller developed to implement business contracts.
17

O modelo do sistema viável na concepção da arquitetura de sistemas de informação: aplicação no contexto de incidentes em instalação de pesquisa na área nuclear. / The Viable System Model (VSM) in the conception of information system architectures - an application in the context of incidents for a research nuclear installation.

Maria Cláudia Santiago Hampshire 10 November 2008 (has links)
O trabalho apresenta um estudo com a finalidade de verificar a aplicabilidade do Modelo do Sistema Viável (VSM Viable System Model) no projeto de uma arquitetura robusta de um Sistema de Informação voltado à área naval nuclear. A ênfase do estudo está em avaliar uma modelagem alternativa para a especificação da arquitetura do Sistema de Informação, incorporando o conjunto de funcionalidades especificadas pelo VSM, com o objetivo de fortalecer esta arquitetura. A estratégia desta pesquisa baseia-se em uma revisão bibliográfica relacionada ao VSM, aos Sistemas de Informação e a sua arquitetura, e às influências destes elementos na sobrevivência das organizações diante das mudanças constantes no ambiente. É apresentado um estudo de caso onde são mostrados os elementos teóricos do VSM e da arquitetura de SI aplicados na elaboração da arquitetura de um SI. O Sistema escolhido para esta aplicação é o Sistema de informação de incidentes nucleares (SIN) nas instalações onde são feitas pesquisas e desenvolvimento de tecnologia nuclear a ser aplicada na propulsão de um submarino. / The present work presents a study aiming to verify the applicability of the Viable System Model (VSM) in a robust architecture for an Information System targeting nuclear naval area. The emphasis of the study is in assessing an alternative modeling for the Information System (IS) architecture specification, incorporating a set of functionalities defined by the VSM, with the purpose of strengthening this architecture. The strategy of this research is based on a bibliographic revision on VSM, Information System and its architecture, and the influence of those elements in the survival of the organizations in a ever changing environment. It is presented one case study where it is showed the theoretical elements of the VSM and IS architecture applied on the development of a IS architecture. The selected system for this application is the IS for nuclear incidents (SIN) on the installations dedicated to research and development on nuclear technology applied to submarine propulsion system.
18

Digital Wall : The University’s learning and information space

Agiorgitis, Georgios, Bennani, Mohamed, Drakoularakos, Mixalis, McConnon, Paul John January 2017 (has links)
A North American university is engaged in a large transformation project involving the wholeorganisation. Students, Lecturers, departments and additional questions from the shared leadership team are engaging in defining the services offered, in particular from the university library and its associated sub-services. It is an exciting time for the University as it seeks to not only define its services but also how these can be created and consumed.There are many aspects to this re-organisation and many items to be addressed. In this report,we look at the current situation at the University, as well as taking into account the aspirations of the stakeholders. We start by drawing out a Rich Picture, part of Soft System Methodology (SSM) (Checkland, 1981) which we use in order to spot opportunities that are available for further exploration. Much of the information that we use comes from material supplied by the University itself as well as interviews with the Head of Library services and Head of Library IT. We look indepth at how SSM assists in this process of evaluation through its focus on participation and how it may assist us to understand the many different perspectives collected in our research. SSM consequently assists in defining problems with solutions to any areas that have drawn our attention. Following the evaluation of collected data, discussions and our own observations, we identify that a digital wall that is being proposed for the redesigned library presents an opportunity to explore possibilities for exploitation of this technology. Further research on other digital walls such as Brisbane’s Cube (Abdi et al, 2014), and Auraria Library’s Discovery Wall(Burch, 2016) shows some of the uses that these walls have been put to and how the Institutions use them. We then use a number of models to evaluate the data that we collected on digital walls and from the North American University and analyse it in order to inform our thinking. These models can be used independently or collectively to evaluate data from different perspectives. As such we were able to look at problems and solutions from the perspective of many of the actors involved in shaping the future library services. These models and results are discussed in the report. Finally, we take our results and make a number of proposals for the North American University digital wall along with the relevant justifications at the end of this report. / <p>This is a report in the Informatics course 5IK501 during the school year of 2016/2017.</p>

Page generated in 0.039 seconds