A Four Layer Bayesian Network for Product Model Based Information Mining

Business and engineering knowledge in AEC/FM is captured mainly implicitly in project and corporate document repositories. Even with the increasing integration of model-based systems with project information spaces, a large percentage of the information exchange will further on rely on isolated and rather poorly structured text documents. In this paper we propose an approach enabling the use of product model data as a primary source of engineering knowledge to support information externalisation from relevant construction documents, to provide for domain-specific information retrieval, and to help in re-organising and re-contextualising documents in accordance to the user’s discipline-specific tasks and information needs. Suggested is a retrieval and mining framework combining methods for analysing text documents, filtering product models and reasoning on Bayesian networks to explicitly represent the content of text repositories in personalisable semantic content networks. We describe the proposed basic network that can be realised on short-term using minimal product model information as well as various extensions towards a full-fledged added value integration of document-based and model-based information

A Four Layer Bayesian Network for Product Model Based Information Mining

Business and engineering knowledge in AEC/FM is captured mainly implicitly in project and corporate document repositories. Even with the increasing integration of model-based systems with project information spaces, a large percentage of the information exchange will further on rely on isolated and rather poorly structured text documents. In this paper we propose an approach enabling the use of product model data as a primary source of engineering knowledge to support information externalisation from relevant construction documents, to provide for domain-specific information retrieval, and to help in re-organising and re-contextualising documents in accordance to the user’s discipline-specific tasks and information needs. Suggested is a retrieval and mining framework combining methods for analysing text documents, filtering product models and reasoning on Bayesian networks to explicitly represent the content of text repositories in personalisable semantic content networks. We describe the proposed basic network that can be realised on short-term using minimal product model information as well as various extensions towards a full-fledged added value integration of document-based and model-based information

Design: the quintessential business transaction

The fundamental structures that underpin business activities must evolve and change in order to equip companies to thrive in a market whose characteristics are increasing competition and instability. The incremental advances in applied computing technology and business methodologies which focus on improving one aspect of company operations ignore the need for an underlying structure and model through which to engage any and all functions in a consistent and integrated fashion. Indeed, many exacerbate the problem through closed architectures, isolationist views of entity data storage and rigid methodologies imposed on the company that employs them. The Product Model proposed fulfils that role. It is a model of the processes and entities that a company uses to conduct its business, at all levels and across all departments. Two other concepts are exposed: product model data and the design history record. Product model data are the values of instances of product model entities and relations, created to represent a particular design, artefact or object. The design history record captures the data and functions used in a transaction and the order and context in which they are used. To exercise these concepts, a software suite was written, the Glasgow Utility for Integrated Design, Guide. It supports the definition of a proud model and its subsequent use in the creation of product model data. Each interaction with the system is recorded, thus capturing the design history record, which can subsequently be processes to various advantageous ends. The major such uses are for re-use of part information in other designs and the extraction of design best practice with which to augment the company's design methodology. It is a comprehensive record, since all business processes are supported by, and can be transacted through Guide. Guide has been used to validate the adequacy of the product model and has established many benefits through its use. Applications in many spheres are possible; engineering has been the primary focus for exemplars and case studies. The development was carried out under the scrutiny of constant validation and testing in live situations with several industrial partners. Guide is built on industry standard tools and uses relational database technology to store frame-based representations of entities, methods and relationships. The design of project plans is carried out on the same platform used to support the project itself; the design data are not dissociated from the project controlling mechanism. Resources, including staff, are engaged according to requirements and audit mechanisms allow for constant re-evaluation of the project development. Control and communication mechanisms support applications in an extended enterprise environment and the distribution of resources that this entails

Requirements engineering for computer integrated environments in construction

