1 / 11

NATO Armaments Support Services User Training

NATO Armaments Support Services User Training. Closing Release 4.0 September 2008. Agenda. Introduction Overview Development Environment SCPP Configuration Packages Autotest Closing. Presentation Structure. Operational Processor Issues Change Control National Usage

tom
Download Presentation

NATO Armaments Support Services User Training

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. NATO Armaments Support Services User Training Closing Release 4.0 September 2008 Releasable for Internet Transmission NATO/PfP UNCLASSIFIED

  2. Agenda • Introduction • Overview • Development Environment • SCPP • Configuration • Packages • Autotest • Closing Releasable for Internet Transmission NATO/PfP UNCLASSIFIED

  3. Presentation Structure • Operational Processor Issues • Change Control • National Usage • Summary of Key Points • Points of Contact Releasable for Internet Transmission NATO/PfP UNCLASSIFIED

  4. Operational Processor Issues (1) • Between each major release three interim versions of NASS are available for integration with the other kernels in the suite. This way, any issue with code compatibility can be captured early in the process. • In each major release of the NASS, certain features and/or capabilities of the code may be “deprecated” (marked as obsolete) • “Deprecated” features will be kept in the code for two major versions of the NASS and then deleted. Avoid using “Deprecated” features of the NASS Releasable for Internet Transmission NATO/PfP UNCLASSIFIED

  5. Operational Processor Issues (2) • Use the Source Code Pre-Processor (SCPP) on the NASS released code to strip out all “-- @Rx.y@” tagged code • This will avoid accidental use by the developers of your new OPr Avoiding the use of already deprecated code will reduce future maintenance costs Releasable for Internet Transmission NATO/PfP UNCLASSIFIED

  6. Operational Processor Issues (3) • Use the Source Code Pre-Processor (SCPP) on the NASS released code to strip out “-- @Rx.y@” tagged code • This will help understand the dependencies on obsolete code in your OPr • Do this in two passes to understand changes that have to be addressed by the next release and what can wait Structure necessary OPr updates with other planned modifications to reduce impact. Releasable for Internet Transmission NATO/PfP UNCLASSIFIED

  7. Change Control – PR/CR • Requirements, Change Request (CR) • a new capability or modify an existing capability; generally generated by NASS users • Bugs, Problem Report (PR) • reports a problem with the behavior of the NASS software; usually found by NASS testers and users • NASS CRs and PRs are kept in a ClearQuest Web database Releasable for Internet Transmission NATO/PfP UNCLASSIFIED

  8. Change Control - Submitting • Change Control Database (CQ Web) • Facilitated by CAN • NASS Project controlled by SWE • SWE will Accept or Reject the PR/CR • Any S4 member country can submit a CR or PR • In the submitted record, please provide: • Detailed description of change/problem/issue • Support for future analysis • It is helpful to provide the following additional information, if relevant: • NASS Configuration/Ada Compiler information • Test Case(s) that failed Releasable for Internet Transmission NATO/PfP UNCLASSIFIED

  9. National Usage - Testing • Your usage of NASS may not match the scenarios explored during Canada’s Acceptance Testing of NASS Plan for National acceptance testing of NASS in your operational environment. Releasable for Internet Transmission NATO/PfP UNCLASSIFIED

  10. Summary of Key Points • Read the NASS SRS to understand the capabilities of the NASS • Read the IDIUG and Ada specifications for details on NASS usage • Read the NASS Audit Reports for details on the results of the independent evaluation of the NASS (code quality, software safety, etc.) • Monitor NASS Status Reports for information progress/issues • Test your configuration of the NASS • Report problems to the NASS product leader • Attend S4 Reviews [Program and Software Development] (or read the minutes of the S4 Reviews) to monitor the progress of the NASS program Releasable for Internet Transmission NATO/PfP UNCLASSIFIED

  11. Points of Contact • NASS Product Lead • Erik Larsson (SWE)(erik.larsson@fmv.se) • NASS Development Lead • Robert Gustavsson (SWE) (robert.gustavsson@baesystems.se) • NASS Quality Lead • Paul Makepeace (CAN)(makepeace@lsec.dnd.ca) Releasable for Internet Transmission NATO/PfP UNCLASSIFIED

More Related