Business Analysis S1 2018 – Assignment 2 “Medigood” Case Study

This assignment focuses on the development of a new information system for Medigood. It covers work breakdown structure, to-be design activity, organizational change, screen design, acceptance criteria, applications architecture, report to user, and agile and waterfall differences.

Running head: BUSINESS ANALYSIS
Business Analysis S1 2018 – Assignment 2
“Medigood” Case Study
Student Name:
University Name:

1BUSINESS ANALYSIS ASSIGNMENT 2
Table of Contents
Task 2.01 Work Breakdown Structure............................................................................................2
Task 2.02 “To-be” design activity...................................................................................................3
Task 2.03 Organisational change.....................................................................................................3
Task 2.04 Screen design..................................................................................................................6
Task 2.05 Acceptance Criteria.........................................................................................................7
Task 2.06 Applications Architecture...............................................................................................9
Task 2.07 Report to User...............................................................................................................10
Task 2.08 Agile and Waterfall differences....................................................................................11
Bibliography..................................................................................................................................16
Appendix – Project Journal...........................................................................................................18

2BUSINESS ANALYSIS ASSIGNMENT 2
Task 2.01 Work Breakdown Structure
Activity Duration
Determining required activities for completion of the assignment 02 days
Developing the “To-be” process diagram according to requirement of Medigood 03 days
Illustrating the impact that new system will have on the Medigood business and
determining plan to manage organizational changes
05 days
Designing of two screen interfaces according to requirements of the users
determined from user stories
04 days
Defining the criteria for acceptance of the screen designs developed as per two
user stories
02 days
Demonstration of new system architecture with the help of application architecture
diagram
01 day
Preparation of executive summary to be included in user report with explanation
on the processes undertaken to select suitable supplier
03 days
Comparing Agile approach with Waterfall model and illustrating the advantages as
well as disadvantages of both the approaches
03 days

3BUSINESS ANALYSIS ASSIGNMENT 2
Task 2.02 “To-be” design activity
Task 2.03 Organisational change
Organizational change implies for all time adjusting examples of authoritative conduct.
Authoritative change is not about individual change, or making new associations. Along these
lines, authoritative change is centered on what is occurring inside existing associations, and
inside their surroundings. In spite of the way that change administration has been in presence for
over 50 years, one of the real difficulties stays to be the limit of chiefs to actualize change. As
change programs advance from characterizing technique and setting focuses to outline and
execution, these activities influence distinctive levels of the association. People are naturally

4BUSINESS ANALYSIS ASSIGNMENT 2
judicious and will question to what degree change is required, regardless of whether the
organization is going the correct way, and whether they need to confer actually to getting change
going.
Accordingly, the fundamental change demonstrate characterizes change as: for all time
modifying examples of conduct. There are two settings of conduct: individual and hierarchical.
The individual setting is impacted by training, age and identity. The authoritative setting is
impacted by structure, legislative issues and culture. In the present complex business condition,
change is constantly present. Focused weights, industry movements, and innovation interruptions
are just a couple of the components plotting toward change. The vulnerability of rearrangements
and rebuilding can hurt worker resolve and efficiency, particularly when redesigns and
restructurings are required. The business approach within Medigood has been examined and it is
perceived that new information structure will be productive for recording the data of patients and
furthermore specialists related in the methodology for accommodating treatment. There might be
season of misunderstandings as the present structure for securing records is manual and the
association is facing burden in overseeing game plans got from the patient’s adjacent finding
expert as indicated by the essential of patients. There is an essential of new information system
with the true objective that booking of strategies can be managed effectively to check availability
of medical specialist.
Further, the information system will assist Medigood with outfitting the patients with
telehealth gathering office so they can complete their treatment from remote zone and do not
need to visit the medical specialist physically every time they require any remedial controlling.
The new system will assist the patients with checking their prosperity with no other individual's
help and it will in like way help Medigood in compelling association of their business works out.

5BUSINESS ANALYSIS ASSIGNMENT 2
The structure will in like way reinforce furnishing the patients with definitive outcomes
remotely. The change and utilization of another information structure will insistently impact
business strategy of the connection. The change inside the association because of utilization of
the new structure must be managed gainfully with honest to goodness rolling out game plans for
improvement organization and plausible fundamental activity. The developments ought to be
made sense of how to such an extent, to the point that those remaining parts lines up with the
goals behind utilization of the new information structure. The new system will assist the
association with coming to more customers and increase their ability by growing adaptability of
the present structure.

6BUSINESS ANALYSIS ASSIGNMENT 2
Task 2.04 Screen design
Login/Signup
Functionalities

