|
| |
| Flash | |
|
| |
| Ext Links - agiledata.org entArc - ent-arc.info entArc - software.org entArc - gcn.com entArc - Unified EA - cio.state.nm.us | |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
| |||||||||||||
 Main topic: network-centric warfare. The ASD(NII) as the CIO for DoD is charged with ultimate responsibility for the GIG. His authority extends to all phases of the GIG design. The DISA has been charged by the CIO with heading the GIG project. DISA has classified the GIG as a data computing grid and designed an intricate foundation architecture called GIG Enterprise Services (ES). GIG ES establishes a collection of core services that provides the foundation for lower-level GIG components all the way down to the individual soldier. GIG ES enables distributed storage, information assurance (security), collaboration, messaging, mediation, service management, and interfaces for node to client connectivity. As of 2004, there are nine functional GIG ES core services. These are: Storage, Messaging, Enterprise Service Management, Discovery, Mediation, Information Assurance, Application Hosting, User Assistant, Collaboration. The 2002 DoD Directive effectively redesignates all existing networks, technology services, and data applications within the Department as part of the GIG. Agencies have evolved independent efforts to bring their services into compliance with GIG ES architecture. One such infrastructure to join the GIG is the NMCI network.See also:
Service-Oriented Architecture The nodes in a SOA environment, make resources available to other participants in the network as independent services that the participants access in a standardized way. Most definitions of SOA identify the use of Web services (i.e. using SOAP or REST) in its implementation. However, one can implement SOA using any service-based technology. The OASIS SOA Reference Model Technical Committee is working on defining SOA independent of any specific technologies. Unlike traditional point-to-point architectures, SOAs comprise loosely coupled, highly interoperable application services. These services interoperate based on a formal definition independent of the underlying platform and programming language (e.g., WSDL) . The interface definition encapsulates (hides) the vendor and language-specific implementation. A SOA is independent of development technology (such as Java and .NET). The software components become very reusable because the interface is defined in a standards-compliant manner. So, for example, a C# (C Sharp) service could be used by a Java application. SOA provides a methodology and framework for documenting enterprise capabilities and can support integration and consolidation activities. High-level languages such as BPEL or WS-Coordination take the service concept one step further by providing a method of defining and supporting workflows and business processes. SOA design and development: The modeling and design methodology for SOA applications has become known by the terms service-oriented analysis and design and SODA. The SOA functions as much as a software development framework as it does as a delivery framework. In order for a SOA environment to operate successfully, software developers need to orient themselves to its mindset of creating common services which clients or middleware then orchestrate to implement processes. Development of systems using the SOA requires a commitment to this model in terms of planning, tools, and infrastructure. When most people speak of a service-oriented architecture, they speak of a set of services residing on the Internet or an intranet using "Web services." A set of standards exists which generally feature in all discussions of Web services. These standards include XML , HTTP (or HTTPS), SOAP, WSDL, UDDIIn general, SOA is behind the scenes, not visible to the users. SOA is fronted by a client UI, and end users only see the Client UI. In other words, there is no SOA without clients using it. As such, SOA is an enabling technology, behind the scenes, waiting to be used. See Client/SOA for a discussion of one such architecture. See also:
External links:
Articles
ITtoolbox Blogs: *Is SOA Right For You?
| |||||||||||||
