Lakshmi Srinivasa Rao Gogula highlights that SAP Business Technology Platform (BTP) is revolutionizing enterprise software by enhancing agility, integration, security, developer empowerment, and sustainability beyond traditional ABAP.

Honeywick, a local, full-service web design, development, and marketing agency, has expanded to a new space in the heart of downtown Louisville at 225 S 5th Street, #201, Louisville, KY 40202, after being located in the Glassworks building since 2016.

Software start-ups generally use development practices that are adapted to their agile and innovative environment. However, these practices, although consolidated, may not be the best ones for a specific context. This paper aims to present a set of guidelines for software development in start-ups. It also aims to show the results of three studies to validate and refine the proposed guidelines: a confirmatory survey, a focus group, and an expert panel. The participants were actors from both the industry and the academia. The results revealed that the guidelines obtained a positive perception from the participants of both contexts. Based on their approval, we can infer that those guidelines can increase the quality of products generated by start-ups and the chances of success for these organisations. Besides, the need for some improvements has been identified, and they will be implemented in the next version of the guidelines.

A number of studies have applied social network analysis (SNA) to show that the patterns of social interaction between software developers explain important organisational outcomes. However, these insights are based on a single network relation (i.e., uniplex social ties) between software developers and do not consider the multiple network relations (i.e., multiplex social ties) that truly exist among project members. This study reassesses the understanding of software developer networks and what it means for performance in software development settings. A systematic review of SNA studies between 1990 and 2020 across six digital libraries within the IS and management science domain was conducted. The central contributions of this paper are an in-depth overview of SNA studies to date and the establishment of a research agenda to advance our knowledge of the concept of multiplexity on how a multiplex perspective can contribute to a software developer's coordination of tasks and performance advantages.

Aim/Purpose: This research aims to describe layering of career-like experiences over existing curriculum to improve perceived educational value. Background: Feedback from students and regional businesses showed a clear need to increase student’s exposure to career-like software development projects. The initial goal was to develop an instructor-optional project that could be used in a single mid-level programming course; however, the pilot quickly morphed into a multi-year study examining the feasibility of agile projects in a variety of settings. Methodology: Over the course of four years, an agile project was honed through repeated Design Based Research (DBR) cycles of design, implementation, testing, communication, and reflective analysis. As is common with DBR, this study did not follow single methodology design; instead, analysis of data coupled with review of literature led to exploration and testing of a variety of methodologies. The review phase of each cycle included examination of best practices and methodologies as determined by analysis of oral and written comments, weekly journals, instructor feedback, and surveys. As a result of participant feedback, the original project was expanded to a second project, which was tested in another Software Engineering (SE) course. The project included review and testing of many academic and professional methodologies, such as Student Ownership of Learning, Flipped Classroom, active learning, waterfall, agile, Scrum, and Kanban. The study was homogenous and quasi-experimental as the population consisted solely of software engineering majors taking required courses; as based on validity of homogenous studies, class sizes were small, ranging from 8 to 20 students. Close interactions between respondents and the instructor provided interview-like settings and immersive data capture in a natural environment. Further, the iterative development practices of DBR cycles, along with the inclusion of participants as active and valued stakeholders, was seen to align well with software development practitioner practices broadly known as agile. Contribution: This study is among the first to examine layering a career-like software development project on top of a course through alteration of traditional delivery, agile development, and without supplanting existing material. Findings: In response to industry recommendations for additional career-like experiences, a standalone agile capstone-like project was designed that could be layered over an existing course. Pilot data reflected positive perceptions of the project, although students did not have enough time to develop a working prototype in addition to completing existing course materials. Participant feedback led to simultaneous development of a second, similar project. DBR examination of both projects resulted in a simplified design and the ability to develop a working prototype, if and only if the instructor was willing to make adjustments to delivery. After four years, a solution was developed that is both stable and flexible. The solution met the original charge in that it required course delivery, not course material, to be adjusted. It is critical to note that when a working prototype is desired, a portion of the lecture should be flipped allowing more time for guided instruction through project-focused active learning and study group requirements. The results support agile for standalone software development projects, as long as passive delivery methods are correspondingly reduced. Recommendations for Practitioners: Based on the findings, implementation of a career-like software development project can be well received as long as active learning components are also developed. Multiple cycles of DBR are recommended if future researchers wish to customize instructional delivery and develop complex software development projects. Programming instructors are recommended to explore hybrid delivery to support development of agile career-like experiences. Small class sizes allowed the researchers to maintain an interview-like setting throughout the study and future studies with larger classes are recommended to include additional subject matter experts such as graduate students as interaction with a subject matter expert was highly valued by students. Recommendation for Researchers: Researchers are recommended to further examine career-like software development experiences that combine active learning with agile methods; more studies following agile and active learning are needed to address the challenges faced when complex software development is taught in academic settings. Further testing of standalone agile project development has now occurred in medium sized in person classes, online classes, independent studies, and creative works research settings; however, further research is needed. Future research should also examine the implementation of agile projects in larger class sizes. Increasing class size should be coupled with additional subject matter experts such as graduate students. Impact on Society: This study addresses professional recommendations for development of agile career-like experiences at the undergraduate level. This study provides empirical evidence of programming projects that can be layered over existing curriculum, with no additional cost to the students. Initial feedback from local businesses and graduates, regarding agile projects with active learning, has been positive. The area business that refused to hire our underprepared SE graduates has now hired several. Future Research: Future research should explore layering agile projects over a broader range of software development courses. Feedback from hiring professionals and former students has been positive. It is also recommended that DBR be used to develop career-like experiences for online programming courses.

Aim/Purpose: The teaching of appropriate problem-solving techniques to novice learners in undergraduate software development education is often poorly defined when compared to the delivery of programming techniques. Given the global need for qualified designers of information technology, the purpose of this research is to produce a foundational template for an educational software development methodology grounded in the established literature. This template can be used by third-level educators and researchers to develop robust educational methodologies to cultivate structured problem solving and software development habits in their students while systematically teaching the intricacies of software creation. Background: While software development methodologies are a standard approach to structured and traceable problem solving in commercial software development, educational methodologies for inexperienced learners remain a neglected area of research due to their assumption of prior programming knowledge. This research aims to address this deficit by conducting an integrative review to produce a template for such a methodology. Methodology: An integrative review was conducted on the key components of Teaching Software Development Education, Problem Solving, Threshold Concepts, and Computational Thinking. Systematic reviews were conducted on Computational Thinking and Software Development Education by employing the Preferred Reporting Items for Systematic Reviews and Meta-Analyses (PRISMA) process. Narrative reviews were conducted on Problem Solving and Threshold Concepts. Contribution: This research provides a comprehensive analysis of problem solving, software development education, computational thinking, and threshold concepts in computing in the context of undergraduate software development education. It also synthesizes review findings from these four areas and combines them to form a research-based foundational template methodology for use by educators and researchers interested in software development undergraduate education. Findings: This review identifies seven skills and four concepts required by novice learners. The skills include the ability to perform abstraction, data representation, decomposition, evaluation, mental modeling, pattern recognition, and writing algorithms. The concepts include state and sequential flow, non-sequential flow control, modularity, and object interaction. The teaching of these skills and concepts is combined into a spiral learning framework and is joined by four development stages to guide software problem solving: understanding the problem, breaking into tasks, designing, coding, testing, and integrating, and final evaluation and reflection. This produces the principal finding, which is a research-based foundational template for educational software development methodologies. Recommendations for Practitioners: Focusing introductory undergraduate computing courses on a programming syllabus without giving adequate support to problem solving may hinder students in their attainment of development skills. Therefore, providing a structured methodology is necessary as it equips students with essential problem-solving skills and ensures they develop good development practices from the start, which is crucial to ensuring undergraduate success in their studies and beyond. Recommendation for Researchers: The creation of educational software development methodologies with tool support is an under-researched area in undergraduate education. The template produced by this research can serve as a foundational conceptual model for researchers to create concrete tools to better support computing undergraduates. Impact on Society: Improving the educational value and experience of software development undergraduates is crucial for society once they graduate. They drive innovation and economic growth by creating new technologies, improving efficiency in various industries, and solving complex problems. Future Research: Future research should concentrate on using the template produced by this research to create a concrete educational methodology adapted to suit a specific programming paradigm, with an associated learning tool that can be used with first-year computing undergraduates.

