MIS3504 Fall 2015 Section 3

Class Discussion on User Experience

JustinMind demonstration on the creation of a solution scenario

Team submission of draft persona(s) and scenario(s)

Exam 2

Draft views of your team’s User Persona(s)  and Scenario(s)

Deliverables:

Use the persona template found on the web site to describe the typical user(s) that will be engaged in the project solution.  Depending on the project solution there may be more than one persona.

Create a draft outline of scenario(s) that the user will work thought as it pertain to the project solution.  The scenario(s) tell a story as to how the user interacts with the solution, there many be one or more scenarios needed to tell the story.  For the initial draft of the scenario(s) you may create a simple document or PowerPoint slide that outlines the steps and decisions in the form of bullet points.

Exam 2 will be taken on October 27, 2015  during the last hour of class

The Exam will primarily focus on the analysis tools outlined and demonstrated in class discussions 5 –  (Process Mapping), 6 –  (Data Mapping and Relationships)  and 7  – (Business Rules and Decision Trees)  and the respective individual case assignments.

Key topic areas covered in the exam will be: Process Flows, (Swim Lane), Data Analysis (Entity Relationship) and Business Rules (Decision Tree).

Chapter 6 in the text book specifically covered the analysis tools with addition background information found in chapter 4.  Review of the class discussions posted on the web site and follow up case assignments will serve as good study aids.  The Software Requirements Memory Jogger also has examples of the analysis tools and the their components.

Case Solutions can be found on the web site page: Case Assignment Solutions

Turn in case assignment due for JustinMind Introduction Lab2

Review Case assignment for – Business Rules/Decision Tree

Class Discussion on Persona – Scenario – Prototype

Exam 2 Review

Team Project As Is deliverable review

Complete the JustinMind Prototype Introduction Lab2

Due on 3/17/2015

Turn in a hardcopy print out at the beginning of next weeks class

Lab can be found under the Assignment Case Material section of the website

JustinMind Prototype Introduction Lab 2

Turn in case assignment due for Decision Tree Case Study

Review Case assignment for Data Analysis – Case

JustinMind demonstration of linking screens and review of individual assignments

Class Discussion on Design and Team Exercise

Team Project time to work on As Is analysis and deliverables

Individual Challenge: 

Case Study  

Due Class 8, October 13, 2015

We Sell All Cars – Decision Tree Case

Business Rule Template

Follow up on Team Project Scope Documents

Review Swim Lane Process flow case assignment

Class discussion on business rules

Team exercise on decision diagram

Review individual assignment on business rules / decision diagram due 10/13/2015

Project Team Support and questons

Individual Assignment:

Data Analysis Case:  Solutions-Plus Client Project Data Analysis

The Deliverables:

Use the ERD Sample Excel Template to:

1. Create a Glossary of terms from the case
2. Identify all the data entities that the Solutions-Plus Client Project Case will need.
3. For each entity, identify all of the attributes that must be collected.
4. Indicate the relationships between the different entities.

Use the tool of your choice (Excel template ERD Tab, Google docs, MS Access, Word, or Sketch on Paper) to create an ER or Schema Diagram to demonstrate the relationships graphically

Team Assignment:

Revised Team Project Scope based on follow class discussion:

• In the third paragraph of the scope document’s problem statement, be sure to include the specific deliverables outlined in the Team Project Deliverables section of the class web site.
• Use the deliverables from the scope document to layout a project plan (timing and resources) with the project managers assigned to your team (the creation of project plan is the Project Managers responsibility).
• Review and adjust the project scope Objectives to ensure they are written as a measurable set of metrics in which your teams proposed solution can be evaluated against.
• Please have an updated copy of the Scope document ready for review.