Pre-PDR Peer Review 1 UCB MAVEN Particles and Fields Flight Software Peer Review RFAs and Recommendations Peter R. Harvey.

Slides:



Advertisements
Similar presentations
AESuniversity Ad hoc Reporting. Ad hoc Reports What are ad hoc reports? Why would you use ad hoc reports? Creating an ad hoc report from a query Building.
Advertisements

Rosetta Magnetic Field PDS Review B. J. Anderson.
Blackfin BF533 EZ-KIT Control The O in I/O Activating a FLASH memory “output line” Part 2.
1 PFP IPDR 2010/6/ Particles and Fields Package (PFP) GSE Timothy Quinn.
EE694v-Verification-Lect5-1- Lecture 5 - Verification Tools Automation improves the efficiency and reliability of the verification process Some tools,
The Project AH Computing. Functional Requirements  What the product must do!  Examples attractive welcome screen all options available as clickable.
MAVEN CDR May 23-25, 2011 Particles and Fields Package Pre-Environmental Review May , 2012 Flight Software Peter R. Harvey Mars Atmosphere and Volatile.
Solar Probe Plus FIELDS ICU/FSW Peter R. Harvey Dorothy Gordon –ICU Will Rachelson – FSW Dec 1, 2012.
SwRR 4/28/ Telecon MAVEN Particles and Fields Flight Software Requirements Review SwRR Peter R. Harvey April 28, 2010.
Technological Design STS-118 Lunar Plant Growth Chamber Challenge © 2013 International Technology and Engineering Educators Association STEM  Center for.
1 PFP MSR, 11/17/2009 Particles and Fields Package Monthly Status Review (MSR) November 17, 2009 Dave Curtis, PFP PM.
Barbara PlanteFIELDS iPDR – DCB Flight Software Solar Probe Plus FIELDS Instrument PDR DCB Flight Software Barbara Plante UC Berkeley SSL
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
INFO 424 Team Project Practicum Week 2 - Launch report, Project tracking, Review report Glenn Booker Notes largely from Prof. Hislop.
21-1 MAVEN IPSR October 30,31, 2012 Particles and Fields Package Pre-Ship Review October 30,31, : Flight Software Peter R Harvey Mars Atmosphere.
8:15 AM Tuesday September 15, 2009 Karl Frank, Point of Contact for Constellation Projects Validating Integration Requirements Diagrams for illustrative.
RBSP Radiation Belt Storm Probes RBSP Radiation Belt Storm Probes 12/25/20151 Flight Software Template for Instrument Critical Design Review Gary M. Heiligman.
Renesas Technology America Inc. 1 SKP8CMINI Tutorial 2 Creating A New Project Using HEW.
GLAST Large Area Telescope LAT Flight Software System Checkout TRR Systems Engineering Mike DeKlotz GSFC Stanford Linear Accelerator Center Gamma-ray Large.
ACT476 CAPSTONE WRITING AN USER MANUAL. Developers VS Users Developers want to write code Have little time to document or write user’s manuals Users on.
Status 1 Telecon MAVEN PFFSW STATUS 8/14/2012 Conf: #
SPI NIGHTLIES Alex Hodgkins. SPI nightlies  Build and test various software projects each night  Provide a nightlies summary page that displays all.
Pre-PDR Peer Review 1 UCB MAVEN Particles and Fields Flight Software Peer Review Requirements Definition Peter R. Harvey May 12, 2010.
HarveyFIELDS iCDR – Flight Software Solar Probe Plus FIELDS DCB FSW Requirements Peter Harvey University of California 1.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Lab 3 – SRS Review & Implementation Planning. Milestones 1.Web Page Design & Implementation 2.Revise communication protocol 3.Develop a test tool for.
HarveyFIELDS iCDR – Flight Software Solar Probe Plus FIELDS DCB Flight Software Design Peter Harvey University of California 1.
ESOC | Chris Watson | ESA/ESOC | Page 1 SOC-Instrument Team interfaces CHRIS WATSON ESAC.
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
Software Development Module Code: CST 240 Chapter 6: Software Maintenance Al Khawarizmi International College, AL AIN, U.A.E Lecturer: Karamath Ateeq.
SOFTWARE TESTING TRAINING TOOLS SUPPORT FOR SOFTWARE TESTING Chapter 6 immaculateres 1.
Benefits of a Virtual SIL
Operational Flight Software
Simulink Interface Layer (SIL)
Particles and Fields Package (PFP) SWEA Pre-CDR Peer Review
What’s New in Time Off for ADP Workforce Now
I&T&C Organization Chart
Introduction to the C Language
PANA Issues and Resolutions
Architecture Concept Documents
Configuration Management Why do we need it? What does it do?
Proposals and Progress Reports
GLAST Large Area Telescope:
Sizing With Function Points
A451 Theory – 7 Programming 7A, B - Algorithms.
Software Documentation
Acceptance Test Review
Performance Feedback Training
IS442 Information Systems Engineering
IBM Kenexa BrassRing on Cloud Responsive Apply: Gateway Questionnaire Configuration April 2017.
Test Planning Mike O’Dell (some edits by Vassilis Athitsos)
The Object-Oriented Thought Process Chapter 05
Proposed Software Development Process
The Student Experience
Chapter 5 Architectural Design.
More on Estimation In general, effort estimation is based on several parameters and the model ( E= a + b*S**c ): Personnel Environment Quality Size or.
An Introduction to Software Architecture
Chapter 7 –Implementation Issues
CS 8532: Advanced Software Engineering
Software Requirements Specification (SRS) Template.
NSS Instrument Project Tollgate Coordinator
Geant4 Documentation Geant4 Workshop 4 October 2002 Dennis Wright
Submission Title: LB Resolutions from kivinen
Copyright © 2010 Pearson Education, Inc.
Command and Data Handling
FPGA Vinyl to Digital Converter (VDC)
Integration & Test Instrument Operations Coordination
<Your Team # > Your Team Name Here
MIB TruthValue Usage Patterns Presentation
DSG Governance Group Recommendations.
Presentation transcript:

