Patient Information System

For the following exercises, use the patient information system introduced as a case study within Chapter 1. Use this case study across all exercises.

1. Create one or more UML activity diagram(s) illustrating how this system might handle the management of individual care needs, patient monitoring and administrative reporting. Include at least 10 elements or process boxes within your diagram.
   • Use the drawing features within applications like Word, PowerPoint or Visio to generate the diagram. If Visio is used, print the file to a .pdf format prior to submitting it for grading.
2. Write 15 or more SCRUM user stories for the patient information system. Use the following story format: “As a (role), I want/need (functionality), so that I can (justification/benefit).”
   • Normally, user stories are transferred into story cards written on index cards or post-it notes. Then, the story cards are posted on a story board.
   • For this assignment, user stories can be submitted using Microsoft Word.
3. Using the user stories you just identified, create a prioritized Product Backlog for the patient information system. The highest priority items should be near the top of your Product Backlog, with the lowest priority appearing toward the bottom.
4. Using the Product Backlog you just identified, create a Sprint Backlog that might be suitable for a 2-week sprint.

Question 2

For each of the following 4 questions, in 100–200 words per question, explain if you agree or disagree with the statement and why. Use outside references to validate your claim.

• When performing a feasibility analysis, is it necessary to decompose large systems into layers before proceeding with a new system design or reengineer effort?
• Should a system architecture effort be mostly centered on the hardware platforms in play at an organization?
• When tasked with designing a new system, is it necessary that all systems that interface with the target system also be upgraded to the current technology to be used? Think version levels (e.g., operating system, hardware, applications like Java).
• Can a new system design be pursued while excluding any of the following considerations?
  • Budget
  • Technical staff competence and expertise
  • Workforce training

  Please explain your opinion for each area.