7BUSINESS ANALYSIS ASSIGNMENT 2
Task 2.05 Acceptance Criteria
User Stories are short conversational writings that are utilized for introductory necessities
revelation and project arranging. User stories are generally utilized as a part of conjunction with
agile programming advancement project administration techniques for Release Planning and
meaning of User Acceptance Criteria for programming improvement projects. User Goals,
expressed as User Stories, are more firmly lined up with Business Priorities than programming
improvement undertakings, thus it is the User Story organize which wins in composed
explanations of User Acceptance Criteria. An Agile Project Team is normally situated to
finishing and conveying User-esteemed Features as opposed to on finishing confined
advancement assignments. These improvement Tasks in the end join into a User-esteemed
Feature. A User Goal is an end condition, though an improvement Task is a middle of the road
procedure expected to accomplish this User Goal. User stories shape the premise of User
Acceptance Testing.
Acknowledgment tests can be made to check that the User Story has been accurately
actualized. The affirmation of the new information system will interminable supply of the
customer necessities and use of appropriate programming movement structure. The system will
be recognized if the movement strategy being taken after is as indicated by the fitting
programming change rationale. The enormous insistence criteria for the new structure to help
Medigood relies on the UI proposes the outline ought to be something besides difficult to use
with the genuine target that the users do not lose their vitality over the system. The UI is
considered as the middle person that cooperates with a structure so it must be anything besides
hard to use to such an extent, to the point that the users wear not feel inconsistency in utilizing
the system. The new system must be made in such a course, to the point that it meets required

8BUSINESS ANALYSIS ASSIGNMENT 2
functionalities of the users and besides the customer. The introduction of the system must be laid
out in a sensible structure so the users can without a considerable amount of hassle pick the
breaking points performed by the specific modules inside the structure.
The structure must be executed with proper security tries as record of patient and besides
other essential data will be secured through the system. The structure change must be done by
keep up the quality measures with the target that the users are fulfilled while utilizing the system.
The structure must be tried utilizing unit testing and for checking the supportiveness, solace,
common sense and ardent quality with the genuine target that the system mirrors a positive
impression amidst user insistence testing. The presence of mind close-by versatility tests must be
upgraded the condition the system with the target that quality is kept up and the customer is
guaranteed about the institutionalized thing. The structure ought to be executed with appropriate
endorsement and security tries as there will be farthest point of individual data and moreover
trade of data. The records of the patient can be gotten to by the authority in any case other
patients will not have the ability to see the information.

9BUSINESS ANALYSIS ASSIGNMENT 2
Task 2.06 Applications Architecture
In the above diagram layout of the system is conveyed for Medigood so the present
business shapes and existing structure inside the alliance can be pushed ahead. The blueprint
outline is made resulting to taking a look at the modules that must be conveyed for the
information system. The information system will incorporate generally two modules that is one
for organization of patients and the other for legitimate parts of the alliance. The patient

10BUSINESS ANALYSIS ASSIGNMENT 2
association structure identifies with securing, controlling and recovery of patient record. The
administrative module will investigate the association related data set away with the structure.
The database for both the modules will be isolated with the target that restore and support
information can be done effectively in the event of any disappointment. The association module
will in like way empower preparing of information from outer sources, for example, information
on clinical associations being offered to the patients.
Task 2.07 Report to User
In this report, the attention is on portraying the frameworks that has been attempted to
settle on a choice to build up the data structure. The favored decision for working up the
proposed data framework is that In-House designers will be given contract and the structure will
be made with the joint effort of Medigood. The present business approach of Medigood has been
analyzed to pick necessities of the assistants related with the connection. The new framework is
being proposed for interfacing patients with the specialists and in like manner giving therapeutic
guidance to the patients so they do not need to visit the recovering concentration or office
physically every time they require a gathering.
The Waterfall technique has been chosen for movement of the new framework as the
necessities have been unmistakably perceived and it would decrease the time required for
working up the structure. The affirmation of a legitimate provider is vital for convincing progress
of a data framework as the acquirement of required materials on time and with unprecedented
quality will guarantee accomplishment of the structure. The structure will be conveyed by rolling
out an in-house improvement assembling and to such an extent, to the point that it lines up with
the business basics. The adjustments in necessities can be overseen while following the spry
framework yet if there should be an occurrence of waterfall approach the developments cannot

