Approved for public release; distribution in unlimited. / The "paperless' ship is an idea wvhich has been advocated at the highest levels in the Navy. The goal is to eliminate the enormous amount of paper required in the normal operation of a modern naval warship. The ARGOS system under development at the Naval Postgraduate school is a prototype solution which uses HyperCard/HyperTalk for prototype development. The operations functional area, including sections for training, scheduling, message generation, and publication management is an important part of this development. / http://archive.org/details/designimplementa00ault

M.Com. (Business Management) / It is possible to manage the software development process efficiently. It is, however, important to gain a thorough understanding of the software development process and to be able to measure productivity easily and repeatedly. .A concept which may be used with success in the management of a software project is that of software economy. Software economy is achieved when the greatest quantity of software of the highest quality is produced using the smallest amount of resources (people, hardware and software) in the shortest possible time. The extensive software development process model is an important tool which can be used to maintain the various stages of the development process. Important conclusions can be made from the model. One such a conclusion is that adding more people to a project which is running behind schedule, will not help the project to be finished on time, but may even slow the project down further. The most useful and easy to implement metric, the measurement of productivity, is Function Points. Non-technical personnel may use this technique and it can be implemented early in the life cycle of a project. It is possible to successfully manage the software development process by using basic management principles such as planning, organization, monitoring and control together with the necessary adjustments outlined in this work.

No description available.

No description available.

Background. Websites are getting larger in size each year, the median size increased from 1479.6 kilobytes to 1699.0 kilobytes on the desktop and 1334.3 kilobytes to 1524.1 kilobytes on the mobile. There are several methods that can be used to decrease the size. In my experiment I use the methods tree shaking, code splitting, gzip, bundling, and minification. Objectives. I will investigate how using the methods separately affect the loading time and con- duct a survey targeted at participants that works as JavaScript developers in the field. Methods. I have used Vue for creating a website and ran Lighthouse tests against the website. All this within two Docker containers to make the reproducibility easier. Interviews with JavaScript developers were made to find out if they use these methods in their work. Results. The best result would be to use all of the methods; gzip, minification, tree shaking, code splitting, and bundling in a combination. If gzip is the only option available for the developer to use, we can see around 60% decrease in loading time. The inter- views showed that most developers did not use or did not know of tree shaking and code splitting. Some frameworks have these methods built in to work automatically, therefor the developers does not know that it is being utilized. Conclusions. Since tree shaking and code splitting are two relatively new techniques, there is not much scientific measured values available. From the results, we can give the conclusion that using all of the mentioned methods will give the best result in loading time. All of the methods will affect the loading time, and only using gzip will affect it with a 60% decrease.

No description available.

No description available.

