Skip to content

Peer Review - Stakeholder requirements #140

@calvynsiong

Description

@calvynsiong

Artifact Under Review

2.2 Customer

Team Number for Team Doing the Review

Team 03

Description of Issue

Both sections clearly cover the relevant stakeholders that the project is targeting, but the description seems to be relatively broad without much specificity, especially in 2.2 when addressing the customers as "all software developers" who will use the product.

Are these developers part of a specific industry (like how project managers is clarified to likely be associated with large scale operations)? Is there a primary focus on specific environments like mobile or embedded systems? Though the role of feedback is mentioned, it doesn’t specify how the feedback loop will work, what kind of feedback is expected, or how that feedback will be incorporated into future product iterations. I think some clarification on that part of the description would enhance it.

Metadata

Metadata

Assignees

Labels

peer-reviewFeedback from peersrequirementsRelated to the SRS document (deliverable 2)

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions