|
|
Roles
|
| |
Developer:
the person responsible for actually writing source code
in a specific programming language, such as Java, C or C++,
or HTML. Developers base their source code upon the design
created by the Architect.
Architect: the person
responsible for the design of code in a given project or
application. Additional responsibilities include verifying
that source code is implemented according to the specification
in use and improving the processes used for building an
application.
In this latter role, the Architect is a fundamental figure
in Automated Error Prevention (AEP), chaperoning and guiding
the AEP process throughout the entire software development
lifecycle. Through feedback loops within the software development
lifecycle, the Architect correlates bugs with the particular
process that generated those bugs and takes appropriate
steps to correct the process. This eliminates future bugs
from being generated by that process deficiency.
Project Manager:
the person responsible for delivering the project, on time,
with the designed functionality, and under budget. The Project
Manager makes his decision concerning the final deployment
of a product using Confidence Factors.
Confidence factors help you estimate the progress of your
current project using a scale from 0% to 100%. From this
scale, you can determine how successful your tests have
been in analyzing a project, and understand what types of
tests may still need to be conducted. The higher the confidence
factor number, the better your application is working and
the more likely it is to succeed after deployment.
Ideally, what you want to see when you use confidence factors
during a project is an increase in all statistics as the
project matures. These statistics are particularly valuable
when integrating and testing various modules into a final
product. Confidence factors show you at a glance if any
one module that is added to a project is complete enough
to stay in the final build or if it needs further work.
Database Administrator (DBA): the
person who monitors and verifies the performance of databases,
and takes appropriate measures to ensure peak performance
whenever necessary.
Tester/QA Personnel: the
person responsible for verifying the functionality of a
system. In a traditional software development environment,
the Tester/QA Personnel simply finds a bug in an application
and notifies a developer, who takes steps to fix the bug.
However, within AEP, the role of the Tester/QA Personnel
is different, and much more important. In AEP, Tester/QA
Personnel find bugs, figure out why these bugs happened,
and correlate them to the particular process within the
software development lifecycle where they were generated
in order to fix the process so that these bugs do not reoccur.
In this role, Tester/QA Personnel support the Architect
in their effort to implement AEP and prevent errors from
occurring.
Webmaster: the person
responsible for monitoring the performance and functionality
of both stage and production servers within a Web Development
environment. Using test suites created by development and
modified by QA, the Webmaster can correct any remaining
errors or procedural issues on the stage server and migrate
to the production server using validated, error-free code.
These same test suites can then be used by the Webmaster
to verify and monitor operational parameters and the functional
health of the entire, live system.
|
|
