Background: Tomato is commonly treated as “Protective Food” as it contain high amounts of several nutritive compounds especially carotenoids such as lycopene and â carotene (Provitamin A), ...flavonoids, phenolic acids and ascorbic acid and minerals like calcium, iron and phosphorus. Development of high yielding varieties, genetic improvement and best selection are the basic outcome of a superior breeding programme. Therefore, a study was conducted out to analyze the combining ability for yield and yield contributing traits of tomato genotypes. Methods: This study analyzed the general combing ability (GCA) and specific combing ability (SCA) of tomato (Lycopersicon esculantum Mill.) including different breeding lines and landraces, which were grown during three seasons (March 2020, September 2020 and March 2021) with row to row and plant to plant spacing of 60 × 45 cm in randomized block designs (RBD) having three replications at the Agriculture research farm of Choudhary Chhotu Ram (PG) College, Muzaffarnagar U.P., India. Morpho-metric data were recorded on five competitive randomly selected plants in each line for sixteen traits.
Result: Number of fruit per plant and fruits yield was governed by non-additive gene action suggesting the advancement of the generation for selection to improve these traits. The parents floradade, arka meghali and EC-164563 were estimated to be best combiners for the inclusion in further breeding programs. The cross EC-620406 × EC-528360, a product of good combiners was best performing and can be used to obtain superior recombinants.
What Makes Agile Software Development Agile? Kuhrmann, Marco; Tell, Paolo; Hebig, Regina ...
IEEE transactions on software engineering,
09/2022, Letnik:
48, Številka:
9
Journal Article
Recenzirano
Odprti dostop
Together with many success stories, promises such as the increase in production speed and the improvement in stakeholders' collaboration have contributed to making agile a transformation in the ...software industry in which many companies want to take part. However, driven either by a natural and expected evolution or by contextual factors that challenge the adoption of agile methods as prescribed by their creator(s), software processes in practice mutate into hybrids over time. Are these still agile? In this article, we investigate the question: what makes a software development method agile? We present an empirical study grounded in a large-scale international survey that aims to identify software development methods and practices that improve or tame agility. Based on 556 data points, we analyze the perceived degree of agility in the implementation of standard project disciplines and its relation to used development methods and practices. Our findings suggest that only a small number of participants operate their projects in a purely traditional or agile manner (under 15 percent). That said, most project disciplines and most practices show a clear trend towards increasing degrees of agility. Compared to the methods used to develop software, the selection of practices has a stronger effect on the degree of agility of a given discipline. Finally, there are no methods or practices that explicitly guarantee or prevent agility. We conclude that agility cannot be defined solely at the process level. Additional factors need to be taken into account when trying to implement or improve agility in a software company. Finally, we discuss the field of software process-related research in the light of our findings and present a roadmap for future research.
The surveyed companies applied hybrid development approaches to specific projects even when company-wide policies for process usage existed. These approaches emerged from the evolution of different ...work practices and were consistently used regardless of company size or industry sector.
As the software industry transitions to a subscription-based software-as-a-service (SaaS) model, software development companies are transforming to hybrid development organizations with increased ...adoption of Agile and Continuous Integration/ Continuous Delivery (CI/CD) development practices for newer products while continuing to use Waterfall methods for older products. This transformation is a huge undertaking impacting all aspects of the software development life cycle (SDLC), including the quality management system. This paper presents a case study of a large-scale transformation of a legacy quality management system to a modern system developed and implemented at Cisco Systems. The framework for this transformation is defined by six distinct areas: metrics, process, measurement, reporting, quality analytics, and culture & leadership. Our implementation leveraged recent advances in Machine Learning (ML), Artificial Intelligence (AI), connected data, integrated operations, and big data technologies to solve the challenges created by a hybrid software development organization. We believe this case study will help researchers and industry leaders understand the benefits and potential challenges of such sizeable transformations.
•Hybrid development organizations are using waterfall and agile in different groups.•Transformation of quality management system needed to improve customer satisfaction.•Quality transformation for hybrid organizations include six different focus areas.•They are metrics, process, measurement, reporting, analytics, culture & leadership.•Use of machine learning and big data are required to accelerate this transformation.
Agile models are widely used in the software industry due to their unique features, such as quick response to requirement changes, reduced documentation and agility. SCRUM is one of the most useful ...agile models that offer a unique management technique to reduce the risk of rework, delay, and scheduling for a good quality product. However, the SCRUM model has certain limitations, such as lacks in engineering practice, fully depends upon customer, lacks in structured reviews. SCRUM is also in direct conflict with security engineering activity and techniques. SV-Model is a secure plan-driven method that encourages a proactive definition of security requirements. The SV-model is criticized of being inflexible and slow to respond to rapidly changing requirements. Although both models SV-Model and SCRUM contain good features and strengths but still there are improvement possibilities in these models. Keeping above mentioned context in view, this paper intends to propose a Hybrid SV-SCRUM Model by accommodating SCRUM management practices in the SV-Model to expedite product development. The biggest benefit of using SCRUM and SV-Model together is, SCRUM is an agile framework and SV-Model is a secure engineering methodology. This combination is primarily done to harness the qualities of the SV-model and reduce its weaknesses by incorporating the strengths of the SCRUM approach.
Recently, bombesin (BN) and its analogs have attracted much attention as excellent anticancer agents because they interact with specific receptors widely distributed on the surface of various cancer ...cells. However, their biological properties proceed far beyond this, given a broad spectrum of activity. Bombesin receptor ligands are effective drugs for the treatment of rheumatoid arthritis or gastrointestinal diseases. However, most diseases are complex, and the use of polytherapy may lead to pharmacokinetic and pharmacodynamic drug–drug interactions, resulting in side effects. Therefore, there is a need to develop effective compounds that also contain BN or its analogs, which are combined with other structural entities, thus generating a so-called hybrid drug. Hybrid drugs that contain bombesin pharmacophore(s) may be proposed as a solution to the problem of polytherapy or the lack of an effective cure. Such structures have now demonstrated the desired efficacy, though information on these aforementioned compounds is relatively scarce. Therefore, our paper aims to encourage researchers to focus on bombesins. Herein, we indicate that the hybrid approach should also be firmly applied to bombesins and the BN receptor family. This paper’s structure is divided into two main sections demonstrating bombesins and their properties, as well as recent data on bombesin-based hybrid compounds and their potential usefulness in medicine. Overall, it refers to the discovery and synthesis of modified bombesin-based hybrid compounds.
The number of companies that use agile methods increases steadily. However, these companies often do not implement a pure agile approach but combine agile and plan‐based methods to so‐called hybrid ...development approaches. However, the development of these approaches is rather difficult for the companies, since agile and plan‐based approaches often follow opposite concepts. To benefit from agile and plan‐based approaches at the same time, the companies have to identify and address the conflicts between agile and plan‐based methods. The conflicts depend on the goals that are pursued with the implementation of agile and plan‐based methods. However, there is no overview of the exact goals that are pursued in hybrid approaches and which challenges and conflicts arise with them. Therefore, we conducted a systematic mapping study to gather and analyze the goals and challenges in hybrid development approaches. The mapping study is focused on literature that presents the actual needs and goals of companies and projects. Based on our results, we present the influence factors that cause conflicts in hybrid approaches and discuss how these conflicts can be addressed.
This work investigates the goals that are pursued in hybrid approaches and how these goals are addressed in the context of a systematic mapping study. Further, it identifies conflicts and challenges that arise in hybrid approaches by a simultaneous use of agile and plan‐based methods for the same activity. In order to guide practitioners in the creation of hybrid approaches, the authors discuss how these conflicts can be addressed.
Mungbean (Vigna radiata L.) is a cleistogamous plant in which flowers are pollinated before they open, which prevents yield improvements through heterosis. We previously generated a chasmogamous ...mutant (CM) mungbean in which open flowers are pollinated. In this study, we developed insertion/deletion (indel) markers based on the transcriptome differences between CM and Sulu-1 (i.e., normal flowering) plants. An F2 population derived from a cross between CM and Sulu-1 was used for gene mapping. Segregation analyses revealed that a single recessive gene regulates the production of chasmogamous flowers. Using newly developed indel and simple sequence repeat markers, the cha gene responsible for the chasmogamous flower trait was mapped to a 277.1-kb segment on chromosome 6. Twelve candidate genes were detected in this segment, including Vradi06g12650, which encodes a YUCCA family protein associated with floral development. A single base pair deletion producing a frame-shift mutation and a premature stop codon in Vradi06g12650 was detected only in CM plants. This suggested that Vradi06g12650 is a cha candidate gene. Our results provide important information for the molecular breeding of chasmogamous mungbean lines, which may serve as new genetic resources for hybrid cultivar development.
Agile methodologies are sometimes adopted, with the assumption that benefits can be attained by only using a set of best practices, which can sometimes work to a degree. In this paper, a case is ...discussed where a software‐producing organization of seven teams achieved significant improvements. The goal of the research was to answer two questions: how an already agile organization could improve its performance further and what is the impact of promoting quality aspects? The questions were answered by implementing interventions based on prior literature and data emerging from semi‐structured interviews. The context was an established business with a complex revenue stream structure, meaning the mix of various project/service/product based work rendered the adoption of agile methods a challenge. Action research comprising three rounds of interventions was conducted to improve the organization and its quality culture while enforcing code review practices. Interventions resulted in a significant improvement in quality, as measured by reported defects. Therefore, it is suggested that agile methods are not sufficient on their own to take software business forward unless a quality‐focused culture is simultaneously achieved through a mindset change and organizational structures to enforce quality practices. The paper contributes to research on the managerial practices of software business and agile transformation by providing empirical support to introducing formal quality improvement to the agile mix as a method for practitioners to improve organizations with complex business models and multiple teams.
Agile transformations tend to ignore accompanying implementation of software quality or it is considered a developer skill rather than organizational practice. This paper presents an empirical investigation of improving a multi‐team organization. It is demonstrated that significant software defect reduction is possible with small quality related cultural and procedural changes. Further, it is suggested that existing agile organizations with complex business models can enhance performance through quality improvements.