RDRay Dawson

Ray Dawson

*This is an algorithmically generated author record based on publicly available information.

Current Organizations / Institutes

The organizations/institutes from the scholar's latest article


Ray Dawson has a total of 9 co-authors. Here are the top co-authors by number of shared publications:


Latest Publications

  • Open Access

    Repetition between stakeholder (user) and system requirements

    by Richard Ellis-Braithwaite, Russell Lock, Ray Dawson, Tim King


  • Open Access

    Towards an Approach for Analysing the Strategic Alignment of Software Requirements using Quantified Goal Graphs

    by Richard Ellis-Braithwaite, Russell Lock, Ray Dawson, Badr Haque

    Analysing the strategic alignment of software requirements primarily provides assurance to stakeholders that the software-to-be will add value to the organisation. Additionally, such analysis can improve a requirement by disambiguating its purpose and value, thereby supporting validation and value-oriented decisions in requirements engineering processes, such as prioritisation, release planning, and trade-off analysis. We review current approaches that could enable such an analysis. We focus on Goal Oriented Requirements Engineering methodologies, since goal graphs are well suited for relating software goals to business goals. However, we argue that unless the extent of goal-goal contribution is quantified with verifiable metrics, goal graphs are not sufficient for demonstrating the strategic alignment of software requirements. Since the concept of goal contribution is predictive, what results is a forecast of the benefits of implementing software requirements. Thus, we explore how the description of the contribution relationship can be enriched with concepts such as uncertainty and confidence, non-linear causation, and utility. We introduce the approach using an example software project from Rolls-Royce.

  • Lessons Learned from Lessons Learned

    by Lucy Rhodes, Ray Dawson

    This paper describes a case study, examining the problems of capturing, disseminating and benefiting from lessons learned from projects within the project management department of a large, information‐intensive organisation. A set of recommendations to improve the organisation's involvement with ‘lessons learned’ is derived, and how these recommendations are relevant to a wider range of organisations is considered. The literature associated with lessons learned was used to direct research into the project management department of the selected organisation through the use of focus groups and questionnaires to determine why their lessons learned process is not as effective as required. The key barriers to lessons learned were found to be culture, motivation and a lack of process. Furthermore, a large percentage of the project management community was found to be unaware of any lessons learned system and found it hard to access and share lessons with other project managers. The paper therefore provides a set of recommendations to overcome these barriers concerning immediate actions and strategies for the future. The recommendations have received very positive feedback from the employees of the organisation. The paper concludes that the provided recommendations are adaptable to a wide range of organisations. Copyright © 2013 John Wiley & Sons, Ltd.


  • Open Access

    Modelling the Strategic Alignment of Software Requirements using Goal Graphs

    by Richard Ellis-Braithwaite, Russell Lock, Ray Dawson, Badr Haque

    This paper builds on existing Goal Oriented Requirements Engineering (GORE) research by presenting a methodology with a supporting tool for analysing and demonstrating the alignment between software requirements and business objectives. Current GORE methodologies can be used to relate business goals to software goals through goal abstraction in goal graphs. However, we argue that unless the extent of goal-goal contribution is quantified with verifiable metrics and confidence levels, goal graphs are not sufficient for demonstrating the strategic alignment of software requirements. We introduce our methodology using an example software project from Rolls-Royce. We conclude that our methodology can improve requirements by making the relationships to business problems explicit, thereby disambiguating a requirement's underlying purpose and value.

  • An analysis of software quality management at AWE plc.

    by Michael Elliott, Ray Dawson, Janet Edwards