Thesis (Ph. D.)--University of California, Riverside, 2008. / Includes abstract. Title from first page of PDF file (viewed February 3, 2010). Available via ProQuest Digital Dissertations. Includes bibliographical references (p. 122-129). Also issued in print.

Thesis (M.S.)--West Virginia University, 2003. / Title from document title page. Document formatted into pages; contains x, 86 p. : ill. (some col.). Vita. Includes abstract. Includes bibliographical references (p. 84).

When working with software development in Microsoft Dynamics AX 2009 applications as an independent solution vendor (ISV) with more than a few products in the portfolio, the number of applications/installations to support the processes tends to be vast. Annata and To-Increase are both ISVs and face this situation; To-Increase for example has about 50 environments for one single version of Dynamics AX. Change is inevitable in the software industry, regardless if the need originates from new features, bug fixes or change requests from customers; it requires modifications to existing products. Uncontrolled changes to the products must be avoided and any modifications should be introduced without affecting existing functionality. This thesis investigates how two ISVs work with Dynamics AX and the existing tool Development Center and suggests improvements to the Software Configuration Management. The most beneficial change suggested is to create a single repository within the existing tool across the applications.

Thesis (M.C.S.) Carleton University, 2005. / Includes bibliographical references (p. 257-260). Also available in electronic format on the Internet.

Thesis (M.S.)--Ohio University, November, 2007. / Title from PDF t.p. Includes bibliographical references.

Thesis (M.S. in Computer Science)--Naval Postgraduate School, March 2006. / Thesis Advisor(s): Cynthia E. Irvine, Thuy D. Nguyen. "March 2006." Includes bibliographical references (p. 123-124). Also available online.

Denna rapport har skrivits under ett examensarbete på Linköpings Universitet för att ta reda på vilket program som är mest tidseffektivt att använda för hantering av datorkonfigurationer. De konfigurationshanterarna som analyserades i detta arbete är Ansible, Chef och Puppet som är tre av de ledande programmen inom ämnet. Motiveringen till arbetet är att när komplexiteten hos infrastrukturen ökar, så är det viktigt att hitta en konfigurationshanterare som verkställer konfigurationen på systemen tillräckligt snabbt för att möta den komplexa infrastrukturens behov. Jämförelsen görs baserat på hur lång tid det tar för varje program att genomföra olika typer av konfigurationer, med olika uppsättningar av antalet system som konfigureras, och från denna data görs slutsatser om programmens tidseffektivitet, spridning och skalning.

The goal of this thesis is to describe a compare selected open source tools for mass linux server administration. In the first part, the tools are described, including their principles and internal architecture. The next part follows with the comparison of these selected tools using several groups of comparison criteria. The main contribution of this thesis is the actual comparison of software tools of this type. The method chosen to fulfill the goal of this thesis is literature search and custom practical testing of these tools.

Background: In developing and maintaining a large-scale system-of-systems (SoS), interface coordination & control (ICC) among interdependent subsystems is crucial for evolving individual subsystems and the overall SoS. However, the available literature offers little or no support to guide ICC in practice. Objectives: To describe how ICC can be done in the context of a large-scale SoS.We aimed to explore and analyze Ericsson’s (an example of a typical large-scaleSoS) current process and practices. To identify any limitations of the process, we investigated the challenges faced by practitioners regarding ICC, their reasons, and implications. Furthermore, we researched and proposed improvement possibilities to overcome the identified challenges. Method: We conducted a case study research and used observations, interviews, focus groups, and archival analysis for data collection. We used coding techniques from grounded theory and descriptive statistics to analyze qualitative and quantitative data, respectively. Moreover, the tabulation technique was employed to identify improvement opportunities. Results: We found that ICC is part of an overall technical coordination process. ICC is implemented through a recurrent cycle of activities. It brings together stakeholders to present upcoming changes, discuss their impact, and plan mitigation strategies. The outcome of ICC is a list of agreed-upon changes, impacted subsystems, and version numbers of interacting objects for the next release. We categorised the identified challenges in three groups: "people & subsystems", "tools, artifacts & technique", and "organization & management". These challenges impeded the effectiveness of the ICC process, quality of the SoS, and overall efficiency of the ICC and development process. Need for training, tool support, and stronger governance were identified as possible improvements to address multiple categories of identified challenges. Conclusion: The studied ICC process is well adapted for the large-scale SoS context. It is reasonably effective in minimizing the impact of evolving subsystems on the functioning and quality of SoS (as evident from the defect report analysis in this thesis). It also helps in cost-saving through early detection of compatibility-related issues. This thesis describes an ICC process used in practice, a novel contribution to the software configuration management (SCM) literature. In addition, companies in similar contexts can use the ICC description. The described ICC process is generalizableas as it is agnostic of the underlying development technologies used in a company.

Approved for public release, distribution is unlimited / Configuration Management (CM) plays a vital role in the development of trusted computing systems. The Common Criteria (CC) provides a framework for performing Information Technology (IT) security evaluations of these systems and further emphasizes CM's role in the development and evaluation process by specifying a minimum set of CM qualities for each Evaluated Assurance Level (EAL). As an evaluation guide, the Common Methodology for Information Technology Security Evaluation, Part 2: Evaluation Methodology (CEM), recommends a set of minimum CM guidelines which can be used by evaluators in the performance of a CM evaluation at the lower Evaluated Assurance Levels. Evaluators and developers will quickly note the CEM's lack of recommended CM guidelines at the higher assurance levels. Thorough study of the listed references supports the hypothesis for this work: Configuration Management guidelines are useful in the evaluation of trusted computing systems. As an assurance mechanism, complete CM guidance helps users of high assurance products obtain a degree of confidence the system security requirements operate as intended and do not contain clandestine code. Complete CM guidance provides evaluators with a "completed assurance scale" and ensures only authorized changes were made to the TOE during development. Useful CM guidelines at the higher assurance levels (EAL5, 6, and 7) will help developers and evaluators ensure products meet the minimum requirements needed for high assurance systems. / Lieutenant, United States Navy