Agile global software development (AGSD) is an increasingly prevalent software development strategy, as organizations hope to realize the benefits of accessing a larger resource pool of skilled labor, at a potentially reduced cost, while at the same time delivering value incrementally and iteratively. However, the distributed nature of AGSD creates geographic, temporal, socio-cultural distances that challenge collaboration between project stakeholders. The Cloud Computing (CC) service models of Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS) are similar to the aspirant qualities of AGSD as they provide services that are globally accessible, efficient, and stable, with lower predictable operating costs that scale to meet the computational demand. This study focused on the 12 agile principles upon which all agile methodologies are based, therein potentially increasing the potential for the findings to be generalized. Domestication Theory was used to assist in understanding how cloud technologies were appropriated in support of AGSD. The research strategy took the form of case study research. The findings suggest that some of the challenges in applying the agile principles in AGSD may be overcome by using CC.

Aim/Purpose: This paper aims to describe how various Kanban elements can help alleviate two prominent types of challenges, communication and collaboration in Global Software Development (GSD). Background: Iterative and Lean development methodologies like Kanban have gained significance in the software development industry, both in the co-located and globally distributed contexts. However, little is known on how such methodologies can help mitigate various challenges in that occur in a globally distributed software development context. Methodology: The study was conducted using a single-case study based on a general inductive approach to analysis and theory development. Through the literature review, collaboration and communication challenges that GSD teams face were identified. Data collected through semi-structured interviews was then inductively analyzed to describe how the case-study teams employed various Kanban elements to mitigate communication and collaboration challenges they face during GSD. Findings: The study found that some Kanban elements, when properly employed, can help alleviate collaboration and communication challenges that occur within GSD teams. These relate to Inclusion Criteria, Reverse Items, Kanban Board, Policies, Avatars, and Backlog. Contribution: The paper contributes to knowledge by proposing two simple concept maps that detail the specific types of communication and collaboration challenges which can be alleviated by the aforementioned Kanban elements in GSD. Recommendations for Practitioners: This paper is relevant to GSD teams who are seeking ways to enhance their team collaboration and communication as these are the most important elements that contribute to GSD project success. It is recommended that relevant Kanban elements be used to that effect, depending on the challenges that they aim to alleviate. Future Research: Future research can investigate the same research questions (or similar ones) using a quantitative approach.

Current initiatives aim to improve the Snap One's cloud infrastructure to support the growth of remote monitoring, ensure all backend systems are scalable for the future, resolve bugs, maintain and expand interoperability, and develop new features and experiences.

Matt St. Onge is lauded for his contributions to secure embedded systems and open source technology

Richard J. Malina is a leading expert in real-time embedded software for complex machinery missiles and weapons

Julia Kindelsberger channels years of expertise to her work with Oracle

Nina Mushiana is a seasoned Engineering Management expert with 20+ years in site reliability, information security, and service management

Patrick M. Watson is an expert in mobile applications and the CEO of Life Hack Innovations, where he leads the development of advanced mobile solutions for Fortune 500 companies.

BrainerHub Solutions attains ISO 9001 & ISO 27001 certifications, reinforcing our dedication to quality and security in software development.

