Mart Roost

Towards Archetypes-Based Software Development

We present a framework for the archetypes based engineering of domains, requirements and software (Archetypes-Based Software Development, ABD). An archetype is defined as a primordial object that occurs consistently and universally in business domains and in business software systems. An archetype pattern is a collaboration of archetypes. Archetypes and archetype patterns are used to capture conceptual information into domain specific models that are utilized by ABD. The focus of ABD is on software factories - family-based development artefacts (domain specific languages, patterns, frameworks, tools, micro processes, and others) that can be used to build the family members. We demonstrate the usage of ABD for developing laboratory information management system (LIMS) software for the Clinical and Biomedical Proteomics Group, at the Leeds Institute of Molecular Medicine, University of Leeds.

A Role-Based Framework for Information System Self-Development

This paper presents an approach to information systems development based on contemporary business and organization models. Business organizations are changing very quickly and their information systems must evolve dynamically with them. We have developed a concept of IS self-development where the information system is treated as an active information view or a level of a business organization providing and mediating not only the information and communication services but also the development services of the organization and its IS. This makes it possible for IS development processes to be handled in the context of the organizational roles ofthe business organization, allowing specialized development organizations to focus on services for IS development. A meta-model of the architecture of the IS development process and a general methodological framework for modeling and organizing such subject-centered development processes have been developed. The paper reflects the current status of an ongoing project (Estonian Science Foundation grant G3765).

Domain analysis with archetype patterns based Zachman Framework for enterprise architecture

The software factories approach is one of a number of the automated software development methods, which promise greater gains in productivity and predictability by making application assembly more cost effective through systematic reuse and by enabling the formation of supply chains. In our research work on archetypes based development we investigate methods and applications of business archetypes and business archetype patterns (originally described by Arlow and Neustadt) in the development of software factories. In the current paper we describe and explain the Zachman Framework (ZF) from the archetype patterns perspective, explain how we use this archetype patterns based ZF in domain analysis and compare the ZF based approach with Dines Björners domain facets based approach. The business domain in our studies consists of a clinical laboratory. Our research is based on Laboratory Information Management System developments for the Clinical and Biomedical Proteomics Group, University of Leeds, UK. Our studies show, that ZF with archetypes and archetype patterns helps developers to better understand business domains, to design more robust and cost effective enterprise applications through systematic reuse of archetypal components by enabling supply chains of product families and to explain solutions to domain experts.

Towards Self-development of Evolutionary Information Systems: An Action Research of Business Architecture Development by Students in Socially Networked Groups

We present a case study of business architecture development by students working in socially networked groups. In this case study we emulated a self-development of an evolutionary information system. The “client system” in this emulated project was medical laboratory information system. In the role of the “change agent” were students of two different specialties: medical technology students (one group) and IT students (another group). We describe the process and results of the first (finished) phase of strategic analysis where the initial business architecture was developed. Later on this business architecture will be utilized as a platform for (social, self-) development of business processes and software. Medical technology students (knowing the problem) played the business process owner/analyst dual role. IT students (knowing IT-related solution patterns for the problem and processes) played the business designer role. The relationships between (and inside) the two groups/communities were managed using Google Sites (social) software.