Dissertation (MCIS)--AUT University, 2009. / Includes bibliographical references. Also held in print (viii, 83 leaves : ill. ; 30 cm.) in the Archive at the City Campus (T 005.1068 MA)

Thesis (M.S.)--California Polytechnic State University, 2010. / Title from PDF title page; viewed on April 27, 2010. Major professor: Clark S. Turner, J.D., Ph.D. "Presented to the faculty of California Polytechnic State University at San Luis Obispo, California." "In partial fulfillment of the requirements for the degree [of] Master of Science in Computer Science." "March 2010." Includes bibliographical references (p. 62-66).

Thesis (M.S.)--West Virginia University, 2006. / Title from document title page. Document formatted into pages; contains xii, 140 p. : ill. (some col.). Includes abstract. Includes bibliographical references (p. 135-140).

Thesis (M.Sc.)--York University, 2004. Graduate Programme in Computer Science. / Typescript. Includes bibliographical references (leaves 277-284). Also available on the Internet. MODE OF ACCESS via web browser by entering the following URL: http://wwwlib.umi.com/cr/yorku/fullcit?pMQ99344

Thesis (M. Sc. (Computer Science))--Rhodes University, 2006.

Thesis (M.S.C.I.T.)--Regis University, Denver, Colo., 2006. / "December 2005"--T.p. Title from PDF title page (viewed on Aug. 30, 2006). Includes bibliographical references.

Thesis (M.S.E.)--University of Wisconsin -- La Crosse, 2005. / Includes bibliographical references (leaves 45-46)

Thesis (M.S.)--Washington State University, August 2007. / Includes bibliographical references (p. 72-74).

This report addresses the use of computer-aided software engineering (CASE) technology for the development of aircraft software. / Lean Aerospace Initiative

Made available in DSpace on 2013-08-07T18:42:25Z (GMT). No. of bitstreams: 1 000418584-Texto+Completo-0.pdf: 889263 bytes, checksum: b0fc544b8e0b9a5abafd500ef19ed9cc (MD5) Previous issue date: 2009 / Each and every framework instantiation is driven by a process, regardless it is manual or automated. In a manual process, an architect or software engineer follows a sequence of random steps towards creating an instance of a specific framework. In an automated process, the architect or the software engineer takes advantage of one or more tools that follow well-defined, configured steps to guide creation of a framework instance. To assess the real benefit of such tools is the goal of this study, where empirical data will be analyzed by comparing manual to automated process, using a framework instantiation tool in an experiment. With such data, it is expected to obtain information that shows up, in the context analyzed, the real benefits in adopting a tool to automate instantiation process. With the information gathered is also possible to figure out where those tools do not add any value, allowing suggestions to improve them in order to justify their use. / Toda a instanciação de frameworks segue um processo, seja ele manual ou automatizado. Em um processo manual, um arquiteto ou desenvolvedor segue uma seqüencia de passos aleatórios com o objetivo de criar uma instância de determinado framework. Em um processo automatizado o arquiteto ou desenvolvedor utiliza uma ou mais ferramentas que sigam passos bem definidos e pré-estabelecidos que irão auxiliar na criação da instância do framework em uso. Verificar o real benefício em usar tais ferramentas é o objetivo deste trabalho, onde dados empíricos serão analisados ao se comparar o processo manual a uma ferramenta de instanciação de frameworks em um experimento. Com isso, pretende-se obter informações que demonstrem, no contexto pesquisado, os ganhos reais de se utilizar uma ferramenta para esse fim ou que as informações demonstrem onde uma ferramenta não agrega valor, permitindo assim sugerir melhorias que justifiquem o uso de tais ferramentas.