Scribd
Upload
38 views

Software Requirements Engineering

This document discusses various techniques for requirements engineering, including analyzing existing documentation, collecting hard data, and using storyboards. Storyboards involve sketching out scenarios of how users will interact with a system through sketches, screenshots, or other visual representations. They can be passive, showing a narrative, active simulating usage, or interactive allowing user participation. Storyboards are useful early in the design process for exploring designs and verifying requirements with stakeholders.

Uploaded by

syed kashif
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
38 views

Software Requirements Engineering

This document discusses various techniques for requirements engineering, including analyzing existing documentation, collecting hard data, and using storyboards. Storyboards involve sketching out scenarios of how users will interact with a system through sketches, screenshots, or other visual representations. They can be passive, showing a narrative, active simulating usage, or interactive allowing user participation. Storyboards are useful early in the design process for exploring designs and verifying requirements with stakeholders.

Uploaded by

syed kashif
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 14

Software requirements

engineering
Existing Documents
• Background Reading
– company reports, organization charts, policy manuals, job
descriptions, reports, documentation of existing systems, etc.
– understanding of the organization before meeting the people
– being aware of the business objectives of the organization
• Existing Solution Systems
– Documentation
• User manuals
• requirements specification document
– May be seen as reengineering method for documents transferring user
documentation into basic elements of information for requirements
– Focus is on Commonality and Variability
Hard Data Collection

• Identify Collections of Hard Data


– Facts and figures, financial information,…
– Reports used for decision making,…
– Survey results, marketing data,…
• Sampling
– Sampling used to select representative set from a population
– Sample Size is important
– balance between cost of data collection/analysis and required significance
• Process:
– Decide what data should be collected - e.g. banking transactions
– Determine the population to be sampled - e.g. all transactions at 5 local branches
over one week
– Choose type of sample - e.g. simple random sampling
– Choose sample size - e.g. every 10th transaction
Storyboard
• Storyboards, as used in the film industry, are a
portfolio of sketches which briefly tell a story to a
production team.
• A Storyboard "tells a specific story". 
• A Storyboard is a logical and conceptual description of
system functionality for a specific scenario, including
the interaction required between the system users
and the system.
• Storyboard early and often on every project with new
or innovative content.
• A typical storyboard will contain a number of images depicting
features such as menus, dialogue boxes and windows.
• The formation of these screen representations into a sequence
conveys further information regarding the structure, functionality
and navigation options available within an intended system.
• The storyboard can be shown to colleagues in a design team as
well as potential users, which allows others to visualize the
composition and scope of an intended interface and offer critical
feedback.
• This method can be used early in the design cycle where the use
of storyboards supports the exploration of design possibilities
and the early verification of user requirements.
Types of Storyboards
• Passive storyboards
– Tell a story to the user.
– Consist of sketches, pictures, screen shots, PowerPoint presentations, or sample
application outputs.
– Walks the user through the storyboard, with a "When you do this, this happens"
explanation.
– Example: Screen shots, Business rules, Output reports
• Active storyboards
– Try to make the user see "a movie that hasn't actually been produced yet.“
– Provide an automated description of the way the system behaves in a typical usage or
operational scenario.
– Examples: Slideshow, Animation, Simulation
• Interactive storyboards
– Let the user experience the system in as realistic a manner as practical.
– Require participation by the user.
– Examples: Live Demos, Interactive presentations
RUP - use-case storyboard
• A logical and conceptual description of how a
use case is provided by the user interface,
including the interaction required between
the actor(s) and the system.
• Storyboarding is often a good way to get the
users talking about the sequence of actions
that will become the steps in a use case.
• The following people use the use-case storyboards:
• Requirements analysts, who want to understand how the system
carries out the flow of events.
• User-interface designers, to build a model of the user interface.
• Designers of the boundary objects participating in the use-case
storyboard, to understand the objects' roles in the use cases and
how the objects interact. They use this information to design and
implement the boundary object to construct the user interface
• Those who test to test the system's use cases
• The manager, to plan and follow up the analysis and design work
Storyboarding
• Scripted walkthrough of system activities and/or screen
mockups
• Storyboards tell
– Who the players (actors) are?
– What happens to them?
– How it happens?
• Typically expressed in the form of activity diagrams
– to show workflow or performed actions
– may be partitioned to show control flow between different classes
• Usually tied to use cases
– activity partitions correspond to actors
A Sample Storyboard
Animating a Storyboard
Advantages
• Help gather and refine customer requirements in a
user friendly way (promotes communication)
• Encourage creative and innovative solutions
• Encourage team review
• Prevent features no one wants
• Ensure that features are implemented in an
accessible and intuitive way
• Ease the interviewing process
• Storyboards can be created quickly and easily.
Disadvantages
• Storyboards may lack the interactive quality of
prototyping methods.
• Because of their simplicity, storyboards do not
support the evaluation of fine design detail.
• Storyboards do not accurately convey system
responsiveness.
Q&A

You might also like