Modelling information requirements in complex engineering services

Services based around complex engineering equipment and systems provide substantial challenges in both the long-term management of the equipment and the need for guaranteed delivery of the related service. One of the challenges for an organisation providing these services is the management of the information that is required to design, deliver and subsequently assess the success of the service. To assist in this process this paper develops a model for capturing, organising and assessing information requirements for these Complex Engineering Services in which information required to support key decisions in the life cycle of the service is identified. The model – referred to as The 12-Box Model for Service Information Requirements – is embedded in a three-phase procedure for providing an assessment of information requirements of a service contract which also provides insight into the capabilities of available information systems in supporting the contract. An illustrative example examining service information in an aircraft availability contract is used to demonstrate the use of the 12-Box Model and associated assessment procedure.

Requirements engineering for web-based information systems

This chapter overviews the existing methods of requirements analysis as prescribed by some of the best-known web-development methods. It also discusses the pre-eminent importance of stakeholder analysis, identification of stakeholder views and concerns, and the processes governing elicitation of web systems requirements. The chapter finally derives a model of concern-driven requirements evolution from several case studies undertaken in the area of web-enabled employee service systems.

Critical success factors for the requirements engineering process, with reference to quality management of information systems development

Preliminary research into the critical factors associated with software development/implementation identified three dimensions for successful implementation based on alignment of the requirements engineering process with business needs, change management process and quality of the implementation process. Research results demonstrate the link between the conceptual model for process quality and the process management attributes determined during the research.

Analyzing and defining information requirements of knowledge intensive construction management tasks on BIM

With the increasing popularity and adoption of building information modeling (BIM), the amount of digital information available about a building is overwhelming. Enormous challenges remain however in identifying meaningful and required information from a complex BIM model to support a particular construction management (CM) task. Detailed specifications of information required by different construction domains and expressive and easy-to-use BIM reasoning mechanisms are seen as an important means in addressing these challenges. This paper analyzes some of the characteristics and requirements of component-specific construction knowledge in relation to the current work practice and BIM-based applications. It is argued that domain ontologies and information extraction approaches, such as queries could significantly bring much needed support for knowledge sharing and integration of information between design, construction and facility management.

The Impact of Contract Type on Service Provider Information Requirements

This paper is concerned with the role of information in the servitization of manufacturing which has led to “the innovation of an organisation’s capabilities and processes as equipment manufacturers seek to offer services around their products” (Neely 2009, Baines et al 2009). This evolution has resulted in an information requirement (IR) shift as companies move from discrete provision of equipment and spare parts to long-term service contracts guaranteeing prescribed performance levels. Organisations providing such services depend on a very high level of availability and quality of information throughout the service life-cycle (Menor et al 2002). This work focuses on whether, for a proposed contract based around complex equipment, the Information System is capable of providing information at an acceptable quality and requires the IRs to be examined in a formal manner. We apply a service information framework (Cuthbert et al 2008, McFarlane & Cuthbert 2012) to methodically assess IRs for different contract types to understand the information gap between them. Results from case examples indicate that this gap includes information required for the different contract types and a set of contract-specific IRs. Furthermore, the control, ownership and use of information differs across contract types as the boundary of operation and responsibility changes.

Articulation of information requirements for personalised knowledge and construction

The quality of information provision influences considerably knowledge construction driven by individual users’ needs. In the design of information systems for e-learning, personal information requirements should be incorporated to determine a selection of suitable learning content, instructive sequencing for learning content, and effective presentation of learning content. This is considered as an important part of instructional design for a personalised information package. The current research reveals that there is a lack of means by which individual users’ information requirements can be effectively incorporated to support personal knowledge construction. This paper presents a method which enables an articulation of users’ requirements based on the rooted learning theories and requirements engineering paradigms. The user’s information requirements can be systematically encapsulated in a user profile (i.e. user requirements space), and further transformed onto instructional design specifications (i.e. information space). These two spaces allow the discovering of information requirements patterns for self-maintaining and self-adapting personalisation that enhance experience in the knowledge construction process.

Managing the requirements engineering process

Process management is a crucial issue in developing information or computer systems. Theories of software development process management suggest that the process should be supported and managed based on what the process really is. However, our learning from an action research study reveals that the requirements engineering (RE) process differs significantly from that which the current literature tends to describe. The process is not a systematic, smooth and incremental evolution of the requirements model, but involves occasional simplification and restructuring of the requirements model. This revised understanding of the RE process suggests a new challenge to both the academic and industrial communities, demanding new process management approaches. In this paper, we present our understanding of the RE process and its implications for process management.

Managing the requirements engineering process

Process management is a crucial issue in developing information or computer systems. Theories of software development process management suggest that the process should be supported and managed based on what the process really is. However, our learning from an action research study reveals that the requirements engineering (RE) process differs significantly from what the current literature tends to describe. The process is not a systematic, smooth and incremental evolution of the requirements model, but involves occasional simplification and restructuring of the requirements model. This revised understanding of the RE process suggests a new challenge to both the academic and industrial communities, demanding new process management approaches. In this paper, we present our understanding of the RE process and its implications for process management.

Issues in IT service-oriented requirements engineering

Corporate information technology (IT) management is increasingly service-oriented, offering continuous evaluation and improvement of application, communication, delivery and support services to internal and external customers. Service-oriented requirements engineering (SoRE) plays a significant role in identifying and specifying service requirements, formally defined through service-level agreements (SLAs). However, the new frameworks and approaches emerging to guide these developments have not yet addressed how requirements for such services can be effectively developed, nor identified the diverse issues involved. We report a case study of a web services team development of requirements for an internal Service Desk service. The study revealed five main issues of concern when developing service provider requirements: service roles, responsibilities and accountability; service performance metrics; resolution of conflicting stakeholder service requirements; customer acceptance of service change; and service provider team structure. This study suggests that in the new IT services era, new techniques and approaches are needed for eliciting and determining provider and customer requirements that involve key stakeholder groups equitably and more closely negotiate the sometimes-conflicting provider and customer needs.