DevOps model in practice: Applying a novel reference model to support and encourage the adoption of DevOps in a software development company as case study

DevOps has emerged as an approach to help organizations automate, cost optimization, increase profitability, improve the stability of the software development process and the responsiveness of organizations, and create a more agile development and release pipeline. However, its adoption, maintenance and evaluation continue to be a challenge for software organizations, due to the absence of solutions that formalize process elements in a detailed way, such as: practices, roles, artifacts, objectives, among others. This paper presents a DevOps Model, this model to support the adoption of DevOps, which provides a set of fundamental and complementary values, principles, dimensions, and practices. The practices suggest a set of items such as purpose, specific objectives and expected artifacts. The elements defined in proposed DevOps Model arise from the elements found in the studies analyzed through a systematic mapping study. Model evaluation was carried out through a software development company as case study. The results obtained have allowed the case study company to evaluate, diagnose and identify improvement opportunities to be carried out in the processes and projects where a DevOps-based approach is used, the above in a practical, useful, and adequate way that allows this type of companies and with a low use of resources, both economic investment and time. This is how the DevOps Model could guide professionals and organizations towards a better understanding of DevOps, in addition to minimizing the subjectivity and error of its interpretation, adoption and evaluation

Knowledge-Based Decision Support in Department of Defense Acquisitions

Despite numerous reform efforts over the past 30 years, acquisition programs in the Department of Defense (DoD) continue to experience cost overruns and schedule delays. One contributing factor is the decision-making process used by defense officials. The General Accounting Office (GAO) has stated that ‘poor program outcomes are the lack of widespread adoption of a knowledge-based acquisition process within DoD despite polices that support such a process. A knowledge-based business case at the outset of each program would alleviate overpromising on cost, schedule, and performance and would empower program managers.’ Effective decision-making for acquisition programs is very important. It not only affects the performance of a program but could also impact the lives of Airman, Soldiers, Sailors, and Marines protecting our country. Analyzing decision support products is one method to improve the knowledge used during the decision-making process. Therefore, the scope of this research focused on knowledge products supporting decisions made by DoD acquisition officials and their alignment with best practices and their usefulness to decision-makers. This research found that the required information contained in decision support products is not adequate to provide the knowledge needed to make informed decisions. Recommendations for improving decision support for key knowledge areas will be discussed

MBSE METHODOLOGY AND ANALYSIS TOOL TO IMPLEMENT MBSE POST MILESTONE C

This thesis proposes a model-based systems engineering (MBSE) methodology to be implemented post Milestone C, develops a Microsoft Excel MBSE analysis tool which provides a recommendation to implement MBSE, and provides a case study for implementing MBSE post Milestone C on a Department of Defense (DoD) acquisition program. The purpose of the MBSE methodology is to identify how MBSE should be implemented post Milestone C to address the systemic challenges which are faced by DoD acquisition programs post Milestone C. The Excel MBSE analysis tool provides a set of questions which provide metrics to the program office to determine the benefit of implementing MBSE post Milestone C into their program. The thesis then details, through a case study, how the Excel MBSE analysis tool can be used to decide whether to implement MBSE. Prior research on the systemic challenges within DoD acquisition programs as well as the use of MBSE during post Milestone C activities were leveraged in developing the proposed MBSE methodology and Excel MBSE analysis tool. The thesis makes a recommendation to implement MBSE post Milestone C to mitigate schedule, cost, and risk uncertainties. This is done through digitally linking various models, such as a manufacturing model and a logistics model to an integrated master schedule (IMS). Based on the metrics and cost, the Excel MBSE analysis tool provides a recommendation on which models should be implemented.http://archive.org/details/mbsemethodologya1094560439Civilian, Department of the NavyApproved for public release; distribution is unlimited

Development of a Web-Based Information System for Material Inventory Control: the Case of an Automotive Company

Inventory control is controlling the materials movement to fulfill the requirements. The materials can from the direct and indirect materials. the indirect materials are the materials that cannot be calculated according to the bill of materials. Indirect materials need safety stocks, so the requirements can always be fulfilled, means it need the control and monitoring of their levels. To control the movement of the materials, each department have roles to control and information that need to be shared. PT XYZ is an automotive assembler company, the company need a tool to control the indirect materials inbound and outbound and control its stock. This research is to have the tool that will be a web-based program because to share the information throughout the department of planning, production, and logistics. In developing and implementing the program itself, the RUP methodology is used to guide in doing this research with having four phases and activities that support the research. The result is the program itself have been successful to fulfilled the user requirements. The program shows the real time information for the levels of the materials and also the inbound and outbound of the materials for the user to monitor its levels

