Produktutvecklingsmetodik - Kravspecifikation Flashcards

1
Q

What are the basic thoughts in PD?

A
  • Understand the problem: what before how. Can be connected to the design paradox
  • Abstraction of the problem: break down the problem into parts
  • Generate many ideas and concepts: greater probability to find new and suitable solutions
  • Systematic approach: aviod forgetting different aspects and show how decisions are made.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What is “Mission Statement”?

A

A document that is the starting point of the final product. It involves project description, key business goals, primary market, assumptions and stakeholders

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

What is a requirement specification?

A

A list of measurable parameters that describe WHAT the product is going to do, not how it will do it.

It is base on the wishes of different actors

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

What is the purpose of the requirement specification?

A
  • Concretize the problem statement
  • Ensure that all actors´criteria, life cycle phases and product charachteristics are taken into account
  • Give the PD team a unified view of the project goals
  • Guide searches of alternative solutions
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What is a unsuccesful PD?

A

You only listen to the actors requirements, you need to listen as well to the customers!

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

Name some challenges with requirement specification

A
  • Translate actors’ subjective desires into measurable things
  • How can the staff agree on what will make a success?
  • How can PD team be sure product will take a large part of the market?
  • How can PD team solve compromises like cost vs. price?
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What are the requirements on the requirement specification?

A
  1. Measurable requirements must be clearly linked to the stakeholder requirements
    - The specification must be complete - all stakeholder life cycle stages and aspects should be included
    - Criteria should be given solution-independent formulations
    - The criteria must be clear
    - The criteria should be measurable and/or verifiable
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What kind of requirments is there?

A
  • General requirements
  • Design
  • Aesthetic criteria
  • Ergonomics
  • Security
  • Environment
  • Production
  • Marketing etc.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What kind of language should be used?

A

Positive words. Avoid words like Must and Should.

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

Solution-independent formulation?

A

Expresses what the system should do, not how it should do it

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

How can you sort the importance of all requirements?

A

Through normative values. Normerar kraven mot varandra –> relative importance of all requirements

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

How can values be expressed?

A
  • “at least”
  • “a maximum of”
  • “be in an interval”
  • “must be exact”
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What is an ideal value?

A

Is the best imaginable value (wish). Its a value we want to reach but may not be able to do.

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

What is a marginal value?

A

Its a commercially viable value (requirement). Its the least value we want to achieve to be successfull on the market

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