From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,888b7b8e9f905aec X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news1.google.com!news.maxwell.syr.edu!wns13feed!worldnet.att.net!209.244.4.230!newsfeed1.dallas1.level3.net!news.level3.com!news.binc.net!kilgallen From: Kilgallen@SpamCop.net (Larry Kilgallen) Newsgroups: comp.lang.ada Subject: Re: Joint Tactical Radio System (JTRS) Date: 10 Jul 2005 15:42:11 -0500 Organization: LJK Software Message-ID: References: <4ZZue.12291$eM6.11698@newsread3.news.atl.earthlink.net> NNTP-Posting-Host: eisner.encompasserve.org X-Trace: grandcanyon.binc.net 1121028125 27799 192.135.80.34 (10 Jul 2005 20:42:05 GMT) X-Complaints-To: abuse@binc.net NNTP-Posting-Date: Sun, 10 Jul 2005 20:42:05 +0000 (UTC) Xref: g2news1.google.com comp.lang.ada:11986 Date: 2005-07-10T15:42:11-05:00 List-Id: In article <4ZZue.12291$eM6.11698@newsread3.news.atl.earthlink.net>, Marin David Condic writes: > In doing some research into other things, I bumped into the Joint > Tactical Radio System (JTRS). This appears to be a relatively new > initiative by the DoD and from what I can gather, they seem to want to > open it up to some extent to commercial applications. > > Given that its all pretty new stuff, it looks like an opportunity for > Ada to be a player in an emerging market - or at least a big DoD > project. Does anybody know anything about the programming language(s) > being used to develop versions of this radio? It looks like it is > intended to have some sort of underlying OS and an API and then "radio > apps" can be written to go on top of this and reconfigure the unit to > different uses. > > Google turns up lots of stuff, but most of what I can find is not of a > "Tutorial" nature. (Lots of stuff written in government-programese that > talks about how wonderful its going to be one day.) since the above was posted, there has been some non-governmentese posted, but not quite favorable: <<< EISNER::DRA1:[NOTES$LIBRARY]SECURITY.NOTE;1 >>> -< SECURITY >- ================================================================================ Note 297.692 RISKS-FORUM 692 of 692 EISNER::SYS_EISNER "Encompasserve Exec. Committee" 625 lines 10-JUL-2005 13:50 -< [RISKS] Risks Digest 23.93 >- -------------------------------------------------------------------------------- RISKS-LIST: Risks-Forum Digest Sunday 10 July 2005 Volume 23 : Issue 93 ACM FORUM ON RISKS TO THE PUBLIC IN COMPUTERS AND RELATED SYSTEMS (comp.risks) Peter G. Neumann, moderator, chmn ACM Committee on Computers and Public Policy ------------------------------ Date: Fri, 8 Jul 2005 18:32:46 +0100 (BST) From: Pete Mellor Subject: Future Combat Systems procurement problems: GAO report Dawn S. Onley, GAO: Army's FCS initiative faces uncertain future, Government Computer News, 8 Jul 2005 The major communications programs that will support the Army's transformational Future Combat Systems initiative are in jeopardy of failing to meet technical challenges and an accelerated schedule, according to the Government Accountability Office. GAO found that each of the communications pillars of the Army's Future Combat Systems (FCS) program - two Joint Tactical Radio System (JTRS) clusters, the Warfighter Information Network-Tactical (WIN-T) program and the System of Systems Common Operating Environment (SOSCOE) - would likely fail to meet aggressive schedules due to immature technologies. "As currently structured, the JTRS, WIN-T and SOSCOE programs are at risk of not delivering intended capabilities when needed, particularly for the first spiral of FCS," according to GAO. "They continue to struggle to meet an ambitious set of user requirements, steep technical challenges and stringent time frames." FCS is designed to link 18 manned and unmanned weapons systems via a common computer network known as WIN-T and the System of Systems Common Operating Environment. The Army restructured its FCS program last year into spirals, with officials announcing the first spiral would happen in fiscal 2008. But GAO said the first spiral may not demonstrate key networking capabilities. GAO found the FCS program faces network, developmental and financial challenges that continue to slow progress. FCS' information network is dependent on the success of JTRS, WIN-T and SOSCOE - programs that are not included in FCS costs. "Because JTRS, WIN-T and SOSCOE all rely on significant advances in current technologies and capabilities and must be fully integrated to realize FCS, there are substantial risks to this effort," wrote Paul L. Francis, GAO's director of acquisition and sourcing management, in the report. For the full article, with a link to the original GAO report, see: http://www.gcn.com/vol1_no1/daily-updates/36302-1.html Peter Mellor, Centre for Software Reliability, City University, Northampton Square, London EC1V 0HB +44 (0)20 7040 8422 ------------------------------