Interoperability via Extensible Markup Language
The Extensible Markup Language (XML) is a general-purpose specification for creating custom markup languages.[1] It is classified as an extensible language because it allows its users to define their own elements. Its primary purpose is to help information systems share structured data, particularly via the Internet,[2] and it is used both to encode documents and to serialize data. In the latter context, it is comparable with other text-based serialization languages such as JSON and YAML.[3]It started as a simplified subset of the Standard Generalized Markup Language (SGML), and is designed to be relatively human-legible. By adding semantic constraints, application languages can be implemented in XML. These include XHTML,[4] RSS, MathML, GraphML, Scalable Vector Graphics, MusicXML, and thousands of others. Moreover, XML is sometimes used as the specification language for such application languages.
XML- Wikipeida
^ TOP
Risk managment XML
Risk Management XMLThe Open Applications Group (OAGi) has announced the formation of a new RiskML Work Group to define an XML vocabulary for the definition of risk and control libraries. Formation of the RiskML WG is set against the backdrop of recent Sarbanes-Oxley legislation where "there is increased likelihood of ERP customers and Audit Firms exchanging a great deal of risk and control information. The separation of the External Audit from the Risk Assurance activity will mean that Audit firms will be exchanging risk and control information. Mapping different formats from different audit firms and different ERP solutions is inefficient, expensive and adds no value to the parties involved."
The RiskML WG will therefore create a standardized vocabulary to describe a risk and control library facilitating risk library information exchange and a standardized mechanism for publication. It will focus on the Risk and Control structure described in the COSO framework. Key deliverables include a Class Diagram, Use Case Diagram, XML Schema Definition, and corresponding documentation. New OAGIS Business Object Documents (BODs)/Nouns to be added include: Financial Statement, Process, Objective, Risk, Control, and Testing Procedure.
^ TOP
Service Oriented Architecture
Service-oriented architecture (SOA) is a methodology for systems development and integration where functionality is grouped around business processes and packaged as interoperable services. SOA also describes IT infrastructure which allows different applications to exchange data with one another as they participate in business processes. The aim is a loose coupling of services with operating systems, programming languages and other technologies which underlie applications.[1] SOA separates functions into distinct units, or services[2], which are made accessible over a network in order that they can be combined and reused in the production of business applications.[3] These services communicate with each other by passing data from one service to another, or by coordinating an activity between two or more servicesThe application platform concept
J2EE Platform
.Net Platform
^ TOP
OCIO Application Platform
The current approach is an integratioin approach to tie the OCIO applciation tools together using the standard Markup language to integrate the tools. e-CIO suggest to establish an OCIO platform based on the services oriented platform concept such as J2EE. On the OCIO automation platform, the vendors follow an established standard to provide the IT managment tools as an component on the Platform.The Mitre corporation, sponsored by the CIO council, has established the architecture tool framework
The IT managment systems which are considered as the CIO applicaiton systems can be described in the following framework develope by Mitre corporation sponsored by the CIO Council
Management oversight tools The systems oversight tools include investment management, portfolio management , risk management , security management .project management , procurement management , performance measurement and decision support
EA management tools are used to organize and manage the EA artifacts. It contain the enterprise automation environment, the business architecture, the IT standards, the architecture design and the transition plan. EA artifact repository should not make redundant effort to contain system artifact.
System development management tools are used to manage the enterprise system development artifact which include the requirements, the system documents, the meta data model and software version control and release management.
Design tools are used to generate design artifacts such graphic tool, and business process modeling tools , data modeling tools, and Computer Aid Designing (CAD) application development tools. are used. In application development paradigm, application developers relies on modeling tools. The design tools are used to model business activities, analyze business processes models, perform function decomposition and design data models, create application components and produce software code .
^ TOP
Project Managment XML
Project Management XML ^ TOPContent Managment XML
Content Managment XMLXML standards in ECM
In recent years, we have witnessed numerous initiatives from various industries and government agencies to move towards XML to describe their e-content. In fact, industry-specific XML standards for documents are being adopted worldwide. These include:
AECMA & S1000D - Aerospace
DITA - Technical documentation
DocBook - Technical documentation
Dublin Core - Metadata structure
ebXML - E-commerce
HL7 - Healthcare
NewsML - Newspaper & media
NITF - Newspaper & media
RIXML - Finance
SCORM - E-Learning
XBRL - Finance
XHTML - Web content management
XFORM - XML forms
^ TOP
OCIO Application Model
From EA aspect, IT managment tools are consider as the OCIO application system and it must be holisticly design to share application services and data resources.
^ TOP
Align OCIO Application System to Business
Align OCIO Application to business need as shown in the OCIO EA map:
^ TOP
Introduction
The IT community acquires IT managment automation systems as separate tools such as EA managment tool, change management tools, configuration managment tools, project management tool, applicaiton development tools in a stove pipe approach without recognizing that IT managment is a line of business and the IT managment tools are actually the application systems to support IT managment business as shown in the following figure:OCIO Application architecture align application to OCIO business need, establish the framework of OCIO application systems, analyz the application system internal and external connectivities, design an integrated application architecture from holistic consideration.
^ TOP
The OCIO application system framework
From the aspect of EA, IT managment tools should be considered as the IT managment applicaiton systems rather than independent IT managment tools. The OCIO Application architecture establish a holistic IT managment tool architecture design by:.Align the IT managment tools to OCIO business process,
.Catgorise The IT managment systems
.Analyz the conncectivity between differnbt IT managment applications.
.Analyz the IT management users and access control.
Management oversight tools The systems oversight tools include investment management, portfolio management , risk management , security management .project management , procurement management , performance measurement and decision support
EA management tools are used to organize and manage the EA artifacts. It contain the enterprise automation environment, the business architecture, the IT standards, the architecture design and the transition plan. EA artifact repository should not make redundant effort to contain system artifact.
System development management tools are used to manage the enterprise system development artifact which include the requirements, the system documents, the meta data model and software version control and release management.
Design tools are used to generate design artifacts such graphic tool, and business process modeling tools , data modeling tools, and Computer Aid Designing (CAD) application development tools. are used. In application development paradigm, application developers relies on modeling tools. The design tools are used to model business activities, analyze business processes models, perform function decomposition and design data models, create application components and produce software code . ^ TOP
Background
The Mitre corporation, sponsored by the CIO council, has established the architecture tool framework
The tool assessment
The IT managment systems which are considered as the CIO applicaiton systems can be described in the following framework develope by Mitre corporation sponsored by the CIO Council
Management oversight tools The systems oversight tools include investment management, portfolio management , risk management , security management .project management , procurement management , performance measurement and decision support
EA management tools are used to organize and manage the EA artifacts. It contain the enterprise automation environment, the business architecture, the IT standards, the architecture design and the transition plan. EA artifact repository should not make redundant effort to contain system artifact.
System development management tools are used to manage the enterprise system development artifact which include the requirements, the system documents, the meta data model and software version control and release management.
Design tools are used to generate design artifacts such graphic tool, and business process modeling tools , data modeling tools, and Computer Aid Designing (CAD) application development tools. are used. In application development paradigm, application developers relies on modeling tools. The design tools are used to model business activities, analyze business processes models, perform function decomposition and design data models, create application components and produce software code .
^ TOP