Moving Pictures- Stakeholder Interviews

Moving Pictures is an application that captures information about movies, as well as the rating and reviews of movie fans. Interview transcripts regarding it's functionality have been captured as follows. 

Margaret from Marketing:

Anyone can view the content (which might be movie information, actor profiles or movie reviews) without logging in. (However for other functionality, the user must be logged in to an account).

Content includes:

Movie information - Title, Year, Summary, the production company name, and the actor and

character names. Movies can only be added to the system by PCo Users.

Actor Profiles - show an actor's name, DOB, a brief bio.

Movie Reviews - The review date, a blurb and which Fan submitted it. Only Fans can create a movie review, although they can submit as many reviews of one movie as they like.

Movie Ratings - a rating of a movie, using one to five stars. Only Fans can rate a movie, and they can only rate any movie once.

When viewing Movie information, an account holder may flag it for review. The system creates a 'Content Query', capturing a brief reason, the date and the user. It is marked as "Open" and a notification is sent to the Admin. It is possible that a movie will have many Content Queries. 

David the Data Analyst:

There are three types of accounts. All accounts can edit their own account information.

• Fan account. Anyone can create a Fan account. They submit the information requested (Fan's email, password, and nickname) and the account is created immediately.
• Production Company User account (PCo). Anyone can apply for this account, submitting the PCo information requested (user's name, phone, email, password, and the Production Company's name and address). One submitted, it requires approval by an Admin in order to be created. One Production Company may have many user accounts. PCo users can add and edit their own movie entries, including actor/role data.
• Admin account (establishment out of scope) have only an employeeID and access code.

Admin accounts are necessary to

•  
  • Assess PCo account requests (authorise or decline)
  • Review a Flagged Movie's content (described in more detail below). 

Al the Admin:

Users helpfully create Content Queries when they think a Movie entry needs a review. To review, it's a pre-requisite that I'm of course logged in to the system as an admin. I open the Content Query, and have a look at the content. Usually I'll simply make the change required. However I could instead:

• Suspend the Movie entry (make it invisible to Public and Fan users). I usually do this if I think the content is questionable or inaccurate OR
• Delete the entry. I'll only do this if it's a duplicate entry, or some test data OR
• I can leave it unchanged - sometimes there is nothing wrong.

After any of these paths, I mark that my review is "Complete". The system then emails the relevant Production Company with the Content Query and the outcome.

Note also, sometimes it's all too hard or I get interrupted. I can simply close the Content Query and come back to it another day. No action / changes are recorded at this time. 

IT from IT:

Ensure the system captures the following information:

• Remember an actor can work on multiple movies, and a movie can have many actors. At this stage assume a role is only played by one actor in any one film (we'll deal this issue later)
• Assume exactly one production company creates a film
• Don't worry about how to establish an admin account
• Ignore unmentioned functionality at this stage

Use the transcripts to respond to the questions following. Remember you are being assessed on your UML application skills, not your business or strategy insights. 

Part 1. Moving Pictures Use Case Diagram 

Develop ONE UML use case diagram

Draw ONE use case diagram to capture all functionality mentioned in the staff interviews. Include only activities mentioned by the staff - do not include additional functionality however obvious it may appear (no scope creep!).

Your diagram MUST demonstrate the use of:

• Primary Actors
• Includes & Extends
• Generalisation - both actor and use case
• Abstract actor/s
• Appropriate naming conventions
• Appropriate relationships

Your diagram MUST NOT

• Use extension points (we're keeping it simple - ask if you need help turning them off in VP)
• Use notation not covered by the CPT230 2014 SP1 lecture notes
• Show secondary actors
• Include additional functionality not covered in the interviews, regardless of how obvious it may feel
• Exceed one page

Note, you must incorporate a 'Review Content Query' use case (or similarly named) as

this will be used in Part 2. 

Part 2. Moving Pictures Use Case Textual Description 

Write a use case textual description of the 'Review Content Query' use case

Develop a description of this use case using the "Template - Use Case textual description" as per Appendix A. Be sure to ask for help in the forums if you are not sure of the purpose or use of any field. Use the relevant portion of the interview with Al the Admin to logically document the flow of events.

Your response MUST:

• Use of the template in Appendix A
• Display an understanding of the fields in the textual description
• Provide sufficient detail in the Basic Course of Events and Alt Paths
• Be consistent with Al's interview (don't create or deduct information).
• Stick to the scope of this use case, and refer to other use cases as needed (rather than overlap)
• Be consistent with information you have modelled in your use case diagram

Part 3. Moving Pictures Class Diagram 

Develop a domain level UML class diagram based on the interviews

Consider classes carefully to maintain relationships and eliminate data duplication.

Your diagram MUST demonstrate:

• Classes with appropriate attributes
• Associations, all with appropriate multiplicity
• An example of an association class
• Generalisation and abstract class
• A controlling class named 'Application' with at least some of the operations pertinent to this class (operations in other classes are not required)

Your diagram MUST NOT

• Use notation not covered by the CPT230 2014 SP1 lecture notes
• Include information not required or beyond the scenario
• Show getter or setter methods
• Be inappropriate to the problem domain - e.g. arrays, foreign keys, etc.
• Exceed one page

Your diagram MAY

• Show operations in other classes (no extra marks, not required for A1)
• Show attribute types (no extra marks, not required for A1)

Resist the urge to create sophisticated and complex systems - it will quickly turn into a

large task, and you won't receive any extra marks for it. If in doubt keep it simple. 

Part 4. Moving Pictures Object Diagram 

Develop ONE UML object diagram from your class diagram

Develop an object diagram which fully captures the scenario below. Your diagram should demonstrate data integrity (no data repetition, single values per attribute).

Vito Cornelius (password Aziz) has a PCO user account, for the Production Company Gaurmont. Gaurmont produced the film "The Fifth Element" starring Bruce Willis as Corben.

Zorg has a Fan account (nickname Zorg, password Picasso), and rated The Fifth Element film 1 star. Leeloo also has a Fan account (nickname Leeloo, password multipass). Leeloo rated The Fifth Element 5 stars, and on the 26/02/14 gave a review of "Can Relate". Leeloo also rated another Bruce Willis film Red (where Bruce plays the role of Frank). She rated it 2 stars.

Your diagram MUST:

• Be consistent with your class diagram - this includes naming, attributes, associations & multiplicity
• Demonstrate appropriate use of instances, attributes, and links
• Model all of the scenario in ONE diagram

Your diagram MUST NOT

• Use notation not covered by the CPT230 2014 SP1 lecture notes
• Include information not required or beyond the scenario
• Contain duplication of data or instances
• Break the scenario down into separate object diagrams
• Exceed one page