PDA

View Full Version : Project for Students



QUOCDN
07-09-2006, 14:09
Most universities fill most of a student's college career on theory, basic knowledge, and small individual assignments. Usually there is only one "senior project" class or one "software engineering" class where students work in teams to build a fairly large project. In these classes, students get their first real taste of the day-to-day concerns of professional software developers.

This may be the first time that students use a version control or issue tracking system.

This category is for students to host their class projects. Projects can be open or proprietary based on the instructor's rules for the course. After the end of the course, projects will be archived and removed, or made into open source projects.
Students proposing projects in this category should include the course name and instructor email in the project description.

This is the initial web content for your project. Please customize this to fit your project. You dont need to anwser all these questions or follow this exact format, but we do like to see this kind of information before we approve projects for public viewing.

Until your project is approved, only you can view it and work on it. http://ajax.tigris.org

Interested instructors are encouraged to contact me (cultureinit@yahoo.com.vn) with any questions or to discuss plans.

QUOCDN
07-09-2006, 14:13
http://www.collab.net/rn/4_5_0.html

Supported IDEs and Plug-Ins
Subclipse 1.0.0 for Eclipse 3.2 with SVN
Eclipse 3.2 with CVS
NetBeans 5.0 with SVN
NetBeans 5.0 with CVS
Jalindi Igloo version 1.03 (VisualStudio.NET addin for CVS)
Supported Version Control Clients
TortoiseSVN - version 1.3.3 (A Subversion client)
TortoiseCVS - version 1.8.24 (A CVS client)
WinCVS - version 2.0.2.4 (A CVS client)

Supported Bridges
ClearCVS - A bridge between ClearCase and CVS
CVS2SVN - A bridge between CVS and Subversion

QUOCDN
07-09-2006, 14:29
Description
The main list for developers to discuss project development issues/artifacts and requirements for version control.

Subscribe
send email to me : dev-subscribe@ajaxproject.tigris.org

QUOCDN
07-09-2006, 14:31
Aministrator : owner@ajaxproject.tigris.org

QUOCDN
07-09-2006, 14:36
Project members are permitted to work with the full set of project tools, including reporting issues using the Issue
Tracker or Project Tracker tool, participating in project mailing lists and discussion forums, and working on project source code using version control.

There are different types of project membership. When you join a project, you request a particular project role. For example, a Developer role can access the version control repository and a Project Owner role can create and administer new projects. See the project roles help for more details.

To request membership in a project:Click the Request project membership/role link on the Project home page.
Users who are not logged into the domain, do not have permission to join the project or are already members of the project will not see this link. For users who have permission to join the project, the Request project membership/role page is displayed.
To select a project role, click the radio button to the left of the desired role and click the Submit request button.
Depending on the project configuration, you will receive an email approving or disapproving your request. Upon being approved, you will also receive more information about the project.

To change your role in the project: Click the Projects tab.
Click the link for the project where you want to change the role.

On the project home page, if your current role in the project is below Project Owner, a Request project role link is displayed.
Your current role is noted in the top section, and the remaining roles available to you are displayed.

Select a new role and click Submit request.
Your request is submitted to the project owner for approval.

QUOCDN
07-09-2006, 14:38
Process overview: Example of promoting an artifact through lifecycle stages:

A project member clicks the Projects tab, clicks the link to a project that uses the CollabNet Baseline Process template, and clicks the Definition stage icon.

Definition:
The project member clicks the New requirement link, creates a new requirement named Requirement A, and sets the Stage in Lifecycle attribute for Requirement A to Definition.

Requirement A now appears when any project member clicks the Ready for definition link in the activity area of the Definition page.

After evaluating the requirement, a product manager clicks the Ready for definition link, clicks the link for Requirement A, and sets the value of Accepted into current stage? for

Requirement A to Yes.
Requirement A now appears when anyone clicks the Currently in definition link.

Transition to Design:
When all use cases are written for Requirement A, the product manager sets the Definition complete? attribute to Yes for Requirement A and sets the Stage in lifecycle attribute for
Requirement A to Design.

Requirement A now appears when any project member clicks the Ready for design link in the activity area of the Design page.

Design:
A technical lead clicks the Design icon in the navigation toolbar, clicks the Ready for design link, reviews Requirement A, and conducts other activities prescribed by the local development process. When Requirement A is approved, the technical lead sets the value of Requirement A's Accepted into current stage? attribute to Yes.

Requirement A now appears in the results for the Currently in design query on the Design page.

Transition to Code and Build:
A design engineer, after creating design documents, sets the value of Design complete? for Requirement A to Yes, and sets the Stage in Lifecycle for Requirement A to Code & Build.
Requirement A now appears when any project member clicks the Ready for code & build link in the activity area of the Code & Build page.

Code and Build:
An implementation engineer clicks the Ready for Code & Build link in the activity area of the Code & Build page, and clicks the link for Requirement A.

After evaluating whether this requirement is ready to be coded, the implementation engineer sets the value of Requirement A's Accepted into current stage? attribute to Yes.

Transition to Testing:
When Requirement A is fully implemented, the implementation engineer sets the value of Code & Build complete? to Yes, and sets the Stage in lifecycle attribute to Testing.

Testing:
A testing engineer clicks the Testing stage icon, clicks the Ready for testing query, clicks the link for Requirement A, and sets the value of Accepted into current stage? for Requirement A to Yes.

The testing engineer may find bugs and raise defects against the requirement. When testing is complete, the test engineer sets the value of Test complete? for Requirement A to Yes, and sets the Status of Requirement A to Complete.

Note: Other attributes indicate the degree of "done-ness" of the artifact. For example, a Status attribute can be set to Complete when a requirement has been completely defined, designed, coded, and tested.

QUOCDN
07-09-2006, 14:42
CVS client setup instructions-Access options

* Setup WinCvs client
* Setup TortoiseCVS client
* Setup CVS command line client

QUOCDN
07-09-2006, 14:49
Cac ban co the them khao mo hinh web-based software project management qua gioi thieu ben duoi cua cac ban :

About Trac 0.9.6
Trac is a web-based software project management and bug/issue tracking system emphasizing ease of use and low ceremony. It provides an interface to the Subversion revision control systems, integrated Wiki and convenient report facilities.

Trac is distributed under the modified BSD License.
The complete text of the license can be found in the COPYING file included in the distribution.

Please visit the Trac open source project: http://projects.edgewall.com/trac/

Trac is a product of Edgewall Software, provider of professional Linux and software development services.

Copyright © 2003-2006 Edgewall Software