Professional Requirements Engineering as a Key Factor for Successful Software Projects


Felix Holzke is Lead Consultant at NTT DATA Germany and specialist for Requirement Engineering in large-scale projects.


NTT DATA is your Innovation Partner anywhere around the world. Headquartered in Tokyo, with business operations in 42 countries, we put emphasis on long-term commitment and
combine global reach and local intimacy to provide premier professional services from consulting, system development to business IT outsourcing.

Dr. Jens Kawelke is Head of the Competence Unit Requirements Engineering at NTT DATA Germany. He consults clients regarding the Requirements Engineering methodology and offers Requirements Engineering training for clients and internal staff.

1.1 Why do IT projects fail?

Alreaday back in 2004 Standish Group [Standish Group (2004). CHAOS Report (Report). West Yarmouth, Massachusetts: Standish Group] found out that the average cost overrun for IT projects was 43 percent and that 71 percent of projects were over budget, time, and under scope.

This cost overrun can be tracked down to the main reason 'scope creep' [https://en.wikipedia.org/wiki/Scope_creep], which simply means not delivering what the business customer had originally in mind and thus causing considerable rework.

In order to prevent that, the project goal and its detailed requirements have to be determined and constantly checked against the customer's ideas. The set of techniques to achieve this is called Requirements Engineering (RE), which also deals with handling other issues leading to project failure such as poor communication or the lack of stakeholder involvement.

In one word: Poor RE is a major cause of project failure.

1.2 Examples of project failure

Let us start with an artificial example of a missing basic requirement: A business customer is asking for an ultimatively-small smart phone to be constructed. Without specifying that the keypad touch screen to enter text and the display must be on the same side of the phone, this not documented requirement might lead to a non-usable smartphone and tons of rework.

One well known real example for poor RE is the accident of the Ariane 5 rocket in 1996 exploding 37 seconds after liftoff. Reason for this was a broken code fragment, which was required on earlier rockets, but was not required anymore after liftoff on Ariane 5. Professional RE would have recognized the code fragment as to be removed, since it did not satisfy any (traceable) requirement.

1.3 How would professional RE improve projects?

As there are numerous additional benefits, we shall focus onsome key points:

- You can better manage scope creep. RE focuses on detailing requirements unambigiuously before putting effort in developing the wrong artifacts or estimating too little effort. This avoids wrong expectations and request for rework and is a big step towards finishing the project "in budget".

- You can better judge the impact of changes. Since the change of requirements in the course of implementing large products is quite inevitable, one should be able to easily derive what parts of the already-built product along with its artifacts such as test cases will have to be modified. Professional RE enables the customer to prioritize his request appropriately.

- The Requirements Engineer speaks the "language" of both - the customer and the programmers. The requirements, gathered from the customer are documented in a structured way so, that the programmers can implement their artifacts straight-away without further time-consuming enquiries to the customer.

- Especially in large software projects, well documented requirements make it easier for new project members to understand functionality that was implemented years ago.

- You can better manage quality assurance. Quality of the software product can be verified through automatically derived test scenarios if requirements have been documented in an appropriate way.

1.4 What is the key success factor in introducing Requirements Engineering in order to improve project success?

In order to achieve better results in RE, organizations should focus on training their business analysts to stick to a common methodology, i.e develop their skills or hire trained people. Most important skills are
  • analytical competencies,
  • active listening,
  • phrasing requirements without ambiguities,
  • communication skills, especially for dealing with conflicts.
Requirements Engineers should introduce, formalize, and standardize RE processes in the organization or at least at project level - regardless of of the development model - waterfall or agile. That is because RE is tightly integrated with other disciplines in the field of software engineering like development, test and operation/maintenance and greatly influences their success.

Especially when it comes to crossing different time zones with many team members, who speak different languages, it becomes more important to document and distribute requirements in a structured and unambiguous way and in writing.

Since RE is an interconnected discipline, it requires top management support for the organization as a whole or at least the project manager.

1.5 What are the disciplines Requirements Engineering deals with?

In order to achive projects goals professional RE contains techniques for

- collecting requirements from different sources like people (stakeholders), existing documents or existing systems. There are many techniques that can be used in different situations, e.g. interviews or observing techniques (stakeholders), system archeology (existing systems), perspective-based reading (existing documents)

- documenting the collected requirements, e.g. by writing unambigiously phrased natural-language sentences in well-structured form that show different perspectives on the IT system to be developed. Or it represents requirements in standardized graphical (UML-based) models that make them easier to understand even by non-trained business users.

- validating that requirements are what the business customer had in mind. Which can be as easy as presenting an automatically-built clickable software prototype derived from the requirements model. Recognizing wrong requirements early, saves costs compared to late recognition when code and test cases have already been created.

- managing requirements through their lifecycle and track how they interconnect from the first idea to the final tested line of code.

The RE techniques [see above graphic] can be considered part of an RE lifecycle since they are applied recurrently and in a strongly iterative manner.

Where is RE located in common Software Engineering Lifecycles? [see figure below]



We see Requirements Engineering as a subdiscipline of Business Analysis (BA). BA also deals with defining requirements of organization processes or needs (business process management), wheras RE deals with detailing the requirements to build an IT system, which helps to achieve those business goals. Sometimes the business process analysis and optimization are considered part of the Software Engineering Lifecycle. In agile projects the steps from RE to Test will be passed through in cycles, in waterfall projects in a linear manner as shown above in [see the above figure].

1.6 How can I "professionalize" Requirements Engineering?

Besides of training people in the aspects mentioned above, external consultants can help to overcome such a skill gap in an organization. Although people with the appropriate Requirements Engineering skills can help to implement the core techniques, it becomes difficult for humans to handle the amount of requirements for large-scaled systems. RE can be supported by various IT tools:

- Requirements from legacy systems can be easily collected using code analysis tools which create graphical representations of legacy COBOL code. These can later be reused for the requirements documentation of a new modern IT system from scratch.

- The whole lifecycle of a requirement can be documented and tracked in a Requirements Management (RM) tool. Compared to Word and Excel documents, RM tools enable you to document and trace an idea either in natural language or with graphical elements up to the test case. And it enables many collaborators to work efficiently in parallel on the overall versioned collection of your company's IT requirements including digital approval processes.

- Requirements validation can effectively be supported by tools that analyze your textual requirements if they are conform to certain rules for well-formulated requirements. It can be as easy as eliminating ambigious words like 'fast', 'flexible', 'simple', or 'robust' which do not quantitatively reflect what is required.

Related articles

photodune-3834701-laughing-girl-xs

How technology impacts the insurance sector

Rather than merely adding value to the insurance sector, technology and technical innovations are now determining its very growth and evolution. The last few years have seen mobile devices, GPS functionality and social media engagement impact hugely as to how insurance claims are processed by companies and policies assessed by insurance agents. Analysis of data and the value of legitimate customer interactions is more important than ever and have helped insurance companies to maximize profits while keeping the customers happy.

2017-08-17
photodune-3834701-laughing-girl-xs

FRISS: Uncovering insurance fraudsters

If you compare the insurance fraud business to other types of business, it pays off to commit insurance fraud. The benefits are great, the chances of being caught are low, and the sanctions you get once caught are low as well. So, whether working in the claims, financial, underwriting or SIU department; you will all deal with fraud at some point. And it does not stop at an organization or a border. Fraudsters do market research. They use different modus operandi, use different insurers, fake identities; just to make sure that they don't get caught.

2017-05-18
photodune-3834701-laughing-girl-xs

Technology and data: Focus on the good we can do

Technology. The press is covering it, everyone is talking about it and we, as an industry, are spending time and money investing in it. For all this reasons and more, we will shortly talk about this topic at our Swiss Re L&H Conference in Warsaw in May: "Think tomorrow! Innovative solutions for our industry."

2017-05-11
photodune-3834701-laughing-girl-xs

Insurance is the industry most affected by disruptive change, according to PwC

Insurance is the industry most affected by disruptive change - based on the percentage of CEOs who are 'extremely concerned' about the threats to growth from over-regulation, the speed of technological change, changing customer behaviour, and competition from new market entrants, shows the 20th edition of the PwC Global CEO Survey.

2017-02-15
photodune-3834701-laughing-girl-xs

Reducing the loss ratio by effectively detecting insurance fraud

Insurance fraud is a serious issue for the entire insurance sector. Payment of fraudulent claims has a negative effect on the loss ratio and on insurance premiums, which results into a competitive disadvantage. Moreover, investigating 'false positives' takes a huge amount of time and unnecessary costs. Fraudsters are getting smarter in their attempts to evade the insurer's radar. As a consequence, money flows to the wrong people and thus combined ratios are under pressure. Insurance companies must detect insurance fraud before claims are paid. The best way to reduce the loss ratio is to increase the chances of fraud detection at claims and limit false positives to a minimum. 

2017-01-26
photodune-3834701-laughing-girl-xs

Innovation - the right response to the technological challenge

The driverless revolution in the auto industry is already buzzing along city streets around the world, in a variety of tests and trials—and not just for cars, but for 18-wheel delivery trucks loaded with beer. Yet the excitement surrounding the emergence of autonomous vehicles tends to overshadow another tech revolution underway: the addition of dynamic cognition layers that will enable cars to care for human comfort, information and entertainment preferences in new and unimagined ways, say the Watson IoT team.

2017-01-19
photodune-3834701-laughing-girl-xs

Jeroen MORRENHOFCEOFRISS

Fraudsters are getting smarter in their attempts to evade the insurer's radar. As a consequence, money flows to the wrong people and thus combined ratios are under pressure. Insurance companies must detect insurance fraud before claims are paid. The best way to reduce the loss ratio is to increase the chances of fraud detection at claims and limit false positives to a minimum.

2016-12-07
photodune-3834701-laughing-girl-xs

Requirements Engineering and Legacy Systems

In order to remain competitive in the market, for example by a fast introduction of new insurance products, the legacy systems have to be modernized or replaced sooner or later. For this task, three alternatives were introduced with their advantages and disadvantages. All alternatives rely on a successful IT-Project.
In order to help them to succeed in time, budget, and scope, the professional application of different Requirements Engineering techniques are a key success factor.

2016-06-30

ON THE MOVE

TOP EVENT

61st "Rendez-Vous de Septembre" ends today in Monte Carlo: review

The 61st edition of the "Rendez-Vous de Septembre", the annual traditional meeting of reinsurers ends today in Monte Carlo. The Nat Cat insurance protection gap, as well as the global insurance market readiness to deal with the increasing complexity of the cyber risks were among the most debated topics.

14.09.2017

photodune-3834701-laughing-girl-xs

MONTE CARLO: Live news from the "Rendez-Vous de Septembre"

The 61st edition of the "Rendez-Vous de Septembre", the annual traditional meeting of reinsurers has started yesterday in Monte Carlo. XPRIMM publications on the CEE, SEE and CIS insurance markets are available at the XPRIMM stand in Fairmont Hotel as well as at the other event's venues.

10.09.2017

See all