Artigos de revistas: "Maintenance software"

1

Parikh, Girish. "Software maintenance". ACM SIGSOFT Software Engineering Notes 10, n.º 5 (outubro de 1985): 89–98. http://dx.doi.org/10.1145/382288.382774.

Texto completo da fonte

Estilos ABNT, Harvard, Vancouver, APA, etc.

2

Leach, Ronald J. "Software metrics and software maintenance". Journal of Software Maintenance: Research and Practice 2, n.º 2 (junho de 1990): 133–42. http://dx.doi.org/10.1002/smr.4360020204.

Texto completo da fonte

Estilos ABNT, Harvard, Vancouver, APA, etc.

3

Parikh, G. "Software maintenance notes". ACM SIGSOFT Software Engineering Notes 12, n.º 2 (abril de 1987): 51–53. http://dx.doi.org/10.1145/24562.24571.

Texto completo da fonte

Estilos ABNT, Harvard, Vancouver, APA, etc.

4

Parikh, Girish. "Software maintenance news". ACM SIGSOFT Software Engineering Notes 10, n.º 2 (abril de 1985): 58–59. http://dx.doi.org/10.1145/1012621.1012632.

Texto completo da fonte

Estilos ABNT, Harvard, Vancouver, APA, etc.

5

Herrin, William R. "Software maintenance costs". ACM SIGCSE Bulletin 17, n.º 1 (março de 1985): 233–37. http://dx.doi.org/10.1145/323275.323383.

Texto completo da fonte

Estilos ABNT, Harvard, Vancouver, APA, etc.

6

Seaman, Carolyn B. "Practical Software Maintenance". Journal of Software Maintenance: Research and Practice 12, n.º 4 (2000): 249–53. http://dx.doi.org/10.1002/1096-908x(200007/08)12:4<249::aid-smr213>3.0.co;2-n.

Texto completo da fonte

Estilos ABNT, Harvard, Vancouver, APA, etc.

7

April, Alain, Jane Huffman Hayes, Alain Abran e Reiner Dumke. "Software Maintenance Maturity Model (SMmm): the software maintenance process model". Journal of Software Maintenance and Evolution: Research and Practice 17, n.º 3 (2005): 197–223. http://dx.doi.org/10.1002/smr.311.

Texto completo da fonte

Estilos ABNT, Harvard, Vancouver, APA, etc.

8

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

Texto completo da fonte

Resumo:

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.

Estilos ABNT, Harvard, Vancouver, APA, etc.

9

Stojanov, Zeljko. "SOFTWARE MAINTENANCE MANAGEMENT IN MICRO SOFTWARE COMPANIES". Southeast European Review of Business and Economics 3, n.º 1 (junho de 2022): 75–92. http://dx.doi.org/10.20544/serbe.05.01.22.p05.

Texto completo da fonte

Resumo:

Software maintenance is one of the main processes in software companies. It is regarded as more complex and costly compared to software development, and therefore should be carefully planned and managed. Micro software companies are companies with up to 10 employees, and they represent a significant driver of economic development in many countries around the world. However, micro companies have specific internal organizations and a business model, but also have significant constraints on human and financial resources. After outlining the basic concepts of software maintenance and the characteristics of small and micro software companies, the paper presents the author’s experience in software maintenance management in a local micro software company in Serbia. Maintenance management was implemented through a project aimed at improving maintenance processes in the company. The main objective was the improvement of maintenance request processing, which resulted in the implementation of a technical solution related to the timeline of maintenance requests. Since the process improvement project fosters organizational learning and knowledge management activities, a knowledge identification and systematization project was implemented as a subproject. Presented experience gained through fieldwork in the company contributed to the overall knowledge base about software engineering practice in micro software companies, which can be beneficial to both researchers from academia and practitioners from industry.

Estilos ABNT, Harvard, Vancouver, APA, etc.

10

Bhatt, Pankaj, Gautam Shroff e Arun K. Misra. "Dynamics of software maintenance". ACM SIGSOFT Software Engineering Notes 29, n.º 5 (setembro de 2004): 1–5. http://dx.doi.org/10.1145/1022494.1022513.

Texto completo da fonte

Estilos ABNT, Harvard, Vancouver, APA, etc.

11

Bendifallah, S. "Understanding Software Maintenance Work". IEEE Transactions on Software Engineering SE-13, n.º 3 (março de 1987): 311–23. http://dx.doi.org/10.1109/tse.1987.233162.

Texto completo da fonte

Estilos ABNT, Harvard, Vancouver, APA, etc.

12

Burch, John G., e Fritz H. Grupe. "IMPROVED SOFTWARE MAINTENANCE MANAGEMENT". Information Systems Management 10, n.º 1 (janeiro de 1993): 24–32. http://dx.doi.org/10.1080/10580539308906909.

Texto completo da fonte

Estilos ABNT, Harvard, Vancouver, APA, etc.

13

Taylor, Mark, Eddie Moynihan e Trevor Wood-Harper. "Knowledge for software maintenance". Journal of Information Technology 12, n.º 2 (junho de 1997): 155–66. http://dx.doi.org/10.1080/026839697345161.

Texto completo da fonte

Estilos ABNT, Harvard, Vancouver, APA, etc.

14

Sneed, H., e S. Huang. "Value-Driven Software Maintenance". International Journal of Computers and Applications 32, n.º 2 (janeiro de 2010): 215–21. http://dx.doi.org/10.1080/1206212x.2010.11441977.

Texto completo da fonte

Estilos ABNT, Harvard, Vancouver, APA, etc.

15

&NA;. "Master Maintenance Management Software". Journal of Clinical Engineering 20, n.º 6 (novembro de 1995): 450–56. http://dx.doi.org/10.1097/00004669-199511000-00007.

Texto completo da fonte

Estilos ABNT, Harvard, Vancouver, APA, etc.

16

Briggs, JS. "Handbook of software maintenance". Data Processing 28, n.º 8 (outubro de 1986): 442. http://dx.doi.org/10.1016/0011-684x(86)90435-1.

Texto completo da fonte

Estilos ABNT, Harvard, Vancouver, APA, etc.

17

Taylor, Mark, Eddie Moynihan e Trevor Wood-Harper. "Knowledge for Software Maintenance". Journal of Information Technology 12, n.º 2 (junho de 1997): 155–66. http://dx.doi.org/10.1177/026839629701200207.

Texto completo da fonte

Resumo:

Studies have shown that maintenance is up to 80% of the life-cycle effort of developing and maintaining a business information technology (IT) system. There are several factors which significantly affect maintenance work. This paper concentrates on one of these factors which is the knowledge staff require for effective and efficient systems maintenance. The knowledge required is split into two categories. Firstly, there is the knowledge of the business environment within which an IT system operates. Secondly, there is the knowledge of the technical IT system, particularly the details of the software structure. It is argued that both categories of knowledge are equally important and difficult to acquire. Examples of techniques for improving this knowledge are discussed. The article is partly based on case-study research into the actual practice of systems development and maintenance in 31 UK IT departments.

Estilos ABNT, Harvard, Vancouver, APA, etc.

18

KUMAR, M. PAVAN, V. SITA RAMA DAS e N. NETAJI. "Offshore Software Maintenance Methodology". Journal of Software Maintenance: Research and Practice 8, n.º 3 (maio de 1996): 179–97. http://dx.doi.org/10.1002/(sici)1096-908x(199605)8:3<179::aid-smr128>3.0.co;2-s.

Texto completo da fonte

Estilos ABNT, Harvard, Vancouver, APA, etc.

19

TAYLOR, M. J., e A. T. WOOD-HARPER. "Methodologies and Software Maintenance". Journal of Software Maintenance: Research and Practice 8, n.º 5 (setembro de 1996): 295–307. http://dx.doi.org/10.1002/(sici)1096-908x(199609)8:5<295::aid-smr138>3.0.co;2-g.

Texto completo da fonte

Estilos ABNT, Harvard, Vancouver, APA, etc.

20

Taylor, M. J., E. P. Moynihan e A. Laws. "Training for software maintenance". Journal of Software Maintenance: Research and Practice 10, n.º 6 (novembro de 1998): 381–93. http://dx.doi.org/10.1002/(sici)1096-908x(199811/12)10:6<381::aid-smr177>3.0.co;2-n.

Texto completo da fonte

Estilos ABNT, Harvard, Vancouver, APA, etc.

21

Dekleva, Sasa M. "Software Maintenance: 1990 status". Journal of Software Maintenance: Research and Practice 4, n.º 4 (dezembro de 1992): 233–47. http://dx.doi.org/10.1002/smr.4360040406.

Texto completo da fonte

Estilos ABNT, Harvard, Vancouver, APA, etc.

22

Fawareh, Hamed. "Software Quality Model for Maintenance Software Purposes". International Journal of Engineering Research and Technology 13, n.º 1 (30 de janeiro de 2020): 158. http://dx.doi.org/10.37624/ijert/13.1.2020.158-162.

Texto completo da fonte

Estilos ABNT, Harvard, Vancouver, APA, etc.

23

Chapin, Ned, Joanne E. Hale, Khaled Md Khan, Juan F. Ramil e Wui-Gee Tan. "Types of software evolution and software maintenance". Journal of Software Maintenance and Evolution: Research and Practice 13, n.º 1 (janeiro de 2001): 3–30. http://dx.doi.org/10.1002/smr.220.

Texto completo da fonte

Estilos ABNT, Harvard, Vancouver, APA, etc.

24

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

Texto completo da fonte

Estilos ABNT, Harvard, Vancouver, APA, etc.

25

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

Texto completo da fonte

Resumo:

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.

Estilos ABNT, Harvard, Vancouver, APA, etc.

26

Carver, Jeffrey C., e Alexander Serebrenik. "Software Maintenance and Evolution and Automated Software Engineering". IEEE Software 35, n.º 2 (março de 2018): 102–4. http://dx.doi.org/10.1109/ms.2018.1661318.

Texto completo da fonte

Estilos ABNT, Harvard, Vancouver, APA, etc.

27

L. Glass, Robert. "Software maintenance, Y2K and other software non-crises". Journal of Systems and Software 54, n.º 2 (outubro de 2000): 83–85. http://dx.doi.org/10.1016/s0164-1212(00)00028-5.

Texto completo da fonte

Estilos ABNT, Harvard, Vancouver, APA, etc.

28

Souza, Sergio Cozzetti B. de, Nicolas Anquetil e Káthia M. de Oliveira. "Which documentation for software maintenance?" Journal of the Brazilian Computer Society 12, n.º 3 (dezembro de 2006): 31–44. http://dx.doi.org/10.1590/s0104-65002006000400004.

Texto completo da fonte

Estilos ABNT, Harvard, Vancouver, APA, etc.

29

Alija, Nexhati. "Justification of Software Maintenance Costs". International Journal of Advanced Research in Computer Science and Software Engineering 7, n.º 3 (30 de março de 2017): 15–23. http://dx.doi.org/10.23956/ijarcsse/v7i2/01207.

Texto completo da fonte

Estilos ABNT, Harvard, Vancouver, APA, etc.

30

Valentino, Daniela. "Software Assistance and Maintenance Contracts". European Business Law Review 27, Issue 4 (1 de agosto de 2016): 535–53. http://dx.doi.org/10.54648/eulr2016024.

Texto completo da fonte

Resumo:

The paper analyzes the legal issues related to software assistance and maintenance agreements. Contracts generally provide for highly diverse performances and are aimed at providing a global service. Since the assistance and maintenance agreement generally entails a long-term relationship, the regulations for long-term supply contract’s apply. Nevertheless, in specific circumstances, even the rules for service contracts may be applied. In Italy, like in other EU jurisdictions, the applicable regulatory framework depends on the content of the contract. The provider company naturally tends to restrict its liability in proportion to effectively commissioned activity. Exclusion clauses including intentional damage or gross negligence are void, while par. 2 of Article 1229 of the Italian Civil Code permits limitation of liability in cases of minor negligence. The impossibility of changing contractual terms disadvantages the weaker contracting party and the procedure imposed by par 2 of Art. 1341 c.c. has proved inadequate to protect the customer. Art. 9, of Law n 192 of 18 June 1998 (“Disciplina della subfornitura nelle attivita produttive”), which is now considered to be general principle allows exclusion clauses providing for minor negligence to be deemed void, if they oversimplify the debtor position, by defining the requirements of minor negligence. In addition, clauses regarding exclusion or limitation of liability towards third parties, beyond the limit set by Art. 1229, require an assessment based on the nature of the interest which is concretely protected.

Estilos ABNT, Harvard, Vancouver, APA, etc.

31

V, SUJAY, e REDDY M. BABU. "ADVANCED ARCHITECTURE-CENTRIC SOFTWARE MAINTENANCE". i-manager’s Journal on Software Engineering 12, n.º 1 (2017): 1. http://dx.doi.org/10.26634/jse.12.1.13917.

Texto completo da fonte

Estilos ABNT, Harvard, Vancouver, APA, etc.

32

Schneidewind, N. F. "The State of Software Maintenance". IEEE Transactions on Software Engineering SE-13, n.º 3 (março de 1987): 303–10. http://dx.doi.org/10.1109/tse.1987.233161.

Texto completo da fonte

Estilos ABNT, Harvard, Vancouver, APA, etc.

33

Reiss, S. P. "Incremental Maintenance of Software Artifacts". IEEE Transactions on Software Engineering 32, n.º 9 (setembro de 2006): 682–97. http://dx.doi.org/10.1109/tse.2006.91.

Texto completo da fonte

Estilos ABNT, Harvard, Vancouver, APA, etc.

34

Glass, Robert L. "A Study About Software Maintenance". Information Systems Management 29, n.º 4 (setembro de 2012): 338–39. http://dx.doi.org/10.1080/10580530.2012.716997.

Texto completo da fonte

Estilos ABNT, Harvard, Vancouver, APA, etc.

35

Banker, Rajiv D., Srikant M. Datar, Chris F. Kemerer e Dani Zweig. "Software complexity and maintenance costs". Communications of the ACM 36, n.º 11 (novembro de 1993): 81–94. http://dx.doi.org/10.1145/163359.163375.

Texto completo da fonte

Estilos ABNT, Harvard, Vancouver, APA, etc.

36

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

Texto completo da fonte

Estilos ABNT, Harvard, Vancouver, APA, etc.

37

Pruijm, R. A. M. "The Audit of Software Maintenance". EDPACS 14, n.º 2 (agosto de 1986): 1–5. http://dx.doi.org/10.1080/07366988609450361.

Texto completo da fonte

Estilos ABNT, Harvard, Vancouver, APA, etc.

38

Arnold, R. S., e R. J. Martin. "Software Maintenance Guest Editors' Introduction". IEEE Software 3, n.º 3 (maio de 1986): 4–5. http://dx.doi.org/10.1109/ms.1986.233403.

Texto completo da fonte

Estilos ABNT, Harvard, Vancouver, APA, etc.

39

Arango, G., I. Baxter, P. Freeman e C. Pidgeon. "TMM: Software Maintenance by Transformation". IEEE Software 3, n.º 3 (maio de 1986): 27–39. http://dx.doi.org/10.1109/ms.1986.233411.

Texto completo da fonte

Estilos ABNT, Harvard, Vancouver, APA, etc.

40

Grady, R. B. "Measuring and Managing Software Maintenance". IEEE Software 4, n.º 5 (setembro de 1987): 35–45. http://dx.doi.org/10.1109/ms.1987.231417.

Texto completo da fonte

Estilos ABNT, Harvard, Vancouver, APA, etc.

41

Collofello, J. S., e J. J. Buck. "Software Quality Assurance for Maintenance". IEEE Software 4, n.º 5 (setembro de 1987): 46–51. http://dx.doi.org/10.1109/ms.1987.231418.

Texto completo da fonte

Estilos ABNT, Harvard, Vancouver, APA, etc.

42

Charette, R. N., K. M. Adams e M. B. White. "Managing risk in software maintenance". IEEE Software 14, n.º 3 (1997): 43–50. http://dx.doi.org/10.1109/52.589232.

Texto completo da fonte

Estilos ABNT, Harvard, Vancouver, APA, etc.

43

Nighswonger, Gregg. "HEMS Hospital Equipment Maintenance Software". Journal of Clinical Engineering 19, n.º 3 (maio de 1994): 172. http://dx.doi.org/10.1097/00004669-199405000-00005.

Texto completo da fonte

Estilos ABNT, Harvard, Vancouver, APA, etc.

44

McClure, Carma L. "Managing Software Development and Maintenance". IEEE Transactions on Reliability 35, n.º 4 (1986): 398. http://dx.doi.org/10.1109/tr.1986.4335482.

Texto completo da fonte

Estilos ABNT, Harvard, Vancouver, APA, etc.

45

López, Cristina, e Jose L. Salmeron. "Monitoring Software Maintenance Project Risks". Procedia Technology 5 (2012): 363–68. http://dx.doi.org/10.1016/j.protcy.2012.09.040.

Texto completo da fonte

Estilos ABNT, Harvard, Vancouver, APA, etc.

46

Glass, Robert L. "The “maintenance-first” software era". Journal of Systems and Software 50, n.º 3 (março de 2000): 171–74. http://dx.doi.org/10.1016/s0164-1212(99)00095-3.

Texto completo da fonte

Estilos ABNT, Harvard, Vancouver, APA, etc.

47

de Souza, Sergio Cozzetti B., Nicolas Anquetil e Káthia M. de Oliveira. "Which documentation for software maintenance?" Journal of the Brazilian Computer Society 12, n.º 3 (outubro de 2006): 31–44. http://dx.doi.org/10.1007/bf03194494.

Texto completo da fonte

Estilos ABNT, Harvard, Vancouver, APA, etc.

48

Osborne, W. M., e R. Raigrodski. "Annotated bibliography on software maintenance". Computers & Security 7, n.º 5 (outubro de 1988): 516. http://dx.doi.org/10.1016/0167-4048(88)90248-9.

Texto completo da fonte

Estilos ABNT, Harvard, Vancouver, APA, etc.

49

Ketler, K., e E. Turban. "Productivity improvements in software maintenance". International Journal of Information Management 12, n.º 1 (março de 1992): 70–82. http://dx.doi.org/10.1016/0268-4012(92)90053-s.

Texto completo da fonte

Estilos ABNT, Harvard, Vancouver, APA, etc.

50

Euteneuer, Sven, Daniel Draws, Daniel Simon e Barbara Kolany. "Legal Aspects in Software Maintenance". Softwaretechnik-Trends 33, n.º 2 (maio de 2013): 33–34. http://dx.doi.org/10.1007/s40568-013-0035-z.

Texto completo da fonte

Estilos ABNT, Harvard, Vancouver, APA, etc.

Artigos de revistas sobre o tema "Maintenance software"

Crie uma referência precisa em APA, MLA, Chicago, Harvard, e outros estilos