Avail Best SENG205 Software Engineering Assignment Help Service - Hire Expertsminds Tutors For Help!

Home   Course   Kent Institute Australia Assignment Help
Previous << || >> Next

SENG205 Software Engineering Assignment - Client Presentation, Kent Institute Australia

Course Learning Outcomes addressed:

a) To gather, critically analyse, manage and present in meaningful ways information and data.

b) To prepare design and system documentation and written reports.

c) To elicit requirements from clients, discuss intermediate solutions and present oral reports as individuals and in teams.

d) To work collaboratively in small teams on a variety of large and small projects to produce models, software, documentation and reports.

GET GUARANTEED SATISFACTION OR MONEY BACK UNDER SENG205 SOFTWARE ENGINEERING ASSIGNMENT HELP SERVICES OF EXPERTSMINDS.COM - ORDER TODAY NEW COPY OF THIS ASSIGNMENT!

Design and develop a Unified Health Record (UHR) management system which can be used by the patient as well as their healthcare professionals (Doctors, Hospital staff), and their healthcare providers (insurance company).

Here are some of the requirements put forward by the Government:

1. The UHR data should be safe and secure.

2. User (patient) has complete control over what data they want to share with their healthcare professionals, and their healthcare providers.

3. Healthcare data should be maintained until the end of lifetime of the user and has to be kept up-to-date. All health record data should be deleted 1 month after the users demise.

4. Healthcare providers (insurance provider) should be able to access only the summary report provided at the end of the users last visit to their GP.

5. The software has three interfaces, each for the corresponding entity (user, healthcare professional, healthcare provider) accessing the record.

Answer - Unified Health Record System Design

Executive Summary

Healthcare industry is improving day by day and there is a rapid progress to include technology to ease operations and also improve the overall experience of all the stakeholders. The case study given here is about the interest of Australian government to implement an unified health record system that is secured, quick and easy to access and this shall be implemented nation wide. It is identified that there are 4 major user types - administrator, consultant, insurance service provider and patient.

The data flow diagram, use case, relationship and basic database and UI designs are all detailed in this paper. Subsequent to the diagrams, the way this project will be handled by the project team and connected to the project sponsor/client are also explained. Communication between stakeholders stands as the primary concern as this can enable the entire system to achieve the desired degree of performance and mitigate the risks in advance. Towards the end of the project, the architecture is also highlighted. However, database will continue to be cloud based so that it is minimal and easy to manage.

Introduction

Australian Government is looking to develop a unified health record system that can connect varied stakeholders of healthcare industry under one roof. Being a large scale project, it is essential to take extra care towards security of the system. Further, the purpose of this paper is to create a project charter comprising of resource allocation plans, work breakdown structure and other dataflow processes that will integrate front end and the database and present the end result to the client. The paper shall also contain wireframes of the unified health record system for a better understanding. This has a wide scope and is most needed to align the goals of the healthcare industry.

DO WANT TO HIRE TUTOR FOR ORIGINAL SENG205 SOFTWARE ENGINEERING ASSIGNMENT SOLUTION? AVAIL QUALITY SENG205 SOFTWARE ENGINEERING ASSIGNMENT WRITING SERVICE AT BEST RATES!

Requirement analysis

The unified health record (UHR) system to be developed has some of the requirements as mentioned below.

- Four different user categories - patient, insurance provider, healthcare consultant/doctor and administrator

- Security is the key as it includes confidential data that should not be leaked.

- Every user type has different roles and access rights in this system. This difference needs clarity.

- It is essential to maintain patient's data until the end of the lifetime and this has to be up-to-date.

Ideally, the target system includes a front end that interacts with the user and a back end that stores, evaluates and allows user to perform functions on the data.

The technical resource requirement has already been drafted.

Resource Required

Number of resources

Computers (Desktop/Laptops)

14

Internet connection server hubs and routers

2

The priorities of the final UHR system are as follows:

- Accessibility

- Ease of use

- Security

With these in place, it is possible to maximize the efficiency of this system and put it to productive usage that can benefit the stakeholders of healthcare industry to a greater extent.

System architecture

The UHR system has three segments in its architecture.

Software Engineering Assignment.png