A Computer Integrated Environment (CIE) is the type of innovative integrated information system that helps to reduce fragmentation and enables the stakeholders to collaborate together in business. Researchers have observed that the concept of CIE has been the subject of research for many years but the uptake of this technology has been very limited because of the development of the technology and its effective implementation. Although CIE is very much valued by both industrialists and academics, the answers to the question of how to develop and how to implement it are still not clear. The industrialists and researchers conveyed that networking, collaboration, information sharing and communication will become popular and critical issues in the future, which can be managed through CIE systems. In order for successful development of the technology, successful delivery, and effective implementation of user and industry-oriented CIE systems, requirements engineering seems a key parameter. Therefore, through experiences and lessons learnt in various case studies of CIE systems developments, this book explains the development of a requirements engineering framework specific to the CIE system. The requirements engineering process that has been developed in the research is targeted at computer integrated environments with a particular interest in the construction industry as the implementation field. The key features of the requirements engineering framework are the following: (1) ready-to-use, (2) simple, (3) domain specific, (4) adaptable and (5) systematic, (6) integrated with the legacy systems. The method has three key constructs: i) techniques for requirements development, which includes the requirement elicitation, requirements analysis/modelling and requirements validation, ii) requirements documentation and iii) facilitating the requirements management. It focuses on system development methodologies for the human driven ICT solutions that provide communication, collaboration, information sharing and exchange through computer integrated environments for professionals situated in discrete locations but working in a multidisciplinary and interdisciplinary environment. The overview for each chapter of the book is as follows; Chapter 1 provides an overview by setting the scene and presents the issues involved in requirements engineering and CIE (Computer Integrated Environments). Furthermore, it makes an introduction to the necessity for requirements engineering for CIE system development, experiences and lessons learnt cumulatively from CIE systems developments that the authors have been involved in, and the process of the development of an ideal requirements engineering framework for CIE systems development, based on the experiences and lessons learnt from the multi-case studies. Chapter 2 aims at building up contextual knowledge to acquire a deeper understanding of the topic area. This includes a detailed definition of the requirements engineering discipline and the importance and principles of requirements engineering and its process. In addition, state of the art techniques and approaches, including contextual design approach, the use case modelling, and the agile requirements engineering processes, are explained to provide contextual knowledge and understanding about requirements engineering to the readers. After building contextual knowledge and understanding about requirements engineering in chapter 2, chapter 3 attempts to identify a scope and contextual knowledge and understanding about computer integrated environments and Building Information Modelling (BIM). In doing so, previous experiences of the authors about systems developments for computer integrated environments are explained in detail as the CIE/BIM case studies. In the light of contextual knowledge gained about requirements engineering in chapter 2, in order to realize the critical necessity of requirements engineering to combine technology, process and people issues in the right balance, chapter 4 will critically evaluate the requirements engineering activities of CIE systems developments that are explained in chapter 3. Furthermore, to support the necessity of requirements engineering for human centred CIE systems development, the findings from semi-structured interviews are shown in a concept map that is also explained in this chapter. In chapter 5, requirements engineering is investigated from different angles to pick up the key issues from discrete research studies and practice such as traceability through process and product modelling, goal-oriented requirements engineering, the essential and incidental complexities in requirements models, the measurability of quality requirements, the fundamentals of requirements engineering, identifying and involving the stakeholders, reconciling software requirements and system architectures and barriers to the industrial uptake of requirements engineering. In addition, a comprehensive research study measuring the success of requirements engineering processes through a set of evaluation criteria is introduced. Finally, the key issues and the criteria are comparatively analyzed and evaluated in order to match each other and confirm the validity of the criteria for the evaluation and assessment of the requirements engineering implementation in the CIE case study projects in chapter 7 and the key issues will be used in chapter 9 to support the CMM (Capability Maturity Model) for acceptance and wider implications of the requirements engineering framework to be proposed in chapter 8. Chapter 6 explains and particularly focuses on how the requirements engineering activities in the case study projects were handled by highlighting strengths and weaknesses. This will also include the experiences and lessons learnt from these system development practices. The findings from these developments will also be utilized to support the justification of the necessity of a requirements engineering framework for the CIE systems developments. In particular, the following are addressed. • common and shared understanding in requirements engineering efforts, • continuous improvement, • outputs of requirement engineering • reflections and the critical analysis of the requirements engineering approaches in these practices. The premise of chapter 7 is to evaluate and assess the requirements engineering approaches in the CIE case study developments from multiple viewpoints in order to find out the strengths and the weaknesses in these requirements engineering processes. This evaluation will be mainly based on the set of criteria developed by the researchers and developers in the requirements engineering community in order to measure the success rate of the requirements engineering techniques after their implementation in the various system development projects. This set of criteria has already been introduced in chapter 5. This critical assessment includes conducting a questionnaire based survey and descriptive statistical analysis. In chapter 8, the requirements engineering techniques tested in the CIE case study developments are composed and compiled into a requirements engineering process in the light of the strengths and the weaknesses identified in the previous chapter through benchmarking with a Capability Maturity Model (CMM) to ensure that it has the required level of maturity for implementation in the CIE systems developments. As a result of this chapter, a framework for a generic requirements engineering process for CIE systems development will be proposed. In chapter 9, the authors will discuss the acceptance and the wider implications of the proposed framework of requirements engineering process using the CMM from chapter 8 and the key issues from chapter 5. Chapter 10 is the concluding chapter and it summarizes the findings and brings the book to a close with recommendations for the implementation of the Proposed RE framework and also prescribes a guideline as a way forward for better implementation of requirements engineering for successful developments of the CIE systems in the future

