Gaming DevSecOps - A Serious Game Pilot Study

Security affects every software component in different types of computing systems. Many vulnerabilities and attacks on software systems are due to security weaknesses in the software itself. During the process of software specification, development, or testing, security issues are either taken into consideration insufficiently or not at all. Such software, due to internal weaknesses is prone to new attacks. By teaching secure software engineering techniques for designing and developing software modules, students would learn systematic secure software development techniques, such as defect detecting and security testing. This paper presents a series of modules that are designed to be integrated into undergraduate software engineering courses from a security perspective. The goal of the modules is to teach the building of robust software security requirements, secure software design and development, and secure software verification through a secure software development lifecycle.

A modern approach to graduate flight dynamics, stability, and control courses

Many undergraduate IT programs recognize that their graduates will find jobs as software developers. As such, software development (analysis and design) courses are often a core requirement of IT undergraduate degree programs. This paper presents an analysis and comparison of the content of software development courses at several colleges and universities. In particular, the software development methodologies presented in the courses are examined. The comparison is based on two main criteria; the development methodologies presented through the textbook assigned to the class, and the development methodologies presented through the class lectures.A software development methodology is "a recommended collection of phases, procedures, rules, techniques, tools, documentation, management, and training used to develop a system" (Avison 2003). There are hundreds of software development methodologies. An ongoing debate has existed for several years as to what methodology is best. Prior research has shown that no methodology is best all the time and that practitioners are modifying methodologies to suit their needs. This research shows that IT software development courses have not been modified to reflect current trends in the practical application of development methodologies and students may not be learning the tools and techniques that they need to become successful practitioners. Key inadequacies and the associated pedagogical significance are discussed.

Software development productivity, code quality, and knowledge sharing have all increased dramatically with the use of AI code assistants like GitHub Copilot. These technologies provide real-time suggestions, expedite workflows, and speed up prototyping by utilising massive language models that have been trained on extensive code repositories. However, serious questions about software security, developer dependency, and ethical ramifications are brought up by their increasing use. The advantages and disadvantages of AI code helpers for safe software development are discussed in this study. It highlights how crucial human oversight, frequent security audits, ongoing model upgrades, and conformity to DevSecOps and OWASP guidelines are. In the end, software integrity cannot be jeopardised by including AI into development processes. In an increasingly automated development context, strategic implementation is crucial to maximising AI's benefits while protecting against new risks.

In todays world, software security has become essential for protecting the overall organizations operations. Mostly software development companies are adopting various strategies to build secure software to cope with the challenges of the client organization. Information become threatened due to connection with the cyber world, and it requires better security mechanisms. Software development organizations are receiving pressure from their clients to focus on the enhancement of security during the whole software development life cycle (SDLC). This protocol aims to review the literature in a systematic way to identify the state-of-the-art of software security to be considered by Global Software Development (GSD) vendor organizations during the development of a secure software as it evolves from requirements engineering to its final disposal. In order to improve security processes in the context of software development, our current research developed a Systematic Mapping Study (SMS) protocol. Presently, we are in the implementation phase of the protocol for the development of secure software. The expected outcomes of this SMS will be a list of security measurements and their solutions to be incorporated by GSD vendor organizations in each phase of the SDLC. This will also give a direction for new research in this area.

Putting Requirements and Quality at the Core of Global Service Delivery: Current Efforts and Future Plans at Pace University

This article describes a simple two-player game which illustrates basic concepts of brinkmanship, to include calculations of probability and expected outcomes, and risk-taking profiles. The game befits a single 50-minute class period with introduction, gameplay, and discussion. The game can supplement the study of conflict from classic Cold War case studies of crisis bargaining, to arms control, or negotiating international protocols for global climate change such as the Paris Agreement. The Brinkmanship Game was developed for the seventh week of a 10-week graduate course called Game Theory and Decisionmaking: Exploring Strategic Situations. The course features a flipped classroom with class time devoted to experimentation, gameplay, and discussion of readings and games; lectures are online. The Brinkmanship Game would be appropriate for students in any advanced undergraduate or graduate level course in international relations, security studies, negotiation, or game theory. The Brinkmanship Game provides an active learning opportunity that can be valuable for encouraging students to come to their own understanding of concepts of mutual risk-taking. The authors have found the game to be effective in the classroom and hope it may prove valuable to those searching for ways to motivate students and to help them learn.

