Search results

This paper proposes a method for managing client requirements with the use of Building Information Modelling (BIM). The development of healthcare projects demands a large amount of requirements information, in order to deal with a diversity of clients and frequents changes in healthcare services. The proposed method supports healthcare design by adopting a process-based approach for client requirements management, with the aim of improving value generation.

Design Science Research was the methodological approach adopted in this investigation. The main outcome of this study emerged from an empirical study carried out in a healthcare project in Brazil.

The proposed method involves three stages: (1) capturing and processing requirements; (2) product and requirements modelling, which involves the connection between requirements and the BIM 3-D model and (3) supporting design solution refinement, through the communication of requirements and the assessment of design in relation to updated client requirements information.

This study explores client requirements management from a process perspective, proposing activities and their interdependences and possible sources of data, including healthcare services information. The main theoretical contributions are related to the understanding of the nature and complexity of the information involved in client requirements management, and how this can be modelled.

This paper reviews existing business process (BP) modeling languages that are widely used in the industry as well as recent research work on modeling and analysis of BPs in the service-oriented environment and Internetware-based software paradigm. BPs in such environment are different from traditional BPs due to loose coupling of partner services, dynamic and on-the-fly selection of partners and run-time process adaptability. The unique characteristics of these BPs require formal modeling of the requirements and constraints in each phase of their life cycle, including design phase, implementation and deployment phase and execution phase.

The paper first provides a categorization of typical user requirements in each phase of the BP life cycle. Then a detailed comparison of the selected languages with respect to their requirement modeling and analysis capabilities in each of the identified categories is provided. The paper also discusses new requirements engineering research challenges arising from future software needs and emerging trends in software engineering in the context of Web-services-based BPs and Internetware.

There is a need to have a framework that provides support for user requirements modeling and analysis for all the phases of BP life cycle in an integrated manner. Such a framework would be useful not only in resolving the inconsistencies between requirements across phases but also in addressing the issues related to BP evolution due to changes in user requirements over time. Moreover, with the Internet of things (IoT) adoption in BPM, there is a need to have an integrated environment that provides support for capturing the resilience requirements of enterprise BPs as well as the mobility constraints of the underlying IoT devices.

This paper reviews existing BP modeling languages and frameworks and discusses the new requirements engineering research challenges arising from future software needs and the emerging trends in BP management in the service-oriented environment and Internetware-based software paradigm.

Many project failures can be attributed to changes in requirements as the project progresses. The purpose of this paper is to review several system dynamics models of the requirements process from the literature, especially the model of Andersson and Karlsson. This model addresses the deficiencies in the system dynamics model devised hitherto to create a model than can be used to predict requirements acquisition and staff resources for different levels of project complexity and size.

A new control‐theoretic model of requirements gathering is devised using the Software Test Model of Cangussu as a framework. Conventional control system techniques are then used to compute typical responses.

The results agree with the limited published data. This model can be used to predict an estimate of the possible number of requirements that could be devised for the project. It allows the incorporation of workforce, quality and complexity information to predict the time to complete the requirements process. This model is then used to predict how the requirements process responds to requirements creep and to changes in workforce used.

This model is theoretical and is proposed so that it can be simple tested. It makes a number of assumptions not yet recorded by industry that would have to be obtained.

If it is supported by experimental data then a better project development model can be created with the prospect of greater control of project development.

This work, although based on the work of Cangussu et al., is devised by the author.

The main purpose of this paper is to improve a web content management system (WCMS) product line for future implementations by identifying software commonalities in WCMS‐based web applications. WCMS plays a central role in modern web application development: most large public and internal web sites are based on a WCMS foundation. If we can improve the implementation process, the effectiveness and efficiency of web application development will increase significantly.

This research identifies reusable solutions from existing WCMS implementations using problem diagrams and structured goal modeling. From configurations were matched with atomic e‐business models by linking them to the strategic competencies through bottom‐up goal modeling. A designed method was constructed on how requirements can be elicited for WCMS implementations using goal modeling and problem frames.

The resulting method provides insight in relevant e‐business models and their relation to software product lines. Moreover, the approach is applied in a WCMS study which demonstrates its applicability.

The practical implications of this research is twofold: WCMS developers now have a method to improve their product line based on e‐business models; and requirements engineers implementing WCMS can use this model to apply reusable software and prioritize requirements. Both will potentially have a large impact on the effectiveness of implementations since most web applications are developed with WCMS.

The paper presents a novel approach for efficient and effective identification of software commonalities. This research is part of the web engineering method that focuses on development of web applications based on WCMSs.

This paper aims to introduce the goal-oriented requirements extraction approach (GOREA). It is an elicitation approach that uses, specifically, healthcare business goals to derive the requirements of e-health system to be developed.

GOREA consists of two major phases: (1) modelling e-health business requirements phase and (2) modelling e-health information technology (IT) and systems requirements phase. The modelling e-health business requirements phase is divided into two main stages: (1) model e-health business strategy stage and (2) model e-health business environment stage. The modelling e-health IT and systems requirements phase illustrates the process of obtaining requirements of e-health system from the organizational goals that are determined in the previous phase. It consists of four main steps that deal with business goals of e-health system: (1) modelling e-health business process (BP) step; (2) modelling e-health business goals step; (3) analysing e-health business goals step; and (4) eliciting e-health system requirements step. A case study based on the basic operations and services in hospital emergency unit for checking patient against COVID-19 virus and taking its diagnostic testing has been set and used to examine the validity of the proposed approach by achieving the conformance of the developed system to the business goals.

The results indicate that (1) the proposed GOREA has a positive influence on the system implementation according to e-health business expectations; and (2) it can successfully fulfil the need of e-health business in order to save the citizens life by checking them against COVID-19 virus.

The proposed approach has some limitations. For example, it is only validated using one e-health business goal and thus it has to be authenticated with different e-health business goals in order to address different e-health problems.

Many e-health projects and innovations are not established based on robust system requirements engineering phase. In order to ensure the success delivery of e-health services, all characteristics of e-health systems and applications must be understood in terms of technological perspectives as well as the all system requirements.

To provide a more requirements‐driven workload model for eXtensible Markup Language (XML) benchmark over the electronic data exchange and management in collaborative commerce.

A three‐component workload requirements model is formulated. They are the XML object model, the XML query operation model, and the control model. The object model extended from W3C data model gives a set of more generic data and document model. The query model enhanced from current and common benchmarks gives a more generalized set of standard and open queries against XML data and documents. The control model compiled from TPC and industry standards gives a set of more systematic experimental variables and performance metrics to set up and conduct an XML benchmark.

The long‐standing research issues of domain dependency and application irreproducibility of XML benchmarks are addressed, tackled and offered with a novel and computer‐aided alternative. Precision and cost‐effectiveness through a synthetic, standard, and scalable set of requirements‐driven workload model are presented.

XML constructs, constraints, and controls are investigated both in terms of data and documents. Workload formulation from the requirements analysis is explored. In‐depth schema, query, and control model to provide scalability and portability can be applied is developed.

Enterprise information integration over heterogeneous data sources has to be achieved through XML. Performance measurement and evaluation on XML is vital. With a more generic and generalized design, XML benchmark can become the key to the success of B2Bi interoperability and performance.

An origin of requirements‐driven benchmark modeling over collaborative commerce is presented. A novel extension on W3C XML model is created. A innovative enhancement from current XML benchmarks' query model is developed.

This study proposes targeted modernization of the Department of Defense (DoD's) Joint Forces Ammunition Logistics information system by implementing the optimized innovative information technology open architecture design and integrating Radio Frequency Identification Device data technologies and real-time optimization and control mechanisms as the critical technology components of the solution. The innovative information technology, which pursues the focused logistics, will be deployed in 36 months at the estimated cost of $568 million in constant dollars. We estimate that the Systems, Applications, Products (SAP)-based enterprise integration solution that the Army currently pursues will cost another $1.5 billion through the year 2014; however, it is unlikely to deliver the intended technical capabilities.

The IRB capital requirements of Basel II define the minimum level of capital that the bank has to retain to cover the current risks of its portfolio. The major risk that many banks are facing is credit risk and Basel II provides an approach to calculate its capital requirement. It is well known that Pillar I Basel II approach for credit risk capital requirements does not include concentration risk. The paper aims to propose a model modifying Basel II methodology (IRB) to include name concentration risk.

The model is developed on data based on a portfolio of Greek companies that are financed by Greek commercial banks. Based on the initial portfolio, new portfolios were simulated having a range of different credit risk parameters. Subsequently, the credit VaR of various portfolios was regressed against the credit risk indicators such as Basel II capital requirements, modified Herfindahl Index and a non-linear model was developed. This model modifies the Pillar I IRB capital requirements model of Basel II to include name concentration risk.

As the Pillar I IRB capital requirements model of Basel II does not include concentration risk, the credit VaR calculations performed in the present work appeared to have gaps with the Basel II capital requirements. These gaps were more apparent when there was high concentration risk in the credit portfolios. The new model bridges this gap providing with a correction coefficient.

The credit VaR of a loan portfolio could be calculated from the bank easily, without the use of additional complicated algorithms and systems.

The model is constructed in such a way as to provide an approximation of credit VaR satisfactory for business loan portfolios whose risk parameters lie within the range of those in a realistic bank credit portfolio and without the application of Monte Carlo simulations.

The purpose of this paper is to describe and analyze the benefits of the application of a requirements engineering framework to assist Enterprise Resource Planning (ERP) development. This framework combines the technology-driven and the process-driven approaches for requirements analysis and implementation. Specific business process modeling methods enhance the framework and assist the formulation of the functional specifications of the ERP system and the management of requirements.

A case study strategy was chosen as the most appropriate method to answer the research question and test the theoretical propositions. The case study’s unit of analysis is a Greek manufacturing company and its ERP implementation project. A requirements engineering framework enhanced with business process modeling methods was applied and the results were evaluated using metrics for ERP implementation success. Data were collected using multiple sources of evidences, including interviews with various stakeholders, structured questionnaires, direct observations, vendors’ functionality papers and company’s documentation.

This study proves that the configuration of ERP’s reference models together with the adjustments of organization’s processes, provided through a structured requirements engineering framework can lead to reliable functional specifications, a smooth transition to an ERP system and, eventually, to successful ERP implementation, concerning its alignment with requirements.

A single case study is conducted in a typical manufacturing company, providing opportunities for further research in other industries, testing in parallel well-defined requirements and other success factors for ERP implementation.

The paper fulfils the identified needs for applied methodologies and frameworks for requirements engineering which can assist successful ERP implementations.

Successful implementation of a building information modeling (BIM) for building operation and maintenance (O&M) requires purposeful, early-design identification of end-user-specific model exchange requirements. This paper aims to provide a semantic data-rich classification system for model objects to convey facilities management (FM) requirements in BIM guidelines in support of efficient FM-BIM data workflows.

A modularized, repeatable and technical solution for semantic requirements of BIM exchange objects was developed through ontology-based data mapping of the industry foundation classes. The proposed solution further contextualizes syntax per the buildingSMART Data Dictionary schema and provides an implementation agreement to address the quality issues of discipline BIMs and establish consistent modeling and naming conventions to facilitate automated BIM data workflow.

The level of semantics (LOS) development framework and the results of LOS implementation focusing on a building mechanical system case project are presented and discussed to showcase the increased efficiency resulting from its implementation throughout the BIM data management workflows.

This study represents a pioneering effort to create and implement the LOS schema as a modularized solution in support of automatic BIM data creation, adjustment, verification and transition across the design, construction and O&M workflows of a large owner organization in the Midwest USA.