Main.Software History

Hide minor edits - Show changes to output - Cancel

April 01, 2009, at 06:37 PM by 149.32.192.33 - renamed positions; added support applications specialist
Changed line 5 from:
The student lead should have strong organizational skills and know details of the robot electrical and control system. They will serve as the mentor for that group, as well as individual contributor.
to:
The student lead should have strong organizational skills and know details of the robot electrical and control system. This person will serve as the mentor for that group, as well as an individual contributor.
Changed line 12 from:
*Work with co-leads to ensure best use of team members and prioritization of tasks
to:
*Work with specialists,and individual contributors to ensure best use of team members and prioritization of tasks
Changed lines 21-23 from:
[+Student Co-Leads+]

Student co-leads take responsibility for aspects of the software tasking under the direction of the student lead. They serve as subject matter experts. They may coordinate the work of others in their subgroup, make recommendations and report status to the lead, as well as individual contributor.
to:
[+Student Specialists+]

Student specialists take responsibility for aspects of the software tasking under the direction of the student lead. They serve as subject matter experts. They may coordinate the work of others in their subgroup, make recommendations and report status to the lead, as well as be an individual contributor.
Changed lines 27-41 from:
*Ensure work is docmented

[+Student Co-Lead for Robot Operations+]

This person is responsible for working with student lead and mentors to coordinate robot software, including sensors, manipulators and drive. This person is expected to understand the code and serves as backup to all robot coders. This person ensures that the best use is made of test time by working as tasked by the student lead on test plans, test checklists and schedules.

[+Student Co-Lead for Support Applications+]

This person is responsible for working with student lead and mentors to coordinate the
development, maintenance and promotion of non-robot support applications, including the team web site, the scouting database, and other databases and applications used by the team. This person ensures that reviews are held, and that team members are aware of support applications and their benefits. This person also, with mentor approval, may release applications on the Internet, including Sourceforge, Chief Delphi, and the team Web site.

[+Student Co-Lead for Software Configuration Mangement+]

This person is responsible for working with student lead and mentors to investigate, select and implement CM tools and procedures for the software group. This person also ensures that all subteam members know and follow the procedures
. This includes tracking of software changes and software discrepancies, maintaining current baselines and tagging builds at appropriate times.

to:
*Ensure work is documented

[+Student Specialist(s) for Robot Operations+]

Responsible for working with student lead and mentors to coordinate robot software, including sensors, controls, manipulators and drive. Understands the code and serves as backup to all robot coders. Ensures that the best use is made of test time by working as tasked by the student lead on test plans, test checklists and schedules.

[+Student Specialist(s) for Development & Configuration+]

Responsible for working with student lead and mentors to ensure team computers and robots are configured with known versions of
development environments and operational software. Helps troublshoot installation and networking problms. Capable of updating robot / DS firmware and verifying connectivity and firmware versions.

[+Student Specialist(s) for Support Applications+]

Responsible for working with student lead and mentors to coordinate the development, maintenance
and promotion of non-robot support applications, including the dashboard, the team web site, the scouting database, and other databases and applications used by the team. This person ensures that reviews are held, and that team members are aware of support applications and their benefits. This person also, with mentor approval, may release applications on the Internet, including Sourceforge, Chief Delphi, and the team Web site.

[+Student Specialist for Software Configuration Mangement+]

Responsible for working with student lead and mentors to investigate, select and implement CM tools and procedures for the software group
. This person also ensures that all subteam members know and follow the procedures. This includes tracking of software changes and software discrepancies, maintaining current baselines and tagging builds at appropriate times.
June 17, 2008, at 12:15 PM by C B Petrovic - Add pit crew member identification task
Changed lines 19-20 from:
to:
*Assists in identifying Software Team pit crew member.
Changed lines 1-2 from:
This group is responsible for the development of the software component of the control control system of the robot.
to:
This group is responsible for the development of the software component of the control control system of the robot. This group also coordinates non-robot software activities and updates the team on software issues and design of team applications.
Changed lines 7-8 from:
*Interface between Electrical/Controls Team to coordinate software testing time.
to:
*Work with Electrical/Controls group to ensure test board requirements are met
*Work with Design Group to provide feedback and input to robot design
Added line 15:
*Interface with other leads to coordinate software testing time
Changed lines 18-19 from:
to:
*Communicate with the wider FIRST community by sharing code, algorithms, solutions, etc.
Changed line 22 from:
Student co-leads take responsibility for a aspects of the software tasking under the direction of the student lead. They serve as subject matter experts. They may coordinate the work of others in their subgroup, make recommendations and report status to the lead, as well as individual contributor.
to:
Student co-leads take responsibility for aspects of the software tasking under the direction of the student lead. They serve as subject matter experts. They may coordinate the work of others in their subgroup, make recommendations and report status to the lead, as well as individual contributor.
Changed lines 46-47 from:
*Document work
to:
*Follow team procedures for configuration control and documentation
June 12, 2008, at 02:37 AM by Beth - 2008 modifications - first draft
Changed line 8 from:
*Help set direction of design based on team’s strategy
to:
*Help set direction of design based on team's strategy
Changed line 12 from:
*Monitor work progress to ensure timely delivery of components.
to:
*Monitor work progress to ensure timely delivery of components
Changed lines 14-15 from:
*Help identify training needs and assist in developing and scheduling training sessions: work with mentors and assist in delivering the training.
to:
*Help identify training needs and assist in developing and scheduling training sessions: work with mentors and assist in delivering the training
*Ensure software documentation is generated and maintained
Added line 18:
Changed lines 23-24 from:
to:
*Ensure work is docmented
Added line 26:
Changed lines 30-31 from:
This person is responsible for working with student lead and mentors to develop, maintain and promote non-robot support applications, including the team web site, the scouting database, and other databases and applications used by the team.
to:

This person is responsible for working with student lead and mentors to coordinate the development, maintenance and promotion of non-robot support applications, including the team web site, the scouting database, and other databases and applications used by the team. This person ensures that reviews are held, and that team members are aware of support applications and their benefits. This person also, with mentor approval, may release applications on the Internet, including Sourceforge, Chief Delphi, and the team Web site.
Added line 34:
June 12, 2008, at 02:30 AM by Beth - 2008 modifications - first draft
June 12, 2008, at 02:28 AM by Beth - 2008 modifications - first draft
Changed lines 3-4 from:
[+Student Lead & Backup+]
to:
[+Student Lead+]
Changed line 6 from:
*Liaison between mentors and the subteam members
to:
*Ensure software reviews are held and that the content of the software is inspected
Changed line 8 from:
*Help set direction of design based on teamís strategy
to:
*Help set direction of design based on team’s strategy
Changed lines 10-11 from:
*Develop software module interfaces
to:
*Define software module interfaces
*Work with co-leads to ensure best use of team members and prioritization of tasks
Changed lines 14-15 from:
*Help identify training needs and assist in developing and scheduling training sessions: work with mentors who will deliver the training.
to:
*Help identify training needs and assist in developing and scheduling training sessions: work with mentors and assist in delivering the training.

[+Student Co-Leads+]
Student co-leads take responsibility for a aspects of the software tasking under the direction of the student lead. They serve as subject matter experts. They may coordinate the work of others in their subgroup, make recommendations and report status to the lead, as well as individual contributor.
*Help with training
*Consult with student lead on tasking
*Participate in software reviews

[+Student Co-Lead for Robot Operations+]
This person is responsible for working with student lead and mentors to coordinate robot software, including sensors, manipulators and drive. This person is expected to understand the code and serves as backup to all robot coders. This person ensures that the best use is made of test time by working as tasked by the student lead on test plans, test checklists and schedules.

[+Student Co-Lead for Support Applications+]
This person is responsible for working with student lead and mentors to develop, maintain and promote non-robot support applications, including the team web site, the scouting database, and other databases and applications used by the team.

[+Student Co-Lead for Software Configuration Mangement+]
This person is responsible for working with student lead and mentors to investigate, select and implement CM tools and procedures for the software group. This person also ensures that all subteam members know and follow the procedures. This includes tracking of software changes and software discrepancies, maintaining current baselines and tagging builds at appropriate times.


Changed lines 37-38 from:
to:
*Document work
Changed lines 1-21 from:
The Software subteam lead is charged with the following responsibilities:
to:
This group is responsible for the development of the software component of the control control system of the robot.

[+Student Lead & Backup+]

The student lead should have strong organizational skills and know details of the robot electrical and control system. They will serve as the mentor for that group, as well as individual contributor.
*Liaison between mentors and the subteam members
*Interface between Electrical/Controls Team to coordinate software testing time.
*Help set direction of design based on teamís strategy
*Develop and maintain software control flowchart
*Develop software module interfaces
*Monitor work progress to ensure timely delivery of components.
*Keep mentors informed of changes to Plan Of Record (to be determined by overall team & strategy chosen)
*Help identify training needs and assist in developing and scheduling training sessions
: work with mentors who will deliver the training.

[+Individual Contributors+]

*Work with team lead to develop assigned software modules
*Be able to troubleshoot electrical/controls problems during design and competition.
*Keep team lead appraised of work status

Back to [[JobDescriptions]]
Added line 1:
The Software subteam lead is charged with the following responsibilities:


Page last modified on April 01, 2009, at 06:37 PM