Send the link below via email or IMCopy
Present to your audienceStart remote presentation
- Invited audience members will follow you as you navigate and present
- People invited to a presentation do not need a Prezi account
- This link expires 10 minutes after you close the presentation
- A maximum of 30 users can follow your presentation
- Learn more about this feature in our knowledge base article
Do you really want to delete this prezi?
Neither you, nor the coeditors you shared it with will be able to recover it again.
Make your likes visible on Facebook?
You can change this under Settings & Account at any time.
Software Requirements Engineering
Transcript of Software Requirements Engineering
Types of requirements
Session 1 - 70 minutes
Break 1 – 10 minutes
Session 2 - 70 minutes
Break 2 – 10 minutes
Session 3 - 70 minutes
Q&A session – 10 minutes
Total – 4 hours
Software Requirements Engineering
Contents at a glance
We had two Software Requirements Specifications, seventy-five Change Requests, five sheets of Backlog, Vision and Scope document, Requirements Management Plan, Business Analysis Communication Plan, Software Architecture Document, and Business Analysis Plan. I was worried about only the last one, BA Plan.
Not that we needed all that for the project, but once you get locked into a serious documents package, the tendency is to push it as far as you can.
Business Process Model
Use Case Diagram
1992 - 2005
1999 - 2013
2009 - 2015
RUP + UML
“Object-Oriented Software Engineering: A Use Case Driven Approach”, 1992
Ivar Jacobson, Grady Booch, James Rumbaugh “The Unified Software Development Process.”, 1999
Grady Booch, James Rumbaugh, Ivar Jacobson
“Unified Modeling Language User Guide, The, 2nd Edition”, 2005
User-Centered Design, Use Cases, Wiegers
Constantine, L., Lockwood, L.
“Design for Use”, 1999.
“Writing Effective Use Cases”, 2000.
Strategy (Enterprise) Analysis
Why correctly working functionality is not accepted?
Business Analysis Planning
What type of SDLC?
Requirements Life cycle MGMT (mgmt and communication)
Elicitation and collaboration
User Story vs. Use Case
Business analysis: The practice of enabling change in the context of an enterprise by defining needs and recommending solutions that deliver value to stakeholders.
Any person who performs business analysis, no matter their job title or organizational role
Why do you follow me?
Levels of Use cases
Very High Summary
Use Cases Flows
Use Case template
objectives (reason, money)
BA role on the project
main SDLC concepts
main BA techniques
main types of documents
main types of diagrams
Use Case technique
Why are we
What must the
What does BA need to do?
Does it do what it
was supposed to?
understand and agree?
Who can do
Value of business analysis
Projects Success Figures*
53% projects exceed planned budget by 189%
55% projects do not meet business goals
This costs American Business about $30B per year
Focusing on Requirements Saves Budget*
Focusing on Requirements is Key to Success*
*Forrester Research for the US market
*Standish Group CHAOS Report, 2011
* IAG Consulting, 2008
Fixing requirements errors eats up to 33% of your project budget
>80% of errors are introduced at the requirements analysis stage
The interview is a common technique for eliciting requirements. It involves direct communication with individuals or groups of people who are part of an initiative.
Observation of activities, also known as job shadowing, involves examining a work activity firsthand as it is performed. It can be conducted in either natural work environments or specially constructed laboratory conditions. The objectives of the observation dictate how it is planned for and methodically conducted.
Brainstorming is an excellent way to foster creative thinking about a problem. The aim of brainstorming is to produce numerous new ideas, and to derive from them themes for further analysis.
A workshop is a focused event attended by key stakeholders and subject matter experts (SMEs) for a concentrated period of time. A workshop may be held for different purposes including planning, analysis, design, scoping, requirements elicitation, modeling, or any combination of these. A workshop may be used to generate ideas for new features or products, to reach consensus on a topic, or to review requirements or designs.
Prototyping is used to elicit and validate stakeholder needs through an iterative process that creates a model or design of requirements. It is also used to optimize user experience, to evaluate design options, and as a basis for development of the final business solution.
Why do you have altered your functionality again and again?
User Story Quality Checklist
All necessary user story sections are ready
Assumptions and Constraints (
Data Discovery details in Notes (
UI mock-ups attached (
Supporting files attached (
*corresponds to the US quality: Independent, Negotiable, Valuable, Estimatable, Sized appropriately or Small = INVEST
Test Cases from Use Cases
UML or not?
Management by Automation
Level of details
Figure and Ground
The deadline is instant.
• IT experience, years
• Domains/systems: CRM,
MRP (warehouse), SCM
(logistics/distribution), ERP (manufacturing, FMCG), BI, OSS/BSS (telecom billing), Public Safety (i3, NG9-1-1)
• Knowledge in\frameworks\tools: COBIT, BABOK, PMBOK, ITIL practices, ITSM, CMMI, SDLC methodologies, UML, CASE tools
• Bachelor's and Master’s degrees with honors in Computer Science & Management of Technology
• Certified Business Analyst (CCBA®, CSPO®)
on the position,
by education and
due to poor requirements