This structure allows users to access from any type of device. The central system that stores all the confidential information of patients and histories are stored in patient health record and the patient continues to be the owner of the data. This is the personal domain of the UHR system. On the other hand, healthcare service providers, laboratories and insurance providers fall under the organizational domain (Roehrs et al, 2017). All of these stakeholders have similar access rights to private data of the patient.

As security is the key, here is a detailed framework of how operations would happen in this system.

Software Engineering Assignment1.png

The bottom layer in this architecture is the infrastructure layer that decides the storage and computing abilities of electronic health record (EHR) system. Due to ease of use, scalability and cost effectiveness, it is a good idea to implement cloud computing software to maintain data centers. In the middle layer f the architecture, security module, interface, networking, policy manager and HER manager segments are all present. Ideally, this middle layer takes care of the entire operations and authorizes the user who has requested for access of the data.

All the EHRs are aggregated and policies are meant to tighten the usability and security standards of the system. There are also sub modules that will be implemented to take care of specific operations. This shows that the architecture is flexible and scalable and the healthcare information will be stored as EHR instances and aggregated in the cloud computing environment. This architecture is also used to decide privileges for each type of user.

GETTING STUCK WITH SIMILAR SENG205 SOFTWARE ENGINEERING ASSIGNMENT? ENROL WITH EXPERTSMINDS'S SENG205 SOFTWARE ENGINEERING ASSIGNMENT HELP SERVICES AND GET DISTRESSED WITH YOUR ASSIGNMENT WORRIES!

Team description

The team that is responsible for development of UHR system involves 13 resources. Every resource is responsible for different operations. The project manager tops the entire ranking of the resources involved and is responsible for decision making and client communication activities. Senior software developer will supervise the resources in terms of design, development and testing. Under this resource, we have 1 creative artist, 1 front end developer and 2 backend developers. The database administrator shall also work closely with the backend developers to test functionalities and security of the developed system.

Since this is a huge system, we will be in need of 2 testers who can test the system for different use cases (Wu et al, 2015). Alternatively, these testers can either belong to our team or a real time resource like insurance service provider or medical consultant who will use the system in the near future. The user base for this system is vast and hence, we shall deploy 4 sources for support and query resolution. This is the project team for the development of this system. The chosen team members shall sign the contract that states legal obligations to be ensured before, during and after the project lifecycle so that confidential information remains private.

Project organization with organizational chart

The project is organized into 8 steps that will stretch for about 84 days. The organizational chart is given below.

Software Engineering Assignment2.png

This chart perhaps defines the communication structure and the authoritative nature of the organizational structure. Project manager only has the right to interact with the client while the rest of the members work based on the instructions. Further, the results achieved from each of the steps are submitted to the respective authority so that the project manager confirms the progress of the system. However, the database administrator and backend developer shall closely work due to large volumes of data and the need to ensure security, non-redundancy, reliability and quality of it before they are left for public to use.

Work activities based on model

The methodology used for this system is agile. According to this system, it encourages flexibility and guarantees cost-effectiveness. Unlike the waterfall model where one has to perform the activities step by step and one cannot bypass the steps in the middle, this agile methodology allows project team members to work on multiple tasks simultaneously. This approach actually saves time, money and efforts. Further, this flexibility exists even when Australian government plans to expand the infrastructure and add new functions.

Though the interdependency between the phases exists, the agile methodology is highly suitable for this system. Despite the number of iterations or changes suggested by the client, the method minimizes the wastage of resources and there is minimum risk. As a result, it is possible to improve decision making and satisfy the project sponsor or client involved. Based on this model, here is the set of work activities to be carried out.

Stage

Process/Work activities

1

Requirement gathering

2

Requirement analysis and technical and design documentation

3

Wireframe and prototype design

4

Coding

Increment 1: Frontend development

Increment 2: Backend development

Increment 3: System integration

5

Testing

Increment 1: Deployment and project signoff

Scheduled allocation

Task Name

Duration

Start

Finish

Predecessors

Resource Names

Requirement gathering

2 days

Sat 20-04-19

Mon 22-04-19


project manager

requirement analysis

3 days

Tue 23-04-19

Thu 25-04-19

1

project manager

Wireframe and prototype design

7 days

Fri 26-04-19

Mon 06-05-19

2

senior software developer,creative artist

