Jump to content

Draft:James Robertson (software engineer)

From Wikipedia, the free encyclopedia
James Robertson Software Engineer

James Robertson (1944) is an Australian software engineer and author specializing in requirements analysis. He is the lead developer of the Volere requirements method[1] and Volere Requirements Templates[2]. He is a Member of The Atlantic Systems Guild.[3]. He is (with co-authors) winner of the 2009 Jolt Award for best published software development book of the year.[4]

Volere

[edit]

Volere is the umbrella name given to a collection of resources for discovering and managing software requirements. It includes a requirements discovery process, elicitation techniques, a template for writing specifications, a template for formulating individual requirements, and spreadsheets for managing stakeholders, and other contributors.

As a proposed standard framework for requirements engineering,[5] Volere has been adopted by at least one project at more than sixty companies and government organization worldwide.[6] including the European Space Agency's Flight Dynamics Division,[7] the European Union's CPSwarm project,[8] and other organizations doing critical rquirements engineering.[9] Volere has been proposed as a viable tool for scenario and Use-case analysis.[10][11][12] As Richard Mateosian has written, "Given the frequent disconnect between 'what the customer wanted' and 'what the engineers built' , most companies would benefit greatly from improving the way they define requirements . . . . The Volere process turns customers’ wishes into a usable specification document."[13]

Volere is included as a requirements engineering resource for use within The Open Group Architecture Framework (TOGAF).[14][15][16]

Among Volere's cited strengths, is its adaptability for inclusion in custom requirement engineering frameworks such as Sentire,[17] or Hydra.[18] "This requirements process is independent of the actual systems development methodology that can be deployed. Due to its iterative and evolutionary approach Volere could be effectively used with a RAD (Rapid Application Development) methodology which can be similarly iterative."[19]

One component of the framework, the Volere Shell (or "snow card") is used to describe lowest-level requirements, those that cannot be further decomposed into smaller elements. The shell is more widely used than other parts of the framework. as it fits readily into requirements engineering frameworks of all kinds, since all have need of precise description of elemental requirements. Characteristics of the Volere Shell include its unique focus on "fit criteria," which within Volere translates to a statement of how fit to the purpose of a given elemental requirements can be demonstrated empirically when the system is built. As developers of one multi-national project report, "the categorizations of the Volere template require [us] to define fit criteria, a rationale for each requirement and the evaluation of customer satisfaction and dissatisfaction if the requirement is implemented or not. All this has proven to be of great practical value."[18]

The Volere fit criteria provide a mechanism for requirements-time metrics, as reported by Maiden[20] and in Paul Crowther's chapter of Advances In UML And XML-Based Software Evolution.[21] In addition, the shell "affords traceability, both in where a requirement originates and where it appears in later documentation such as use cases. When used correctly and filled out completely, it encourages the originator of a requirement to study the detail of the requirement, justify the requirement, consider how it relates to other requirements, and how a tester can evaluate or test the requirement."[22]

Published works

[edit]

Robertson is author or co-author of the following works:

  • Business Analysis Agility: Delivering Value, Not Just Software with co-author Suzanne Robertson, Addison-Wesley Professional; 1st edition (November, 2018)[1]
  • Mastering the Requirements Process with co-author Suzanne Robertson, Addison-Wesley Professional; 4rd edition (2024)[23]
  • Requirements-Led Project Management with co-author Suzanne Robertson, Addison Wesley Professional (August, 2004)[24]
  • Adrenaline Junkies and Template Zombies: Understanding Patterns of Project Behavior with co-authors Tom DeMarco, Peter Hruschka, Steve McMenamin and Suzanne Robertson, Dorset House (March, 2008). Winner of the 2009 Jolt Award.[25]
  • Happy to Work Here: Understanding and Improving the Culture at Work with co-authors Tom DeMarco, Peter Hruschka, Steve McMenamin and Suzanne Robertson. New Atlantic (2021)[26]
  • Complete Systems Analysis: The Workbook, the Textbook, the Answers with co-author Suzanne Robertson, Dorset House; 1st edition (January, 1998)[27]

References

