C179 is Western Governors University's introduction to the business side of information systems, listed in the IT Management program.
The course description introduces students to information systems (IS) and covers management of information systems (MIS) topics such as system development and business continuity. It also gives an overview of management tools and issue tracking systems.
We confirmed this wording through course materials rather than WGU's own site, so check your course page for the current outcomes.
The challenge is perspective. Technical students tend to describe tools; the course asks how those tools serve the business and protect it.
Course at a Glance
| Item | Details |
|---|---|
| University | Western Governors University (WGU) |
| Course code | C179 |
| Level | Undergraduate |
| Format | Competency-based, self-paced |
| Subject area | Management information systems |
| Assessment | Check your course page for the current assessment type |
What C179 Covers
| Area | Key ideas |
|---|---|
| Information systems | People, processes, data and technology working together |
| System development | Life cycle approaches such as waterfall and agile |
| Business continuity | Keeping critical services running during and after disruption |
| Management tools | Tools that plan and track IT work |
| Issue tracking | Logging, prioritizing and resolving incidents and requests |
Key Concepts Explained
The System Development Life Cycle
The SDLC moves through planning, analysis, design, implementation and maintenance. Waterfall completes each phase before the next; agile repeats short cycles and delivers working parts early.
Example: A clinic wants online appointment booking. A waterfall approach gathers all requirements first, then builds and launches the full system. An agile approach releases basic booking in a few weeks, then adds reminders and cancellations based on patient feedback. Agile suits changing needs; waterfall suits fixed, well-understood requirements.
Business Continuity
A business continuity plan identifies critical functions and how to keep them running. Two key measures are the recovery time objective (how quickly a system must be restored) and the recovery point objective (how much data loss is acceptable).
Example: An online shop sets an RTO of two hours and an RPO of 15 minutes for its order system. That means backups at least every 15 minutes and a standby system that can take over within two hours. Its internal wiki, being less critical, might have an RTO of two days.
Issue Tracking
Issue tracking systems log problems and requests as tickets, assign them, set priorities and record the fix. Reports from the system show trends, such as a recurring fault worth fixing permanently.
Business Impact Analysis
Continuity planning usually starts with a business impact analysis. It lists business functions, the systems they depend on, and the cost of each hour of downtime, financial and otherwise.
The results set priorities. Functions with the highest impact get the shortest recovery times and the most investment. In a written task, showing this link from impact to recovery objectives demonstrates business thinking rather than a list of technical fixes.
Typical Tasks and How to Approach Them
| Task type | What it tests | How to approach it |
|---|---|---|
| Development approach | Choosing a methodology | Match waterfall or agile to the project's needs |
| Continuity plan | Protecting operations | Rank functions, set RTO and RPO, plan recovery |
| Tool evaluation | Management tools | Compare tools against business requirements |
| Issue tracking scenario | Incident handling | Prioritize by impact and urgency |
Incidents, Problems and Changes
IT service management separates three ideas that issue tracking systems often record:
- Incident: an unplanned interruption, such as email being down. The goal is to restore service quickly.
- Problem: the underlying cause of one or more incidents. The goal is a permanent fix.
- Change: a planned modification to a system, reviewed so it does not cause new incidents.
Using these terms precisely in a written task shows you understand how IT work is managed, not just how tools are used.
Where Students Get Stuck
- Too technical. Explain the business reason behind each recommendation.
- RTO versus RPO. RTO is about time to restore; RPO is about data loss.
- Generic plans. Tie continuity steps to the organization in the scenario.
- Ignoring the rubric. Address every rubric point with its own heading.
Study Tips for C179
- Look at a free issue tracking or project tool to see how tickets flow.
- Compare waterfall and agile in a simple table with pros, cons and best uses.
- Practice writing RTO and RPO for systems you use every day.
- Set your own deadlines for each section of a written task.
How We Help with C179
Send the task instructions, rubric, scenario and any evaluator feedback. An IT writer prepares a custom response, explains continuity and development concepts, or edits your draft. See also our case study writing guide.
GradeEssays is independent of Western Governors University. Our work is a study and reference aid: you write and submit your own work under WGU's academic integrity policy. We never take exams or access student accounts. Orders include free revisions within the scope of your original request.
Connect IT Systems to Business Needs
Share the task, rubric and your draft. An IT writer prepares a custom response or feedback to learn from.
Start My C179 HelpFree revisions · Full refund if late · Written from scratch for your order
Frequently Asked Questions
Information systems and MIS topics such as system development and business continuity, plus an overview of management tools and issue tracking systems.
Check your WGU course page for the current assessment.
RTO is the maximum acceptable time to restore a system; RPO is the maximum acceptable amount of data loss, measured in time.
No. It focuses on managing information systems rather than writing code.
It depends on the scenario. Agile suits changing requirements; waterfall suits stable, clearly defined ones.
No. We provide models, explanations and editing so you can produce your own work.