Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question Regarding Definition of Feature #131

Open
e0031374 opened this issue Oct 14, 2019 · 1 comment
Open

Question Regarding Definition of Feature #131

e0031374 opened this issue Oct 14, 2019 · 1 comment

Comments

@e0031374
Copy link

Hi Prof,

Can we clarify on what is considered as a feature. My group split the work based on components instead of commands. So instead of splitting by commands eg "create note command feature" we split it based on components eg Note Logic and Note Model.

Does this fall under one feature or can we claim it as two features for grading purposes?
Is our task division based on components ok?

@damithc
Copy link
Collaborator

damithc commented Oct 14, 2019

See https://nus-cs2103-ay1920s1.github.io/website/admin/project-scope.html#individual-expectations

Some relevant points:
image

I don't think someone testing your product through the UI can evaluate the depth of feature, amount of work, quality of feature, completeness of feature, etc. of person-A's work if person-A worked only in the model component. Furthermore, if you divide work by component, the coding knowledge you gain from the can vary between members (which is not desirable) because different components use different technologies and vary in complexity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants