INCEPTION-Artifacts with the case study on Medical

Transcription and Billing Software Product.

An Introduction to INCEPTION Phase :
The goal of the inception phase is to achieve concurrence among all stakeholders on the lifecycle objectives for the project. The inception phase is of significance primarily for new development efforts, in which there are significant business and requirements risks which must be addressed before the project can proceed. For projects focused on enhancements to an existing system, the inception phase is more brief, but is still focused on ensuring that the project is both worth doing and possible to do. The primary objectives of the inception phase include:

Establishing the project's software scope and boundary conditions, including an operational vision, acceptance criteria and what is intended to be in the product and what is not. Discriminating the critical use cases of the system, the primary scenarios of operation that will drive the major design trade-offs. Estimating the overall cost and schedule for the entire project (and more detailed estimates for the elaboration phase that will immediately follow) Estimating potential risks (the sources of unpredictability) Preparing the supporting environment for the project.

Artifacts of Medical Transcription and Billing Software

Product.
Vision and Business Case
Vision (Business Analyst)

The Vision defines the stakeholders view of the product to be developed, specified in terms of the stakeholders key features, and main constraints. It Contains an outline of the envisioned core requirements, and provides the contractual basis for the more detailed technical requirements.

Business Case (Project Manager)

The Business Case provides the necessary information from a business standpoint, to determine whether or not this project is worth investing in. For a Medical Transcription and billing software product, the business case should include a set of assumptions about the project and the order of magnitude return on investment (ROI) if those assumptions are true. For example, the ROI will be a magnitude of five if completed in one year, two if completed in two years, and a negative number after that. These assumptions are checked again at the end of the elaboration phase when the scope and plan are defined with more accuracy.

Use Case Model and Guidelines (Systems Analyst)

The use-case model is a model of the system's intended functions and its environment, and serves as a contract between the customer and the developers. The use-case model is used as an essential input to activities in analysis, design, and test. The system Analyst will consider all the possible functional or non-functional activities(inputs) of Medical Transcription and billing product that one can cope with. Possible inputs that are most common from doctors or assistance will be analyse and tested.

Risk List (Project Manager)

A sorted list of known, open risks to the Medical Transcription and billing system, sorted in decreasing order of importance, associated with specific mitigation or contingency actions. Medical Transcription and billing System might have the risk of data storage or keep updating the data backups or security of data provided by the patients ect. So the Project Manager will try compiling all the possible risks might it come accross and try providing possible mitigation or response.

Glossary of Terms (Systems Analyst)

The Glossary defines important terms used in the project.

Here all the abbrivations and important terms regarding the project will be listed by the team of System Analysts.

Prototype (Development Team)

One or more proof of concept prototypes, to support the Vision and Business Case, and to address very specific risks

Iteration (Project Manager)

A time-sequenced set of activities and tasks, with assigned resources, containing task dependencies, for the iteration; a fine-grained plan Project Manager will describe what to do in the first elaboration iteration.

Development Case (Systems Analyst)

The development-case description describes the development process that you have chosen to follow in your project. System Analyst of the Medical Transcription and billing system after gathering general data and analysing the system will provide the artifacts about the development case.

Tools (Architecture Group)

The tools to support the software-development effort. A list of all the tools and IDE will be listed that will help in the development of Medical Transcription and billing system.

Product Acceptance Plan (Project Manager)

The Product Acceptance Plan describes how the customer will evaluate the deliverable artifacts from a project to determine if they meet a predefined set of acceptance criteria. It details these acceptance criteria, and identifies the product acceptance tasks (including identification of the test cases that need to be developed) that will be carried out, assigned responsibilities and resources required. In a smaller scale project, this plan may be embedded within the Software Development Plan.

Problem Statement of Medical Transcription and Billing system.

Traditional systems are inflexible, fault intolerant, and difficult to integrate with third-party systems. This leads to problems in timely patient and billing processing, instituting improved processes that don't match the software, and accurate and timely accounting and inventory data to support measurement and planning, among other concerns. This affects doctor Assistants(cashiers), doctors, system administrators, and corporate management.