Godwin Sevor is a distinguished expert in development operations engineering with Perceptyx Inc.

Nermine Aladdin Mahmoud is a Computer Science instructor at the Southern Alberta Institute of Technology

Brian Theory lends years of expertise to his work with NASA

Tarang Bhargava serves as a senior software development engineer at SAP Concur

By enabling greater productivity and accelerated software development timelines, no code/low code is on the rise.

Before the turn of the new millennium, development teams could get away with supporting two platforms: Windows and the web. Today, there are dozens, with more created monthly. As a result, teams struggle to manage vendor, device, and platform fragmentation. To fully realize the potential of virtual reality, the Internet of Things, and other platforms […]

The post The future of software development Is automation first appeared on TECH Intelligence and is written by Aidan Cunniffe.

The rise of distributed software teams has fundamentally transformed how we approach software development. With technology evolving, so does our ability to connect and collaborate across borders, time zones, and cultural barriers. The article will venture into the fascinating world of distributed software development and provide you with the most effective strategies and best practices […]

The post Making Distributed Software Development Work: Strategies and Best Practices for Managing Remote Teams appeared first on 404 Tech Support.

Sophia Antipolis, 2 February 2023

ETSI, the organization for globally applicable standards for information and communication technology (ICT), has adopted a new instrument, Software Development Groups (SDGs). This game-changing move will help ETSI adapt to the ever-evolving landscape of technology and standards development. Developing software to accompany standards will accelerate the standardization process, providing faster feedback loops and improving the quality of standards.

Read More...

Sophia Antipolis, 25 July 2023

ETSI is proud to announce the establishment of its first Software Development Group, called OpenSlice. With this group, ETSI positions itself as a focal point for development and experimentation with network slicing.

Read More...

Sophia Antipolis, 9 November 2023

ETSI is delighted to announce the establishment of a new Software Development Group, called OpenCAPIF. OpenCAPIF is developing an open-source Common API Framework, as defined by 3GPP, allowing for secure and consistent exposure and use of APIs.

Read More...

In this Episode, Eberhard and Markus provide an introduction to Model-Driven Software Development. Since the discussion turned out to be too long, we separated things into two episodes, thus Episode 6 will be the second part of this discussion. In this first part we disucsss core concepts of MDSD, the relationship to MDA, and hint at a couple of tools.

After discussing some of the more technical aspects of MDSD in the last episode, we take a look at other important topics in this one. This includes some tips on how to introduce MDSD into projects and how the development process has to be adapted for this to work, as well as a look at the return on investment for MDSD. The relationship of MDSD and Agile software development is also discussed. Finally, we take a look at offshoring in the context of MDSD.

Michael and Markus discuss what makes a good R&D manager and how to potentially become an R&D manager. You will learn what some of the essential skills are, what the challenges are, and what the 'mission/vision/strategy thing' is actually good for.

In this episode Michael talks with Bas Vodde about how to apply agile principles to large and distributed development organizations.

Sven Apel explains why developing software in a feature-oriented manner is so vital for us as software engineers and why objects are simply not enough.

Recording Venue: University of Passau Guest: Sven Apel Host: Stefan In this second episode on Feature-Oriented Software Development (FOSD), Sven Apel gives us an overview of programming language and tool support for FOSD. He introduces the Eclipse-based FeatureIDE which covers important phases of the FOSD process, namely domain implementation as well as configuration and generation. […]

Ryan Singer on Basecamp’s “Shape Up” software development process. Basecamp has ditched the backlog and 2-week sprint in favor of solution “shaping” and strategic 6-week projects, using tools like scope mapping, checklists, and hill charts to understand and reduce risk.

Wouter Groeneveld, author of The Creative Programmer and PhD researcher at KU Leuven, discusses his research related to programming education with host Jeremy Jung. Topics include evaluating projects, constraints, social debt in teams, common fallacies in critical thinking, maintaining flow state, documenting and retaining knowledge, and creating environments that encourage creativity. Brought to you by IEEE Software and IEEE Computer Society.

