SECTION 07 / 19
Practical guidelines and sample portal features
On this page 2 headings
Identified requirements
After requirement gathering, the Seller Portal could contain the following features.
| # | Identified requirement |
|---|---|
| 1 | Add/Edit/Delete catalogue |
| 2 | Add/Edit/Delete inventory |
| 3 | Track orders |
| 4 | Track payments |
| 5 | Track inventory |
| 6 | Track sales – specific day, last x days |
| 7 | Track customer feedback |
Basic requirement-gathering guidelines
| Guideline | Details |
|---|---|
| Focus on identifying stakeholders' needs | |
| Involve all stakeholder groups | Primary, secondary and tertiary — each has different needs |
| Use a combination of data gathering techniques | Different techniques have different purposes |
| Run a pilot session if possible | Ensure your data-gathering session is likely to go as planned (e.g. a questionnaire may have a missing question or wrong/missing options, and it is difficult to ask users to fill it again) |
| Data gathering is expensive and time-consuming | Be pragmatic and make compromises |