Wong Wai Chi Mavis. / Thesis (M.Phil.)--Chinese University of Hong Kong, 2004. / Includes bibliographical references (leaves 106-112). / Abstracts in English and Chinese. / List of Tables --- p.x / List of Figures --- p.xiii / Chapter 1. --- Introduction --- p.1 / Chapter 1.1 --- Research Focus --- p.4 / Chapter 2. --- Literature Review --- p.6 / Chapter 2.1 --- Theoretical Models --- p.10 / Chapter 2.1.1 --- Transaction Cost Theory --- p.11 / Chapter 2.1.2 --- Limitations of the TCT --- p.14 / Chapter 3. --- Outsourcing Framework --- p.17 / Chapter 3.1 --- Motivation --- p.18 / Chapter 3.2 --- The Infrastructure --- p.19 / Chapter 3.3 --- Implication --- p.29 / Chapter 3.4 --- Limitations of the framework --- p.29 / Chapter 3.5 --- Concluding Remarks --- p.31 / Chapter 4. --- Single Vendor Approach --- p.33 / Chapter 4.1 --- Modeling Considerations --- p.35 / Chapter 4.1.1 --- Fixed cost for insourcing and outsourcing jobs --- p.36 / Chapter 4.1.2 --- Expected extra manufacturing costs --- p.37 / Chapter 4.1.2.1 --- Vendor Performance Matrix --- p.37 / Chapter 4.1.3 --- Coordination costs among the jobs --- p.39 / Chapter 4.1.4 --- Independence of the terms --- p.40 / Chapter 4.2 --- Quantitative Model --- p.41 / Chapter 4.3 --- Numerical Example --- p.44 / Chapter 4.4 --- Managerial Implications --- p.48 / Chapter 4.4.1 --- The importance of the co-relation parameter --- p.48 / Chapter 4.4.2 --- Penalty Scheme --- p.48 / Chapter 4.4.3 --- Price Changes --- p.50 / Chapter 4.5 --- Concluding Remarks --- p.54 / Chapter 5. --- Multiple Vendor Approach --- p.56 / Chapter 5.1 --- Modeling Considerations --- p.57 / Chapter 5.1.1 --- Fixed cost for insourcing and outsourcing jobs --- p.57 / Chapter 5.1.2 --- Expected extra manufacturing costs --- p.58 / Chapter 5.1.2.1 --- Vendor Performance Matrix --- p.58 / Chapter 5.1.3 --- Coordination costs among the jobs --- p.60 / Chapter 5.1.4 --- Independence of the terms --- p.61 / Chapter 5.2 --- Quantitative Model --- p.62 / Chapter 5.3 --- Numerical Example --- p.66 / Chapter 5.4 --- Managerial Implications --- p.70 / Chapter 5.4.1 --- Penalty Scheme --- p.70 / Chapter 5.4.2 --- Limited resources of the vendors --- p.71 / Chapter 5.4.3 --- Limiting the power of the vendors --- p.74 / Chapter 5.4.4 --- Competitive market --- p.76 / Chapter 5.4.5 --- The same purchasing prices --- p.79 / Chapter 5.4.6 --- Evaluation of vendors' performance --- p.82 / Chapter 5.4.6.1 --- Data Envelopment Analysis --- p.82 / Chapter 5.4.6.2 --- Vendor selection problem --- p.83 / Chapter 5.4.7 --- Make the unfair fair --- p.84 / Chapter 5.4.8 --- Applications --- p.84 / Chapter 5.5 --- Concluding Remarks --- p.85 / Chapter 6. --- Future Directions --- p.87 / Chapter 6.1 --- Extension to heuristic method --- p.87 / Chapter 6.2 --- Economy of scales --- p.88 / Chapter 6.3 --- Data Envelopment Analysis --- p.89 / Chapter 6.3.1 --- Vendor selection process --- p.89 / Chapter 6.3.2 --- Outsourcing decisions --- p.90 / Chapter 6.4 --- Vendors' point of view in winning the contracts --- p.90 / Chapter 6.4.1 --- Do not know the model formulation --- p.90 / Chapter 6.4.2 --- Know the model formulation --- p.91 / Chapter 6.5 --- Risk Analysis --- p.91 / Chapter 6.6 --- Outsourcing failure --- p.92 / Chapter 7. --- Conclusion --- p.96 / Appendix A --- p.101 / Appendix B --- p.103 / Appendix C --- p.104 / Bibliography --- p.106

In this thesis a method for selecting test cases for test automation is developed and evaluated. Existing methods from the literature has been reviewed and modified resulting in the proposed method, a decision tree containing 23 factors grouped into 8 decision points. The decision tree has been used and evaluated in an industrial setting. The economic benefits were calculated with return on investment and the organisational benefits were measured in a survey at a software producing company. The result was that automated tests, selected with the decision tree, provided economic benefits after 0.5 to 4 years, these tests were also found leading to 3 organisational benefits: less human effort when testing, reduction in cost and allowing for shorter release cycles.

Requirements specification documents are one of the main sources of guidance in software engineering projects and they contribute to the definition of the final product and its attributes. They can often contain text, graphs, figures and diagrams. However, they are still mostly written in Natural Language (NL) in industry, which is also a convenient way of representing them. With the increase in the size of software projects in industrial systems, the requirements specification documents are often growing in size and complexity, that could result in requirements documents being not easy to analyze. There is a need to provide the stakeholders with a way of analyzing requirements in order to develop software projects more efficiently. In this thesis we investigate how the complexity of textual requirements can be measured in industrial systems. A set of requirements complexity measures was selected from the literature. These measures are adapted for application on real-world requirements specification documents. These measures are implemented in a tool called RCM and evaluated on requirements documentation provided by Bombardier Transportation AB. The statistical correlation between the selected measures was investigated based on a sample of data from the provided documentation. The statistical analysis has shown a significant correlation between a couple of selected measures. In addition, a focus group was performed with a goal of exploring the potential use of these metrics and the RCM tool in industrial systems as well as what different areas of potential improvement future research can investigate.