CW4: Front-End Prototype

sevab commented 10 years ago

Hey guys, So I've decided to star doing the first bit of the coursework. Here are the 2 User Profiles that we need in my opinion:

Customer

Age: almost any
Gender: male & female
Physical abilities: possible senses disablities (sight, hearing, etc)
Background: very varied
IT experience: from novice to power user
Education, training: from none to PhD
Cultural background: any
Goals, motivation: book/reserve/print tickets, browse & rate movies, read newsletter
Position: general public

Admin

Age: almost any
Gender: male & female
Physical abilities: minor senses disablities that do not interfer with the job requirements
Background: very varied
IT experience: from knowledgeable to power user
Education, training: trained in using booking managment systems
Cultural background: any
Goals, motivation: manage customer and movie details, create newsletters
Position: cinema booking system administrator

sevab commented 10 years ago

The next bit is user vocabulary.

akshay378 commented 10 years ago

For admin :

    • Age: Based on IT Experience
• Gender: Male/Female
• Physical abilities: Should not be disabled
• Background: Any
• IT experience: Knowledgeable - Power User
• Education, training: trained in using booking managment systems
• Cultural background: Any
• Goals, motivation: manage customer and movie details, create newsletters
• Position: Cinema booking system administrator

I think i just vary on the age. Also, do you guys think the IT Experience should be specific? Like the example given in the lecture slides?

sevab commented 10 years ago

@akshay378 don't think it should be specific, I mean it's not mentioned in the specification, so we shouldn't come up with numbers. I think age can be any, I mean you can teach a teenager to use the system.

sevab commented 10 years ago

If everyone's happy with that, let's move to User Vocabulary. I'm gonna do the nouns. @akshay378 you can do the verbs and @armand64 you can do special. Let's just read the specification and infer from it.

akshay378 commented 10 years ago

@sevab true, cool lets stick with any for age then and not specify anything. Lets move on to the next bit!

akshay378 commented 10 years ago

So here is the list for the User Vocabulary (Verb) for the customer and admin. Can I ask you guys to go through it once and look for things missing:

User Vocabulary (Verb) - Customer :

• Create
• Browse
• Choose
• Cancel/Start Again
• Sign on
• Book
• Print
• Write
• Read
• Add

User Vocabulary (Verb) - Admin :

✓ Change
✓ Sign on
✓ Browse
✓ Choose
✓ Cancel/Start Again
✓ Distribute
✓ Create

Also, is any one of you recording all this in a document on your laptop or should I do it?

sevab commented 10 years ago

@akshay378 great! Below is the list of nouns. Let's now cross check to make sure everything's there (I'll check yours and you check mine): nouns

Admin -username -password Customer -customer name -password -credit card number Film -title -trailer -synopsis -start date FilmReview -content Newsletter -content -date Screening -price -start date SeatingPlan -seat Ticket

they are all nouns, but I grouped them together and added ticks to make it clearer.

sevab commented 10 years ago

These are the verbs. I think it is more clearer if we group them under appropriate models, what do you guys think?

verbs Admin – change customer details – change film details – change film details details – distribute newsletter Customer – create – sign in – read synopsis, newsletter, reviews – watch trailer – cancel, start again Film – select – browse Film Review – read – write – add to other reviews Newsletter Screening Seat Ticket – book – print – browse Other – charge

akshay378 commented 10 years ago

@sevab as per your list for nouns and what you comment above for verbs, i think it should be for users for the system as a whole? I mean according to the example given on lecture slides, if they would start grouping verbs, nouns and specials for each shrub, that would be a really long list. What do you think? I am uncertain now whether it should be as a whole or as per models from our system.

sevab commented 10 years ago

@akshay378 idk, from the slides it looks like they write the verb across the noun. I don't think it would hurt grouping these together. It only makes things clearer.

akshay378 commented 10 years ago

@sevab we can ask tomorrow maybe? Again, is anyone of you recording these in a document?

armand64 commented 10 years ago

@akshay378 @sevab These are the specials:

Admin Customer Account Cinema Film: last week, next week Ticket: printed, not printed Seat: booked, free Screening Credit-card Price Review Newsletter Contents

sevab commented 10 years ago

@armand64 I think of those the specials are only:

Film: last week, next week Ticket: printed, not printed Seat: booked, free

sevab commented 10 years ago

Now let's do System Requirements

akshay378 commented 10 years ago

@sevab why not Review and Newsletter? They seem to be constant to the system :)

