Page Operations
Browse Space
CI Development Team Meeting, 21-Jan-2009
| ID | Ag. |
Type |
What? |
Who? |
Due Date |
| 1 | 1 | AI | Resolve issue of work assignment to OOI with Ingolf. OOI expects 100% assignments. | Matt, Ingolf | |
| 2 | 2 | I | The development team (DT) has finished development of the DDN. The DDN is up and running as of now. It can be considered delivered as IOC (Initial Operating Capability). | DT | |
| 3 | 2 | I | The architecture team's responsibility in general includes to do testing, documenting the architecture and preparing the IOC system for releases to users. | ||
| 4 | 2 | AI | Demonstrate JIRA for defect tracking to AT such that they are ready to use it | DT (Tom) | Fri 1/23 |
| 5 | 2 | AI | Provide a testable version of the IOC system for testing by AT with a capable web user interface, such that the AT can understand and document the interactions with the end users. | DT (Alex, Dorian) | Fri 1/23 |
| 6 | 2 | AI | Test the IOC deliverable from the DT, enter defects into JIRA and produce a report with summary as deliverable. The report contains: What has been tested and which bugs were found (categories) and how many and strategies to address them. Defects need to be entered into JIRA. |
AT (Claudiu, Emilia) | Mon 1/26 |
| 7 | 2 | AI | Develop a specification/documentation of how the product was built and how it is used by end users. The documentation can be embedded in the end user UI as help hovers (similar to ERDDAP). The decisions of how to document and what are made by the AT. Time and effort are bounded. |
AT (Claudiu, Emilia) | Mon 1/26 |
| 8 | 2 | AI | Architectural Review presentation on architecture and UI. Application architecture emphasize much more important than deployment architecture. Present a workplan of which defects can be addressed by end of week and how documentation tasks can be addressed. |
AT (Claudiu, Emilia) | Mon 1/26 |
| 9 | 2 | AI | Respond to defects reported by AT over the week. Finish the implementation and release a production quality system to be used by end users. | DT (Alex, Dorian) | Fri 1/30 |
| 10 | 2 | AI | Make decision on status of deliverable and how to proceed based on assessment by AT and DT. | DevTeam | Feb 2/2 |
| 11 | 2 | I | Goal: This is a time bounded exercise in executing the roles of development and architecture (IVT, integration and verification teams) teams. The outcome is a delivered DDN prototype that can be used by end users. Teams are DT: Alex, Dorian and AT: Claudiu, Emilia. This is practice for moving ahead and going through the process of the next six months. The backside of the AT's responsibility is to verify that the system was built according to the architecture. Another part is the documentation of the use model. The AT's task is to make decisions regarding documentation that are best suited for limited fixed effort and with good results. There will be testers (roles) in MREFC who are looking at system components as units. This is different from the AT's role of verifying the entire system against the specification. After the AT's OK, it goes to the CI SE and then to end users. |
||
| 12 | 2 | I | Bugs are categorized into four categories: Stop-ship: Fatal, cannot be released, bring the system down Critical: Don't bring the system down but represent a serious risk to users Non-critical: Exists in system as built but not serious risk to users. Nice to have/feature request. Decisions are done based on these categorizations for the entire course of the project. |
||
| 13 | 2 | AI | Work with Munindar on SoW for agent development during pilot. The AT is main point of contact for Munindar. Email to Munindar (CC to Matt, Mike) today. Need Munindar's SoW by Monday and finished by Wed. The SoW is covering the agent project (4 weeks). The agent parts will become core of the DDN. The real part of the DDN is around contract network to be done subsequently |
Claudiu, Emilia | Thu 1/22 |
| 14 | 2 | I | Claudiu and Emilia work with Matt on the data side of data distribution network with Peter Fox, John Graybeal on Hyrax, semantic framework etc. Michael works on OSSE for the time being and calls in resources from the AT and DT when needed. Deadline for both efforts and related efforts is September. Official documents have to be given to NSF during that time period showing status. |
||
| 15 | 2 | I | Mathieu Lemay is just ready to release his implementation of the IaaS. That will be a core component of the resource network. | ||
| 16 | 2 | I | MARS deployment pilot will deploy 100m away from a MARS cabled observatory node a CTD and seismometer on an instrument platform. Instrument agents are required. Feeding the DDN | ||
| 17 | 2 | I | OSSE: By the time of the field deployment of OSSE the goal is to have the agents, DDN, an on-platform navigation system with MOOSDB and CASPER, shore side ASPEN all lined up together. Goal by Dec 2009 | ||
| 18 | 3 | I | Demo of the DDN prototype. It is up and running but has still minor defects that need to be addressed. | ||
| 19 | 3 | I | The cycle in the next 10 days is about delivering an end user product not about innovation or perfectioning. | ||
| 20 | 3 | I | The system to be tested will be in the cloud. The belief is that all systems are installations in the cloud that only differ in configuration for testing, verification and production. There are no laptop versions of the system planned. |