Formal Method Integration with Agile’s Stoyboarding

Agile Storyboarding is an informal method for documenting the software requirements. It is most useful and widely adopted process in agile teams. If we include the formal methods (VDM, Z, Algebraic, OBJ or Ptri Nets) in our case z specification, that can be more effective way of documenting the requirements. To demonstrate it practically I chose the HRIS project. A storyboard was developed by using Microsoft tool storyboard plugin for PowerPoint.

As storyboard gives forest view (high level view) to move the details I used Z specification language for tree view (detail view). As we analyze the forest and move to tree level analysis. Each detail is linked with broader picture, so every module is dependent to each other and gives the complete picture of HRIS software.

Storyboarding requirement elicitation technique is widely used in software industry, A as System analyst experience I use to develop the storyboard for the client and internal stockholders. Requirement analysis and documentation is a first step towards the success journey of project.

As system analyst do the requirement analysis and if formal techniques are used in this phase, although it will take more time and more money will be required in the 1st phase but at the end we will get relief from rework.

Formal techniques are slowly moving and now non-mission critical system are also getting benefit but due to their huge initial cost their progress is very slow in software based solutions. Now requirement engineers want formal methods integration into the requirement phase.

Rather than focusing on preparing the screenshot we should go towards the implementation level details. It will help programmers and if something is missed by system analyst engineers, stakeholders can point out and correction is less costly as compared to after code release.

The formal methods can be integrated seamlessly with storyboarding. In storyboard our focus remains on what factor and if we integrate formal methods we will answer what and How at the same time. As this step requires training, so stakeholders can understand the notations and can interpret and analyze the proposals.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: