Dissertations / Theses: 'Software maintenance. Computer-aided software engineering'

1

Fernandes, Leonie Menco. "An investigation of the effect of a reverse engineering tool on the software maintenance effort /." Online version of thesis, 1991. http://hdl.handle.net/1850/11165.

Full text

APA, Harvard, Vancouver, ISO, and other styles

2

Breidenbach, Jeff. "Survivable software distribution and maintenance." Thesis, Massachusetts Institute of Technology, 1997. http://hdl.handle.net/1721.1/42793.

Full text

Abstract:

Thesis (Ph. D.)--Massachusetts Institute of Technology, Dept. of Electrical Engineering and Computer Science, 1997.
Includes bibliographical references (leaves 79-82).
by Jeff Breidenbach.
Ph.D.

APA, Harvard, Vancouver, ISO, and other styles

3

Egerton, David. "Automated generation of SW design constructs from MESA source code /." Online version of thesis, 1993. http://hdl.handle.net/1850/12144.

Full text

APA, Harvard, Vancouver, ISO, and other styles

4

Akhlaq, Usman, and Muhammad Usman Yousaf. "Impact of Software Comprehension in Software Maintenance and Evolution." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2010. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-2176.

Full text

Abstract:

The need of change is essential for a software system to reside longer in the market. Change implementation is only done through the maintenance and successful software maintenance gives birth to a new software release that is a refined form of the previous one. This phenomenon is known as the evolution of the software. To transfer software from lower to upper or better form, maintainers have to get familiar with the particular aspects of software i.e. source code and documentation. Due to the poor quality of documentation maintainers often have to rely on source code. So, thorough understanding of source code is necessary for effective change implementation. This study explores the code comprehension problems discussed in the literature and prioritizes them according to their severity level given by maintenance personnel in the industry. Along with prioritizing the problems, study also presents the maintenance personnel suggested methodologies for improving code comprehension. Consideration of these suggestions in development might help in shortening the maintenance and evolution time.
Usman Akhlaq Mirpur, Azad Kashmir, Pakistan Muhammad Usman Yousaf Bhimber, Azad Kashmir, Pakistan

APA, Harvard, Vancouver, ISO, and other styles

5

Chadha, Vineet. "Semantics-based change-merging of abstract data types." Master's thesis, Mississippi State : Mississippi State University, 2002. http://library.msstate.edu/etd/show.asp?etd=etd-03272002-120619.

Full text

APA, Harvard, Vancouver, ISO, and other styles

6

Li, Wei. "Applying software maintenance metrics in the object oriented software development life cylce." Diss., Virginia Tech, 1992. http://hdl.handle.net/10919/40020.

Full text

Abstract:

Software complexity metrics have been studied in the procedural paradigm as a quantitative means of assessing the software development process as well as the quality of software products. Several studies have validated that various metrics are useful indicators of maintenance effort in the procedural paradigm. However, software complexity metrics have rarely been studied in the object oriented paradigm. Very few complexity metrics have been proposed to measure object oriented systems, and the proposed ones have not been validated. This research concentrates on several object oriented software complexity metrics and the validation of these metrics with maintenance effort in two commercial systems. The results of an empirical study of the maintenance activities in the two commercial systems are also described. A metric instrumentation in an object oriented software development framework is presented.
Ph. D.

APA, Harvard, Vancouver, ISO, and other styles

7

Alomari, Hakam W. "Supporting Software Engineering Via Lightweight Forward Static Slicing." Kent State University / OhioLINK, 2012. http://rave.ohiolink.edu/etdc/view?acc_num=kent1341996135.

Full text

APA, Harvard, Vancouver, ISO, and other styles

8

Williamsson, Ia. "Total Quality Maintenance (TQMain) A predictive and proactive maintenance concept for software." Thesis, Blekinge Tekniska Högskola, Avdelningen för för interaktion och systemdesign, 2006. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-2281.

Full text

Abstract:

This thesis describes an investigation of the possibility to apply a maintenance concept originally developed for the industry, on software maintenance. Today a large amount of software development models exist but not many of them treat maintenance as a part of the software life cycle. In most cases maintenance is depicted as an activity towards the end of the software life cycle. The high cost ascribed to software maintenance motivates for improvements. The maintenance concept TQMain proposed in this thesis distinguishes from other maintenance concepts by its use of preventive, predictive and proactive maintenance strategies. TQMain uses a common database to store real-time data from various departments and uses it for analyse and assessment to track the development of deviations in the condition of the production process and product quality at an early stage. A continuous cyclic improvement of the maintenance strategy is reached by comparing the data from the real-time measurements with data from the database. The ISO/IEC Software engineering – Product qualities is used as a source of empiric data to conclude that the correct quality characteristics are used for identifying software product quality and its characteristics and compare them with the characteristics of industrial product quality. The results presented are that in the conceptual outline of TQMain measures are obviously not the same as in software maintenance, but the aspect of product quality is common for both. The continuous cyclic improvement of the product quality that TQMain features together with the aspect of detecting potential failures before they occur would, judging from the conceptual outline of TQMain be applicable on software maintenance.

APA, Harvard, Vancouver, ISO, and other styles

9

Kwan, Irwin. "On the Maintenance Costs of Formal Software Requirements Specification Written in the Software Cost Reduction and in the Real-time Unified Modeling Language Notations." Thesis, University of Waterloo, 2005. http://hdl.handle.net/10012/1092.

Full text

Abstract:

A formal specification language used during the requirements phase can reduce errors and rework, but formal specifications are regarded as expensive to maintain, discouraging their adoption. This work presents a single-subject experiment that explores the costs of modifying specifications written in two different languages: a tabular notation, Software Cost Reduction (SCR), and a state-of-the-practice notation, Real-time Unified Modeling Language (UML). The study records the person-hours required to write each specification, the number of defects made during each specification effort, and the amount of time repairing these defects. Two different problems are specified—a Bidirectional Formatter (BDF), and a Bicycle Computer (BC)—to balance a learning effect from specifying the same problem twice with different specification languages. During the experiment, an updated feature for each problem is sent to the subject and each specification is modified to reflect the changes.

The results show that the cost to modify a specification are highly dependent on both the problem and the language used. There is no evidence that a tabular notation is easier to modify than a state-of-the-practice notation.

A side-effect of the experiment indicates there is a strong learning effect, independent of the language: in the BDF problem, the second time specifying the problem required more time, but resulted in a better-quality specification than the first time; in the BC problem, the second time specifying the problem required less time and resulted in the same quality specification as the first time.

This work demonstrates also that single-subject experiments can add important information to the growing body of empirical data about the use of formal requirements specifications in software development.

APA, Harvard, Vancouver, ISO, and other styles

10

Saigal, Nalin. "Modularizing Crosscutting Concerns in Software." Scholar Commons, 2011. http://scholarcommons.usf.edu/etd/3327.

Full text

Abstract:

Code modularization provides benefits throughout the software life cycle; however, the presence of crosscutting concerns (CCCs) in software hinders its complete modularization. Traditional modularization techniques work well under the assumption that code being modularized is functionally orthogonal to the rest of the code; as a result, software engineers try to separate code segments that are orthogonal in their functionality into distinct modules. However, in practice, software does not decompose neatly into modules with distinct, orthogonal functionality. In this thesis, we investigate the modularization of CCCs in software using two different techniques. Firstly, we discuss IVCon, a GUI-based tool that provides a novel approach to the modularization of CCCs. We have designed IVCon to capture the multi-concern nature of code. IVCon enables users to create, examine, and modify their code in two different views, the woven view and the unwoven view. The woven view displays program code in colors that indicate which CCCs various code segments implement, while the unwoven view displays code in two panels, one showing the core of the program and the other showing all the code implementing each concern in an isolated module. IVCon aims to provide an easy-to-use interface for conveniently creating, examining, and modifying code in, and translating between, the woven and unwoven views. Secondly, we discuss LoPSiL, which is a location-based policy-specification language. LoPSiL is Turing-complete and provides users with language constructs that enable them to manipulate location information; hence, LoPSiL can be used to specify and enforce generic policies that might involve location-based constraints. We have implemented a LoPSiL compiler using AspectJ, and we observe and discuss how the use of traditional units of modularization---aspects in this case---help modularize functionally orthogonal CCCs such as security and auditing.

APA, Harvard, Vancouver, ISO, and other styles

11

Hutton, Alistair James. "An empirical investigation of issues relating to software immigrants." Thesis, Connect to e-thesis, 2008. http://theses.gla.ac.uk/136/.

Full text

Abstract:

Thesis (Ph.D.) - University of Glasgow, 2008.
Ph.D. thesis submitted to the Department of Computing Science, Faculty of Information and Mathematical Sciences, University of Glasgow, 2008. Includes bibliographical references. Print version also available.

APA, Harvard, Vancouver, ISO, and other styles

12

Clause, James Alexander. "Enabling and supporting the debugging of software failures." Diss., Georgia Institute of Technology, 2011. http://hdl.handle.net/1853/39514.

Full text

Abstract:

This dissertation evaluates the following thesis statement: Program analysis techniques can enable and support the debugging of failures in widely-used applications by (1) capturing, replaying, and, as much as possible, anonymizing failing executions and (2) highlighting subsets of failure-inducing inputs that are likely to be helpful for debugging such failures. To investigate this thesis, I developed techniques for recording, minimizing, and replaying executions captured from users' machines, anonymizing execution recordings, and automatically identifying failure-relevant inputs. I then performed experiments to evaluate the techniques in realistic scenarios using real applications and real failures. The results of these experiments demonstrate that the techniques can reduce the cost and difficulty of debugging.

APA, Harvard, Vancouver, ISO, and other styles

13

LaFond, Karen A. "The evaluation of project management performance on two software maintenance projects based on a CMMI framework." Thesis, Monterey, Calif. : Springfield, Va. : Naval Postgraduate School ; Available from National Technical Information Service, 2006. http://library.nps.navy.mil/uhtbin/hyperion/06Jun%5FLaFond.pdf.

Full text

Abstract:

Thesis (M.S. in Software Engineering)--Naval Postgraduate School, June 2006.
Thesis Advisor(s): Man-Tak Shing, Russell H. Menko. "June 2006." Includes bibliographical references (p. 89-90). Also available in print.

APA, Harvard, Vancouver, ISO, and other styles

14

Williams, Byron Joseph. "CHANGE DECISION SUPPORT: EXTRACTION AND ANALYSIS OF LATE ARCHITECTURE CHANGES USING CHANGE CHARACTERIZATION AND SOFTWARE METRICS." MSSTATE, 2009. http://sun.library.msstate.edu/ETD-db/theses/available/etd-03312009-022436/.

Full text

Abstract:

Software maintenance is one of the most crucial aspects of software development. Software engineering researchers must develop practical solutions to handle the challenges presented in maintaining mature software systems. Research that addresses practical means of mitigating the risks involved when changing software, reducing the complexity of mature software systems, and eliminating the introduction of preventable bugs is paramount to todays software engineering discipline. Giving software developers the information that they need to make quality decisions about changes that will negatively affect their software systems is a key aspect to mitigating those risks. This dissertation presents work performed to assist developers to collect and process data that plays a role in change decision-making during the maintenance phase. To address these problems, developers need a way to better understand the effects of a change prior to making the change. This research addresses the problems associated with increasing architectural complexity caused by software change using a two-fold approach. The first approach is to characterize software changes to assess their architectural impact prior to their implementation. The second approach is to identify a set of architecture metrics that correlate to system quality and maintainability and to use these metrics to determine the level of difficulty involved in making a change. The two approaches have been combined and the results presented provide developers with a beneficial analysis framework that offers insight into the change process.

APA, Harvard, Vancouver, ISO, and other styles

15

Pierson, Graham C. "Code maintenance and design for a visual programming language graphical user interface." Thesis, Monterey, Calif. : Springfield, Va. : Naval Postgraduate School ; Available from National Technical Information Service, 2004. http://library.nps.navy.mil/uhtbin/hyperion/04Sep%5FPierson.pdf.

Full text

APA, Harvard, Vancouver, ISO, and other styles

16

Brückmann, Tobias. "Model Driven Development and Maintenance of Business Logic for Information Systems." Doctoral thesis, Universitätsbibliothek Leipzig, 2011. http://nbn-resolving.de/urn:nbn:de:bsz:15-qucosa-64148.

Full text

Abstract:

Since information systems become more and more important in today\'s society, business firms, organizations, and individuals rely on these systems to manage their daily business and social activities. The dependency of possibly critical business processes on complex IT systems requires a strategy that supports IT departments in reducing the time needed to implement changed or new domain requirements of functional departments. In this context, software models help to manage system\'s complexity and provide a tool for communication and documentation purposes. Moreover, software engineers tend to use automated software model processing such as code generation to improve development and maintenance processes. Particularly in the context of web-based information systems, a number of model driven approaches were developed. However, we believe that compared to the user interface layer and the persistency layer, there could be a better support of consistent approaches providing a suitable architecture for the consistent model driven development of business logic. To ameliorate this situation, we developed an architectural blueprint consisting of meta models, tools, and a method support for model driven development and maintenance of business logic from analysis until system maintenance. This blueprint, which we call Amabulo infrastructure, consists of five layers and provides concepts and tools to set up and apply concrete infrastructures for model driven development projects. Modeling languages can be applied as needed. In this thesis we focus on business logic layers of J2EE applications. However, concrete code generation rules can be adapted easily for different target platforms. After providing a high-level overview of our Amabulo infrastructure, we describe its layers in detail: The Visual Model Layer is responsible for all visual modeling tasks. For this purpose, we discuss requirements for visual software models for business logic, analyze several visual modeling languages concerning their usefulness, and provide an UML profile for business logic models. The Abstract Model Layer provides an abstract view on the business logic model in the form of a domain specific model, which we call Amabulo model. An Amabulo model is reduced to pure logical information concerning business logic aspects. It focuses on information that is relevant for the code generation. For this purpose, an Amabulo model integrates model elements for process modeling, state modeling, and structural modeling. It is used as a common interface between visual modeling languages and code generators. Visual models of the Visual Model Layer are automatically transformed into an Amabulo model. The Abstract System Layer provides a formal view onto the system in the form of a Coloured Petri Net (CPN). A Coloured Petri Net representation of the modeled business logic is a formal structure and independent of the actual business logic implementation. After an Amabulo model is automatically transformed into a CPN, it can be analyzed and simulated before any line of code is generated. The Code Generation Layer is responsible for code generation. To support the design and implementation of project-specific code generators, we discuss several aspects of code integration issues and provide object-oriented design approaches to tackle the issues. Then, we provide a conceptual mapping of Amabulo model elements into architectural elements of a J2EE infrastructure. This mapping explicitly considers robustness features, which support a later manual integration of generated critical code artifacts and external systems. The Application Layer is the target layer of an Amabulo infrastructure and comprises generated code artifacts. These artifacts are instances of a specific target platform specification, and they can be modified for integration purposes with development tools. Through the contributions in this thesis, we aim to provide an integrated set of solutions to support an efficient model driven development and maintenance process for the business logic of information systems. Therefore, we provide a consistent infrastructure blueprint that considers modeling tasks, model analysis tasks, and code generation tasks. As a result, we see potential for reducing the development and maintenance efforts for changed domain requirements and simultaneously guaranteeing robustness and maintainability even after several changes.

APA, Harvard, Vancouver, ISO, and other styles

17

Santelices, Raul A. "Change-effects analysis for effective testing and validation of evolving software." Diss., Georgia Institute of Technology, 2012. http://hdl.handle.net/1853/44737.

Full text

Abstract:

The constant modification of software during its life cycle poses many challenges for developers and testers because changes might not behave as expected or may introduce erroneous side effects. For those reasons, it is of critical importance to analyze, test, and validate software every time it changes. The most common method for validating modified software is regression testing, which identifies differences in the behavior of software caused by changes and determines the correctness of those differences. Most research to this date has focused on the efficiency of regression testing by selecting and prioritizing existing test cases affected by changes. However, little attention has been given to finding whether the test suite adequately tests the effects of changes (i.e., behavior differences in the modified software) and which of those effects are missed during testing. In practice, it is necessary to augment the test suite to exercise the untested effects. The thesis of this research is that the effects of changes on software behavior can be computed with enough precision to help testers analyze the consequences of changes and augment test suites effectively. To demonstrate this thesis, this dissertation uses novel insights to develop a fundamental understanding of how changes affect the behavior of software. Based on these foundations, the dissertation defines and studies new techniques that detect these effects in cost-effective ways. These techniques support test-suite augmentation by (1) identifying the effects of individual changes that should be tested, (2) identifying the combined effects of multiple changes that occur during testing, and (3) optimizing the computation of these effects.

APA, Harvard, Vancouver, ISO, and other styles

18

Reddy, Rohini Mopu. "Easy Net Admin: Inventory tool for network administrators." CSUSB ScholarWorks, 2004. https://scholarworks.lib.csusb.edu/etd-project/2582.

Full text

Abstract:

The purpose of this project was to develop a tool / utility for network administrators to maintain information about all the systems operated by the College of Natural Sciences at California State University, San Bernardino.

APA, Harvard, Vancouver, ISO, and other styles

19

Kadri, Reda. "Proposition d'une méthode et d'un outil pour le développement d'applications." Phd thesis, Université de Bretagne Sud, 2009. http://tel.archives-ouvertes.fr/tel-00511828.

Full text

Abstract:

De nos jours, le traitement de l'information par l'intermédiaire d'applications Web est largement adopté. Les avantages de ces applications ne sont plus, aujourd'hui, à démontrer et leur adoption massive par les entreprises ou par les administrations est un fait indéniable. Nous remarquons, par exemple, la forte émergence d'applications et de systèmes collaboratifs de gestion de contenus en ligne, de syndication, d'importation et d'exportation de données. En plus du développement de nouvelles applications Web, les entreprises doivent, maintenant, faire face aux demandes de transformations, ou de pseudo migration, des applications de type Desktops vers le mode Web. Ainsi, des milliers d'applications de différents domaines sont appelées à être déployées sur le Web. Ainsi, dans un futur proche, nous n'aurons plus besoin d'installer de logiciels sur nos ordinateurs ni même d'y stocker des fichiers. En effet, d'ores-et-déjà, tous ces services peuvent être rendus par le Web 2.0. Chaque application ou presque a son pendant en ligne, qu'il s'agisse de retoucher une image, de faire du montage vidéo, de convertir des fichiers, de créer des documents, etc. L'objectif de cette thèse, dans le cadre d'une collaboration entre Alkante (société spécialisée dans le conseil et l'ingénierie des technologies de l'information) et le Valoria, est d'offrir un cadre (outils et méthodes) pour faciliter, dans le paradigme composant, le développement et l'évolution d'applications Web. Mon premier travail a consisté à proposer un protocole de migration permettant un passage, en douceur, d'un processus de développement classique à un processus de développement à base de composants logiciels. Ce protocole a rendu possible la réutilisation de codes existants et a permis, aux développeurs, de se familiariser avec les concepts et les bases du développement à base de composants logiciels. Une fois cette migration effectuée, j'ai proposé une nouvelle approche pour la modélisation d'applications Web dans un contexte purement composant. Cependant, une autre question liée à la maintenance et aux coûts d'évolution se posait. Les applications Web sont particulièrement sujettes à de nombreuses évolutions, très régulières dans le temps. Afin de maîtriser l'évolution des applications développées et pour réduire les coûts de maintenance, j'ai utilisé une solution appelée contrats d'évolution.

APA, Harvard, Vancouver, ISO, and other styles

20

Fleurquin, Régis. "Des langages pour améliorer le développement et la maintenance des logiciels à base de composants." Habilitation à diriger des recherches, Université de Bretagne Sud, 2010. http://tel.archives-ouvertes.fr/tel-00511595.

Full text

Abstract:

La définition d'éléments pouvant contribuer à améliorer le développement et la maintenance des logiciels est l'objectif des travaux de recherche menés en Génie Logiciel. Mon domaine de recherche porte depuis 2003 sur la définition et l'usage de langages « supports » (c'est-à-dire complétant les langages de développement) ; ceci dans le but de faciliter et d'améliorer le développement et la maintenance des applications logicielles conçues à l'aide de composants. Mes travaux se trouvent au carrefour de plusieurs disciplines du Génie Logiciel : le développement orienté composant, les architectures des logiciels, la maintenance et l'évolution, la qualité et l'ingénierie dirigée par les modèles. Ce document constitue une synthèse de mes activités de recherche menées au cours des sept dernières années au sein de l'équipe SE du laboratoire VALORIA et de l'équipe-projet INRIA TRISKELL. Il commence par donner une vision assez personnelle des courants qui animent le Génie Logiciel et dresse un aperçu de l'état actuel de cette discipline. Puis il introduit les quelques notions dont la maîtrise est nécessaire pour évoluer dans les domaines dans lesquels se sont déroulées mes activités. Il retrace ensuite mon parcours thématique au cœur de ces disciplines et détaille mes travaux sur le contrôle de l'évolution des architectures, la sélection de composants et la documentation et l'exécution des bonnes pratiques de modélisation.

APA, Harvard, Vancouver, ISO, and other styles

21

Deraman, Aziz B. "A computer-aided software maintenance process model." Thesis, University of Manchester, 1992. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.261996.

Full text

APA, Harvard, Vancouver, ISO, and other styles

22

AlSuhaibani, Reem Saleh. "Part-of-Speech Tagging of Source Code Identifiers using Programming Language Context Versus Natural Language Context." Kent State University / OhioLINK, 2015. http://rave.ohiolink.edu/etdc/view?acc_num=kent1448502094.

Full text

APA, Harvard, Vancouver, ISO, and other styles

23

Le, Gal Thierry. "Re-engineering software for integration using computer aided software engineering." Thesis, This resource online, 1992. http://scholar.lib.vt.edu/theses/available/etd-06232009-063016/.

Full text

APA, Harvard, Vancouver, ISO, and other styles

24

Meqdadi, Omar Mohammed. "UNDERSTANDING AND IDENTIFYING LARGE-SCALE ADAPTIVE CHANGES FROM VERSION HISTORIES." Kent State University / OhioLINK, 2013. http://rave.ohiolink.edu/etdc/view?acc_num=kent1374791564.

Full text

APA, Harvard, Vancouver, ISO, and other styles

25

Bhatti, Muhammad Usman. "Object Identification and Aspect Mining in Procedural Object-Oriented Code." Phd thesis, Université Panthéon-Sorbonne - Paris I, 2009. http://tel.archives-ouvertes.fr/tel-00498436.

Full text

Abstract:

In this dissertation, we present Procedural Object-Oriented Code (POC). POC is the aftermath of the software development activity that involves state of the art object-oriented languages, without employing object-oriented analysis and design. Huge classes, absence of abstractions for domain entities, and shallow inheritance hierarchies are hallmark design defects of procedural object-oriented code. POC also consists of scattered code appearing not only due to the absence of aspects, but it also manifests scattered code appearing due to the non-abstracted domain enti- ties i.e., domain entities that do not have their proper object-oriented classes. The non-abstracted domain logic hinders mining useful crosscutting concerns related to aspects in POC. Confronted with the absence of object-oriented design and the difficulty of mining aspects in POC, we studied it from two perspectives. First, we improve aspect mining techniques by classifying various crosscutting concerns identified in POC with a two-pronged approach: Firstly, the approach identifies and groups crosscutting concerns present in a software system: aspects as well as non-abstracted domain logic. Crosscutting concerns pertaining to non- abstracted domain entities are identified and extracted through their usage of appli- cation domain entity data. Secondly, a new metric called spread-out is introduced to quantify the divulgence of diverse crosscutting concerns. Second, we studied the problem of object identification in procedural object- oriented code. We present a semi-automatic, tool-assisted approach for restructuring POC into an improved object-oriented design. The approach identifies principal classes in POC. These principal classes are then used to extract object-oriented abstractions using Formal Concept Analysis lattices. This is achieved by providing three different concept lattices, namely fundamental, association, and interactions views. We developed tools to validate the approaches presented in the thesis. The approaches are validated on a recently developed industrial application. The appli- cation is used to run blood plasma analysis automatons. The results of our approach are promising.

APA, Harvard, Vancouver, ISO, and other styles

26

Katiyar, Kirti. "CARES - Computer Aided Rehabilitation Software." CSUSB ScholarWorks, 2005. https://scholarworks.lib.csusb.edu/etd-project/2857.

Full text

Abstract:

This project was done with the vision that it would simplify and improve outpatient treatment of substance abusers through a rehabilitation software program with 24-7 access availability. By developing an easy-to-use interface for out-patient substance abuse patients, they along with their counselors, administrators and insurance agencies, will be able to facilitate continuous communication during the course of a patient's treatment.

APA, Harvard, Vancouver, ISO, and other styles

27

Tanga, Rajan M. "Computer aided software engineering tool for generating C code." Ohio : Ohio University, 1988. http://www.ohiolink.edu/etd/view.cgi?ohiou1182872759.

Full text

APA, Harvard, Vancouver, ISO, and other styles

28

Clomera, Arthur B. "Extending the computer-aided software evolution system (CASES) with quality function deployment (QFD)." Thesis, Monterey, Calif. : Springfield, Va. : Naval Postgraduate School ; Available from National Technical Information Service, 2003. http://library.nps.navy.mil/uhtbin/hyperion-image/03Jun%5FClomera.pdf.

Full text

Abstract:

Thesis (M.S. in Software Engineering)--Naval Postgraduate School, June 2003.
Thesis advisor(s): Man-Tak Shing, Josseph F. Puett III. Includes bibliographical references (p. 445-446). Also available online.

APA, Harvard, Vancouver, ISO, and other styles

29

Jennings, Charles A. "Re-engineering software systems in the Department of Defense using integrated computer aided software engineering tools." Thesis, Monterey, California. Naval Postgraduate School, 1992. http://hdl.handle.net/10945/23761.

Full text

APA, Harvard, Vancouver, ISO, and other styles

30

Manley, Gary W. "The classification and evaluation of Computer-Aided Software Engineering tools." Thesis, Monterey, California: Naval Postgraduate School, 1990. http://hdl.handle.net/10945/34910.

Full text

Abstract:

Approved for public release; distribution unlimited.
The use of Computer-Aided Software Engineering (CASE) tools has been viewed as a remedy for the software development crisis by achieving improved productivity and system quality via the automation of all or part of the software engineering process. The proliferation and tremendous variety of tools available have stretched the understanding of experienced practitioners and has had a profound impact on the software engineering process itself. To understand what a tool does and compare it to similar tools is a formidable task given the existing diversity of functionality. This thesis investigates what tools are available, proposes a general classification scheme to assist those investigating tools to decide where a tool falls within the software engineering process and identifies a tool's capabilities and limitations. This thesis also provides guidance for the evaluation of a tool and evaluates three commercially available tools.

APA, Harvard, Vancouver, ISO, and other styles

31

Gavin, Carl Jospeh. "The application of Computer-Aided Software Engineering within manufacturing industry." Thesis, University of Liverpool, 1994. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.241486.

Full text

APA, Harvard, Vancouver, ISO, and other styles

32

Abdeen, Hani. "Visualizing, Assessing and Re-Modularizing Object-Oriented Architectural Elements." Phd thesis, Université des Sciences et Technologie de Lille - Lille I, 2009. http://tel.archives-ouvertes.fr/tel-00498389.

Full text

Abstract:

