|
The four components of our service architecture
below layout in detail our services mechanism making an earnest
effort to leave no stone unturned while following a conventional
SDLC (Software Development Life Cycle) with custom built MeteSys
processes (RADI): RADI's diverse and multi-dimensional work flow
allow us to specialize in providing full service planning,
analysis, design, and implementation that is supported by
Technology and Development expertise.
A successful implementation is in reality a
‘blend’ of skill sets that require not only Implementation
expertise, but Technology and Development lifecycle management
framework as well. Project Implementation requires technical
support for tasks such as hardware administration &
configuration, database configuration, and environment setup for
piloting, testing and moving into the production environment
which is an important component of RADI. RADI offers a deep base
of best practices and knowledge gained by implementing our own
in-house and 3rd party ERP systems. Our RADI team knows your
industry, understand your challenges, and have first-hand
experience for solving your problem. To find out more about the
implementation services that we provide, please contact us at
1-832-220-3318.
Requirements
 Top-level
activities:
Reviews allocated requirements before they are incorporated into
the software project.
Uses allocated requirements as the basis for software plans,
work products, and activities.
Changes to allocated requirements are reviewed and incorporated
into the software project.
Analysis
Top-level
activities:
The software engineering group participates on the project
proposal team.
Software project planning is initiated in the early stages of,
and in parallel with, the overall project planning.
The software engineering group participates with other affected
groups in the overall project planning throughout the project's
life.
Software project commitments made to individuals and groups
external to the organization are reviewed with senior management
according to a documented procedure.
A software life cycle with predefined stages of manageable size
is identified or defined.
The project's software development plan is developed according
to a documented procedure.
The plan for the software project is documented.
Software work products that are needed to establish and maintain
control of the software project are identified.
Estimates for the size of the software work products (or changes
to the size of software work products) are derived according to
a documented procedure.
Estimates for the software project's effort and costs are
derived according to a documented procedure.
Estimates for the project's critical computer resources are
derived according to a documented procedure.
The project's software schedule is derived according to a
documented procedure.
The software risks associated with the cost, resource, schedule,
and technical aspects of the project are identified, assessed,
and documented.
Plans for the project's software engineering facilities and
support tools are prepared.
Software planning data are recorded.
Design
Top-level
activities:
A documented software development plan is used for tracking the
software activities and communicating status.
The project's software development plan is revised according to
a documented procedure.
Software project commitments and changes to commitments made to
individuals and groups external to the organization are reviewed
with senior management according to a documented procedure.
Approved changes to commitments that affect the software project
are communicated to the members of the software engineering
group and other software-related groups.
The size of the software work products (or size of the changes
to the software work products) are tracked, and corrective
actions are taken as necessary.
The project's software effort and costs are tracked, and
corrective actions are taken as necessary.
The project's critical computer resources are tracked, and
corrective actions are taken as necessary.
The project's software schedule is tracked, and corrective
actions are taken as necessary.
Software engineering technical activities are tracked, and
corrective actions are taken as necessary.
The software risks associated with cost, resource, schedule, and
technical aspects of the project are tracked.
Actual measurement data and replanning data for the software
project are recorded.
The software engineering group conducts periodic internal
reviews to track technical progress, plans, performance, and
issues against the software development plan.
Formal reviews to address the accomplishments and results of the
software project are conducted at selected project milestones
according to a documented procedure.
Implementation
Top-level
activities:
A SQA plan is prepared for the software project according to a
documented procedure.
The SQA group's activities are performed in accordance with the
SQA plan.
The SQA group participates in the preparation and review of the
project's software development plan, standards, and procedures.
The SQA group reviews the software engineering activities to
verify compliance.
The SQA group audits designated software work products to verify
compliance.
The SQA group periodically reports the results of its activities
to the software engineering group.
Deviations identified in the software activities and software
work products are documented and handled according to a
documented procedure.
The SQA group conducts periodic reviews of its activities and
findings with the customer's SQA personnel, as appropriate.
|
