Our Quality Policy states the following primary goals:
Development of high-quality software
systems that comply 100% with customer's demands and expectations.
Rigorous and timely fulfillment of
every obligation to a customer.
Continuous improvement of development
and management processes.
Deep involvement of every employee in
the quality management system.
Quality improvement is a permanent process rather than a single action for
eSSL. Such improvement is achieved through regular external surveillance and
internal audits, thorough review of all business processes coupled with client
feedback. We pay special attention to preventing possible problems rather than
follow-up error correction.
Our Process
The above diagram gives an overview of the Software Development Life Cycle
(SDLC) process at eSSL. The Life cycle activities are supported by a set of
continuous activities, which go on at the project level (e.g. Software Quality
Assurance, Change Management, Tracking, Software Configuration Management
etc.). They are performed at different stages based on the project plan.
There are various work products, which are the outcomes of the SDLC activities.
They are listed briefly in the diagram. The sequence and interdependencies of
the activities and work products depend upon the project context and the
lifecycle model chosen.
Together with relevant ISO documents, we actively use IEEE Software Engineering
standards and best practices at all phases of software development. Our
immediate aim is an implementation of capability maturity model (CMM)
methodology in corporate development practice.
To achieve CMM levels eSSL has taken Rational Unified Process and tools as a
base reference, which addresses both, project maturity and organization
maturity. RUP uses UML as standard language for modeling software-intensive
systems.
The RUP emphasizes addressing high-risk areas very early, by rapidly developing
an initial version of the system, which defines its architecture. It does not
assume a fixed set of firm requirements at the inception of the project, but
allows you to refine the requirements as the project evolves. It expects and
accommodates changes. The process does not put either a strong focus on
documents or ‘ceremonies’, and it lends itself to the automation of many of the
tedious tasks associated with software development. The main focus remains the
software product itself and its quality, as measured by the degree to which it
satisfies its end-users and meets its return on investment objective
altogether.
RUP is generic enough to be tailored to a wide variety of software products and
projects, both in size and application domain and it is centered around three
areas: people, process, and tools or methods.
