Unit-3 Software Behavior

Flow

Flow is described as a state of deep focus and engagement in a task. When in flow, people feel
really involved and can be highly productive, especially when using software for activities like
engineering, design, development, or writing.

To support flow, it's important to create software interactions that are smooth and don't disrupt
the user's concentration. Here are some techniques to help with that:

• Follow mental model.

Design the software to be intuitive and match how users naturally expect it to work.
When the software aligns with their mental model, users can interact with it effortlessly.

• Enable Users to direct, don’t force them to discuss.

Provide users with control and autonomy in their interactions with the software. Instead
of forcing them into specific paths or workflows, allow them to navigate and accomplish
tasks in a way that suits their preferences and goals.

• Keep tools close at hand.

Ensure that the necessary tools and features are readily accessible within the software
interface. Users shouldn't have to search or switch between multiple screens to find what
they need. By having tools easily available, users can maintain their focus and flow
without unnecessary disruptions.

• Provide modeless feedback

Offer immediate and continuous feedback to users as they interact with the software.
This feedback can be in the form of visual cues, real-time updates, or subtle notifications.
By providing feedback that doesn't interrupt the user's workflow, they can stay immersed
in the task and maintain their flow state.

Sensible Interaction

In the context of software design and user interfaces, a sensible interaction refers to an
interaction that is logical, intuitive, and meaningful to the user. It means that the actions
and feedback provided by the software align with the user's expectations and goals,
allowing them to accomplish tasks effectively and efficiently.

A sensible interaction takes into account the user's mental model, which is their
understanding of how things should work based on their prior experiences and

Jhalnath Chapagain|GM College

 knowledge. By following the user's mental model, the software interface behaves in a
way that feels natural and familiar, making it easier for users to navigate, perform
actions, and achieve their desired outcomes.

A sensible interaction also includes clear and concise instructions, prompts, and feedback
to guide the user through the software. It provides meaningful visual cues, responses,
and updates to keep users informed about the consequences of their actions and the
status of ongoing processes.

Furthermore, a sensible interaction minimizes unnecessary steps or actions, reducing

cognitive load and streamlining the user's workflow. It avoids presenting irrelevant or
confusing options, dialog boxes, or prompts that may confuse or distract the user from
their main objective.

Example of non-sensible interaction

Changing font size: The user wants to increase the font size of a selected text.

• Non-intuitive menu location: The font size option is buried deep within
multiple menus, making it difficult to locate.

• Inconsistent terminology: The software uses non-standard or confusing

terminology for the font size option, such as "text scaling" or "character
magnification."

• Lack of visual preview: When the user attempts to change the font
size, there is no real-time preview or visual representation of how the
text will appear with the new size.
• Limited customization options: The software only offers a limited set of preset
font sizes, without the ability to input a specific size or adjust it incrementally.

Example of a sensible interaction in a photo editing software:

Suppose a user wants to rotate an image clockwise by 90 degrees. In a software with a sensible
interaction, they would typically expect the following steps:

• Select the image: The user can click on the image they want to rotate to indicate their
intention.

Jhalnath Chapagain|GM College

 • Locate the rotation option: The software provides a clearly visible and easily accessible
rotation option, such as an icon or a menu item.

• Click on the rotation option: The user clicks on the rotation option, indicating their
desire to rotate the image.

• Observe immediate feedback: As soon as the rotation option is selected, the image
begins to rotate smoothly and visually reflects the change in real-time, allowing the user
to see the effect.

• Confirm or save the changes: Once the desired rotation is achieved, the user can either
click a "Save" button to apply the rotation permanently or proceed with other editing
actions while the rotation is temporarily previewed.

Notion of MDI states

SDI

In an SDI application, each document or view is associated with its own independent window,
rather than being contained within a single parent window.

In an SDI application, when a user opens a document, it typically appears in a new window
separate from any existing documents. Each document window operates independently,
allowing users to focus on one document at a time. This design pattern is commonly used in
applications where the primary focus is on working with a single document or view.

Multiple Document Interface (MDI)

The Multiple Document Interface (MDI) is a user interface paradigm used in graphical user
interfaces (GUIs) to allow users to work with multiple documents or windows within a single
application. In an MDI environment, the application's main window acts as a container for
multiple child windows, each representing a separate document or view.