sevab commented 10 years ago

@akshay378 @armand64 The slides say that specials are constants particular to the domain, so they are a kind of variations that nouns can take as I understand. So looking at this table: table

Specials January and April are variations of flowering period. And Bright Pink is a special of a variety.

So in our example last week and next week are variations of a film's starting date. Printed and not printed are variations of a ticket status. Booked and free are variations of seat.

So I'm not sure how Review and Newsletter are specials and not nouns.

sevab commented 10 years ago

We might then want to add ticket printed status and seat booking status to the nouns to reflect the fact that we have specials for these nouns.

armand64 commented 10 years ago

@sevab yeah I think you're right

sevab commented 10 years ago

Let's move to the system requirements then

akshay378 commented 10 years ago

@sevab @armand64 @hornets ok i think i get what you mean now. I am going to put all of these down in a document and save it on my laptop. Lets do system requirements and i'll keep updating that document.

sevab commented 10 years ago

@akshay378 no need, I already keep the document

sevab commented 10 years ago

From the slides

Presented as a numbered list of the form R1, R2, ... with suitable headings for each section to relate the requirements to the User Profiles. • If the system will have several users or roles, there may be one section which applies to all profiles, and then sections for each individual profile • This should be expressed in terms of the derived User Vocabulary where possible

So we need to have 3 sections: Common, User, Admin.

So how shall we divide these?

akshay378 commented 10 years ago

@sevab i can do the user, you do the common, @armand64 can do admin and @hornets can review what we did?

sevab commented 10 years ago

cool

sevab commented 10 years ago

Common system requirements section Sign In:

R1 Allow a user (customer or admin) to sign into the system with their customer name and password, if they are not already signed on.
R2 Ensure that credentials supplied during sign in are correct before signing in the user (customer or admin)

Cancel and start again:

R3 Allow user (customer or admin) to cancel current action and start it again

akshay378 commented 10 years ago

Customer System Requirements

• R1 Allow a customer to browse films for next week by reading synopsis, reviews or watch trailer • R2 Allow a customer to choose a film • R3 Allow a customer to browse the seating plan for a screening available for a film • R4 Allow a customer to choose a seat that is not booked • R5 Allow a customer to book a cinema ticket with chosen seat, screening and film

• R6 Allow a customer to browse their ticket • R7 Allow a customer to print ticket

• R8 Allow a customer to browse films from last week • R9 Allow a customer a read reviews • R10 Allow a customer to write a film review and add to other reviews

• R11 Allow a customer to read a newsletter

Sign Up:

• R12 Allow a customer to create an account using any networked self-service machine. • R13 Ensure that the customer inputs a password, a username and a credit-card number • R14 Ensure that the password is at least eight characters long, includes at least one upper-case character and one digit. • R15 Ensure that the customer name is not taken already • R16 Ensure that the credit-card number is a sixteen digit-number

akshay378 commented 10 years ago

Admin System Requirements :

• R1 Allow the admin to change details of films • R2 Allow the admin to browse films • R3 Allow the admin to choose a film

• R4 Allow the admin to browse films reviews • R5 Allow the admin to choose a film review • R6 Allow the admin to change contents of film reviews

• R7 Allow the admin to create a newsletter • R8 Allow the admin to distribute a newsletter

sevab commented 10 years ago

And here's the sign up for the admin: • R9 Allow an administrator to create an account using only staff's networked self-service machine • R10 Ensure that the admin inputs a password and a username • R11 Ensure that the password is at least eight characters long, includes at least one upper-case character and one digit. • R12 Ensure that the admin username is not taken already

sevab / picture-house

CW4: Front-End Prototype #7