Pre-PDR Peer Review 1 UCB MAVEN Particles and Fields Flight Software Peer Review RFAs and Recommendations Peter R. Harvey

Pre-PDR Peer Review 2 UCB Recommendation SwPDR-1 Title : Requirement Comm Loss Response Reviewer: S. Harris (Chair) Recommendation: Currently the time out is set to 3 seconds. Instrument needs an override on the response to deal with test scenarios. Response: The FSW response to a Communication Timeout is planned to be a Real-Time-Sequence action. Since all RTS’s can be disabled, it would be straightforward to disable that RTS in test scenarios when S/C messages are turned off.

Pre-PDR Peer Review 3 UCB Recommendation SwPDR-2 Title : Requirement 310 – Similar HV requirements Reviewer: S. Harris (Chair) Recommendation: This requirement, as well as similar ones for several instruments, looks identical to the generic rule for HV control (Req 243). Why have separate requirement for Static and each instrument? Response: Agreed. Below is a comparison of the HV requirements. We plan to move common elements to one general requirement, and leave unique elements with each instrument HV system.

Pre-PDR Peer Review 4 UCB Recommendation SwPDR-3 Title : Requirement Typo Reviewer: S. Harris (Chair) Recommendation: “Sun” should be “Sum” Response: Corrected in the MAVEN_PF_SYS_010_FSWRequirements revision F And will be corrected in MAVEN_PF_FSW_002_SRS revision D

Pre-PDR Peer Review 5 UCB Recommendation SwPDR-4 Title : S/C Command Timing Reviewer: S. Harris (Chair) Recommendation: The gap time between commands from the S/C needs clarification in the ICD. Response: Will clarify the timing in the S/C ICD has no TBDs and is consistent with the FPGA and FSW expectations. Answer:

Pre-PDR Peer Review 6 UCB Recommendation SwPDR-5 Title : New Platform, New FSW Risk Reviewer: S. Harris (Chair) Recommendation: The team should consider adding a project risk that using a new processor (Coldfire) and developing the FSW in a different language (C), presents a risk to the schedule. The FSW is based on the same architecture as the heritage code, but is being entirely re-written in C and assembly, for a different processor, using a new development environment Response: We have added this to the risk list as a schedule risk (not technical since we have plenty of technical margins). The plan would be to watch the development to determine what troubles we run into. If the conversion process is much more difficult than planned, we should review the approach before we run out of time.

Pre-PDR Peer Review 7 UCB Recommendation SwPDR-6 Title : Document Due Dates Reviewer: T. Jackson Recommendation: Re-evaluate your project requested document list and due dates. Your list is not correct. Response: MAVEN-SYS-PLAN-0020 page 47 is the source of columns 1 and 2 of the table below. The STP and SMP are due in 2011 and 2012 and are not due this year. The confusion stems from pages 41 and 42 where these documents are listed as necessary for the successful PDR.

Pre-PDR Peer Review 8 UCB Recommendation SwPDR-7 Title : Re-Evaluate FSW Risks Reviewer: T. Jackson Recommendation: Re-evaluate your current risks. Add in some realistic risks. Also remove the absurd. Response: The risk list shown in the presentation showed only the format of risks, and was not supposed to represent the actual list. We plan to provide a FSW risk list shortly.

Pre-PDR Peer Review 9 UCB Recommendation SwPDR-8 Title : Define Instrument Mode Set Reviewer: E. Taylor Recommendation: Comment during the review that we wouldn't have defined instrument modes, configuration is set by RTS. Suggest a number of modes be explicitly defined for test and used initially for early orbit operations. (Compression algorithms should be run on modes to get accurate (tested) estimate of real data volume). Response: Will define a risk here, that we don’t understand the interplay between instruments and this could lead to resource issues of one sort or another. We would retire the risk by defining the modes carefully.

