SMI University

Assignment
Dec 18, 2024

Name | Muhammad Hassan mansoor

ID | BSE-23S-220
Department of software engineering
Section | SE4D
Subject | Software design and architecture
Question No 1: Why It Is Important to Offer Keyboard Shortcuts for
Equivalent Mouse Actions?
Offering keyboard shortcuts as an alternative to mouse actions is important for several reasons:

1. Accessibility
 Keyboard shortcuts enable individuals with motor disabilities or conditions that make
mouse usage difficult (e.g., arthritis, tremors, or repetitive strain injuries) to navigate and
use software effectively.
 They comply with accessibility standards like the Web Content Accessibility Guidelines
(WCAG), which promote inclusivity.

2. Efficiency
 Keyboard shortcuts are often faster than navigating menus with a mouse, allowing users
to perform tasks with fewer steps and reduced effort.
 Professionals who work extensively with software (e.g., programmers, designers, and
writers) benefit from the speed boost provided by keyboard shortcuts.

3. Ergonomics
 Frequent switching between the mouse and keyboard can interrupt workflow and
contribute to strain over time. Keyboard shortcuts reduce unnecessary movements,
supporting ergonomic efficiency.

4. Catering to Power Users

 Advanced users often prefer shortcuts for their speed and ease of use. Providing shortcuts
can improve user satisfaction and retention among this group.

5. Continuity in Workflow
 For tasks that involve extensive typing, using the mouse disrupts the flow. Keyboard
shortcuts keep users focused by eliminating the need to switch input devices.

6. Multi-tasking and Screen Real Estate

 Shortcuts are essential in scenarios with limited screen space or when multi-tasking with
multiple windows. They allow users to access functions without crowding their display
with menus or tools.

By integrating keyboard shortcuts alongside mouse actions, developers create a more user-
friendly, accessible, and efficient experience for a diverse range of users.
Question No 2: How Would You Present the Current Load on the System
Over Time?

Presenting the current load on a system over time requires a clear, concise, and actionable
approach, typically using visualizations that highlight trends and patterns. Below are some
effective ways to present this information:

1. Line Chart
 Best For: Continuous monitoring of system load (e.g., CPU, memory, disk I/O) over
time.
 Why: A line chart displays trends clearly, showing peaks, valleys, and averages over
time.
 Features to Include:
o X-Axis: Time (e.g., hours, minutes, or days).
o Y-Axis: System load metric (e.g., CPU usage percentage, memory usage in GB,
etc.).
o Use different colored lines for multiple metrics or systems.

2. Stacked Area Chart

 Best For: Visualizing cumulative load across multiple components (e.g., multi-core CPU
loads).
 Why: It shows the combined load while also breaking it down by contributors.
 Features to Include:
o Segments for individual cores, processes, or services.
o Dynamic scaling to reflect real-time or historical loads.

3. Heat map
 Best For: Identifying load patterns over longer periods (e.g., days, weeks).
 Why: Highlights times of high or low load intensity using color gradients.
 Features to Include:
o X-Axis: Time of day.
o Y-Axis: Date or system component.
o Color scale to represent load levels.
4. Gauge or Dial
 Best For: Real-time snapshots of the system load.
 Why: Provides an intuitive view of the system's current state.
 Features to Include:
o Threshold indicators (e.g., green for normal, yellow for warning, red for critical).
o Labels for specific load levels.

5. Bar Chart
 Best For: Comparing discrete time intervals or system components.
 Why: Useful for summarizing average or peak loads across specific periods or systems.
 Features to Include:
o Grouped bars for comparing metrics over intervals (e.g., hourly load).

6. Dashboard with Multiple Widgets

 Best For: Comprehensive monitoring of diverse metrics.
 Why: Combines various visualization types (line charts, heat maps, gauges) for a holistic
view.
 Features to Include:
o Interactive filters (e.g., by time range or system).
o Alerts for thresholds exceeded.

7. Interactive Timeline
 Best For: Drilling down into specific periods or components.
 Why: Allows users to zoom in/out and view granular or aggregated data.
 Features to Include:
o Pan-and-zoom capabilities.
o Overlay of events (e.g., deployments or incidents) for context.

Key Considerations:
 Real-Time Updates: Ensure the visualization updates in real-time if needed.
 Threshold Indicators: Clearly mark thresholds for warning and critical levels.
 Annotations: Allow users to mark or annotate significant events.
 Responsiveness: Ensure the presentation adapts to various screen sizes and devices.
Question No 3: What is the worst UI you have ever used, what design
principles did it violate?
The worst UI experiences are often memorable because they violate fundamental design
principles that make interfaces usable, accessible, and enjoyable. While I don’t personally use
interfaces, I can provide examples of commonly cited “worst UI” types and analyze the design
principles they violate.

Example of a Bad UI: Overly Complex Control Panels

Imagine an old-fashioned microwave interface with:

 Over 50 buttons, most of which have cryptic abbreviations.

 No clear hierarchy or grouping of controls.
 Lack of feedback (no light or sound to confirm actions).
 Poor labeling (e.g., "DEF" for "Defrost" but no explanation).

Design Principles Violated

1. Simplicity:
o The interface overwhelms users with too many options and no prioritization of
primary functions. This violates the principle of making the most common tasks
easy to perform.
2. Clarity:
o Cryptic abbreviations and unclear labels make the interface confusing. Users
should not need a manual to understand basic functionality.
3. Consistency:
o Buttons and features may follow inconsistent patterns, such as mixing text labels
with icons or using non-standard terminology.
4. Feedback:
o The interface lacks feedback to confirm that an action has been taken (e.g.,
pressing "Start" doesn’t give an audible or visual signal).
5. Accessibility:
o Tiny buttons and poorly contrasting labels make the interface hard to use for
individuals with vision impairments or dexterity issues.
6. Affordance:
o Controls do not clearly indicate how they should be used. For example, it might
not be apparent which buttons are essential for basic cooking versus advanced
settings.
7. Learnability:
o Users are forced to guess or repeatedly refer to a manual because the system does
not guide them intuitively.
Why Such UIs Persist
 Legacy Constraints: Older systems often prioritize functionality over usability.
 Poor User Testing: Insufficient testing with real users leads to designs that only make
sense to engineers or designers.
 Feature Creep: Adding too many features without regard for usability overwhelms the
interface.

What Could Fix It?

1. Prioritize Core Functions:
o Emphasize frequently used buttons (e.g., "Start," "Stop," "Time") and hide or
simplify less common features.
2. Use Clear Labels:
o Replace cryptic abbreviations with full, meaningful terms or icons supported by
tooltips.
3. Group Related Controls:
o Organize buttons into logical sections (e.g., cooking modes, timer controls).
4. Provide Feedback:
o Add audible or visual signals for key actions.
5. Ensure Accessibility:
o Use larger, tactile buttons and high-contrast labels to improve usability for all
users.
Question No 4: What is the worst website you used recently, how would you
fix it?
Bad websites often leave a lasting impression because of how frustrating they are. While I don't
personally browse websites, I can describe common examples of poor websites and how they can
be improved. Let’s break this down with a common scenario:

Example: A Poorly Designed E-commerce Website

 The website is cluttered with ads and pop-ups.

 The navigation is confusing, with no clear categories for products.
 The search bar doesn’t return relevant results.
 The checkout process is unnecessarily long, requiring multiple steps and redundant
information.

Key Issues and Fixes

1. Cluttered Interface
o Problem: Too many ads, banners, and irrelevant distractions obscure the primary
purpose of the site.
o Fix: Simplify the layout by prioritizing the content that matters (e.g., featured
products or promotions). Use white space effectively to reduce visual noise.
2. Confusing Navigation
o Problem: Menus are buried under multiple layers, or categories overlap (e.g.,
“Shoes” and “Footwear” as separate categories).
o Fix: Implement a clear and consistent navigation bar with well-defined
categories. Add breadcrumbs so users can easily track their location.
3. Ineffective Search Functionality
o Problem: Searches return irrelevant or incomplete results because of poor
filtering and indexing.
o Fix: Improve the search algorithm to support keyword matching, synonyms, and
typo correction. Provide filters for refining search results (e.g., by price, size, or
brand).
4. Slow Loading Times
o Problem: Images, scripts, or poorly optimized code make the site sluggish.
o Fix: Optimize images, enable caching, and minimize heavy scripts. Use tools like
Google Lighthouse to diagnose and resolve performance issues.
5. Annoying Pop-ups
o Problem: Pop-ups appear too frequently, asking for sign-ups, feedback, or
promotions before the user engages with the site.
o Fix: Reduce pop-up frequency and use them strategically (e.g., exit-intent pop-
ups). Allow users to dismiss pop-ups easily without blocking content.
6. Lengthy Checkout Process
o Problem: The checkout process requires unnecessary information or too many
clicks, leading to cart abandonment.
o Fix: Streamline the process by:
 Enabling guest checkouts.
 Pre-filling fields for returning users.
 Reducing steps to a single-page or condensed flow.
 Displaying a progress indicator for multi-step processes.
7. Poor Mobile Optimization
o Problem: The site doesn’t scale properly on mobile devices, making it hard to
navigate.
o Fix: Ensure the site is responsive and optimized for touch interactions. Test
across devices and screen sizes.
8. Inadequate Error Handling
o Problem: Users encounter vague error messages like “Something went wrong”
with no further guidance.
o Fix: Provide clear, actionable error messages (e.g., “Your payment method was
declined. Please try a different card or contact support.”).

Propose Redesign Strategy

1. User-Centered Design:
o Conduct usability testing to understand user needs and pain points.
o Use analytics to identify problem areas (e.g., pages with high bounce rates or
abandoned carts).
2. Visual Hierarchy:
o Use consistent fonts, colors, and button styles to guide user focus.
o Highlight calls to action (e.g., “Buy Now” or “Add to Cart”).
3. Iterative Improvements:
o Start with the most critical fixes (e.g., navigation and checkout flow).
o Gather user feedback post-launch and iterate.
4. Accessibility:
o Ensure compliance with WCAG standards for color contrast, screen reader
support, and keyboard navigation.

Question No 5: What is good or bad with MS Word help system?

Strengths of the MS Word Help System:

1. Integrated Search Functionality:
o Allows users to search directly within the application for assistance with specific
tasks.
o Results often include step-by-step guides, videos, and hyperlinks for related
topics.
2. Contextual Help:
o Tooltips appear when hovering over menu items, providing brief explanations.
o Some features offer "Tell Me What You Want to Do," where users type a
question, and Word directs them to the relevant functionality.
3. Online Help and Community Resources:
o Links to extensive online documentation, forums, and tutorials from Microsoft
Support.
o Includes access to community-based answers for common issues.
4. Accessibility Features:
o Support for screen readers and an intuitive design make the help system more
accessible to users with disabilities.
5. Visual Aids and Examples:
o Interactive guides, illustrations, and animations demonstrate how to use features
effectively.
6. Automatic Updates:
o Content updates dynamically when the software is online, ensuring users receive
the latest information.

Weaknesses of the MS Word Help System:

1. Overwhelming Information:
o The sheer volume of options and information can confuse users, particularly
beginners.
o Search results often include unrelated or advanced topics, making it hard to find
precise answers.
2. Dependence on Internet Connection:
o Offline users face limitations as much of the help content and resources are
online.
3. Limited Customization:
o The help system does not always adapt well to individual user needs or provide
tailored guidance.
4. Inconsistent Depth of Information:
o Some topics are covered in exhaustive detail, while others lack sufficient
explanations.
o Troubleshooting guides can sometimes be generic and fail to address specific
issues.
5. Search Limitations:
o The built-in search tool sometimes struggles to interpret natural language queries,
requiring users to phrase questions precisely.
6. Less Emphasis on Advanced Features:
o While basic features are well-documented, advanced or less commonly used tools
may not be explained thoroughly.

Suggestions for Improvement:

 Improve natural language processing in the search tool to better understand user queries.
 Provide a more structured, tiered approach to help content (basic, intermediate, and
advanced).
 Enhance offline help capabilities for users without reliable internet access.
 Offer personalized learning paths or tutorials based on the user’s skill level and history of
queries.

Overall, Microsoft Word's help system is powerful and resourceful but could benefit from better
organization and a more user-focused approach.