How develop a specification for a new software and/or App.
We remember how to collaborate with stakeholders, define types of requirements and examine a structure of the IEEE SWEBOK SRS template.
2. BRIEF ABOUT THE PRESENTER
Start-up consultant with successful portfolio
Ph. D. (twice) in System Analysis and Technical management
(ISCED verified)
Portfolio manager and IT consultant, and a trainer for 15+ years
with the following certifications:
PgMP®, PMP®
EXIN accredited trainer for ITIL®, MOF®, Cloud computing, Operation
services and Analysis (OSA®)
3. PATH FROM GREAT IDEA TO BUSINESS. REVIEW:
HTTP://WWW.SLIDESHARE.NET/IAMCP_MENTORING/HOW-TO-CREATE-A-BUSINESS-PLAN-44673629
Estimate our
project
Attract Investors
Our idea is great!Clouds!
5. SOFTWARE AND APP PROJECTS
ARE SPECIFIC
Distributed multi-cultural teams
Virtual teams
High-educated and
motivated staff
Mass clients Close
collaboration
6. STEP1. COLLECT AND BALANCE
STAKEHOLDER DEMANDS AND EXPECTATIONS
REVIEW: HTTP://WWW.SLIDESHARE.NET/IAMCP_MENTORING/STAKEHOLDER-
MANAGEMENT-44672689
NAME Position ROLE in a
PROJECT
CONTACTS DEMANDS EXPECTATIONS INFLUENCE RELATION to
a PROJECT
Mr. X CEO Sponsor Decrease
expenditures per
client
Innovation solution
from world known
vendor
Increase brand value
High Devoted to this
project
7. TOOLS TO COLLECT REQUIREMENTS
Laws, bylaws,
procedures
Focus groups,
Charts
Mission and vision
Brainstorming & Delphi
8. STEP 2. CLASSIFY AND BALANCE
REQUIREMENTShttp://www.i-mokymas.com
9. GENERAL TYPES OF REQUIREMENTS
Product
Development processes
Operations and support
10. TYPES OF REQUIREMENTS II.
SWEBOK GUIDE V.3. PART I. CHAPTER 1.3.-4.
Functional – concerns product and its functional abilities
Non-functional – support and operation demands, organizational or
technical constraints
Emergent – requirements which are fit not to a single product
11. PRODUCT AND PROCESS REQUIREMENTS
SWEBOK GUIDE V.3. PART I. CHAPTER 2
Target customers
Client (user) Use cases
Competitors and your competitive advantages
Description of main marketing channels
14. STEP 3. FIX REQUIREMENTS
IN A STRUCTURED DOCUMENT NAMED SRSНижний колонтитул
Example:
https://onedrive.live.com/view.aspx?cid=C891D0D484D25509&resid=c891d0d484d25509%21137&app
=Word
15. SOFTWARE REQUIREMENT SPECIFICATION (SRS) CONTENT EXAMPLE
Нижний колонтитул
Table of Contents ii
Revision History ii
1. Introduction 1
1.1. Purpose 1
1.2. Project Scope and Product Features 1
1.3. References 1
2. Overall Description 1
2.1. Product Perspective 1
2.2. User Classes and Characteristics 1
2.3. Operating Environment 2
2.4. Design and Implementation Constraints 2
2.5. User Documentation 2
2.6. Assumptions and Dependencies 2
3. System Features 2
3.1. – 3… Detailed Functional requirements
4. External Interface Requirements 6
4.1. User Interfaces 6
4.2. Hardware Interfaces 7
4.3. Software Interfaces 7
4.4. Communications Interfaces 7
5. Other Nonfunctional Requirements 7
5.1. Performance Requirements 7
5.2. Safety Requirements 8
5.3. Security Requirements 8
5.4. Software Quality Attributes 8
Appendix A: Data Dictionary and Data Model 8
Appendix B: Analysis Models 12
19. SUMMARY
Define stakeholders
Gather requirements, expectations, constraints
Classify and balance product requirements
Structure requirements, constraints and assumptions in the SRS
Define project model: waterfall and adaptive
20. THINK POSITIVE!
CAN IT MAKE THE WORLD MORE HAPPY?
Our services for start-ups:
http://i-mokymas.com/services/business-on-start/Get
detailed information on the subject
Request our detailed consulting service
Enjoy our free templates, presentations and video
IAMCP Mentoring framework:
http://www.slideshare.net/IAMCP_Mentoring
http://i-mokymas.com