Relevant bibliographies by topics / Software maintenance. Computer-aided software engineering

Contents

  1. Journal articles
  2. Dissertations / Theses
  3. Books
  4. Book chapters
  5. Conference papers
  6. Reports

Academic literature on the topic 'Software maintenance. Computer-aided software engineering'

Author: Grafiati
Published: 4 June 2021
Last updated: 3 February 2022

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

Select a source type:

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources on the topic 'Software maintenance. Computer-aided software engineering.'

Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.

You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.

Journal articles on the topic "Software maintenance. Computer-aided software engineering"

1

Kwon, Oh Cheon, Cornelia Boldyreff, and Malcolm Munro. "Software Configuration Management for a Reusable Software Library within a Software Maintenance Environment." International Journal of Software Engineering and Knowledge Engineering 08, no. 04 (December 1998): 483–515. http://dx.doi.org/10.1142/s0218194098000273.

Full text
Abstract:
Software Configuration Management and software reuse are now generally considered to be important technologies in software engineering. Both have been proposed for making a significant improvement in productivity and quality. However, these two technologies have been investigated separately. In order to make Software Configuration Management and reuse more effective, both approaches require to be introduced into a development or maintenance environment together. The authors have developed a process model for Maintenance with Reuse (MwR) to support Software Configuration Management for a reuse library within a maintenance environment. As software reuse and Software Configuration Management as well as software reuse and software maintenance have many similarities in their activities, and these areas can therefore be integrated within a software maintenance environment. An integrated approach to the common areas of these different activities will greatly contribute to the productivity and quality of software. This paper will address an integrated approach that can overcome some of the barriers that exist in software maintenance and reuse. A process model of an integrated approach has been created and validated using Process Weaver. In order for the reuse library to allow accesses from many potential reusers, the process model has been implemented on the WWW. The paper describes an integrated process model and its prototype to support change and version control for evolution of software components within both a reuse library and a legacy system.
APA, Harvard, Vancouver, ISO, and other styles
2

BERZTISS, ALFS T. "REVERSE ENGINEERING, REENGINEERING, AND CONCURRENT ENGINEERING OF SOFTWARE." International Journal of Software Engineering and Knowledge Engineering 05, no. 02 (June 1995): 299–324. http://dx.doi.org/10.1142/s0218194095000150.

Full text
Abstract:
This survey reviews four classes of reengineering of software systems: code restructuring and translation of code into a new language, design recovery for corrective maintenance, design recovery for software enhancement, and software reengineering as part of radical business process reengineering. Special attention is given to the reengineering of data bases and user interfaces. We also consider concurrent software engineering, its place in the software reengineering process, and groupware in support of this process.
APA, Harvard, Vancouver, ISO, and other styles
3

Wee, Nam-Sook. "Optimal Maintenance Schedules of Computer Software." Probability in the Engineering and Informational Sciences 4, no. 2 (April 1990): 243–55. http://dx.doi.org/10.1017/s026996480000156x.

Full text
Abstract:
We present a decision procedure to determine the optimal maintenance intervals of a computer software throughout its operational phase. Our model accounts for the average cost per each maintenance activity and the damage cost per failure with the future cost discounted. Our decision policy is optimal in the sense that it minimizes the expected total cost. Our model assumes that the total number of errors in the software has a Poisson distribution with known mean λ and each error causes failures independently of other errors at a known constant failure rate. We study the structures of the optimal policy in terms of λ and present efficient numerical algorithms to compute the optimal maintenance time intervals, the optimal total number of maintenances, and the minimal total expected cost throughout the maintenance phase.
APA, Harvard, Vancouver, ISO, and other styles
4

KAJKO-MATTSSON, MIRA, and NED CHAPIN. "DATA MINING FOR VALIDATION IN SOFTWARE ENGINEERING: AN EXAMPLE." International Journal of Software Engineering and Knowledge Engineering 14, no. 04 (August 2004): 407–27. http://dx.doi.org/10.1142/s0218194004001725.

Full text
Abstract:
Consider two independently done software engineering studies that used different approaches to cover some of the same subject area, such as software maintenance. Although done differently and for different purposes, to what extent can each study serve as a validation of the other? Within the scope of the subject area overlap, data mining can be applied to provide a quantitative assessment. This paper reports on the data mining that attempted to cross validate two independently done and published software engineering studies of software maintenance, one on a corrective maintenance maturity model, and the other on an objective classification of software maintenance activities. The data mining established that each of the two independently done studies effectively and very strongly validates the other.
APA, Harvard, Vancouver, ISO, and other styles
5

