No description available.

Thesis (M.Eng.(Chemical Engineering))--Universiteit van Pretoria, 2007. / Abstract in English. Includes bibliographical references.

Thesis (Ph. D.)--Rutgers University, 2009. / "Graduate Program in Industrial and Systems Engineering." Includes bibliographical references (p. 114-120).

Thesis (Ph. D.)--Rutgers University, 2007. / "Graduate Program in Industrial and Systems Engineering." Includes bibliographical references (p. 118-122).

see document / Master of Science

Thesis (Ph. D.)--Rutgers University, 2008. / "Graduate Program in Chemical and Biochemical Engineering." Includes bibliographical references (p. 268-270).

International Telemetering Conference Proceedings / October 23-26, 2000 / Town & Country Hotel and Conference Center, San Diego, California / The Capability Maturity Model (CMM) developed by the Software Engineering Institute is widely promoted as a method to help decrease the volume of error riddled and late software projects. Because of the projected benefits, the 96th Communications Group/SC (SC) at Eglin Air Force Base began an intensive software process improvement effort in late 1997. This effort was rewarded in September 1999 when the group achieved a CMM Level 2 software rating on its first attempt. As of December 1999, 68% of assessed organizations remained at Level 1 on their first or second assessment. The SC success was not only obtained on its first attempt, but also 11 months ahead of the industry standard. The Level 2 rating was accomplished in the volatile environment needed to support the test and evaluation mission. This environment includes frequent requirement changes, short notice modifications, and externally driven schedules. One reason this milestone was possible is close and direct involvement by management. This paper will present additional factors to implementing a successful software process improvement effort.

Today, globally distributed software development is an unstoppable trend in Information Technology (IT) all over the world due to the benefits it provides such as cost benefits, time saving, accessing the large labor pool and available resources. However, globally distributed software companies face some issues in this regard. Cultural differences are introduced and discussed as one of the fundamental issues in globally distributed IT companies. Further, it is evident from the literature that business analysis process is the fundamental phase of software development process that affects the entire process of software development, and requires effective communication and collaboration among teams and between team members. Globally distributed software development makes the business analysis process and its related sub-phases even much more complicated than it is. Therefore, in this study, the influence of cultural differences on globally distributed business analysis process is analyzed. In order to do that, I conduct a qualitative study in which employees of the Turkey and Poland branches of the GTECH IT Company are interviewed. Hence, in this study remote project team member are asked about varying cultural differences that I extract from several existing cultural models and unify them into an integrated model. There are many studies exist about cultural differences in literature and these studies has similarity and differences which are creating complexity for readers and researchers. Hence, in this research Hofstede’s, Hall’s and Trompenaars’ cultural frameworks are unified and then I develop a new cultural model. By applying this new framework or model I investigated the influence of varying cultural differences on business analysis process that is conducted in a globally distributed IT company.

Sustainability and green engineering are two main concepts considered throughout this study. Sustainability deals with the utilization of renewable and replaceable sugar-based twelve most promising building blocks included in the report prepared by U.S. Department of Energy and green engineering concept is related with the incorporation of environmental performance criteria to chemical process design. Process performance criteria at the conceptual design stage are selected as persistence, bioaccumulation and aquatic toxicity, economical potential of the processes, atom &amp / mass efficiency of the processes and the relationship between Gibbs free energy of reaction values and economical potential. It is observed that bioaccumulation potentials of both the raw materials and products are low. Petrochemical raw materials are more persistent in air than the bio-based ones. The aquatic toxicity of bio-based raw materials is low / whereas some of the petrochemicals are moderately toxic and allyl alcohol and acrylonitrile among the petrochemicals are classified as highly toxic. Bio -based routes are not economically feasible with 2002 market prices. Atom and mass efficiencies of petrochemical reactions for a group of chemicals are higher than bio-based ones due to mostly addition or substitution reactions. Among high number of products, 1,3 propanediol production from glycerol with two microorganisms is analyzed at preliminary design stage. Process performance criteria are selected as material and energy consumption, cooling water requirement, CO, CO2, SO2 and NOX emissions to the atmosphere per unit of 1,3 propanediol production. Klebsiella pneumoniae process requires less cooling water, but it is less energy efficient and causes higher emissions.

[pt] Nesta tese é proposto um processo de desenvolvimento de groupware (software para dar suporte ao trabalho em grupo). O processo proposto é resultado de oito anos de experiência com o desenvolvimento dos serviços do ambiente AulaNet, e mais especificamente, dos cinco anos de pesquisa e desenvolvimento de versões do Mediated Chat. As boas práticas aprendidas ao longo destas experiências foram incorporadas no processo: uso do Modelo 3C de Colaboração para guiar o desenvolvimento de groupware, desenvolvimento evolucionário focando um problema por versão num processo investigativo, e desenvolvimento baseado em componentes e orientado ao reuso. O processo aqui proposto, denominado RUP-3C-Groupware consiste na extensão do RUP, Rational Unified Process, na qual foram incorporadas as boas práticas aprendidas. Na tese são apresentados os fluxos de atividades e os artefatos estendidos ou elaborados para o RUP-3C-Groupware. Para investigar o processo proposto, foi realizado um Estudo de Caso onde alunos de Engenheira de Software executaram algumas das atividades produzindo alguns artefatos-chave. Do estudo de caso foram obtidos indícios sobre a repetitividade do processo e de sua adequação para o desenvolvimento de groupware. / [en] A groupware (group work support software) development process is proposed in this thesis. This process is the result of eight years of experience with the development of services for the AulaNet environment, and more specifically of five years researching and developing Mediated Chat tool versions. The good practices learned through these activities were incorporated into the process proposed: the use of the 3C Collaboration Model to guide groupware development, evolutionary development focusing on a single problem per version in an investigative process, and reuse-oriented component- based development. These practices were used to guide the specification of the RUP, Rational Unified Process, resulting in the new process, namely the RUP-3C- Groupware. The new or extended RUP-3C-Groupware workflows and artifacts are presented. This process was investigated through a case-study in which Software Engineering students performed certain activities producing a few key- artifacts. From this case-study some indications regarding process repetitiveness and its suitability to groupware development were obtained.