MDI is commonly used in applications such as word processors, spreadsheets, graphic design
software, or development environments, where users often work on multiple documents
simultaneously. It provides a flexible and efficient way to handle multiple documents within a
single interface, enhancing productivity and improving the overall user experience.

Multiple Document Interface can optimizes space, improves document management, facilitates
document relationships, provides a consistent interface, and simplifies window management
compared to SDI.

Jhalnath Chapagain|GM College

Task Overhead

In the context of software design, a task refers to a specific unit of work or activity that a user
performs within the software application to achieve a particular goal or complete a specific
objective. It represents a discrete action or set of actions that the user initiates and expects the
software to facilitate or support.

we can categorized the task in two types.

• Revenue Task

These are the core tasks or actions that directly contribute to achieving the primary goals
or objectives of the software application. Revenue tasks are the essential actions that
users perform to accomplish their intended purpose or desired outcomes. They are the
key functionalities or features of the software that provide value and enable users to
complete their tasks efficiently.

For example, in a word processing software, revenue tasks could include creating a new
document, editing text, formatting content, saving files, and printing. These are the
primary actions that users need to perform to fulfill their writing and document-related
needs.

• Excise Task

Excise tasks, in the context of software design, can be understood as the supporting or
ancillary tasks that are necessary but do not directly contribute to the primary objectives
or goals of the software. These tasks are often required to set up, configure, or maintain
the software, but they may not be the main focus of user interaction.

Excise tasks could involve tasks such as software installation, customization of settings,
updating preferences, managing user accounts, or performing system maintenance.
While these tasks are necessary for the software to function properly and for users to
personalize their experience, they are not directly related to the core functionality or
primary objectives of the software.

In the context of driving a car from inside a garage to the office, we can identify the
revenue tasks and excise tasks as follows:

Jhalnath Chapagain|GM College

 Revenue Tasks:
• Starting the motor: This task directly contributes to initiating the car's
movement and is essential for driving.
• Accelerating and braking: These tasks involve controlling the speed and
stopping the car when necessary, which are directly related to the act of
driving.
• Steering the vehicle: Steering the car in the desired direction is crucial for
navigating the road and reaching the office.

Excise Tasks:
• Opening and closing the garage door: While necessary for accessing the
road, opening and closing the garage door are not directly related to the act
of driving itself.
• Checking mirrors and adjusting seats: These tasks are important for safety
and comfort but do not directly contribute to the act of driving the car.
• Fastening seatbelts: While it is a safety measure, fastening seatbelts can be
considered an excise task as it is not directly involved in the act of driving
the car.
• Using turn signals: While important for indicating lane changes or turns,
using turn signals can be categorized as an excise task as it is not directly
involved in the actual driving of the vehicle.

It's important to note that the classification of revenue tasks and excise tasks can
vary depending on the specific context and interpretation. The tasks mentioned
above are based on the given scenario of driving a car from inside a garage to the
office.

Revenue Tasks Excise Tasks

Creating a new document Installing and configuring the software
Editing and formatting content Customizing user preferences and settings
Saving and retrieving data Performing software updates and maintenance
Generating reports or analytics Managing user accounts and permissions
Sending notifications or messages Performing backups or data archiving

Jhalnath Chapagain|GM College

 Eliminating Excise Task

Eliminating excise tasks is a valuable goal in software design and user experience. By
minimizing or eliminating non-essential tasks, we can enhance the efficiency,
productivity, and overall user satisfaction with the software. Here are some approaches
to consider when aiming to eliminate or reduce excise tasks:

• Simplify Installation and Setup: If software installation is identified as a significant

excise task, explore ways to streamline the process. Consider options such as
simplified installation wizards, automated configuration, or cloud-based solutions
that require minimal user intervention.

• Optimize Default Settings: Review the default settings of the software to ensure
they align with users' expectations and minimize the need for customization.

• Design Intuitive User Interfaces: Create user interfaces that are intuitive and require
minimal training or guidance. Use clear and concise language, provide visual cues,
and adopt familiar interaction patterns to reduce the learning curve and eliminate
unnecessary confusion.

• Automate Routine Maintenance: If the software requires periodic maintenance

tasks, explore opportunities for automation. Consider implementing automatic
updates, scheduled backups, or self-diagnostic features that reduce the need for
manual intervention.

• Prioritize Essential Features: Focus on the core features that directly contribute to
users' goals and minimize the inclusion of unnecessary functionalities. By prioritizing
essential features, you reduce the cognitive load on users and eliminate the need to
navigate through unnecessary options.

• Gather User Feedback: Regularly collect and analyze user feedback to identify pain
points and areas of improvement. Understand the excise tasks that users find
burdensome or unnecessary, and prioritize efforts to eliminate or optimize those
tasks based on user input.

By implementing these strategies, you can work towards eliminating or reducing excise tasks
within the software. Remember, the goal is to enhance the user experience by allowing users to
focus more on the revenue tasks that directly contribute to their objectives while minimizing the
time and effort spent on non-essential actions.

Jhalnath Chapagain|GM College

Task Coherence(coherence means logical, consistent and able to be understood)

Task coherence means designing software to match users' predictable task patterns, resulting in
a more efficient and user-friendly experience.

The concept of task coherence in software design is based on the principle that users tend to
repeat similar actions or tasks when using a program. This means that by remembering what
users did in the past, software can predict their behavior and greatly reduce the number of
questions or inputs required from the user.

When a software program has a good memory of user actions, it offers several benefits. Firstly, it
reduces excise, which refers to the unnecessary effort spent on managing the tool instead of
doing the actual work. With a program that remembers user behavior, it can automatically recall
previous settings or preferences, saving users from repetitive actions and reducing their
cognitive load.

Having a memory of user actions also helps in reducing errors. For example, when entering data
into an invoice, the software can pre-fill common information based on the user's history,
requiring less typing and lowering the chances of mistakes.

Auto-saving, Form autofill, Undo/Redo functionality, Personalized recommendations are

examples of task coherence. These examples demonstrate how task coherence is implemented
to streamline user interactions, minimize repetitive actions, and enhance the overall usability of
software applications.

Decision-set streamline

Decision-set streamlining means optimizing or simplifying the group of choices available to

users within a system or process to make decision-making more efficient and effective.

Decision-set streamlining is a concept in software design that recognizes that user choices or
decisions often occur in groups with multiple correct options. Instead of having a single
predetermined correct choice, there may be several valid possibilities to consider.

For example, consider a weather forecasting application. When presenting clothing

recommendations for the day, there may be multiple outfit choices that would be suitable based
on the weather conditions. Some users might prefer a more casual style, while others might
prefer a formal or professional look. In this case, the software can offer a set of clothing options
that are all correct for the weather, but the user's personal preferences and context would
determine which option they ultimately choose.

By incorporating decision-set streamlining principles into software design, developers aim to

create interfaces and systems that can intelligently analyze and interpret user choices. This

Jhalnath Chapagain|GM College

allows the software to provide more personalized and relevant suggestions or
recommendations, enhancing the user experience and overall satisfaction.

For example, in an e-commerce application, decision-set streamlining might be used to present

a curated selection of product recommendations based on the user's browsing history,
preferences, or similar customer profiles. Instead of a single recommendation, the software
would analyze various factors to generate a set of choices that are all valid options for the user.
The system then employs subtle clues, such as previous purchases or browsing patterns, to
determine which options are most likely to be of interest to the user.

By leveraging decision-set streamlining techniques, software can enhance its ability to adapt to
user preferences, improve decision-making processes, and ultimately deliver a more tailored and
engaging user experience.

Prefrerence Threshold

Preference threshold is a concept that helps us understand how people make decisions by
distinguishing between what's important and what's not. It's like a personal limit or boundary
that determines how much attention we give to different aspects of a decision-making process.

Imagine we're choosing a new phone.Our preference threshold might be high for certain
features like battery life or camera quality, meaning these are crucial factors for you. On the
other hand, our preference threshold might be lower for things like the color of the phone or
the brand of the charger it comes with—these details are less important to us.

Preference thresholding guides us in focusing on the key aspects of a decision, so we don't

waste time or effort on less significant factors. It helps streamline decision-making by
highlighting what truly matters to us, allowing us to make choices more efficiently.

Jhalnath Chapagain|GM College