Software Process

Perkembangan teknologi informasi telah mendorong penggunaan sistem terdistribusi dalam berbagai bidang, termasuk pada konsep Smart City. Sistem terdistribusi memungkinkan pengolahan data dilakukan secara terpisah namun tetap saling terhubung melalui jaringan komputer. Penelitian ini membahas implementasi sistem terdistribusi pada Smart City untuk meningkatkan efisiensi layanan publik, pengelolaan data, dan keamanan informasi. Metode penelitian yang digunakan adalah studi literatur dengan menganalisis berbagai jurnal, artikel ilmiah, dan sumber terpercaya mengenai penerapan sistem terdistribusi. Hasil penelitian menunjukkan bahwa sistem terdistribusi mampu meningkatkan kecepatan akses data, mengurangi beban server pusat, dan mendukung pengambilan keputusan secara real-time. Selain itu, teknologi ini juga mendukung integrasi Internet of Things (IoT), cloud computing, dan edge computing dalam pengelolaan kota pintar.

The rapid growth of digital technology has increased the need for stable systems capable of serving large numbers of users simultaneously. A prime example of this technology's implementation can be observed in Netflix, a global streaming platform. This study employs a descriptive qualitative method with a case study approach, combining literature review and technical document analysis. The research aims to analyze the mechanics of distributed systems at Netflix, identify the causes of server failures, and understand the implemented system resilience strategies. Data were gathered through the examination of scientific literature, Netflix's official open-source documentation, and qualitative analysis of their system architecture. The results indicate that Netflix utilizes cloud computing, microservices architecture, load balancing, replication, and chaos engineering to maintain service stability. One of the most prominent technologies used is Chaos Monkey, a system designed to intentionally and randomly shut down servers to test system resilience. Through this combined approach, this study provides an in-depth, field-technical data-driven overview of how Netflix minimizes downtime and preserves user experience despite failures occurring in parts of its servers.

Abstrak Perangkat Internet of Things (IoT) umumnya memiliki keterbatasan sumber daya, baik dari sisi daya maupun kapasitas komputasi. Di sisi lain, keamanan data pada jaringan Internet of Things (IoT) masih menjadi tantangan utama dalam pengembangan sistem terdistribusi. Kelemahan pada arsitektur terpusat dapat membuka peluang terjadinya manipulasi data hingga gangguan terhadap keseluruhan sistem. Penelitian ini membahas penerapan blockchain sebagai pendekatan desentralisasi untuk meningkatkan integritas dan keamanan data pada lingkungan IoT. Melalui mekanisme distributed ledger dan konsensus jaringan, data sensor dapat dicatat secara permanen sehingga risiko perubahan data secara tidak sah dapat diminimalkan. Hasil analisis menunjukkan bahwa arsitektur berbasis blockchain mampu menyediakan mekanisme autentikasi yang lebih transparan tanpa bergantung sepenuhnya pada otoritas pusat. Meskipun demikian, latensi transaksi dan konsumsi energi pada perangkat dengan kapasitas terbatas masih menjadi tantangan yang perlu dioptimalkan sebelum implementasi dilakukan secara luas.

Aligning the software process and the documentation process is a recipe for having both software and documentation in synchrony where changes in software seamlessly ripple along its documentation counterpart. This paper focuses on documentation for Software Product Lines (SPLs). A SPL is not intended to build one application, but a number of them: a product family. In contrast to single-software product development, SPL development is based on the idea that the distinct products of the family share a significant amount of assets. This forces a change in the software process. Likewise, software documentation development should now mimic their code counterpart: product documentation should also be produced out of a common set of assets. Specifically, the paper shows how DITA process and documents are recasted using a feature-oriented approach, a realization mechanism for SPLs. In so doing, documentation artifacts are produced at the same pace and using similar variability mechanisms that those used for code artifacts. This accounts for three main advantages: uniformity, separation of concerns, and timely and accurate delivery of the documentation.

Process mining is a field that uses elements from data mining and business process modeling to do tasks such as process discovery, conformance checking, and process improvement. This paper presents a study about the application of process mining techniques in the software development process. It shows a series of case studies that illustrate possible applications in the process and the product. Also, the main current challenges in applying process mining in software engineering are described. The objective of this paper is to show the importance and practical usefulness of applying process mining approaches in software engineering. The main result of this study is the fact that using process mining facilitates software process evaluation and auditing. The development of a methodology for applying process mining in software engineering is proposed as future work, considering the main challenges described previously.

