D.B 4
docx
keyboard_arrow_up
School
University of Maryland, University College *
*We aren’t endorsed by this school
Course
610
Subject
Information Systems
Date
Dec 6, 2023
Type
docx
Pages
2
Uploaded by richealagyei42
The work breakdown structure below is based on a patient portal software application that was
presented in the week 3 discussion. This portal software is used for a hypothetical hospital to
allow patients to schedule appointments, view services, consult doctors, and receive care while
being away from the hospital. This software is essential for hospitals to have during pandemics
where patients should not be interacting in person with staff if possible. This work breakdown
structure shows how the project will be structured.
Work Breakdown Structure
Initiation
Identify the needs of the project
Define the "why" and the purpose of the project. What need is not being met?
Conduct feasibility study
Determine if the proposed solution actually accomplishes the identified goal.
Planning
Identify the scope
Determine what features the software will not include.
Identify requirements
List all requirements for the project and finalize the scope of the project. Make sure to prevent
scope creep in the future.
Gather team
Hire developers and UI designers to accomplish the project. Establish the project head and the
team that will bring the project to completion.
UI/UX design
Define the UI of the software to begin to receive feedback from stakeholders. Use the feedback
to guide the design of the prototype software and prevent issues in the future.
Execution
Develop prototype
Create a minimal proof-of-concept that accomplishes the vital goal of the project. Discuss and
demo the prototype to stakeholders to receive feedback and guide the rest of the project.
Complete the plan
Implement feedback from the prototype to finalize the design of the product and complete the
final plan to bring the project to completion.
Develop final software
Develop the bulk of the project using the team that was built. Minor changes to the project are
allowed but major changes should be identified with the prototype feedback.
Follow a strict timeline to ensure the project is completed at a reasonable time.
Conduct alpha and beta testing to verify that the product works.
Closeout
Verify requirements met
Ensure that the developed software actually accomplishes the goal that it set out to. Ensure
patients can use it as designed.
Software/customer support
Train hospital staff and educate patients on how to use the software and its availability. Many
long-time patients will need to be taught how to use the program as they may be used to other
means of accessing care.
Bug fixing
Provide bug support to ensure that users have a useful experience.
Long-term support
Provide support in the form of bug fixes, UI tweaks, and updates in the future.
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
- Access to all documents
- Unlimited textbook solutions
- 24/7 expert homework help