D479 explores the tools and techniques of user experience design. WGU's Software Engineering guide says students create deliverables such as persona profiles, information architectures and prototypes of different fidelity, and study usability testing.
It is a 3-unit course in term 5 of the Standard Path. Students who are used to coding find it unfamiliar, because the aim is to design for real users and justify choices with evidence rather than to build working software.
Course at a Glance
| Item | Details |
|---|---|
| University | Western Governors University (WGU) |
| Program | Bachelor of Science, Software Engineering |
| Position | Term 5, 3 competency units |
| Competencies | Four, plus the opening planning conversation |
| Deliverables named | Persona profiles, information architectures, prototypes |
| Subject area | User experience design and usability testing |
What D479 Covers
| Competency (summarized) | What it means |
|---|---|
| Conduct formal and informal usability testing as part of prototyping | Observing users attempt tasks and recording problems |
| Design wireframes and prototypes using industry-standard tools and techniques | Moving from rough sketches to higher fidelity |
| Establish timeframes for UX projects based on business requirements | Planning effort and milestones |
| Update designs based on user testing analysis | Using findings to improve |
Key Concepts Explained
Personas
A persona is a realistic profile of a typical user: goals, needs, context and frustrations. It keeps design decisions focused on people rather than on the team's own preferences.
Example: "Maria, a part-time student, books clinic appointments on her phone between classes. Goal: book in under a minute. Frustration: long forms." That persona justifies a short form and large tap targets.
Fidelity
Low-fidelity sketches test structure cheaply. High-fidelity prototypes test visual detail and interaction. Choosing the right fidelity for the question you want to answer is part of the skill.
Usability Testing
Give users realistic tasks and watch where they hesitate. Record task success, time, errors and comments. A few participants reveal most major problems.
Example: Four of five users cannot find the "reschedule" option because it sits under "Profile". The finding leads to a specific change: move it to the appointment card, then retest.
Typical Assignments and How to Approach Them
The guide names deliverable types but not task wording. Follow your course's task and rubric.
| Deliverable | What it tests | How to approach it |
|---|---|---|
| Personas | Understanding users | Base them on stated research or the scenario, not invention |
| Information architecture and wireframes | Structure and flow | Show the main tasks and the shortest path to each |
| Prototype | Interaction design | Use a standard tool and keep screens consistent |
| Usability test report | Evidence-based improvement | Present findings, then changes linked to each finding |
Where Students Get Stuck
- Designing for yourself. Tie each choice to a persona need.
- Unjustified decisions. Explain why a layout helps a task.
- Test without findings. Report what went wrong and what you changed.
- Time planning. The competencies include timeframes, so add a realistic schedule.
Study Tips for D479
- Sketch first on paper; digital tools can wait.
- Write a task list per persona and check each screen supports it.
- Run a quick test with a friend even if the task allows only informal testing.
- Keep a consistent style across screens.
How We Help with D479
Send your task text, rough designs and notes. A writer can explain UX methods, draft a model write-up for study, or review your own deliverable for logic and clarity. For the next course in the sequence, see our guide for D480 Software Design and Quality Assurance.
GradeEssays is independent and not affiliated with WGU. We do not produce designs for submission, access portals or sit assessments. Our work is a study and feedback aid under WGU's academic integrity policy. Orders are written from scratch, with free revisions within the scope of your original request and a full refund if late.
A Practical Study Plan for D479
Design learning is easiest through making. Pick a simple app idea, such as a campus appointment booker, and use it as a running project through the course.
- Understand users. Write two personas with goals, needs and frustrations.
- Structure. Draw an information architecture showing the main sections and the paths to key tasks.
- Wireframe and prototype. Sketch low-fidelity screens, then build a higher-fidelity prototype in an industry-standard tool.
- Test. Run a quick usability test, record task success and problems, and list changes.
- Plan the work. Add a realistic timeline with milestones.
Keep before-and-after screens. Showing how test findings changed a design is the clearest evidence for the competency on updating designs.
Self-Check Questions for D479
Run through these before finalizing any design deliverable.
- Which user need does each screen serve?
- Can a new user finish the main task in few steps?
- What did usability testing reveal, and what did you change?
- Why did you choose this level of fidelity for this stage?
- Does the timeline reflect business requirements and realistic effort?
Strengthen Your UX Deliverables
Share your draft personas, wireframes or write-up. A design-minded writer gives feedback on clarity and logic.
Start My D479 HelpFree revisions · Full refund if late · Written from scratch for your order
Frequently Asked Questions
User Experience Design, a 3-unit course in term 5 of WGU's Bachelor of Science in Software Engineering.
The guide mentions persona profiles, information architectures and prototypes of different fidelity.
Yes. Conducting usability testing and updating designs from the results are listed competencies.
The description focuses on design deliverables rather than programming.
No. We explain, give examples for study and review your own work.
No. We are independent.