Please include ref in the body of the text and a separate ref Page This link also is a reading...

Question

Please include ref in the body of the text and a separate ref Page

This link also is a reading material along with liang

Please use external references as well

http://www.universityofcalifornia.edu/news/article/25105
Task
This assignment revolves around the Case Study, which may be found as a separate PDF document in the Resources/Assignment 1 section of the subject Interact site.
The objective of the assignment is to apply and consolidate skills acquired in the requirement and analysis disciplines through analysis of a simple case study, and to express the results through the relevant UML diagrams.
Part A – Vision (20 marks)
1. Analyse the Case Study documents and produce a Vision document for a software system to meet the needs identified in the Case Study. Make sure your Vision document:
a) Identifies the business case for development of the proposed system, identifying both the problem it is intended to solve, and the benefits to be expected from solving it.
b) Identifies all the stakeholders relevant to the system and their interest in it.
c) Identifies the key features of the proposed system
d) Clearly identifies the scope of the system
e) Identifies key considerations and constraints which affect the technical solution to be developed.
Use the Vision template provided in the Resources section for Assignment XXXXXXXXXXmarks)
Part B – High Level Functional Requirements (20 marks)
2. Analyse the Case Study documents and produce an initial high level functional requirements specification. Document these requirements with:
i. A use case diagram for the functional requirements of the entire system. (10 marks)
ii. Short use case descriptions for all use cases. (10 marks)
Part C – Detailed Functional Requirements (40 marks)
3. Detail the functional requirements for the system’s critical core use case. Document these requirements with:
i. A full use case description for the critical core use case. (10 marks)
ii. An activity diagram that shows the normal and major alternate flows for the critical core use case. (10 marks)
iii. A system sequence diagram showing the user’s inputs and system’s responses for the critical core use case’s normal flow. (10 marks)
iv. An operation specification for the most important single interaction between user and system during the critical core use case’s normal flow. (10 marks)
Part D – Object Modelling (20 marks)
4. Develop a domain model for the Case Study. Document your model with:
i. A domain class diagram showing inheritance and compositional relationships (10 marks)
5. Analyse the behaviour of the most important stateful object of the system and document this behaviour with:
ii. A state diagram (10 marks)
Rationale
This assignment elicits performance of taught skills in the requirement and analysis areas relevant to the following learning objectives:
• be able to analyse and validate system requirements;
• be able to produce and validate analysis and design models for a system;
• be able to demonstrate use of a CASE tool to document the models in a system
Marking criteria
Vision
• How well does the Vision document address its intended purpose?
• How well is the business case addressed in business terms?
• How well are stakeholders and their interests identified?
• How well are all key features identified and described in business terms?
• How well is the scope of the system identified?
• How well are key constraints and considerations identified?
• How suitable for release to stakeholders is the document?
High Level Functional Requirements
Use Case Diagram
• Is a correct concept of use cases demonstrated?
• Is correct UML syntax for use case diagrams applied?
Short Use Case Descriptions
• Is a correct concept of use cases demonstrated?
• Are all use cases identified and briefly described?
Detailed Functional Requirements
Full Use Case Description
• Is a correct concept of use cases demonstrated?
• Are all facets of a full use case description addressed?
• Are normal, alternate and exceptional flows identified and described, correctly?
Activity Diagram
• Is a correct concept of activities and flows demonstrated?
• Is the activity diagram consistent with the full use case description?
• Is correct UML syntax for activity diagrams applied?
System Sequence Diagram
• Are correct concepts of actors lifelines and messages demonstrated?
• Is the SSD consistent with the full use case description?
• Is correct UML syntax for activity diagrams applied?
Operation Specification
• Is a correct concept of an operation demonstrated?
• Is the operation specification consistent with the full use case description and the SSD?
• Are all facets of an operation specification addressed?
Object Modelling
Domain Model Class Diagram
• Is a correct concept of domain objects demonstrated?
• Is the domain model correct and does it support the use cases identified?
• Is correct UML syntax for domain class diagrams applied?
State Diagram
• Is a correct concept of object state demonstrated?
• Is the state diagram for the domain object correct?
• Is correct UML syntax for domain class diagrams applied?
Detailed objective standards for the criteria may be found in the Marking Criteria document in the Resources/Assignment 1 section of the subject Interact site.
Presentation
Submit assignments either as a single word processed document compatible with Microsoft Office, a PDF (.doc, .docx, or .pdf formats only) or as a single zip file containing all files submitted for the assignment.
Note: no other compression format apart from zip is acceptable. Any assignments submitted using some other compression format will be regarded as 'did not submit'.
Any diagrams must be contained in a word processed document, presented as images, or as an exported XML file from Visual Paradigm. Visual Paradigm Projects are not an acceptable format.
Requirements
You must submit your assignments as a single ZIP file containing all required documents.
Documents must be Microsoft Office compatible or PDF format.

005_zyauapo-pf3eevvx.zip 005_rseuapo-q1kzmw3k.zip

Robert · Accepted Answer

Electronic Health Records                                                                 1
Electronic health records 
Collaborative strategies predicated upon best practices 
According to the results of 2008 Kaiser Permanente and Ascension Health national time-and-
motion study, health care system has seen a major frustration among the care provider staff that 
is they spend more time with the paper and less with the patients. There was need to design, 
build and validate the standards for collection, organization and display of the patient 
information in computer system. The electronic documentation system for the nurses will capture 
vital patient information as part of their work while minimizing their documentation burden 
which would result in strong health care system and having common documentation with 
uniform goals and standards for the nurses. As it is known in other area of application, software 
systems have been able to eliminate medical errors when they are designed carefully to balance 
workflows with appropriate software applications.  (Neale G, Vincent C, 2007) 
Kaiser Permanente realized the need for the change and brought together its components: Inter-
regional Nursing Council (INC), Kaiser Permanente Labor Management Partnership (LMP). INC 
envisioned a clinical information system to inculcate the habit of evidence-based practice,foster a 
professional practice framework, and allow point-of-care documentation. Earliest of the 
collaborative effort was the development of a standardized process developed with the assistance 
of IDEO, an innovation and design consultant, for shift change between the arriving and 
departing nurses called as Nurse Knowledge Exchange (NKE). Thinking about these initiatives, 
the KP HealthConnect national and regional teams collaborated to launch KP Health-connect. 
Before KP HealthConnect was launched, each of the regions with the hospitals had different 
documentation practices for the nurses and thus INGG adopted the practices which were 
appropriate. After that INGG collaborated to create set of uniform care goals for the patient 
Electronic Health Records                                                                 2
irrespective of the location of the admission. Also, awareness among nurses was promoted to 
involve them into adopting and integrating the innovative workflows with content and 
functionality in KP HealthConnect implementation of which changed the key nursing practices.  
Lessons learned from failure 
The key lessons learned from the KP HealthConnect are: The apparent leaders among the staff 
members should be identified in order to recognize people who push behind their comfort zone 
and are willing to learn newer ways of doing things. The governance practice of nursing should 
be established early on by defining the roles and accountabilities and decision making steps. The 
nursing practice documentation and workflow should be in line with the commitment and 
engagement of leadership in decision making process. (Ontario Medical Association) The front 
line staff should be engaged in formulating the design of the content from the very early stage to 
develop trust and positive working relationships. The HER content should be general in nature 
and applicable to the wide range of patients and demographics.

Please include ref in the body of the text and a separate ref Page This link also is a reading material along with liang Please use external references as well...

Solution

Answer To This Question Is Available To Download

Related Questions & Answers

Submit New Assignment