SNACH a new framework to support business process improvement.

Business processes are central to any organisation. They coordinate activities, roles, resources, systems and constraints within and across organisational boundaries to achieve predefined business goals. The demand for dynamic business environments, customer satisfaction, global competition, system integration, operational efficiency, innovation and adaptation to market changes necessitates the need for continuous process improvement. In order to adequately respond to these demands, business processes are designed in two approaches: Business Process Re-engineering (BPR) and Business Process Improvement (BPI). This thesis follows the BPI approach which considers existing infrastructure in an organization to improve operational efficiency and achieve organisational goals. Many methodologies have been developed for conducting BPI projects, but they provide little support for the actual act of systematically improving a business process. We adopted case study as the research strategy to examine a collaborative business process, specifically the UK Higher Education Institutions (HEI) admission process. The design science research methodology was used to answer the research questions and satisfy the research objectives. The Map technique was employed to construct the new BPI artefact based on the Mandatory Elements of Method (MEM) from Method Engineering. The new BPI framework comprises of a number of elements to support analysts and practitioners in process improvement activities. We present a novel approach to BPI, the SNACH (Simulation Network Analysis Control flow complexity and Heuristics) framework that supports the actual act of process improvement using a combination of process analysis techniques with integrated quantitative measurable concepts to measure and visualize improvement in four dimensions: cost, cycle time, flexibility and complexity. A simulation technique was employed to analyse the process models in terms of time and cost; and Control Flow Complexity was used to calculate the logical complexity of the process model. A complex network analysis approach was used to provide information about the structural relationship and information exchange between process activities. Using a complex network analysis approach to reduce a process model to a network of nodes and links so that its structural properties are analysed to provide information about the structural complexity and flexibility of the network. To achieve this higher level of abstraction, an algorithm was defined and validated using four disparate process models. The complex network analysis technique is integrated into the SNACH framework and its significance lies in the study of the nature of the individual nodes and the pattern of connections in the network. These characteristics are assessed using network metrics to quantitatively analyse the structure of the network, thereby providing insight into the interaction and behavioural structure of the business process activities. To conclude the design science research process phases, the artefact was evaluated in terms of its effectiveness and efficiency to systematically improve a business process by conducting an experiment using another use case

Context-Aware and Secure Workflow Systems