Mastering concepts on power electronics and motor drives can be very challenging for many students. In order to deliver the concepts successfully hardware based learning tools are frequently used in undergraduate and graduate level courses. But most of these tools fall below expectations due to their complexity, lack of functionality or cost. This paper presents a learning tool on motor drives which addresses most of these issues. This proposed learning tool has the capability to deliver effective learning experiences on different types of motors discussed in advanced driving courses. The learning tool comes with user software which provides additional functionalities, such as the ability to manipulate closed loop variables, monitor real time speed variation, control firing patterns, log data and program the motor speed variation. The proposed learning tool is ideal to be incorporated in lab sessions to deliver important concepts in motor drives effectively and efficiently.

As more and more software applications are directly or indirectly accessible from the Internet, the importance of the security of these applications grows steadily. Hence, it is important that university curricula for computer scientists and software engineers include courses on secure software development. Such courses should make students familiar with the programming language technology, run-time support and available APIs for security, and they should also teach them how to use these technological means appropriately. The .NET framework is a good example of the current state-of-the-art support for secure development. The Shared Source Common Language Infrastructure (SSCLI) provides a source for some of the security related aspects of the framework. The paper describes how the secure software development course at the Katholieke Universiteit Leuven uses the .NET framework and the SSCLI. An overview is given of the contents of the course, and a number of example project assignments based on .NET or the SSCLI are presented.

Software development communities have made the true venture to software development through the concept of component-based software approach and commercial off-the-shelf (COTS). Majority of the present software applications have software components as the basic elements, and component-based software development (CBSD) has been successful in building applications and systems. However, the security of CBS for the software component is still not properly noticed. Developing secure software is the accountability of all the stakeholders involved with component-based software development model. The main challenge is to access how much security we have achieved or how can we predict and evaluate the security at the early stage of software development? Software security has a very constructive impact on software productivity, maintainability, cost, and quality. Therefore, more early we introduce and evaluate security into component-based software more productivity and quality we can achieve. In this paper, efforts are done to provide some suitable guiding principle to the software engineers in the development of secure component-based software products. This paper also discusses the overview of requirement specification and analyzes the software architectures and design for developing secure component-based software products.

Secure software development: a prescriptive framework

Costume in Motion is a guide to all stages of the collaboration process between costume designers and choreographers, documenting a wide range of approaches to the creation of a dance piece. Featuring interviews with a diverse selection of over 40 choreographers and designers, in-depth case studies of works by leading dance companies, and stunning original photography, the book explores the particular challenges and creative opportunities of designing for the body in motion. Filled with examples of successful collaborations in contemporary and modern dance, as well as a wide range of other styles, Costume in Motion provides costume designers and choreographers with a greater understanding of the field from the other’s perspective. The book is designed to be part of the curriculum for an undergraduate or graduate level course in costume design or choreography, and it can also be an enriching read for artists at any stage of their careers wishing to hone their collaboration skills in dance.

There has been a surge in number of software security threats and vulnerabilities in recent times. At the same time, expectations towards software and data security are growing. Thus there is a need to ensure that security-related tasks are effectively integrated in the software development process. However, integrating security practices with agile software development is not trivial due to, for instance, differences in process dynamics and concentration on functional vs non-functional requirements. In this short paper we present a literature review on challenges and solutions when adopting security in agile software development contexts. Our findings show that there are ongoing efforts to integrate security-practices in agile methods, but more research is needed to make the processes more optimized and simpler for developers.

The development of secure software could be simplified if tooling were readily available to application developers. Improvements can be made to better support software developers to secure their applications, without requiring that security code be inserted throughout core application processing code. The Aclamate framework is introduced here for securing software that imposes little restrictions on the writing of software. Aclamate uses AOSD to secure applications in a non-invasive manner. Both the existing state of software security frameworks and what support already exists to assist application development are discussed. Emphasis is placed on access control and authorization - as these areas are particularly lacking with security tooling to support software development in a non-invasive manner. Finally, there is a critique of Aclamate, the challenges remain in its development, and the remaining opportunities that may exist to provide application developers with more tools to ease the development of secure software

When working with software security in a risk-centric way, development projects become equipped to make decisions on how much security to include and what type of security pays off. This article presents the results of a study made among 23 public organisations, mapping their risk-centric activities and practices, and challenges for implementing them. The authors found that their software security practices were not based on an assessment of software security risks, but rather driven by compliance. Additionally, their practices could in many cases be characterised as arbitrary, late and error driven, with limited follow up on any security issues throughout their software development projects. Based on the results of the study, the authors identified the need for improvements in three main areas: responsibilities and stakeholder cooperation; risk perception and competence; and, practical ways of doing risk analysis in agile projects.