T-76.4115/5115 Software Development Project I/II Experience Exchange Session: QA Managers, requirements engineering - PowerPoint PPT Presentation

1 / 8
About This Presentation
Title:

T-76.4115/5115 Software Development Project I/II Experience Exchange Session: QA Managers, requirements engineering

Description:

Elicitation (ryhm ty t ryhm t iden purku) business goals, ... As a result of the elicitation activity, there can be a huge amount of unstructured information. ... – PowerPoint PPT presentation

Number of Views:99
Avg rating:3.0/5.0
Slides: 9
Provided by: JariVa9
Category:

less

Transcript and Presenter's Notes

Title: T-76.4115/5115 Software Development Project I/II Experience Exchange Session: QA Managers, requirements engineering


1
T-76.4115/5115Software Development Project
I/IIExperience Exchange SessionQA Managers,
requirements engineering
  • Jari Vanhanen
  • Ohjelmistoliiketoiminnan ja tuotannon
    laboratorio
  • Software Business and Engineering Institute
  • (SoberIT)

2
Agenda
  • Esittäytyminen
  • nimi, projekti, miten pitkällä olette REhen
    liittyen
  • Kommunikointi asiakkaan kanssa
  • Elicitation (ryhmätyöt ryhmätöiden purku)
  • business goals, main domain concepts
  • user groups
  • functional requirements, non-functional reqs.,
    contraints
  • Analysis
  • (Representation)

3
Requirements Engineering
4
Kommunikointi asiakkaan kanssa
  • Miten kommunikointi on tapahtunut käytännössä?
  • Minkälaisiin ongelmiin olette törmänneet?
  • Mitä toimintatapoja olette havainneet hyviksi?

5
Ryhmätyöt
  • Aiheet
  • business goals, main domain concepts
  • user groups
  • functional requirements, non-functional reqs.,
    contraints
  • Valitkaa yksi projekti kontekstiksenne
  • mutta tuokaa esille ajatuksia kaikista
    projekteista
  • Onko asia tärkeä (miksi, miksi ei)?
  • Mitä haasteita on tiedossa?
  • Miten asian saa hoidettua hyvin?

6
Requirements Analysis
  • As a result of the elicitation activity, there
    can be a huge amount of unstructured
    information.
  • Analyze the gathered information gt big picture
  • List identified requirements shortly
  • Group related requirements
  • Analyze the listed requirements very roughly from
    three viewpoints
  • Importance for customer must, essential,
    conditional
  • Impact to architecture high, medium, low
  • Development effort high, medium, low

7
Requirements Representation
  • Why to represent/document requirements in detail?

8
Requirements Representation
  • Why to represent/document requirements in detail?
  • Well-documented requirements
  • decrease interpretation
  • are a contract i.e. official statements of
    requirements)
  • are a communication tool
  • are a collective memory
  • guide design
  • guide testing
  • are a basis for iteration and project planning
Write a Comment
User Comments (0)
About PowerShow.com