D779 is a term 1 course in WGU's Master of Science, Software Engineering, AI Engineering, listed at 3 competency units.
WGU describes it as an in-depth look at integrating user needs and system requirements into software development, covering types of requirements, gathering techniques, prioritization and documentation.
It is the course where good engineers meet the people who will use the software. Many students find that writing a clear requirement is harder than expected: a good one is specific, testable and traceable to a stakeholder, while a vague one causes rework months later.
Course at a Glance
| Item | Details |
|---|---|
| University | Western Governors University |
| Code | D779 (confirm on your degree plan) |
| Program | Master of Science, Software Engineering, AI Engineering |
| Size and term | 3 competency units, term 1 |
| Subject | Requirement types, elicitation, prioritization, documentation, usability |
What D779 Covers
| Competency (WGU wording, summarized) | What you show |
|---|---|
| Explains the importance of requirement types for a project's needs | Functional, non-functional and constraints |
| Gathers and documents stakeholder needs and constraints | Elicitation and a clear record |
| Describes the impact of new requirements on design | Change impact reasoning |
| Translates requirements into software design | A bridge from needs to structure |
| Describes usability testing to evaluate effectiveness and recommend improvements | A test plan and how findings drive changes |
Key Concepts Explained
Functional and Non-Functional Requirements
Functional requirements say what the system does. Non-functional requirements describe qualities such as speed, security, accessibility and reliability. Both need to be testable.
Weak: The app should be fast.
Stronger: The search page shall return results within 2 seconds for 95 percent of queries under a load of 500 concurrent users.
Elicitation Techniques
| Technique | Best for | Watch out for |
|---|---|---|
| Interviews | Depth from key stakeholders | Individual bias |
| Surveys | Breadth across many users | Shallow answers |
| Observation | Real workflows | Time cost |
| Prototypes | Testing understanding early | Treating a prototype as final |
Prioritization
Methods such as MoSCoW (must, should, could, won't) help agree what ships first. The reason for each ranking matters as much as the ranking.
Example: For a booking app, "reset a forgotten password" is a Must because users cannot otherwise return. "Dark mode" is a Could, as it improves comfort but does not block use.
Typical Assignments and How to Approach Them
| Assignment type | What it tests | How to approach it |
|---|---|---|
| Requirements specification | Clarity and completeness | Group by type, make each testable, trace to a stakeholder |
| Elicitation plan | Choosing techniques | Match technique to stakeholder and risk |
| Change impact analysis | Effect of new requirements | Trace to design, cost and schedule |
| Usability test plan | Evaluation | Define tasks, participants, measures and how results change the design |
Study Approach
- Practice rewriting vague requirements into measurable ones.
- Build a traceability table from stakeholder to requirement to design element.
- Write a five-task usability test for a simple app.
- Run a change through your table and note what moves.
From Requirement to Design
The translation competency is easier with one traceable chain.
| Stakeholder need | Requirement | Design element |
|---|---|---|
| Patients want to book without calling | The system shall let a user book an available slot in no more than 4 steps | Booking service and calendar view |
| Clinic must protect records | All patient data shall be encrypted in transit and at rest | Encrypted storage and secure API gateway |
| Staff need quick changes | Authorized staff shall reschedule within 2 minutes | Role-based admin interface |
Usability Testing in Brief
Usability testing is easy to describe loosely. A good plan is specific.
| Element | Example |
|---|---|
| Participants | Five users representing the main user group |
| Tasks | Book an appointment, change it and cancel it |
| Measures | Task success, time on task, errors, satisfaction rating |
| Findings to action | If three of five users miss the cancel button, move it and retest |
The last row matters: the competency asks how results lead to recommended improvements.
Handling a Changed Requirement
Change impact is a named competency. Show it as a short sequence.
- State the new requirement and who requested it.
- Trace which existing requirements and design elements it touches.
- Estimate the effect on cost, schedule and risk.
- Recommend accept, defer or decline, with reasons.
For example, adding text-message reminders to a booking app touches the notification service, user preferences and privacy rules, so the impact is larger than it first looks.
Where Students Get Stuck
- Untestable wording. Add numbers and conditions.
- Solutions as requirements. State the need, not the technology.
- Missing non-functional needs. Check security, performance and accessibility.
- No link to design. Show how each requirement shapes a design decision.
Study Tips for D779
- Use "shall" with a measurable condition.
- Keep stakeholder names consistent.
- Label each requirement with an ID.
- Use rubric headings.
How We Help with D779
Send the instructions, case and rubric. We explain requirement engineering, prepare model structures or review your draft. Design follows in D780.
GradeEssays is independent of Western Governors University. Our work is a study and reference aid: use it to understand the method, then write and submit your own work under WGU's academic integrity policy.
Every order is written from scratch, plagiarism-checked, includes free revisions within the scope of your original request, and is refunded in full if it is late.
Get Your D779 Requirements in Order
Share the scenario and your draft. We prepare a model requirements structure or give feedback against the rubric.
Start My D779 HelpFree revisions · Full refund if late · Written from scratch for your order
Frequently Asked Questions
3 competency units, in term 1 of the MS Software Engineering, AI Engineering program.
Types of requirements, gathering techniques, prioritization and documentation, plus usability testing and translating requirements to design.
A quality the system must have, such as performance, security or accessibility.
A prioritization method: must have, should have, could have and won't have this time.
Mostly analysis and documentation, though you should understand how requirements shape software.
No. We tutor, prepare model structures and give feedback. You submit your own work.