1. 1/10 POSDATA Team EVR:MAKING USE Hou, Kyu Cho, Eun Young Jeung, Min Ho Jung,Hee Joon

2. 2/10 POSDATA Team Contents Design Characteristics Scenarios Role of Scenarios Scenario based Design Use Cases vs. Scenarios Reflection SBD on Studio

3. 3/10 POSDATA Team Design Characteristics Six characteristic and difficult properties of design –Incomplete description of the problem –Lack of guidance on possible design moves –The design solution state cannot be know in advance –Trade-offs among many interdependent elements –Reliance on a diversity of knowledge and skills –Wide-ranging and ongoing impacts on human activity Design is tough –Description of current situation is inaccurate, irrelevant –Understanding of problems does not specify the solution –Design requires a diversity of skills and knowledge

4. 4/10 POSDATA Team Scenarios What is a scenario? –Describe narratively what users do for future system –A sequence of actions and events that lead to an outcome –Present various stakeholders’ view –Differ from a list of requirements and specifications Different approach of requirements Function based Scenario based Focus on what functions should be included in the system Hard to gather all requirements by listing them Boring and frustrating Focus on what users may interact with future system Include all kinds of user activities Easy and interesting

5. 5/10 POSDATA Team Roles of Scenarios Task scenario Usability spec. Summativeevaluation Functional spec. UI metaphor Prototype Design rationale Documentation, Training & help Object model Formativeevaluation System vision

6. 6/10 POSDATA Team Scenario based Design(SBD) What is scenario based design? –Manage the complexity of design problem not by abstraction but by concretization –Focus on design work from describing how people will work by using future system Strengths of scenario based design –Enable rapid communication about usage possibilities and concerns among many different stakeholders –Push designers beyond static answers by creating and using scenarios –Concrete but flexible - Particular usage to be prototyped - Easy to revise or elaborate

7. 7/10 POSDATA Team Use Cases vs. Scenarios Use Cases –Focus on WHAT the actor interacts with the system –Each use case contains all the paths to reach a goal –Provide a conceptual model of the system –Tend to be individual function oriented Scenarios –Focus on HOW the system prompts for information –Each scenario is a possible path with specific information –Provide rich, informal and open-ended descriptions of real practice –Activity oriented

8. 8/10 POSDATA Team Reflection SBD on Studio (1/2) Overall System Blueprint Automatic Fare Collection Home Network Remote Control Intelligent Transit System ETCS Business Bureau Home Network Business Bureau WiBro Mobile Internet Business Bureau Internet Transport Broadcasting Business Bureau TV DMB DVR Business Bureau Future Application Future Business Hands-free Mobile Phone Stock Game Park Restaurant Travel Lodging Road Guidance Repair Service AVLS Gas station Interface integration layer

9. 9/10 POSDATA Team Reflection SBD on Studio (2/2) Challenges of Studio –S/W failure may cause critical situations in automobiles –A lot of interaction with external systems are necessary –Software components are growing Benefits of SBD –Provides easy way to communicate with clients –Allows for exploration of all possible scenarios in critical situation –Independent from member’s technical backgrounds –Enables to make variety of realistic test cases

10. 10/10 POSDATA Team Q & A