This repository was archived by the owner on Jun 30, 2024. It is now read-only.
Repository navigation
Kano Requirement Analysis
praffulj24 edited this page Feb 17, 2017
·
1 revision
| SI.NO | Requirements | M/O/A |
|---|---|---|
| 1 | The board should accept all the modules connected to it | O |
| 2 | The casing should not have any sharp surfaces | M |
| 3 | The board should be able to supply the required voltages for I/O pins | M |
| 4 | The board should be easily fixed/removed from the casing | O |
| 5 | The software should be able to program all the modules/sensors connected | M |
| 6 | The casing material should be shock proof | O |
| 7 | The modules should be easily attached/detached | M |
| 8 | The UI should be able to demonstrate ongoing process | A |
| 9 | The system developed (Hardware + Software) should be affordable | O |
| 10 | Casing should be strong and efficient | M |
| 11 | Casing should be durable | M |
| 12 | The UI should work on all the browsers smoothly | O |
| 13 | The software and the UI developed should be user friendly | O |
| 14 | The board should be able to work in all environments | M |
| 15 | The material used for casing should be rigid | O |
| 16 | The material used for casing should be light weight | A |
| 17 | The material used for casing should be low cost | A |
| 18 | The material used for casing should not affect the board | O |
| 19 | The board should dissipate less heat | A |
| 20 | The board should not affect the casing material | O |
| 21 | The casing should have proper heat flow | O |
| 22 | The heat sink should be able to remove the heat from the casing | M |
| 23 | The heat sink should be light weight | O |
| 24 | The heat sink should be shock proof | M |
| 25 | The heat sink should not damage the board | M |
| 26 | The board should be able to connect all the modules | M |
| 27 | The board should be able to run the installed OS | M |
| 28 | The board should be able to execute the programs dumped | M |
| 29 | The board should be capable to execute multiple codes | O |
| 30 | The board should have good processing speed | O |
| 31 | The code written should be according to the sensors connected | M |
| 32 | The software should be able to interact with the board | M |
| 33 | The UI should display the components connected to the board | A |
| 34 | The software should run on all the operating systems | M |
| 35 | The software should communicate with the UI | O |
| 36 | The UI should display the code running on the board | A |
| 37 | The code written should consume less memory | A |
| 38 | If needed the code can be directly written on the board | A |
| 39 | The software must be able to communicate to the board and the UI at the same time | A |
Where A - Attractive, O - One dimensional, M - Must be