BTS330: Business Requirements Analysis using OOLecture 5

Requirements Development: Practices and Skills

Agenda

The Requirements Development Cycle Good Practices Requirements Analyst: tasks, skills Analyst Skills: Presentation The Presentation

Requirements Development

Elicitation Analysis Specification Validation

Clarify

Correct and close gaps

Rewrite

Re-evaluate

Text, p. 59

Agenda

The Requirements Development Cycle Good Practices Requirements Analyst: tasks, skills Analyst Skills: Presentation The Presentation

Good Practices

Knowledge– Train/Educate/Document

Requirements Management– Change Management

Project Management– Plan/Track/Manage risks

Requirements Development– …

Requirements Development

Elicitation Good Practices– Development process– Vision/scope– Users/stake holders– Product champions, focus groups– Use Cases– Events/Responses

Requirements Development

Analysis Good Practices– Context diagram– Prototypes– Prioritization– Modeling

Requirements Development

Specification Good Practices– Template– Business rules– Quality attributes

Requirements Development

Validation Good Practices– Inspection/review of document– Acceptance criteria

Agenda

The Requirements Development Cycle Good Practices Requirements Analyst: tasks, skills Analyst Skills: Presentation The Presentation

Requirements Analyst--Duties Define vision/scope Identify users and stakeholders Elicit requirements Analyze Write Model Lead the validation Facilitate prioritization Manage the requiremetns

Requirements Analyst--Skills Communication—listening and getting

information across Interviewing/Observational Analytical Facilitation/Interpersonal Writing Presenting Modeling Creativity Organization

Agenda

The Requirements Development Cycle Good Practices Requirements Analyst: tasks, skills Analyst Skills: Presentation The Presentation

Crucial Analyst Skills

Writing Facilitation Getting/Giving information =>Many presentations!

Analyst Skills: Presentation Format

– Give the client her/his preference– Don’t just read it!– Consistency and flow—even if several presenters

Focus– Requirements of the client– Information presented should be relevant to the client– Have some kind of conclusion for the client

Language– That the client can understand– Avoid Acronym Mania

Analyst Skills: Presentation

Credibility– Do your research—don’t try to “fake it”– Understand what you are presenting– Deliver value, not “filler”

Analyst Skills: Presentation

Collect Data Analyze Present

How it should work:

How it should not be done:

Collect Data Present

Collect Data

Understand the purpose of the presentation– Requirements of the client

• Could be a problem to be solved, a computer system, and so on.

Understand what you have to research Gather sources Do the research!

Analyze

Based on the requirements:– Identify relevant material in your findings– Analyze– Make recommendations/observations/etc.

(depending on what is required)

Present

Identify key material– The points of highest value to the client

Have a conclusion or recommendation– This is the most important part

Present to the client – In a format the client prefers– Introduction/Body/Conclusion– Consistency!

Agenda

The Requirements Development Cycle Good Practices Requirements Analyst: tasks, skills Analyst Skills: Presentation The Elfin Works Presentations

Elfin Works: Data Collection

Purpose– Present the functions that the computer system

will provide for the Business Area– Present results of the regulations researched to

show how they would impact the proposed Elfin Works computer system (or why they would not)

Elfin Works: Data Collection

Client as information source– The partners have been in business since 2001

so they are familiar with some of the regulations: business number, gst, tax forms, etc.

Domain experts on your teams (students who are working in the business area)

Elfin Works: Data Collection

Other information sources– Given URL’s– Search for URL’s– Talk to people who work in a manufacturing

company– Search for relevant examples

Spend some time

Elfin Works: Analysis

How do the regulations relate to Elfin Works?– Separate “generic” from “applies to Elfin

Works” Do any of the regulations need to be

accommodated by the new computer system being developed for the Business Area?– Should they be part of the new system?– Should they be connected to the new system?

Elfin Works: Presentation

Identify key points relating to Elfin Works– Eliminate “irrelevant” information

Identify points related to the new computer system– How is the business area impacted?

PowerPoint– Intro / Rose Diagram./ Findings / Conclusion!!!KEY

– Eliminate technical language and unfamiliar acronyms

– Talk; don’t read

Elfin Works: Presentation

Length: no longer than 10 minutes Number of presenters: 1 or many NOTE: only those members of the team

who are present for all of the team presentations will receive the marks allocated to the presentation.