WGU D779 SJN1 – Task 2
EasyBank Usability Testing Plan, UML Design, Wireframes & Interactive
Prototype
Course: Software Product Design and Requirement Engineering
Institution: Western Governors University
Resource edition: 2026/2027
Research verification
For Task 2, we need to change scenarios. Task 1 uses CityLink, while the publicly available Task 2 scenario
identifies EasyBank, a web-based banking application being developed by TechWave Solutions.
The EasyBank scenario establishes that:
• The application serves small and medium-sized financial institutions.
• Its features include account management, fund transfers, bill payments, transaction history, and customer
support.
• Users have reported navigation difficulties, contributing to increased support inquiries.
• The identified users include retail customers, business customers, and customer support representatives.
• The design must account for accessibility, responsive layouts, security, and financial regulatory obligations.
Independent D779 student accounts corroborate that Task 2 involves usability testing, wireframes, UML
diagrams, and an interactive prototype. Some reported using Figma or PowerPoint.
Verification limitation: These sources establish the likely assessment structure, but the complete October 2026
WGU Task 2 rubric remains unavailable. The resource below is an original comprehensive worked example, not a
verified reproduction of the scoring instructions.
Interactive EasyBank prototype
The accompanying prototype has been created and browser-tested. It includes working navigation and simulated
banking workflows using fictional account data.
WGU D779 • EasyBank Task 2 Page 1 of 35
,The prototype demonstrates account balances, transfers, bill payments, transaction history, and support. It does
not process real financial transactions or implement production banking security.
PART A: EASYBANK SOFTWARE PRODUCT DESIGN
Usability Testing Plan, Requirements Analysis, Wireframes, UML Modeling, and
Prototype Design
Course: D779 – Software Product Design and Requirement Engineering
Assessment: SJN1 – Task 2
Institution: Western Governors University
Project: EasyBank Web-Based Banking Application
Organization: TechWave Solutions
Version: 1.0 | October 2026
Document Status: Original scenario-based design and usability resource
1. Executive Summary
TechWave Solutions is developing EasyBank, a web-based banking application intended to provide accessible,
secure, and convenient financial services to customers of small and medium-sized financial institutions. The
application supports core banking activities, including account management, fund transfers, bill payments,
transaction history, and customer support.
Although EasyBank is approaching the later stages of development, preliminary feedback indicates that some
users experience difficulties navigating the interface. These difficulties have contributed to increased customer
support inquiries, suggesting a gap between the available functionality and users' ability to discover and
complete essential banking activities efficiently.
WGU D779 • EasyBank Task 2 Page 2 of 35
,The primary challenge is therefore not necessarily the absence of required banking features. Instead, the
application needs a more understandable information architecture, clearer navigation pathways, and consistent
interaction patterns.
This project proposes a user-centered design approach consisting of requirements analysis, low-fidelity
wireframes, UML modeling, interactive prototyping, and structured usability testing.
The proposed design organizes the application around five primary areas: account overview, fund transfers, bill
payments, transaction history, and customer support. Each section supports a common user goal, reducing the
need to search through unrelated screens or interpret unclear interface labels.
The interactive demonstration includes representative workflows for reviewing account information, transferring
funds between fictional accounts, scheduling simulated payments, searching transaction records, and receiving
help.
The usability testing plan establishes measurable objectives, participant criteria, testing scenarios, observation
methods, and an approach for converting user feedback into design improvements.
The expected outcome is a banking interface concept that allows users to find essential functions, understand
financial information, recognize potential errors, and complete ordinary account-management activities more
confidently.
This resource documents a proposed product design. It does not claim that live customer testing has been
performed or that production banking transactions are operational.
2. Project Background
2.1 Company Overview
TechWave Solutions specializes in developing customized software applications for businesses.
One of its projects is EasyBank, a banking application intended for financial institutions serving retail and
business customers.
The application is designed for access through modern web browsers and includes functions typically associated
with online banking.
These functions include account access, transaction management, bill payment, fund transfers, and customer
support.
2.2 Current Situation
The EasyBank application is in the late stages of its development.
Initial feedback indicates that users are experiencing difficulty navigating the application interface. This creates
additional demand for customer support because customers may require assistance finding features or
completing common tasks.
The problem suggests that some existing design decisions may not adequately reflect users' expectations, mental
models, or interaction needs.
A technically functional application can still create a poor experience when critical functions are difficult to
locate, instructions are unclear, or users receive insufficient feedback during important operations.
2.3 Problem Statement
EasyBank's existing interface presents usability challenges that make it difficult for some customers to navigate
the application and complete common banking activities independently.
WGU D779 • EasyBank Task 2 Page 3 of 35
, These challenges are associated with increased customer support inquiries and create a need to improve
navigation, interface clarity, workflow efficiency, and accessibility.
2.4 Proposed Solution
The proposed solution is a redesigned user interface organized around common banking activities.
The design introduces clearly labeled primary navigation, a simplified dashboard, consistent transaction forms,
review and confirmation steps, understandable error messages, and readily accessible support options.
An interactive prototype will allow stakeholders and representative users to evaluate these design decisions
before substantial implementation changes are made.
Structured usability testing will then identify areas requiring further refinement.
3. Project Objectives
The project has six primary objectives.
Objective 1: Improve navigation clarity.
Users should be able to recognize where important banking functions are located without relying on customer
support.
Objective 2: Improve task completion.
Users should be able to perform ordinary account activities with clear instructions and understandable system
feedback.
Objective 3: Reduce avoidable interaction errors.
Forms should support correct data entry and provide opportunities to review important details before
confirmation.
Objective 4: Improve accessibility.
The interface should support keyboard navigation, meaningful control labels, readable content, and responsive
layouts.
Objective 5: Maintain requirements traceability.
Product features, user stories, screen designs, and usability tasks should connect to defined requirements.
Objective 6: Provide an evidence-based design improvement process.
Usability observations should inform revisions rather than relying entirely on developer assumptions.
4. Scope
4.1 In Scope
The proposed design covers:
• Navigation and account dashboard organization.
• Account balance presentation.
• Transaction-history discovery and search.
• Statement download interface.
• Fund transfer workflows.
• Registered payee selection.
WGU D779 • EasyBank Task 2 Page 4 of 35
EasyBank Usability Testing Plan, UML Design, Wireframes & Interactive
Prototype
Course: Software Product Design and Requirement Engineering
Institution: Western Governors University
Resource edition: 2026/2027
Research verification
For Task 2, we need to change scenarios. Task 1 uses CityLink, while the publicly available Task 2 scenario
identifies EasyBank, a web-based banking application being developed by TechWave Solutions.
The EasyBank scenario establishes that:
• The application serves small and medium-sized financial institutions.
• Its features include account management, fund transfers, bill payments, transaction history, and customer
support.
• Users have reported navigation difficulties, contributing to increased support inquiries.
• The identified users include retail customers, business customers, and customer support representatives.
• The design must account for accessibility, responsive layouts, security, and financial regulatory obligations.
Independent D779 student accounts corroborate that Task 2 involves usability testing, wireframes, UML
diagrams, and an interactive prototype. Some reported using Figma or PowerPoint.
Verification limitation: These sources establish the likely assessment structure, but the complete October 2026
WGU Task 2 rubric remains unavailable. The resource below is an original comprehensive worked example, not a
verified reproduction of the scoring instructions.
Interactive EasyBank prototype
The accompanying prototype has been created and browser-tested. It includes working navigation and simulated
banking workflows using fictional account data.
WGU D779 • EasyBank Task 2 Page 1 of 35
,The prototype demonstrates account balances, transfers, bill payments, transaction history, and support. It does
not process real financial transactions or implement production banking security.
PART A: EASYBANK SOFTWARE PRODUCT DESIGN
Usability Testing Plan, Requirements Analysis, Wireframes, UML Modeling, and
Prototype Design
Course: D779 – Software Product Design and Requirement Engineering
Assessment: SJN1 – Task 2
Institution: Western Governors University
Project: EasyBank Web-Based Banking Application
Organization: TechWave Solutions
Version: 1.0 | October 2026
Document Status: Original scenario-based design and usability resource
1. Executive Summary
TechWave Solutions is developing EasyBank, a web-based banking application intended to provide accessible,
secure, and convenient financial services to customers of small and medium-sized financial institutions. The
application supports core banking activities, including account management, fund transfers, bill payments,
transaction history, and customer support.
Although EasyBank is approaching the later stages of development, preliminary feedback indicates that some
users experience difficulties navigating the interface. These difficulties have contributed to increased customer
support inquiries, suggesting a gap between the available functionality and users' ability to discover and
complete essential banking activities efficiently.
WGU D779 • EasyBank Task 2 Page 2 of 35
,The primary challenge is therefore not necessarily the absence of required banking features. Instead, the
application needs a more understandable information architecture, clearer navigation pathways, and consistent
interaction patterns.
This project proposes a user-centered design approach consisting of requirements analysis, low-fidelity
wireframes, UML modeling, interactive prototyping, and structured usability testing.
The proposed design organizes the application around five primary areas: account overview, fund transfers, bill
payments, transaction history, and customer support. Each section supports a common user goal, reducing the
need to search through unrelated screens or interpret unclear interface labels.
The interactive demonstration includes representative workflows for reviewing account information, transferring
funds between fictional accounts, scheduling simulated payments, searching transaction records, and receiving
help.
The usability testing plan establishes measurable objectives, participant criteria, testing scenarios, observation
methods, and an approach for converting user feedback into design improvements.
The expected outcome is a banking interface concept that allows users to find essential functions, understand
financial information, recognize potential errors, and complete ordinary account-management activities more
confidently.
This resource documents a proposed product design. It does not claim that live customer testing has been
performed or that production banking transactions are operational.
2. Project Background
2.1 Company Overview
TechWave Solutions specializes in developing customized software applications for businesses.
One of its projects is EasyBank, a banking application intended for financial institutions serving retail and
business customers.
The application is designed for access through modern web browsers and includes functions typically associated
with online banking.
These functions include account access, transaction management, bill payment, fund transfers, and customer
support.
2.2 Current Situation
The EasyBank application is in the late stages of its development.
Initial feedback indicates that users are experiencing difficulty navigating the application interface. This creates
additional demand for customer support because customers may require assistance finding features or
completing common tasks.
The problem suggests that some existing design decisions may not adequately reflect users' expectations, mental
models, or interaction needs.
A technically functional application can still create a poor experience when critical functions are difficult to
locate, instructions are unclear, or users receive insufficient feedback during important operations.
2.3 Problem Statement
EasyBank's existing interface presents usability challenges that make it difficult for some customers to navigate
the application and complete common banking activities independently.
WGU D779 • EasyBank Task 2 Page 3 of 35
, These challenges are associated with increased customer support inquiries and create a need to improve
navigation, interface clarity, workflow efficiency, and accessibility.
2.4 Proposed Solution
The proposed solution is a redesigned user interface organized around common banking activities.
The design introduces clearly labeled primary navigation, a simplified dashboard, consistent transaction forms,
review and confirmation steps, understandable error messages, and readily accessible support options.
An interactive prototype will allow stakeholders and representative users to evaluate these design decisions
before substantial implementation changes are made.
Structured usability testing will then identify areas requiring further refinement.
3. Project Objectives
The project has six primary objectives.
Objective 1: Improve navigation clarity.
Users should be able to recognize where important banking functions are located without relying on customer
support.
Objective 2: Improve task completion.
Users should be able to perform ordinary account activities with clear instructions and understandable system
feedback.
Objective 3: Reduce avoidable interaction errors.
Forms should support correct data entry and provide opportunities to review important details before
confirmation.
Objective 4: Improve accessibility.
The interface should support keyboard navigation, meaningful control labels, readable content, and responsive
layouts.
Objective 5: Maintain requirements traceability.
Product features, user stories, screen designs, and usability tasks should connect to defined requirements.
Objective 6: Provide an evidence-based design improvement process.
Usability observations should inform revisions rather than relying entirely on developer assumptions.
4. Scope
4.1 In Scope
The proposed design covers:
• Navigation and account dashboard organization.
• Account balance presentation.
• Transaction-history discovery and search.
• Statement download interface.
• Fund transfer workflows.
• Registered payee selection.
WGU D779 • EasyBank Task 2 Page 4 of 35
