Hasil Pencarian  ::  Simpan CSV :: Kembali

"Software engineering : architecture-driven software development is the first comprehensive guide to the underlying skills embodied in the IEEE's Software Engineering Body of Knowledge (SWEBOK) standard. Standards expert Richard Schmidt explains the traditional software engineering practices recognized for developing projects for government or corporate systems.Software engineering education often lacks standardization, with many institutions focusing on implementation rather than design as it impacts product architecture. Many graduates join the workforce with incomplete skills, leading to software projects that either fail outright or run woefully over budget and behind schedule.Additionally, software engineers need to understand system engineering and architecture—the hardware and peripherals their programs will run on. This issue will only grow in importance as more programs leverage parallel computing, requiring an understanding of the parallel capabilities of processors and hardware. This book gives both software developers and system engineers key insights into how their skillsets support and complement each other. With a focus on these key knowledge areas, software engineering offers a set of best practices that can be applied to any industry or domain involved in developing software products."

""This book focuses on the inherent issues to help practitioners in gaining understanding of software development processes aimed at software professionals,students and researchers in the domain of software engineering in order to successfully employ knowledge management procedures"--Provided by publisher."

"ABSTRAKSebuah rancangan prosedur operasional standar POS untuk requirement engineering pada pengembangan perangkat lunak di Subdirektorat Integrasi Pengolahan Data Subdit IPD , Badan Pusat Statistik BPS , telah dihasilkan. BPS merupakan lembaga pemerintah non kementrian yang bertugas untuk menyelenggarakan kegiatan sensus dan survei. POS requirement engineering disusun menggunakan soft system methodology SSM yang telah dimodifikasi dan scrum sebagai metode pengembangannya. Kebutuhan POS dirancang berdasarkan studi literatur, SBOK trade; Guide sebagai referensi best practice, serta penelitian sebelumnya untuk menentukan tahapan proses requirement engineering pada scrum. Wawancara dengan analisis tematik juga dilakukan untuk mengetahui kebutuhan organisasi BPS akan POS requirement engineering. Rancangan POS requirement engineering yang dihasilkan terdiri dari tiga buah POS, yaitu POS Tahap Inisiasi, POS Tahap Pengembangan, dan POS Tahap Perencanaan Iterasi. Konsep POS requirement engineering divalidasi kepada narasumber di Subdit IPD BPS yang telah mengikuti pelatihan pengembangan perangkat lunak dengan menggunakan metode scrum. Selain itu, hasil rancangan POS juga divalidasi kepada Kepala Subdit IPD BPS dan menunjukkan bahwa rancangan POS dapat diimplementasikan namun memerlukan dukungan pimpinan dalam pelaksanaannya. Hasil rancangan POS requirement engineering ditujukan untuk standarisasi proses requirement engineering pada pengembangan perangat lunak di Subdit IPD BPS. Dengan dihasilkannya rancangan POS requirement engineering ini, diharapkan perangat lunak yang dihasilkan oleh Subdit IPD BPS menjadi berkualitas.

---

ABSTRACTA design of Standard Operating Procedure SOP for requirement engineering in software development in Data Processing Integration Subdirectorate Statistics Indonesia was resulted. Statistics Indonesia is non ministerial government institution that is responsible for conducting statistical surveys. SOP for requirement engineering was designed using modified soft systems methodology SSM . Scrum method is used as an approach. The needs of SOP is derived from literature, SBOK trade Guide as best practice, and previous research to determine the process in scrum. Interview with thematic analysis was also conducted to determine the needs of requirement engineering SOP from the organizations. The design of requirement engineering SOP consists of three steps Initiation, Development, and Iteration Planning. Concepts of requirement engineering SOP have been validated to the interviewees in Data Processing Integration Subdirectorate, who have had training software development using scrum. Futhermore, The design of SOP has been validated to the Chief of Data Processing Integration Subdirectorate. The result from validation process show that the design of SOP for requirement engineering can be implemented in Data Processing Integration Subdirectorate, but still need the support from high level management. The result is aimed to standardize the process of requirement engineering in Data Processing Integration Subdirectorate. With this SOP design, software produced by Data Processing Integration Subdirectorate is expected to achieve the quality."

"This book constitutes the thoroughly refereed post-conference proceedings of the 4th IFIP TC2 Central and East European Conference on Software Engineering Techniques, CEE-SET 2009, held in Krakow, Poland, in October 2009. The 19 revised full papers presented were carefully reviewed and selected from 63 submissions. The papers are organized in topical sections on software architectures and development, modelling and formal methods in software development, measurements, testing, and quality of software."

