Business Analysis of Medigood

Running head: BUSINESS ANALYSIS
Business Analysis S1 2018 – Assignment 2
“Medigood” National Health Insurance System
Student Name:
University Name:

1BUSINESS ANALYSIS ASSIGNMENT 2
Table of Contents
Task 2.02 “To-be” design activity...................................................................................................2
Task 2.03 Organisational change.....................................................................................................2
Task 2.04 Screen design..................................................................................................................4
Task 2.05 Acceptance Criteria.........................................................................................................5
Task 2.06 Applications Architecture...............................................................................................6
Task 2.07 Report to Client...............................................................................................................7
Task 2.08 Agile and Waterfall differences......................................................................................7
Bibliography..................................................................................................................................10

2BUSINESS ANALYSIS ASSIGNMENT 2
Task 2.02 “To-be” design activity
Task 2.03 Organisational change
The business policy existing within Medigood has been analyzed and it is identified that a
new information system will be beneficial for recording the information of patients as well as
doctors who will be associated in the procedure for medical treatment. There may be generation

3BUSINESS ANALYSIS ASSIGNMENT 2
of errors as the existing system for storing records is manual and the management is facing
difficulty in managing appointment requests received from the patients along with finding
suitable specialists. A new information system is required such the booking of appointments can
be handled efficiently only after checking the availability of specialists.
Further, the new information system will help Medigood to provide the patients with
telehealth consultation facility so that they can get their treatment done from remote location and
do not have to visit the specialists physically every time they require any medical consultation.
The new system will help the patients to keep track of their health by themselves only and it will
also help Medigood in effective management of their business processes. The system will also
support providing the patients with diagnostic results remotely. The development and
implementation of a new information system will have a positive impact on business processes
of the organization. The change within the organization due to implementation of the new system
have to be handled efficiently with proper change management planning and effective decision
making. The changes should be managed such that those remains aligned with the objectives
behind implementation of the new information system. The new system will help the
organization to reach to more clients and increase their capacity by expanding scalability of the
existing system.

4BUSINESS ANALYSIS ASSIGNMENT 2
Task 2.04 Screen design
New User (Appointment Booking)
Available Specialists

5BUSINESS ANALYSIS ASSIGNMENT 2
Task 2.05 Acceptance Criteria
The acceptance of the new information system will depend on fulfillment of the client
requirements and application of suitable software development methodology. The system will be
accepted if the development process being followed is in accordance with the appropriate
software development methodology. The major acceptance criteria for the new system to support
Medigood depends on the user interface means the design should be easy to use such that the
users do not lose their interest over the system. The user interface is considered as the mediator
that helps to interact with a system so it has to be user friendly such that the users don not feel
complexity in using the system. The new system have to be developed in such a manner that it
meets required functionalities of the users as well as the client. The presentation of the system
have to be designed in a suitable structure so that the users can easily determine the functions
performed by the different modules within the system.

6BUSINESS ANALYSIS ASSIGNMENT 2
The system have to be implemented with appropriate security measures as record of
patient as well as other vital information will be stored through the system. The system
development have to be carried out by maintain the quality standards so that the users are
satisfied while using the system. The system have to be tested using unit testing and for checking
the functionality, usability, efficacy and reliability such that the system reflects a positive
impression during user acceptance testing. The maintainability along with portability tests have
to be done for the system so that quality is maintained and the client is ensured about the
standardized product. The system should be implemented with proper authentication and security
measures as there will be storage of personal information as well as interchange of information.
The records of the patient can be accessed by the administrator but it will not be visible to other
patients.

7BUSINESS ANALYSIS ASSIGNMENT 2
Task 2.06 Applications Architecture
The above diagram represents architecture of the system to be developed for Medigood
so that the current business processes and existing system within the organization can be
improved. The architecture diagram is developed after analysing the modules that have to be
developed for the information system. The information system will comprise of mainly tow
modules that is one for patient management and the other for managerial aspects of the
organization. The patient management system relates to storing, manipulating and retrieval of
patient record. The managerial module will look into the management related information stored
with the system. The database for both the modules will be separated so that data backup and
recovery can be carried out easily in case of any failure. The management module will also

8BUSINESS ANALYSIS ASSIGNMENT 2
facilitate processing of data from external sources such as data on clinical services being offered
to the patients.
Task 2.07 Report to Client
This report is focused on describing the processes that has been undertaken to make a
decision to develop the information system. The preferred choice for developing the new
information system is In-House development means developers will be hired and the system will
be developed with the collaboration of Medigood. The present business policy of Medigood has
been analyzed to determine requirements of the stakeholders associated with the organization.
The new system is being proposed for connecting patients with the specialists as well as
providing medical consultation to the patients so that they do not have to visit the hospital or
clinic physically every time they need a consultation.
The Waterfall method has been selected for development of the new system as the
requirements have been clearly identified and it would reduce the time required for developing
the system. The selection of a suitable supplier is essential for successful development of an
information system as the procurement of required materials on time and with good quality will
ensure success of the system. The system will be developed by creating an in-house development
team and such that it aligns with the business requirements. The changes in requirements can be
managed while following the agile methodology but in case of waterfall methodology the
changes cannot be adopted and the whole system have to be discarded and it has to be started
over again to accomplish the desired goals.

