Entity usage

From MaRDI portal

This page lists pages that use the given entity (e.g. Q42). The list is sorted by descending page ID, so that newer pages are listed first.

List of pages that use a given entity

Showing below up to 45 results in range #1 to #45.

View (previous 50 | next 50) (20 | 50 | 100 | 250 | 500)

  1. Test processes in software product evolution—a qualitative survey on the state of practice: Label: en
  2. Tailoring the software maintenance process to better support complex systems evolution projects: Label: en
  3. Latitudinal and longitudinal process diversity: Label: en
  4. Process diversity: Label: en
  5. Evolving hypermedia systems: a layered software architecture: Label: en
  6. Relating functional requirements and software architecture: separation and consistency of concerns: Label: en
  7. Separating computation, coordination and configuration: Label: en
  8. Behavioural modelling of long‐lived evolution processes—some issues and an example: Label: en
  9. Change impact analysis to support architectural evolution: Label: en
  10. Consistent database sampling as a database prototyping approach: Label: en
  11. Identifying high maintenance legacy software: Label: en
  12. A model of factors affecting an information system's change in state: Label: en
  13. An approach for extracting code fragments that implement functionality from source programs: Label: en
  14. A concept-oriented belief revision approach to domain knowledge recovery from source code: Label: en
  15. Types of software evolution and software maintenance: Label: en
  16. Impact of experience on maintenance skills: Label: en
  17. Maintenance issues in the Web site development process: Label: en
  18. Experimental evaluation of hypertext access structures: Label: en
  19. Software Maintenance: Concepts and Practice: Label: en
  20. A case study in repeated maintenance: Label: en
  21. Case study: a maintenance practice used with real-time telecommunications software: Label: en
  22. MANTOOL: a tool for supporting the software maintenance process: Label: en
  23. An empirical study of the influence of departmentalization and organizational position on software maintenance: Label: en
  24. Field studies using functional size measurement in building estimation models for software maintenance: Label: en
  25. Piecemeal legacy migrating with an architectural pattern language: a case study: Label: en
  26. A semantic entropy metric: Label: en
  27. Graph-based tools for re-engineering: Label: en
  28. Automating the management of software maintenance workflows in a large software enterprise: a case study: Label: en
  29. Problem management maturity within corrective maintenance: Label: en
  30. Testing and maintaining de‐localized software systems in a multi‐site environment using Web‐based tools: Label: en
  31. Predicting project delivery rates using the Naive–Bayes classifier: Label: en
  32. Metrics for maintainability of class inheritance hierarchies: Label: en
  33. Policy analysis for warranty, maintenance, and upgrade of software systems: Label: en
  34. A decision framework for enterprise resource planning maintenance and upgrade: A client perspective: Label: en
  35. The maintenance implications of the customization of ERP software: Label: en
  36. Characteristics of ERP software maintenance: a multiple case study: Label: en
  37. Emergent maintenance of ERP: new roles and relationships: Label: en
  38. Modelling fault-proneness statistically over a sequence of releases: a case study: Label: en
  39. Evaluation of a scenario-based reading technique for analysing process components: Label: en
  40. An improved method of selecting regression tests for C++ programs: Label: en
  41. Inference of object-oriented design patterns: Label: en
  42. Ageing of a data-intensive legacy system: symptoms and remedies: Label: en
  43. A model of factors affecting an information system's change in state: Label: en
  44. Function-point analysis using design specifications based on the Unified Modelling Language: Label: en
  45. Computing ripple effect for software maintenance: Label: en

View (previous 50 | next 50) (20 | 50 | 100 | 250 | 500)