Influence of stakeholder communication on consensus making in requirements negotiation

Consensus building is essential in aligning multiple stakeholder viewpoints which are commonly emerging during the process of requirements elicitation, analysis and validation [15]. In fact, agreement among diverse groups of stakeholders is deemed prerequisite to establishing project cooperation and collaboration. While individuals frequently rank the importance of their personal goals over the goals of an organisation, having an appropriate strategy for finding common ground among individuals is crucial to any project's success. This paper therefore explores factors that influence the consensus making process and develops a model that helps with understanding the role of consensus specifically during the elicitation phase of the Requirements Engineering process.

Creativity, requirements and perspectives

Is there room for more creativity in information systems? This article grew out of an AWRE'04 panel discussion on creativity in requirements engineering, and the impact of requirements engineering on creativity in systems engineering and systems use. Both panel and article were motivated by the goal of identifying a framework for understanding creativity in a larger context and thus establishing a potential structure for future research. The authors' research backgrounds differ widely and, at times, our views conflict occasionally, quite sharply. We make underlying world views - our own and those of relevant disciplines - explicit; identify the paradox caused by the need to be functionally creative while leaving room for creativity in successive stages; and argue for a multi paradigm framework for resolving this paradox.

GUITAR: An ontology-based automated requirements analysis tool

Combining goal-oriented and use case modeling has been proven to be an effective method in requirements elicitation and elaboration. However, current requirements engineering approaches generally lack reliable support for automated analysis of such modeled artifacts. To address this problem, we have developed GUITAR, a tool which delivers automated detection of incorrectness, incompleteness and inconsistency between artifacts. GUITAR is based on our goal-use case integration meta-model and ontologies of domain knowledge and semantics. GUITAR also provides comprehensive explanations for detected problems and can suggest resolution alternatives.

Investigating factors influencing the perception of creativity in web design

In many disciplines, creativity has been recognised as an important part of problem solving. In business, creativity enables the generation of better solutions and provides an opportunity to gain a competitive advantage. In Information Systems (IS) creativity assists developers in finding solutions to difficult problems by helping to efficiently utilise available resources and allows the more effective planning and running of complex projects. One of the most important aspects of IS development is Requirements Engineering (RE), the development activity aimed at understanding the needs and wants of IS customers. While previous RE researchers suggested that creativity is crucial in building high quality information systems, fostering creative outcomes in RE is difficult as it is affected by the multifaceted socioorganisational context within which IS development commonly takes place. This paper reports findings from an empirical study into creativity in RE. Specifically, it reports various contextual factors which were found to influence the creativity of individuals and their teams.

Global software development : the next RE frontier?

Requirements Engineers face an emerging set of challenges, which compound the traditional Requirements Engineering (RE) challenges (stakeholder identification, domain expertise, communication, analytic skills, problem solving, ...) that have arguably still not been fully addressed. This is the challenge of RE in the world of global software development, with requirements teams working in virtual mode (possibly on different continents), with the software having to operate in multiple contexts, addressing the needs of different cultures and legal jurisdictions, and having to build sales in different marketplaces. Further the need arises to specify software that is progressively enhanced through regular releases, rather than the “green field” specification of products.

This theoretical paper introduces these challenges, and presents an initial selection of theoretical models, drawn from many and varied source disciplines, which might be employed to gain insight into various features of RE in support of global software development. To illustrate the potential relevance of this selection of models, a longitudinal case study with a recently identified software developer, to follow the specification and subsequent roll-out of a future release of a software product for sale globally, is introduced. Features of the situation faced by that organisation are highlighted, to illustrate the potential relevance of the diverse models that have been identified.

Using constructivist experiential simulations in RE education

Experiential simulations have been used effectively for teaching business, medicine and engineering. Many are supported by computer systems that create artificial virtual spaces so learners can safely practice intricate professional skills. Surprising few attempts have been made to utilise such approaches in teaching IT/IS principles and requirements engineering (RE) in particular. This paper reports on FAB ATM, which is one of those few learning environments which rely on computer simulation and which have been designed specifically to train IS professionals, and in particular, develop their RE skills. In its framework, FAB ATM combines and balances elements of video-based computer simulation with activities, such as classroom instructions. This paper explains the principles of the FAB ATM design, its coverage of RE activities and the anecdotal experiences of students and staff that have used this environment in practice.

Touch it, feel it and experience it: developing professional IS skills using interview-style experiential simulations

The IS education field has made increasing use of computerised experiential simulations, but few attempts have been made to create an authentic learning environment that combines and balances elements of video-based computer simulation with real-life learning activities. This paper explores the design principles used to develop a CD-ROM simulation where learners use interviewing skills to elicit system requirements from simulated employees in an authentic context. The employees are videoed actors who converse with each other and with learners within a dynamic interaction model. The paper also describes how we combined this simulation with other teaching approaches such as in-class discussions, student team work, formal presentations, etc.

Incorporating design explanation within formal object-oriented method (FOOM)

Requirements engineering is a commencing phase in the development of either software applications or information systems. It is concerned with understanding and specifying the customer's requirements of the system to be delivered. Throughout the literature, this is agreed to be one of the most crucial and, unfortunately, problematic phases in development. Despite the diversity of research directions, approaches and methods, the question of process understanding and management is still limited. Among contemporary approaches to the improvement of the current practice of Requirements Engineering, Formal Object-Oriented Method (FOOM) has been introduced as a new promising solution. The FOOM approach to requirements engineering is based on a synthesis of socio-organisational theory, the object-oriented approach, and mathematical formal specification. The entire FOOM specification process is evolutionary and involves a large volume of changes in requirements. During this process, requirements evolve through various forms of informal, semi-formal, and formal while maintaining a semantic link between these forms and, most importantly, conforming to the customer's requirements. A deep understanding of the complexity of the requirements model and its dynamics is critical in improving requirements engineering process management. This thesis investigates the benefits of documenting both the evolution of the requirements model and the rationale for that evolution. Design explanation explains and justifies the deliberations of, and decisions made during, the design activity. In this thesis, design explanation is used to describe the requirements engineering process in order to improve understandability of, and traceability within, the evolving requirements specification. The design explanation recorded during this research project is also useful in assisting the researcher in gaining insights into the creativity and opportunistic characteristics of the requirements engineering process. This thesis offers an interpretive investigation into incorporating design explanation within FOOM in order to extend and advantage the method. The researcher's interpretation and analysis of collected data highlight an insight-driven and opportunistic process rather than a strictly and systematically predefined one. In fact, the process was not smoothly evolutionary, but involved occasional 'crisis' points at which the model was reconceptualised, simplified and restructured. Therefore, contributions of the thesis lie not only in an effective incorporation of design explanation within FOOM, but also a deep understanding of the dynamic process of requirements engineering. The new understanding of the complexity of the requirements model and its dynamics suggests new directions for future research and forms a basis for a new approach to process management.

Fuzzy concepts and formal methods

It has been recognised that formal methods are useful as a modelling tool in requirements engineering. Specification languages such as Z permit the precise and unambiguous modelling of system properties and behaviour. However some system problems, particularly those drawn from the information systems problem domain, may be difficult to model in crisp or precise terms. It may also be desirable that formal modelling should commence as early as possible, even when our understanding of parts of the problem domain is only approximate. This thesis suggests fuzzy set theory as a possible representation scheme for this imprecision or approximation. A fuzzy logic toolkit that defines the operators, measures and modifiers necessary for the manipulation of fuzzy sets and relations is developed. The toolkit contains a detailed set of laws that demonstrate the properties of the definitions when applied to partial set membership. It also provides a set of laws that establishes an isomorphism between the toolkit notation and that of conventional Z when applied to boolean sets and relations. The thesis also illustrates how the fuzzy logic toolkit can be applied in the problem domains of interest. Several examples are presented and discussed including the representation of imprecise concepts as fuzzy sets and relations, system requirements as a series of linguistically quantified propositions, the modelling of conflict and agreement in terms of fuzzy sets and the partial specification of a fuzzy expert system. The thesis concludes with a consideration of potential areas for future research arising from the work presented here.

Ontology-based automated support for goal–use case model analysis

Combining goal-oriented and use case modeling has been proven to be an effective method in requirements elicitation and elaboration. To ensure the quality of such modeled artifacts, a detailed model analysis needs to be performed. However, current requirements engineering approaches generally lack reliable support for automated analysis of consistency, correctness and completeness (3Cs problems) between and within goal models and use case models. In this paper, we present a goal–use case integration framework with tool support to automatically identify such 3Cs problems. Our new framework relies on the use of ontologies of domain knowledge and semantics and our goal–use case integration meta-model. Moreover, functional grammar is employed to enable the semiautomated transformation of natural language specifications into Manchester OWL Syntax for automated reasoning. The evaluation of our tool support shows that for representative example requirements, our approach achieves over 85 % soundness and completeness rates and detects more problems than the benchmark applications.

Automatic acceptance test case generation from essential use cases

Requirements validation is a crucial process to determine whether client-stakeholders' needs and expectations of a product are sufficiently correct and complete. Various requirements validation techniques have been used to evaluate the correctness and quality of requirements, but most of these techniques are tedious, expensive and time consuming. Accordingly, most project members are reluctant to invest their time and efforts in the requirements validation process. Moreover, automated tool supports that promote effective collaboration between the client-stakeholders and the engineers are still lacking. In this paper, we describe a novel approach that combines prototyping and test-based requirements techniques to improve the requirements validation process and promote better communication and collaboration between requirements engineers and clientstakeholders. To justify the potential of this prototype tool, we also present three types of evaluation conducted on the prototpye tool, which are the usability survey, 3-tool comparison analysis and expert reviews.

A preliminary study on building demolition engineering and management

In recent years, building demolition has been challenging urban developers due to the increased incidence of demolition projects and the elevation of demolition requirements. The importance of building demolition is also recognised by researchers and, given its environmental impacts, it is anticipated to achieve the same attention as conventional planning, design,
construction and maintenance in the near future. In this article, the authors aim to develop a series of strategies for promoting building demolition practice. Environmentally-friendly demolition procedures are introduced through a waste minimisation decision that makes the approach on alternatives to demolition and an integrated demolition planning and design approach focus on a just-in-time (JIT) philosophy. A conceptual management framework is also presented for the implementation of demolition projects.

A Euro-American-Australian study of the mechanical engineering profession as a foundation for the study of mechanical engineering attributes

The increasing attribute focus in the formation (engineering education, training, work-based learning and experience) of engineers now being adopted by engineering education accrediting bodies is based on meeting the perceived needs of professional practice. Related to this is an increasing expectation of new graduates being work-ready rather than relying on work-based learning and experience to develop many of the essential professional practice attributes.

The scope of the mechanical engineering profession is broad and practitioners contributing to debate on attribute requirements have their own individual views of the nature of the profession, largely influenced by their own professional formation. As a foundation for detailed study on attribute requirements for effective Australian professional mechanical engineers, in this paper we provide a concise study of the development of the established scope of practice and knowledge base of the profession over the last two centuries. Formation practices in Europe and the United States played significant roles in the 19th century.

We conclude with a discussion on the impact of the considerable changes currently affecting mechanical engineering practice in the UK, US and Australia, including organisational, technical and societal expectations, industry profile, and educational factors.