This document provides a user interface specification for a health insurance claims management application. It outlines 57 use cases covering features like downloading claims data, reviewing claims, payments, spending analysis, and more. For each use case, it describes the primary user flow and any alternative flows. The specification also includes framework details, screen images, and information on design goals, users, and related documents.
This three-day course is designed for engineers, scientists, project managers and other professionals who design, build, test or sell complex systems. Each topic is illustrated by real-world case studies discussed by experienced CONOPS and requirements professionals. Key topics are reinforced with small-team exercises. Over 200 pages of sample CONOPS (six) and templates are provided. Students outline CONOPS and build OpCons in class. Each student gets instructor’s slides; college-level textbook; ~250 pages of case studies, templates, checklists, technical writing tips, good and bad CONOPS; Hi-Resolution personalized Certificate of CONOPS Competency and class photo, opportunity to join US/Coalition CONOPS Community of Interest.
This document provides an overview of the tasks and timeline for the PPS6 EDEN project. The project aims to develop a roadmap and action plan for Portugal's transition to a hydrogen economy. Key tasks include developing energy scenarios and a long-term vision, analyzing pathways and impacts through modeling, assessing infrastructure needs and niche markets, and synthesizing results into a roadmap and action plan. The work is divided into three phases with workshops, meetings, and deliverables scheduled throughout 2007-2008 to engage stakeholders and document findings. Quantitative modeling will analyze economic, social, and environmental impacts while qualitative work will examine challenges, opportunities, and necessary actors. The vision and roadmap development process is meant to be iterative, with modeling and analysis
PATHS Final prototype interface design v1.0pathsproject
This document summarizes the design methodology and current status of the interface design for the second prototype of the PATHS project. It begins with a three-stage design methodology that includes: evaluating the first prototype design process, creating low-fidelity storyboards, and developing high-fidelity interaction designs. It then reviews lessons learned from developing the first prototype interface. The document introduces new user interface components and presents preliminary high-fidelity designs for key pages like the landing page, path editing, and item pages. Expert evaluation of the designs is planned along with user evaluation of a working prototype. The goal is to address issues identified in prior evaluations and create an intuitive interface for the PATHS cultural heritage system.
ATI Technical CONOPS and Concepts Technical Training Course SamplerJim Jenkins
This three-day course is designed for engineers, scientists, project managers and other professionals who design, build, test or sell complex systems. Each topic is illustrated by real-world case studies discussed by experienced CONOPS and requirements professionals. Key topics are reinforced with small-team exercises. Over 200 pages of sample CONOPS (six) and templates are provided. Students outline CONOPS and build OpCons in class.
625
A P P E N D I X T W O
Computer Project
Exercises
In developing the exercises, trade-offs had to be made to enrich the learning
experience. One of the major problems students initially encounter is data and detail
overload. This reduces their ability to identify project and data problems and to
compare alternatives. Although the project found in the exercises is real, it has been
reduced and detail has been eliminated many times to concentrate on applying project
management principles and understanding linkages. In addition, other simplifying
assumptions have been made so that students and instructors can trace problems and
discuss outcomes. These assumptions detract from reality, but they keep the focus on
the objectives of the exercises and reduce student frustration with software intricacies.
Moving from these exercises to real projects is primarily one of increasing detail. The
simplifying assumptions are given below (make sure they are included in “default,”
“preferences,” and/or “options” sections of the software used):
The POM1 Project*
Big Kola Company has been concerned that specialized fruit drinks have been
eroding their cola market. The CEO mandates that “If you can’t beat them, join
them.” Grape juice was the first product that was successful after an advertising
blitz claiming the antitoxin benefits. Lately, competition is compressing grape
juice margins and profits. Months of additional market surveys and focus groups
have resulted in three potential high-margin drinks: cranberry, blueberry, and
pomegranate. All these choices represent antitoxins. The decision is to produce the
pomegranate drink that has many health claims. For example, the relative ability of
these juices to eliminate harmful free radicals (antitoxins) is 71 percent for pome-
granate, 33 percent for blueberry, and 20 percent for cranberry (Technion Institute
of Technology). The market potential appears very attractive and should have a
higher profit margin than the other potential juice products. Another appeal for
pomegranate juice is its familiarity in the Middle East and Asia.
The Priority Matrix for the POM1 Project is:
Time Scope Cost
Constrain X
Enhance X
Accept X
* Cliff Gray, Erik Larson, & Pinyarat Sirisomboonsuk, doctoral candidate at Rawls College of Business, Texas Tech University.
Lar03342_app2_625-641.indd Page 625 2/3/10 9:06:02 PM user-f498Lar03342_app2_625-641.indd Page 625 2/3/10 9:06:02 PM user-f498 /Users/user-f498/Desktop/03:02_evening/MHBR165:Larson:208/Users/user-f498/Desktop/03:02_evening/MHBR165:Larson:208
626 Appendix 2 Computer Project Exercises
Connor Gage, the project manager, has formed his project team and the members
have come up with the following work breakdown structure.
1.0 POM1Project
1.1 R&D product development
1.1.1 Need survey
1.1.2 Set product specs
1.1.3 Shelf life report
1.1.4 Nutrition report
1.2 Secure fruit suppliers
1.3 Initial Production
1..
GeneXus en Mitsubishi Heavy Industries (MHI) – JapónGeneXus
This document discusses Mitsubishi Heavy Industries' use of the Genexus application development platform. It provides background on MHI, outlines the history of Genexus usage at MHI's Yokohama Engineering Center since 2000, and describes some of the benefits of using Genexus, including easier integration with SAP systems, a common application platform, splitting up large codebases, and replacing legacy mainframe and SAP systems. Genexus has allowed MHI to more easily develop and maintain applications, leverage existing SAP investments, and transition engineers away from outdated technologies.
This document is a resume for Radu BADICEANU, a consultant with experience in SAP implementations, project management, and logistics. It lists his competencies in tools, methods, programming languages, and software packages. It also provides details of his professional experience managing SAP rollouts for TOTAL in multiple countries and implementing profitability ratios for Michelin. His education includes a master's degree and training in SAP modules.
This three-day course is designed for engineers, scientists, project managers and other professionals who design, build, test or sell complex systems. Each topic is illustrated by real-world case studies discussed by experienced CONOPS and requirements professionals. Key topics are reinforced with small-team exercises. Over 200 pages of sample CONOPS (six) and templates are provided. Students outline CONOPS and build OpCons in class. Each student gets instructor’s slides; college-level textbook; ~250 pages of case studies, templates, checklists, technical writing tips, good and bad CONOPS; Hi-Resolution personalized Certificate of CONOPS Competency and class photo, opportunity to join US/Coalition CONOPS Community of Interest.
This document provides an overview of the tasks and timeline for the PPS6 EDEN project. The project aims to develop a roadmap and action plan for Portugal's transition to a hydrogen economy. Key tasks include developing energy scenarios and a long-term vision, analyzing pathways and impacts through modeling, assessing infrastructure needs and niche markets, and synthesizing results into a roadmap and action plan. The work is divided into three phases with workshops, meetings, and deliverables scheduled throughout 2007-2008 to engage stakeholders and document findings. Quantitative modeling will analyze economic, social, and environmental impacts while qualitative work will examine challenges, opportunities, and necessary actors. The vision and roadmap development process is meant to be iterative, with modeling and analysis
PATHS Final prototype interface design v1.0pathsproject
This document summarizes the design methodology and current status of the interface design for the second prototype of the PATHS project. It begins with a three-stage design methodology that includes: evaluating the first prototype design process, creating low-fidelity storyboards, and developing high-fidelity interaction designs. It then reviews lessons learned from developing the first prototype interface. The document introduces new user interface components and presents preliminary high-fidelity designs for key pages like the landing page, path editing, and item pages. Expert evaluation of the designs is planned along with user evaluation of a working prototype. The goal is to address issues identified in prior evaluations and create an intuitive interface for the PATHS cultural heritage system.
ATI Technical CONOPS and Concepts Technical Training Course SamplerJim Jenkins
This three-day course is designed for engineers, scientists, project managers and other professionals who design, build, test or sell complex systems. Each topic is illustrated by real-world case studies discussed by experienced CONOPS and requirements professionals. Key topics are reinforced with small-team exercises. Over 200 pages of sample CONOPS (six) and templates are provided. Students outline CONOPS and build OpCons in class.
625
A P P E N D I X T W O
Computer Project
Exercises
In developing the exercises, trade-offs had to be made to enrich the learning
experience. One of the major problems students initially encounter is data and detail
overload. This reduces their ability to identify project and data problems and to
compare alternatives. Although the project found in the exercises is real, it has been
reduced and detail has been eliminated many times to concentrate on applying project
management principles and understanding linkages. In addition, other simplifying
assumptions have been made so that students and instructors can trace problems and
discuss outcomes. These assumptions detract from reality, but they keep the focus on
the objectives of the exercises and reduce student frustration with software intricacies.
Moving from these exercises to real projects is primarily one of increasing detail. The
simplifying assumptions are given below (make sure they are included in “default,”
“preferences,” and/or “options” sections of the software used):
The POM1 Project*
Big Kola Company has been concerned that specialized fruit drinks have been
eroding their cola market. The CEO mandates that “If you can’t beat them, join
them.” Grape juice was the first product that was successful after an advertising
blitz claiming the antitoxin benefits. Lately, competition is compressing grape
juice margins and profits. Months of additional market surveys and focus groups
have resulted in three potential high-margin drinks: cranberry, blueberry, and
pomegranate. All these choices represent antitoxins. The decision is to produce the
pomegranate drink that has many health claims. For example, the relative ability of
these juices to eliminate harmful free radicals (antitoxins) is 71 percent for pome-
granate, 33 percent for blueberry, and 20 percent for cranberry (Technion Institute
of Technology). The market potential appears very attractive and should have a
higher profit margin than the other potential juice products. Another appeal for
pomegranate juice is its familiarity in the Middle East and Asia.
The Priority Matrix for the POM1 Project is:
Time Scope Cost
Constrain X
Enhance X
Accept X
* Cliff Gray, Erik Larson, & Pinyarat Sirisomboonsuk, doctoral candidate at Rawls College of Business, Texas Tech University.
Lar03342_app2_625-641.indd Page 625 2/3/10 9:06:02 PM user-f498Lar03342_app2_625-641.indd Page 625 2/3/10 9:06:02 PM user-f498 /Users/user-f498/Desktop/03:02_evening/MHBR165:Larson:208/Users/user-f498/Desktop/03:02_evening/MHBR165:Larson:208
626 Appendix 2 Computer Project Exercises
Connor Gage, the project manager, has formed his project team and the members
have come up with the following work breakdown structure.
1.0 POM1Project
1.1 R&D product development
1.1.1 Need survey
1.1.2 Set product specs
1.1.3 Shelf life report
1.1.4 Nutrition report
1.2 Secure fruit suppliers
1.3 Initial Production
1..
GeneXus en Mitsubishi Heavy Industries (MHI) – JapónGeneXus
This document discusses Mitsubishi Heavy Industries' use of the Genexus application development platform. It provides background on MHI, outlines the history of Genexus usage at MHI's Yokohama Engineering Center since 2000, and describes some of the benefits of using Genexus, including easier integration with SAP systems, a common application platform, splitting up large codebases, and replacing legacy mainframe and SAP systems. Genexus has allowed MHI to more easily develop and maintain applications, leverage existing SAP investments, and transition engineers away from outdated technologies.
This document is a resume for Radu BADICEANU, a consultant with experience in SAP implementations, project management, and logistics. It lists his competencies in tools, methods, programming languages, and software packages. It also provides details of his professional experience managing SAP rollouts for TOTAL in multiple countries and implementing profitability ratios for Michelin. His education includes a master's degree and training in SAP modules.
Project management: defining the projectOscar Vadillo
This document discusses defining a project through a work breakdown structure (WBS). It outlines 5 steps to define a project: 1) defining the scope, 2) establishing priorities, 3) creating the WBS, 4) linking the WBS to organizational units, and 5) coding the WBS. The WBS breaks down the project into deliverables, work packages, and sub-packages to facilitate planning, execution, and control of the project. It also discusses how the WBS can be integrated with an organizational breakdown structure to assign responsibilities and track costs. Clear definition of a project's scope, priorities, and WBS are key factors for effective project management.
The document outlines the key aspects of a project to develop an Android application called HandSimDroid. It included sections on project overview, demonstrations, operations and processes, planning and risks. The application allows running simulations of Ptolemy models, an open-source modeling tool, on handheld devices. It aimed to serve as a proof of concept and inspire innovation at Bosch, the client. The team tracked hours, identified process improvements, and released multiple versions to complete requirements and adapt to changes.
This document discusses optimizations and updates to ELK logging in 2021. It covers the importance of logging, motivations for changes to improve logging, benefits to developers, and an overview of the multi-cluster logging architecture. Key points include faster log searches by indexing logs from different environments separately, automatic log shipping setup, cleaner log formats, and enabling log correlation and conversion to metrics. The logging flow involves Filebeat selecting logs and metadata, Logstash parsing and aggregating logs, Elasticsearch storing logs in indices, and Kibana for visualization and analysis.
This training manual provides instruction on using Bentley GEOPAK Civil Engineering Suite 2004 Edition for horizontal alignment generation and coordinate geometry. It covers accessing and using tools for storing, modifying, and manipulating alignment elements graphically or through component-based tools. Exercises guide users in creating alignments, applying superelevation, and linking alignments to profiles and cross sections.
Model-driven prototyping for corporate software specification Thomas Memmel
Model-driven prototyping is proposed as an approach to address increasing complexity in automotive human-machine interface development. Currently, development processes are predominantly paper-based and supported by heterogeneous tools. This leads to communication problems, unnecessary work, and delays. The proposed approach defines a domain-specific modeling language for automotive interfaces based on concepts identified by domain experts. Formal specifications can then be used to generate interactive prototypes early in development, allowing for rapid feedback. This standardized and model-driven process aims to improve flexibility, avoid duplicate work, and facilitate cross-discipline collaboration.
The document provides a user guide for the Forest Cover Analyzer webtool. It allows users to visually assess forest cover change in Kalimantan, Indonesia and analyze selected areas. The user interface includes tools to explore tree cover maps and additional layers, draw or upload areas of interest to analyze, and view a summary of results for the selected areas.
SOCET GXP and FME, Creating an Integrated System for Geospatial Analysis and ...Safe Software
SOCET GXP is a geospatial-intelligence (GEOINT) tool that uses imagery from commercial, satellite, and tactical means to identify and analyze ground features. SOCET GXP Version 4.0 will be integrated with FME Desktop 2011 for spatial data conversion. By integrating with FME, the SOCET GXP staff can focus on developing new tools for geospatial analysis.
This document discusses embedded systems. It defines an embedded system as a special-purpose computer system built into a larger device. The document outlines the architecture of embedded systems, including hardware components like processors and interfaces. It describes characteristics of embedded systems like being single-purpose, constrained by size/power/cost, and requiring real-time performance. The document also covers design issues for embedded systems and gives examples of applications like consumer electronics and mobile devices.
Agile-4-FSM - Improving estimates by a 4-pieces puzzleLuigi Buglione
The document discusses improving estimates in Agile projects through a four-piece puzzle approach: (1) requirements including representing both functional and non-functional requirements in user stories, (2) methods for sizing non-functional requirements such as SNAP, (3) using appropriate size measures for both functional and non-functional work, and (4) refining estimating and planning approaches to account for different types of requirements and iterations. Properly addressing all pieces of the puzzle through techniques like classifying user stories and using function point and SNAP analyses can help generate more accurate estimates for Agile projects.
The document discusses the development of two prototypes for a wireless endoscopic capsule. The first prototype had difficulties meeting requirements due to being MCU-based. A second prototype uses a more parallel approach to address these issues and allow future expansions. The developer is currently selecting components for the second prototype and working on subsystems while ensuring compatibility.
The document provides an introduction to App Designer fundamentals. It outlines the lesson objectives which are to list App Designer features, discuss relational databases and definitions, describe the integrated platform, and understand course goals. The goals of the course are also defined, which are to identify App Designer components, understand fields, records, pages, and menus, use the registration wizard, and access PIA pages.
The document provides a user guide for the Suitability Mapper web tool which enables users to identify potentially suitable sites for sustainable agriculture. The guide summarizes how to use the main features of the tool including exploring suitability maps, changing suitability criteria, and analyzing user-defined areas of interest using drawing or upload functions.
Intel 8080 8085 assembly language programming 1977 intelOmar Alkinani
The document describes what an assembler is and what it does, including translating assembly language source code into executable object code, and generating listings of the source code, object code, and symbol table. It also provides an overview of the 8080/8085 microprocessors and their memory, registers, instruction set, and addressing modes to help programmers understand the processors they are writing code for.
Soccnx III - Using Social Controls in XPagesLetsConnect
Speakers: Martin Donnelly & Tony McGuckin
There is a lot of talk about "social" these days - social applications, social business, social media, social services and so on. This session uses a definition of "social" in the context of IBM Domino XPages, custom application development and IBM Domino/IBM XWork Server. It describes new social requirements, maps them to technologies and shows how the XPages Extension Library helps you create powerful social solutions to integrate with IBM Connections and other social providers within your custom application development. People are connected more than ever, blurring the line between business and private life. For example often employees have Twitter accounts that they use to tweet both private and business messages. Many employees use their private smartphones to access business applications and data. Furthermore, information is scattered more than ever, within enterprises and in public social networks, within on premise systems and on the cloud. The corporate inbox is no longer only the mail inbox, new notifications also come in via IBM Connections, Facebook, Google+, Twitter, LinkedIn, etc! The XPages Extension Library provides utilities that make integration of Social APIs really easy, including a new storage facility for OAuth application and consumer tokens. IBM Domino XPages is on the fast track to help make your applications social. Participate in this session to see the latest contributions to the XPages Extension Library for Social Business. XPages is ready today, are you?
R&M Technologies provides reliability, maintainability and logistics support analysis services. It developed RamLog software in 1992 to manage lifecycle logistics data. RamLog includes capabilities like FMECA, RCM analysis, maintenance task analysis, technical manual authoring, and a simulation edition to model system operations and support over the lifecycle. RamLog integrates with RAMLOG.NET for transactional database support.
The document discusses key aspects of software and software engineering. It defines software as computer programs, data structures, and documentation. Software is engineered rather than manufactured. The document outlines different types of software applications and discusses characteristics that are important for web applications. It provides definitions of software engineering from seminal and IEEE sources, describing it as the systematic and disciplined development of quality software. The document presents a process framework for software engineering including core activities, umbrella activities, and considerations for adapting process models.
This document provides guidance on detailing post-tensioned structures. It discusses general principles like:
- Post-tensioning introduces anchor forces, friction forces, and deviation forces into concrete from tendons.
- Strut-and-tie models are suitable for detailed design, but an elastic analysis is not always necessary.
- After bonding, prestressed reinforcement can be treated like non-prestressed reinforcement, with its yield stress measured from the point of initial stressing.
The document outlines performance criteria such as ensuring the maximum anchorage force is at most 70% of the guaranteed ultimate tensile strength immediately after stressing, and decreases over time due to losses. It also discusses design considerations for bonded
This document provides guidance on detailing post-tensioned structures. It discusses general principles like:
- Post-tensioning introduces anchor forces, friction forces, and deviation forces into concrete from tendons.
- Strut-and-tie models are suitable for detailed design, but an elastic analysis is not always necessary.
- After bonding, prestressed reinforcement can be treated like non-prestressed reinforcement, with its yield stress measured from the point of initial stressing.
The document outlines performance criteria such as ensuring the maximum anchorage force is at most 70% of the guaranteed ultimate tensile strength immediately after stressing, and decreases over time due to losses. It also discusses design considerations for bonded
This document discusses user experience at InsideView and includes an agenda for a presentation. It defines user experience, discusses who is involved in user experience including the user experience team. It outlines the user experience goals and process, and describes the design and research activities involved such as requirements definition, wireframes, mockups, site visits, interviews and usability studies. The presentation introduces Beth Goldman as the Director of User Experience and concludes by asking for any questions.
The document discusses a user's experience navigating an unfamiliar website. The user found the navigation confusing and unclear on how to get back to previous pages. Suggestions are made to improve the usability, such as adding breadcrumbs or a site map to help orient the user. The need for better labeling of buttons and links is also noted, to avoid unexpected page changes.
Project management: defining the projectOscar Vadillo
This document discusses defining a project through a work breakdown structure (WBS). It outlines 5 steps to define a project: 1) defining the scope, 2) establishing priorities, 3) creating the WBS, 4) linking the WBS to organizational units, and 5) coding the WBS. The WBS breaks down the project into deliverables, work packages, and sub-packages to facilitate planning, execution, and control of the project. It also discusses how the WBS can be integrated with an organizational breakdown structure to assign responsibilities and track costs. Clear definition of a project's scope, priorities, and WBS are key factors for effective project management.
The document outlines the key aspects of a project to develop an Android application called HandSimDroid. It included sections on project overview, demonstrations, operations and processes, planning and risks. The application allows running simulations of Ptolemy models, an open-source modeling tool, on handheld devices. It aimed to serve as a proof of concept and inspire innovation at Bosch, the client. The team tracked hours, identified process improvements, and released multiple versions to complete requirements and adapt to changes.
This document discusses optimizations and updates to ELK logging in 2021. It covers the importance of logging, motivations for changes to improve logging, benefits to developers, and an overview of the multi-cluster logging architecture. Key points include faster log searches by indexing logs from different environments separately, automatic log shipping setup, cleaner log formats, and enabling log correlation and conversion to metrics. The logging flow involves Filebeat selecting logs and metadata, Logstash parsing and aggregating logs, Elasticsearch storing logs in indices, and Kibana for visualization and analysis.
This training manual provides instruction on using Bentley GEOPAK Civil Engineering Suite 2004 Edition for horizontal alignment generation and coordinate geometry. It covers accessing and using tools for storing, modifying, and manipulating alignment elements graphically or through component-based tools. Exercises guide users in creating alignments, applying superelevation, and linking alignments to profiles and cross sections.
Model-driven prototyping for corporate software specification Thomas Memmel
Model-driven prototyping is proposed as an approach to address increasing complexity in automotive human-machine interface development. Currently, development processes are predominantly paper-based and supported by heterogeneous tools. This leads to communication problems, unnecessary work, and delays. The proposed approach defines a domain-specific modeling language for automotive interfaces based on concepts identified by domain experts. Formal specifications can then be used to generate interactive prototypes early in development, allowing for rapid feedback. This standardized and model-driven process aims to improve flexibility, avoid duplicate work, and facilitate cross-discipline collaboration.
The document provides a user guide for the Forest Cover Analyzer webtool. It allows users to visually assess forest cover change in Kalimantan, Indonesia and analyze selected areas. The user interface includes tools to explore tree cover maps and additional layers, draw or upload areas of interest to analyze, and view a summary of results for the selected areas.
SOCET GXP and FME, Creating an Integrated System for Geospatial Analysis and ...Safe Software
SOCET GXP is a geospatial-intelligence (GEOINT) tool that uses imagery from commercial, satellite, and tactical means to identify and analyze ground features. SOCET GXP Version 4.0 will be integrated with FME Desktop 2011 for spatial data conversion. By integrating with FME, the SOCET GXP staff can focus on developing new tools for geospatial analysis.
This document discusses embedded systems. It defines an embedded system as a special-purpose computer system built into a larger device. The document outlines the architecture of embedded systems, including hardware components like processors and interfaces. It describes characteristics of embedded systems like being single-purpose, constrained by size/power/cost, and requiring real-time performance. The document also covers design issues for embedded systems and gives examples of applications like consumer electronics and mobile devices.
Agile-4-FSM - Improving estimates by a 4-pieces puzzleLuigi Buglione
The document discusses improving estimates in Agile projects through a four-piece puzzle approach: (1) requirements including representing both functional and non-functional requirements in user stories, (2) methods for sizing non-functional requirements such as SNAP, (3) using appropriate size measures for both functional and non-functional work, and (4) refining estimating and planning approaches to account for different types of requirements and iterations. Properly addressing all pieces of the puzzle through techniques like classifying user stories and using function point and SNAP analyses can help generate more accurate estimates for Agile projects.
The document discusses the development of two prototypes for a wireless endoscopic capsule. The first prototype had difficulties meeting requirements due to being MCU-based. A second prototype uses a more parallel approach to address these issues and allow future expansions. The developer is currently selecting components for the second prototype and working on subsystems while ensuring compatibility.
The document provides an introduction to App Designer fundamentals. It outlines the lesson objectives which are to list App Designer features, discuss relational databases and definitions, describe the integrated platform, and understand course goals. The goals of the course are also defined, which are to identify App Designer components, understand fields, records, pages, and menus, use the registration wizard, and access PIA pages.
The document provides a user guide for the Suitability Mapper web tool which enables users to identify potentially suitable sites for sustainable agriculture. The guide summarizes how to use the main features of the tool including exploring suitability maps, changing suitability criteria, and analyzing user-defined areas of interest using drawing or upload functions.
Intel 8080 8085 assembly language programming 1977 intelOmar Alkinani
The document describes what an assembler is and what it does, including translating assembly language source code into executable object code, and generating listings of the source code, object code, and symbol table. It also provides an overview of the 8080/8085 microprocessors and their memory, registers, instruction set, and addressing modes to help programmers understand the processors they are writing code for.
Soccnx III - Using Social Controls in XPagesLetsConnect
Speakers: Martin Donnelly & Tony McGuckin
There is a lot of talk about "social" these days - social applications, social business, social media, social services and so on. This session uses a definition of "social" in the context of IBM Domino XPages, custom application development and IBM Domino/IBM XWork Server. It describes new social requirements, maps them to technologies and shows how the XPages Extension Library helps you create powerful social solutions to integrate with IBM Connections and other social providers within your custom application development. People are connected more than ever, blurring the line between business and private life. For example often employees have Twitter accounts that they use to tweet both private and business messages. Many employees use their private smartphones to access business applications and data. Furthermore, information is scattered more than ever, within enterprises and in public social networks, within on premise systems and on the cloud. The corporate inbox is no longer only the mail inbox, new notifications also come in via IBM Connections, Facebook, Google+, Twitter, LinkedIn, etc! The XPages Extension Library provides utilities that make integration of Social APIs really easy, including a new storage facility for OAuth application and consumer tokens. IBM Domino XPages is on the fast track to help make your applications social. Participate in this session to see the latest contributions to the XPages Extension Library for Social Business. XPages is ready today, are you?
R&M Technologies provides reliability, maintainability and logistics support analysis services. It developed RamLog software in 1992 to manage lifecycle logistics data. RamLog includes capabilities like FMECA, RCM analysis, maintenance task analysis, technical manual authoring, and a simulation edition to model system operations and support over the lifecycle. RamLog integrates with RAMLOG.NET for transactional database support.
The document discusses key aspects of software and software engineering. It defines software as computer programs, data structures, and documentation. Software is engineered rather than manufactured. The document outlines different types of software applications and discusses characteristics that are important for web applications. It provides definitions of software engineering from seminal and IEEE sources, describing it as the systematic and disciplined development of quality software. The document presents a process framework for software engineering including core activities, umbrella activities, and considerations for adapting process models.
This document provides guidance on detailing post-tensioned structures. It discusses general principles like:
- Post-tensioning introduces anchor forces, friction forces, and deviation forces into concrete from tendons.
- Strut-and-tie models are suitable for detailed design, but an elastic analysis is not always necessary.
- After bonding, prestressed reinforcement can be treated like non-prestressed reinforcement, with its yield stress measured from the point of initial stressing.
The document outlines performance criteria such as ensuring the maximum anchorage force is at most 70% of the guaranteed ultimate tensile strength immediately after stressing, and decreases over time due to losses. It also discusses design considerations for bonded
This document provides guidance on detailing post-tensioned structures. It discusses general principles like:
- Post-tensioning introduces anchor forces, friction forces, and deviation forces into concrete from tendons.
- Strut-and-tie models are suitable for detailed design, but an elastic analysis is not always necessary.
- After bonding, prestressed reinforcement can be treated like non-prestressed reinforcement, with its yield stress measured from the point of initial stressing.
The document outlines performance criteria such as ensuring the maximum anchorage force is at most 70% of the guaranteed ultimate tensile strength immediately after stressing, and decreases over time due to losses. It also discusses design considerations for bonded
This document discusses user experience at InsideView and includes an agenda for a presentation. It defines user experience, discusses who is involved in user experience including the user experience team. It outlines the user experience goals and process, and describes the design and research activities involved such as requirements definition, wireframes, mockups, site visits, interviews and usability studies. The presentation introduces Beth Goldman as the Director of User Experience and concludes by asking for any questions.
The document discusses a user's experience navigating an unfamiliar website. The user found the navigation confusing and unclear on how to get back to previous pages. Suggestions are made to improve the usability, such as adding breadcrumbs or a site map to help orient the user. The need for better labeling of buttons and links is also noted, to avoid unexpected page changes.
The document outlines different use cases for saving, viewing, and modifying reports in a system. It describes starting from a new or existing report and going through the report wizard to format it. It also covers a user saving a report, performing analysis on it without saving, and modifying and saving an existing report. The system will then add the saved or modified report to the reports menu and jobs list.
The document describes different report, chart, and options types for trend analysis. It lists report types like single series, split series, and multiple series analysis that can be displayed as line, area, column, or table charts. It also describes distribution reports that can be shown as bar, pie, or table charts. Additional options include handling null values, time range binning, stacking modes, and scaling.
John Smith, a marketing analyst, is asked to create a report of total product downloads by product ID in the past week for his manager. He searches Splunk for events of type "downloads" within the last week time range and sees the needed productID field. He is also asked to create a line chart showing average throughput by input type for every 5 minutes in the last hour, labeling the y-axis as "Average throughput".
The document describes a software application for creating and managing reports. It includes sections for searching data, building charts and graphs from result sets, applying filters, and formatting report output. The application allows customizing reports through selection of data fields, aggregation functions, chart types, and other parameters. Reports can be saved, shared on dashboards, and exported from the application.
This document provides instructions for creating a report from search results in three steps:
1. Selecting a report type (trend over time with split fields).
2. Mapping fields to axes and categories (cookies to the y-axis, file to the secondary/split by field, over time on the x-axis).
3. Formatting the results as a stacked column chart showing the distinct count of cookies over time split by file.
The summary outlines the key steps taken to generate a split field trend over time report visualizing the count of distinct cookies grouped and trended by file over the specified time range.
This document contains a summary of system monitoring data from a Splunk installation, including statistics on forwarders, indexers, searches, and a detailed view of configuration and activity for a specific host. Key metrics shown include top forwarders and indexers by throughput, longest and most frequent searches, and CPU/memory usage over time for the selected host. The host details view contains in-depth information on applications, open ports, running processes, configuration files, tickets, and recent changes for the localhost.
The document contains UI messages for various common situations including errors, notifications, and server status updates. Examples include messages for when search returns no results, login errors occur, changes are saved, the server is restarting, and license violations exist. It also includes messages for form errors, deleting objects, and unsaved changes when navigating away from a form.
The document appears to be a user interface for viewing and managing reports. It includes a list of existing reports with details like name, frequency of execution, date ranges, and number of instances. It also provides options to view report details, edit or delete reports/instances, and run reports. There are instructions on how to create a new report by running a search and selecting the "report on results" option.
1) The document outlines the use cases for creating, publishing, and reviewing reports.
2) The key steps for creating a report include finding data, mapping fields to axes, formatting charts and labels, and finalizing the report content.
3) Publishing a report involves identifying reviewers, scheduling delivery, and saving templates.
4) Reviewing a report consists of opening the report, analyzing the data, and providing feedback to improve the report if needed.
The document discusses use case development, including the objectives, value, and process of developing use cases. It provides guidance on reviewing existing use cases, the key elements of use cases including name, description, actors, flows, and exceptions. The document uses examples to illustrate use case anatomy and best practices for writing use cases.
The document outlines a site navigation and user experience optimization project that included:
1) Collecting and summarizing usability and concept testing data from May to August 2007 and 2008.
2) Reviewing design specifications and concepts by various teams from May to August 2008.
3) Developing the site navigation from August 2008 to January 2009 based on usability testing results.
4) Conducting a heuristic review and refining concepts from July to September 2008.
This document outlines requirements and concepts for improving the Y! Travel user experience in Wave 5. It identifies key insights such as travelers wanting recommendations tailored to their interests, guidance in deciding destinations, and the ability to easily share and plan recurring trips. The proposed site map and concepts focus on helping users explore destinations, research places, and plan trips with more flexibility. Milestones include developing new regional pages, navigation models, and page templates by December, followed by user testing.
This document outlines a travel UE optimization project timeline from November 2007 to January 2008. It involves several tasks including navigation model, destination finder, guides, and deals front pages concept design and prototyping. It also includes trip planner collections, my travel community enhancements, object tagging, deals optimization content merge, events and guides integration, and page templates integration projects. Key milestones are concept reviews, internal design reviews, and design details.
The document discusses the design process and issues for an iteration of a medical bill tracking product called Husky. Key issues discussed include:
- Setup being too long and complicated due to security requirements
- Whether the product's framework and navigation metaphor fit how users think about the tasks
- Ensuring users understand the difference between claims and bills, and who they need to pay
- Concerns that claim details contain too much information and are overwhelming for users
- Ensuring users know the appropriate next steps after reviewing their claims
- Clarifying the product's payment capabilities for users
The document outlines changes already made to address issues and plans for further user testing and improvements in the next iteration.
The document summarizes several research studies on online travel behavior conducted between 2005-2006. Key findings include:
- People want to plan trips collaboratively but have security concerns about sharing details. They share memories mostly with close friends/family.
- Travelers use the internet for research but also value reviews from friends. Younger travelers are more engaged in online communities.
- Sharing photos and memories online is emotional rather than informational for most. Effort for contributing is low.
- Market segments include passionate travelers, inspired planners, and those seeking a one-stop-shop for travel arrangements.
1. USER INTERFACE SPECIFICATION
Designers: Beth Goldman Lead Designer, Feature Teams 2&3
Matt Homier Lead Designer, Feature Teams 1&4
Seonghee Park Designer, Feature Teams 1, 3, & 4
Document History
Version Author(s) Date Section Comments
1.9 – Matt Homier 08/29/06 Added I1 & I2 UI text Also ujpdated several issues based on input Ready for
DRAFT Lyda Woods revisions feature team review
1.8 – Matt Homier 08/28/06 ADDED missing printed Also ujpdated several issues based on input Ready for
DRAFT Seongee Park reports and uninstall feature team review
1.7 – Matt Homier 08/28/06 Added – UC I3 deliverable. For feature team review
DRAFT Seongee Park 14,15,16,32,34,54,55,58
,64, 65
1.6 – Beth Goldman 08/24/06 Added – UC60: Find & For feature team review.
DRAFT FT2 areas for UC33: Updates to UC13: Payments and UC63: Record HP
Print Reimbursement based on not having data about who
Updated – UC9, 10, & 49 insurance paid will be made next week.
1.5 – Beth Goldman 08/16/06 FT 1& 2 I 1&2 Use cases Updated based on team feedback.
DRAFT
1.4 – Matt Homier Framework, UC 4,5,6,53 Updated missing sections, updated issues, and design
DRAFT changes based on FT1&4 input
1.3 - Beth Goldman 08/14/2006 I – 1 & 2 Designs for FT Updated document based on initial feedback from feature
DRAFT Seonghee Park 2 & 3 Use Cases teams 2 & 3.
Added required help links/topics and flyoversb
FT 1 & 4 updates pending
Text is still not final.
1.2 - Beth Goldman 08/08/2006 Updated Iteration 1 Original version for review by feature teams. Includes
DRAFT Matt Homier Designs designs for all Iteration 1 & 2 Use Cases.
Seonghee Park Added all Iteration 2 Text is still not final.
Designs
1.1 - Matt Homier 7/27/2006 Framework, UC 4, UC 5, Text is still not final.
DRAFT UC 53
1.0 - Beth Goldman 06/13/2006 All Iteration 1 Designs Original version for review by feature teams. Includes
DRAFT Matt Homier designs for all Iteration 1 Use Cases.
Seonghee Park
User Interface Specification |Husky: Version 1.0 Intuit Confidential
2. TABLE OF CONTENTS
USER INTERFACE SPECIFICATION 1
TABLE OF CONTENTS 2
UI FEATURES – DESCRIPTION TABLES 1
UI FEATURES – SCREEN IMAGES 4
OVERVIEW 8
ABOUT THIS DOCUMENT 8
DESIGN GOALS 8
VOICE & STYLE 8
NAMING UI ELEMENTS 8
USERS & OUTCOMES 9
RELATED DOCUMENTS 10
UI FRAMEWORK (I1) 11
OVERVIEW 11
FRAMWORK FLOW DIAGRAM 12
FRAMEWORK ZONING 13
COMPONENT ELEMENTS 18
HELP FRAMEWORK 28
TYPOGRAPHY 33
COLORS 34
Co-branding within Quicken Health 35
Accessibility 35
UC1: GET PRODUCT (I1) 42
OVERVIEW 42
UC2: GET PRODUCT DOWNLOAD (I1) 43
OVERVIEW 43
UC3: INSTALL (I1) 44
OVERVIEW 44
ALT FLOW: User’s system doesn’t meet requirements 53
ALT FLOW: User has ultra slow connection 54
UC4: FIRST USE / SETUP (I1) 56
OVERVIEW 56
PRIMARY FLOW 57
UC5: CONFIGURE SETTINGS (I1) 60
OVERVIEW 60
PRIMARY FLOW 61
ALT FLOW 5.1: User clicks side tab with required fields empty. 78
UC6: PATCH (I2) 79
OVERVIEW 79
INTEGRATION POINTS WITH eDELIVERY 80
UC7: DOWNLOAD DATA (I1) 81
OVERVIEW 81
PRIMARY FLOW 83
ALT FLOW 7.1: Authentication Data not Stored or Incorrect 87
ALT FLOW 7.2: No New Claims Data 87
ALT FLOW 7.3: User has multiple Quicken-Certified Health Plans 87
ALT FLOW 7.4: First Download 88
ALT FLOW 7.7: Download includes a change to Plan Design and/or Eligibility 88
ALT FLOW 7.8: User Rejects Plan Design and/or Eligibility Info 89
ALT FLOW 7.9: System Downloads Possible Matching Member 89
EXCEPTION 7.0.E.1: Unable to connect 90
User Interface Specification |Husky: Version 1.0 Intuit Confidential
3. EXCEPTION 7.0.E.2: Claim contains flawed data (from the source) 90
EXCEPTION 7.0.E.3: Unable to Login 90
EXCEPTION 7.0.E.4: Plan detail & Eligibility info is incorrect or missing 90
UC8: PLAN DETAILS ELIGIBILITY (I1) 91
OVERVIEW 91
PRIMARY FLOW 92
ALT FLOW 8.1: User does not find info he wanted 95
ALT FLOW 8.2: User disagrees with info presented 96
ALT FLOW 8.3: Plan Details for Straddling Years 96
EXCEPTION 8.0.E.1: Plan Detail & Eligibility info is incorrect or missing 96
UC 9: REVIEW MEDICAL CLAIMS (I1) 97
OVERVIEW 97
PRIMARY FLOW 99
ALT FLOW 9.1: Reject bill & claim because amounts due don’t match 113
ALT FLOW 9.2: Reject bill & claim because there is a mistake on bill or claim 114
ALT FLOW 9.3: Reject bill & claim because claim was denied or not fully paid 114
ALT FLOW 9.4: Reject bill & claim because user doesn’t understand why they owe what they owe 114
ALT FLOW 9.6: User does not have paper bill yet. 114
ALT FLOW 9.6: User does not have paper bill yet. Claim says balance due. 115
ALT FLOW 9.8: Reimbursement from Health Plan with no paper EOB. 115
OVERVIEW 116
PRIMARY FLOW 118
ALT FLOW 10.1: Follow-up needed 145
ALT FLOW 10.2: Contact by Letter or Email. 145
ALT FLOW 10.3: Contact Someone Else 145
ALT FLOW 10.4: Formal Appeal or Legal Action 146
UC11: NOTIFICATIONS (I1) 148
OVERVIEW 148
PRIMARY FLOW 149
ALT FLOW 11.1: Balance due but user decides to pay without reviewing claim 153
ALT FLOW 11.2: Balance due, user decides to wait 153
ALT FLOW 11.3: No balance due, user decides to review anyway 153
ALT FLOW 11.4: No balance due, user does not review claim 153
ALT FLOW 11.5: User unable to open application now 154
EXCEPTION FLOW 11.0.E.1: User doesn’t receive notification due to a reason the system can’t recognize (bounce) 154
EXCEPTION FLOW 11.0.E.2: User doesn’t receive notification due to a reason the system cannot recognize (email client not
working, notification filtered into spam mailbox) 154
EXCEPTION FLOW 11.0.E.3: Email was never sent 154
EXCEPTION FLOW 11.0.E.4: Email sent to wrong address 155
EXCEPTION FLOW 11.0.E.5: Email illegible due to wrong format 155
EXCEPTION FLOW 11.0.E.6: Contents of email are incorrect or blank. 155
EXCEPTION FLOW 11.0.E.7: User attempts to open application from link, but it is not installed on this computer. 156
EXCEPTION FLOW 11.0.E.8: User attempts to open application from link, but it is already open for a different household.
NEW 156
EXCEPTION FLOW 11.0.E.9: User attempts to open application from link, but system cannot find household. NEW 156
UC12: PORTABILITY (I2) 157
OVERVIEW 157
PRIMARY FLOW 158
UC13: PAYMENTS (I2) 161
OVERVIEW 161
PRIMARY FLOW 162
ALT FLOW 13.1: Billed for Copay (before claim arrives) 167
ALT FLOW 13.2: Billed for Copay (after claim arrives) 167
ALT FLOW 13.3: Pay Copay and Deductible/Coinsurance at time of Service 167
ALT FLOW 13.4: Owe deductible or coinsurance after time of service 168
User Interface Specification |Husky: Version 1.0 Intuit Confidential
4. ALT FLOW 13.5: Negotiate amount due 168
ALT FLOW 13.6: Amount is partially paid 170
UC14: ACCOUNTS PAYABLE 171
OVERVIEW 171
ALT FLOW 14.1: User wants to know how much they owe a provider 175
UC15: ACCOUNTS RECEIVABLE 176
OVERVIEW 176
PRIMARY FLOW 177
ALT FLOW 15.1: User wants to know how much they are owed by a provider or health plan, presumably so they can obtain
reimbursement (UC10 Disputes) 178
ALT FLOW 15.2: User wants to know how much they are owed by a health plan, presumably so they can obtain
reimbursement (UC10 Disputes) 178
UC16: SPENDING ANALYSIS (I3) 179
OVERVIEW 179
PRIMARY FLOW 180
ALT FLOW 16.1: User wants to know how much they have spent on their medical expenses for a given area 184
ALT FLOW 16.2: User wants to know how much they have spent on their medical prescriptions for a given area 187
UC17: SHOW DEDUCTIBLE PROGRESS (I2) 188
OVERVIEW 188
PRIMARY FLOW 189
ALT FLOW 17.1: User is dissatisfied with Deductible/OOP Max progress 192
EXCEPTION FLOW 17.0.E.1: Deductible/OOP max accumulator is not available 192
UC18: PHR-LIKE REPORT (I3+) 193
OVERVIEW 193
UC19: LEARN THE PRODUCT (I2) 194
OVERVIEW 194
PRIMARY FLOW 195
UC32: BACK-UP & RESTORE FILE (I3) 198
OVERVIEW 198
PRIMARY FLOW 199
UC33: PRINT (I3) 203
OVERVIEW 203
PRIMARY FLOW 204
UC36: REQUEST QUICKEN CERTIFICATION (In Product) (I2) 225
OVERVIEW 225
PRIMARY FLOW 226
ALT FLOW 36.1: Want to learn more about Quicken Certification 229
ALT FLOW 36.2: In Setup Workflow, Can’t Find Data Provider 230
UC37: EOB OPT-OUT (I2) 231
OVERVIEW 231
PROCESS FLOW 232
UC45: SET UP REMINDERS (on hold) 234
OVERVIEW 234
UC46: GET REMINDERS (on hold) 235
OVERVIEW 235
UC47: ADJUSTED CLAIMS (I2) 236
OVERVIEW 236
PRIMARY FLOW 237
ALT FLOW 47.1: Health plan does adjustments as two transactions. System can match replacement claim to original claim.
241
ALT FLOW 47.2: Adjustment to an adjustment. 241
EXCEPTION FLOW 47.0.E.1 Replacement not matched. 241
UC49: REVIEW PHARMACY CLAIMS (I1) 243
User Interface Specification |Husky: Version 1.0 Intuit Confidential
5. OVERVIEW 243
PRIMARY FLOW 244
ALT FLOW 49.1: Pharmacy claim needs to be filed (unusual) 246
ALT FLOW 49.2: Pharmacy claim filed but rejected (unusual) 246
ALT FLOW 49.3: User wants to questions something about the claim 247
UC50: REGISTER (I1) 248
OVERVIEW 248
PRIMARY FLOW 249
ALT FLOW 50.1: Don’t Register Twice 252
ALT FLOW 50.2: Already Registered 252
ALT FLOW 50.3: Change Registration Data 252
UC51: LOGIN (I1) 253
OVERVIEW 253
PRIMARY FLOW 254
ALT FLOW: Logout and log back in 257
ALT FLOW: User switches household directly 257
UC52: RECOVER PASSWORD (I2) 259
OVERVIEW 259
FEATURE TEAM 259
OUTSTANDING ISSUES 259
PRIMARY FLOW 260
ALT FLOW 52.1: User can’t remember security answer 266
ALT FLOW 52.2: User miss-enters the answer 10 times 266
ALT FLOW 52.3: User can’t click the link in the email 266
UC53: CREATE NEW HOUSEHOLD (I1) 267
OVERVIEW 267
ALT FLOW: User has more than one login for a health plan 278
ALT FLOW: User skips entering insurance id & password 279
ALT FLOW: User not connected to the internet 279
ALT FLOW: Unable to create household account because of server returns error 280
UC54: COPY MEMBER (I3) 281
OVERVIEW 281
PRIMARY FLOW 282
UC55: DELETE MEMBER (I3) 285
OVERVIEW 285
PRIMARY FLOW 286
UC56: SUNSET (I3+) 288
OVERVIEW 288
UC57: COORDINATION OF BENEFITS (I2&I3) 289
OVERVIEW 289
ALT FLOW 57.2: Quicken Certified Plan is Primary, Non-Quicken Certified Plan is Secondary 290
UC58: UNINSTALL (I3) 292
OVERVIEW 292
UC59: RECORD PROVIDER REIMBURSEMENT (I2) 295
OVERVIEW 295
PRIMARY FLOW 296
ALT FLOW 59.1: Record and use provider credit 299
ALT FLOW 59.2: Assign credit to a provider (Q) 301
ALT FLOW 59.3: Record provider partial reimbursement. 301
UC60: FIND CLAIMS (I3) 302
OVERVIEW 302
PRIMARY FLOW 303
ALT FLOW 60.1 User does not initially find the claim; repeats find process 307
ALT FLOW 60.2 Bill corresponds to multiple claims 307
User Interface Specification |Husky: Version 1.0 Intuit Confidential
6. ALT FLOW 60.3 Bill reflects a correction 307
ALT FLOW 60.4 Find without bill (“More like this…”) 307
ALT FLOW 60.5 Find corresponding claims when system cannot match Adjustment (UC-47 Adjusted Claims scenario 47.0.E.1
and 47.0.E.2) or Coordination of Benefits (UC-57 COB scenario 57.6.E.1) 307
ALT FLOW 60.6 Repeat Find 308
ALT FLOW 60.7 Find in order to confirm payment 308
EXCEPTION 60.0.E.1 User can’t find recent claim because it hasn’t been downloaded yet. 308
EXCEPTION 60.0.E.2 User can’t find a recent claim because it hasn’t been downloaded yet, and user has turned off auto-
download. 308
EXCEPTION 60.0.E.3 User can’t find a claim because it doesn’t exist in the system or he has entered invalid search criteria
308
UC63: RECORD HEALTH PLAN REIMBURSEMENT 309
OVERVIEW 309
PRIMARY FLOW 310
UC64: TAX DEDUCTION REPORT 314
OVERVIEW 314
PRIMARY FLOW 315
ALT FLOW 64.1: User needs to indicate that some expenses are not tax-deductible 319
UC65: FSA/HAS Payments Report 321
OVERVIEW 321
PRIMARY FLOW 322
ALT FLOW 65.1: User wants to share a record of what they have indicated are their FSA/HSA-applied payments, e.g. with
their FSA/HSA administrator 325
UI ASSETS (REQUIRED IMAGES) 326
User Interface Specification |Husky: Version 1.0 Intuit Confidential
7. UI FEATURES – DESCRIPTION TABLES
Table 1: Top Menu Items.......................................................................................................................13
Table 2: Tab states for content navigation...........................................................................................17
Table 3: Frameword - Alert Dialogs.......................................................................................................21
Table 4: Common Error Windows..........................................................................................................22
Table 5: Tool Dialog Elements...............................................................................................................23
Table 6: Setup Window Details..............................................................................................................24
Table 7: Email........................................................................................................................................27
Table 8: Updated UI Text for Figure 21: Various Help Panes...............................................................31
Table 9: Color Usage.............................................................................................................................34
Table 10: Keyboard Shortcuts for Main screen.....................................................................................36
Table 11: Claims Details Keyboard Controls........................................................................................38
Table 12: Keyboard Shortcuts for Insurance Plan Details....................................................................39
Table 13: Keyboard Shortcuts for Preference Dialogs.........................................................................40
Table 14: Keyboard Shortcuts for User Login.......................................................................................41
Table 15: Update UI Text for Figure 29: Install - Welcome Screen......................................................46
Table 16: Updated UI Text for Figure 30: Install - Accept EULA..........................................................47
Table 17: Updated UI Text for Figure 31: Install - Select Destination Folder......................................48
Table 18: Updated UI Text for Figure 32: Install Download Component..............................................49
Table 19: Updated UI Text for Figure 33: Install - Install Files.............................................................50
Table 20: Updated UI Text for Figure 34: Installer - Ready to Restart.................................................51
Table 21: Updated UI Text for Figure 35: Installer - Congrats Screen.................................................52
Table 22: Updated UI Text for Figure 36: Installer - Requirements Error.............................................53
Table 23: Updated UI Text for Figure 37: Install - Connection too slow..............................................54
Table 24: Updated UI Text for Figure 38: Install - No Connection Error...............................................55
Table 25: Setup - Welcome Screen.......................................................................................................58
Table 26: Updated UI Text for Figure 39: Setup -Welcome Screen......................................................58
Table 27: Configure Settings – Household Component List..................................................................65
Table 28: Update UI Text for Figure 40: Configure Settings - Household.............................................65
Table 29: Preferences - Configure Settings- Change Household Password Component List...............66
Table 30: Configure Setting - Download Component List.....................................................................68
Table 31: Updated UI Text for Figure 43: Preferences - Configure Settings- Download......................69
Table 32: Change Insurance Web Site ID & Password Component List ..............................................70
Table 33: Updated UI Text for Figure 44: Preferences - Change Insurance Web Site ID & Password.70
Table 34: Updated UI Text for Figure 45: Preferences - Add New Insurance Web Site ID & Password
71
Table 35: Configure Settings – Contact Email Component List............................................................72
Table 36: Updated UI Text for Figure 46: Configure Settings - Contact Email.....................................73
Table 37: Configure Setting – Product Update Component List...........................................................77
Table 38: Updated UI Text for Figure 47: Configure Settings – Product Update – Option 1.................77
Table 39: Updated UI Text for Options 2, 3, & 4 - Figure 48, Figure 49, Figure 50...............................78
Table 40: Updated UI Text for Figure 51 and Figure 52........................................................................84
Table 41: Download Status Toolbar Area..............................................................................................86
Table 42: Updated UI Text for Figure 55: Claim Details – Showing Access Points to Health Plan
Details 93
Table 43: Insurance Plan Details Window.............................................................................................94
User Interface Specification |Husky: Version 1.0 Intuit Confidential
8. Table 44: Unpaid Insurance Claims List.............................................................................................100
Table 45: Updated UI Text for Figure 57: Unpaid Insurance Claims List...........................................102
Table 46: In Dispute Insurance Claims List........................................................................................103
Table 47: Updated UI Text for Figure 58: In Dispute Insurance Claims List......................................104
Table 48: Paid Insurance Claims List..................................................................................................105
Table 49: Updated UI Text for Figure 59: Paid Insurance Claims List...............................................106
Table 50: Insurance Claims Details....................................................................................................108
Table 51: Updated UI Text for Figure 64: Claim Details – Next Steps Assistance.............................119
Table 52: Claim Details - Next Steps Assistance................................................................................120
Table 53: Problem/Issue topic display rules.......................................................................................125
Table 54 Updated UI Text for Problem/Issue topic display...............................................................125
Table 55: Next Steps Topic Advice.....................................................................................................140
Table 56 Updated UI Text for NS Topic Advice and Step Contents...................................................140
Table 57: Email Notification................................................................................................................151
Table 58: Updated UI Text for Figure 71: Email Notification..............................................................152
Table 59: Email claim to yourself pop-up............................................................................................160
Table 60 Payment Dialog Elements....................................................................................................163
Table 61: Balance Report Details........................................................................................................173
Table 62: Expense Analysis Report Details........................................................................................182
Table 63: Expense Comparison Report Details...................................................................................186
Table 64: Insurance Plan Details Window - benefits/deductibles.......................................................190
Table 65: Updated UI Text forFigure 83: Insurance Plan Details – with deductibles details.............191
Table 66: Claims List Print Layout......................................................................................................205
Table 67: Claims Details Print Layout.................................................................................................209
Table 68: Balance Report Details........................................................................................................214
Table 69: Expense Analysis Details....................................................................................................216
Table 70: Expense Comparison Details...............................................................................................219
Table 71: Expense Deductible Report Details.....................................................................................222
Table 72: FSA/HSA Payment Report Details ......................................................................................224
Table 73: Updated UI Text for Figure 102: Request Quicken Certification Window 1.......................227
Table 74: Request Quicken Certification Component List..................................................................228
Table 75: Opt-Out of Paper EOB Link..................................................................................................233
Table 76: Adjusted claim details window...........................................................................................240
Table 77: Pharmacy Claim Details......................................................................................................245
Table 78: Registration Reminder Component List..............................................................................250
Table 79: Registration Form Component List.....................................................................................251
Table 80: Login Screen Zoning............................................................................................................255
Table 81: Login Screen Elements........................................................................................................255
Table 82: Login Screen - Top Menu.....................................................................................................256
Table 83: Forgot password, step 2......................................................................................................261
Table 84: Forgot Password, step 2......................................................................................................262
Table 85: Password reset email..........................................................................................................264
Table 86: Password reset dialog.........................................................................................................265
Table 87: Setup - Household Information Detials...............................................................................269
Table 88: Updated UI Text for Figure 120: Setup - Household Information........................................270
Table 89: Setup - Password & Security Question...............................................................................270
User Interface Specification |Husky: Version 1.0 Intuit Confidential
9. Table 90: Updated UI Text for Figure 121: Setup - Password & Security Question...........................271
Table 91: Setup – Insurance IDs & Passwords....................................................................................273
Table 92: Updated UI Text for Figure 123: Setup - Insurance IDs & Passwords................................274
Table 93: Setup - First download.........................................................................................................277
Table 94: Multiple Insurance IDs.........................................................................................................278
Table 95: Updated UI Text for Figure 125: Setup - Multiple Insurance IDs........................................278
Table 96: Manage Family Member Data Dialog...................................................................................283
Table 97: Copy Member - Select destination household dialog..........................................................284
Table 98: Find Claims..........................................................................................................................304
Table 99: Deductible Expense Details................................................................................................316
Table 100: Select Family Members Dialog details..............................................................................318
Table 101: FSA/HSA Payments details................................................................................................323
User Interface Specification |Husky: Version 1.0 Intuit Confidential
10. UI FEATURES – SCREEN IMAGES
Figure 1: Zones of the Framework........................................................................................................13
Figure 2: Tab states for content navigation..........................................................................................17
Figure 3: Button States.........................................................................................................................18
Figure 4: Top Menu Example.................................................................................................................18
Figure 5: Framework - Example Actionable List - Claims list..............................................................19
Figure 6: Framework - Example Informational List...............................................................................19
Figure 7: Drag & Drop............................................................................................................................20
Figure 8: Framework - Alert dialogs......................................................................................................21
Figure 9: Tool Dialog.............................................................................................................................22
Figure 10: Setup Window.......................................................................................................................24
Figure 11 - Framework - About Quicken for Healthcare Dialog............................................................25
Figure 12: Ghosted Text........................................................................................................................26
Figure 13: Framework Form Element - Input Validation.......................................................................26
Figure 14: Framework Form Element – Auto-fill Input..........................................................................26
Figure 15: Email.....................................................................................................................................27
Figure 16: Tooltip..................................................................................................................................28
Figure 17: Contextual help link, inline..................................................................................................29
Figure 18: Contextual help link, sideline...............................................................................................29
Figure 19: Help topic pop-up – DRAFT...................................................................................................30
Figure 20: Dialog Help Icon...................................................................................................................30
Figure 21: Various Help Panes..............................................................................................................31
Figure 22: Colors...................................................................................................................................34
Figure 23: Using Health Plan Logos in Husky.......................................................................................35
Figure 24: Keyboard Shortcuts for Main screen...................................................................................36
Figure 25: Claims Details Keyboard Controls.......................................................................................38
Figure 26: Keyboard Shortcuts for Insurance Plan Details...................................................................39
Figure 27: Keyboard Shortcuts for Preferences dialog.........................................................................40
Figure 28: Keyboard Shortcuts for User Login......................................................................................41
Figure 29: Install - Welcome Screen.....................................................................................................46
Figure 30: Install - Accept EULA...........................................................................................................47
Figure 31: Install - Select Destination Folder.......................................................................................48
Figure 32: Install Download Component...............................................................................................49
Figure 33: Install - Install Files..............................................................................................................50
Figure 34: Installer - Ready to Restart..................................................................................................51
Figure 35: Installer - Congrats Screen..................................................................................................52
Figure 36: Installer - Requirements Error..............................................................................................53
Figure 37: Install - Connection too slow...............................................................................................54
Figure 38: Install - No Connection Error................................................................................................55
Figure 39: Setup -Welcome Screen.......................................................................................................58
Figure 40: Configure Settings - Household............................................................................................64
Figure 41: Preferences - Configure Settings- Change Household Password Window 1.......................66
Figure 42: Preferences - Configure Settings- Change Household Password Window 2.......................66
Figure 43: Preferences - Configure Settings- Download ......................................................................68
Figure 44: Preferences - Change Insurance Web Site ID & Password..................................................70
Figure 45: Preferences - Add New Insurance Web Site ID & Password...............................................70
User Interface Specification |Husky: Version 1.0 Intuit Confidential
11. Figure 46: Configure Settings - Contact Email......................................................................................72
Figure 47: Configure Settings – Product Update – Option 1..................................................................74
Figure 48 - Configure Settings – Product Updates - Option 2...............................................................75
Figure 49: Configure Settings – Product Updates - Option 3................................................................76
Figure 50: Configure Settings – Product Updates - Option 4................................................................77
Figure 51: Main Application Screen with Menu & Toolbar....................................................................84
Figure 52: Download Status Toolbar Area - Authentication Progress..................................................85
Figure 53: Download Status Toolbar Area - Download Progress..........................................................86
Figure 54: Download Status Toolbar Area– Download Summary..........................................................87
Figure 55: Claim Details – Showing Access Points to Health Plan Details...........................................93
Figure 56: Insurance Plan Details.........................................................................................................94
Figure 57: Unpaid Insurance Claims List............................................................................................100
Figure 58: In Dispute Insurance Claims List.......................................................................................103
Figure 59: Paid Insurance Claims List.................................................................................................105
Figure 60: Insurance Claim Details.....................................................................................................108
Figure 61: Claim Details with Insurance Payment breakout for service............................................112
Figure 62: Claim Details - Out of Network Provider............................................................................112
Figure 63: Claim Details - Notes Expanded.........................................................................................113
Figure 64: Claim Details – Next Steps Assistance..............................................................................119
Figure 65: 1: Next Steps Assistance Navigation – step 1 expanded; 2: step 2 expanded to show topic
groups; 3: issue groups expanded to display issue topics.................................................................120
Figure 66: Next Steps - Understand why... Topic Content..................................................................141
Figure 67: Next Steps - Problem/Issue Topic Content........................................................................142
Figure 68: Next Steps - Pending Provider Reimbursement.................................................................143
Figure 69: : Next Steps - Pending Provider Reimbursement Received...............................................143
Figure 70: Email Notification in Inbox.................................................................................................150
Figure 71: Email Notification...............................................................................................................151
Figure 72: Claim Details - access to email claim................................................................................159
Figure 73: Email claim to yourself pop-up...........................................................................................160
Figure 74 Payment Dialog Window .....................................................................................................163
Figure 75 Payment in-line error message for the required field ........................................................166
Figure 76 Negotiated Amount Window 1(left), 2(right).......................................................................169
Figure 77: Balance Report...................................................................................................................173
Figure 78: Spending Analysis - Expense Analysis Report 1................................................................181
Figure 79: Spending Analysis - Expense Analysis Report 2................................................................182
Figure 80: Spending Analysis - Expense Comparison Report 1..........................................................185
Figure 81: Spending Analysis - Expense Comparison Report 2..........................................................185
Figure 82: Spending Analysis - Expense Comparison Report in Summary.........................................186
Figure 83: Insurance Plan Details – with deductibles details.............................................................190
Figure 84: Getting Started Tutorial Window.......................................................................................196
Figure 85: Restore Household - Enter password.................................................................................201
Figure 86: Claims List Print Layout.....................................................................................................205
Figure 87: Insurance Claim – print options.........................................................................................206
Figure 88: Claims Details Print Layout – All info – 1 of 2....................................................................207
Figure 89: Claims Details Print Layout – All info – 2 of 2....................................................................208
Figure 90: Claims Details Print Layout – Insurance Info only.............................................................209
Figure 91: Health Plan Details – selected family member only..........................................................211
User Interface Specification |Husky: Version 1.0 Intuit Confidential
13. Figure 139: Deductible Expenses........................................................................................................316
Figure 140: Select Family Members Dialog.........................................................................................318
Figure 141: Deductible Expenses with Tax-deductible only unchecked............................................319
Figure 142: FSA/HSA Payments...........................................................................................................323
User Interface Specification |Husky: Version 1.0 Intuit Confidential
14. OVERVIEW
ABOUT THIS DOCUMENT
This document describes the user experience for Quicken Health Version 1 (Husky). This document does not include:
» Designs for iteration 2 & 3 use cases. These will be added later.
» The final, complete visual design. Current treatment is at 90%.
DESIGN GOALS
» Be the destination for knowing what to do next with my medical expenses
» Become a trusted source that eases the anxiety and worry over dealing with medical expenses
» Allow users to ignore what doesn’t matter
» Can’t emphasize SIMPLE enough
» Information should be clear, understandable, and in plain English
» Motivate use by immediately and clearly demonstrating benefits.
» Clearly communicate what the system does and what it doesn’t do.
VOICE & STYLE
Voice
• Writing in the first person, using the pronoun “I” is useful in writing plain English questions we predict
consumers having.
• Writing in the second person, using the pronoun “You” is useful in writing embedded help prompts in the voice
of the application.
• Avoid using the pronoun “We” because the consumer will be confused. Is it her insurance carrier talking to her
or Quicken for Healthcare?
Style
Text will be developed and revised in accordance with UA Style Guides, with certain exceptions.
Exception 1: internet and website
The UI will treat “internet” and “website” as regular nouns instead of proper nouns for the following reasons:
• No company enforces trademark protection of either “internet” or “website,” in fact, quite the opposite. One of
the early internet developers, Robert Kahn, points out that the internet's creators have gone to court to make
sure that the word “internet” remains in the public domain. Kahn told the New York Times in 2003: "We
defended the right of people to use the word whether you use a cap I or little i."
• Trends in publication are moving toward treating these terms as regular nouns
• This decision aligns with similar conventions in modern day language usage for inventions in the public domain:
we listen to radio programs, not Radio programs, and watch television, not Television.
• Most importantly, reducing capitalization increases readability, according to generally-accepted design principles
NAMING UI ELEMENTS
Apply these principles when naming UI Elements:
1. What do health plans call a particular concept or thing and why, and more importantly, are consumers familiar
with the term(s)? Is this term routinely used in conversations between members and insurers, or members and
providers? Do usability trials confirm that a portion of users are familiar with the term and have presupposed
its meaning?
User Interface Specification |Husky: Version 1.0 Intuit Confidential | 8
15. 2. Avoid naming something using a term already employed in the healthcare industry if the meaning is not the
same.
3. If there are multiple healthcare terms for one element, such as “Amount Billed” which is also called: "Amount
submitted by the provider," then consider the healthcare term that is easiest to comprehend before creating an
entirely new name that has no resonance with consumers or healthcare providers.
If it is necessary to come up with a new term for a UI element because the healthcare term(s) are
unclear or misleading, then find one that has meaning in plain English similar to its healthcare intent,
and doesn’t violate the other principles stated here.
USERS & OUTCOMES
We are designing this system for our target user types – people with employee-sponsored PPO health plans. The focus is
on Engaged Esther and Tracking Thomas, but we are expecting to attract Uneasy Una as well. More details about the
User Types can be found in Husky User Types.doc. A summary of the user types and their desired outcomes from the
MRD appears below:
User Types Relative Market Size (among 27MM PPO users):
• Engaged Esther 21%
• Tracking Thomas 14%
• Uneasy Una 29% (but assuming not all are prospective customers)
Numbers on outcomes indicate priorities based on judgment since we have not surveyed this. Unnumbered, grayed-out
outcomes are tangentially related but not being addressed by this product.
Jobs Tracking Thomas (& Uneasy Una) Engaged Esther
Primary Jobs
1. Make sure expenses I 1. Min time spent working on healthcare expenses
owe are correct 2. Min paying for erroneous charges
3. Min overpayment
3. Make sure my claims 6. Min healthcare expenses I’m responsible for
are reimbursed 7. Min likelihood of being taken advantage of by others or the system
8. Inc likelihood of being reimbursed by FSA/HSA
4. Ensure my insurance Inc likelihood provider is paid fairly
pays provider correctly Min time to get reimbursed
Min likelihood of being reported to credit agency
5. Get help understanding Inc sense of safety, comfort, peace of mind
costs, bills, and EOBs 4. Inc likelihood of detecting errors in bills & claims
5. Inc likelihood of getting reimbursed by third party
9. Inc likelihood of taking tax deduction
10. Inc sense of accomplishment for knowing the system
2. Resolve billing and 1. Min time spent to dispute
insurance disputes 2. Min healthcare expenses I’m responsible for
3. Min paying for erroneous charges
5. Min likelihood of being taken advantage of by others or the system
Min likelihood of being reported to credit agency
4. Inc likelihood of winning a dispute
6. Inc sense of accomplishment for knowing the system
Secondary Jobs
6. Reduce the amount I Min healthcare expenses I’m responsible for
have to spend Min overpayment
Inc likelihood of taking tax deduction
7. Determine if costs are Min healthcare expenses I’m responsible for
reasonable Min paying for erroneous charges
Min likelihood of being taken advantage of
Inc likelihood of detecting errors in bills & claims
8. Negotiate prices with Min healthcare expenses I’m responsible for
out-of-network providers Inc likelihood of winning a dispute
(in case of disputes) Inc sense of accomplishment for knowing the system
User Interface Specification |Husky: Version 1.0 Intuit Confidential | 9
16. RELATED DOCUMENTS
» MRD – document on Quickbase
User Interface Specification |Husky: Version 1.0 Intuit Confidential | 10
17. UI FRAMEWORK (I1)
OVERVIEW
» This section describes the user experience for the UI framework and overall navigation.
Feature Team
FEATURE TEAM Role Name
UE Lead Matt Homier
UE Designer Seonghee Park
Outstanding Issues
Issue Description Status
Framework will be affected by the following Iteration 2/3 use cases: In progress
» Reports like
» UC14: ACCOUNTS PAYABLE (I3)
» UC16: SPENDING ANALYSIS (I3)
» UC15: ACCOUNTS RECEIVABLE (I3)
» UC17: SHOW DEDUCTIBLE PROGRESS (I2)
» UC18: PHR-LIKE REPORT (I3)
» UC33: PRINT (I3)
Quicken Health’s Branding will need to be add once it is developed. Not Started
Framework design will be affected by upcoming accessibility requirements. In Progress
All text is placeholder, pending contribution of UA and review by Marketing and Legal. Final text In Progress
will be provided in another document.
Open question about using Insurance company and household names in the menus due to length. Wait to see
real data in
this situation
We don’t really have a dedicated feature team for this part like we do for all the others. Closed
FT4 is handling this
Emails Closed
» Linking from an Email directly has yet to be proven, although it looks like it may
work
» Need to add guidance about how users can dismiss the Open/Save dialog for good
» What happens when they have text only email?
» Popup windows will have the explorer logo. Is this acceptable? Closed
» Yes
» Blue underlined links may not be readable in setup screens. Closed
» Network errors messages need to be identified and crafted In Progress
Rollovers will not possible at this moment because of the way the list Open
is coded (using frames)
User Interface Specification |Husky: Version 1.0 Intuit Confidential | 11
19. FRAMEWORK ZONING
The main framework is divided into multiple zones. The layout is optimized for 1024x768 and supports 800x600. The
minimum size is 800x600. The default size is 1024x768.
1
2
3
4
4a 4b
Figure 1: Zones of the Framework
Zone 1: Menu Bar
Table 1: Top Menu Items
Item Name Type Behavior Keyboard
Top Menu
General Behavior » The menu bar performs like any application menu bar.
File Top menu » For all functions related to file TBD
management
Create New Household… Menu Item » Activates Create New Household flow in
UC 53
Switch to Sub Menu » Opens a submenu listing the current
households for this item.
» Selecting any of these items opens a
dialog box for logging in as depicted in UC
51
Manage Family Member Menu » Opens the Copy/Delete Member dialog
described in UC54: COPY MEMBER (I3)
and UC55: DELETE MEMBER (I3)
User Interface Specification |Husky: Version 1.0 Intuit Confidential | 13
20. Item Name Type Behavior Keyboard
Logout of <NAME> Menu Item » <NAME> is the current name of currently
Household open household file
» Selecting this item logs the user out and
sends them to the main login screen as
depicted in UC 51
MENU DIVIDER Divider »
Backup to File… Menu Item » As described in UC 32
Restore Backup… Menu Item » As described in UC 32
MENU DIVIDER Divider »
Print Menu Item » Placeholder if needed pending UC 33
MENU DIVIDER Divider »
Exit Menu Item » Quits the application.
Edit Top Menu » For all manipulation actions
Undo Menu Item » Backs out of any change of status on a CTRL Z
claim
» Disabled if no change of status was made
MENU DIVIDER Divider »
Cut Menu Item » Copies highlighted text to the clipboard CTRL X
and removes it
» Disabled if no text selected
Copy Menu Item » Copies highlighted text to the clipboard CTRL C
» Disabled if no text selected
Paste Menu Item » Pastes clipboard text into selected text CTRL V
field
» Disabled if no text field selected or
clipboard empty
MENU DIVIDER Divider »
Preferences… Menu Item » Opens up the Preferences dialog box as
depicted in UC 5
Change Household Menu Item » Brings up the change password sequence
Password… as depicted in UC 5
Edit Download Logins… Menu Item » Brings up the Preferences dialog with the
tab set to Download tab depicted in UC 5
Claims Top Menu » Central access for all claim based
functions
Unpaid Claims Menu item » Navigates users to the Claims tab/Unpaid
In Dispute Claims Menu item » Navigates users to the Claims
tab/Indispute
Paid Claims Menu Item » Navigates users to the Claims tab/Paid
Find Claims Menu Item » Navigates users to the Claims tab/ Find
claoms
MENU DIVIDER Divider »
Sort Claims by Sub menu » Only active if the claims list is present
» List each sortable column in the list,
selecting one changes the sort to it.
» Selecting the same sort that is active
reverses the sort
MENU DIVIDER Divider »
View Claim Details Menu Item » Opens the claim details of the currently
selected claims
» Not active if no claim is selected
User Interface Specification |Husky: Version 1.0 Intuit Confidential | 14
21. Item Name Type Behavior Keyboard
Mark Claim as Paid Menu Item » Moves currently selected item to the paid
tab
» Not active if no claim is selected.
Mark Claim as In Menu Item » Moves currently selected claims to the in
Dispute dispute tab
» Not active if no claim is selected
Mark Claim as Unpaid Menu Item » Moves currently selected claims to the
unpaid tab
» Not active if no claim is selected
Reports Top menu » This is a central access point for all pop up
tools in the application
Balance Report Menu Item » Brings up the Balance Report as depicted
in UC14: ACCOUNTS PAYABLE and UC15:
ACCOUNTS RECEIVABLE
Expense Analysis Menu Item » Brings up the Expense Analysis as
Report depicted in UC16: SPENDING ANALYSIS
(I3)
Expense Comarison Menu Item » Brings up the Expense Comparison as
Report depicted in UC16: SPENDING ANALYSIS
(I3)
Tax deductible Report Menu Item » Brings up the Tax deductible Report as
depicted in UC64: TAX DEDUCTION
REPORT
FSA/HSA Report Menu Item » Brings up the FSA/HSA Report as depicted
in UC65: FSA/HAS Payments Report
Tools Top menu » This is a central access point for all pop up
tools in the application
Insurance Details… Menu Item » Brings up the Insurance Details tool as
depicted in UC 8
MENU DIVIDER Divider »
Download Claim Data » Initiates a download sequence as depicted
in UC 7
Help » This is the central access for all help and
related tools
Contact <Insurance> Menu » Opens the Insurance details of the listed
Item(s) insurance
» One item for every insurance in the
system
» <Insurance> is replaced with the
Insurance name
MENU DIVIDER Divider »
Quicken Health Online Menu Item » Opens up an external browser to the
Support SPECS site
Quicken Health Online Menu Item » Opens up an external browser to the
User Forums LITHIUM site
Give Us Feedback Menu Item » Opens up an external browser to the
SPECS site
MENU DIVIDER Divider »
Getting Started Menu Item » Opens up the Getting Started tutorial as
described in UC19: LEARN THE PRODUCT
(I2)
Tutorials Menu Item » Opens up an external browser to tutorials
on the SPECS site
MENU DIVIDER Divider »
User Interface Specification |Husky: Version 1.0 Intuit Confidential | 15
22. Item Name Type Behavior Keyboard
Quicken Health Privacy Menu Item » Opens up an external browser to the
Statement SPECS site
Change Marketing Menu Item » Opens and external browser to Intuits
Settings contact policy site
MENU DIVIDER Divider »
Check for Updates Menu Item » Launches eDelivery’s check for updates
MENU DIVIDER Divider »
Request Other Insurance Menu Item » Opens up an external browser to a form
Provide Download users can request their other health plans
allow downloads as depicted in UC 36
Register Now Menu Item » Only appears if the user has not registered
the product
» Opens up the register interface as
depicted in UC 50
About Quicken for » Brings up the About screen
Healthcare
Zone 2: Toolbar
Item Name Type Behavior Keyboard
General Behavior » The toolbar area is for features that are not big enough for there own content
area but are stand alone tools. They usually have a global use within the product
» These tools open up in a modal dialog box
Insurance Details Toolbar Icon » Brings up the Insurance Details tool as
depicted in UC 8
» Left aligned
Help Toolbar Icon » Opens up an external browser to the SPECs
web site
» Right Aligned, separated from other tools by
a vertical divider
Download Feature space » Shows progress of a current download or the
Progress state of the last download.
» Depicted in UC 7
Zone 3: Content Tabs
FUNCTIONALITY MOVED TO ZONE 4a
Zone 4: Content Area
The content area is the main works space in husky. It is divided into 3 sub-zones.
In Husky v1, the top area is titled by “Insurance Claims” in Tahoma Bold, 16pt. black.
Sub-zone 4a: Content navigation
Within a content section, the left area is reserved for navigation within the content area. It is optional area. The top half
of this zone is used for main sections within the feature. The lower half is reserved for tools and reports contextual to the
feature.
User Interface Specification |Husky: Version 1.0 Intuit Confidential | 16
23. 1
5
3
4
2
Figure 2: Tab states for content navigation
Table 2: Tab states for content navigation
Figure Type Behavior
Figure Main Tab -Selected State » Folder icon open
2.1 » Text color is Deep Blue
» Background is visible
Figure 2 Main Tab – Normal State » Folder icon closed
.2 » Text color is White
» Background is not visible
» Tahoma Bold, 14px
Figure 2 Sub Tab – Selected State » Background image is visible
.3 » Tahoma Bold, 11px
Figure 2 Sub Tab – Normal State » Background image is not visible
.4 » Tahoma Normal, 11px
Not Sub Tab – Rollover State » Background image is not visible
Shown » Tahoma Bold, 11px
Figure 2 New indicator » Lists the number of new claims there are in
.5 each tab.
» Not shown if there are no new items
» Tahoma, 14px Black
Content navigation has a fixed width and is the full height of the Content area.
Sub-zone 4b: Content display
This is the main workspace within the content feature. This zone expands both vertically and horizontally to take up the
available space.
Sub-zone 4c: Help and Task pane
The help and task pane is an optional zone on the right side of any content pane. It is used to display contextual help and
task panes from the main area. This area is defined in the Help Framework section of this document.
The help and task pane has a fixed width and is the full height of the Content area.
This zone is not used in the main view of Husky V1, but is there for Claims Details.
User Interface Specification |Husky: Version 1.0 Intuit Confidential | 17
24. COMPONENT ELEMENTS
Buttons
Figure 3: Button States
NOTE: Buttons will no longer be bold.
Menus
Figure 4: Top Menu Example
User Interface Specification |Husky: Version 1.0 Intuit Confidential | 18
25. Lists / Datagrids
Figure 5: Framework - Example Actionable List - Claims list
Figure 6: Framework - Example Informational List
There are 2 types of datagrids used in Husky. An actionable list and and informational list.
Item Type Description
Actionable Lists
General behavior
» First item in the list is selected by default
» May or may not be sortable. Lists that are sorted have an
affordance indicating which way the sort is going
Selected row Datagrid row » #FFFFCC
User Interface Specification |Husky: Version 1.0 Intuit Confidential | 19
26. Item Type Description
Action buttons Buttons » Appear at the bottom of the list
» Right aligned are the primary actions
» Other action are left aligned
» Note that the make payments dialog is an
acception, the buttons yielded its position to
the totals.
» If the button acts upon the line item, but no
rows are selected, the user is presented with
an error alert message:
» Title: No <ITEM NAME>s selected.
» Text: You must select an item from the list
above.
Right click menu Menu » Actionalble lists may have there actions
appear in this way
Drag & Drop Grid action » See below
Informational List
General Behavior » May or may not have hightlighting rows
» Not sortable
Selected row Datagrid row » #FFFFCC
» Deselects when a user clicks on a different
area
Drag & Drop
Figure 7: Drag & Drop
User Interface Specification |Husky: Version 1.0 Intuit Confidential | 20