A Simulation Model for Application Development in Data Warehouses

Software development projects have been blamed for being behind schedule, cost overruns, and the delivery of poor quality product. This paper presents a simulation model of a data warehouse to evaluate the feasibility of different software development controls and measures to better manage a software development lifecycle, and improve the performance of the launched software. This paper attempts to address the practical issue of code defects in each stage of data warehouse application development. The author has compared the defect removal rate of their previous project to the newly proposed enhanced project development life cycle that uses code inspection and code scorecard along with other phases of software development life cycle. Simulation results show that the code inspection and code score-carding have achieved a significant code defect reduction. This has also significantly improved the software development process and allowed for a flawless production execution. The author proposes this simulation model to a data warehouse application development process to enable developers to improve their current process.

Software Testing Under Agile, Scrum, and DevOps

The adoption of agility at a large scale often requires the integration of agile and non-agile development practices into hybrid software development and delivery environment. This chapter addresses software testing related issues for Agile software application development. Currently, the umbrella of Agile methodologies (e.g. Scrum, Extreme Programming, Development and Operations – i.e., DevOps) have become the preferred tools for modern software development. These methodologies emphasize iterative and incremental development, where both the requirements and solutions evolve through the collaboration between cross-functional teams. The success of such practices relies on the quality result of each stage of development, obtained through rigorous testing. This chapter introduces the principles of software testing within the context of Scrum/DevOps based software development lifecycle.

Weaving Security into DevOps Practices in Highly Regulated Environments

In this article, the authors discuss enhancing a DevOps implementation in a highly regulated environment (HRE) with security principles. DevOps has become a standard option for entities seeking to streamline and increase participation by all stakeholders in their Software Development Lifecycle (SDLC). For a large portion of industry, academia, and government, applying DevOps is a straight forward process. There is, however, a subset of entities in these three sectors where applying DevOps can be very challenging. These are entities mandated by security policies to conduct all, or a portion, of their SDLC activities in an HRE. Often, the reason for an HRE is protection of intellectual property and proprietary tools, methods, and techniques. Even if an entity is functioning in a highly regulated environment, its SDLC can still benefit from implementing DevOps as long as the implementation conforms to all imposed policies. A benefit of an HRE is the existence of security policies that belong in a secure DevOps implementation. Layering an existing DevOps implementation with security will benefit the HRE as a whole. This work is based on the authors extensive experience in assessing and implementing DevOps across a diverse set of HREs. First, they extensively discuss the process of performing a DevOps assessment and implementation in an HRE. They follow this with a discussion of the needed security principles a DevOps enhanced SDLC should include. For each security principle, the authors discuss their importance to the SDLC and their appropriate placement within a DevOps implementation. They refer to a security enhanced DevOps implementation in an HRE as HRE-DevSecOps.

Generation and Visualization of Static Function Call Graph for Large C Codebases

As software systems evolve, there is a growing concern on how to manage and maintain a large codebase and fully understand all the modules present in it. Developers spend a significant amount of time analyzing dependencies before making any changes into codebases. Therefore, there is a growing need for applications which can easily make developers comprehend dependencies in large codebases. These applications must be able to analyze large codebases and must have the ability to identify all the dependencies, so that new developers can easily analyze the codebase and start making changes in short periods of time. Static analysis provides a means of analyzing dependencies in large codebases and is an important part of software development lifecycle. Static analysis has been proven to be extremely useful over the years in their ability to comprehend large codebases. Out of the many static analysis methods, this paper focuses on static function call graph (SFCG) which represents dependencies between functions in the form of a graph. This paper illustrates the feasibility of many tools which generate SFCG and locks in on Doxygen which is extremely reliant for large codebases. The paper also discusses the optimizations, issues and its corresponding solutions for Doxygen. Finally, this paper presents a way of representing SFCG which is easier to comprehend for developers.

A Comparison on Continuous Integration and Continuous Deployment (CI/CD) on Cloud Based on Various Deployment and Testing Strategies

Continuous Integration/Continuous Delivery/Deployment (CI/CD) emphasizes the rapid release of small, incremental changes and the use of automation throughout the development process. CI/CD technique is central to DevOps and key to its success. Consumers expect to have continuous interaction with DevOps team so that they can provide their continuous feedback. DevOps is blending of two terms: development and operations which aims to provide conjoin approach to industry’s software development and operation team job in software development lifecycle. Continuous practices, i.e., continuous integration, delivery, and deployment, are the software development industry practices that enable organizations to frequently and reliably release new features and products. Shows the comparison on deployments. With the increasing interest in literature on continuous practices, it is important to systematically review and synthesize the approaches, tools, challenges, and practices reported for adopting and implementing continuous practices.

Penguatan Promosi Melalui Media Website pada Hotel Alvina Pematangsiantar

The partner in the Community Service Program (PkM) is Hotel Alvina Pematangsiantar. Seeing the need for Hotel Alvina for the use of information technology that seems not optimal, especially in supporting media ads platform. To support a better promotion, it is necessary to have a website that can increase the capacity of promotion and visitors. The implementation of the PkM program refers to a qualitative approach and is combined with the stages in the Software Development Lifecycle which have been modified into 6 stages, starting from initiation, design, data migration, development, implementation, and maintenance. The resulting website can be used by Hotel Alvina to manage hotel information, such as contact us, about us, blogs, and galleries. The website is also supported by online reservation facilities that can be used by visitors. The website that has been successfully implemented is expected to increase services and promotions for Hotel Alvina, so that it can compete and develop in a sustainability.

ANALISA DAN PERANCANGAN SISTEM INFORMASI JADWAL PERKULIAHAN (SIJADKUL) MENGGUNAKAN WEB PADA STMIK ROSMA

Abstrak Perkembangan teknologi informasi dan komunikasi memberikan sesuatu yang bermanfaat berupakemudahan dalam informasi-informasi yang dibutuhkan. Suatu perusahaan atau instansi perlumenerapkan sistem informasi dalam kegiatan mereka berjalan dengan baik dan sesuai keinginan yangsemestinya. Pengaturan jadwal perkuliahan adalah merupakan suatu kegiatan yang dilakukan olehBAAK yang selama ini dilakukan secara manual, dan distribusi jadwal perkuliahan kepadamahasiswa dan dosen pun dirasa kurang efektif. Sistem Informasi Jadwal Perkuliahan menggunakanweb di harapkan mampu dalam pembuatan jadwal dan distribusi jadwal ke dosen dan mahasiswaTahapan pengembangan peneilitian ini dengan menggunakan metode Software Development LifeCycle (SDLC) yaitu tahap analisa, desain dan implentasi. Tools yang digunakan pada penelitian iniadalah Notepad++ dan MySQL sebagai databasenya. Hasil analisis ini diharapkan dapat membantubagian Akademik (BAAK) dalam membuat jadwal kuliah.