Skip to main content
Article thumbnail
Location of Repository

An evaluation framework to drive future evolution of a research prototype

By David Nutter, Stephen Rank and Cornelia Boldyreff


The Open Source Component Artefact Repository (OSCAR) requires\ud evaluation to confirm its suitability as a development environment\ud for distributed software engineers. The evaluation will take note of\ud several factors including usability of OSCAR as a stand-alone system,\ud scalability and maintainability of the system and novel features not\ud provided by existing artefact management systems. Additionally, the\ud evaluation design attempts to address some of the omissions (due to\ud time constraints) from the industrial partner evaluations.\ud \ud This evaluation is intended to be a prelude to the evaluation of the\ud awareness support being added to OSCAR; thus establishing a baseline\ud to which the effects of awareness support may be compared

Topics: G400 Computer Science
Year: 2004
OAI identifier:

Suggested articles


  1. (2002). Active artefact management for distributed software engineering. doi
  2. (2002). Architectural requirements for an Open Source Component and Artefact Repository System within GENESIS.
  3. (2004). Communication and conflictissuesincollaborativesoftwareresearchprojects. doi
  4. (2002). Determination and evaluation of web accessibility. doi
  5. (1994). Encyclopaedia Of Software Engineering, chapter The Goal Question Metric Approach.
  6. (2002). Generalised enviroment for process management in cooperative software engineering. doi
  7. (2002). Generalised environment for process management in cooperative software engineering. doi
  8. (2003). Historical awareness support and its evaluation in collaborative software engineering. doi
  9. (2004). IST project fact sheet: GEneralized eNvironment for procEsS management in cooperatIve Software engineering.,
  10. (2000). Module size distribution and defect density. doi
  11. (2004). Open solution to managing distributed software developments.,
  12. (2003). Self-organizing maps applied in visualising large software collections.
  13. (2001). Software Engineering: A Practitioners Approach,
  14. (2004). Static analysis of students’ Java programs.
  15. (1999). The Goal/Question/Metric Method: A Practical Guide for Quality Improvement of Software Development. doi

To submit an update or takedown request for this paper, please submit an Update/Correction/Removal Request.