Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

Professional Software Development > 3. Requirements Gathering > Flashcards

3. Requirements Gathering Flashcards

1
Q

Customers may :

A
  1. may not know what is realistic
  2. may not know how to explain what they want
  3. change their minds frequently
  4. may not be reliable
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Developers responsibility

A
  1. managing their expectations and our own workload
  2. be flexible about requirement changes but also be realistic
  3. be prepared to say that something is not possible
  4. customers to deliver their commitment
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Objectives for requirement gathering

A
  1. get to know customers and businesses for planning
  2. decide on rules for engagement
  3. establish primary contact (product owner)
  4. clarify overall goals
    - customers big picture
    - realistic goals within the scope
    - high level features to be implemented
    - minimum viable product
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Preparation for requirement gathering

A
  1. review literature and survey market solutions to understand project scope and develop awareness of existing solutions
  2. identify key stakeholders
  3. identify significant requirements/constraints/risk
    - system boundary
    - technologies to use
    - meeting the customer
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Project stakeholders

A
  1. user
  2. customers
  3. beneficiaries
  4. partners
  5. external services
  6. regulators
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Non-functional requirements

A 
usability
error handling
documentation
performance
storage capacity
compatibility
availability
environmental
security
resources
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What is Effective Requirement gathering

A
  1. clear agenda and meeting goals
  2. use visual aides to focus customer attention
  3. use customer meetings to highlight complex decisions, follow up later
  4. describe requirements/ features with structured techniques (user stories)
  5. use visual walkthroughs
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Setting Agenda

A
  1. summarise the agenda at the start of the meeting
  2. agenda should be specific to the project
  3. summarise specific work
    - business understanding
    - models
    - plans for next sprint
  4. key questions for customers
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Why is Time boxing needed

A
  1. estimate time needed for each agenda and record
  2. help team decide how best to use time
  3. help chair decide when to pause discussion of an agenda
  4. discussions that over run should be paused
    - make tasks to resolve after offline
    - use extra time is available
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Setting goals

A
  1. decide goals for first release
    - what can be achieved by the next meeting
    - what feature/ prototype can you show?
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Attributes/ workstyle, choose 2 out of 3

A
  1. quick
  2. high quality
  3. complete
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Ways to describe requirement

A
  1. natural language
  2. structured natural language
  3. use case diagram
  4. pseudo code
  5. view frames
  6. algebraic languages
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

User stories flow

A

As an [actor]
I want to [action on system]
so that I can [rationale]

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Roles for meeting

A
  1. meeting chair
  2. product owner
  3. note taker
  4. checker
  5. lead demonstrator
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

How to manage discussions

A

Balance needs to be maintained between

  • ensuring useful ideas and suggestions
  • not deviate too much from agenda

Chair has authority over who talks

  • interrupt speaker if he dominates too much
  • ask customer to elaborate more if unclear
  • ask someone to contribute to stimulate discussion
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Documenting the meeting

A
  1. only job for at least one person to take meeting minutes
  2. may write directly on github wiki
  3. ask customer if they mind you recording the meeting
17
Q

Setting plan for future work

A
  1. have a proposal ready
    - new project understanding
    - new feature identified
  2. anticipate priority of work items
  3. be realistic
    - have person-time estimates
    - ensure total work planned is less than time available
    - assume 1 person day per week
18
Q

Negotiating with customers

A
  1. customers expection and priorities with vary from your own
  2. radical changes in direction need to be approached cautiously
    - don’t say yes immediately
    - take time to evaluate
  3. be honest
    - be prepared to negotiate a new schedule
    - incorporate previous delays in new schedule
  4. ask supervisor if in doubt
19
Q

Managing meeting outcome

A
  1. summarise agreed overall goal and work items before end of meeting
  2. create a backlog of items
  3. create issues for follow up task
20
Q

Customer collaboration

A

engage customers throughout the development process

  • periodic demonstration
  • continuous improvements based on feedback
  • pursue customer satisfaction

Professional Software Development (11 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions