The cleanroom case study in the Software Engineering Laboratory: Project description and early analysis

This case study analyzes the application of the cleanroom software development methodology to the development of production software at the NASA/Goddard Space Flight Center. The cleanroom methodology emphasizes human discipline in program verification to produce reliable software products that are right the first time. Preliminary analysis of the cleanroom case study shows that the method can be applied successfully in the FDD environment and may increase staff productivity and product quality. Compared to typical Software Engineering Laboratory (SEL) activities, there is evidence of lower failure rates, a more complete and consistent set of inline code documentation, a different distribution of phase effort activity, and a different growth profile in terms of lines of code developed. The major goals of the study were to: (1) assess the process used in the SEL cleanroom model with respect to team structure, team activities, and effort distribution; (2) analyze the products of the SEL cleanroom model and determine the impact on measures of interest, including reliability, productivity, overall life-cycle cost, and software quality; and (3) analyze the residual products in the application of the SEL cleanroom model, such as fault distribution, error characteristics, system growth, and computer usage

Estimasi Biaya Proyek Pengembangan Perangkat Lunak Kepemerintahan Berskala Small-Medium Dengan Metode Use Case Point (UCP)

Metode Use Case Point (UCP) merupakan metode yang sering dijadikan acuan perhitungan estimasi usaha (effort) yaitu banyaknya pekerja dan waktu yang dibutuhkan dalam proyek pengembangan perangkat lunak. Kenyataan di lapangan, dalam perencanaan proyek perangkat lunak tidak hanya diperlukan estimasi effort namun juga perlu mengetahui estimasi biaya proyek untuk memperkirakan alokasi biaya pemakaian sumber daya yang dihabiskan dalam pengembangan perangkat lunak. Penelitian ini bertujuan untuk mengembangkan UCP yang selama ini digunakan sebagai estimasi effort agar dapat digunakan untuk menghitung estimasi biaya pengembangan perangkat lunak. Untuk menghasilkan tahapan-tahapan penghitungan estimasi biaya tersebut, perlu diketahui persentase dari masing-masing tahapan pengembangan perangkat lunak, dalam hal ini disebut distribusi usaha. Nilai distribusi usaha didapatkan melalui pengumpulan data-data vi empiris pengembangan perangkat lunak kepemerintahan di bidang bisnis berskala small-medium yang telah berjalan. Hasil dan temuan dari penelitian ini adalah persentase nilai distribusi usaha masing-masing tahapan proyek pengembangan perangkat lunak beserta tahapan penghitungan estimasi biaya dengan menggunakan Use Case Point. Selanjutnya, untuk mengetahui apakah hasil distribusi usaha dapat diterima dan diterapkan maka dilakukan uji validasi terhadap nilai distribusi usaha. Persentase yang dihasilkan pada tahapan pengembangan perangkat lunak adalah sebesar 75%, tahapan aktivitas yang sedang berjalan adalah sebesar16%, dan tahapan kualitas dan pengujian adalah sebesar 9%. Validasi yang dilakukan terhadap usaha (effort) perangkat lunak menghasilkan rata-rata nilai deviasi sebesar 7% ========================================================================================================== Use Case Point (UCP) is a method that often used as a reference to calculate effort estimation, the amount of labor and time required in software development project. In Reality, software project planning is not only need effort estimation, but also cost estimate to estimate how much cost of resource allocation spent in software development. This research aims to develop UCP which has been used as effort estimation become cost estimate. To produce the phases of calculating the cost estimate of software development, need to know the percentage of each phase of software development, in this case called the effort distribution. The percentage of effort distribution obtained through the collection of empirical data of governance’s software development in small to medium scale. The Result of this research is effort percentage of each phase software development and the stages of calculate cost estimate by Use Case Point method. Furthermore, validate viii the result to determine the results of effort distribution can be accepted and implemented. Percentage of each phases in software development is 75%, percentage of ongoing activity is 16%, quality and testing phases is 9 %. Validation was performed that average of effort in software development is about 7%

Cost and schedule estimation study report

This report describes the analysis performed and the findings of a study of the software development cost and schedule estimation models used by the Flight Dynamics Division (FDD), Goddard Space Flight Center. The study analyzes typical FDD projects, focusing primarily on those developed since 1982. The study reconfirms the standard SEL effort estimation model that is based on size adjusted for reuse; however, guidelines for the productivity and growth parameters in the baseline effort model have been updated. The study also produced a schedule prediction model based on empirical data that varies depending on application type. Models for the distribution of effort and schedule by life-cycle phase are also presented. Finally, this report explains how to use these models to plan SEL projects

Implementation of Application Packaging Technology in Healthcare Industry

Application packaging bundles applications for operating systems into a single file called a distribution unit (.msi), which makes the administrator work easier to deploy and install them on user\u27s computers. This project was about repackaging Adobe Reader and after successful repackaging of the application, the customization of Adobe was done with the help of Adobe Customization Wizard. By applying Software Development Life Cycle (SDLC) methodology based on the requirement the packagers were able to create detailed analysis on Adobe Reader to support each step involved in managing a desktop application from deployment through retirement. The main objective of this project was to analyze the data to make the required and necessary customizations to the Adobe Reader to save time and effort. Application packaging can be important component for efficiently managing the increased volume of software on desktop and notebook systems. By streamlining software installation, uninstallation, repair, and patching, application packaging can help reduce costs associated with each phase of the application deployment and support life cycle

Reactor performance estimation in microscale flow calorimeter for rapid characterization of exothermic reactions

Continuous flow calorimeters are a promising tool in process development and safety engineering, especially for flow chemistry applications to characterize the heat release and kinetic parameters of rapid chemical reactions. In this study, the digital accompaniment of an isoperibolic flow calorimeter for characterization of exothermic reactions is presented. To support experimental planning and evaluation, computational fluid dynamic simulations are carried out for single-phase flow in the microreactor. The residence time distribution is obtained and used for estimation of conversion and temperature profiles along the microreactor channel. This leads to an integration of CFD simulations into the calorimeter’s software-guided workflow reducing the experimental effort regarding the determination of thermokinetic data. The approach is tested for a highly exothermic test reaction, which provides further hints for future investigations

Integrating automated support for a software management cycle into the TAME system

Software managers are interested in the quantitative management of software quality, cost and progress. An integrated software management methodology, which can be applied throughout the software life cycle for any number purposes, is required. The TAME (Tailoring A Measurement Environment) methodology is based on the improvement paradigm and the goal/question/metric (GQM) paradigm. This methodology helps generate a software engineering process and measurement environment based on the project characteristics. The SQMAR (software quality measurement and assurance technology) is a software quality metric system and methodology applied to the development processes. It is based on the feed forward control principle. Quality target setting is carried out before the plan-do-check-action activities are performed. These methodologies are integrated to realize goal oriented measurement, process control and visual management. A metric setting procedure based on the GQM paradigm, a management system called the software management cycle (SMC), and its application to a case study based on NASA/SEL data are discussed. The expected effects of SMC are quality improvement, managerial cost reduction, accumulation and reuse of experience, and a highly visual management reporting system

Software cost estimation

The paper gives an overview of the state of the art of software cost estimation (SCE). The main questions to be answered in the paper are: (1) What are the reasons for overruns of budgets and planned durations? (2) What are the prerequisites for estimating? (3) How can software development effort be estimated? (4) What can software project management expect from SCE models, how accurate are estimations which are made using these kind of models, and what are the pros and cons of cost estimation models