Result for Question 2.1

Responses Shown

Hide Responses

Go up to Question 2
Go to Question 2.2

2.1.

Source Code Repository

Mark cvs
Joseph cvs
Jacob cvs
William repository
Alvin CVS
Austin Source control system
Phil cvs
Brendan cvs
Luke CVS
Gabriel CVS or even RCS or some other version control tool
10 Responses

2.1.1.

Brief Description

  2.1.1.1. CVS (Concurrent Versions System)
Mark concurrent version system; client/server source control system
Joseph cvs
Jacob version control system
Alvin Concurrent Versioning System. Allows revision of a centralized copy of source code by many developers simultaneously.
Phil a tool to allow concurrent development of software
Brendan helps track changes to projects
Luke A code repository with support for versions
Gabriel Tools for version control and computer supportes cooperative work
8 Responses
  2.1.1.2. Client/server source control system
Mark concurrent version system; client/server source control system
  2.1.1.3. Maintains a centralised repository of current and previous versions of source code, documentation, etc.
William A versioning repository for the storage of code, documentation, websites, and other data that is of importance to the participants in
the project. Concrete example: CVS.
Alvin Concurrent Versioning System. Allows revision of a centralized copy of source code by many developers simultaneously.
Austin Maintains a repository of current and previous versions of source code, documentation, etc.
Brendan helps track changes to projects
Luke A code repository with support for versions
Gabriel Tools for version control and computer supportes cooperative work
6 Responses
  2.1.1.4. Allow concurrent development of software, support cooperative work by many developers
Alvin Concurrent Versioning System. Allows revision of a centralized copy of source code by many developers simultaneously.
Phil a tool to allow concurrent development of software
Gabriel Tools for version control and computer supportes cooperative work
3 Responses

2.1.2.

What are the important features of this tools?

  2.1.2.1. Complied to established standard, widely available and understood
Mark established standard, widely available and understood
  2.1.2.2. Client/server architecture, works over a network
Mark client/server, works over a network
  2.1.2.3. Permitting concurrent development without locking and the ability to handle conflicting updates
Mark permits concurrent development without locking
William Because of the geographically dispersed nature of participants, it
must be extremely good in handling conflicting updates.
Phil it allows multiple writers to update the software (independently of each other)
3 Responses
  2.1.2.4. Handling of branching of code
Joseph branching
Alvin Allows branching of code
Luke Branching of code base
3 Responses
  2.1.2.5. Tagging of various points in development
Luke Tagging of various points in development
  2.1.2.6. Version control
Joseph version
Phil it maintains the history of the software
Luke Version control
3 Responses
  2.1.2.7. Rollback
Luke Security and rollback features
  2.1.2.8. Allowing anonymous users read only access
William It should be usable both "through-the-web" as well have locally available clients. This allows a casual bypasser to peruse the repository and the active developer to have powertools that employ
a native user interface.
Alvin Ability to allow anonymous passwordless access to source repositories (read only)
  2.1.2.9. Security features, e.g. usernames and passwords protection, access via ssh encryption
William It should be usable both "through-the-web" as well have locally available clients. This allows a casual bypasser to peruse the repository and the active developer to have powertools that employ
a native user interface.
Alvin Ability to allow usernames and passwords for access
Alvin Can be set up to run with ssh encrypted.
Luke Security and rollback features
4 Responses
  2.1.2.10. Accessable both through WWW as well as a local client program
William It should be usable both "through-the-web" as well have locally available clients. This allows a casual bypasser to peruse the repository and the active developer to have powertools that employ
a native user interface.

2.1.3.

What are the important usability factors of this tools?

  2.1.3.1. Learnability - It is easy and intuitive to learn how to operate the site
Mark Learnability
  2.1.3.2. Memorability - It is easy to remember how to operate the site
Mark Memorability
  2.1.3.3. Simple and natural dialogue - Interaction between computer and users is as simple as possible and information in the interaction is presented in natural and logical fashion
Mark Simple and natural dialogue
Joseph Simple and natural dialogue
  2.1.3.4. Speak the users' language - During the interaction between computer and users, terms and concepts that are familiar to users are used rather than system-oriented terms
Mark Speak the users' language
  2.1.3.5. Connectivity - The connection to the site is fast
Jacob Connectivity
  2.1.3.6. Ease of Navigation - The information is in a structure that is easy to navigate
William Ease of Navigation
  2.1.3.7. Coherence - The information is presented logically and without contradiction
William Coherence
Gabriel Coherence
  2.1.3.8. Accuracy - The information processed and presented can be relied upon to be correct
William Accuracy
  2.1.3.9. Feedback - The site gives informative feedback to users within reasonable response time
William Feedback
  2.1.3.10. Collaboration - Enables distributed users to collaborate by easy synchronization of their work
Gabriel Collaboration
  2.1.3.11. Completeness - All relevant materials are presented
Phil Completeness
Gabriel Completeness
  2.1.3.12. Updated Frequently - The site is frequently updated with latest information
Gabriel Updated Frequently
  2.1.3.14. Prevent errors - The site is designed to prevent possible error like spelling mistake from users
Joseph Prevent errors
  2.1.3.15. Efficiency - The users can achieve a level of high productivity when using the site
Luke Efficiency

Hide Responses

Go up to Question 2
Go to Question 2.2

Go to Infrastructure For Hosting Open Source Project (IFHOSP) Delphi Survey
Generated On: 27 Sep 2002