9BUSINESS ANALYSIS ASSIGNMENT 2
Task 2.08 Agile and Waterfall differences
There are various methodologies that can be implemented for software development
however different approaches are associated with the different software development
methodologies. The traditional waterfall model is defined as the most primitive methodology ad
it is being widely used for development of systems. The Agile methodology is also being now a
days used by various organizations for developing software products. The major differences
between the Agile and Waterfall methodology is illustrated as below:
Waterfall model
Pros
 Waterfall model is easy, simple and easily understandable from the developers end
 All phases of the waterfall methodologies are clearly documented and can be
implemented singly
 It gives high level of visibility to the developers
 The phases are individually developed thus, the consumers engagement are not needed in
the later phases
 This approach offers clear control over the deadline as soon as the work is being
distribute
Cons
 This model is no flexible due to its rigidness during the development phase no
requirements can be easily changed
 Within the phases, the progress cannot be easily identified
 The usage of this model is quite expensive than the others

10BUSINESS ANALYSIS ASSIGNMENT 2
 The challenges, issues, bottlenecks can be identified at the end of the development cycle
and not in progress period
 If the project assumptions are found to be wrong then, the estimated completion time may
exceed and the project may fail to meet the expected deadline
Agile model
Pros
 Agile methodology is much focused on the team collaboration. There will be no presence
of any kind of rouge elements that may lead a project towards failure.
 Through the help of this methodology a software development become much easier and
quicker than others. Even for repeating business occurrence this methodology is helpful.
 For managing cost though this stands easier. Small businesses can easily afford this
approach.
 The clients can examine the progress and it also offers suggestion in each step.
Cons
 The cost needed for the development of the software is not at predictable each time
 This methodology is difficult to understand only for large project this is suitable and
small projects are not supported through this methodology
 The timing for this approach is little problematic
 Through this methodology software can be implemented successfully only if, clients
make all the resources available

11BUSINESS ANALYSIS ASSIGNMENT 2

12BUSINESS ANALYSIS ASSIGNMENT 2
Bibliography
Ashmore, S., Townsend, A., DeMarie, S. and Mennecke, B., 2018. An exploratory examination
of modes of interaction and work in waterfall and agile teams. International Journal of Agile
Systems and Management, 11(1), pp.67-102.
De Thurah, A., Stengaard‐Pedersen, K., Axelsen, M., Fredberg, U., Schougaard, L.M., Hjollund,
N.H., Pfeiffer‐Jensen, M., Laurberg, T.B., Tarp, U., Lomborg, K. and Maribo, T., 2018. Tele‐
Health Followup Strategy for Tight Control of Disease Activity in Rheumatoid Arthritis: Results
of a Randomized Controlled Trial. Arthritis care & research, 70(3), pp.353-360.
Fleisher, C. S., & Bensoussan, B. E. (2015). Business and competitive analysis: effective
application of new and classic methods. FT Press.
Goetsch, D.L. and Davis, S.B., 2014. Quality management for organizational excellence. Upper
Saddle River, NJ: pearson.
Gollenia, L.A., 2016. Business transformation management methodology. Routledge.
Greenhalgh, T., Procter, R., Wherton, J., Sugarhood, P., Hinder, S. and Rouncefield, M., 2015.
What is quality in assisted living technology? The ARCHIE framework for effective telehealth
and telecare services. BMC medicine, 13(1), p.91.
Hair Jr, J. F., Wolfinbarger, M., Money, A. H., Samouel, P., & Page, M. J. (2015). Essentials of
business research methods. Routledge.
Hall, J.L. and McGraw, D., 2014. For telehealth to succeed, privacy and security risks must be
identified and addressed. Health Affairs, 33(2), pp.216-221.

13BUSINESS ANALYSIS ASSIGNMENT 2
Hiekata, K., Mitsuyuki, T., Goto, T. and Moser, B.R., 2016, October. Design of Software
Development Architecture Comparison of Waterfall and Agile Using Reliability Growth Model.
In ISPE TE (pp. 471-480).
Hornstein, H.A., 2015. The integration of project management and organizational change
management is now a necessity. International Journal of Project Management, 33(2), pp.291-
298.
Kanaane, R., Akabane, G., Peterossi, H. and Endler, D.C.N., 2015. Organizational change
management in a strategic perspective. American Journal of Management, 15(2), p.88.
Kaufman, H., 2017. The limits of organizational change. Routledge.
Komai, S., Saidi, H. and Nakanishi, H., 2016. Man-Hour Comparison Between Two Methods of
Agile and Waterfall in IT System Development. INNOVATION AND MANAGEMENT,
p.1707.
Mahadevan, L., Kettinger, W.J. and Meservy, T.O., 2015. Running on Hybrid: Control Changes
when Introducing an Agile Methodology in a Traditional" Waterfall" System Development
Environment. CAIS, 36, p.5.
Mitsuyuki, T., Hiekata, K., Goto, T. and Moser, B., 2017. Evaluation of Project Architecture in
Software Development Mixing Waterfall and Agile by Using Process Simulation. Journal of
Industrial Integration and Management, 2(02), p.1750007.
Serrador, P. and Pinto, J.K., 2015. Does Agile work?—A quantitative analysis of agile project
success. International Journal of Project Management, 33(5), pp.1040-1051.

14BUSINESS ANALYSIS ASSIGNMENT 2
Steinke, G.H., Al-Deen, M.S. and LaBrie, R.C., 2017. NNOVATING INFORMATION
SYSTEM DEVELOPMENT METHODOLOGIES WITH DESIGN THINKING. In Proceedings
of the 5th International Conference on Applied Innovations in IT (pp. 51-55).
Vijayasarathy, L.R. and Butler, C.W., 2016. Choice of software development methodologies: Do
organizational, project, and team characteristics matter?. IEEE Software, 33(5), pp.86-94.