|
| |
Let Medical Technology Research work with you on your next programming
project. We'll help you meet your goals by
helping you to correctly determine the need, use, and correct
implementation for your product or project.
Proper Use Model and Solid Implementation
- Higher user satisfaction
- Lower cost of ownership
- Lower cost of maintenance
- Easier to deploy and administer
Capabilities
Medical Technology Research offers requirements analysis,
use-case modeling, project planning, implementation,
testing, and deployment to make your products the best
they can be. We have extensive experience developing C/C++ and
JAVA solutions. We are a Microsoft partner and support development
in the Windows, CE, and .NET environments. We can deliver everything
from cutting-edge mobile applications to traditional stand-alone or N-tier
solutions. We can make your applications web-based, web-accessible,
or just plain-old locally hosted with a GUI or command line interface.
The choice is yours!
- Requirements Analysis
- We start a project by collecting the requirements. This is
typically done by becoming familiar with the end user and their work
methods. By combining interviews, observation, and video
recording, the intended use of a product can be determined and
documented. Using the information gathered a basic set of uses
is developed (see the next section).
-
- A requirements document is derived by taking a closer look at the
use-cases and needs of the users. The requirements document
contains the heart of the project and outlines what an application or
system needs to provide in order to properly satisfy the needs of the
end users. The success of the program lies in properly
determining the use and requirements of the program.
-
- Use-Case Modeling
- The use-case modeling effort usually takes the form of a simple set of
graphical drawings depicting the actors (users and system entities)
and their interaction. The
model created depends largely on the needs of the client and the level
of understanding you have of modeling.
-
- The use-case modeling is part of a feedback loop and
affects the requirements analysis. As the usage of part
of a program is detailed an element known as hidden requirements
begin to surface. These newly discovered requirements are
folded back into the requirements analysis document in order to
properly record all of the needs the program is required to have.
-
- Project Planning
- The next phase of the project can be fairly simple or quite
involved. A project plan is developed which is proportional to
the scale of the effort. A project plan is created using
Microsoft Project. This plan exhibits the details of the
implementation effort and the time lines of development.
-
- This plan details the staffing, financing, and time required to
complete each of the activities that has been determined critical to
the success of the program.
-
- Implementation
- Using all of the material that has been created up to this point the
actual implementation occurs. Systems, software, and any third
party components are obtained. Implementation of any custom
software occurs now.
-
- As the implementation phase progresses the integration portion of
implementation occurs. Ongoing integration and white-box testing
of sub-systems are the key to making our solutions stable and
robust.
-
- Testing
- Once the entire solution is completed, a system-level test phase
occurs. This phase looks at the system from a black-box
perspective. The test phase ensures that all requirements have
been met and that the system behaves as the original use-cases had
intended.
-
- The test phase is NOT the first time that conformance to
specifications is checked but it is the FINAL stamp of approval on
conformance.
-
- The third and final aspect of the test phase is beta testing
also
known as clinical trials in the medical field. It is at this
point that the software and system are put through its paces with live
users, live situations, and human interaction. This is the phase
where the client accepts the system design and implementation and
declares it fit for general deployment.
-
- Deployment
- Deployment is the project wrap up phase from an engineering
standpoint. All the work has been completed and the product has
been accepted by the customer. Now the system is deployed for
general use by the intended user base. As the system is deployed,
the software enters the bug fixing and maintenance phase. Issues
will be raised by the end users. The issues will be evaluated
and the appropriate changes will be implemented if and when
appropriate.
Contact us to
have us prepare a project proposal for you today.
|
