Overview
As you learned from this module’s resources, one of the most important steps in a systems planning phase involves analyzing a business case. A business case provides background information on the organization that plans to implement a new system. It often includes an organizational mission statement, a problem statement for the current system, and stakeholder interviews. Analyzing the business case allows an IT project team to develop a system requirements specification (SRS) and an implementation plan that addresses the needs of the business.
Prompt
Imagine that you are the systems engineer leading a project to implement a new software system for a healthcare organization, Millennia HealthCenter (MHC). In order to plan for the project, you have to better understand the organization and its needs for a new system. Review the following documents to strategize how your team can implement an IT solution:
- Business case for Millennia HealthCenter (Document Attached Below***)
- Interviews with the stakeholders: (Skateholders Interviews Document Attached Below***)
- Doctor
- Nurse
- Business Admin
- Pharmacist
- The workflow of existing system and processes (Document Attached Below***)
By thoroughly reviewing these documents, you will have a better idea as to why MHC plans to implement a new system. You will use the information you learned about the organization, its processes, and the users to help you develop an SRS. For the purpose of this activity, you will work on the Introduction section of your SRS for Millennia HealthCenter’s new IT system.
After you have reviewed all of the files:
- Download the Systems Requirements Specification Template (Template Attached Below***)
- Create the Introduction content, which must include:
- System purpose
- System scope
- System overview
- System context
- System functions
- User characteristics
Guidelines for Submission
- Upload and submit your template with the Introduction section completed.
- If you want to get ahead or take notes on the sections after the introduction, you have the option to do so. Only the Introduction section will be graded by your instructor for this activity.
| Criteria | Exemplary (100%) | Proficient (85%) | Needs Improvement (55%) | Not Evident (0%) | Value |
|---|---|---|---|---|---|
| System Purpose | Exceeds proficiency in an exceptionally clear, insightful, sophisticated, or creative manner | Identifies the purpose of the system and its intended audience | Shows progress toward proficiency, but with errors or omissions; areas for improvement may include providing more detail so a project team can understand the purpose | Does not attempt criterion | 10 |
| System Scope | Exceeds proficiency in an exceptionally clear, insightful, sophisticated, or creative manner | Defines the problems that the system will resolve, the vision for the system, and what the system may or may not be able to do | Shows progress toward proficiency, but with errors or omissions; areas for improvement may include addressing more completely the limitations of the system | Does not attempt criterion | 15 |
| System Overview | Exceeds proficiency in an exceptionally clear, insightful, sophisticated, or creative manner | Provides an overview of the system, such as its important aspects | Shows progress toward proficiency, but with errors or omissions; areas for improvement may include highlighting multiple components of the system | Does not attempt criterion | 10 |
| System Context | Exceeds proficiency in an exceptionally clear, insightful, sophisticated, or creative manner | Describes the context of the system, such as who will be using the system, where the system will be used, the industry and organizations that will use the system, and the various interfaces that will interact with the system | Shows progress toward proficiency, but with errors or omissions; areas for improvement may include greater consideration as to how the system will interact with users and other systems | Does not attempt criterion | 15 |
| System Functions | Exceeds proficiency in an exceptionally clear, insightful, sophisticated, or creative manner | Describes the main functionality of the system, such as how the current system functions and how the new system will differ from the current system | Shows progress toward proficiency, but with errors or omissions; areas for improvement may include more ways in which the system will function | Does not attempt criterion | 20 |
| User Characteristics | Exceeds proficiency in an exceptionally clear, insightful, sophisticated, or creative manner | Describes the characteristics of the users who will be using the system once it is implemented | Shows progress toward proficiency, but with errors or omissions; areas for improvement may include descriptions of more key users | Does not attempt criterion | 20 |
| Articulation of Response | Exceeds proficiency in an exceptionally clear, insightful, sophisticated, or creative manner | Clearly conveys meaning with correct grammar, sentence structure, and spelling, demonstrating an understanding of audience and purpose | Shows progress toward proficiency, but with errors in grammar, sentence structure, and spelling, negatively impacting readability | Submission has critical errors in grammar, sentence structure, and spelling, preventing understanding of ideas | 5 |
| Citations and Attributions | Uses citations for ideas requiring attribution, with few or no minor errors | Uses citations for ideas requiring attribution, with consistent minor errors | Uses citations for ideas requiring attribution, with major errors | Does not use citations for ideas requiring attribution | 5 |
| Total: | 100% | ||||
0 comments