You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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.
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?
The text was updated successfully, but these errors were encountered: