Selected techniques from the Creative Design Process Vision statement Requirements workshop, other facilitated workshops Creative Design Brief Navigation.

Slides:



Advertisements
Similar presentations
Chapter 11 Designing the User Interface
Advertisements

User Experience Modelling
Dreamweaver Domain 3 KellerAdobe CS5 ACA Certification Prep Dreamweaver Domain 2 KellerAdobe CS5 ACA Certification Prep Dreamweaver Domain 2: Planning.
1 Information Systems Development (ISD) Systems Development Life Cycle Overview of Analysis Phase Overview of Design Phase CP2236: Information Systems.
IT Requirements Capture Process. Motivation for this seminar Discovering system requirements is hard. Formally testing use case conformance is hard. We.
Gerhard Dueck -- CS3013Capturing Requirements as Use Cases 1 Capturing the Requirements as use Cases  Requirements Description  We need to describe –The.
© by Pearson Education, Inc. All Rights Reserved.
Rational Unified Process
Use-case Modeling.
UML Extensions for Web Design Design activities: –Partitioning of objects into tiers such as client, server, etc. –Separating and defining user interfaces.
Development Processes UML just is a modeling technique, yet for using it we need to know: »what do we model in an analysis model? »what do we model in.
© 2005 Prentice Hall12-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
From Inception to Elaboration Chapter 8 Applying UML and Patterns -Craig Larman.
1 Software Requirements Specification Lecture 14.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
Mastering OOA/OOD with UML. Contents Introduction Requirements Overview OOAOOD.
Chapter 13: Designing the User Interface
Slide 1 Requirements Workflow. Slide 2 The Phases/Workflows of the Unified Process Figure 3.1 l Phase is Business context of a step Workflow is Technical.
Expression Web 2 Concepts and Techniques Expression Web Design Feature Web Design Basics.
Problemsolving 2 Problem Solving: Designing a website solution Identifying how a solution will function Taking into account the technical constraints a.
Model the User Experience Today:  Detail some Use Cases  Develop a storyboard of the use cases  Sketch mock-ups of the use case's information requirements.
RUP Requirements RUP Artifacts and Deliverables
Requirements Management with Use Cases Module 6: Define the System Requirements Management with Use Cases Module 6: Define the System.
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
Object-Oriented System Analysis and Design Chapter III- Requirement Elicitation Collecting and organizing users requirement- WHAT- User needs.
Chapter 4 User Experience Model. User experience model (Ux) Visual specification of the user interface Visual specification of the user interface Both.
Business Requirements Using Unified Modeling Language Eric H. Castain, SVP Internet Services Group, Architecture Wells Fargo March 2005.
14 Chapter 11: Designing the User Interface. 14 Systems Analysis and Design in a Changing World, 3rd Edition 2 Identifying and Classifying Inputs and.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
Business Analysis and Essential Competencies
IE 411/511: Visual Programming for Industrial Applications
Storyboarding 1. Purpose of Storyboarding  To gain an early reaction from users on the concepts proposed for the application.  They are an effective.
Understanding User Requirements. Documenting Use Cases 2 At this stage of the exploration, the participants should be thinking of essential use cases.
Patterns, effective design patterns Describing patterns Types of patterns – Architecture, data, component, interface design, and webapp patterns – Creational,
Role-Based Guide to the RUP Architect. 2 Mission of an Architect A software architect leads and coordinates technical activities and artifacts throughout.
10/12/ Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 1. Interviews & questionnaires.
Software Engineering Chapter 7 Fall Capturing the Requirements as Use Cases Capturing the Requirements as Use Cases By using use cases analysts.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 4: Developing Requirements.
Chapter 7 Applying UML and Patterns Craig Larman
U.S. Department of Agriculture eGovernment Program Design Approach for usda.gov April 2003.
Requirements as Usecases Capturing the REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
Requirements Capture. Four Steps of requirements capture List candidate requirements Understand system context Capture functional requirements Capture.
Notes of Rational Related cyt. 2 Outline 3 Capturing business requirements using use cases Practical principles  Find the right boundaries for your.
INFO 355Week #71 Systems Analysis II User and system interface design INFO 355 Glenn Booker.
Problemsolving Problem Solving – 4 Stages Analysis Design Development Evaluate (ADDE) Note: In this unit Evaluate is not covered in depth.
UML-1 8. Capturing Requirements and Use Case Model.
A Use Case Primer 1. The Benefits of Use Cases  Compared to traditional methods, use cases are easy to write and to read.  Use cases force the developers.
1 Capturing Requirements As Use Cases To be discussed –Artifacts created in the requirements workflow –Workers participating in the requirements workflow.
Lecture 2 Developing Requirements
Rational Unified Process Fundamentals Module 7: Process for e-Business Development Rational Unified Process Fundamentals Module 7: Process for e-Business.
CSC480 Software Engineering Lecture 8-9 September 20, 2002.
Web Site Design Plan Checklist Web Design Presented by: Angelo Russo #10 11/22/2014Angelo Russo #101.
Creating & Building the Web Site Week 8. Objectives Planning web site development Initiation of the project Analysis for web site development Designing.
Lecture 14 22/10/15. The Object-Oriented Analysis and Design  Process of progressively developing representation of a system component (or object) through.
UML - Development Process 1 Software Development Process Using UML.
An Agile Requirements Approach 1. Step 1: Get Organized  Meet with your team and agree on the basic software processes you will employ.  Decide how.
Oman College of Management and Technology Course – MM Topic 7 Production and Distribution of Multimedia Titles CS/MIS Department.
Requirement Discipline Spring 2006/1385 Semester 1.
5. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Describe the activities of the requirements discipline  Describe the difference.
Learning Aim B.  It is a good idea to think carefully about the design of a website before you try to implement it.
Designing User Experience (UX) This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License.Creative Commons.
What? + How. = Wow! Imani Butler Silver Creek High School San Jose, CA The Methodology In Action: Migrating to a School Loop Hosted Site.
Software Engineering Developing Requirements. © Lethbridge/Laganière 2001 Chapter 4: Developing requirements2 4.1 Domain Analysis The process by which.
Your Prescription for Requirements Management 1. Assumptions The prescription for requirements management is based on the following assumptions:  The.
Section 7.1 Section 7.2 Identify presentation design principles
Web Site Design Plan Checklist
Multimedia and Internet Technology
Phases of Designing a Website
Presentation transcript:

Selected techniques from the Creative Design Process Vision statement Requirements workshop, other facilitated workshops Creative Design Brief Navigation Map Creative Design Comps Web Design Elements Initial Web UI Prototype, UI Guidelines, Full Web UI Prototpe Full Navigation Map

Vision Statement Successful Web applications start with a compelling vision statement. Web solutions involve a variety of stakeholders: business executives, marketing, customer support, development, graphic design, etc., whose communication and cooperation is critical to success. The vision statement must be developed personally by the stakeholders, ensuring agreement on the project‘s goals form the outset. –Discuss potential difficulties.

Vision Statement Purposes of the vision statement: –It achieves agreement on what problems need to be solved –It defines the boundaries of the system –It describes the most important features and qualities of the system.

Requirements Workshop Once the vision is (largely) agreed upon, facilitated workshops are held with the stakeholders to further identify the users and services the system should provide along with the essential qualities and constraints. Use of brainstorming Gathering of requirements on post-it cards to identify actors, use-cases, and supplementary features. Use of other moderation techniques to ensure participation and expression of stakeholders‘ views. Use of UML use-case diagrams and other semi-formal notations (compare WISDM) to capture meanings of stakeholders.

Creative Design Brief The Creative Design Brief identifies the initial user interface guidelines. It defines: –The mood of the site –How users are expected to access the site –The browsers the users will be using –Whether the site will use frames –Any color limitations/orientations the site will have –If applicable, a graphics standards guide –What sort of „bells and whistles“ are wanted (e.g. mouse-overs, animation, news feeds, multimedia, …)

Navigation Map The navigation map („site map“) is a view that represents the web application in the form of a tree diagram. Each level of the diagram shows the number of clicks necessery to to get to that (logical) page. (if possible, # ≤ 3) The navigation map evolves from the use-case model, it accompanies the use-case storyboard. For a larger system, one navigation map is constructed per actor (or even per use-case).

Creative Design Comps Creative Design comps present to the stakeholders a number of visual options. Comps consist of mock-ups of what the site might look like. They are non-functional, flat pictures framed with browser window graphics. They help to postpone the investment for the more costly HTML prototypes. To create Comps, we take an important use-case and develop many alternative designs. Three most promising options are selected to be presented to the stakeholders. Typically it takes three iteration before a consensus on the final design is reached.

Web Design Elements Web Design Elements are discrete images that are assembled to build the web pages. Consistency of the user interface across a web site is essential to usability, since the site should provide a consistent user experience. The project must consistently use a set of standard graphhical components across the site. These components should be developed early in the project, along with guidelines for their usage. Reusing (a tight set of) high quality standard graphical elements reduces development cost and increases quality. The Creative Design Comps serve as input for the web design elements being created in parallel with the initial UI prototype.

Initial Web UI Prototype The initial UI prototype is based on the Use-Case storyboard, the Creative Design Comps and uses the Web Design Elements identified before. It typically supports only portions of the system, based on the most important and representative use cases.

UI Guidelines Detailed guidelines for the user interface are developed after the initial user interface prototype is complete. This system specific style-guide specifies e.g.: –How and when web design elements shall be used –Color schemes, fonts –Cascading style-sheets or XSL specification –Details on how navigational elements shall function and be positioned.

Full Web UI Prototype; Full Navigation Map Based on initial UI prototype Covers all use-cases Demonstrates full navigation between screens and visual elements Real or dummy data is used depending on the development of the functionality and content of the application Goal: Come to agreement with the stakeholders on the scope and specific nature of each of the user interfaces. The full navigation map includes all known pages/screens identified in the web UI prototype.

Overview of combining Creative Design techniques with the UP

Navigation Map Insert an example for a full web site navigation map. Use either Fig., 2 from ers/ jsp or better something adapted from that figure. ers/ jsp