Question

As a systems analyst you are leading a project to identify improvements for the current R-ADT system. The primary uses of the system include patient scheduling, patient admitting, HIM, case management, and nursing.

Explain what options you have for conducting the requirements analysis, identify which of these you would choose to use and why, and then describe in detail the process you would follow.

**When they say identify which of these you would chose it is referring to these:

System Initiation

Requirements Analysis

System Design

System Construction

System Acceptance

System Implementatio

Answer 1

System Initiation

A phase in the data system life cycle which includes, documentation of the system goals and the process that will be used for creating and implementing a technical solution to meet those goals.

Requirements Analysis

requirements analysis encompasses those tasks that go into determining the needs or conditions to meet for a new or altered product or project, taking account of the possibly conflicting requirements of the various stakeholders, analyzing, documenting, validating and managing software or system requirements.^[2]

Requirements analysis is critical to the success or failure of a systems or software project.^[3] The requirements should be documented, actionable, measurable, testable, traceable, related to identified business needs or opportunities, and defined to a level of detail sufficient for system design.

Requirements Analysis is the process of defining the expectations of the users for an application that is to be built or modified. Requirements analysis involves all the tasks that are conducted to identify the needs of different stakeholders. Therefore requirements analysis means to analyze, document, validate and manage software or system requirements. High-quality requirements are documented, actionable, measurable, testable, traceable, helps to identify business opportunities, and are defined to a facilitate system design.

Eliciting requirements

The process of gathering requirements by communicating with the customers is known as eliciting requirements.

Analyzing requirements

This step helps to determine the quality of the requirements. It involves identifying whether the requirements are unclear, incomplete, ambiguous, and contradictory. These issues resolved before moving to the next step.

Requirements modeling

In Requirements modeling, the requirements are usually documented in different formats such as use cases, user stories, natural-language documents, or process specification.

Review and retrospective

This step is conducted to reflect on the previous iterations of requirements gathering in a bid to make improvements in the process going forward.

Systems design is the process of defining the architecture, modules, interfaces, and data for a system to satisfy specified requirements. Systems design could be seen as the application of systems theory to product development. There is some overlap with the disciplines of systems analysis, systems architecture and systems engineering

System Construction

Explain the purpose of the construction and implementation phases of the systems life cycle.Describe the systems construction and implementation phases in terms of your information building blocks.Describe the systems construction implementation phases in terms of major tasks, roles, inputs and outputs.Explain several application program and system tests.Identify several system conversion strategies.Identify those chapters in this textbook that can help you actually perform the tasks of systems construction and implementation.No additional notes.Chapter 19 – System Construction and Implementation

Using all our skill and experience the technical team will work closely with you to develop and create the perfect solution.

Our ability to understand and appreciate the fine details of the tray sealing process from start to finish ensures the result

Construction and delivery of Mondini systems are to the highest design, engineering and hygiene standards exceeding regulatory requirements

System Acceptance

System Acceptance is the point in the lifecycle at which every aspect of the application being developed, along with any supporting data conversion routines and system utilities, are thoroughly validated by the Customer Representatives prior to proceeding with System Implementation. This entire phase is centered around gaining sufficient evidence of the system’s accuracy and functionality to be able to proceed to System Implementation with the highest level of confidence possible in the success of the system. This phase differs from System Construction in that acceptance testing is the final opportunity to establish that the system performs as expected in an environment that mimics production as closely as possible. In addition, while the Customer Representatives were certainly engaged throughout prior testing efforts, they now assume an even more critical role in the testing efforts in that they now need to exercise the system in the same way that they will once the full system is implemented. With the testing roadmap established in earlier lifecycle phases, the Customer Representatives now take responsibility for maneuvering the system through its operations. In addition to confirming the operation of the system and its fit to the business needs that it is intended to satisfy, System Acceptance is also the point in the lifecycle during which all supporting documentation and reference materials are updated to guarantee their consistency with the final delivered system

System Implementation

Systems implementation is the process of:

1. defining how the information system should be built (i.e., physical system design),
2. ensuring that the information system is operational and used,
3. ensuring that the information system meets quality standard (i.e., quality assurance).