Customer Meeting - Software Engineering Methodology | COMP 410, Exams of Software Engineering

Material Type: Exam; Class: SOFTWARE ENGINEERING METHODOLOGY; Subject: Computer Science; University: Rice University; Term: Unknown 2006;

Typology: Exams

Pre 2010

Uploaded on 08/19/2009

koofers-user-o2m-1
koofers-user-o2m-1 🇺🇸

10 documents

1 / 1

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Customer Meeting 9.27.06
What the customer wants
- The customer is concerned about the user interface being user friendly
oHe wants to make sure it is intuitive enough that musicians don’t have
to have a lot explained to them before using it
oHe thinks we need to consider doing HCI - human computer interface -
research, so we know more about naturalness and ease of use
He knows we have other things to worry about, but thinks it is
something we should put on our agenda.
-Rather than having small proofs-of-concept, he wants something that is
actually tied together with something behind it
owould rather have a less-featured GUI that is connected with the
model
ohe stated that he would be happy with a GUI that is just a grid, rather
than one that has movable toolbars and such
ohe liked Adam’s Jam Session demo. He wants more demos where you
click and noise comes out of another person’s computer—ones that
you can actually see something going on.
- his view of the GUI is one where the user can logon and see not only his own
instrument, but everyone else’s as well. If he can’t see the instruments, he at
least wants a list of people that are currently in the session, and when you
click on them, more detailed information pops up.
-
What we promised
- by the next customer meeting, next week, we will have a tied-together proof
of concept
- to email the listserv to find a good time for the meeting next week. This will
be attended by his technical staff (the TAs) who can ask us anything they
want to see if we know what we are talking about and can deliver what we
have promised.
- Good documentation and UML for the technical staff to read quickly and
understand
oAlso, things like Barnaby’s network distance-time information need to
be well-documented
- Chase says networking should write a test to send a midi event to another
computer and respond with a midi event as it will provide a more realistic test
time.

Partial preview of the text

Download Customer Meeting - Software Engineering Methodology | COMP 410 and more Exams Software Engineering in PDF only on Docsity!

Customer Meeting 9.27.

What the customer wants

  • The customer is concerned about the user interface being user friendly o (^) He wants to make sure it is intuitive enough that musicians don’t have to have a lot explained to them before using it o (^) He thinks we need to consider doing HCI - human computer interface - research, so we know more about naturalness and ease of use  (^) He knows we have other things to worry about, but thinks it is something we should put on our agenda.
  • Rather than having small proofs-of-concept , he wants something that is actually tied together with something behind it o (^) would rather have a less-featured GUI that is connected with the model o (^) he stated that he would be happy with a GUI that is just a grid, rather than one that has movable toolbars and such o (^) he liked Adam’s Jam Session demo. He wants more demos where you click and noise comes out of another person’s computer—ones that you can actually see something going on.
  • his view of the GUI is one where the user can logon and see not only his own instrument, but everyone else’s as well. If he can’t see the instruments, he at least wants a list of people that are currently in the session, and when you click on them, more detailed information pops up.

What we promised

  • by the next customer meeting, next week, we will have a tied-together proof of concept
  • to email the listserv to find a good time for the meeting next week. This will be attended by his technical staff (the TAs) who can ask us anything they want to see if we know what we are talking about and can deliver what we have promised.
  • Good documentation and UML for the technical staff to read quickly and understand o Also, things like Barnaby’s network distance-time information need to be well-documented
  • Chase says networking should write a test to send a midi event to another computer and respond with a midi event as it will provide a more realistic test time.