Forty-one requirements, every one attributed to one of eleven labor-unit roles and given a measurable fit criterion, make up the HI580 Unit 2 list at one composite hospital. Searches like "hi 580 unit 2 assignment example", "hi580 unit 2 sample" and "hi580 unit 2 example" land here.
What a finished HI580 Unit 2 stakeholder requirements list looks like
A stakeholder register opens the list: labor nurse, charge nurse, obstetrician, certified nurse-midwife, anesthesiologist, neonatal nurse, unit clerk, risk manager, health information management, biomedical engineering and the interface analyst, each with the interview date and method. The requirements table follows. Each row holds an identifier, the requirement in one sentence, the source role, a rationale, the fit criterion and a priority from 1 to 3. REQ-19, from the neonatal nurse, reads: a newborn record created at delivery links to the mother's record without re-entry of shared data, and its fit criterion requires twins to produce two linked records, labeled A and B, in under [two] minutes. REQ-27, from risk management, requires every archived tracing to be retrievable by patient and date within [five] minutes. Conflicts between roles get a table of their own.
How a HI580 Unit 2 example is structured
Stakeholders come before requirements so a reader can check that no role was skipped, and the register notes two roles reached only by survey rather than interview. Requirements are grouped along the course of a labor, admission and triage, surveillance, documentation, delivery and newborn, transfer and archive, with a final group for availability and downtime, so a gap at any stage shows. Each requirement states what, never how, leaving design for later units. The fit criterion is what makes a line testable: a number, a time or an observable result. Rationale explains why the role needs it, which matters once priorities are argued. The conflicts table records the three places roles disagreed, such as obstetricians wanting remote tracing access that risk management wanted logged, and names who resolves each. Assumptions and exclusions close the list.
Eleven roles, two by survey
The register of who was asked, when and how, including the two roles reached only by questionnaire and the gaps that method may leave.
Grouped along a labor
Admission, surveillance, documentation, delivery and newborn, transfer and archive, then availability, so each stage of care can be checked for missing requirements.
A fit criterion on every line
The measurable condition attached to each requirement, a time, a count or an observable result, which later becomes the basis of an acceptance script.
Where roles disagree
Three conflicts, including remote tracing access for obstetricians against risk management's logging demand, each with the person named to settle it.
What, never how
Requirements stated as needs rather than features, so no line quietly selects a product before the selection unit has weighed the candidates.
Where marks go in HI580 Unit 2
Requirements phrased as qualities, reliable, intuitive, fast, draw the most pointed comments, because a line with no fit criterion cannot be accepted or refused later. Unattributed requirements come next; many sections expect the source role on every row, and a list that reads like one analyst's opinion loses the stakeholder half of the title. Feature statements disguised as needs, must include a mobile app, quietly choose a product before evaluation. Graders also watch for missing roles, and on a labor unit the neonatal side and health information management are the ones most often absent. Conflicts smoothed over rather than recorded suggest the interviews were never compared. Priorities assigned to everything as top priority give selection nothing to work with, and a list with no downtime requirements leaves the system's most dangerous hour unspecified.
Get a HI580 Unit 2 example written to your instructions
A requirements list depends on who your scenario names. Send the Unit 2 prompt, its rubric and the assigned setting, and a custom list will trace each line to a role and attach a measurable condition to it. The first sample is free, returned in 24-48h and formatted as your course expects.
HI580 Unit 2 questions, answered
What is a fit criterion?
A measurable condition that shows whether a requirement has been met, such as a time limit, a count or an observable outcome. The term comes from requirements engineering practice, and the example attaches one to every line. Without it, a requirement like fast retrieval cannot pass or fail a test, and the later acceptance scripts have nothing to check against.
Can I include requirements from roles I could not interview?
Yes, if the paper says how they were gathered. The example reaches two roles by survey and marks those rows, so a reader knows their evidence is thinner. Published role descriptions or scenario materials can also stand in, labeled as such. What graders object to is a requirement attributed to a role with no indication of where it came from.
Should the list rank requirements?
Most rubrics expect some prioritization, and the method matters less than its discipline. The example uses three levels and explains what separates each, with patient safety and legal retention requirements held at the top. A list where nearly every line is top priority gives the selection unit no way to separate candidates that meet different subsets.