This paper explores the operational context of software processes and how it can inform the micro-process level environment. It examines the case of software project performance, describing a novel explanation. Drawing on the management literature, project performance is modeled as the contested outcome of learning as a driver of success and certain barrier conditions as drivers of failure, through their effects on organizational capabilities. A case study illustrates application of the theory. Implications of this macro-process case for micro level software process improvement are discussed.

This paper reports our initial investigations into the use of workflow technology for constructing a software process management tool. We examine some recent work undertaken in the fields of tool construction technologies and low cost workflow engines. Using an example Software Engineering Environment (PSEE) built on top of a commercial RDBMS, we demonstrate a mapping from the PSEE onto the WfMCs Process Definition Interchange Process Model. The resultant workflow process definition can be imported into a WfMC conformant workflow management system, thereby enabling the enactment of the software process model by different workflow management systems.

Reducing the number of bugs is a crucial issue during software development and maintenance. Software process and product metrics are good indicators of software complexity. These metrics have been used to build bug predictor models to help developers maintain the quality of software. In this paper we empirically evaluate the use of hunk metrics as predictor of bugs. We present a technique for bug prediction that works at smallest units of code change called hunks. We build bug prediction models using random forests, which is an efficient machine learning classifier. Hunk metrics are used to train the classifier and each hunk metric is evaluated for its bug prediction capabilities. Our classifier can classify individual hunks as buggy or bug-free with 86 % accuracy, 83 % buggy hunk precision and 77% buggy hunk recall. We find that history based and change level hunk metrics are better predictors of bugs than code level hunk metrics.

Together with many success stories, promises such as the increase in production speed and the improvement in stakeholders' collaboration have contributed to making agile a transformation in the software industry in which many companies want to take part. However, driven either by a natural and expected evolution or by contextual factors that challenge the adoption of agile methods as prescribed by their creator(s), software processes in practice mutate into hybrids over time. Are these still agile? In this article, we investigate the question: what makes a software development method agile? We present an empirical study grounded in a large-scale international survey that aims to identify software development methods and practices that improve or tame agility. Based on 556 data points, we analyze the perceived degree of agility in the implementation of standard project disciplines and its relation to used development methods and practices. Our findings suggest that only a small number of participants operate their projects in a purely traditional or agile manner (under 15%). That said, most project disciplines and most practices show a clear trend towards increasing degrees of agility. Compared to the methods used to develop software, the selection of practices has a stronger effect on the degree of agility of a given discipline. Finally, there are no methods or practices that explicitly guarantee or prevent agility. We conclude that agility cannot be defined solely at the process level. Additional factors need to be taken into account when trying to implement or improve agility in a software company. Finally, we discuss the field of software process-related research in the light of our findings and present a roadmap for future research.

Resumo. Cada vez mais os requisitos não funcionais são considerados primordiais aos sistemas computacionais. Satisfazer esses requisitos exige uma atenção especial com a arquitetura já que uma arquitetura inadequada introduz uma complexidade maior, além da complexidade intrínseca do sistema. Estudos mostram que apesar das atividades de engenharia de requisitos e de arquitetura de software atuarem em diferentes aspectos do desenvolvimento, é preciso executá-las de forma iterativa e entrelaçada para produzir sistemas computacionais satisfatórios. O processo STREAM apresenta uma abordagem sistemática para diminuir a lacuna entre requisitos e o desenvolvimento da arquitetura, enfatizando os requisitos funcionais, enquanto que os requisitos não-funcionais são usados de forma ad hoc. No entanto, alguns estudos mostram que requisitos não-funcionais impactam o sistema como um todo. Este artigo apresenta uma proposta para auxiliar o processo STREAM na realização da escolha de padrões arquiteturais a partir de requisitos não-funcionais, com propósito de guiar o refinamento da solução arquitetural.

In the recent past, a relevant effort has been devoted to the definition of process modeling languages (PMLs). The resulting languages and environments -although technically successfuldid not receive much attention from industry. On the contrary, researchers and practitioners have recently started experimenting with the usage of UML as a PML. Being so popular and widely used, UML has an important competitive advantage compared to any specialized PML. However, it has also a main limitation. While most PMLs are executable by some process engine, UML was conceived as a non-executable, semi-formal language. The work described here aims at assessing the possibility of employing a subset of UML as an executable PML. The article proposes a formalization of the semantics of the UML subset and presents the translation of UML process models into code, which can be enacted in the OPSS process-centered environment. The paper also presents a case study to validate the approach. We expect that process modeling by means of UML is easier and available to a larger community of software process managers. Moreover, process enactment makes the process more efficient, reliable, predictable and controllable, as widely shown by previous research.

