SENG 310 Project Phase 1 -  Comments

Please direct any questions to Louis (yul@uvic.ca)



Group 1_01

- You list restaurants as a stakeholder, so shouldn't you have a profile to represent that?

- For usability goals, the system should also be able to allow easy repair, that is, if the system is down

it should be backed up quickly, also some fault tolerant methods should be implemented.

- Can the system be allowed to reserve seats for a restaurant online? that would be a nice feature wouldn't it?

  (I didn't take mark off of that, just a suggestion)

- listing a existing way how customer finding restaurant and do a comparison would be helpful

- You guys should elaborate on how you research to your conclusion of user requirement or user experience goal. Like

  some reasoning, explanation, or some simple interview ect.

- Everyone's getting the same mark in this one, if you guys have complaints on whom did more work, let me know

 

 

Group 1_02

- very nice intro

- the resturant customer section, you separated into tourist and international student, and researchers. I'm not

sure if that is a complete classfication of people whom use the website. What about people whom just decided to

eat out and are not tourist or international students.

- you listed waittress as one of your profiles, so shouldn't your stakeholder include waittress? But, I don't think

waittresses should be one of the stakeholder, so you shouldn't have a waittress user profile

- shouldn't your user profile include a administrator since you made a point that the system should be easy to maintain?

- The interview you guys did are excelent

- If the system is designed partly for international student, or tourist, shouldn't easy to use or a a clean and simple

  interface be important and part of the user experience goal?

- you guys did some really good research, however, putting it together, some points are forgotten, good job nontheless

 

Group 1_03

- the intro didn't describe the system enough, only provided a short paragraph

- stakeholder, potential costumers could be broken down

- Include a system administrator in your user profile, since you mentioned it in stakeholder

- There should be more user experience goals.

- user requirement, secnario and so on are pretty good

 

Group 1_04

- love the intro

- end user in stakeholder should be broken down, at lease show me what different type of users are there

- Again, maybe have a system administrator as user profile

- Scenario should be in steps, it's a bit messy describing what user did in a chunk

- wait! where is your user experience and usability goals, and justifications

 

Group 1_05

- your interface is a bit strange

- intro too simple

- usability goals and user experience goals are not listed, they are things like "effectiveness" or "efficientcy"

  please see the textbook, also you have to justify why you need those goals

- stakeholder are not the same as names in user profile, they are things like "customers", or "administrators"

- in keystakeholder, you describe a list of people invovled, but what is "user and stakeholder" suppose to be

- please cleanup your interface, I'm getting confused, especially in key stakeholder and stakeholder

- HTA and scenario are too simple

 

Group 2_01

- brief intro

- user profile need to represent all sort of users, not just students. Teacher maybe? administrtive people

- Please separate the requirement into user experience and usability. Also, some user requirement goals would be nice

- user scenario should be in steps, and be more detail

- I do like your HTA

- mainly the mark are taken off because of the usability and user experience goals section, but overall some of the aspects

  needs more reasoning and explanation

 

Group 2_02

- good intro

- stakeholder list should be more than that, also there should be some more explanation with each stakeholder.

- User profile is too limited, what about a professor, administrtor.

- where is your usability and user experience goals?

- main marks are being deducted for lack of usability and user experience goals, and justification

 

Group 2_03

- nice intro

- there's only two user profile? Joey and Joe, and they're similar

- same goes for the user scenario and HTA

- wait, user requirement don't need to be separated into Joey and Joe's

- I can not view the user requirement section at all!! and where are your usability and user experience goal

- HTA are completely unviewable, the picture can't be shown

- website are entirely too simple and most of the things can't be viewed.

 

Group 2_04

- simple intro

- stakeholders should be better explained, and there are more than 2

- why is your main goal after your key stakeholder

- simple user profile

- where is your usability goal and user expenerience goal

- scenarios are targeted towards your user profile, individual users

- so should your HTA

- main the website is lacking explanation and try to sum up all the requirements in one or two sentences.

 

 

Group 2_05

- really simple webpage

- user profile are done wrong, it's suppose to be "Jack, a student" and so on so on, see the webpage for instruction

- therefore, user scenarios and HTA are done (slightly) wrong