[edit]
  1. ^ a b Robertson, James; Robertson, Suzanne (2018). Business Analysis Agility: Delivering Value, Not Just Software. Addison-Wesley Professional. ISBN 978-0134847061.
  2. ^ "Volere Requirements Resources".
  3. ^ "The Atlantic Systems Guild".
  4. ^ "List of Jolt Award winners 1991-2011".
  5. ^ Cleland-Huang, Jane (March–April 2014). "Don't Fire the Architect! Where Were the Requirements?". IEEE Software. 31 (2): 27–29. doi:10.1109/MS.2014.34.
  6. ^ "Experiences of Volere Users".
  7. ^ Faily, Shamal (2008). "Towards Requirements Engineering Practice for Professional End User Developers: A Case Study". 2008 Requirements Engineering Education and Training. pp. 38–44. doi:10.1109/REET.2008.8. ISBN 978-1-4244-4086-3. {{cite book}}: |journal= ignored (help)
  8. ^ "CPSwarm" (PDF). CPSwarm: A Horizon 2020 Project.
  9. ^ Duboc, Leticia; McCord, Curtis; Becker, Christoph; Ahmed, Syed Ishtiaque (January–February 2020). "Critical Requirements Engineering in Practice". IEEE Software. 37: 17–24. arXiv:1910.01678. doi:10.1109/MS.2019.2944784.
  10. ^ de Silva, Alberto Rodrigues (2021). "Linguistic Patterns, Styles, and Guidelines for Writing Requirements Specifications: Focus on Use Cases and Scenarios". IEEE Access. 9: 143506–143530. Bibcode:2021IEEEA...9n3506S. doi:10.1109/ACCESS.2021.3120004.
  11. ^ Cockburn, Alistair (2001). Writing Effective Use Cases. Addison-Wesley.
  12. ^ Maiden, Neil; Jones, Sarah; Flynn, Mary (2003). "Integrating RE methods to support use case based requirements specification". Journal of Lightwave Technology. pp. 369–370. doi:10.1109/ICRE.2003.1232790. ISBN 0-7695-1980-6.
  13. ^ Mateosian, Richard (September–October 2001). "Managing development". IEEE Micro. 21 (5): 86–87. doi:10.1109/MM.2001.958702.
  14. ^ "Guide to Security Architecture in TOGAF ADM" (PDF).
  15. ^ Evernden, Roger. "Guideline – Volere Requirements Specification".
  16. ^ Phélizon, Renaud (April 2012). "Integrating Volere with TOGAF for Requirements Management". The Open Group Conference, Cannes, France.
  17. ^ Porter, Chris; Letier, Emmanuel; Sasse, M. Angela (2014). "Building a National E-Service using Sentire: A Volere-based requirements framework driven by calibrated personas and simulated user feedback". IEEE 22nd International Requirements Engineering Conference, Karlskrona, Sweden.
  18. ^ a b Prause, Christian; Scholten, Marius; Zimmermann, Andreas; Reiners, René; Eisenhauer, Markus (2008). "Managing the Iterative Requirements Process in a Multi-National Project using an Issue Tracker". IEEE International Conference on Global Software Engineering.
  19. ^ Seltsikas, Philip; Papas, Nikolaos (2009). "Developing User Requirements for Trans-national Government Information Systems". Proceedings of the 42nd Hawaii International Conference on System Sciences.
  20. ^ Maiden, Neil (November–December 2006). "Improve Your Requirements: Quantify Them". IEEE Software. 23 (6): 68–69. doi:10.1109/MS.2006.165.
  21. ^ Yang, Hongji (2005). Advances In UML And XML-Based Software Evolution. Igi Global. ISBN 978-1591406211.
  22. ^ Hatley, Debra; Nuseibeh, Bashar; Sharp, Helen; Taylor, Josie (January 2008). "Managing Requirements for Mobile Learning". a MOBIlearn project …. Academia.
  23. ^ Robertson, James; Robertson, Suzanne (2024). Mastering the Requirements Process. Addison-Wesley Professional. ISBN 978-0-321-81574-3.
  24. ^ Robertson, James; Robertson, Suzanne (2004). Requirements-Led Project Management. Addison-Wesley Professional.
  25. ^ DeMarco, Tom; Hruschka, Peter; Lister, Timothy R.; McMenamin, Steve; Robertson, James; Robertson, Suzanne (2013). Adrenaline Junkies and Template Zombies. Addison-Wesley Professional. ISBN 9780133492279.
  26. ^ DeMarco, Tom; Hruschka, Peter; Lister, Timothy R.; McMenamin, Steve; Robertson, James; Robertson, Suzanne (2021). Happy to Work Here: Understanding and Improving the Culture at Work. New Atlantic.
  27. ^ Robertson, James; Robertson, Suzanne (1998). Complete Systems Analysis: The Workbook, the Textbook, the Answers. ISBN 978-0932633507.
Retrieved from "https://wiki.riteme.site/w/index.php?title=Draft:James_Robertson_(software_engineer)&oldid=1231208652"