Book--Group+2 Monday

8/14/2019 Book--Group+2 Monday

1/40

CHAPTER 8:CHALENGES OFREQUIREMENT ELICITATION

Group 2: Andrew Denner


2/40

Overview

There are three main syndromes ofsoftware elicitation Yes, but

Undiscovered ruins

Users and Developers


3/40

Yes, but

Two typical responses to software Cool

Yes but, wouldnt it be neat if it coulddo

Why the yes but? Human nature

User didnt understand developer Developer didnt understand user


4/40


5/40

Yes, but cont.

Solution? Software development compared to

mechanical device development

Annoying, yes but Yes, but can bea good thing It leads to insights

It is human nature expect it and planfor it

Get the buts out early


6/40

Undiscovered Ruins Syndrome

Requirements can be like looking forruins, the more you find the more youknow remain

Take time to identify all stakeholders.Especially non user stakeholders

You never will find them all when is

enough enough?


7/40

User & Developer Syndrome

Techniques have existedfor 40 years

Communication problemsexist due to differentbackgrounds motivationsand objectives

How do we communicate?


8/40

User and Developer, solutions


9/40

Conclusion

Understanding needs moves you outof comfort zone

We will be covering skills for problemanalysis over the next fewpresentations Interviews and questionnaires

Requirements Workshops Brainstorming sessions and Idea

Reduction

Story Boards


10/40

CHAPTER 9THE FEATURES OF

A PRODUCT OR SYSTEM

Group 2: Hojun Jaygarl


11/40

Key points

The development team active role!!in eliciting requirements for the system

Features : high level expression of desiredsystem behavior

# of system features = 25-99


12/40

Active role

Why? The dev team was passive

The basis forsystemdevelopment

Specification It is usually

NOT a perfector perhapsevenreasonableunderstanding

Problem


13/40


14/40

Stakeholder and User Needs

Obvious fact: the dev teamunderstands the true needs of thestakeholder they will build a better

system That knowledge: the information to make

better decision in the definition and

implementation of the system. Stakeholder or user needs

This set of input provides a crucial piece ofpuzzle.


15/40

Stakeholder and User Needs

Definition

Stakeholder need: A reflection of the business, personal, or

operational problem (or opportunity) thatmust be addressed in order to justifyconsideration purchase, or use of a newsystem


16/40

Features

If stakeholders need

If I dont increase productivity in thisdepartment. I wont get my bonus thisyear

I want to be able to slow this vehicledown as quickly as possible withoutskidding

I must reduce sales order entrytransaction processing time by 50percent

Real

Needs

ActualRequireme

nt for a

Instead, they describe what seems

to be an abstraction somewherebetweenI need a new GUI based order entry

screen

andI want a vehicle with ABS


17/40

The high-level expression thefeatures!!

Problem: Often not well defined May even be in conflict with one

another

Features

I want increased

order process ratesWhat is their

real needs????I want to provide a farmore user friendlyinterface to help our new

Productivit

Safety


18/40


19/40

If the dev team doesnt understandthe need behind the feature realrisk!

If the feature does not solve the realneed the system may fail to meet theobjectives (even though the

implementation delivered the feature)

You are right, but you still lose!

Caveat of Features


20/40

Feature : a service that a systemprovides to fulfill one or morestakeholder needs

Features are a convenient way todescribe functionality withoutgetting bogged down in detail.

features cannot be too far removedfrom their needs

a handy way to define the system.

Definition of Features


21/40


22/40


23/40

Pick the level of abstraction

A relatively small and manageable

amount of informationa comprehensive and complete basis

for product definition, communication, scopemanagement, and project management.

Managing Complexity

# of

Features

Effectively pickthe level ofabstraction ofthe definition

22-99,

< 50preferred


24/40

Start making such decision as

defer to a later release

implement immediatelyreject entirely

investigate further

Team Skill 4

Scoping after enumerating


25/40

Attributes help better manage features, complexity of

the information

make relation to other types of projectinformation

No limited type

Use to

Track (name, unique id, sponsor, history data,allocated from, traced to

Prioritize(priority field)

Manage(status, progress)

Attributes of Features


26/40

Feature

25-50 features describe simply andelegantlywhat a system needs to dohow much time and effort may be

required to do it

Summary

Simple, but CriticalEasy to elicitEasy to documentEasy to maintainUser friendly


27/40

Chapter 10

INTERVIEWING


28/40

1. Key Points

3.Two types of questions

5. Compiling the Needs Data

7. Questionnaires

Content


29/40

A simple and direct technique

Can be used in most circumstances

Context-free questions for bias-free interviews

Solution-context questions for undiscoveredrequirements

Initiate a requirements repository

A questionnaire is no substitute for an interview

Key Points


30/40

Help us gain an understanding of thereal problem without biasing theusers input.

Force us to listen before attempting tooffer solution.

Give us better understanding of thecustomers real problem.

Context-Free Questions


31/40

After context-free questions session.

Not only understanding but alsoproviding appropriate solutions.

May give the user new insights andeven a different view of the problem.

Solutions-Context Questions


32/40

Part1: Establishing the customer/userprofile Name, company, industry, job title, etc

Key responsibilities, outputs, for whom,etc

Part2: Assessing the problem

Which problems do you lack a goodsolution ? What are they ? How theycurrently be solved ?

Part 3: Understanding the user

The generic, almost context-free


33/40

Part 4: Recap for understanding List customer described problems in your own

words Check it whether adequately represent the

current problems Part 5: The analysts inputs on the

customers problem List any needs or additional problems you think

should concern the customer/user

For each suggested problems check it is feasibleand realistic enough.

Part 6: Assessing your solution Summarize the key capabilities of your proposed

solution and ask the customer/user to rank them.



34/40

Part 7: Assessing the Opportunity Who needs this application ? How many

types of users ?

Part 8: Assessing the reliability,performance, and support needs What are your expectation for ? What

about maintenance/serviceaccess/installation/configuration ?



35/40

Part 9: Other requirements Are there any legal, regulatory or

environmental requirements or otherstandards that must be supported ?

Could you think any other requirements weshould know about ?

Part 10: Wrap-up Any other questions ? Will you participate in

a requirements review?

Part 11: The analysts summary Summarize three highest priority

needs/problems identified by user/customer



36/40


37/40

Prepare an appropriate context-freeinterview

Research the background of thestakeholder and the company to beinterviewed.

Do not ask questions you are ableanswer but it is ok to verify the

Notes on the Interview


38/40

Write down answers in your notebookduring the interview.

It is ok to let the interviewee wanderoff course a bit, but the interviewerhas to keeps the goal of interview in

mind.

Notes on the Interview (cont)


39/40

Can be used effectively to gather asignificant amount of focused data ina short period of time.

No substitute for an interview Relevant questions cannot be decided inadvance

The assumptions behind the questions

bias the answer Difficult to explore new domains

No Interaction

Difficult to follow up on unclear user

Questionnaires


40/40

One of easiest way to find out what asystem needs.

Gathering requirements in astructured way (ask right person aright question in a right way).

Workshop can be helped to augmentthis fundamental process.

Summary

Documents

Book--Group+2 Monday