frontend development

31 days

Tue 07-05-19

Tue 18-06-19

3

frontend developer

backend development

20 days

Wed 19-06-19

Tue 16-07-19

4

backend developer

system integration

5 days

Wed 17-07-19

Tue 23-07-19

5

database administrator,senior software developer

testing

14 days

Wed 24-07-19

Mon 12-08-19

6

Tester

deployment and project sign off

2 days

Tue 13-08-19

Wed 14-08-19

7

project manager,support

The allocation of tasks to the resources along with the duration for each of them is given in the table below. In this case, we have excluded all the weekends so that the resources work only on weekdays as per the laws of the country.

ORDER NEW COPY OF SENG205 SOFTWARE ENGINEERING ASSIGNMENT AND SECURE HIGHER MARKS!

Resource allocation

The involvement of each resource in this system development is portrayed as follows:

Software Engineering Assignment3.png

This is the resource statistics. On the other hand, we also have the essential data comprising of number of work hours spent by each resource and this is given below.

Name

Start

Finish

Remaining Work

project manager

Sat 20-04-19

Wed 14-08-19

56 hrs

senior software developer

Fri 26-04-19

Tue 23-07-19

96 hrs

creative artist

Fri 26-04-19

Mon 06-05-19

56 hrs

frontend developer

Tue 07-05-19

Tue 18-06-19

248 hrs

backend developer

Wed 19-06-19

Tue 16-07-19

160 hrs

database administrator

Wed 17-07-19

Tue 23-07-19

40 hrs

tester

Wed 24-07-19

Mon 12-08-19

112 hrs

support

Tue 13-08-19

Wed 14-08-19

16 hrs

The next aspect of this resource allocation is costing. The cost detail for each resource is given below.

Name

Standard Rate

project manager

$15/hr

senior software developer

$15/hr

creative artist

$10/hr

frontend developer

$10/hr

backend developer

$10/hr

database administrator

$10/hr

tester

$15/hr

support

$10/hr

To understand the amount spent towards each phase of the project, the graph is presented below.

Software Engineering Assignment4.png

In a total of $9160 excluding contingencies and research works towards system development, it is possible to complete this project in the time limit given above.

NEVER BE CAUGHT IN PLAGIARISM, AVAIL SENG205 SOFTWARE ENGINEERING ASSIGNMENT HELP SERVICE OF EXPERTSMINDS.COM AND SAVE HIGHER MARKS!

Risk management plan

The risk management plan for this project is established with the help of a risk matrix (PMI, 2010).

Risk

Implications

Risk level

Impact

Management

Delayed start of the project

Delayed completion of the phases

Compromise of quality

Reputational damage

Medium

High

Plan milestones and start in advance

Inform resources about impacts of delayed start

Ensure collaboration of resources

Data errors

Incorrect results

Client dissatisfaction

Low

High

Enable database resource to check quality whenever the backend developer updates data

Provide accurate documents

Operational overheads

Extra budgets involved

Need for allocation of more resources to complete within the stipulated time

Medium

High

Keep a note on the progress

Keep all the team members updated on issues encountered

Regular communication is the key

Gantt chart

Based on the resources involved, tasks and duration allocated to each phase of the project, the Gantt chart is created.

Software Engineering Assignment5.png

This Gantt chart is used to communicate with other resources during the development of the system. As seen in this Gantt chart, it keeps us informed about the schedule and resources allocated. It is clear that project manager has to intervene in most of the phases.

Flow chart

Software Engineering Assignment6.png

According to this diagram, there are 2 instances when conditions are imposed and the rest of them ensure a smooth workflow. Data sufficiency and integration status are the two instances when the project manager will have to engage in assessment of the activity flow by the resources involved in the project. The purpose of a flow chart is to understand how the workflow happens during the project lifecycle (Phillips, 2003). It is evident from this diagram that it happens step by step but there is still scope to alter the workflow since we have followed agile methodology for completion of the project.

System/component design

The overall system design for this project is given below.

Software Engineering Assignment7.png

During the implementation of this project, all the departments of Australian government assigned to this project will have access to the central server where the progress of the system shall be updated. Alternatively, there is a separate section for vendors and this vendor implies the infrastructure sought out and implemented for this UHR system. Throughout the lifecycle of this project development, we shall make use of Cisco routers to have remote access. During the testing phase, we shall have partners like consultants and insurance service providers who would offer their feedbacks towards the system.

