Clear Requirements

The Problem

The teacher, or your customer, envisages a house built on a hill, they see this as their requirements. In their mind they understand what they want, they have an inherent understanding of how a house should be oriented.

The pupil,  or supplier, may not have the same inherent understanding and this can disappoint the customer.

House 'on' in the loose sense, a hill
Requirement for a house ‘on’ a hill

The Managed Requirements Solution

Managing requirements, managing expectations, ensuring clear and unambiguous understanding creates a successful project and a happy customer.

Furthermore, following a defined process of elicitation, discussion, refinement and validation will ensure all parties are kept in the picture throughout the process. There should be no surprises.

The stages can be generalised as:

  • recording the Customer requirements (what the teacher said);
  • connecting these to System Requirements (what the pupil thinks is the right way to place a house on the hill);
  • reviewing and verifying with the customer that all is clear and understood (the teacher has a chance to see that the relative orientation has not been considered);
  • correction and update;
  • build and validate;
  • Happy customer!

Equally we live in the real world and thing need and do change. A process needs to cope with and manage those changes. These may be customer initiated, corrections as part of the refinement and understanding stage, or external influences.

Control and Managing Change

This could be through a set of documents, but this is not very scalable. The more complex and numerous the requirements, the more difficult it is to manage the inter dependencies between different parts of the document set.

Imagine the simple case in our example:

  • “The foundations shall comply with building regulation ABC”.

It is easy enough to imagine one chapter with some dimensions for the foundations and one building regulation document.

Remaining with the simplistic house:

  • “Kitchen wiring shall provide one outlet for each of the 12 appliances in accordance with regulation GHI(i)”,
  • “Lounge wiring shall provide a multiple in window bay and one outlet in each of the other corners in accordance with regulation GHI(i)”,
  • “Bedroom 1 shall provide one outlet in each corner of the room in accordance with regulation GHI(i)”,
  • “Bedroom2….”

It is still possible to get your head round the interconnects. It will be a bit more time consuming when GHI(i) is up-released to GHI(ii) and building work hasn’t started and you have to check all the items ordered for the socket outlets still comply in each room.

Conclusion

With a small scale step the complexity the above can soon become unmanageable. Our house may only have seven rooms, but what if these were tens of different compartments on a submarine, hundreds shops owned by a national retailer? GHI(ii)- sub section ‘Public accessible spaces’ is upgraded after a regulatory consultation. How many room specifications are affected?

In a managed solution, a simple report on elements dependent on GHI will give a quick way of calculating the cost impact of altering all the specified outlets. If the power outlets had been categorised when the requirements were written with say Public / Employee / Private access, the number affected, and thus the impact to your customer, could have been further refined.

Article Updated 30/01/2019 – Updated formatting

 

Shoulds and Shalls

Conformance Checker

Do you need to validate the quality of your Requirements?  Using Cradle’s Conformance Checker will help you sort the to sort the “shoulds” from the “shalls”. Validate your items’ text  with a set of regular expressions to ensure you have clear statements.

Picture of conformance checker output
Conformance check your “Shoulds” and “Shalls”

Language Analysis

There are numerous aspects you can search for in the Cradle Conformance Checker.

  1. Stipulations such as Shall and Must
  2. Expectations such as Should
  3. Desires such as Might
  4. Continuations such as  As Follows
  5. Exemplifications such as e.g.
  6. Detractions such as Around
  7. Incompletes such as TBD

These can all be altered to suit your language and product / engineering domain. They are written as Regular Expressions (Regexes) through the project setup.

From Now to Goal – Requirements Management

Goal

If you don’t know where you are currently, or how you arrived or what your ultimate goal is, how do you know in which direction to head? Requirements Management is a skill made easier by the full traceability of tools such as Cradle.

non directional ruler
From – Now – Goal

Build Me a Home

Starting a project without having a base understanding of the situation is a like building a house on unstable foundations. When the walls start to wander you’ll have no idea whether it was because the foundations were not level or were inappropriate or whether the direction of the wall is simply wrong.

Not knowing the ultimate goal could lead to a double height wall being built for a bungalow.

If you have no measure of how high the wall currently stands, you’ll have no chance of estimating how long it will take to finish.

Baseline, Elicit  and Measure

It may sound obvious when applied to the ‘simple’ task of  building a home. It appears ridiculous to start building without knowing whether our goal is a bungalow, house or flat. Yet many projects start with a very loose understanding  between stakeholders and producers and can head off in the wrong direction.

Baseline

Do we know the current situation? Do the foundations exist, is this a single storey  build that needs extending with an upper floor or are we to start from scratch. Are there any assumptions we need to record, this project assumes that there bedrock will be found within a metre.

Elicit Requirements

Have we investigated what the customer / stakeholder actually wants? We could achieve the same m2 with two storeys or one larger floor. No point building a house and then finding mobility restrictions mean a bungalow was needed. Do they actually need a house. The baseline may show they actually have somewhere to live and all they need is some more storage. We could provide them with a shed and achieve their goal. This honesty in not selling them a new house may mean we have a smaller turnover, but a far better reputation. This should lead to repeat and new business as knowledgeable supplier.

Measure

This needs to be done at each stage. Internally we need to know that we are meeting the design. When do we stop building the walls? Externally we need to know that the customer is going to be happy. Milestones and intermediate reviews will prevent big surprises at the end. Whilst we want to avoid requirements creep, we have no intention to build a mansion for the price of a flat, customer requirements change and to remain agile, we need to build in steps to accommodate change.

Summary

If you can see the sense in this simplistic example you have every justification you need to correctly control and manage your project. If you can’t see the point, you’re likely to return to your back of envelope calculations and assumptions of what your customer needs. Good luck to you, but we’d prefer you to take steps to de-risk your plans. Put yourself on the receiving end, a 20 storey building each with a floor of 1m*1m and a ladder pinned to the outside. It fulfils the requirements, but you try sleeping in your new bedsit.

Manual ‘ V’ Cradle

Compare

When it comes to managing your requirements  and designs there really is no contest between a manual based system and a tool based system.  A cross referenced and baselined design in Cradle is your ultimate goal.

Manual

A manual based system at worst is a set of paper requirements, managed in folders with paper-clips and sticky notes. An electronic system may include a number of word processor documents, drawings and spreadsheets. These have very limited, or manually updated meta data to describe how they interlink.

RM tool

A Requirements Management and Systems Engineering software tool brings these elements together in one place and provides the meta data and traceability that binds them together into a successful project.

 

Paper and pencil versus Cradle
Manual versus Cradle

B2B Supply Chain, A Requirements Management Task?

Scenario

“Good morning, are our Wonder Widgets ready yet?”

“Urm, Yes…., I think so, I’ll just check with packaging”

“If you could just include your conformance report with the consignment, that would be great”

“Report, yes, I’ll add one…”

Image of the conformance checker window
Conformance Checker

“Great, that just gives my team the confidence that everything from the mechanical safety standards to the power unit’s supply duration are all up to scratch. We’re happy to pay the extra for a fast courier if that means they will be here tomorrow”

“Mmm, power unit! urm, I’ll get on to it… Bye”

Dissecting the problem

Oh dear, wasn’t it clear that the power unit was part of the sourcing deal? Did you just forget? What was the required duration? Where can I source 300 on a Thursday afternoon?

Managing a supply chain is just like managing the individual requirements of an in-house project. Just because you don’t manufacture each item doesn’t mean you don’t have to manage its specification, purchase and conformance. Changes to your customer’s original specification need to be managed all along the chain. That’s only possible if the links are clearly defined.

By importing your customer’s original documentation as a set of requirements, creating items from your supplier’s specifications and linking them together you can ensure complete coverage of your project’s vital obligations.

Trace and control your customer’s needs with your supplier’s products, commodities, crops or services and ensure you’re not the weakest link in the supply chain.

January 2017 Newsletter

Happy New Year

3SL would like to wish all our customers, partners and suppliers a happy and fruitful 2017.

We hope you are all back to work and busy using Cradle-7.1.2 for your design, requirements management. If you’ve not got the latest version for the start of the year head over to www.threesl.com, login to your account and download it from the Software part of the Resources area in our website here.

If you install Cradle-7.1.2 clients don’t forget to update the server too and visa versa!

Role for RM and SE Tools

We obviously love the fact that Cradle is used on such a diverse set of projects within a huge range of companies. Some customers have fully embraced integrated thinking and manage every aspect of their project with appropriate tools. However, we also know there are pockets of Cradle being used in isolation in engineering departments and disparate projects dotted around our customers’ sites, where unfortunately the wider organisation, their suppliers and customers are just not as tuned into well balanced control and design.

If you find yourself in that situation you may like to use the details in our set of white papers dealing with the uses of information systems in engineering. A paper dealing with the role of RM and SE tool scan be seen here.

Agile Controls

3SL in Australia is distributed by our new partners at Agile Controls.

We are thrilled to announce they have recently signed up their first major customer, we wish them continued success in 2017 and look forward to supporting Cradle’s ‘down under’.

They can be contacted at:

Agile Controls,
108A Tregarthen Road,
Ashton
australia@threesl.com
+61 427 975 674

Twitter Tips

Sometimes you don’t have time to digest all the information in a newsletter. 3SL often tweet simple usage tips that can make a difference when learning all the capabilities of Cradle.

For example:

Confused about which symbol is which? Hover to see a tool tip or select Draw button from Tools ribbon.

tweetClick to view this post or followfollow @threesl if you want to chat about #Cradle or #3SL don’t forget to use an appropriate #tag

Sharing With Others – Web Publisher

When you need a static intranet version of your project, a version you can place on a CD or pen-drive and ship then consider Cradle’s Web Publisher. This allows you to publish your project to a linked set of html pages that can be packaged up and sent to anyone with a browser. You could of course publish parts as a paper report, or as a more complete document with Document Publisher. However, the simplicity of being click a symbol on a diagram and be taken to the specification behind it provides a simple way to share your data with other parties. Of course if you are able to enlighten your customer or supplier, then 3SL will happily demonstrate the full benefits of Cradle and then you can share exports or a common project database.

Rationale for RM and SE Tools

We are pleased to release a new presentation that discusses the need and role for requirements management (RM) and systems engineering (SE) tools and the need for a change in paradigm from document-based processes to data-based processes.

It is available here:

https://www.threesl.com/downloads/download.php?version=v7.1&section=presentations&filename=rr01106-UK_SE_Tool_Rationale.pptx

And as a short link here:

http://ow.ly/4nfxU1

Please visit the Resources section of our website: www.threesl.com for this and many other useful resources!

We hope that this presentation is helpful to those considering RM and SE tools!