Result for Question 2.1

Show All Relevant Data (Sort by Rating)

Show Only Top Ten
Show Only Numerical Data
Show All Relevant Data (Sort by Controversy)

Go up to Question 2
Go to Question 2.2

2.1.

Source Code Repository

Average
Totally
Irrelevant
Extremely
Relevant
No. of
Votes

2.1.1 Brief Description
2.1.1.1 CVS (Concurrent Versions System)
No Votes
0
Details
Answer from Previous Round
This sub-question is summarised from the following answer(s) from round 1
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
Relevant Glossary
Concurrent Versions System
No Votes
0
2.1.1.2 Client/server source control system
No Votes
0
Details
Answer from Previous Round
This sub-question is summarised from the following answer(s) from round 1
Mark concurrent version system; client/server source control system
No Votes
0
2.1.1.3 Maintains a centralised repository of current and previous versions of source code, documentation, etc.
No Votes
0
Details
Answer from Previous Round
This sub-question is summarised from the following answer(s) from round 1
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
Relevant Glossary
Concurrent Versions System
No Votes
0
2.1.1.4 Allow concurrent development of software, support cooperative work by many developers
No Votes
0
Details
Answer from Previous Round
This sub-question is summarised from the following answer(s) from round 1
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
Relevant Glossary
Concurrent Versions System
No Votes
0

2.1.2 What are the important features of this tools?
2.1.2.6 Version control
1.3  
6
Details
Answer from Previous Round
This sub-question is summarised from the following answer(s) from round 1
Joseph version
Phil it maintains the history of the software
Luke Version control
3 Responses
No Votes
0
2.1.2.2 Client/server architecture, works over a network
1.5  
6
Details
Answer from Previous Round
This sub-question is summarised from the following answer(s) from round 1
Mark client/server, works over a network
No Votes
0
2.1.2.5 Tagging of various points in development
1.6  
5
Details
Answer from Previous Round
This sub-question is summarised from the following answer(s) from round 1
Luke Tagging of various points in development
No Votes
0
2.1.2.9 Security features, e.g. usernames and passwords protection, access via ssh encryption
1.6  
5
Details
Answer from Previous Round
This sub-question is summarised from the following answer(s) from round 1
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
No Votes
0
2.1.2.3 Permitting concurrent development without locking and the ability to handle conflicting updates
1.7  
6
Details
Answer from Previous Round
This sub-question is summarised from the following answer(s) from round 1
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
No Votes
0
2.1.2.4 Handling of branching of code
1.8  
5
Details
Answer from Previous Round
This sub-question is summarised from the following answer(s) from round 1
Joseph branching
Alvin Allows branching of code
Luke Branching of code base
3 Responses
Relevant Glossary
Branching
No Votes
0
2.1.2.1 Complied to established standard, widely available and understood
1.8  
6
Details
Answer from Previous Round
This sub-question is summarised from the following answer(s) from round 1
Mark established standard, widely available and understood
No Votes
0
2.1.2.7 Rollback
2.0  
5
Details
Answer from Previous Round
This sub-question is summarised from the following answer(s) from round 1
Luke Security and rollback features
No Votes
0
2.1.2.8 Allowing anonymous users read only access
2.0  
5
Details
Answer from Previous Round
This sub-question is summarised from the following answer(s) from round 1
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)
No Votes
0
2.1.2.10 Accessable both through WWW as well as a local client program
2.5  
6
Details
Answer from Previous Round
This sub-question is summarised from the following answer(s) from round 1
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.
Comment made in round 3
Terence Helpful, but non-essential.
No Votes
0

2.1.3 What are the important usability factors of this tools?
2.1.3.10 Collaboration - Enables distributed users to collaborate by easy synchronization of their work
1.2  
6
Details
Answer from Previous Round
This sub-question is summarised from the following answer(s) from round 1
Gabriel Collaboration
No Votes
0
2.1.3.15 Efficiency - The users can achieve a level of high productivity when using the site
1.3  
4
Details
Answer from Previous Round
This sub-question is summarised from the following answer(s) from round 1
Luke Efficiency
No Votes
0
2.1.3.12 Updated Frequently - The site is frequently updated with latest information
1.6  
5
Details
Answer from Previous Round
This sub-question is summarised from the following answer(s) from round 1
Gabriel Updated Frequently
No Votes
0
2.1.3.8 Accuracy - The information processed and presented can be relied upon to be correct
1.8  
6
Details
Answer from Previous Round
This sub-question is summarised from the following answer(s) from round 1
William Accuracy
No Votes
0
2.1.3.5 Connectivity - The connection to the site is fast
2.2  
5
Details
Answer from Previous Round
This sub-question is summarised from the following answer(s) from round 1
Jacob Connectivity
No Votes
0
2.1.3.11 Completeness - All relevant materials are presented
2.3  
4
Details
Answer from Previous Round
This sub-question is summarised from the following answer(s) from round 1
Phil Completeness
Gabriel Completeness
No Votes
0
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
2.5  
4
Details
Answer from Previous Round
This sub-question is summarised from the following answer(s) from round 1
Mark Simple and natural dialogue
Joseph Simple and natural dialogue
No Votes
0
2.1.3.7 Coherence - The information is presented logically and without contradiction
2.5  
4
Details
Answer from Previous Round
This sub-question is summarised from the following answer(s) from round 1
William Coherence
Gabriel Coherence
No Votes
0
2.1.3.6 Ease of Navigation - The information is in a structure that is easy to navigate
2.6  
5
Details
Answer from Previous Round
This sub-question is summarised from the following answer(s) from round 1
William Ease of Navigation
No Votes
0
2.1.3.9 Feedback - The site gives informative feedback to users within reasonable response time
2.7  
3
Details
Answer from Previous Round
This sub-question is summarised from the following answer(s) from round 1
William Feedback
No Votes
0
2.1.3.1 Learnability - It is easy and intuitive to learn how to operate the site
2.8  
4
Details
Answer from Previous Round
This sub-question is summarised from the following answer(s) from round 1
Mark Learnability
No Votes
0
2.1.3.2 Memorability - It is easy to remember how to operate the site
3.5  
4
Details
Answer from Previous Round
This sub-question is summarised from the following answer(s) from round 1
Mark Memorability
No Votes
0
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
3.8  
4
Details
Answer from Previous Round
This sub-question is summarised from the following answer(s) from round 1
Mark Speak the users' language
Comment made in round 3
Terence Typically, abstruse names emphasize logical consistency vs. familiarity. While familiarity is useful, consistency is essential.
No Votes
0
2.1.3.14 Prevent errors - The site is designed to prevent possible error like spelling mistake from users
  4.6
5
Details
Answer from Previous Round
This sub-question is summarised from the following answer(s) from round 1
Joseph Prevent errors
No Votes
0

Show Only Top Ten
Show Only Numerical Data
Show All Relevant Data (Sort by Controversy)

Go up to Question 2
Go to Question 2.2

Generated On: 25 Oct 2002