accountable role (RACI model), 34–35
agile development model
project life cycle of, 52, 60–62, 66
workshop sessions, 105–106
assumptions, 8–9
brainstorming
defined, 3, 97
rules for, 98–99
stakeholder involvement, 32
tailoring sessions, 100
types of, 98
BRD (business requirements document), 10–12
BSLC (business solution life cycle), 4.
See also requirements planning
business outcome, 9
business process improvement, 104–105
business requirements
defined, 7–9
sample document, 139–160
sample use cases, 161–183
workshops focusing on, 101–110
business requirements document
(BRD), 10–12
business rules, 8–9
business solution, 6–7, 82–83
business solution life cycle (BSLC), 4.
See also requirements planning
business system, 6–7
CASE tools, 106
closed questions, 115, 120
communication
defined, 113
interviewing considerations, 111–112
nonverbal, 113
with stakeholders, 32
with users, 43
conflict resolution during workshops, 102–103
constraints, 9
construction phase (BSLC), 4, 81–82
construction project life cycle, 50–51
consulted role (RACI model), 34–35
customer site visits, 112
deliverables
assigning, 35–36
determining strategies, 69–70
project vs. product scope, 10
scaling to projects, 26–29
deliver phase (BSLC), 4
discovery sessions, 103, 107–108
documentation
business requirements sample, 139–160
for ground rules, 43–44
in SRLC, 4
use cases sample, 161–183
for user participation, 41–42
documentation reviews
benefits, 125
defined, 5
in planning process, 20–23
rules for, 125–126
tailoring, 127
elicitation. See requirements
elicitation
end-users. See users
Enterprise Analysis phase (BSLC), 4, 20–23
evolutionary development model, 52, 58–59, 66
eXtreme Programming (XP), 105–106
functional vs. supplemental
requirements, 7–9
functions, in BRD, 11
government acquisition project life cycle, 50–51
ground rules, user, 43–44
guidelines as business rules, 8
guiding principles, 43–44
influence, stakeholder, 38–40
informed role (RACI model), 34–35
integrated project life cycle, 48
interface analysis/reviews
benefits of, 129
defined, 5, 129
rules for, 129–130
tailoring, 131
types of meetings, 129–130
interviewing
benefits of, 113
communication challenges, 111–112
defined, 5, 111
rules for, 115–117
tailoring, 118
tips for, 113–114
types of, 112–113
JAD (joint application design), 106–107
job shadowing, 112
joint application design (JAD), 106–107
legacy maintenance model, 52, 62–63, 66
methodology, 49
multiple build. See RAD (rapid application development) model
nonfunctional vs. functional requirements, 7–9
nonverbal communication, 113
open-ended questions, 115, 120
Operations & Maintenance phase
(BSLC), 4
personal interviews, 112
planning requirements activities.
See requirements planning
planning teams, assembling, 19
Plutarch, 114
PMP (project management plan), 86–87
policies as business rules, 8
power, stakeholder, 38–40
procedures as business rules, 8
product life cycle, 48–49
product scope, 10
product vision document. See BRD
(business requirements document)
products, 10
project complexity
for interface analysis/reviews, 131
Project Complexity Model, 26–27
scaling brainstorming, 100
scaling interviews, 118
scaling surveys, 123
scaling workshop sessions, 110
selecting project life cycle based on, 65–68
for supplemental requirements, 135
vee model, 52, 56–58
Project Complexity Model, 26–27
project life cycles
agile development model, 52, 60–62, 66
construction, 50–51
defined, 49
evolutionary development model, 52, 58–59, 66
government acquisition, 50–51
iterative nature of, 49
legacy maintenance model, 52, 62–63, 66
prototyping model, 52, 63–66
purpose, 47–49
rapid application model, 52, 54–56, 66
selecting, 65–68
solution delivery strategies, 69–70
spiral development model, 52, 59–60, 66
tailoring, 68–69
training in, 70–71
variations in, 51–65
vee model, 52, 56–58, 66
waterfall model, 52–54, 66
project management plan (PMP), 86–87
project scope, 9–10
projects, 10, 26–29
prototyping model, 52, 63–66
questions
closed vs. open-ended, 115, 120
in interviewing, 117
in surveys, 121
RACI model, 34–36
RAD (rapid application development) model
project life cycle of, 52, 54–56, 66
workshop sessions, 106
regulations as business rules, 8
requirements analysis (SRLC)
depicted, 4
detailed plans, 78–79
flow of information, 73–75
requirements documentation and
validation (SRLC), 4, 73–75, 79–81
requirements elicitation (SRLC)
brainstorming technique, 3, 32, 97–100
business solution life cycle, 4–6
defined, 1
detailed plans, 76–78
determining conclusion, 13–14
documentation reviews, 5, 20–23, 125–127
flow of information, 73–75
interface analysis/reviews, 5, 129–131
interviewing, 5, 111–118
planning for, 76–78
process overview, 91–95
sample task information, 85
supplemental requirements, 133–136
surveys, 5, 119–123
terminology, 6–13
workshop sessions, 101–110
requirements management plan.
See RMP (requirements management plan)
requirements phase (BSLC)
depicted, 4
detailed plans, 76–81
summary-level requirements plans, 81–82
workshop sessions, 101–110
requirements planning process.
See also project life cycles; RMP
(requirements management plan)
assembling teams, 19
assessing project components, 25–29
barriers, 83
flow of information into, 73–75
reviewing relevant documentation, 20–23
stakeholder analysis, 31–42
user analysis, 41–44
requirements specification (SRLC), 4, 79–80
responsible role (RACI model), 34–35
risk management
assessing project risk, 26–29
for interface analysis/reviews, 131
for interviews, 118
project life cycle selection and, 65–68
scaling brainstorming, 100
for stakeholder involvement, 32
for supplemental requirements, 135
with surveys, 123
in workshop sessions, 110
RMP (requirements management plan)
approval needed, 87–88
barriers, 83
benefits of, 84–86
defined, 17, 83–84
detailed requirements phase plans, 76–81
elements of, 87
flow of information, 73–75
relationship to project management plan, 86–87
sample plan, 185–202
summary-level requirements plans, 81–83
typical table of contents, 88
roles, stakeholder, 34–35
Scrum method, 106
Six Sigma technique, 104
solution development life cycle, 48
SOW (statement of work), 12–13
spiral development model, 52, 59–60, 66
SRLC (System Requirements Life Cycle), 4
stakeholder analysis
purpose, 31–32
five-step process, 33–40
reexamining information, 40–41
defined, 31–32
identifying, 33–34
identifying interest, 37–38
identifying power and influence, 38–40
identifying roles, 34–36
workshops involving, 102
statement of work (SOW), 12–13
supplemental requirements, 7–9, 133–136
surveys
benefits of, 120–121
defined, 5, 119
rules for, 121–122
scaling, 123
tailoring, 122
types of, 120
System Requirements Life Cycle
(SRLC), 4
tailoring
brainstorming sessions, 100
documentation reviews, 127
interface analysis/reviews, 131
interviews, 118
project life cycles, 68–69
supplemental requirements, 134–135
surveys, 122
workshop sessions, 110
task analysis, 112–113
test phase (BSLC), 4, 81–82
training in project life cycles, 70–71
UML (Unified Modeling Language), 105
use cases, 161–183
user analysis, 41–44
users
communicating with, 43
defined, 33
elicitation process and, 93
establishing ground rules with, 43–44
identifying, 41
identifying champion, 43
interface analysis/reviews, 129–130
justification for participation, 41–42
in workshop sessions, 109
vee model, 52, 56–58, 66
verbal communication. See
communication
waterfall model, 52–54, 66
WBS (work breakdown structure), 9–10, 76–77
workshop sessions
agile requirements, 105–106
business process improvement, 104–105
defined, 3, 101
formal requirements, 104
joint application design, 106–107
rapid application design, 106
requirements, 102–103
rules for, 107–108
tailoring, 110
tips for, 108–109
XP (eXtreme Programming), 105–106