Vision Feedback

Feedback on Vision & Mock-up

Vision does not follow the template.
Vision is incomplete: lacks background, list of stakeholders, opportunity, and vision of solution.
"How will it be used?" (don't use Q&A style) should be Major Features.
Poor layout. Don't use ad hoc Q&A style headings, e.g. "What is it ?" (and don't put space before "?"). Use section headings as in template, or something equivalent.
No link to Mock-up in Vision.
Mock-up is OK, but does not show submittal steps. There should be feedback and confirmation during submittal.

Team name is too long.
Vision doesn't follow template: Background, Vision, Scope, Business Case.
Don't use Q&A style headings. Use descriptive names.
Vision contains some detailed requirements (which are wrong) instead of describing major features and purpose.
Mockup is very incomplete.

Vision doesn't follow the template. Vision is very incomplete.
Don't use ad hoc Q&A style headings.
Has some background, description of need, and requirements. But parts are WRONG! ExceedCamp never used Google Forms (which is stated multiple times in Vision), QR code was not Aj. Panpiti's requirement.
Wrong features: Web app can't work offline, "trackable data" and "server constraint" are vague, "not as reliable as Google Forms" is arbitrary speculation (how do you know?).
Mock-up using http://moqups.com is interesting, but mock-up lacks explanation and screens seem arbitrary. Some of them are not important to the application. I doubt we will use mobile interface to create teams.

Vision doesn't follow template.
Don't use Q&A style with ad hoc headings. Use standard headings.
Content is too terse and imprecise. What does "Who?" mean?
Vision states some minor or detailed requirements instead of broader requirements.
Same "Google Forms" error as Maepo's vision. ExceedCamp did not use Google Forms.
Mock-up is poor. I wouldn't know how to vote if presented with those screens.

Vision doesn't follow template.
Vision is incomplete.
Don't use ad hoc Q&A style headings. Use heading as in template or equivalent.
English errors (several). Space after comma, never a space before comma.
Wording of features is too vague: "users can rate and vote the application". What application? What's the difference between "rate" and "vote"?
"Every thing can be change by admin". Really? EVERYTHING? (Not: "Every thing")
Mock-up is good but some steps missing. Lacks explanation of what is happening.

Please list team members on first page (README.md).
"Overall Description" section of SRS is not a substitution for Vision statement. The purpose of the Vision is to provide an overall picture of the context, the problem, the proposed solution, and business case (why is it worth doing).
No mockup.

Team name is too long.
Vision doesn't follow template.
Don't use ad hoc Q&A style section names, like "Who is Customer?"
"Who is customer?" wrong: students, instructors, visitors are NOT your customers. They are stakeholders affected by the problem.
Analysis of last year inaccurate. People could vote from any web browser. I don't think "voting withoug visiting projects" is actually a problem.
English is OK but still some errors. Punctuation: "::" is not valid punctuaion, and no space before colon.
Has some non-requirements or minor requirements. Vision should define "big picture" and major features.
Vision of your solution should be expanded.
Mock-up looks nice, but it is incomplete. Should illustrate the entire flow of how application is used.

Vision is incomplete and doesn't have the sections as in template.
Poor punctuation in Vision.
Mock-up does not show how application is used, and has lots of junk that are not required. For example, sign-in with Facebook or Github is not a requirement, and probably not desirable (how are you going to uniquely identify allowed voters?).

ExceedVoting - assignment for 16-23 April.