The characteristics of railway service disruption: implications for disruption management

Rail disruption management is central to operational continuity and customer satisfaction. Disruption is not a unitary phenomenon - it varies by time, cause, location and complexity of coordination. Effective, user-centred technology for rail disruption must reflect this variety. A repertory grid study was conducted to elicit disruption characteristics. Construct elicitation with a group of experts (n=7) captured 26 characteristics relevant to rail disruption. A larger group of operational staff (n=28) rated 10 types of rail incident against the 26 characteristics. The results revealed distinctions such as business impact and public perception, and the importance of management of the disruption over initial detection. There were clear differences between those events that stop the traffic, as opposed to those that only slow the traffic. The results also demonstrate the utility of repertory grid for capturing the characteristics of complex work domains

The Effect of software requirements analysis on project success and product quality

This paper will demonstrate that the general project management principles\u27 regarding requirements analysis also hold true for software development projects. According to conventional project management wisdom, sound requirements analysis and scope definition tends to improve quality planning, thereby reducing project cost and duration, increasing project success and improving the quality of the resulting product. This paper will demonstrate that software development projects tend to challenge this time-proven notion. The paper will also demonstrate that the software development industry pays a high price for these practices by suffering longer project schedules, higher costs and producing poorer quality products by rushing requirements definition and analysis. The practice of unwise attempts to shorten software projects takes away from both the successes of the project and the quality of the resulting product. This demonstration will be accomplished by means of a literature review and an informal survey of various members of the software development industry

Managing Requirements Change the Informal Way: When Saying 'No' is Not an Option

© 2016 IEEE. Software has always been considered as malleable. Changes to software requirements are inevitable during the development process. Despite many software engineering advances over several decades, requirements changes are a source of project risk, particularly when businesses and technologies are evolving rapidly. Although effectively managing requirements changes is a critical aspect of software engineering, conceptions of requirements change in the literature and approaches to their management in practice still seem rudimentary. The overall goal of this study is to better understand the process of requirements change management. We present findings from an exploratory case study of requirements change management in a globally distributed setting. In this context we noted a contrast with the traditional models of requirements change. In theory, change control policies and formal processes are considered as a natural strategy to deal with requirements changes. Yet we observed that "informal requirements changes" (InfRc) were pervasive and unavoidable. Our results reveal an equally 'natural' informal change management process that is required to handle InfRc in parallel. We present a novel model of requirements change which, we argue, better represents the phenomenon and more realistically incorporates both the informal and formal types of change

Managing project scope creep in construction industry

Purpose Project scope creep is a nightmare and nearly intolerable task. Most project managers struggle to curtail the expanse and degree of scope creep. This study examines different likely project scope creep factors associated with the construction industry projects. Design/methodology/approach After many brainstorming sessions with construction stakeholders, several project scope creep factors were identified. Then, a detailed survey was executed in big construction projects of the United Arab Emirates (UAE). The data were analyzed using exploratory factor analysis (EFA) and confirmatory factor analysis (CFA). Findings The results derived and validated five conspicuous factors leading to project scope creep. Respectively, the highest and the lowest impact on project scope appears to be imposed by tasks/specifications and complexity/uncertainty. Practical implications It offers crucial support to the project stakeholders in scrutinizing different factors that stand as hurdles to project success and allows them to seek remedies to resolve them. Originality/value It is among the first study in the region that identifies and validates the factors that hinder construction project success.©2022 Emerald Publishing Limited. This manuscript version is made available under the Creative Commons Attribution–NonCommercial 4.0 International (CC BY–NC 4.0) license, https://creativecommons.org/licenses/by-nc/4.0/fi=vertaisarvioitu|en=peerReviewed

Situation-oriented requirements engineering

The establishment of smart environments, Internet of Things (IoT) and socio-technical systems has introduced many challenges to the software development process. One such main challenge is software requirements gathering which needs to address issues in a broader spectrum than traditional standalone software development. Consideration of bigger picture that includes software, its domain, the components of the domains and especially the interactions between the software and the surrounding domain components, including both human and other systems entities, is essential to gathering reliable requirements. However, most of the traditional Requirements Engineering approaches lack such comprehensive overlook of the overall view. The main objective of this work is to introduce a human-centered approach to Requirements Engineering in order to push the boundaries of traditional concepts to be more suitable for use in the development of modern socio-technical systems in smart environments. A major challenge of introducing a human-centered approach is to effectively identify the related human factors; especially, since each individual has unique desires, goals, behaviors. Our proposed solution is to use the observational data sets generated by smart environments as a resource to extract individual\u27s unique personalities and behaviors related to the software design. The concept of situations defined in our earlier study is used to represent the human and domain related aspects including human desires, goals, beliefs, interactions with the system and the constrained environment. In the first stage of this work, a computational model called situation-transition structure is developed to understand the discrete factors and behavior patterns of individuals through the observational data. During the second stage, the information mined from the situation transition structure is applied to propose new human-centered approaches to support main Requirements Engineering concepts: requirements elicitation, risk management, and prioritization. The pertinence of the proposed work is illustrated through some case studies. The conclusion asserts some of the future research direction

Leadership competencies in the requirements phase of IS/IT development projects

Doutoramento em GestãoWhile the successful implementation of an Information Systems/Information Technology (IS/IT) project is widely recognised as being a key research topic, yet recent surveys continue to show significant failure rates. Inadequate requirements management together with inadequate project management have frequently been identified as the principal causes of failure. As a result, the requirements phase has been considered to be one of the most critical phases of the IS/IT project life cycle, especially in relation to software development projects, where new systems must be defined. Moreover, a review of the literature suggests that management leadership is considered to be one of the most important factors in team, project and organisational effectiveness. Management leadership is regarded as being a vital factor in achieving project success, namely in the field of IS/IT. Further research acknowledges that leadership effectiveness may depend on contingency factors, such as the project type, or the project life cycle phase. However, few studies have focussed on the impact of leadership along the software project life cycle, and the literature review found no study that focusses on any particular phase. This is surprising, as the literature suggests that each phase has specific characteristics which are distinguishable by the activities that must be performed. Thus, this research study aims to integrate all these elements within a framework, through a multiple case study using exploratory research. Therefore, this framework will identify which leadership competencies are considered to be relevant to the requirements phase of software development projects’ life cycle. Contingency factors are also be identified and discussed, as well as their impact on the set of identified competencies. Finally, the practical and theoretical contribution of the results are presented, as well as new insights into the requirements and leadership research streams.O estudo da gestão de projetos de Sistemas e Tecnologias de Informação (SI/TIs) é largamente reconhecido como um tópico de investigação atual e relevante. No entanto, estudos empíricos recentes continuam a demonstrar um elevado nível de falhas no processo. Algumas das principais causas mais frequentemente identificadas envolvem a gestão inadequada de requisitos, bem como práticas inadequadas ao nível da gestão global do projeto. Assim, não é surpreendente que a fase que envolve as atividades dos requisitos seja considerada como uma das mais criticas fases de todo o ciclo de vida dos projetos de SI/TI, nomeadamente dos projetos de desenvolvimento de software onde se define um novo sistema a implementar. Para além disso, a revisão da literatura sugere que a liderança é considerada como um dos fatores mais importantes para a obtenção de eficácia das equipas, dos projetos e ainda das organizações. A liderança da gestão é considerada como um fator vital na obtenção do sucesso do projeto, nomeadamente na área dos SI/TIs. Adicionalmente, a literatura reconhece que a eficácia da liderança depende de fatores contingenciais, tais como o tipo de projeto ou a fase do ciclo de vida a que se aplica. No entanto, apenas uma pequena parte desses estudos focam o impacto da liderança ao longo do ciclo de vida do projeto. Surpreendentemente, não foi encontrado nenhum estudo que foque alguma fase em particular, mesmo considerando que a literatura sugere que diferentes fases têm características e atividades que as distingue das demais. Assim, este projeto de investigação pretende explorar a integração de todos estes elementos num quadro de análise comum, através da execução de múltiplos casos de estudos. Este quadro de análise pretende identificar quais as competências de liderança relevantes para a execução da fase de requisitos do ciclo de vida de projetos de desenvolvimento de software. Também se pretende explorar os fatores contingenciais que influenciam o conjunto de competências encontradas, bem como compreender a forma como isso se processa. Finalmente, são apresentadas as contribuições teóricas e práticas, e ainda enumerados os tópicos de investigação futura decorrentes dos resultados obtidos

FRAMEWORK FOR RELIABILITY, MAINTAINABILITY AND AVAILABILITY ANALYSIS OF GAS PROCESSING SYSTEM DURING OPERATION PHASE

In facing many operation challenges such as increased expectation in bottom line performances and escalating overhead costs, petrochemical plants nowadays need to continually strive for higher reliability and availability by means of effective improvement tools. Reliability, maintainability and availability (RAM) analysis has been recognised as one of the strategic tools to improve plant's reliability at operation phase. Nevertheless, the application of RAM among industrial practitioners is still limited generally due to the impracticality and complexity of existing approaches. Hence, it is important to enhance the approaches so that they can be practically applied by companies to assist them in achieving their operational goals. The objectives of this research are to develop frameworks for applying reliability, maintainability and availability analysis of gas processing system at operation phase to improve system operational and maintenance performances. In addition, the study focuses on ways to apply existing statistical approach and incorporate inputs from field experts for prediction of reliability related measures. Furthermore, it explores and highlights major issues involved in implementing RAM analysis in oil and gas industry and offers viable solutions. In this study, systematic analysis on each RAM components are proposed and their roles as strategic improvement and decision making tools are discussed and demonstrated using case studies of two plant systems. In reliability and maintainability (R&M) analysis, two main steps; exploratory and inferential are proposed. Tools such as Pareto, trend plot and hazard functions; Kaplan Meier (KM) and proportional hazard model (PHM), are used in exploratory phase to identify critical elements to system's R&M performances. In inferential analysis, a systematic methodology is presented to assess R&M related measures

System engineering for radio frequency communication consolidation with parabolic antenna stacking

2020 Fall.Includes bibliographical references.This dissertation implements System Engineering (SE) practices while utilizing Model Based System Engineering (MBSE) methods through software applications for the design and development of a parabolic stacked antenna. Parabolic antenna stacking provides communication system consolidation by having multiple antennas on a single pedestal which reduces the number of U.S. Navy shipboard topside antennas. The dissertation begins with defining early phase system lifecycle processes and the correlation of these early processes to activities performed when the system is being developed. Performing SE practices with the assistance of MBSE, Agile, Lean methodologies and SE / engineering software applications reduces the likelihood of system failure, rework, schedule delays, and cost overruns. Using this approach, antenna system consolidation via parabolic antenna stacking is investigated while applying SE principles and utilizing SE software applications. SE / engineering software such as IBM Rational Software, Innoslate, Antenna Magus, ExtendSim, and CST Microwave Studio were used to perform SE activities denoted in ISO, IEC, and IEEE standards. A method to achieve multi-band capabilities on a single antenna pedestal in order to reduce the amount of U.S. Navy topside antennas is researched. An innovative approach of parabolic antenna stacking is presented to reduce the amount of antennas that take up physical space on shipboard platforms. Process simulation is presented to provide an approach to improve predicting delay times for operational availability measures and to identify process improvements through lean methodologies. Finally, this work concludes with a summary and suggestions for future work