NRAO Home  >  Green Bank  |  Wiki Topic:    GB > Software > ModificationRequest4C108

Changes | Index | Contents | Search | Statistics | Go

DSS: Create, Read, Update, and Delete

Modification Request #4 (C1 2008)

• 1. Introduction
• 2. Background
• 3. Requirements
• 4. Out of Scope
• 5. Design
• 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 current DSS Mock-up contains rudimentary display web pages for projects, sessions, news, and scheduled sessions. It is important that the information is displayed for perusing and editing such that it is useful to the observers and scheduler as opposed to being an obstacle. This iteration is a first cut toward providing the central user's interface.

2. Background

Fourth step in the SoftwareAgileWorkBreakdownStructure (release 0.4) [refer to "project/session view, edit, and add/delete" in the User table]. See DSS project charter for more information.

This MR builds upon the Long-Term Probabilities Generation.

3. Requirements

Add the following features by February 1, 2008:

• provide for display and editing of project and session database table fields
• display breakdown of scoring of sessions for selected times
• display status of proposed, scheduled, pending, and completed sessions.
• allow for generation of schedule-analysis plots a la Dana's simulator Move out into its own MR (ModificationRequest11C208)
• shared code for generation of simulated sessions for the mock-up and Dana's simulator

"Round Tuits"

• telescope-wide ical
• basic navigation menu
• projects view
• day/night scoring
• news items for high telescope-time probability and sessions modifications

4. Out of Scope

5. Design

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	- MarkClark - 17 Jan 2008
Checked	- MikeMcCarty - 17 Jan 2008
Approved by Sponsor	- KarenONeil - 06 Feb 2008
Approved by CCC	- AmyShelton - 06 Feb 2008
Accepted/Delivered by Sponsor	- KarenONeil - 14 Mar 2008

Symbols:

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

CCC Discussion Area