To cope with the complexity of large object-oriented software systems, developers organize classes into subsystems using the concepts of module or package. Such modular structure helps software systems to evolve when facing new requirements. The organization of classes into packages and/or subsystems represents the software modularization. the software modularization usually follows interrelationships between classes. Ideally, packages should to be loosely coupled and cohesive to a certain extent. However, Studies show that as software evolves to meet requirements and environment changes, the software modularization gradually drifts and looses quality. As a consequence, the software modularization must be maintained. It is thus important to understand, to assess and to optimize the organization of packages and their relationships. Our claim is that the maintenance of large and complex software modularizations needs approaches that help in: (1) understanding package shapes and relationships; (2) assessing the quality of a modularization, as well as the quality of a single package within a given modularization; (3) optimizing the quality of an existing modulariza- tion. In this thesis, we concentrate on three research fields: software visualizations, metrics and algorithms. At first, we define two visualizations that help maintainers: (1) to understand packages structure, usage and relationships; (2) to spot patterns; and (3) to identify misplaced classes and structural anomalies. In addition to visual- izations, we define a suite of metrics that help in assessing the package design quality (i.e., package cohesion and coupling). We also define metrics that assess the quality of a collection of inter-dependent packages from different view points, such as the degree of package coupling and cycles. Finally, we define a search-based algorithm that automatically reduces package coupling and cycles only by moving classes over existing packages. Our optimization approach takes explicitly into account the origi- nal class organization and package structure. It also allows maintainers to control the optimization process by specifying: (1) the maximal number of classes that may change their packages; (2) the classes that are candidate for moving and the classes that should not; (3) the packages that are candidate for restructuring and the packages that should not; and (4) the maximal number of classes that a given package can entail. The approaches presented in this thesis have been applied to real large object- oriented software systems. The results we obtained demonstrate the usefulness of our visualizations and metrics; and the effectiveness of our optimization algorithm.

APA, Harvard, Vancouver, ISO, and other styles

33

Favre, Jean-Marie. "Une approche pour la maintenance et la ré-ingénierie globale des logiciels." Phd thesis, Université Joseph Fourier (Grenoble), 1995. http://tel.archives-ouvertes.fr/tel-00724676.

Full text

Abstract:

Alors que l'informatique est résolument tournée vers l'avenir, cette thèse se concentre sur le passé ; non pas par nostalgie mais plutôt parce que le futur des logiciels âgés est une question d'actualité. Plus particulièrement trois thèmes sont abordés : la maintenance, la ré-ingénierie et la programmation globale. L'objectif de cette étude est d'explorer l'intersection entre la ré-ingénierie et la programmation globale, domaine que nous avons baptisé ré-ingénierie globale. L'idée principale est de réutiliser des concepts et des techniques de programmation détaillée. En fait nous proposons de définir la programmation globale en distinguant 4 aspects du logiciel : l'architecture, la manufacture, la variation et l'évolution. Un modèle abstrait basé sur des concepts ensemblistes est proposé pour modéliser les différentes entités de programmation globale. La technologie relative à ce domaine est ensuite décrite en considérant aussi bien l'état de l'art que l'état de la pratique. La différence entre ces deux aspects souligne l'intérêt de la ré-ingénierie globale. A titre d'illustration, nous étudions le cas des préprocesseurs en tant qu'outils de programmation globale. Ces outils de bas niveau provenant des années 70 sont traditionnellement utilisés pour décrire des familles de programmes. Pour faciliter la compréhension de tels artefacts nous proposons d'utiliser des techniques comme l'évaluation partielle, l'analyse inter-procédurale de flot de données ou encore le découpage. Ces techniques, définies de manière rigoureuse, s'appuient sur la sémantique dénotationnelle du préprocesseur utilisé. Un prototype montrant leur utilité a été réalisé. Il prouve qu'une approche basée sur des fondements théoriques issus de la programmation détaillée est applicable pour résoudre des problèmes pratiques de programmation globale.

APA, Harvard, Vancouver, ISO, and other styles

34

Ouerd, Messaouda. "An algorithm directed computer aided software engineering (CASE) environment for C." Thesis, University of Ottawa (Canada), 1990. http://hdl.handle.net/10393/5964.

Full text

Abstract:

The objectives of computer aided software engineering (CASE) systems are to improve productivity during the software development process and the quality of software using software engineering concepts via automation of the software development life cycle. This will result in a reusable software and will decrease the cost and time of software development and maintenance. The main concern in this thesis is with describing the features of a particular software understanding environment for C. An algorithm directed computer aided software engineering environment for C language has been developed and implemented. The system has been implemented on a Sun Workstation using the Sunview window interface. It provides computer aided software engineering tools which: (1) Assist the user in developing structured algorithms for procedural languages; (2) Automatically transform a structured algorithm into a corresponding program; (3) Redocument the resulting C program (or any C program developed using any other technique) in an organized representation.

APA, Harvard, Vancouver, ISO, and other styles

35

Milinkovich, S. Michael (Michael Steven) Carleton University Dissertation Information and Systems Science. "An Object-oriented database for a computer aided software engineering environment." Ottawa, 1988.

Find full text

APA, Harvard, Vancouver, ISO, and other styles

36

Yetkin, Recep Erdinc Enriquez Sotero. "Re-engineering portabililty of the Computer Aided Prototyping System (CAPS) /." Monterey, Calif. : Springfield, Va. : Naval Postgraduate School ; Available from National Technical Information Service, 1997. http://handle.dtic.mil/100.2/ADA333411.

Full text

APA, Harvard, Vancouver, ISO, and other styles

37

Su, Mehmet Onur. "Business Process Moedlling Based Computer-aided Software Functional Requirements Generation." Master's thesis, METU, 2004. http://etd.lib.metu.edu.tr/upload/3/12604698/index.pdf.

Full text

Abstract:

Problems of requirements which are identified in the earlier phase of a software development project can deeply affect the success of the project. Thus studies which aim to decrease these problems are crucial. Automation is foreseen to be one of the possible solutions for decreasing or removing some of the problems originating from requirements. This study focuses on the development and implementation of an automated tool that will generate requirements in natural language from business process models. In this study, The benefits of the tool are discussed, and the tool is compared with other software requirement s related tools with respect to their functionality. The developed tool has been tested within a large military project and the results of using the tool are presented.

APA, Harvard, Vancouver, ISO, and other styles

38

Son, Ju Young. "Computer aided software engineering tool for automatically generating database management system code." Ohio : Ohio University, 1989. http://www.ohiolink.edu/etd/view.cgi?ohiou1182519080.

Full text

APA, Harvard, Vancouver, ISO, and other styles

39

Grieshaber, Michele Marie. "A computer-aided software engineering toolkit for the integration of CAD/CAM application software in a network environment." Diss., Virginia Tech, 1991. http://hdl.handle.net/10919/37875.

Full text

Abstract:

Much progress has been made in recent years in the development of Computer-Aided Design and Computer-Aided Manufacturing (CAD/CAM) tools for engineering design, analysis, and manufacturing. Unfortunately, most of these CAD/CAM applications were constructed independently and without standardization. In essence, they automate a single aspect of design, analysis, or manufacturing and cannot be combined to form a cohesive environment, since integration among applications was not addressed during the design phase of CAD/CAM application software creation. In view of this problem, a novel approach is suggested for software integration of applications in a network environment. The distributed integration solution described in this dissertation employs a new "integration client/server" relationship, where the integration server is the core of the system, providing functions to translate or transform data between applications. The integration client consists of an interface with the server, a CAD/CAM application, and a user interface with the integrated system called the GRIM (GRaphical Interface Manager). There is only one integration server in the system, but there may be an unlimited number of clients. The solution created for distributed integration is implemented in a Computer-Aided Software Engineering (CASE) workbench, geared specifically toward the generation of integration systems. This workbench is known as the CAD/CAM CASE Workbench, and includes an integration solution as well as standard CASE tools. The integration solution contains several tools which will aid a system designer in generating integration systems for CAD/CAM applications. Included is the distributed integration solution described in this dissertation. The distributed integration solution is designed to facilitate the semi-automatic generation of an integration system. It consists of an integration server at the center of the integration system which manages the exchange of data among the integration clients. The integration clients are the CAD/CAM applications in the context of the integration system. To use the distributed integration solution, the integration system designer will customize portions of the structure charts, data dictionary, and module specifications contained in the workbench according to the needs of the applications programs and generate C-source code defining the integration system. Using the distributed integration solution, the user will be able to effect data requests for applications, using the GRIM to interact with the system. All data exchanges are request driven. In addition to the distributed integration solution, this research includes a prototype integrated system which allows data to be requested from one application, and translated to a second for display and manipulation. The prototype was tested in a distributed environment and the results are described.
Ph. D.

APA, Harvard, Vancouver, ISO, and other styles

40

Lin, Chungping. "The RMT (Recursive multi-threaded) tool: A computer aided software engineeering tool for monitoring and predicting software development progress." CSUSB ScholarWorks, 1998. https://scholarworks.lib.csusb.edu/etd-project/1787.

Full text

APA, Harvard, Vancouver, ISO, and other styles

41

Huang, He. "Case-based expert system using wavelet packet transform and kernel-based feature manipulation for engine spark ignition diagnosis." Thesis, University of Macau, 2010. http://umaclib3.umac.mo/record=b2148260.

Full text

APA, Harvard, Vancouver, ISO, and other styles

42

Sanlaville, Rémy. "Architecture logicielle : une expérimentation industrielle avec Dassault Systèmes." Phd thesis, Université Joseph Fourier (Grenoble), 2002. http://tel.archives-ouvertes.fr/tel-00004589.

Full text

Abstract:

L'architecture logicielle est un domaine récent du génie logiciel qui a reçu une attention particulière ces dix dernières années. Les éditeurs de logiciels ont pris conscience qu'une architecture est un facteur critique dans la réussite du développement et facilite la maintenance et l'évolution du logiciel. Elle contribue à la maîtrise des grands logiciels. L'architecture logicielle permet d'améliorer ces aspects grâce à l'étude des structures de haut niveau du logiciel. De nombreuses avancées ont été proposées au niveau de la formalisation par des Langages de Description d'Architecture (ADLs: Architecture Description Languages), du raisonnement et de l'analyse au niveau architectural. Bien que la communauté scientifique ait réalisé des progrès significatifs, les résultats restent essentiellement académiques. Les retombées de ces recherches ont du mal à pénétrer le milieu industriel. Ce rapport de thèse relate notre expérience avec Dassault Systèmes : répondre aux besoins de Dassault Systèmes pour le développement de ses logiciels en utilisant une approche basée sur l'architecture logicielle. Dassault Systèmes est le leader mondial de la Conception Assistée par Ordinateur (CAO) avec son logiciel phare CATIA V5 (~5 MLoc). Pour atteindre cet objectif, nous avons parcouru les principales approches pour la description d'une architecture logicielle et tenté de les appliquer dans notre contexte industriel. Nous expliquerons les difficultés que nous avons rencontrées pour les utiliser et montrerons pourquoi ces approches ne sont pas adaptées pour la maintenance et l'évolution d'un logiciel tel que CATIA V5. Nous décrirons notre démarche basée sur l'analyse des besoins architecturaux des différents acteurs de Dassault Systèmes qui a permis de fournir des solutions concrètes et exploitables. Enfin, nous expliciterons ces besoins architecturaux et présenterons les divers prototypes que nous avons développés pour y répondre.

APA, Harvard, Vancouver, ISO, and other styles

43

