Send the exact assignment or rubric from your course of study and a custom sample written to it lands in 24 to 48 hours, the first one free. C798 is WGU’s Informatics System Analysis and Design course. It centers on planning a clinical information system project through the systems development life cycle, from charter to evaluation, with realistic time and resources. Searches like "c798 task 2 assignment example", "C798 sample paper", and "C798 task samples" land on this page.
What C798 is really about
Informatics System Analysis and Design asks the student to act as the informatics nurse specialist on a system project and plan it from start to finish. The systems development life cycle gives the structure: planning, analysis, design, building and testing, implementation, and maintenance and evaluation. The course is less interested in whether a student can name the phases than in whether the plan is realistic. That means tasks that belong to the right phase, dependencies that make sense, owners for every task, milestones and a time frame that allows for testing and training rather than squeezing them.
Current versions frame the work around a scenario, often a newly hired specialist at a midsize or rural hospital, and ask for a Gantt chart alongside the written plan. The chart carries real weight, because it shows at a glance whether the student understands sequence and overlap. Many plans also address the social side of implementation: stakeholders, communication, training and the risks that come from people and workflow rather than software. Any practice experience record connected to the course is the student's own. The projects and hospitals on this shelf are composites.
What C798’s tasks ask for
The task typically asks for a project plan covering each life cycle phase with tasks, deliverables and responsible roles, a Gantt chart showing timing and dependencies, and a description of the resources required. Expect to address stakeholders, risk and communication, and in many versions testing, training and go-live support in some detail. Some versions ask how the project will be evaluated after implementation. Scholarly support is expected where the plan relies on published guidance about safe implementation or usability.
Why C798 tasks come back for revision
Plans come back when phases are described in general terms that would fit any project, with no tasks specific to the system in question. Gantt charts are returned for missing dependencies, such as training scheduled before the build is tested, or for owners left blank. A common miss is an implementation phase with no support plan for the first days after go-live. Revision notes are usually precise and the fixes additive.
The C798 drawers
C798 Task 1 SDLC project plan example
In many versions the task is a full life cycle plan with a Gantt chart for one system. On request, free, 24-48h.
C798 Task 2 implementation risk plan example
Some versions add a piece on risks, communication and go-live support. On request, free, 24-48h.
Your course of study shows something else?
Western Governors University revises courses; task counts and deliverables shift between terms. Send what your classroom shows and the desk matches it exactly.
Using a C798 sample the right way
Read a C798 sample alongside its chart. Notice that each phase lists tasks, a deliverable, an owner and a dependency, and that the chart matches the text row for row. Then plan your own scenario with the same discipline. Send the task instructions and rubric aspects for a custom sample in 24-48h, the first one free.
How these samples are written
The discipline behind every task here: aspects are the outline, each gets its section, artifacts match their narratives, and OA courses get prep-note treatment instead, because the sit is always yours. Send your portal's rubric with a request and the sample matches it, revisions included.
C798 questions, answered
What should a C798 Gantt chart include?
Tasks down one side, time periods across the top, bars or marks for when each task runs, milestones and, ideally, owners. Dependencies should be visible, either by sequence or by notes.
How long should the C798 project timeline be?
Long enough to be realistic for the system and the setting. Allow time for analysis, testing and training; a plan that builds and goes live within a month or two usually reads as unrealistic.
Does the C798 plan need a budget?
Many versions ask for resources rather than a detailed budget. Name the people, time and tools required, and include costs if your instructions ask for them.