Dear Abhi, What you are talking about is software tech standards, which would be limited to systems which are capable of operating these technologies/protocols. This way, you would end up leaving out a very large chunk of software which runs on very small embeded systems, who may them selves be autonomous in their operations.
Very large number of mil softwares do not run on processors which can handle these tech standards. They are designed for single small job. I was talking about quality standards by which, the design, testing, integration and everything else takes place. The software may or may not follow the tech standards mentioned by you. Your definition will disqualify almost entire mil aviation software which uses its own protocols and tech standards. Regards. Atul Asthana [EMAIL PROTECTED] 2004-03-18 21:24:33 First they ignore you, then they laugh at you, then they fight you, then you win. --Mahatma Gandhi ======= At 2004-03-18, 17:11:00 Abhi [EMAIL PROTECTED] wrote: ======= >----- Original Message ----- >From: "Arjun Asthana" <[EMAIL PROTECTED]> > >> No. Not exactly. Mil grade means the software does exactly and only what >it is suppose to do. > >*Sigh* What is an elephant really like ? - Asked the blind men (no offence >intended). > >US DoD has Defense Information Infrastructure Common Operating >Environment(DII COE) stanard in place for this purpose. DII COE is a set of >standards and guidelines that describe a "plug and play" open architecture >designed around a client/server model defined by the Defense Information >System Agency (DISA). DISA collects the requirements from the U.S. Army, the >Navy, the Air Force, and so on, and then works with the Jet Propulsion >Laboratory in Pasadena, CA, to create a platform-independent environment >called the COE Kernel. DISA distributes this code to vendors and integrators >for porting to various platforms. DISA also distributes a set of >requirements concerning features of the environment (for example, minimal >required tools for networking, system, and account management) and the >procedures to be followed in order to be certified. > >DII COE is designed to provide a common information technology architecture, >to promote interoperability, and to establish cross-platform capabilities >for the increasingly diverse US Department of Defense (DOD) operations. >These criteria include compliance with industry standards, commercial >testing, and satisfaction of DISA interoperability, security, and functional >requirements. But the Kernel Certification program has however been lately >stopped. > >Basically since most of the other countries adapted to computers etc. on a >mass sale much later than US, it made sense for them to simply adapt USA's >standards (which were already in place) regards this. Some of the standards >included in COE are POSIX (1003.1 & 1003.2), X11, Motif, CDE, TCP/IP. > >Quoting just *one* of these criterions would be plain wrong. > >Perhaps the original poster should have also mentioned "which military" ? >Answer will differ depending on that. > > > >_______________________________________________ >ilugd mailinglist -- [EMAIL PROTECTED] >http://frodo.hserus.net/mailman/listinfo/ilugd >Archives at: http://news.gmane.org/gmane.user-groups.linux.delhi >http://www.mail-archive.com/[EMAIL PROTECTED]/ = = = = = = = = = = = = = = = = = = = = _______________________________________________ ilugd mailinglist -- [EMAIL PROTECTED] http://frodo.hserus.net/mailman/listinfo/ilugd Archives at: http://news.gmane.org/gmane.user-groups.linux.delhi http://www.mail-archive.com/[EMAIL PROTECTED]/