11BUSINESS ANALYSIS ASSIGNMENT 2
be gotten a handle on and the entire structure must be disposed of and it must be begun before
long to achieve the pined for targets.
Task 2.08 Agile and Waterfall differences
There are diverse techniques that can be executed for advancement of frameworks yet the
choice of procedure relies upon the kind of framework to be produced. Both undertaking
administration approaches are similarly comparable to each other. It is simply the undertaking
write which should drive which procedure is utilized. There are numerous focal points and
drawbacks of both methodologies.
Waterfall is an organized stage by arrange consecutive approach where every specific
piece of work to finish the activity is done in stages. When one stage completes, the task at that
point moves onto the following stage. The quantity of stages changes as indicated by the specific
Waterfall system. Waterfall is an approach to project management that uses a predictive model
of risk control. Everything hinges on making good predictions. That is why waterfall uses a long
requirements gather phase up front. If all the requirements can be identified up front and they
truly do not change, waterfall can work.
Pros of Waterfall approach:
 Easy advances or in reverse arranging and execution.
 Tangible yield toward the finish of each stage - This produces better visibility to
others and gives a standard to push ahead and in addition provides food for a
consecutive subsidizing model (Serrador and Pinto 2015).
 Ability to outwardly observe and convey an objective conveyance or end date in
view of degree concurred.

12BUSINESS ANALYSIS ASSIGNMENT 2
 Estimate clear due dates: Waterfall's predictable work process approach makes it
easy to assess expenses and gauge courses of events.
 Well-sorted out process: As each advancement stage is clear with a begin point
and a settled assessment process, the undertaking group finishes all the
characterized assignments to continue the entire project.
 Well reported: As each stage requires legitimate documentation, it is anything but
difficult to utilize the rationale of prior projects and furthermore make a solid base
for future activities.
 Clear project refreshes: Foreseeable courses of events and very much archived
projects makes it easy to give notices to all the task partners including clients.
Cons of Waterfall approach:
 Change - Change in extension can truly affect time, cost and quality.
 If undertakings are not done appropriately in each stage and basically
distinguished at a later stage, the whole task can be seriously affected (Mitsuyuki
et al. 2017).
 Dependencies - If the project has inward or outer conditions (key asset, outside
project(s) and so forth), deferrals can happen as the "plan" has just been
composed.
 Modifications can be costly: The significant deficiency is Waterfall's rigidity to
oversee change. Testing is executed late in the project life cycle, and on the off
chance end clients do not care for the item being developed, at that point it can be
past the point where it is possible to hold upgrades.

13BUSINESS ANALYSIS ASSIGNMENT 2
 Sluggish conveyance times: It needs four periods of advancement to be proficient
before any coding starts, which implies partners and clients cannot see a working
item until the point when late in the undertaking life cycle.
 Assembling prerequisites too soon can be sketchy: Users and partners regularly
do not comprehend what they really need until the point that they have had a
choice to play with a working item show. In any case, as the Waterfall
demonstrate deals with all the undertaking necessity assembling ahead of
schedule in the task life cycle, there is dependably a substantial hazard down the
project line.
 Testing can be dangerous: Keeping all the testing exercises at last can be unsafe.
It can prompt an awful undertaking dispatch if not oversaw well.
Agile is an iterative kind approach where stages expected to finish a task are for the most
part done in parallel together. There are numerous light-footed systems yet each successfully has
the same observational structure where tasks are separated into little arranging cycles.
Prerequisites and arrangements are consistently advancing and in view of need and train. Agile
methods generally encourage us to observe reality and change our plans to match what we learn
from reality. When we discover something, we have the opportunity to learn from it or recover
from it. Agile methods generally encourage us to continually challenge our assumptions. This
relates directly to the previous point. In this case, the “something” discovered is that an incorrect
assumption has been made or that the context around us has changed in a way to invalidate the
previously correct assumption. It is discovered when still there is a chance to learn form or
recover from it.

14BUSINESS ANALYSIS ASSIGNMENT 2
Unrelated, Agile methods generally encourages to treat the people in project communities
as people. They recognize the social aspects of working together and it encourages to accept the
human nature, rather than try to drive that human nature out of the work. It also encourages to
accept uncertainty. Instead of trying to turn us into predictable machines, agile methods
generally encourage us to build work systems and social systems that accept our inherent
unpredictability. People tend to feel better about working in environments like this, so they bring
more energy to the work and they can sustain that energy better over time.
Pros of Agile approach:
 Change - Requirements are regularly advancing so change can be provided food
for effortlessly given the shorter arranging cycles.
 Encourages dynamic contribution and collaboration from key undertaking
partners which takes into account item fabricate in light of need and exactness.
Consistent 'show and tell' sessions consider item understanding (Mitsuyuki et al.
2017).
 Team connection - Constant group contribution and organized correspondence
stations take into account the revelation of advance, hindrances and joint effort.
 Continuous change that lessons are learnt from and at last used to better the
following cycles.
 Flexibility: The chief advantage light-footed improvement offers to organizations
