Software Shipping Time Estimation for Markovian Change-Point Reliability Model

A Markovian software reliability model is known as one of the useful models which enable us to describe the details on the dynamic behavior of software reliability growth process with imperfect debugging activities. As the application of this model for software development management, we discuss software shipping time estimation based on the extended Markovian software reliability model considering with the effect of change-point, which is the testing-time when the characteristic of the software failure-occurrence or fault-detection phenomenon changes notably. Especially in our discussion on the software shipping time estimation, we derive an analytical software shipping policy under certain software reliability objective and show numerical examples of the application of the software shipping policy by using actual software reliability data. Finally, we give some useful consideration on the relationship between the software shipping time and the software reliability growth process for conducing quality-oriented software development management.

Studi Literatur Penerapan Scrum Framework untuk Meningkatkan Produktivitas Pembuatan Software

Agile method is a method of software development management that comes in response to criticism of the waterfall method. This method is widely applied in large-scale software companies, because of its superiority that emphasizes service oriented rather than waterfall approach. One of the frameworks of the agile method is Scrum. Scrum is a framework that focuses on software development management on developer team performance as a single unit that works together indivisibly, iteration of product items, product incremental, and collaboration with customers. In Scrum, product requirements are flexible because they are not exhaustive at the start of a project, but at each iteration, because customers generally difficult to express their needs explicitly. However, how does Scrum's effectiveness improve software productivity? In this paper, we propose a literature study about SCRUM implementation of some articles that considers resources, cost, time, and system complexity for minimizing software development problems. The results had proven that Scrum could improve software productivity, but with some challenges, such as how to organize team skills, cultural constraints and scenarios of different companies, including communication problems between teams that are often constrained because of the large number of teams and teams scattered in multiple locations.