Signoff – Challenges and how to approach them ?

Requirement sign off is one of the key milestone on the Software Development Life Cycle and often considered as a dreaded milestone by the approvers or the signing authority.

Before we move on see why this is considered that way, and how do we approach this, let’s understand, why an approval is required on the requirement package.

Why  sign-off is required?

When a requirement is presented for the sign-off, the requirement is basically the business analyst’s understanding of the scope, business requirements etc. Obtaining a sign-off ensures that the stakeholders goes through the understanding that the Business analyst have and fill up the gaps if any; that way, ensures that the solution requirements are captured and will be delivered in the right direction (this is the first step towards building the right product). This also helps in resolving any conflict that may arise in future where the stakeholder may change their mind on the requirement and the construction has already begun.

Why this is considered a dreaded milestone?

Continue reading

Traceability

What is traceability ?

The relative form of ‘Traceable’; the dictionary meaning says “capable of being traced” i.e. the series of footprints, the track or the path, anything which can help what we are looking for. On the software engineering, an important aspect is ‘trace the requirement’.

So, what is the need to ‘trace the requirement’? because there is a possibility, that on the subsequent phases of the development and testing we may miss the track and that way we reach to a destination (product), we are not suppose to (deliver). Either, we move on a completely off the track, stopped before the destination (missing requirement) OR moved ahead of the same (deliver extra functionality), not realizing, we have already crossed our destination long back. So, traceability helps sticking to the track and the destination.

Speaking specifically on the requirements aspect, traceability is all about discovering and maintaining relationships between important facets of Requirement, such as the following:

Continue reading