EXPERTSMINDS.COM GIVES ACCOUNTABILITY OF YOUR TIME AND MONEY - AVAIL TOP RESULTS ORIGINATED SENG205 SOFTWARE ENGINEERING ASSIGNMENT HELP SERVICES AT BEST RATES!

Use case diagram

In this section, we shall detail about the use case for clinical module management.

Software Engineering Assignment8.png

Security is guaranteed in each step of this system and this use case confirms the same. The clinical record user will typically include a consultant/doctor who manages records and updates details pertaining to a specific patient.

Data flow diagram

At the level 0 of this system, the data flow is given as a snapshot below.

Software Engineering Assignment9.png

The administrator updates data of patients and patients get the opportunity to access their clinical histories and management plans to be followed. For the user to gain detailed information of their health issues and for the hospitals to enter bills and medical records as and when the patients visit the location, level 2 of patient record database is also created as follows.

Software Engineering Assignment10.png

This diagram once again gives an understanding about the patient's association with a hospital and present health status.

Relationship diagram

An example entity-relationship diagram for this system is mentioned below.

Software Engineering Assignment11.png

There are multiple internal stakeholders who will take care of updating patient's data. For instance, the receptionist keeps a note of the patient's appointment schedule. On the other hand, the system administrator makes a note of the patient's medical record and eliminates any data redundancies. Further, this administrator also ensures that the entire system is secured.

ENROL WITH SENG205 SOFTWARE ENGINEERING ASSIGNMENT HELP AND HOMEWORK WRITING SERVICES OF EXPERTSMINDS.COM AND GET BETTER RESULTS IN SENG205 SOFTWARE ENGINEERING ASSIGNMENTS!

Database design

Software Engineering Assignment12.png

This design is supposed to be the data storage and retrieval system followed to store the details of the patients. It includes all the basic categories of treatment and allows consultants to enter progress and medicines suggested. The diagram given here is said to be an overview of the patient database. This will be accessed by the insurance service providers and medical health professionals.

UI design

As already stated, the UHR system to be implemented for patients in Australia will have to be compatible on all the devices so that they can enjoy the overall experience and do not face constraints.

Here is the first look of the patient's record as displayed by the system.

Software Engineering Assignment13.png

On the left side, there is a range of options provided and the users can choose the ones available based on the access rights granted.

Conclusion

The idea of building an integrated health record system is definitely rewarding to the government and the healthcare industry. In this paper, it has been noticed that this project will involve about 13 resources from the project development team and the workflow and use cases given here make it clear that the team is ready to execute the objectives of the project with effective mitigation of risks.

24/7 AVAILABILITY OF TRUSTED SENG205 SOFTWARE ENGINEERING ASSIGNMENT WRITERS! ORDER ASSIGNMENTS FOR BETTER RESULTS!

Access our Top Quality Central Kent Institute Australia Assignment Help Service for Various Courses and Units, Such As -

  • CPRO303 Capstone Project Assignment Help
  • CLBE304 Cloud and Beyond Assignment Help
  • CARC103 Computer Architecture Assignment Help
  • CTEC104 Communications and Technology Assignment Help
  • DCAN202 Data Communication and Networking Assignment Help
  • DSAA204 Data Structure and Algorithms Assignment Help
  • DBFN212 Database Fundamentals Assignment Help
  • DWIN309 Developing Web Information Systems Assignment Help
  • ENSN201 Enterprise Social Networks Assignment Help
  • ITBO201 IT for Business Organisations Assignment Help
  • MGTP102 Management Principles Assignment Help
  • OODP101 Object-Oriented Design and Programming Assignment Help
  • PAQM321 Project & Quality Management Assignment Help
  • SYAD310 System Analysis and Design Assignment Help
  • TITP105 The IT Professional Assignment Help
  • WPDD202 Webpage Design and Development Assignment Help
Tag This :- EM1901ASH3005WR SENG205 Software Engineering Assignment Help

get assignment Quote

Assignment Samples

Get Academic Excellence with Best Skilled Tutor! Order Assignment Now! Submit Assignment