Integrating security activities into the software development life cycle and the software quality assurance process

1986 ◽  
Vol 5 (3) ◽  
pp. 218-242 ◽  
Author(s):  
Frederick G. Tompkins ◽  
Russell S. Rice
2015 ◽  
Author(s):  
Fernanda C. P. Motta Fernandes ◽  
Ricardo Bedin França

In this paper, we present an evaluation of Scrum's impacts over the software quality assurance process in the embedded aerospace software domain. We present basic concepts of the DO-178C and Scrum, then we assess related work and introduce the case study used as reference for our study, as well as the perceived results of using Scrum in both the development teams and in quality assurance. Finally, we summarize good practices for using Scrum in software quality assurance teams.


2014 ◽  
Vol 1049-1050 ◽  
pp. 2032-2036
Author(s):  
Ai Ming Huang ◽  
Guang Shan Deng ◽  
Jun Hu ◽  
Yong Jun Huang

This paper mainly make a theoretical research and exploration on software quality assurance quality assurance improvement based on CMM process, with the educational software quality assurance model as an example. It elucidates the relationship between educational software process improvement and quality assurance, and explicits the importance of educational software development process improvement to the quality of educational software. Additionally, it discussed the establishment of educational software development model on the basis of the waterfall model of traditional software development, and construction of process quality management models and platforms based on CMM educational software process improvement.


2012 ◽  
Author(s):  
Denise Lazzeri Gastaldo Bombonatti ◽  
Flávio Lenhari

This experience report describes MM-SQAP (Method for Modeling Software Quality Assurance Process). This method was defined and applied in a financial company in order to establish its software quality assurance process. The results obtained with this application demonstrated its feasibility. The application of MM-SQAP in other areas, in different domains, will make it more flexible than its original version.


Author(s):  
Andriy Lishchytovych ◽  
Volodymyr Pavlenko

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