LaGuardia, John Louis. "Computer Aided Parametric Screw Design and Analysis Using Pro/Engineer Solid Modeling Software." University of Akron / OhioLINK, 2009. http://rave.ohiolink.edu/etdc/view?acc_num=akron1237988201.

Full text

APA, Harvard, Vancouver, ISO, and other styles

44

Stobart, Simon. "Automated support for the implementation phase of the software development cycle : an investigation." Thesis, University of Sunderland, 1997. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.361205.

Full text

APA, Harvard, Vancouver, ISO, and other styles

45

De, los Reyes Adrian. "The role of computer-aided drafting, analysis, and design software in structural engineering practice." Thesis, Massachusetts Institute of Technology, 2006. http://hdl.handle.net/1721.1/35080.

Full text

Abstract:

Thesis (M. Eng.)--Massachusetts Institute of Technology, Dept. of Civil and Environmental Engineering, 2006.
Includes bibliographical references (p. 102-103).
Perhaps the greatest innovation in engineering in the last fifty years, computer software has changed the way structural engineers conduct nearly every aspect of their daily business. Computer-aided drafting, analysis, and design software are invaluable tools for any structural engineering firm. Given the growth, extensive competition, and demands of the industry, a firm cannot survive if it does not take advantage of the powers and capabilities that modem computer software offer. Computers have drastically altered the way engineers communicate with co-workers, clients, architects, and construction managers, improving the efficiency of the design delivery system and facilitating the conveying of design changes, issues, and concerns between all entities involved in a project. This software has optimized the structural drafting, analysis, and design processes in ways engineers never could have imagined possible half a century ago. These innovations not only add up to major savings in construction costs and increased profits for all parties involved in a project, but also to more accurate designs, quicker design completions, improved organization and sharing of data, and higher productivity within the engineering office.
(cont.) This thesis examines the applications of computer software in the structural engineering industry, its effects both positive and negative, the professional and legal responsibility of engineers to use software wisely, methods of checking the results of computer analysis and design programs, recent innovations and the future of structural engineering computer software, and the importance of educating future structural engineers on the use of computer software. An examination of the drafting, structural analysis, and design of two complex structures using three-dimensional modeling programs is included to illustrate the value and correct use of structural engineering computer software. It is the intention of this thesis to highlight the benefits and dangers associated with the use of computer software in the structural engineering industry and to inspire innovations in the technology and capabilities of such software.
by Adrian de los Reyes.
M.Eng.

APA, Harvard, Vancouver, ISO, and other styles

46

Oliver, Stephen E. "T[subscript]EXspec, a Computer Aided Software Engineering tool for scientific and mathematical applications." Thesis, National Library of Canada = Bibliothèque nationale du Canada, 2001. http://www.collectionscanada.ca/obj/s4/f2/dsk3/ftp05/mq62813.pdf.

Full text

APA, Harvard, Vancouver, ISO, and other styles

47

DEBONI, JOSE E. Z. "Metodo para integracao de sistemas de apoio a engenharia atraves da reutilizacao de software." reponame:Repositório Institucional do IPEN, 1997. http://repositorio.ipen.br:8080/xmlui/handle/123456789/10501.

Full text

Abstract:

Made available in DSpace on 2014-10-09T12:41:12Z (GMT). No. of bitstreams: 0
Made available in DSpace on 2014-10-09T14:08:32Z (GMT). No. of bitstreams: 1 04672.pdf: 5899292 bytes, checksum: 2ce0b22a333f0012e1da4d7c3da1b4f7 (MD5)
Tese (Doutoramento)
IPEN/T
Escola Politecnica, Universidade de Sao Paulo - POLI/USP

APA, Harvard, Vancouver, ISO, and other styles

48

Kwon, Jimmy Y. (Jimmy Yongil). "Remote fabrication of integrated circuits : software support for the M.I.T. computer aided fabrication environment." Thesis, Massachusetts Institute of Technology, 1995. http://hdl.handle.net/1721.1/37794.

Full text

APA, Harvard, Vancouver, ISO, and other styles

49

Cournoyer, Richard John. "The Application of Parametric Software into the Undergraduate Computer-Aided Manufacturing Environment." Digital WPI, 1999. https://digitalcommons.wpi.edu/etd-theses/1078.

Full text

Abstract:

"This thesis presents an in depth study of Pro/Engineer's manufacturing module and its application into the Computer-Aided Manufacturing (CAM) undergraduate education environment. Mechanical Engineering has a lot to gain by incorporating computers into the undergraduate curriculum in comparison to only the traditional classroom surroundings. Today, complex problems can be solved in mere seconds thanks to the power and speed of current computers. Likewise within today's manufacturing sector, numerical controlled (NC) machines are no longer programmed manually. In today's globally competitive manufacturing environment, integrated systems such as CAD/CAM help reduce the ever-shrinking time to market. This thesis contains the background as well as the curriculum material necessary to teach undergraduate students CAM using Pro/Engineer's manufacturing module. The curriculum material starts with the tutorials to teach and reinforce Pro/Engineer basic sketcher skills, which are necessary background information. Followed with in-depth click tutorials to teach the manufacturing module for 2 axes turning, and 3 axes hole drilling and milling. It also includes the necessary lab manuals that reinforce the class lecture material, an electronic manufacturing exam, and the students' evaluations from 2 terms when the CAM course (ME3820) was offered."

APA, Harvard, Vancouver, ISO, and other styles

50

Theotokis, Dimitrios. "A classificaton framework, evaluation and selection criteria and technological advances for Computer-Aided Software Engineering (CASE) tools." Thesis, Heriot-Watt University, 1992. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.335262.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Dissertations / Theses on the topic 'Software maintenance. Computer-aided software engineering'

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles