Site Map
Client Login
Service Models
Contact us
  Quality Paradigm
  Quality Policy
  Quality Assurance

"Quality is never an accident; it is always the result of high intention, sincere effort, intelligent direction and skillful execution; it represents the wise choice of many alternatives."

Quality and profit has been pretty straight forward for everyone - no quality, no customer. In the real world, lesser the quality, sooner the customer departs! More the quality, the harder it is for the customer to depart which is what every organization strives for. Quality initiatives often fail because there is no direction to the effort or the direction is not communicated to everyone working. So its essential to find the purpose for quality and the means will follow - more so when in offshore programming. In other words we believe that "Quality for what " - is the question that directs "How quality, where quality and when quality".

Software Product Quality encompasses following:

Correctness : The extent to which a program satisfies its specification and fulfills the customer's mission objectives.

Reliability : The extent to which a program can be expected to perform its intended function with required precision. it should be noted that other more complex definitions of reliability have been proposed.

Efficiency : The amount of computing resources and code required by a program to perform its function.

Integrity : Extent to which access to software or data by unauthorized person can be controlled.

Usability : Effort required to learn, operate, prepare,input and interpret output of a program.

Maintainability : Effort required to locate and fix an error in a program. This is a very limited definition.

Flexibility : Effort required to modify an operational program.

Testability : Effort required to test a program to ensure that it performs its intended function.

Portability : Effort required to transfer the program from one hardware and /or software system environment to another.

Reusability : Extent to which a program (or parts of a program) can be reused in other application--related to the packaging and scope of the functions that the program performs.

Interoperability: Effort required to couple one system to another system.

A Software product should have following features to have high quality.

Auditability: The ease with which conformance to standards can be checked.

Accuracy : The precision of computations and control.

Communication commonality : The degree to which standard interfaces, protocols and bandwidth are used.

Completeness : The degree to which full implementation of required function has been achieved.

Conciseness : The compactness of the program in terms of lines of code.

Consistency : The use of uniform design and documentation techniques throughout the software development project.

Data commonability : The use of standard data structures and types throughout the program.

Error tolerance : The damage that occurs when the program encountered an error.

Execution efficiency :The run-time performance of a program.

Expandability : The degree to which architectural, data, or procedural design can be extended.

Generality : The breadth of potential application of program components.

Hardware Independence : The degree to which the software is decoupled from the hardware on which it operates.

Instrumentation : The degree to which the program monitors its own operation and identifies errors that do occur.

Modularity : The functional independence of program components.

Operability : The ease of operation of a program.

Security : The availability of mechanism that control or protect programs and data.

Self Documentations : The degree to which the source code provides meaningful documentation.

Simplicity : The degree to which a program can be understood without difficulty.

Software system Independence: The degree to which the program is independent of nonstandard programming language features, operating system characteristics and other environmental constraints.

Traceability : The ability to trace a design representation or actual program component back to requirements.

Training : The degree to which the software assists in enabling new users to apply the system.

| Home | Term of Use | Private Policy | Site map | Contact us