Agent Assisted Methodologies have become an important subject of research in advance Software Engineering. Several methodologies have been proposed as, a theoretical approach, to facilitate and support the development of complex distributed systems. An important question when facing the construction of Agent Applications is deciding which methodology to follow. Trying to answer this question, a framework with several criteria is applied in this paper for the comparative analysis of existing multiagent system methodologies. The results of the comparative over two of them, conclude that those methodologies have not reached a sufficient maturity level to be used by the software industry. The framework has also proved its utility for the evaluation of any kind of Agent Assisted Software Engineering Methodology.

In a component-based software development life cycle, selection of preexisting components is an important task. Every component that has to be reused has an associated risk of failure of not meeting the functional and non-functional requirements. A component's failure would lead a developer to look for some other alternative of combinations of COTS, in-house and engineered components among possible candidate combinations. This means design itself can readily change. The very process of design of a software system and component selection seems to be heavily dependent on testing results. Instability of design, further, becomes more severe due to requirements change requests. Therefore, this instability of design has to be essentially mitigated by using proper design and testing approaches, otherwise, it may lead to exorbitantly high testing cost due to the repeated testing of various alternatives. How are these three activities: Component-based software design, component selection and component-based software testing interrelated? What process model is most suited to address this concern? This work explores the above questions and their implication in terms of nature of a process model that can be convincing in case of component-based software development.

This paper explores the operational context of software processes and how it can inform the micro-process level environment. It examines the case of software project performance, describing a novel explanation. Drawing on the management literature, project performance is modeled as the contested outcome of learning as a driver of success and certain barrier conditions as drivers of failure, through their effects on organizational capabilities. A case study illustrates application of the theory. Implications of this macro-process case for micro level software process improvement are discussed.

This paper explores the operational context of software processes and how it can inform the micro-process level environment. It examines the case of software project performance, describing a novel explanation. Drawing on the management literature, project performance is modeled as the contested outcome of learning as a driver of success and certain barrier conditions as drivers of failure, through their effects on organizational capabilities. A case study illustrates application of the theory. Implications of this macro-process case for micro level software process improvement are discussed.

The research area of interactive digital television is in the midst of a significant revival. Unlike the first generation of digital television -which focused on the concerns of producers and broadcasters, and limited the end-user impact -the current generation of digital television research is closely linked to the role of the user in selecting, producing and distributing content. This paper presents the rationale for evaluating new interaction paradigms with television content: microlevel navigation and selection of content, direct recommendation of (pieces of) content, and enrichment of content while watching. The rationale is composed of four steps: system design, business analysis, prototype implementation, and user studies.

Contrary to the basic tenants of the information technology project management literature, this research adopts a positive stance towards current practices. We report from a one-year action research effort in which we applied appreciative inquiry to improve project management practices at a small software firm, TelSoft. The paper presents our design of the appreciative inquiry process; it describes the resulting intervention into project management practices; and it discusses the results and the lessons learned.

In the past decades, Law has turned to Computation in search of solutions for the representation of legal domain, for storage of large volumes of information and for retrieval of this information to generate knowledge to support decision-making. Among the several solutions proposed for representation of legal domain, we highlight legal ontologies, which propose the representation of a shared conceptualization of legal concepts and their relations. Those legal ontologies that represent generic legal concepts that can be used and reused in the construction of other ontologies or in legal modeling languages are called Legal Core Ontologies (LCOs). The approach of most LCOs is focused on legal norms. However, in this research, we opted for a different approach, namely, on basing the construction of our Legal Core Ontology on legal relations. Although both approaches bring benefits, the advantage of the latter is the possibility of making explicit of concepts and relations that are not e...

A data scanner system, which is a part of the front-end data acquisition system of the BELLE silicon vertex detector, carries out analog-to-digital conversion of preamplified signals from the detector and stores digitized data into local memory. The sequence control and buffer managing are performed by the software process of an on-board CPU. With this data scanner system, we can achieve data acquisition with less than 10% dead time up to 800 Hz trigger rate

Currently the concept of Software Factories (SF), where reuse plays a leading role, is being adopted. Due to the different approaches in this area, and although SF concept is not new in Software Engineering, it is still not mature enough to clearly identify the treatment of certain variables within the process. One of these variables is Quality. Therefore, this paper presents a historical review of the SF concept, proposes an ontology based on the most recent definitions and establishes a relationship between these concepts and the ISO 15504 standard, with the purpose of specifying the systemic quality in software developer companies that decide to implement an SF strategy.

