Software Product and Process, Slides of Distributed Database Management Systems

Download Software Product and Process and more Slides Distributed Database Management Systems in PDF only on Docsity!

Product & Process

Software Products

Software Products are nothing but software systems delivered to the customer with the documentation that describes how to install and use the system. In certain cases, software products may be part of system products where hardware, as well as software, is delivered to a customer. Software products are produced with the help of the software process. The software process is a way in which we produce software.

Essential characteristics of Well-Engineered Software Product:

A well-engineered software product should possess the following essential characteristics: Efficiency: The software should not make wasteful use of system resources such as memory and processor cycles. Maintainability: It should be possible to evolve the software to meet the changing requirements of customers. Dependability: It is the flexibility of the software that ought to not cause any physical or economic injury within the event of system failure. It includes a range of characteristics such as reliability, security, and safety.

In time: Software should be developed well in time. Within Budget: The software development costs should not overrun and it should be within the budgetary limit. Functionality: The software system should exhibit the proper functionality, i.e. it should perform all the functions it is supposed to perform. Adaptability: The software system should have the ability to get adapted to a reasonable extent with the changing requirements.

Software quality product & Process quality

Software quality product is defined in term of its fitness of purpose. That is, a quality product does precisely what the users want it to do. For software products, the fitness of use is generally explained in terms of satisfaction of the requirements laid down in the SRS document.

Process quality

Process quality refers to the degree to which an acceptable process, including measurements and criteria for quality, has been implemented and adhered to in order to produce the artifacts. Software development requires a complex web of sequential and parallel steps.

Product Quality Metrics

This metrics include the following − Mean Time to Failure Defect Density Customer Problems Customer Satisfaction

• (^) Mean Time to Failure It is the time between failures. This metric is mostly used with safety critical systems such as the airline traffic control systems, avionics, and weapons.
• (^) Defect Density It measures the defects relative to the software size expressed as lines of code or function point, etc. i.e., it measures code quality per unit. This metric is used in many commercial software systems.

In-process Quality Metrics

In-process quality metrics deals with the tracking of defect arrival during formal machine testing for some organizations. This metric includes −

• (^) Defect density during machine testing
• (^) Defect arrival pattern during machine testing
• (^) Phase-based defect removal pattern
• (^) Defect removal effectiveness Defect density during machine testing Defect rate during formal machine testing (testing after code is integrated into the system library) is correlated with the defect rate in the field. Higher defect rates found during testing is an indicator that the software has experienced higher error injection during its development process, unless the higher testing defect rate is due to an extraordinary testing effort.

Defect arrival pattern during machine testing The overall defect density during testing will provide only the summary of the defects. The pattern of defect arrivals gives more information about different quality levels in the field. Phase-based defect removal pattern This is an extension of the defect density metric during testing. In addition to testing, it tracks the defects at all phases of the development cycle, including the design reviews, code inspections, and formal verifications before testing. Defect removal effectiveness This metric can be calculated for the entire development process, for the front-end before code integration and for each phase. It is called early defect removal when used for the front-end and phase effectiveness for specific phases.

Walkthrough

Walkthrough is a method of conducting informal group/individual review. In a walkthrough, author describes and explain work product in a informal meeting to his peers or supervisor to get feedback. Here, validity of the proposed solution for work product is checked. It is cheaper to make changes when design is on the paper rather than at time of conversion. Walkthrough is a static method of quality assurance. Walkthrough are informal meetings but with purpose.

Inspections

Sooftware Inspections is generally a fully established and proven activity. It was introduced and developed by Michael Fagan (1970s). It was designed as an elaborated process simply for a systematic review of software artifacts. It is also a process of identifying and detecting defects, errors, violations of development standards, and any other deficiencies in a software product being developed. It also ensures that whether the software product fulfills requirements of client’s or not.

Structure

Structural Testing is a type of testing in which the complete code of the application is tested. This is different from the other type testing which black box where the main concentration is on the type of output generated rather than the way the output generated.

Checklist

It's a very focused list of what you need to do. In this case, it's what you need to do to release your documentation to your users. Your checklist should contain only the information that you need and can absorb at a glance.

Audits

Audit documentation is the record of procedures performed, evidence obtained, and conclusions reached as part of an audit. The proper preparation of audit documentation is critical for several reasons, including the following: It can be used as a defense if the auditor is ever accused of negligence.

Roles and Responsibilities

Documentation Specialist responsibilities include working with colleagues to ensure the consistency of documents, training employees on document usage, and organizing documents across the organization. A documentation manager handles the release and management of a company's technical communications. They ensure documents are free from error, in line with brand voices, and valuable to their target consumers. With the rise in demand for technical communication, document manager jobs are openly available.