China
Africa
Explore chapters and articles related to this topic
Quality Assurance Improvement with Metrics
Published in Boyd L. Summers, Effective Processes for Quality Assurance, 2019
Measuring the length of code using number of lines of code or assess software quality through defects/bugs. A line of code is any line of program text that is not a comment or a blank line, regardless of the number of statements or fragments of statements on the line. This specifically includes all lines containing program headers, declarations, and executable and nonexecutable statements. Accepted measurements are dependent on the programming language and programmer and well designed with short programs. Source code creation is only a small part of the total development effort, and it is often unclear how to count lines of code implemented for delivery to the client when the product is completely finished. Most work on software measurement has focused on code-based metrics and plan-driven development processes, and more software is now developed by configuring system requirements. Software measurement per metrics can be used to gather data about software and software processes. Product Quality Assurance metrics are particularly useful for highlighting anomalous components that may have quality problems.
Improving Quality with Software Metrics
Published in Steven F. Blanding, Enterprise Operations Management, 2020
Gaining these benefits requires implementing a software measurement program. Some basic steps are: Defining objectives. Define why a measurement program is needed and what the specific types of questions to be answered are. This identifies what type of data is needed and the scope of the effort.Identifying data sources. A check should be made of the existing data. Is the data complete as required? What data can be collected automatically? What data must be collected manually? Some examples of each type of data should be collected to check its ease of collection, accuracy, and completeness.Obtaining tools. If the company does not already have an analysis tool, it is time to get one. Some tools, such as project tracking and library management software, may be in house but may require specific option settings to collect the necessary data.Defining reports. Copies of the reports and graphs that will be used as output of the measurement program should be mocked up. Distribution frequency should be decided on. Displaying these examples is a key to getting buy-in on the project.Pilot testing. Results from the preceding steps should be tested on a pilot set of applications. It is best to use two or three diverse types of applications to ensure that any potential problems are caught. Training requirements should be identified for those involved in the project.Tuning the results. Any of the collection methods, metrics, and reports should be fine tuned, using the results of the pilot test. This information should be used to estimate effort for the final roll out.Developing a roll-out plan. A plan should be developed to roll out the measurement program across the organization, making sure to include sufficient training.Implement. The process is put in place. Data should be reexamined periodically and tuned accordingly as new information is received. Results should be saved in a data base to allow for comparisons over time.
Physico-mechanical and in-vivo evaluations of tri-layered alginate-gelatin/polycaprolactone-gelatin-β-TCP membranes for guided bone regeneration
Published in Journal of Biomaterials Science, Polymer Edition, 2023
Garima Tripathi, Van Hai Ho, Hae-Il Jung, Byong-Taek Lee
Surface morphology observation and component analysis (EDS) was conducted through scanning electron microscopy (SEM; JSM-6701F, JEOL, Japan) and X-ray spectroscopy (EDS; JSM-7410F, JEOL, Japan) additionally equipped on the SEM. Samples of the electrospun mat were mounted on the sample holders and coated with a thin layer of platinum in a sputter coater (Cressington Scientific Instruments, UK). The micro-fiber morphology of the samples was observed under a scanning electron microscope (SEM, JSM6701F, JEOL, Japan). The β-TCP powder content was detected using EDS detection of Calcium and Phosphate content from SEM scanning. The fiber diameter was determined by randomly measuring 30 areas of fiber diameter using ImageJ software measurement tools. The tensile properties of the samples were tested using a universal testing machine (UTM, R&B UNITECH-T, Korea). Samples were cut into 20 × 3 × 0.1 mm3 rectangular dimension. Tensile strength and % strain was calculated by breaking the material using a 500 g load at a rate of 1 cm min−1.
A complexity metric for object-oriented software
Published in International Journal of Computers and Applications, 2020
This paper, based on the maximum deviation-based multi-attribute decision theories and methods, presents a new UML class diagram metric. By comparing Dr Zhou and Dr Yi's metric methods through the experimental case, we can clearly draw the conclusion that the research results of UML class diagram calculated by the maximum deviation method correspond closely with practical experience. On the one hand, the study of the research can increase the accuracy of metric results of the software, making these results more in tune with the practical experience. On the other hand, the study of results can be particularly helpful to analyze and evaluate the quality of the software, for the reason that it can make a more reasonable and effective evaluation of the quality of the software, significantly reducing the consumption manpower and material resources in the latter stage of software development. The research method of this paper can improve and enrich the software measurement research theoretical system.
Measuring the complexity of migration transition: an attempt using metrics
Published in Journal of Experimental & Theoretical Artificial Intelligence, 2020
Harjot Kaur, Karanjeet Singh Kahlon
Most of the object-oriented software metrics can be applied either for the product (code) or process evaluation (Dumke et al., 2000, 2008). Hence, the metrics-based analysis of agent behaviour and organisational processes can be stated as one of the new and emerging areas in software measurement of agent-based systems. And, for extended aspects of software agents related to objects, a new kind of metric suite can be developed, which can address distributed and semantic aspects of software agents and their associated processes. The most extensive though a set of informal metrics have been defined in Dumke et al. (2000, 2008) and Wille et al. (2002). But, the assessment methodology or validation techniques for the same have not been described.