Вы находитесь на странице: 1из 17





Control means to check whether the work is running as per plan and take necessary steps whenever needed.

Software Quality Control It is the set of procedures used by organizations to ensure that a software product will meet its quality goals at the best value to the customer, and to continually improve the organizations ability to produce software products in the future.

It also specified functional requirements as well as non-functional requirements such as supportability, performance and usability. It also refers to the ability for software to perform well in unforeseeable scenarios and to keep a relatively low defect rate.

The characteristics of the Quality Plan are as follows: Consistent : The plan should follow the standard and guidelines set by standards. Complete: The plan should include the overall representation of the project requirements , features , documentation of the project plan such plan should be developed through all the stages of the project development activity.

Clear: The plan ,thus developed should be very clear to the developer and also to the stakeholders regarding project requirements and other project details . Correct: The project details will be very clear to stakeholders regarding product delivery date of its postponement or cancellation of the product. Constructible: The project development plan should be such that if by chance some design errors occurs in product development then it should be constructible within small time span

The main objective of Quality Control Plan is to provide mechanism by which all the plans are executed consistently without any design errors. It ensures that the procedures are continuously reviewed by the stakeholders and the designers. To achieve quality control, a project file document is created where feedback is given at regular intervals. Periodic review of the feedback results in appropriate changes in the development process.

Quality Control Activities

Check that assumptions and criteria for the selection of data and the different factors related to data are documented. Check for transcription errors in data input and reference. Check the integrity of database files. Check for consistency in data. Check that the movement of inventory data among processing steps is correct. Check for uncertainties in data , database files etc. Undertake review of internal documentation. Check methodological and data changes resulting in recalculations. Undertake completeness checks. Compare Results to previous Results.


Verification and Validation assures that a software system meets a user's needs. Verification: "Are we building the product right". The software should conform to its specification. Validation: "Are we building the right product". The software should do what the user really requires. Two principal objectives are Discovery of defects in a system. Assessment of whether the system is usable in an operational situation.

Integrity, in terms of software is the assurance that information can only be accessed or modified by those authorized to do so. Measures taken to ensure integrity include controlling the physical environment of networked terminals and servers, restricting access to data, and maintaining rigorous authentication practices, integrity can also be threatened by environmental hazards, such as heat, dust, and electrical surges.

Data integrity can be compromised in a number of ways: Human errors when data is entered Errors that occur when data is transmitted from one computer to another Software bugs or viruses Hardware malfunctions, such as disk crashes Natural disasters, such as fires and floods

There are many ways to minimize these threats to data integrity. These include: Backing up data regularly Controlling access to data via security mechanisms Designing user interfaces that prevent the input of invalid data Using error detection and correction software when transmitting data

Network administration measures to ensure data integrity include: maintaining current authorization levels for all users, documenting system administration procedures, parameters, and maintenance activities, and creating disaster recovery plans for occurrences such as power outages, server failure, and virus attacks.

It means compatible with new technology, Easy to adopt new updatetion Can be bring back to the original form

Inter organisational communication. Legacy in systems. Standarisation


Asking the vendors for the software. Asking for the possible modification Rate the vendor Submission of proposal by the vendor Create issues at proposal time Re-submmission of the proposal