TAUP Software Requirements Specification

From TAPASWiki

1 Introduction
2 Functional Requirements
- 2.1 Core
- 2.2 Extension Modules
3 Use Cases
4 Non-functional Requirements
5 Environmental Requirements
- 5.1 APIs Provided

Introduction

Family physicians practice according to their own style. Physicians are at different levels of preparedness in terms of adopting technology to assist in their practice. TAPAS was built around this premise: that by producing a suite of tools that physicians can adopt at their own rate (thus creating a hybrid practice), they will slowly progress to a point where they are ready to use a full electronic medical record.

TAPEAR, the TAPAS client, although designed to eventually accommodate flexible customization, is still a monolithic Java Swing application. If a physician adopts TAPAS, he or she will get all features at once.

We propose to refactor TAPEAR to be rebuilt on the Netbeans platform, as well as give recommendations how to adapt the CASA server so that this pluggable structure can 'hook up' to CASA. This would give TAPAS extreme flexibility in terms of customizing the client to use only the current features a physician needs, as well as allowing limitless future extensions. TAPAS would then be better able to integrate with any physician’s practice. Next to that, TAPEAR would gain the benefits of being built on the Netbeans platform.

As TAUP is a re-engineering effort, the new TAPEAR will continue to meet all of the functional requirements, use cases, non-functional requirements, and environmental requirements described in the original Software Requirements Specification. Only new requirements will be described in this document.

[edit]