NRAO Home  >  Green Bank  |  Wiki Topic:    GB > Software > PlanOfRecordC22008 > ModificationRequest10C208

Changes | Index | Contents | Search | Statistics | Go

DSS: Overview Calendar

Modification Request #10 (C2 2008)

• 1. Introduction
• 2. Background
• 3. Requirements
  • 3.1 "Round Tuits"
• 4. Out of Scope
• 5. Design
  • Tasks
• 6. Deployment
• 7. Test Plan
  • 7.1 Internal Testing
  • 7.2 Sponsor Testing
  • 7.3 Integration/Regression Tests
• Signatures
• CCC Discussion Area

1. Introduction

The scheduler's responsibilities require that he or she is able to understand the long-term implications of the telescope schedule beyond the currently known weather forecast to handle monitoring projects, fixed sessions, and receiver changes. This implies a broad view of the trimester, while currently the DSS provides only a 2-5 day scheduling calendar.

2. Background

This is not in the SoftwareAgileWorkBreakdownStructure because its need became out of the work on importing backlog projects (ModificationRequest8C108) which contained many monitoring projects. See DSS project charter for more information.

3. Requirements

Add the following features by end of April:

Create an overview calendar which:

• provides a wider view of the schedule
• provides functionality for making adjustments to the schedule across days and weeks
• spans roughly a months worth of time
• provides the same information about sessions as does the existing schedule page (up to physical limits)
• color codes sessions such that:
  • all fixed sessions are the same color (i.e. black)
  • all windowed sessions of the same allocation share the same color

3.1 "Round Tuits"

• display all types of sessions with a way to toggle between different types.
• color codes open sessions such that all are the same color (i.e. gray)

4. Out of Scope

• The Overview Calendar should be used for moving scheduled sessions (windowed, fixed, and open), but will not be used for scoring, packing, or brining up candidates for a datetime; this functionality should be the exclusive responsibility of the schedule page.

5. Design

Tasks

• refactor database in regards to relations between allocations, sessions, and opportunities

• backfill unit tests

See the Dynamic Scheduling Documentation.

6. Deployment

Not being deployed at time of completion.

7. Test Plan

7.1 Internal Testing

Unit tests.

7.2 Sponsor Testing

Inspect skeleton as it is developed.

7.3 Integration/Regression Tests

None required since it is not being deployed upon completion.

Signatures

APPROVED: I acknowledge that my request is fully contained in this MR, and if the SDD delivers exactly what I specified, I will be happy.

ACCEPTED: I acknowledge that I have validated the completed code according to the acceptance tests, and I am happy with the results.

Written	- PaulMarganian - Mar 19 08
Checked	- MarkClark - 19 Mar 2008
Approved by Sponsor	-- KarenONeil - 27 Mar 2008
Approved by CCC	- AmyShelton - 27 Mar 2008
Accepted/Delivered by Sponsor	- KarenONeil - 05 May 2008

Symbols:

• Use %X% if MR is not complete (will display )
• Use %Y% if MR is complete (will display )

CCC Discussion Area