Businesses do evolve. Their evolution necessitates the re-engineering of their existing "business processes”, with the objectives of reducing costs, delivering services on time, and enhancing their profitability in a competitive market. This is generally true and particularly in domains such as manufacturing, pharmaceuticals and education). The central objective of workflow technologies is to separate business policies (which normally are encoded in business logics) from the underlying business applications. Such a separation is desirable as it improves the evolution of business processes and, more often than not, facilitates the re-engineering at the organisation level without the need to detail knowledge or analyses of the application themselves. Workflow systems are currently used by many organisations with a wide range of interests and specialisations in many domains. These include, but not limited to, office automation, finance and banking sector, health-care, art, telecommunications, manufacturing and education. We take the view that a workflow is a set of "activities”, each performs a piece of functionality within a given "context” and may be constrained by some security requirements. These activities are coordinated to collectively achieve a required business objective. The specification of such coordination is presented as a set of "execution constraints” which include parallelisation (concurrency/distribution), serialisation, restriction, alternation, compensation and so on. Activities within workflows could be carried out by humans, various software based application programs, or processing entities according to the organisational rules, such as meeting deadlines or performance improvement. Workflow execution can involve a large number of different participants, services and devices which may cross the boundaries of various organisations and accessing variety of data. This raises the importance of _ context variations and context-awareness and _ security (e.g. access control and privacy). The specification of precise rules, which prevent unauthorised participants from executing sensitive tasks and also to prevent tasks from accessing unauthorised services or (commercially) sensitive information, are crucially important. For example, medical scenarios will require that: _ only authorised doctors are permitted to perform certain tasks, _ a patient medical records are not allowed to be accessed by anyone without the patient consent and _ that only specific machines are used to perform given tasks at a given time. If a workflow execution cannot guarantee these requirements, then the flow will be rejected. Furthermore, features/characteristics of security requirement are both temporal- and/or event-related. However, most of the existing models are of a static nature – for example, it is hard, if not impossible, to express security requirements which are: _ time-dependent (e.g. A customer is allowed to be overdrawn by 100 pounds only up-to the first week of every month. _ event-dependent (e.g. A bank account can only be manipulated by its owner unless there is a change in the law or after six months of his/her death). Currently, there is no commonly accepted model for secure and context-aware workflows or even a common agreement on which features a workflow security model should support. We have developed a novel approach to design, analyse and validate workflows. The approach has the following components: = A modelling/design language (known as CS-Flow). The language has the following features: – support concurrency; – context and context awareness are first-class citizens; – supports mobility as activities can move from one context to another; – has the ability to express timing constrains: delay, deadlines, priority and schedulability; – allows the expressibility of security policies (e.g. access control and privacy) without the need for extra linguistic complexities; and – enjoy sound formal semantics that allows us to animate designs and compare various designs. = An approach known as communication-closed layer is developed, that allows us to serialise a highly distributed workflow to produce a semantically equivalent quasi-sequential flow which is easier to understand and analyse. Such re-structuring, gives us a mechanism to design fault-tolerant workflows as layers are atomic activities and various existing forward and backward error recovery techniques can be deployed. = Provide a reduction semantics to CS-Flow that allows us to build a tool support to animate a specifications and designs. This has been evaluated on a Health care scenario, namely the Context Aware Ward (CAW) system. Health care provides huge amounts of business workflows, which will benefit from workflow adaptation and support through pervasive computing systems. The evaluation takes two complementary strands: – provide CS-Flow’s models and specifications and – formal verification of time-critical component of a workflow

Introducing requirements engineering into product development : towards systematic user requirements definition

Without knowing the requirements of customers and users, it is difficult to build the right product. Although requirements engineering (RE) is considered a critical activity in product development, the state of RE practices seems to be immature in many organizations. For several years, researchers have tried to understand why so many companies have informal RE processes and why it is so difficult to introduce RE technology into mainstream practice. This thesis investigates how RE can be introduced into organizations that develop market-driven products. The results are based on the experiences gathered from four Finnish organizations that considered it essential to improve their product development processes by investing in RE. To gain a deep understanding of RE process improvement in real product development contexts, we conducted four longitudinal case studies using an action research approach. One of our main findings is that introducing RE into product development appears to involve a cultural change. By this we mean that development personnel need to adopt a new way of thinking and working when defining requirements systematically from the customers' and users' points of view. Furthermore, this cultural change involves such human factors as beliefs, attitudes, motivation, and commitment of development engineers and managers. One way of supporting the cultural change is to define a simple RE process model that links business goals to technical requirements via user needs and user requirements. The purpose of the process model is to give an overview of RE, support communication by providing common terminology, and emphasize the importance of systematic user requirements definition. On the basis of the lessons learned from the four case studies, we also recommend a set of RE practices that support the systematic definition of user requirements. Furthermore, the thesis provides a model of factors that affect organization-wide implementation of RE practices and describes challenges organizations may face when introducing RE into product development. The main conclusion drawn from this work is that changing the perspective from technical requirements to user requirements can be difficult for product development personnel. Furthermore, it can take several years for the cultural change towards systematic user requirements definition to spread throughout the whole product development organization. However, the experiences from the case studies show that the organization-wide adoption of RE practices can be enhanced by offering Just-in-Time training and an RE expert's assistance for development teams when they are defining user requirements for the first time.reviewe

Rationale Management Challenges in Requirements Engineering

Rationale and rationale management have been playing an increasingly prominent role in software system development mainly due to the knowledge demand during system evaluation, maintenance, and evolution, especially for large and complex systems. The rationale management for requirements engineering, as a commencing and critical phase in software development life cycle, is still under-exploited. In this paper, we first survey briefly the state-of-the-art on rationale employment and applications in requirements engineering. Secondly, we identify the challenges in integrating rationale management in requirements engineering activities in order to promote further investigations and define a research agenda on rationale management in requirements engineering.