Assignment: Analysis and Design of Business Systems

ASSIGNMENT
ANALYSIS AND DESIGN OF BUSINESS

SYSTEMS
DR. RITU VASHISHTH MAM
ANS 1.
(A) The systems development life cycle, in its variant forms, remains
one of the oldest and yet still widely used methods of software
development and acquisition methods in the information technology (IT)
arena. While it has evolved over the years in response to ever-changing
scenarios and paradigm shifts pertaining to thebuilding or acquiring of
software, its central tenants are as applicable today as they ever were.
Life-cycle stages have gone through iterations of different names and
number of steps, but at the core the SDLC is resilient in its tried-and-true
deployment in business, industry, and government. In fact, the SDLC has
been called one of the two dominant systems development
methodologies today, along with prototyping (Piccoli, 2012). Thus,
learning about the SDLC remains important to the students of today as well
as tomorrow.This paper describes the use of the SDLC in a real-world heath
care setting involving a principle component of a regional hospital care
facility. The paper can be used as a pedagogical tool in a systems analysis
and design course, or in an upper-division or graduate course as a case
study of the implementation of the SDLC in practice. First, a review of the
SDLC is provided, followed by a description of the case study
environment. Next, the application of the methodology is described
indetail. Following, inferences and observations from the project are
presented, along with lessons learned. Finally, the paper concludes
with implications for the three areas of research, practice, and
pedagogy, as well as suggestions for future research.
(B) The SDLC has been a part of the IT community since the inception
of the modern digital computer. A course in Systems Analysis and
Design is requisite in most Management Information Systems programs
(Topi, Valacich, Wright,Kaiser, Nunamaker, Sipior, and de Vreede, 2010).
While such classes offer an overview of many different means of developing
or acquiring software (e.g., prototyping, extreme programming, rapid
application development (RAD), joint application development (JAD),
etc.), at their heart such programs still devote a considerable amount
of time to the SDLC, as they should. As this paper will show, following the
steps and stages of the methodology is still a valid method of insuring the
successful deployment of software. While the SDLC, and systems analysis
and design in general, has evolved over the years, at its heart it remains a
robust methodology for developing software and systems.Early treatises of
the SDLC promoted the rigorous delineation of necessary steps to
follow for any kind of software project. The Waterfall Model (Boehm,
1976) is one of the most well-known forms. In this classic representation,
the methodology involves seven sequential steps: 1) System Requirements
and Validation; 2) Software Requirements and Validation; 3)
Preliminary Design and Validation; 4) Detailed Design and Validation; 5)
Code, Debug, Deployment, and Test; 6) Test, Preoperations, Validation
Test; and 7) Operations, Maintenance, Revalidation. In the original
description of the Boehm-Waterfall software engineering methodology,
there is an interactive backstep between each stage. Thus the Boehm-
Waterfall is a combination of a sequential methodology with an
interactive backstep (Burback, 2004).
ANS 2.
(A) The first step in the Systems Development Life Cycle is the Problem
Definition component of the Analysis phase. One would be hard-pressed to
offer a solution to a problem that was not fully defined. The Home Health
portion of General Hospital had been reorganized as a separate, subsidiary
unit located near the main hospital in its own standalone facility.
Furthermore, the software they were using was at least seven years old and
could simply not keep up with all the changes in billing practices and
Medicare requirements and payments. The current system was not scalable
to the growing needs and transformation within the environment. Thus, in
addition to specific desirable criteria of the chosen software (described in
the following section), our explicit purpose in helping General was twofold:
1) to modernize their operations with current technology; and 2) to provide
the best patient care available to their clients in the Home Health arena. A
precursor to the Analysis stage, often mentioned in textbooks (e.g.,
Valacich, George, and Hoffer, 2009) and of great importance in a practical
setting, is the Feasibility Study. This preface to the beginning of the Analysis
phase is oftentimes broken down into three areas of feasibility: 
Technical (Do we have the necessary resources and infrastructure to
support the software if it is acquired?)  Economic (Do we have the
financial resources to pay for it, including support and maintenance?) 
Operational (Do we have properly trained individuals who can operate and
use the software.
(B) The author, having taught the SAD course many times, recognized from
the outset that this particular project would indeed follow the stages of the
traditional SDLC. While we would not be responsible for some of the steps
(e.g., testing, and training of staff), we would follow many of the others in a
lockstep fashion, thus, the task was an adaptation of the SDLC (i.e., a
software acquisition project) as opposed to a software development project
involving all the stages. For students, it is important to see that they benefit
from understanding that the core ideas of the SDLC can be adapted to fit a
“buy” (rather than “make”) situation. Their knowledge of the SDLC can be
applied to a non-development context. The systematic approach is
adaptable, which makes the knowledge more valuable. In this project, we
used a modified version of the SDLC that corresponds to the form
advocated by McMurtrey (1997). Consequently, we proceed in this
monograph in the same fashion that the project was presented to us: step
by step in line with the SDLC.
ANS 3. The principle investigators arranged another meeting with the

primary stakeholders of General
Hospital’s Home Health division. After all, although we had done the
research, they were the
ones that would be using the system for the foreseeable future. As such, it
only made sense that
they be heavily involved. This is in line with what is put forth in systems
analysis and design
textbooks: user involvement is a key component to system success. Having
carefully reviewed
our research notes, in addition to the various brochures, websites,
proposals, communications,
and related documents from each of our shortlist of five vendors, together
as a group we made our
decision. We would invite Vendor B for a site visit and demonstration.
Vendor B was very professional, courteous, prompt, and conscientious
during their visit. One
thing that greatly supported their case was that their primary business
model focused on Home
Health software. It was, and still is, their core competency. In contrast, one
other vendor (not on
our original short list of five) came and made a very polished presentation,
in the words of the
Director. However, this company was a multi-billion dollar concern, of which
Home Health
software was only a small part. Thus the choice was made to go with
Vendor B.
Ironically, this seller’s product was not Meditech compatible, which was one
of the most
important criteria for selection. However, through the use of a middleware
company that had
considerable experience in designing interfaces to be used in a Meditech
environment, a suitable
arrangement was made and a customized solution was developed and put
into use. The
middleware vendor had done business with General before and, therefore,
was familiar with their
needs.
ANS 4. As the post I can get of manager firstly I will analyse and understand
all the problems that can come in the company. from one problem company
apply the rule of SDLC in the company so that all the employee and financial
problems of company will be sought out by this act. and as a manager i can
clear about my decision making skills and after sought out this problem, the
manager should carefull that such problems cant come in organisation
again.

Assignment: Analysis and Design of Business Systems

Uploaded by

Copyright:

Available Formats

Assignment: Analysis and Design of Business Systems

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Assignment: Analysis and Design of Business Systems

Uploaded by

Copyright:

Available Formats

ASSIGNMENT

ANALYSIS AND DESIGN OF BUSINESS

ANS 3. The principle investigators arranged another meeting with the

You might also like