Computing system to support software development, testing, and product quality assurance for an earth observing system instrument: a case study

1995 ◽  
Author(s):  
Shahin Samadi ◽  
Edward J. Masuoka
Keyword(s):  
Quality Assurance ◽  
Software Development ◽  
Product Quality ◽  
Computing System ◽  
Earth Observing System ◽  
Support Software

Implementing Software Metrics at a Telecommunications Company

2011 ◽  
pp. 58-76
Author(s):  
David I. Heimann
Keyword(s):  
Software Development ◽  
Organizational Structure ◽  
Product Quality ◽  
Software Metrics ◽  
High Quality ◽  
Telecommunications Company

Establishing and using fundamental measures of software development progress is an essential part of being able to predictably produce high-quality customer-satisfying software within a reasonable agreed-to timeframe. However, in many organizations such measurement is done incompletely or not at all. While various forces encourage measurement programs, others form barriers to such implementation. This case study explores a formal Metrics Program established to track and analyze the development of a new version for the major voicemail product of a mid-sized telecommunications company. The study addresses the evolution of the company’s organizational structure and culture that led to the adoption of the program, the components and structure of the program, the implementation of the program, its effects on product quality and timeliness, and what happened thereafter. The study also raises questions with respect to facilitating an organizational atmosphere where a Metrics Program can flourish.

scholarly journals Quadruple Factors Interference and Its Effects on Quality of Outsourcing Testing: A Case Study

2021 ◽  
Vol 10 (1) ◽  
pp. 228-236
Keyword(s):  
Quality Assurance ◽  
Software Development ◽  
Software Testing ◽  
Global Market ◽  
Success Factor ◽  
Test Automation ◽  
High Quality ◽  
Software Products

The share of IT companies in the global market has been increasing and many organizations are moving to outsource their software development projects to off-shore vendors. Recently, the IT sector in Palestine has been gaining much ground with many software development companies specializing in software development outsourcing services. Maintaining high-quality and robust software products has always been a key success factor in the outsourcing sector. Software testing is considered to be the main phase in which teams can assure high quality of software products.Therefore, we did an exploratory multiple-case study and this study involvesfour Palestinian software outsourcing companiesof different domain. We provide insights about factors that affect the quality of software testing practice, and explore applied testing techniques, methods and confronted challenges. The results reveal that there is big attention toward software testing assoftware development companies are investing more effort, time, and technical resources into their quality assurance teams. Additionally, among the applied software testing methods, more attention needs to be directed towards test automation. Moreover, more theoretical and technical courses targeting software quality assurance should be included in national Palestinian universities’ curriculum. Finally, we propose a new model that can help practitioners to enhance the quality of their outsourced software products

Assurance for Temporal Compatibility Using Contracts

2009 ◽  
pp. 360-371
Author(s):  
Omkar J. Tilak
Keyword(s):  
Distributed Computing ◽  
Software Development ◽  
Distributed System ◽  
Large Scale ◽  
Formal Method ◽  
Computing System ◽  
Temporal Constraints ◽  
System Activity ◽  
Temporal Interaction

Software realization of a large-scale Distributed Computing System (DCS) is achieved through the Componentbased Software Development (CBSD) approach. A DCS consists of many autonomous components that interact with each other to coordinate each system activity. The need for such coordination, along with requirements such as heterogeneity, scalability, security, and availability, considerably increases the complexity of code in a distributed system. This chapter depicts a formal method to specify component interactions involving temporal constraints. Using the component interactions, various types of temporal interaction compatibility classes are defined. A simple case study is presented that indicates the benefits of the component interaction specifications discussed in this chapter.

Computable metrics of personal performance in software development teams

2019 ◽  
Author(s):  
Andriy Lishchytovych ◽  
Volodymyr Pavlenko
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Product Quality ◽  
Performance Indicators ◽  
Key Performance Indicators ◽  
Project Manager ◽  
Development Life Cycle ◽  
Software Product ◽  
Software Development Life Cycle

The present article describes setup, configuration and usage of the key performance indicators (KPIs) of members of project teams involved into the software development life cycle. Key performance indicators are described for the full software development life cycle and imply the deep integration with both task tracking systems and project code management systems, as well as a software product quality testing system. To illustrate, we used the extremely popular products - Atlassian Jira (tracking development tasks and bugs tracking system) and git (code management system). The calculation of key performance indicators is given for a team of three developers, two testing engineers responsible for product quality, one designer, one system administrator, one product manager (responsible for setting business requirements) and one project manager. For the key members of the team, it is suggested to use one integral key performance indicator per the role / team member, which reflects the quality of the fulfillment of the corresponding role of the tasks. The model of performance indicators is inverse positive - the initial value of each of the indicators is zero and increases in the case of certain deviations from the standard performance of official duties inherent in a particular role. The calculation of the proposed key performance indicators can be fully automated (in particular, using Atlassian Jira and Atlassian Bitbucket (git) or any other systems, like Redmine, GitLab or TestLink), which eliminates the human factor and, after the automation, does not require any additional effort to calculate. Using such a tool as the key performance indicators allows project managers to completely eliminate bias, reduce the emotional component and provide objective data for the project manager. The described key performance indicators can be used to reduce the time required to resolve conflicts in the team, increase productivity and improve the quality of the software product.

Sign in / Sign up

Export Citation Format

Share Document