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.

Traceable and Intelligent Supply Chain based on Blockchain and Artificial Intelligence

Smart manufacturing focuses on maximizing the capabilities to increase multiple objectives, like cost, delivery, and quality, in manufacturing enterprises. This requires implementing product development lifecycle, production system lifecycle, and business cycle for supply chain management. In short, a considerable amount of data is generated in a given manufacturing enterprise. Likewise, progress has been made to adopt blockchain in financial industries, but the adoption is slow in non-financial sectors. The article elaborates a methodology for the realization of a traceable and intelligent supply chain. First, the methodology elaborates on the realization of traceability of enterprise entities, which are an integral part of the supply chain. In this case, each participating stakeholder of the supply chain is required internally to realize a smart manufacturing system with an extension to write critical control data to the blockchain (i.e., a subset of process data). Artificial Intelligence (AI) is being adopted in most industries. A supply chain stakeholder has access to its data and can employ AI to derive new insights. The data available with the stakeholder provides a narrow context. With blockchain, all the stakeholders have access to the data from other stakeholders. Subsequently, the insights derived by a stakeholder will be more meaningful. This will assist in realizing an intelligent supply chain.

The Design and Development of the i-Jury Management System

Handling an event requires a repetitive and complex task; from initial preparation until its conclusion. One of the important elements in an innovation event is the jurying process. The jurying process usually involves tasks with higher priority and must be completed in limited duration, usually within 4 to 5 days. The inexistence of inexpensive jurying information systems leads to the development of the i-Jury management system (i-Jury). The i-jury management system was developed based on PHP programming language, MySQL database, and jQuery. The development of the information system follows the System Development Lifecycle methodology. The findings show that the development of the information system speeds up the process of managing jury, project management, as well as speeding up the disbursement of results, comparing to previous traditional evaluation methods

INVESTIGATING TRANSPORT INFRASTRUCTURE OBJECTS WITHIN THEIR SPATIAL DEVELOPMENT LIFECYCLE

Precise and detailed information for infrastructure assets, as well as information about the property interests attached to them are crucial to prevent unnecessary costs, disruptions, and delays when planning, constructing, and managing such objects. Various models encapsulating infrastructure objects information are available, mostly during their design stage, and could be also reused in other stages of the Spatial Development Lifecycle (SDL), such as the Land Registration. In this respect, and as ISO 19152:2012 Land Administration Domain Model is currently under revision, it is well-timed to consider the modelling of infrastructure objects within the scope of the upcoming Edition II of the standard. Given this background, the aim of this paper is to initiate the discussion on the registration options of infrastructure objects in the context of the LADM revision. Attention is given on specific categories of transport infrastructure objects, identifying the information required to be reused in other stages of the SDL, sourced from BIM/ IFC files used in the design stage. As currently IFC does not support infrastructure information, in order to investigate how such information is stored in IFC models based on the modellers’ decisions and the software used, two models of transport infrastructure objects coming from the industry were inspected and based on these findings, the conceptual modelling followed, based on the LADM concept. The paper aims to provide insights on to the limitations of the current use of IFC for transport infrastructure objects and propose the future steps to overcome them.

A hybrid threat model for system-centric and attack-centric for effective security design in SDLC

Threat modeling is an essential activity in the security development lifecycle. To provide security at the design phase of software development, Microsoft introduced threat modeling stride to identify the vulnerabilities and attacks of application. An efficient solution is necessary to deal with these issues in the software development life cycle. In this context, the paper focused on the analysis of threats and attack tree techniques that are traditionally available and frequently used. Automated Threat modeling enables to simulate attacks and visualized the existing vulnerabilities and misconfiguration. A hybrid model is proposed based on system-centric and attacker-centric to identify the threats in the software application during the software design phase. This model is built by STRIDE by defining security architecture and then analyzed the risks regarding its security characteristics and applied to its real application system. Our model is applied in a case study of the health center management system and shows a better result is identifying the threats and severity in the design phase. And also attack tree defines the stages of threats to understand the severity.

Implementasi Electronic Customer Relationship Management menggunakan Metode Framework of Dynamic berbasis Web

The purpose of this study is to build soft devices for electronic customer relationship management (e-CRM) with the Framework of Dynamic method which will facilitate customer relationship management that can help relationships between stores and customers so that customers can enjoy and feel comfortable with the store services that can eventually be formed. In implementing this software, the author uses the system development lifecycle (SDLC) method then produces a web-based e-CRM prototype with PHP programming languages and MySQL DBMS. This e-CRM prototype has been tested in terms of verification, validation, and prototype testing. To design this system Use Cases, ERD, LRS, Class Diagrams, and Sequence Diagrams are used. From the test results, it can be seen that the e-CRM prototype has been successful and is in accordance with the planning objectives. The result of this Marketplace Design is as a forum to make it easier for shop owners in the field of Building Materials and the like to market the products they have here.Keywords:e-CRM, Framework of Dynamic CRM, Customer, System Development Life Cycle.