"[The complexity of software is continuously growing as a result of today’s interconnected business processes. Governance of architecture and technology strategy helps to ensure coherence of software and avoid excessive complexity. At the same time software development needs room for creativity and empowerment to provide solutions to business problems of increasing complexity. The book looks at this software dilemma from the perspectives of CIOs/CTOs, software architects, and auditors. Each of these groups has different interests which need to be considered, reconciled, and balanced. CIOs/CTOs are provided with the boundary conditions they have to establish assuring the achievement of strategic objectives. Architects and auditors find proven concepts for effectively assessing software projects and architectures, as well as for effectively communicating identified issues to responsible persons. The book is based on the author’s long experience in software engineering, governance, and auditing., The complexity of software is continuously growing as a result of today’s interconnected business processes. Governance of architecture and technology strategy helps to ensure coherence of software and avoid excessive complexity. At the same time software development needs room for creativity and empowerment to provide solutions to business problems of increasing complexity. The book looks at this software dilemma from the perspectives of CIOs/CTOs, software architects, and auditors. Each of these groups has different interests which need to be considered, reconciled, and balanced. CIOs/CTOs are provided with the boundary conditions they have to establish assuring the achievement of strategic objectives. Architects and auditors find proven concepts for effectively assessing software projects and architectures, as well as for effectively communicating identified issues to responsible persons. The book is based on the author’s long experience in software engineering, governance, and auditing.]"

"Terkadang realisasi kebutuhan pengembangan aplikasi web baru sudah diimplementasikan sebagian pada aplikasi web lain. Harusnya efisiensi pengembangan dapat ditingkatkan dengan me-reuse realisasi tersebut dan mengurangi jumlah kebutuhan yang diimplementasikan dari awal. Developer menyelesaikan kasus tersebut dengan pendekatan clone-and-own yang memungkinkan penggunaan fungsionalitas suatu perangkat lunak pada perangkat lunak lain. Meskipun meningkatkan efisiensi pengembangan, namun clone-and-own menimbulkan masalah maintainability pada perangkat lunak yang sudah dikembangkan. Masalah tersebut dapat diatasi dengan pendekatan alternatif seperti paradigma software product line engineering (SPLE) yang efisiensinya dapat ditingkatkan dengan konsep multi product line (MPL). Sayangnya, SPLE dan MPL belum umum digunakan untuk mengembangkan perangkat lunak web karena kurangnya web framework yang menunjang kedua pendekatan tersebut. Hal ini yang mendasari implementasi WinVMJ framework sebagai web framework untuk mengembangkan aplikasi web dengan SPLE dan MPL. Framework ini belum menerapkan alur kerja SPLE secara menyeluruh, sehingga validitas perangkat lunak tidak terjamin. Untuk melengkapi alur kerja SPLE WinVMJ, penelitian ini mengintegrasikannya dengan FeatureIDE. Integrasi dilaksanakan dalam tiga tahap: merancang alur kerja SPLE, mendefinisikan kumpulan artefak yang diperlukan untuk pengembangan perangkat lunak, dan implementasi plugin bernama WinVMJ composer untuk memproses kumpulan artefak yang didefinisikan. Alur kerja SPLE WinVMJ berhasil dilengkapi dengan WinVMJ composer yang mampu memproses artefak dari FeatureIDE dan melakukan validasi produk secara menyeluruh. Selain itu, evaluasi WinVMJ composer juga menunjukkan adanya keunggulan penerapan MPL dan penyusunan produk dibandingkan WinVMJ framework.

---

Sometimes the realization of new web application development needs has been partially implemented in other web applications. Development efficiency should be increased by reusing the realization and reducing the number of requirements implemented from scratch. Developers solve this case with a clone-and-own approach that allows using the functionality of one software on another. Although this approach improves development efficiency, clone-and-own causes maintainability issues in the developed software. This problem can be overcome by alternative approaches, such as the software product line engineering (SPLE) paradigm, whose efficiency can be increased by the multi-product line (MPL) concept. Unfortunately, SPLE and MPL are not commonly used to develop web software due to the lack of web frameworks that supports them. This issue underlies the implementation of the WinVMJ framework as a web framework for developing web applications with SPLE and MPL. This framework has not fully implemented the SPLE workflow, which causes a lack of software validity. To complete it, this research integrates it with featured. The integration is carried out in three stages: designing the SPLE workflow, defining the artifact set for software development after integration, and implementing a plugin named WinVMJ composer to process the defined artifacts set. The WinVMJ's SPLE workflow is completed with WinVMJ composer, which can process FeatureIDE's artifacts and perform thorough product validation. In addition, the evaluation of the WinVMJ composer also shows the advantages of implementing MPL and product compilation compared to the WinVMJ framework."