DUCS-CRAVE guide2008

From CRAVEwiki

Jump to: navigation, search

DUCS & CRAVE has come a long way from its establishment. New structure and new projects have caused the organization to evolve into an elite computer student body like none other in DBIT.


This article is guidebook to new project manager, DUCS - CRAVE members and interested students. A certain list of simple procedures and rules to be followed for the academic year 2008 - 2009. The guide is likely to be revised with the input from more project managers and core group members of DUCS.


Contents

DUCS - CRAVE Structure

The first step is to understand DUCS - CRAVE Structure and its functioning. Given below is pictorial representation of structure of DUCS and CRAVE which can help in understanding the functioning of the organization. For more details you can always DUCS site and CRAVE site.


DUCS - CRAVE Projects

All the members are required to be involved in a certain project. Students interested in joining are asked to join an existing projects or pick up ideas from here for DUCS or for CRAVE. For more details you can read the following articles

Project's monthly report must be handed over to project manager and its documentation should be hosted on CRAVE wiki. Along with project documentation and the research members are also requested to write articles on applications they have used in their project.

On completion or half way through the project, members are encouraged to make a formal presentation.


Documentation

The key to success of this organization is documentation through which knowledge sharing takes place among members of CRAVE & DUCS. After a year of its establishment, CRAVE decided to start documenting everything CRAVE wiki. Since the goal of DUCS and CRAVE is to create a vast knowledge base DUCS too decided to contribute by documenting all that is done in CRAVE wiki.


It is mandatory for all the members of DUCS & CRAVE to document their projects, their finding and their new learned concepts on CRAVE wiki.


Text Engineering Group & Documentation Department

Needless to say moderation and administration of CRAVE wiki is of utmost importance. The web development team is completely responsible for technical aspects of site. Whereas the Text Engineering Group of DUCS and Documentation department of CRAVE are responsible for moderating CRAVE wiki. The two bodies are responsible of the design & structure of CRAVE wiki. It is their duty to guide members while they are documenting on wiki. Time to time revision and addition of tutorials on using wiki is part of the program for these bodies


Web Development Team

Along with crave wiki the web development team are also responsible for maintaining CRAVE site. The involvement of the team in CRAVE site will be under direct supervision of project manager since the site also provides services to clients of CRAVE.

They are also expected to put forth an helping hand to DUCS Infrastructure Group (DIG) when required help in maintaining DUCS site.

DUCS site will provide many options and features to students and staff of DBIT. Site will be administered by a few dedicated members of DIG.


System Administration

Maintenance of the machines in CRAVE lab including the DWARF is top priority, since the machines will not only be used by members but also by other students of DBIT for academic activities.

The responsibility is been given to the DIG and System Administration team. They can be called upon by the central administration department of DBIT to help them manage or build certain infrastructure likes labs, networking, etc.


Free Software Support Group

Free Software Support Group will be looked upon by other members in case if they are looking for an open source application or have found any. Although the tutorials on applications have to be written by the member using it . Future moderation of such tutorials is this group's responsibility. This group is expected to have the latest information on new open source applications and its revision. They also have to publish latest news in open source technology on DUCS site.

This group will also consult visual/sound & E-learning departments of CRAVE. Currently this group will be actively involved in the execution and management of DBIT Open Source Revolution project.

Project Manager

Every year a new project manager would be appointed by the management to take forth the organization into next level and execution of new projects. A student who has recently given his B.E. examination is offered the position of project manager of CRAVE under the designation of an Research Associate for CRAVE Project. The selection criteria of the project manager depends largely on his or hers active involvement in the organization as a student, area of interests, future goals, etc.


The project manager of CRAVE is not only responsible for the effective functioning of CRAVE but also of DUCS since he or she will automatically be a core group member of DUCS.


Some of the duties involve:

  • Monitor all member's respective Project.
  • Supervise various SIGs and departments in the organization.
  • Execute the project assigned by the management.
  • Administer the CRAVE site and the mailing lists.
  • Assign forum moderators for CRAVE site.
  • Conduct the annual presentation.
  • Conduct the annual training program.
  • Submit a monthly report to the Director R&D and Management.
  • Documents everything that is done.
  • Present to the management the next project manager.
  • Train the new project manager.
  • Handover the necessary authorization to the next project manager.
  • Establish some future goals for organization before leaving.


Author

  • Kevin Pinto
Personal tools