is its adaptability to change. Clients get quicker answers for their issues in light of
its need. Partners can arrange required expectations continuously.

15BUSINESS ANALYSIS ASSIGNMENT 2
 Predict cost and time: As each dash is of a settled time term, the task cost and
time is anything but difficult to anticipate and identifying with the status of work
finished.
 Emphases on business esteem: With client controlling the need of highlights, the
improvement group comprehends what is critical to the client's business and can
convey the highlights in like manner.
 Focus on client esteem and quality work: Focusing on highlights encourages to
satisfy the requirements of real clients. Each component conveys esteem and is
not only a product component. Additionally, by partitioning the project into
reasonable units, it gives quality advancement, testing and cooperation.
Cons of Agile approach:
 Planning (target conveyance date) can be now and then be questionable.
 Business portrayal - Time and endeavors will be persistently required from item
assets. This is critical to cycle arranging and achievement (Serrador and Pinto
2015).
 External Stakeholder purchase in - Given its interesting and elective approach,
once in a while opposition is basic so preparing and training is required (at times
to a wide group of onlookers).
 Team individuals must be very talented/cross gifted in abilities as center groups
are little. They should likewise be up-gifted on the lithe structure picked.
 Difficulty in characterizing project scope: There are troubles looked in
characterizing the task scope as there is substantially less consistency at the

16BUSINESS ANALYSIS ASSIGNMENT 2
underlying stages. This makes it intense to characterize extends financially,
particularly when taking care of settled value projects.
 Testing is required all through the task: Testers are required all through the
project lifecycle and this effects the asset cost definitely.
 Lastly, normal input is that agile advancement is moderately thorough for
specialized groups. The need to build up each element inside every emphasis and
the power of keeping up various cycles is comprehensive and lessens the speed of
the task.

17BUSINESS ANALYSIS ASSIGNMENT 2
Bibliography
Fleisher, C. S. and 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. and Page, M. J., 2015. Essentials of
business research methods. Routledge.
Hajri, I., Goknil, A. and Briand, L., 2017. A change management approach in product lines for
use case-driven development and testing. In 23rd International Working Conference on
Requirements Engineering: Foundation for software Quality (REFSQ 2017).
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.
Khan, A.S., Oracle America Inc, 2016. System and method for automatically generating XML
schema for validating XML input documents. U.S. Patent 9,286,275.
Kvedar, J., Coye, M.J. and Everett, W., 2014. Connected health: a review of technologies and
strategies to improve patient care with telemedicine and telehealth. Health Affairs, 33(2), pp.194-
199.

18BUSINESS ANALYSIS ASSIGNMENT 2
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.
Nelson, R. and Staggers, N., 2016. Health Informatics-E-Book: An Interprofessional Approach.
Elsevier Health Sciences.
Satzinger, J.W., Jackson, R.B. and Burd, S.D., 2011. Systems analysis and design in a changing
world. Cengage learning.
Scott, R.E. and Mars, M., 2015. Telehealth in the developing world: current status and future
prospects. Smart Homecare Technol Telehealth, 3, pp.25-37.
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.

19BUSINESS ANALYSIS ASSIGNMENT 2
Appendix – Project Journal
Number Date Activity Explanation Status
1 25/04/201
8
Determining required
activities for completion
of the assignment
This task included setting up the
Work breakdown structure to
finish the assignment.
Completed
2 27/04/201
8
Developing the “To-be”
process diagram
This task relates to designing of
“To-be” process diagram
according to requirement of
Medigood.
Completed
3 01/05/201
8
Illustrating the impact
that new system will
have on the Medigood
business
This task involved illustrating the
impact that new system will have
on the Medigood business and
determining plan to manage
organizational changes.
Completed
4 06/05/201
8
Designing of two screen
interfaces according to
requirements of the
users
This task comprised of designing
two screen interfaces according to
requirements of the users
determined from user stories.
Completed
5 08/05/201
8
Defining the criteria for
acceptance of the screen
designs
This activity involved defining
the criteria for acceptance of the
screen designs developed as per
two user stories.
Completed

20BUSINESS ANALYSIS ASSIGNMENT 2
6 09/05/201
8
Demonstration of new
system architecture with
the help of application
architecture diagram
This activity comprised of
demonstrating new system
architecture with the help of
application architecture diagram.
Completed
7 13/05/201
8
Preparation of executive
summary to be included
in user report
This activity involved preparation
of executive summary to be
included in user report with
explanation on the processes
undertaken to select suitable
supplier.
Completed
8 17/05/201
8
Comparing Agile
approach with Waterfall
model
This activity relates to comparing
Agile approach with Waterfall
model and illustrating the
advantages as well as
disadvantages of both the
approaches.
Completed