Pre-PDR Peer Review 10 UCB Recommendation SwPDR-9 Title : S/C Interface Concerns Reviewer: E. Taylor Recommendation: Not a lot of confidence in the SC/PFIDPU Interface. Seemed to be confusion on what was in ICD, what should be in there. No LM SC Simulator is being delivered to UCB. ETU test is hardware test only, LM instrument I/F FSW will not be implemented until shortly before Instrument delivery Response: We could define a risk here that the FSW is being developed while the S/C interface is still changing. Of course, it is standard practice to have these TBDs for a while. Nonetheless, we would retire the risk when the ICD is firm.

Pre-PDR Peer Review 11 UCB Recommendation SwPDR-10 Title : New Platform, New FSW Risk Reviewer: E. Taylor Recommendation: New software language (0 line of codes re-use), new platform should be a risk. Response: Same response as SwPDR-5

Pre-PDR Peer Review 12 UCB Recommendation SwPDR-11 Title : Simplify HV Control Requirements Reviewer: P. Harvey Notes Recommendation: In the requirements section, there are many requirements for HV control that seem to be the same. Perhaps it would be better to reduce these to a single requirement.. Response: Same response as SwPDR-2

Pre-PDR Peer Review 13 UCB Recommendation SwPDR-12 Title : Simplify Attenuator Control Requirements Reviewer: P. Harvey Notes Recommendation: In the requirements section, there are many requirements for Attenuator control that seem to be the same. Perhaps it would be better to reduce these to a single requirement. Response: Agreed. Below is a comparison of the Atten requirements. We plan to move common elements to one general requirement, and leave unique elements with each instrument attenuator.

Pre-PDR Peer Review 14 UCB Recommendation SwPDR-13 Title : Requirement 516: Typo Reviewer: P. Harvey Notes Recommendation: In the requirements section, PFFSW-516 has "Sun" instead of "Sum" in two places. Needs to be corrected in the SRS. Response: Same response as SwPDR-3

Pre-PDR Peer Review 15 UCB Recommendation SwPDR-14 Title : Requirement 802 Correction Reviewer: P. Harvey Notes Recommendation: In the requirements section, PFFSW-802 has 256 bytes per table. This should be 512 bytes per table. Response: Corrected in the MAVEN_PF_SYS_010_FSWRequirements revision F And will be corrected in MAVEN_PF_FSW_002_SRS revision D

Pre-PDR Peer Review 16 UCB Recommendation SwPDR-15 Title : Code Coverage Metric Reviewer: P. Harvey Notes Recommendation: In the plan section, page 6, the Code Warrior toolset includes a code coverage metric which may be useful. Response: We already bought the Standard version and it does not include the code coverage analysis. If we buy another copy, we will consider this option.

Pre-PDR Peer Review 17 UCB Recommendation SwPDR-16 Title : New Platform, New FSW Risk Reviewer: P. Harvey Notes Recommendation: In the plan section, page 9, a risk should be written that captures the "new" development environment, new language. Response: Same response as SwPDR-5

Pre-PDR Peer Review 18 UCB Recommendation SwPDR-17 Title : Document Due Dates Reviewer: P. Harvey Notes Recommendation: In the plan section, page 17, the STP and SMP are not due at this time. Response: Same response as SwPDR-6

Pre-PDR Peer Review 19 UCB Recommendation SwPDR-18 Title : SRAM typo Reviewer: P. Harvey Notes Recommendation: In the design section, page 3, the DRAM should be SRAM. Response: Corrected in the figure for PDR.

Pre-PDR Peer Review 20 UCB Recommendation SwPDR-19 Title : TM Output requirement Reviewer: P. Harvey Notes Recommendation: In the design section, page 7, the TM only has one low rate output. There is no high rate transmitter Response: Corrected in the figure for PDR.

Pre-PDR Peer Review 21 UCB Recommendation SwPDR-20 Title : SWIA description Reviewer: P. Harvey Notes Recommendation: In the design section, page 7, the SWIA has a "manager" too Response: Corrected in the figure for PDR.

Pre-PDR Peer Review 22 UCB Recommendation SwPDR-21 Title : TM NOOP Requirement Reviewer: P. Harvey Notes Recommendation: In the design section, page 11, the TM needs to produce something every 5 seconds, at minimum a NOOP Response: Corrected in the figure for PDR.

Pre-PDR Peer Review 23 UCB Recommendation SwPDR-22 Title : TM Allocation Table is Old Reviewer: P. Harvey Notes Recommendation: In the design section, page 11, the PF telemetry breakdown table is old. The new table is SYS- 002K Response: Corrected in the figure for PDR.

Pre-PDR Peer Review 24 UCB Recommendation SwPDR-23 Title : Flash Capacity Typo Reviewer: P. Harvey Notes Recommendation: In the design section, page 25, the capacity of the Flash is 8GB, not 32 Response: Corrected in the figure for PDR.