1Collaborative Design SessionA.K.A. a JAD (Joint Application Development) session2Purpose of a CDS• To work with applications users interactively• To rapidly define requirements• To create a “strawman” (a paper mockup) of a possible UI for an application.• To use to help the design an development team to understand the users needs and wants.• To help create a UI that will be acceptable to the Users3Risks• Risk: What users think they want and what they will really accept are differentMitigation: Usability testing• R: Users will think the application is farther along in development than it really is.M: Use paper prototyping instead of creating software based prototypes• R: Using the time to gather information and/or do initial analysis instead of design.M: Do initial observations and analysis before the session.4Process• Well defined roles of participants• Interactive• Iterative• Facilitated brainstorming• Clearly Defined Goals• Documented Artifacts (drawings, documents, screens designs, etc.)5Process – Roles• Facilitator (1) – guides and controls the process. Manages the time. Timeboxesdiscussion (keeps process focused). Does NOT do the design or contribute information to the design. Asks questions but does NOT answer the questions. Like the official in a football or soccer game.• Scribe (1) – documents what significant information is developed during the session. Records the drawings, and other design that is done on the whiteboards/chalkboards/whitepaper, etc. Does NOT ask or answer the questions involved in the design. Good handwriting and drawing skills. Keeps good, concise notes.6Process – Roles (2)• Design Team (1 or more people)–asks questions of the users. Defines and refines the requirements derived from the information gathered previous to the session and during the session. Draws suggested designs with the input of the users. Suggests the layout, controls, placement, flow, information architecture, etc. • User Team (1 or more people) – answers questions about their business processes and business problems. Tells the designers what their needs and wants are. Gives feedback and suggestions about the designs created by a design team.7Process - Interactive• People ask questions give answers, suggests designs, get feedback, ask questions, give answers, etc.• To manage this chaos is the facilitators role.8Process - Facilitated Brainstorming• There are no stupid questions or stupid answers.• Many seemingly “stupid” questions often lead to innovative design approaches. Brainstorm helps to discover these ideas in a manageable way.• The facilitation is to prevent the discussion from getting off track. The facilitator may:– take discussions “off line” (if they are important but will take too much time in the current session)– declare a “flag on the play” (if someone is out of line, they get a warning, like a “yellow card” in soccer).– Timebox a discussion – give it a certain prescribe amount of time and then declare it is done. Often an interval like 5 minutes, 15 minutes, etc.9Process – Goals -> Artifacts• Understand the users’ wants and needs through interaction and feedback.• Develop software quicker that matches the user’s needs more.• Define and refine:–Users– Actors– Actors Goals–Workflows– Users’ Requirements for the Application– Possible UI layouts, flows and functionality10Process - Artifacts• Document:– Business Entities (objects/concepts)–Users–Actors– Actors Goals– Workflows – tasks and goals for a specific task– Users’ Requirements for the Application– Possible UI layouts, flows and functionality11Tools• Whiteboard / Chalkboard / White Paper• Markers / Chalk / Markers• Information• Observations• Interviews• Imagination• Critical Thinking12ArtifactsThings that are produced in the software development process; info, analysis docs, requirements, design docs, prototypes, code, data, user documentation, etc.13Business DomainBusiness Name:Business Domain (General):Business Domain (Specific):Description:Consumers:Providers:Suppliers:Competitive Businesses:Related Domains:14User• real persons / system that interact with the business. • They utilize the services or consume the products of the business.• Ex: Jane, Jin, Zhou are users of NYU. • A few students in each group should act as users. • Assume the persona of a user– tell what they want the UI to do and why. – tell their goals, tasks, workflows and concerns to the designers. – should not design the UI.– Try to think like a real users NOT like a UI designer.• They will try to design but you should gently encourage them to tell you what the problem is NOT what the solution should be (that isdesign. • They can be given a solution and tell the designers why they think it will/won’t work for their problems.15UserName:Title(s):Age:Education:Training:Skills:Limitations:Other:16Actor• Actors are abstractions of users.• A user may be represented by one or more actor types. Ex: Jane, Jin, Zhou are users of NYU.• Ex Actor titles:– grad student– java developer– coffee drinker– department admin– student club member• Actors play one or more roles. • Roles:– CS Undergrad, CSMasters Candidate, PhD CS Candidate– Beginning Java Dev, expert Java Dev, struts Developer, DB Developer– President Of Web Dev Club, secretary Of Web Dev Club, treasurer …• Sometimes the actors name and the role are the same. You don’t always need to go to this level of detail.17ActorTitle:Role(s):Users in this group:Age Range:Education Range:Training Range:Skills Range:Other:18Goals• Actors have goals. • Why they would use a given service or product. • hope to achieve by using a given product. • A goal accomplishes something. • It usually results in a demonstrable change of state for a given actor. • Ex: Grad Students attend NYU to accomplish the following goals: – get a degree, increase their subject knowledge, get a job, get a better job, meet girls/guys, do something with their time, get away from their parents. • Workflows are done to achieve a goal• A workflow is a series of tasks/activities that are done in a sequence with decision made in between activities to determine what the next activities is. • The degree program tracks are examples of a workflow – you take a certain sequence of courses in a certain order and if you get good