This document provides an overview of Joe Sokohl's presentation on detailed design for preserving the user experience vision. The presentation covers what detailed design is, where it breaks down, and potential solutions. It applies to agencies, independent UX practitioners, and distributed or cross-border teams. The presentation compares typical documentation approaches to detailed design processes like VIEWW and FiveDs and discusses activities at each stage to refine requirements and designs for development.
Agile Methods for NTU Software EngineersAndy Marks
A 1 hour presentation given to 2nd year NTU students on Feb 29 2012 by Jolly Tan.
Covers a brief overview of Agile, a comparison of XP and Scrum and finishing with a quick introduction to Lean Startup, Lean and Continuous Delivery thinking.
Natalie Hanson, PhD. April 2011 presentation to the Philadelphia chapter of ACM-CHI (Association for Computing Machinery, special interest group on Computer Human Interaction).
Agile Methods for NTU Software EngineersAndy Marks
A 1 hour presentation given to 2nd year NTU students on Feb 29 2012 by Jolly Tan.
Covers a brief overview of Agile, a comparison of XP and Scrum and finishing with a quick introduction to Lean Startup, Lean and Continuous Delivery thinking.
Natalie Hanson, PhD. April 2011 presentation to the Philadelphia chapter of ACM-CHI (Association for Computing Machinery, special interest group on Computer Human Interaction).
This presentation was made by Adam Monago in China in 2009. It covers topics like
Agile and Analysis: Common Misconceptions
Agile Analysis
Agile Analysis Life Cycle
Defining Objectives and Trade-Offs
SADT & IDEF0 for Augmenting UML, Algile & Usability EngineeringDavid Marca
Correct and complete context for software engineering requires domain modeling. Structured Analysis and Design Technique (SADT/IDEF0) is a proven way to model any kind of domain. This talk explains how SADT/IDEF0 domain modeling can bring correct and complete domain knowledge, including all required context, to today’s commonplace disciplines of Agile System Development, Unified Modeling Language (UML) methodology, and Usability Engineering methods.
This study focuses on the effects of interactive energy visualization in residential domain to understand if an energy interface with social and competitive elements motivates residential users to become proactive in energy conservation; further verifying effectiveness of such interfaces in increasing awareness at community level.
Leveraging Reusability and Traceability in Medical Device DevelopmentSeapine Software
Learn best practices for creating verifiable, traceable requirements. The presentation also includes information about how Seapine's TestTrack supports streamlining better processes, data capture, reusability, and traceability in the requirements phase and a Q&A session.
An Introduction to Software Performance EngineeringCorrelsense
Software performance engineering is becoming increasingly important to businesses as they look to improve the non-functional performance of applications and get more out of IT investments. By leveraging performance engineering techniques, IT professionals can be indispensable in building and optimizing scalable systems. This
introductory course will teach you the essentials of software
performance engineering including :
• The performance challenges faced by Enterprise IT today
• What is software performance engineering (SPE)?
• Best practices for building scalable software systems
• The approaches to integrating SPE into IT project lifecycles
• Common frameworks for measuring application performance and service levels
• The impact of SPE on software developers, testers, capacity planes,
and other IT professionals
• Case studies from the finance, retail, and insurance industries
Instructor: Walter Kuketz, SVP and CTO, Collaborative Consulting
This training is sponsored by Correlsense, Collaborative Consulting,
and New Horizons
This presentation was made by Adam Monago in China in 2009. It covers topics like
Agile and Analysis: Common Misconceptions
Agile Analysis
Agile Analysis Life Cycle
Defining Objectives and Trade-Offs
SADT & IDEF0 for Augmenting UML, Algile & Usability EngineeringDavid Marca
Correct and complete context for software engineering requires domain modeling. Structured Analysis and Design Technique (SADT/IDEF0) is a proven way to model any kind of domain. This talk explains how SADT/IDEF0 domain modeling can bring correct and complete domain knowledge, including all required context, to today’s commonplace disciplines of Agile System Development, Unified Modeling Language (UML) methodology, and Usability Engineering methods.
This study focuses on the effects of interactive energy visualization in residential domain to understand if an energy interface with social and competitive elements motivates residential users to become proactive in energy conservation; further verifying effectiveness of such interfaces in increasing awareness at community level.
Leveraging Reusability and Traceability in Medical Device DevelopmentSeapine Software
Learn best practices for creating verifiable, traceable requirements. The presentation also includes information about how Seapine's TestTrack supports streamlining better processes, data capture, reusability, and traceability in the requirements phase and a Q&A session.
An Introduction to Software Performance EngineeringCorrelsense
Software performance engineering is becoming increasingly important to businesses as they look to improve the non-functional performance of applications and get more out of IT investments. By leveraging performance engineering techniques, IT professionals can be indispensable in building and optimizing scalable systems. This
introductory course will teach you the essentials of software
performance engineering including :
• The performance challenges faced by Enterprise IT today
• What is software performance engineering (SPE)?
• Best practices for building scalable software systems
• The approaches to integrating SPE into IT project lifecycles
• Common frameworks for measuring application performance and service levels
• The impact of SPE on software developers, testers, capacity planes,
and other IT professionals
• Case studies from the finance, retail, and insurance industries
Instructor: Walter Kuketz, SVP and CTO, Collaborative Consulting
This training is sponsored by Correlsense, Collaborative Consulting,
and New Horizons
Calen Legaspi, O&B CEO, discusses a quick overview of Agile Software Development for the absolute beginner.
About O&B:
Orange & Bronze is a proponent of Agile Software Development. We believe that software development requires a collaborative environment where the software can start and evolve into a useful and strategic system. A common vision between O&B and the client is essential to have an effective collaborative environment. This, along with constant communication and repeated testing, ensures that the project will be delivered on time, all the time.
Orange & Bronze is an offshore product and software development firm in the Philippines, is one of the first companies in Asia to use and advocate Agile Software Development, and has been using it since our inception in 2005, back when Agile was still an emerging movement. O&B offers training courses for Agile with Scrum and XP - these classes were developed and are taught by some of the Philippines' well-known and respected Agile / Scrum coaches and practitioners, and uses the format trusted by some of the best companies in the Philippines.
Mage Titans USA 2016 - Mathew Beane - Edit Fully Stacked: Less OOPS, More OPS...Stacey Whitney
Learn how to make development and operations work together while using Magento. This session will explore Magento dev-ops community resources, leading practices, common tools, and software. A quick look at server choices under today’s cloud environments will illustrate how to simplify the whole process while developing or deploying with Magento 1 or Magento 2.
Out of My Brain on the 5:15 | Practical User Research for the Enterprise UXerjsokohl
In some ways, this talk is a simple one, designed to provide a single solution to a core problem facing all us UXers: Too many project managers, product managers, project sponsors, and so on balk at the idea of performing ANY user research.
Two key objections arise when user research is proposed:
“Our users don’t have time to go to a focus group or a conference room and spend hours listening to someone or doing inane exercises.”
“We can’t spend tons of project time for six months just fiddling around with talking to users…who need to be doing their jobs, by the way.”
To cut through this barrier, I came up with the method I call “”5:15.”” Put simply, it involves asking a person to commit to answering five questions in only 15 minutes.
Almost no one can spend two hours out of their workday talking to a user experience researcher; almost everyone has 15 minutes. Even asking someone for an hour of their time seems excessive, especially in enterprise settings. However, that request for 15 minutes seems innocuous.
We’ll look at how these questions work well, how you can gain insights easily, and why you should never take NO to research plans as an answer.
Kill Your Darlings: Solving Design by Throwing Away Your Prototypesjsokohl
Wireframing has held sway over UXers for the past 20 years. From its metaphoric origins in filmmaking to its pinnacle in countless UX books, wireframing stood as a key approach in defining both structure & interaction. In recent years, however, wireframing has come under attack. UX thinkers propose replacing wireframes with sketches and prototypes; yet we need to understand that bridge between idea and specification.
I spent several years as a manager, a booking agent, a road manager, and a radio DJ in one of my pasts. Several key ideas from that life apply directly to my UX world.
How do we move from research to design to development without losing sight of the user experience. This session looks at specifying UX artifacts for team members to glean meaning from our work. How does experience design specify its output in a way that developers can code and business can understand how the UX relates to business requirements?
"When we said we wanted a house at Bear Creek," client Lillian Kaufmann said to Frank Lloyd Wright, "we didn't imagine you would build it ON the creek!"
To which Wright replied, "In time you'd grow tired of the sight of creek...but you'll never grow tired of the sound."
And he was right. Fallingwater stands as the most recognized house in architecture. yet it's not just a landmark...it was a home. The Kaufmanns' loved it.
Similarly, owners of other Wright-designed buildings may have struggled with the architect, the implementation may have had flaws, the builders and other constructors may have gone behind Wright's back to fix perceived design flaws... but they all loved the buildings. The architect's vision remains inspiration to this day.
This presentation looks at three Wright landmarks— Fallingwater in Ohiopyle, the Pope-Leighy house in Alexandria, and Taliesin West in Phoenix— and the experience architecture inspiration they hold for experience designers.
I also believe that, through Wright's examples, we can learn elements that take our approaches to experience architecture to newly useful and inspiring levels for our clients and the users of our work.
During this presentation, we'll take a look at pictures and principles from these three sites. We will explore analogs to our practice through these elements:
* Context: How does the site selection integrate with user needs and desires?
* Clients: What do Wright's relationships with his clients teach us? Where did he innovate, and where did he fail?
* Connection: How does the architect connect the lives of the clients with the results of the design? Expect lots of pictures.
Make it or Break It: Evolutionary or Throwaway Prototypingjsokohl
Prototyping is a key tool for improving the user experience and defining a product. What's the best approach: incrementally use the target development environment to create the code, or use a technique that explores design ideas without delivering on the prototype platform?
As Agile teams struggle with how to address the user experience, they often look to models that tack UX activities on to their process. UX architects & designers spend time begging for a place at the Agile table, while developers & PMs & product owners scratch their heads, wondering what these weird folks are doing on their teams.
Yet rather than asking, "How do we tack UX onto Agile?" let's let’s ask, “Do we want to define projects with users in mind? If we do, then who should be responsible for that task?” This session looks at how user experience is taken into account in projects, why user requirements should lead project development, and how addressing UX provides key business value.
Agile team professionals often find themselves working on projects with tight deadlines, tighter budgets, and unreasonably high expectations for success. Too often user research, usability, and design processes are compressed or even cut entirely for the sake of time, while development and business analysis time is increased. As UX professionals become more involved with agile development methods, we have discovered novel approaches to user-centered design that are adaptable to any budget or deadline.
This discussion will explore how user research, usability, IA and interaction design practices are adapted and thrive in agile projects.
Focusing on their experiences at Agile 2009 in Chicago this past fall, they will discuss:
* How to provide timely and valuable UX support to stressed web development teams
* How to let go and modify research/design/development dogmas
* How to advocate for users when time for user research and usability are unavailable
* How to balance rigor, quality, and speed
How Can You Be in Two Places at Once: Designing Across Space and Timejsokohl
Design often is considered an in-person collaboration. Perhaps, however, we can leverage key principles and base tools to enhance our lives as well as our designs. Not only do we work with people across the hall, across town, and across the country, but we also work with people we never meet.
Technology has provided us the ability to work in many ways, telecommute to save fuel and frustration, reduce travel costs, and use various forms of communication. The promise is there, yet the reality sometimes eludes us.
An old presentation about what human-computer interaction is, what usability is, and how it fits into development. Pondering now just how well this stands up. It seems to...but....
1. Nailing It Down
Detailed Design to Preserve the UX Vision
STC Summit 2011
Joe Sokohl
@mojoguzzi
#dtlDesign at #STC11
CONFIDENTIALITY
The concepts and methodologies contained herein are proprietary to Regular Joe Consulting LLC.
Duplication, reproduction or disclosure of information is this document without the express written
permission of Regular Joe Consulting is prohibited. Enjoy the work. We hope you find it useful.
Tuesday, May 17, 2011
2. Agenda
What “detailed design” is
Where it breaks down
What some solutions are
@mojoguzzi #dtlDesign 2
Tuesday, May 17, 2011
3. A bit about me
http://www.uxaustralia.com.au/conference-2010/design-thinking-is-this-our-ticket-to-the-big-table
@mojoguzzi #dtlDesign 3
Tuesday, May 17, 2011
4. Who this talk applies to
Agencies
Independent UXers
Highly regulated areas: healthcare, government,
military
Anyone working with distributed teams (including
cross-border, multiple time zone teams)
UX teams of one
@mojoguzzi #dtlDesign 4
Tuesday, May 17, 2011
5. Who this talk might not apply to
Heterogenous teams
UXers who also do the front-end
development of their apps
Co-located, nimble teams who don’t have
a need to retrace steps
Then again....
@mojoguzzi #dtlDesign 5
Tuesday, May 17, 2011
7. So what’s the big deal, anyway?
Determining what the problem is
7
Tuesday, May 17, 2011
8. Typical documentation approaches
Research artifacts such as competitive reviews,
heuristic analysis, mental models/affinity diagrams,
and personas
User/task matrixes
Hi-level wireframes
Concept models
Card sorts
And on and on and on...
@mojoguzzi #dtlDesign 8
Tuesday, May 17, 2011
9. Typical documentation approaches
Research artifacts such as competitive reviews,
heuristic analysis, mental models/affinity diagrams,
and personas
User/task matrixes
Hi-level wireframes
Concept models
Card sorts
And on and on and on...
@mojoguzzi #dtlDesign 9
Tuesday, May 17, 2011
10. What is Detailed Design?
Looking at different processes
10
Tuesday, May 17, 2011
11. VIEWW Summary
VISION INCEPTION ELABORATION WORK WEB
Discover the project goals, Design the information Refine the User Experience Develop the application, Deploy the finished
define requirements, and structure and system Design & System Design so integrating front end and application into production,
frame the initial scope of architecture of the an application can be built. back end systems. transfer ownership to
an application. application. support and maintenance
teams.
Activities Activities Activities Activities Activities
• Gather Input on Business, • Create High-Level User • Usability Testing • Create Deployment Plan • Initial Data Load
User and System Experience Design
• User POC • Update Detailed Design • Deployment
Requirements
• Create User Proof-of-Concept Document
• Create Detailed User • Create Administrative Guide
• Define Business
• Conduct Usability Testing Experience Design • Develop Components
Requirements • Develop User Education
(Component Source)
• Create High-Level System • Assess and Select Manual
• Define User Requirements
Architecture Technologies • Conduct Code Review
• Transition to Maintenance
• Develop Creative Brief
• Create Technical Proof-of- • Deployment Plan Team
• Define System Requirements Concept
• Detailed Architecture FUNCTIONAL
• Develop Initial Deployment TESTING RESULTS
• Create Technical POC USER ACCEPTANCE
Specification
REQUIREMENTS TESTING RESULTS
• Coding Standards
DOCUMENT
• Plan and Implement
HIGH-LEVEL
Development Environment
DESIGN DOCUMENT
DETAILED DESIGN
DOCUMENT
@mojoguzzi #dtlDesign 11
Tuesday, May 17, 2011
12. FiveDs Summary
Discover Design Define Develop Deliver
Define project goals, Further define a Refine design details, Build and integrate Complete the
business reqs, set of requirements create final design and front-end and commercialization of
and initial scope. and create systems obtain signoff. back-end systems. the product
and UX models
Activities Activities Activities Activities Activities
• Define goals • Brainstorming • Merge visual and • Image and page • Acceptance testing
functional design creation
• Key success factors • Scenario building • System and
• Final content • Content integration knowledge transfer
• VOC workshops • Wireframes
• Test scenarios • Coding • Product deployment
• EOC interviews • Visual direction
• Object analysis, • Unit testing • Marketing campaign
• B/U/S requirements • HL Info Architecture
modeling, design
• System staging in
• Site analysis • HL Sys Architecture
• Database analysis QA environment
• Audience analysis • Define technology and design
• Incremental QA and
• Initial use cases • Design testing on multiple
• Business processes documentation platforms
@mojoguzzi #dtlDesign 12
Tuesday, May 17, 2011
13. FiveDs Summary
Discover Design Define Develop Deliver
Define project goals, Further define a Refine design details, Build and integrate Complete the
business reqs, set of requirements create final design and front-end and commercialization of
and initial scope. and create systems obtain signoff. back-end systems. the product
and UX models
Activities Activities Activities Activities Activities
• Define goals • Brainstorming • Merge visual and • Image and page • Acceptance testing
functional design creation
• Key success factors • Scenario building • System and
• Final content • Content integration knowledge transfer
• VOC workshops • Wireframes
• Test scenarios • Coding • Product deployment
• EOC interviews • Visual direction
• Object analysis, • Unit testing • Marketing campaign
• B/U/S requirements • HL Info Architecture
modeling, design
• System staging in
• Site analysis • HL Sys Architecture
• Database analysis QA environment
• Audience analysis • Define technology and design
• Incremental QA and
• Initial use cases • Design testing on multiple
• Business processes documentation platforms
@mojoguzzi #dtlDesign 13
Tuesday, May 17, 2011
14. User Experiences Go Beyond the User Interface
Expectations frame users’
experiences through brand
perception and prior
experience
Users achieve goals by
performing tasks
They accomplish tasks by
interacting with content, Powerful Interactions
features, and functions in the
agent portal and other
applications, software and
tools
User interfaces bring the
User Rich Internet Application Solutions Single, reliable view of the
Single View of the
user experience alive, Interfaces Customer user’s entire relationship
providing simplified, with the enterprise supports
enjoyable online interactions Distributed Content business processes critical to
and instant feedback in and Functionality the delivery of a seamless
Web Sites Software / Tools Applications experience
flexible, intuitive and
forgiving workspaces
Business Information Identity
Processes Delivery
Transactional Analytics
Management
Loosely joined customer-
facing and internal business Content Reporting and
Notification Syndication
processes support quick and Management Monitoring
continuous experience
improvement Marketing Campaign Authentication and
Workflow Others
Management Authorization
Reliable content Experience
and data form the Enablers
foundations of a strong
user experience
product / service meta data analytic data user
content & data
•••
Beautiful experiences are more than pixel deep
@mojoguzzi #dtlDesign 14
Tuesday, May 17, 2011
16. Detailed Design Activities
Detailed sketches
Detailed scenarios with branching
User-centered use cases
Visual design specifications
Database design, specifically, fields & interactions
Exact interaction design, to include motion
High-fidelity (and possibly evolutionary) prototypes
L10N/I14N/A11Y
What else?
@mojoguzzi #dtlDesign 16
Tuesday, May 17, 2011
17. What’s the difference between reqs & specs?
Requirements
Requirements cannot be “gathered”
Requirements are not features
Requirements are not specifications
Specifications
“Effective documentation combines
text and images to describe the
anatomy and physiology
of a product.”
@mojoguzzi #dtlDesign 17
Tuesday, May 17, 2011
18. What’s Your Definition?
• My definition? A detailed design is
• The body of information that conveys
sufficient detail to communicate that
which can be coded.
• Just enough detail to enable the non-UX
team (dev, biz, mkt, release) to
understand the UX designer’s intent.
@mojoguzzi #dtlDesign 18
Tuesday, May 17, 2011
20. Where do they break? Why
Spec need
Team proximity or regulatory need (or both)
@mojoguzzi #dtlDesign 20
Tuesday, May 17, 2011
21. Two Sides of the Problem
?? !!
@mojoguzzi #dtlDesign 21
Tuesday, May 17, 2011
22. Requirements masquerading as specifications
Traditional approach
1.1.1. The system shall allow the teacher to
click a control which displays the first answer in the
lesson.
NOTE: Subsequent answers can be accessed by
User story approach
As a clinician and/or front desk assistant, I need to record the writer, provider(s),
assistant(s), as well as the date and time of entry for every clinical note, so that I can
maintain accurate clinical records.
@mojoguzzi #dtlDesign 22
Tuesday, May 17, 2011
23. Requirement: Turn indicators
1.3.2.5a: The system shall
include the ability for the
operator to indicate a changed
direction of travel
As a motorcyclist, I want to
indicate to followers the direction
I’m turning so that I won’t be hit.
@mojoguzzi #dtlDesign 23
Tuesday, May 17, 2011
25. Maybe a bit tooooo much....
Planning Track
Dev Project
IPM Officer
Manager Manager
QA
Manager
Once, at start of project
Org Process Guidance Project Process Instance
Tailoring Guidelines Project Plan
Vision Statement Master Schedule
Personas Risk Management Strategy
Plan Project
BaselineCM Project Commitments
Master Schedule Test Metrics
Test Approach
Release
Manager Define-Update Test
Approach
Track Complete
Test Approach
once per project
CM Guidelines CM Plan
Baseline CM Guidelines
Configuration
BaselineCM CM Access Control Policy
Management
CM Baseline Report
Every iteration
Scenario List
Scenario List Create a Scenarios
BaselineCM
Scenario
Architect
Business
Analyst
UATs
Every iteration
Iteration Start
QoS Req List
scenarios Create a Quality of
BaselineCM QoS Requirements
@mojoguzzi
Lifestyle Snapshot #dtlDesign Service Requirement 25
Tuesday, May 17, 2011 User Subject
26. A bridge to nowhere?
@mojoguzzi #dtlDesign 26
Tuesday, May 17, 2011
27. “
That is not it at all,
That is not what I meant,
at all. . . . . .
”
http://static.guim.co.uk/sys-images/Guardian/Pix/pictures/2009/3/30/1238371335802/TS-Eliot-003.jpg
@mojoguzzi #dtlDesign 27
Tuesday, May 17, 2011
29. Big, grandiose statement
Anything that specifies user
behavior or activities that
affect users belongs to the
user experience team
@mojoguzzi #dtlDesign 29
Tuesday, May 17, 2011
30. Big, grandiose statement
Anything that specifies user
behavior or activities that
affect users belongs to the
purview of the user
experience team
@mojoguzzi #dtlDesign 30
Tuesday, May 17, 2011
31. Who Does What
Typical roles on a project
PO Product owner
PM Project manager
IA Information architect
IxD Interaction designer
VisD Visual designer
TW Technical writer
BA Business analyst
SA Systems architect
DA Data architect
DBA Database analyst
Dev Developer
QA Quality assurance analyst
@mojoguzzi #dtlDesign 31
Tuesday, May 17, 2011
32. Sometimes specs fall into the wrong hands
@mojoguzzi #dtlDesign 32
Tuesday, May 17, 2011
33. Special order 191
Major Taylor will proceed to Leesburg, Va., and arrange for transportation of the sick and
those unable to walk to Winchester, securing the transportation of the country for this
purpose. The route between this and Culpeper Court-House east of the mountains being
unsafe will no longer be traveled. Those on the way to this army already across the river
will move up promptly; all others will proceed to Winchester collectively and under
command of officers, at which point, being the general depot of this army, its movements
will be known and instructions given by commanding officer regulating further movements.
III. The army will resume its march tomorrow, taking the Hagerstown road. General
Jackson's command will form the advance, and, after passing Middletown, with such
portion as he may select, take the route toward Sharpsburg, cross the Potomac at the
most convenient point, and by Friday morning take possession of the Baltimore and Ohio
Railroad, capture such of them as may be at Martinsburg, and intercept such as may
attempt to escape from Harper's Ferry.
IV. General Longstreet's command will pursue the main road as far as Boonsborough,
where it will halt, with reserve, supply, and baggage trains of the army.
V.General McLaws, with his own division and that of General R. H. Anderson, will follow
General Longstreet. On reaching Middletown will take the route to Harper's Ferry, and by
Friday morning possess himself of the Maryland Heights and endeavor to capture the
enemy at Harper's Ferry and vicinity.
@mojoguzzi #dtlDesign 33
Tuesday, May 17, 2011
35. Solutions
More detail at the right time
35
Tuesday, May 17, 2011
36. What Are Some Solutions
Frameworks
Style guides and pattern libraries
Accurate diagrams and traceable notes
A proverbial seat at the table.
@mojoguzzi #dtlDesign 36
Tuesday, May 17, 2011
37. Frameworks and design principles
NextGen Design Principles & Frameworks: a Case
Study
Windows Presentation Framework
HTML5
CSS
@mojoguzzi #dtlDesign 37
Tuesday, May 17, 2011
38. Style guides and pattern libraries
Apple HI Guidelines
YUI!
Search Patterns from Peter Morville
NeXTStep Style Guide
@mojoguzzi #dtlDesign 38
Tuesday, May 17, 2011
39. Let’s Talk Traceability
Along the Natchez Trace
@mojoguzzi #dtlDesign 39
Tuesday, May 17, 2011
40. Old School is So Old School
@mojoguzzi #dtlDesign 40
Tuesday, May 17, 2011
41. Display All Taxes & Fees - Currency
References
Functionality of this page is based on the current reservation review, reserve, and
confirmation pages. It covers reservations made in currency amounts. The GCCI free Use Case: 3.3
night reservation confirmation wireframe appears on the next page. Requirements Matrix: 4.A.1, 4.A.2, 4.A.3, 4.A.4
All modified items should be consistent with existing functionality and visual standards. Site Map: site_map_display_all_fees
Base Wireframe: 4.1,4.2,4.3,4.4,4.5
1 Separated Rooms and Fees
The room stay is separated by first the total for all rooms reserved,
without any taxes or fees. Then the estimated taxes and fees
1 appears, followed by the total stay amount. If taxes and fees are
included in the rate, use the term “included”.
2 Breakdown of Taxes and Fees
2
The system breaks out and identifies all taxes, separate from any
optional service charges. The CPM system provides the tax and
fee information. If taxes and fees are included in the rate, use the
3 term “included in reservation amount”.
3 Optional Service Charges
If the property assesses any additional yet optional charges, they
appear here. If there are no optional charges, do not display
anything.
4
4 Additional Confirmations
The Reservation Amount module appears the same on the
following pages:
• Reservation Confirmation Email
• Change Reservation
• View Reservation
• Cancel Reservation
It contains the same information as the Reservation summary, just
in a different layout.
Best Western International Web Release I (AR0637) E,W, W Keane Architecture Services 41
Tuesday, May 17, 2011
42. Display All Taxes & Fees - Currency
References
Functionality of this page is based on the current reservation review, reserve, and
confirmation pages. It covers reservations made in currency amounts. The GCCI free Use Case: 3.3
night reservation confirmation wireframe appears on the next page. Requirements Matrix: 4.A.1, 4.A.2, 4.A.3, 4.A.4
All modified items should be consistent with existing functionality and visual standards. Site Map: site_map_display_all_fees
Base Wireframe: 4.1,4.2,4.3,4.4,4.5
1 Separated Rooms and Fees
The room stay is separated by first the total for all rooms reserved,
without any taxes or fees. Then the estimated taxes and fees
1 appears, followed by the total stay amount. If taxes and fees are
included in the rate, use the term “included”.
2 Breakdown of Taxes and Fees
2
The system breaks out and identifies all taxes, separate from any
optional service charges. The CPM system provides the tax and
fee information. If taxes and fees are included in the rate, use the
3 term “included in reservation amount”.
3 Optional Service Charges
If the property assesses any additional yet optional charges, they
appear here. If there are no optional charges, do not display
anything.
4
4 Additional Confirmations
The Reservation Amount module appears the same on the
following pages:
• Reservation Confirmation Email
• Change Reservation
• View Reservation
• Cancel Reservation
It contains the same information as the Reservation summary, just
in a different layout.
Best Western International Web Release I (AR0637) E,W, W Keane Architecture Services 42
Tuesday, May 17, 2011
46. Case Study: Agile and an FDA-Compliant Company
“One can never get away from needing to provide
'objective evidence' of design inputs, verification &
validation and design outputs, this being the bare
framework of what is required by the FDA and
most, if not all the international medical device
quality requirements.”
@mojoguzzi #dtlDesign 46
Tuesday, May 17, 2011
47. “The Problem with ‘Quick and Dirty’...”
“...‘dirty’ is remembered long after
‘quick’ is forgotten.”
@mojoguzzi #dtlDesign 47
Tuesday, May 17, 2011
49. Find a way to detail your design
You can’t develop a user-centered product from
user stories
You can use personas to ask, “What would Juan
do?”
Take photos of sketches. Place them in the backlog.
Embed scenarios into the backlog for empathy
traceability
@mojoguzzi #dtlDesign 49
Tuesday, May 17, 2011
50. Culture of Your Community
@mojoguzzi #dtlDesign 50
Tuesday, May 17, 2011
51. Summary
What did we learn today?
51
Tuesday, May 17, 2011
52. “ In preparing for battle, I have always
found that plans are useless...
...but planning is indispensable. ”
—Dwight Eisenhower
@mojoguzzi #dtlDesign 52
Tuesday, May 17, 2011
53. So...
Detailed design is...
The body of information that conveys sufficient
detail to communicate that which can be coded.
Just enough detail to enable the developer
to understand the UX designer’s intent.
The codification of our empathy with users.
@mojoguzzi #dtlDesign 53
Tuesday, May 17, 2011
54. Many thanks!
Joe Sokohl
Joe@RegularJoeConsulting.com
1.804.873.6964
@mojoguzzi
@RegJoeConsults
Tuesday, May 17, 2011