Software Measurement – an overview for CIOs

Software measurement is important because it is hard to manage what you don't measure.  Software work is knowledge work.  It is one of the costliest endeavours undertaken by mankind, with more than 50 million people across the world working in highly paid software roles, and for most of them, their efforts are unmeasured.  Many people don't realise that software size can be measured.  Most other forms of human labour have standardised measures of size and productivity.  But with software work, although suitable metrics exist, they are seldom used.  Industry leaders, educators, executives and even governments have so far been relaxed about [...]

October 5th, 2021|Categories: Blog|

Book recommendations

Some of our favourite books on software: Software Measurement and Estimation Applied Software Measurement: Global Analysis of Productivity and Quality, by Capers Jones The Economics of Software Quality by Capers Jones and Olivier Bonsignour Quantifying Software by Capers Jones Software Estimation: Demystifying the Black Art  by Steve McConnell A Guide to Software Size Measurement (free) by  Charles Symons Software Engineering and coding The Certified Software Quality Engineer Handbook by Linda Westfall Code Complete: A Practical Handbook of Software Construction by Steve McConnell More Effective Agile by Steve McConnell Requirements Work Software Requirements (Developer Best Practices) by Karl Wiegers and Joy Beatty Discovering Real Business Requirements [...]

May 6th, 2021|Categories: Blog|

Product Backlog Refinement – Hyperautomated

Product backlog refinement (PBR) is the continuous process of improving the list of (software) work to be done. PBR is the cornerstone to deciding what must be done and in what order. In this article we describe the main activities of product backlog refinement and how they can be accelerated with ScopeMaster®'s intelligent requirements analyser. Product Backlog Refinement Product Backlog Refinement is the regular activity carried by most or all of the team in a meeting with the goal of preparing activities for the upcoming iteration(s). The key activities are: Clarifying user stories, so that the team has a common [...]

April 10th, 2021|Categories: Blog|

Requirements Engineering – automated

Requirements Engineering - what is it? The activities of requirements engineering typically include following: Requirements elicitation - Discovering needs and wants regarding the software product. Requirements analysis– examining, interpreting and verifying requirements, includes checking for defects, tracing requirements to business objectives.  This can include diagramming. System Modeling - is a form of requirements analysis, it means describing a system with diagrams such as Use Case Diagrams, Entity Relationship Models, Data flow diagrams, Class diagrams, wire frames and other user experience mock ups.  The role of modelling is to describe the system so that a common and consistent understanding is reached by all those involved [...]

March 21st, 2021|Categories: Blog|

Webinar for Software Architects

Register now Join the upcoming webinar hosted by IASA Global (International Association of Software Architects) by Colin Hammond on the value and benefits of hyperautomation of requirements analysis for Software Architects. In this talk Colin Hammond will present hyperautomation of requirements analysis and the benefits that this can bring to software architects. Colin will describe the principles and techniques used and then give some real examples of the kind of insight that this can bring to software architects. He will show how within a set of requirements for a piece of software, the approach can help detect ambiguities, validate of customer need, check [...]

March 19th, 2021|Categories: Press Releases|
Go to Top