The community panel closes out the discussion with a look at the interplay between developers and architects, and the evolving nature of both roles.

There is little in our lives that does not rely on software. That has been the reality for quite some time, and it will be even more true as self-driving cars and similar technologies become an even greater part of our lives. But as our reliance on software grows, so does the potential for disaster as software becomes increasingly complex.

In September 2017 The Atlantic magazine featured “The Coming Software Apocalypse,” an article by James Somers, that offers a fascinating and sobering look at how rampant code complexity has caused massive failures in critical software systems, like the 2014 incident that left the entire state of Washington without 911 emergency call-in services until the problem was traced to software running on a server in Colorado.

One of the people interviewed in that Atlantic article was Chris Newcombe, an expert in dealing with software complexity. Chris, an architect on the Oracle Bare Metal infrastructure as a service team,  is one of the panelists for the discussion you are about to hear. Chris is joined by Java Champion and microservices expert Chris Richardson, Java Champion Adam Bein, and Oracle ACE Director and Developer Champion Lucas Jellema. The conversation focuses on what developers can do to combat complexity.

Here are some photos, stories, and lessons I've collected over the years building Open Source software development communities at Sun Microsystems, Oracle, and on my own. I like taking photos and I like talking to developers — it's how I learn. So in this comprehensive commentary I talk about pretty much everything I've learned during the previous 15 years or so doing community development. Everything I've learned I still use today.

You can follow along with the photos below or view the video. I gave an earlier version of this talk at the All India Oracle User Group's (AIOUG) virtual OG Yatra in 2020, and I've talked about bits and pieces of the content in many other presentations. That's why I wanted to bring it all together into a single narrative centered around some specific images and stories. Hope it hangs together. 

Podcast Host: Jim Grisanzio, Oracle Developer Relations

https://twitter.com/jimgris
https://developer.oracle.com/team/ 

Photos

https://jimgrisanzio.files.wordpress.com/2021/07/grisanzio-community-stories.pdf

Video

https://youtu.be/nzo0PYv4tUM

Article

https://jimgrisanzio.wordpress.com/building-communities/

All India Oracle User Group OGYatra 2020 Slides

https://jimgrisanzio.files.wordpress.com/2020/06/2020-grisanzio-ogyatra.pdf

All India Oracle User Group OGYatra 2020 Video

https://youtu.be/gz7nMtWaUB0

Oracle Developer Relations Social

https://twitter.com/jimgris

https://twitter.com/groundbreakers

https://twitter.com/oracleace

https://twitter.com/oracleugs

https://developer.oracle.com/

"With Low-code, no-code it's no different than your standard traditional coding. You still have the ability to scan the code, said Jerry Hingtgen.

The post What’s behind a software development strategy at the Agriculture Department first appeared on Federal News Network.

Rivian and Volkswagen Group have finalized a multi-billion-dollar joint venture to develop software, paving the way to let the German auto giant leverage the EV startup’s more technical chops in the coming years. Volkswagen will invest up to $5.8 billion by 2027, about 16% more than when the deal…

A Brief History of DevOps To understand the future of DevOps, it’s worth understanding its past—which I can recall with a level

The post DevOps, LLMs, and the Software Development Singularity appeared first on Gigaom.

Company: Microchip Technology India Private Limited
Experience: 2 to 5
location: Bengaluru / Bangalore
Ref: 24828664
Summary: Job Description Early-career Full Stack Development Engineer opening based in Bangalore, India to be a key contributor in the development effort of our next generation common automated test framework and ....

Company: Microchip Technology India Private Limited
Experience: 4 to 5
location: India
Ref: 24828663
Summary: Job Description r Responsibilities * DCS Embedded System Test Automation Team * Key contributor in the Quality Assurance effort of MCHP DCS storage products * Design and develop common automation framework....