Skip to main content

Usecase Scenario development and User Stories


A common comic mail circulates with this image, which gives good understanding of how requirements captured during a project life cycle goes like this:


Typical Software Development Life-cycle explained

Above picture succinctly tells about common perception of developing a software, how requirement understanding filters with changing roles, time and space with gaps between factual and results. Thanks to the  the word "agility", which has evolved in world of software technology with the evolution of Rational unified process the term use-case or scenario development for documenting and capturing requirement in the initial phase of software development.



"A use case is a software artifact of systems and process of expected sequence of interactions between a module and an external actor, which leads the actor to desired goals and objectives."

Use case scenarios can be mirrored as clip of a movie making scene development where-in director has assigned a script or stories to actors to act in the dialog delivery with lights, camera and action that's called a TAKE. 

On the very same lines we have User Stories which can be a powerful tool to be converted into a Use-case scenarios. User Stories can be categorized into user needs, wants and demands from usability perspective of the system development.


Definitely Use cases are key building blocks of any software development life cycle which is again powered by user stories. It is well known fact, mislead requirement will lead to many gaps created in early part of project to be rectified at each cycle of the project in later phases of the project.













Writing Effective Use Cases    Use Cases: Requirements in Context (2nd Edition)          User Stories Applied: For Agile Software Development

Comments

Popular posts from this blog

Games People Play in context to Projects

Games People Play in context to Projects: Contextually life and projects full of games, work on  dynamics of human relationships by   Dr. Eric Berne guides us not only in many social but relationship situations in corporate world also. In Todays concurrent world where we are living in a global village with Orkut, Facebook, Linkedin, Twitter and other social media leads to discounts of information in social network, where more of transactional games played knowingly(conscious) or unknowingly(unconscious). Precede to this let us understand game, A game full of transactions played with different roles by players changing their roles for a outcome in different ego states like Parent, Adult and Child ego states that will payoff.  Continuing with Payoff, specifically in context to Project teams where transactions happen at concrete or transformational levels where people not necessarily behaving rationally and motivat...

Constructive Blame storming and using Devils Advocate in problem solving and competency development

Cover of Six Thinking Hats Discussions leads to solutions , mistakes leads to innovations, As part of innovation , solution approaches, models quite often used technique in healthy discussions on day to day basis is Brain Storming , mischievously known as blame storming. To the extent organizations build competency around subjects of real time situations, till it takes to materialized very few of them make it to the concrete implementations. Take for example Google revolutionized the way we use internet with countable team, that storm sustained and now second wave coming from Facebook, Linked etc. Questions asked about their revenue models but skepticism will always there, social networks are strong tools not only for marketing but of communication, collaboration, and increased productivity and realized intangible benefits. Discussions are full of Arguments, counter arguments, statements, facts, thesis, anti thesis etc. Contextually the term devil's advocate can be dis...