Rine, David. "Software perfective maintenance: Including retrainable software in software reuse." Information Sciences 75, no. 1-2 (December 1993): 109–32. http://dx.doi.org/10.1016/0020-0255(93)90116-4.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Boston, R. C., H. Granek, N. Sutton, K. Weber, P. Greif, and L. Zech. "The maintenance, distribution and development of biomedical computer software: an exercise in software engineering." Computer Methods and Programs in Biomedicine 22, no. 3 (June 1986): 305–21. http://dx.doi.org/10.1016/0169-2607(86)90007-6.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

GANNOD, GERALD C., and BETTY H. C. CHENG. "FACILITATING THE MAINTENANCE OF SAFETY-CRITICAL SYSTEMS." International Journal of Software Engineering and Knowledge Engineering 04, no. 02 (June 1994): 183–204. http://dx.doi.org/10.1142/s0218194094000106.

Full text
Abstract:
As software is increasingly used to control safety-critical systems, correctness becomes paramount. Formal methods in software development provide many benefits in the forward engineering aspect of software development. Reverse engineering is the process of constructing a high-level representation of a system from existing lower level instanti-ations of that system. Reverse engineering of program code into formal specifications facilitates the utilization of the benefits of formal methods in projects where formal methods may not have previously been used, thus facilitating the maintenance of safety-critical systems.
APA, Harvard, Vancouver, ISO, and other styles
8

Chandra, C., and C. V. Ramamoorthy. "An Evaluation of Knowledge Engineering Approaches to the Maintenance of Evolutionary Software." International Journal of Software Engineering and Knowledge Engineering 08, no. 01 (March 1998): 3–20. http://dx.doi.org/10.1142/s0218194098000030.

Full text
Abstract:
Reverse engineering and reengineering are two major research challenges in the software maintenance process. Reverse engineering is the process of rederiving the specification of a program; and reengineering is the process of modifying an already existing software to add additional functionalities or to correct any malfunction. The difficulty in these tasks are that software development commonly involves many software engineers with implicit assumptions about the behavior of each module. These assumptions are not documented and often leads to inconsistencies in the code. During reverse engineering, such assumptions may not be uncovered. These assumptions usually have complex dependencies, and are the cause of a lot of bugs when the software is reengineered. Many approaches and prototype tools have been developed to address these issues. Reverse engineering and automated program understanding tools have been developed to support the reverse engineering tasks; while various theoretical works on structural program analysis and programs for automated ripple effect analysis have attempted to deal with the reengineering process. These works can be classified into two main types of approaches: those using shallow knowledge or knowledge about the structure of the system and those utilizing deep knowledge or knowledge about the semantics and behavior of the software system. In this paper, we attempt to survey works that have been done under these two broad categories of approaches to deal with the software maintenance tasks, evaluate the strengths and drawbacks of each approach, and attempt to draw a conclusion on the advantages and disadvantages of the two main lines of approaches.
APA, Harvard, Vancouver, ISO, and other styles
9

CANFORA, GERARDO, FILIPPO LANUBILE, and GIUSEPPE VISAGGIO. "IESEM: INTEGRATED ENVIRONMENT FOR SOFTWARE EVOLUTION MANAGEMENT." International Journal of Software Engineering and Knowledge Engineering 05, no. 01 (March 1995): 49–71. http://dx.doi.org/10.1142/s0218194095000046.

Full text
Abstract:
Software evolution has no common paradigm which practitioners can adhere to. On the contrary, there is a wide range of models, methods, techniques, and tools which are selected according to the specific task, the application domain, the professional experience, and the organizational culture. We argue that different approaches and technologies may be combined into a unique platform to satisfy the needs of software systems which evolve over long periods of time. This paper presents the Integrated Environment for Software Evolution Management (IESEM) which includes software repositories, reverse engineering tools, rationale capture tools, software measurement tools, and a user-friendly interface. It can manage heterogeneous systems characterized by various design methods and programming languages. IESEM is based on a central repository which stores software engineering artifacts, program code, design, and implementation decisions in the form of a traceability graph. The repository stores also software measures computed both from programs and external CASE repositories. Measures are used to control software degradation during its evolution and to support decisions based on quality factors. The key concepts of IESEM, its design, and implementation are presented. The use of IESEM during development and maintenance is discussed. A case study shows IESEM's effectiveness in performing maintenance tasks.
APA, Harvard, Vancouver, ISO, and other styles
10

Mellor, P. "Field monitoring of software maintenance." Software Engineering Journal 1, no. 1 (1986): 43. http://dx.doi.org/10.1049/sej.1986.0008.

Full text
APA, Harvard, Vancouver, ISO, and other styles
More sources

Dissertations / Theses on the topic "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
More sources

Books on the topic "Software maintenance. Computer-aided software engineering"

1

CASE: Computer-aided software engineering. New York: Van Nostrand Reinhold, 1991.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
2

Software engineering and management. Englewood Cliffs, N.J: Prentice Hall, 1988.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
3

Software engineering concepts. New York: McGraw-Hill, 1985.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
4

Wallace, Dolores R. Study of a prototype software engineering environment. Gaithersburg, MD: U.S. Dept. of Commerce, National Bureau of Standards, 1986.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
5

Wallace, Dolores R. Study of a prototype software engineering environment. Gaithersburg, MD: U.S. Dept. of Commerce, National Bureau of Standards, 1986.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
6

Wright, David. Software maintenance in scientific & engineering environments: An introduction & guide. Moffett Field, Calif: National Aeronautics and Space Administration, Ames Research Center, 1988.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
7

Einbu, John. A program architecture for improved maintainability in software engineering. Chichester, England: Ellis Horwood, 1989.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
8

Corporate accounting systems: A software engineering approach. Wokingham, England: Addison-Wesley, 1988.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
9

Kenneth, Smith. Corporate accounting systems: A software engineering approach. Wokingham: Addison-Wesley, 1988.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
10

Naono, Ken. Software Automatic Tuning: From Concepts to State-of-the-Art Results. New York, NY: Springer Science+Business Media LLC, 2010.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
More sources

Book chapters on the topic "Software maintenance. Computer-aided software engineering"

1

Cross, P. "Cost effective computer software in maintenance management." In Condition Monitoring and Diagnostic Engineering Management, 162–68. Dordrecht: Springer Netherlands, 1990. http://dx.doi.org/10.1007/978-94-009-0431-6_26.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Kavitha, D., and Ananthi Sheshasaayee. "Requirements Volatility in Software Maintenance." In Lecture Notes of the Institute for Computer Sciences, Social Informatics and Telecommunications Engineering, 142–50. Berlin, Heidelberg: Springer Berlin Heidelberg, 2012. http://dx.doi.org/10.1007/978-3-642-27317-9_15.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Jamain, N. S., and Z. M. Kasirun. "Potential of Using Virtual Environment for Aircraft Maintenance Learning System in Making Tacit Knowledge Explicit." In Software Engineering and Computer Systems, 506–16. Berlin, Heidelberg: Springer Berlin Heidelberg, 2011. http://dx.doi.org/10.1007/978-3-642-22170-5_43.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Lee, Young, Jeong Yang, and Kai H. Chang. "Identifying Connected Classes for Software Reuse and Maintenance." In Innovations and Advances in Computer Sciences and Engineering, 389–93. Dordrecht: Springer Netherlands, 2009. http://dx.doi.org/10.1007/978-90-481-3658-2_68.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Shiran, Yehuda. "The Single Array Approach to Engineering and Maintenance of CAD Software." In Advanced Computer Graphics, 306–17. Tokyo: Springer Japan, 1986. http://dx.doi.org/10.1007/978-4-431-68036-9_21.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Sarang, Nita, and Mukund A. Sanglikar. "An Analysis of Effort Variance in Software Maintenance Projects." In Advances in Computer and Information Sciences and Engineering, 366–71. Dordrecht: Springer Netherlands, 2008. http://dx.doi.org/10.1007/978-1-4020-8741-7_66.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Qiu, Gang, and Shi-han Zhang. "Research on Data Optimization Method of Software Knowledge Base Operation and Maintenance Based on Cloud Computing." In Lecture Notes of the Institute for Computer Sciences, Social Informatics and Telecommunications Engineering, 229–38. Cham: Springer International Publishing, 2021. http://dx.doi.org/10.1007/978-3-030-67871-5_21.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Weik, Martin H. "aided software engineering." In Computer Science and Communications Dictionary, 34. Boston, MA: Springer US, 2000. http://dx.doi.org/10.1007/1-4020-0613-6_437.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Saleh, H. Sardar Amin. "Computer Aided Design of Shell Structures." In Engineering Software IV, 535–47. Berlin, Heidelberg: Springer Berlin Heidelberg, 1985. http://dx.doi.org/10.1007/978-3-662-21877-8_41.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Müller, Hausi A., Ronald J. Norman, and Jacob Slonim. "CASE: The Coming of Age for Automated Software Development." In Computer Aided Software Engineering, 5–7. Boston, MA: Springer US, 1996. http://dx.doi.org/10.1007/978-1-4613-1439-4_1.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Conference papers on the topic "Software maintenance. Computer-aided software engineering"

1

Wang, Xiaowei. "The Metric System about Software Maintenance." In 2011 International Conference on Information Technology, Computer Engineering and Management Sciences (ICM). IEEE, 2011. http://dx.doi.org/10.1109/icm.2011.382.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Robillard, Pierre N., Noureddine Kerzazi, Martin Tapp, and Hamid Hmima. "Outsourcing Software Maintenance: Processes, Standards & Critical Practices." In 2007 Canadian Conference on Electrical and Computer Engineering. IEEE, 2007. http://dx.doi.org/10.1109/ccece.2007.175.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Xing, Jixin. "Study on the Maintenance and Management Technology of Computer Software." In 4th International Conference on Computer, Mechatronics, Control and Electronic Engineering. Paris, France: Atlantis Press, 2015. http://dx.doi.org/10.2991/iccmcee-15.2015.7.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Dong, Jong Sung, Keun Lee, Kyong Hwan Kim, Sang Tae Kim, Ji Man Cho, and Te Hi Kim. "Platform Maintenance Process for Software Quality Assurance in Product Line." In 2008 International Conference on Computer Science and Software Engineering. IEEE, 2008. http://dx.doi.org/10.1109/csse.2008.1520.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Song, Huan-Huan, and Zhi-Xiang Zhang. "Study on Approach of Software Maintenance Based on Ontology Evolution." In 2008 International Conference on Computer Science and Software Engineering. IEEE, 2008. http://dx.doi.org/10.1109/csse.2008.267.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Benbelkacem, S., N. Zenati-Henda, M. Belhocine, A. Bellarbi, and M. Tadjine. "HCI Knowledge in Software Engineering Practices for Designing Interactive Maintenance Assistance Systems." In 2012 IEEE 36th Annual Computer Software and Applications Conference - COMPSAC 2012. IEEE, 2012. http://dx.doi.org/10.1109/compsac.2012.56.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Wang, Tianren, Yue Liu, and Yongtian Wang. "Infrared Marker Based Augmented Reality System for Equipment Maintenance." In 2008 International Conference on Computer Science and Software Engineering. IEEE, 2008. http://dx.doi.org/10.1109/csse.2008.8.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Stack, Paul. "Development of a Mobile Platform to Support Building Maintenance Engineering." In 2012 IEEE 36th IEEE Annual Computer Software and Applications Conference Workshops (COMPSACW). IEEE, 2012. http://dx.doi.org/10.1109/compsacw.2012.91.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Shukla, R., and A. K. Misra. "AI Based Framework for Dynamic Modeling of Software Maintenance Effort Estimation." In 2009 International Conference on Computer and Automation Engineering. ICCAE 2009. IEEE, 2009. http://dx.doi.org/10.1109/iccae.2009.47.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Munandar, Devi, and Djohar Syamsi. "Data logger management software design for maintenance and utility in remote." In 2014 1st International Conference on Information Technology, Computer and Electrical Engineering (ICITACEE). IEEE, 2014. http://dx.doi.org/10.1109/icitacee.2014.7065717.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Reports on the topic "Software maintenance. Computer-aided software engineering"

1

Humphrey, Watts S. CASE (Computer-Aided Software Engineering) Planning and the Software Process. Fort Belvoir, VA: Defense Technical Information Center, May 1989. http://dx.doi.org/10.21236/ada219066.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Dampier, David A., Ronald B. Byrnes, and Mark R. Kindl. Computer-Aided Maintenance for Embedded Real-time Software. Fort Belvoir, VA: Defense Technical Information Center, August 1995. http://dx.doi.org/10.21236/ada299314.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Woyna, M. A., and C. R. Carlson. Evaluation of computer-aided software engineering tools for data base development. Office of Scientific and Technical Information (OSTI), February 1989. http://dx.doi.org/10.2172/5698662.

Full text
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'Software maintenance. Computer-aided software engineering' for particular source types:
Journal articles Dissertations / Theses Books
We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!

To the bibliography