Information Technology: DOD Needs to Strengthen Management of Its Statutorily Mandated Software and System Process Improvement Efforts

A letter report issued by the Government Accountability Office with an abstract that begins "The Department of Defense's (DOD) acquisition of weapon systems and modernization of business systems have both been on GAO's list of high-risk areas since 1995. To assist DOD in managing software-intensive systems, Section 804 of the Bob Stump National Defense Authorization Act for Fiscal Year 2003 required the Office of the Secretary of Defense (OSD) and DOD component organizations, including the military departments, to undertake certain software and systems process improvement (SSPI) actions. As requested, GAO assessed (1) the extent to which DOD has implemented the process improvement provisions of the act, and (2) the impact of DOD's process improvement efforts. To do so, GAO analyzed relevant plans, policies, guidance, performance measures, and reports against statutory requirements and relevant guidance, and interviewed DOD officials.

Caractérisation de projets de développement logiciel dans une perspective de flux de connaissances

RÉSUMÉ Face aux ratés auxquelles fait face l'industrie du développement logiciel et l'incapacité des différentes approches de processus logiciels à régler ces problèmes, il s‘avère intéressant de se baser, d‘une part, sur les acquis du domaine des processus logiciels et, d‘autre part, de s‘inspirer des innovations de domaines connexes. En particulier, la gestion des connaissances appliquée au génie logiciel est un sujet présentement en émergence. Une meilleure compréhension des mécanismes de création et de conversion de connaissances au sein d'un projet de développement logiciel est une avenue de recherche prometteuse. L'objectif principal de cette thèse de doctorat est donc de caractériser les projets de développement logiciel dans une perspective de flux de connaissances. Cette thèse par articles propose d'atteindre l'objectif de recherche par la présentation de trois articles en plus d'un chapitre détaillant des résultats complémentaires. Le premier article présente et justifie la méthodologie utilisée dans le cadre des travaux de recherche de cette thèse. Plus précisément, l'article détaille la méthodologie ATS (activity time slip), une approche à partir de laquelle des développeurs logiciels doivent enregistrer leurs activités dans une perspective de connaissances. Les données recueillies sont ensuite codifiées selon le modèle de flux de connaissances, qui est inspiré du modèle de création de connaissances de Nonaka & Takeuchi (1995) et qui définit six facteurs cognitifs dans le cadre d'un projet de développement logiciel: l'acquisition, la cristallisation, la validation, la réalisation, la vérification et l'organisation du travail. Une étude de cas multiples est présentée, afin de démontrer l'originalité et la pertinence de la méthodologie proposée. Le second article présente l'utilisation du modèle de flux de connaissances, dans le cadre d'une étude de cas, afin d'analyser les conséquences de la qualité de la documentation lors de la réutilisation de composants FLOSS (free/libre open source software). L'analyse de l'étude de cas permet de déterminer les conséquences négatives d'une documentation inadéquate sur le flux de connaissances au sein d'un projet de développement logiciel. Le troisième article vise à comprendre les mécanismes menant aux divergences observées entre la conception et l'implémentation d'un projet de développement logiciel. L'utilisation de la méthodologie ATS et du modèle de flux de connaissances facilite l'analyse de l'étude de cas. Ainsi, les discordances entre les artefacts de conception et l'implémentation s'expliquent par le fait que la conception n'est qu'une image de possibilités. Les résultats de recherche complémentaires permettent de caractériser trois projets intégrateurs de développement logiciel, à la manière d'une étude de cas multiples de type exploratoire reposant sur la méthodologie ATS et la modélisation par flux de connaissances. Ainsi, l'analyse des jetons d'activité (ATS) permet de porter un jugement sur la rigueur des développeurs et donc sur la fiabilité des jetons, selon les trois profils identifiés. De plus, les facteurs cognitifs sont caractérisés selon leur caractère individuel et participatif. Par ailleurs, le séquencement cognitif permet l'identification de quatre profils de développeurs: le cristallisateur, le codeur, le polyvalent et l'agent libre. Finalement, une forte corrélation a été observée entre un effort d'acquisition élevé et une productivité du code source faible, ce qui constitue une contribution majeure, de par son originalité et ses conséquences théoriques et pratiques.----------ABSTRACT Given the failures faced by the software development industry and the inability of different software process approaches to solve these problems, it is interesting to rely, on the one hand, on achievements in the software process field and, on the other hand, learn from innovations in related fields. In particular, knowledge management applied to software engineering is a subject currently emerging. A better understanding of knowledge creation and conversion's mechanisms in software development projects is promising. The main objective of this thesis is to characterize software development projects from a knowledge flow perspective. This doctoral thesis intends to achieve the research goal by presenting three papers and additional complementary results. The first paper presents and justifies the methodology used in this thesis. The paper details the ATS (activity time slip) methodology, where software developers must log their activities from a knowledge perspective. Data are then codified based on the knowledge flow model, which is related to Nonaka and Takeuchi‘s (1995) knowledge creation model and which defines six cognitive factors: acquisition, crystallization, validation, implementation, verification and work organization. A multiple case study is presented to demonstrate the originality and relevance of the proposed methodology. The second paper presents a case study using the knowledge flow model to analyze the consequences of documentation quality in FLOSS components reuse. The case study's analysis allows the identification of negative consequences on a software development project's knowledge flow resulting from inadequate documentation. The third paper focuses on understanding the mechanisms leading to discrepancies between design and implementation in a software development project. The use of the ATS methodology and the knowledge flow model facilitates the case study's analysis. The discrepancies between design artifacts and implementation can be explained by the fact that design is an image of possibilities. Complementary research results allow the characterization of three software development capstone projects by means of an exploratory multiple case study based on the ATS methodology and the knowledge flow model. The analysis of the activity time slips (ATS) allows to judge the developers' rigor and therefore the reliability of their activity time slips, according to three identified patterns. Also, cognitive factors are characterized from a individual and participative viewpoint. Furthermore, cognitive sequencing allows the identification of four developers profiles: the crystallizer, the coder, the "versatile", and the free agent. Moreover, a strong correlation was observed between high acquisition effort and low source code productivity, which is a major contribution, because of its theoretical and practical implications

Impact of cross section, web reinforcement and load history on the seismic performance of slender concrete walls

Many reinforced concrete buildings in seismic regions employ reinforced concrete shear walls as part of the lateral force resisting system and these walls often have non-planar cross-sectional geometries. To date, the majority of experimental tests on slender concrete walls have been conducted on planar walls which have been subject to low shear stress demands. An experimental program was developed to examine the response of flanged C-shaped walls with respect of load history and a computational parametric study was conducted to focus more specifically on the impact of web reinforcement for walls subject to a range of shear stress demands. The experimental program investigated the impact of bi-directional loading on flanged C-shaped walls that were designed to meet the minimum ACI 318-08 special structural wall requirements. The results indicate that irrespective of load history the C-shaped walls have a similar damage progression leading to a buckling-rupture failure and a nearly identical strong-axis load-deformation response up to the peak flexural strength. However, bi-directionally loaded walls exhibit earlier onset of critical damage limit states and reduced strong-axis drift capacity. Compared to experimentally-tested planar walls that tend to fail via crushing-buckling, the flanged C-shaped wall geometry has a more ductile failure mode despite being subject to higher shear stress demands. The improved response can be attributed to the ability to redistribute forces to the boundary elements and flanges after considerable web damage. Damage to the unconfined web of the flanged C-shaped walls was substantial. Though walls developed distributed cracking, there was a single wide crack plane that developed near the wall base. Widening of this crack led to high tensile strains in web reinforcement and ultimately the widespread fracture of vertical web bars, limited fracture of horizontal web bars, as well as severe concrete degradation in the surrounding region. This performance suggests that the minimum web steel content required by ACI 318 may be insufficient. As such, the current minimum web reinforcement requirements were studied using an experimentally-validated, high-resolution finite element modelling approach. The computational parametric study examined the impact of the shear stress demand and web reinforcement ratio on wall deformation and ductility. The study results indicate that increased shear stress demand can significantly reduce wall deformation and ductility; however, designs with excess horizontal reinforcement, beyond what is required by ACI 318-14 to meet shear demand, can improve ductility. The data suggest there are similar performance benefits of reducing the design shear demand-to-capacity ratio. A second stage of the parametric study explored the combined effect of modifying the horizontal reinforcement ratio and increasing boundary element length from the ACI 318-14 minimum to the full neutral axis depth. For walls with low-moderate shear stress demands, this combination results in even greater wall ductility than providing excess horizontal reinforcement alone. The experimental tests provide critical data to developing performance-based design criteria for non-planar walls, since most prior efforts have been related to planar walls. The computational parametric study results are of value in developing new code recommendations for the minimum horizontal web reinforcement ratio which have essentially remained unchanged throughout the history of the ACI 318 building code