Reducing the number of bugs is a crucial issue during software development and maintenance. Software process and product metrics are good indicators of software complexity. These metrics have been used to build bug predictor models to help developers maintain the quality of software. In this paper we empirically evaluate the use of hunk metrics as predictor of bugs. We present a technique for bug prediction that works at smallest units of code change called hunks. We build bug prediction models using random forests, which is an efficient machine learning classifier. Hunk metrics are used to train the classifier and each hunk metric is evaluated for its bug prediction capabilities. Our classifier can classify individual hunks as buggy or bug-free with 86 % accuracy, 83 % buggy hunk precision and 77% buggy hunk recall. We find that history based and change level hunk metrics are better predictors of bugs than code level hunk metrics.

The development of high quality software is the need of current technology driven world. Component Based Software Engineering (CBSE) has provided a cost effective, fast and modular approach for developing complex software. CBSE is mainly based on the concept of reusability. Apart from these CBSE has several advantages as well as challenges which are summarized in this paper. Large and complex software development requires management of reusable components and can be selected from component repository and assembled to obtain a working application. Development of components and their assembly is different from traditional softwares which leads to the need of new development paradigms for Component Based Systems (CBS). Software development life cycle (SDLC) provides planned and systematic arrangement of activities to be carried out to deliver high quality products within time and budget. This paper presents a comparative study of component based software development life cycle models w...

Comparison against non-outsourced versions of the projects. One of the benefits of the structure is that the same project is implemented by teams using the outsourcing models and not using the outsourcing models. • Anecdotal instructor feedback. • Project teams conclude process by conducting postmortems, and this information may also prove useful in assessing the outsourcing experience. Finally, we again note that our emphasis is process-centered, not project-centered. While the quality of the resulting software deliverables is a significant factor in the overall success of the project, we emphasize the role of process in determining project success. Were student teams able to define and follow a process? Did students encounter, address, and gain experience with "real-world" project obstacles related to process and people management? The true measure of experiment's success will be in the answers to questions such as these, and not necessarily in whether their resulting software works at all.

Computer science and software engineering programs are in a constant struggle to update curriculum content and instructional methodologies so graduates are better prepared to enter today's fast-paced technology sector. Despite these efforts, the general perception of industry remains that new graduates are ill equipped to perform their duties when entering the marketplace. We find our students are often caught between the academic mission to learn the science and the need to find gainful employment when they complete their degree requirements. Our response to this dilemma is the introduction of a four-semester capstone project sequence dubbed "the software enterprise". The instructional methodology involves a combination of lecture, problem-centered learning, and project work to expose, practice, and apply concepts over short intervals. In this way, students understand not only the skills but also how they are applied. The length of the sequence ensures prolonged and r...

Top-down approaches to process improvement based on generic "best practice" models (e.g., CMM, TRILLIUM, BOOTSTRAP, SPICE) have become popular. Despite the idiosyncrasies of each of these approaches, they share some common characteristics: all of them are based on numerous assumptions about what are best practices, and about the business goals of organizations and the problems they face. Other organizations, like the Software Engineering Laboratory of the NASA Goddard Space Flight Center, HP and CRIM in Canada, have adopted the Quality Improvement Paradigm (QIP). The QIP stipulates a more bottomup and inductive approach to process improvement. The focus of this paradigm is to first understand what processes exist in the organization and to determine what causes the most significant problems. Based on this, opportunities for improvement are devised, and empirical studies are conducted to evaluate potential solutions. In this paper, we present a method, named AINSI 1 (An INductive Software process Improvment method), which defines general but concrete steps and guidelines for putting in place the QIP. This method is the result of the collective experiences of the authors and integrates many lessons learned from process improvement efforts in different environments. It also integrates many complementary techniques such as qualitative analysis, methods for data collection (e.g., the Goal/Question/Metric paradigm), and quantitative evaluation.

This paper looks at how Cooperative Software Engineering (CSE) can be supported. We first investigate the process aspects by presenting a traditional process architecture supporting CSE. Then we propose a multi-agent architecture for CSE, which is better in terms of simplicity and flexibility, and particularly useful in modelling and providing support to cooperative activities. We describe an industrial scenario of CSE, and show how to apply the proposed architecture to this scenario. The scenario is based on a software development and maintenance process for a Norwegian software company.

Measurement based software process improvement is nowadays a mandatory activity. This implies continuous process monitoring in order to predict its behavior, highlight its performance variations and, if necessary, quickly react to them. Process variations are due to common causes or assignable ones. The former are part of the process itself while the latter are due to exceptional events that result in an unstable process behavior and thus in less predictability. Statistical Process Control (SPC) is a statistical based approach able to determine whether a process is stable or not by discriminating between the presence of common cause variation and assignable cause variation. It is a well-established technique, which has shown to be effective in manufacturing processes but not yet in software process contexts. Here experience in using SPC is not mature yet. Therefore a clear understanding of the SPC outcomes still lacks. Although many authors have used it in software, they have not considered the primary differences between manufacturing and software process characteristics. Due to such differences the authors sustain that SPC cannot be adopted "as is" but must be tailored. In this sense, we propose an SPC-based approach that reinterprets SPC, and applies it from a Software Process point of view. The paper validates the approach on industrial project data and shows how it can be successfully used as a decision support tool in software process improvement.

Cloud computing memungkinkan pengguna untuk menjalankan aplikasi pada cloud server melalui jaringan. Cloud computing dapat diterapkan di berbagai bidang, salah satunya adalah game. Cloud gaming dapat meringankan beban komputasi perangkat pengguna dalam menjalankan sebuah game. Hal ini dikarenakan seluruh penyimpanan dan proses-proses dalam game mulai dari komputasi sampai rendering berada di server. Hasil rendering akan dikirim ke perangkat client secara streaming. Pengguna berinteraksi dengan game melalui perangkat client yang terhubung ke server. Cloud gaming memungkinkan game dapat dimankan di mana saja, kapan saja, dan dengan perangkat apa saja, mulai dari PC sampai perangkat mobile (telepon seluler dan tablet). Penelitian ini akan membahas mengenai perancangan aplikasi cloud gaming pada server dan client. Aplikasi server akan dibuat pada sistem operasi Windows 7, sedangkan aplikasi klien akan dibuat pada Android. Hasil yang diharapkan dari penelitian ini adalah terciptanya aplikasi cloud gaming yang memungkinkan pengguna memainkan game pada server secara streaming.

In order to facilitate better Information Systems Development (ISD), Method Engineering technqiues and tools are needed that support flexible creation, modification, and reuse of ISD methods and tools for use on specific problem domains. A metamodelling notation is needed for specifying and integrating different design notations. MetaCASE support is required for building, reusing and evolving tools for these design notations.

Komunikasi verbal adalah komunikasi umum digunakan sebagai sarana dalam memberikan informasi kepada orang lain. Disamping itu, untuk berkomunikasi dengan tuna rungu serta tuna wicara sarana komunikasi dapat melalui bahasa isyarat. Indonesia telah memiliki sistem bahasa isyarat yaitu Bahasa Isyarat Indonesia atau Sistim Isyarat Bahasa Indonesia (SIBI). Aplikasi pengenalan dan pembelajaran SIBI yang ada pada saat ini berupa aplikasi yang terikat pada platform. Aplikasi beserta proses pengenalan menjadi satu sehingga memiliki kebergantungan yang cukup tinggi. Penelitian ini bertujuan mengembangkan platform cloud sebagai backend untuk pengenalan gerakan tangan, sehingga memudahkan pengembang untuk membuat aplikasi pengenalan SIBI. Platform tersebut memiliki kemampuan untuk mengenal gerakan tangan yang diperoleh dari data sensor Myo Armband. Aplikasi yang berada sisi frontend dapat menggunakan fitur platform melalui Application Programming Interface (API) yang disediakan. Penelitian ini ...

The challenge for software development house in Bangladesh is to find a path of using minimum process rather than CMMI or ISO type gigantic practice and process area. The small and medium size organization in Bangladesh wants to ensure minimum basic Software Process Improvement
(SPI) in day to day operational activities. Perhaps, the basic practices will ensure to realize their company's improvement goals. This paper focuses on the key issues in basic software practices for small and medium size software organizations, who are unable to effort the CMMI, ISO,  ITIL etc. compliance certifications. This research also suggests a basic software process practices model for Bangladesh and it will show the mapping of our suggestions with international best practice. In this IT competitive world for software process improvement, Small and medium size software companies that require collaboration and strengthening to transform their current perspective into inseparable global IT scenario. This research performed some investigations and analysis on some projects’ life cycle, current good practice, effective approach, reality and pain area of practitioners, etc. We did some reasoning, root cause analysis, comparative analysis of various approach, method, practice and justifications of CMMI and real life. We did avoid
reinventing the wheel, where our focus is for minimal practice, which will ensure a dignified
satisfaction between organizations and software customer.