It's the value of information and technology assets that drive business decisions. How can the value of these assets be increased in the presence of changing standards, increasing complexity, increasing competition, and the Internet?
Processes in the Networked Economies: Portal, Vortex, and Dynamic Trading Pro...Amit Sheth
Amit Sheth, Keynote at the Software Architectures for Business Process Management (SABPM'99) Workshop at CAiSE *99, Heidelberg, June 1999.
Processes will be chief differentiating and the competitive force indoing business in the networked economy. They will be deeply integrated with the way of doing business, and that they will be
critical components of almost all types of systems supporting enterprise-level and business critical activities.
http://knoesis.org/amit
Processes Driving the Networked Economy: Process Portals, Process Vortex and ...Amit Sheth
Amit Sheth's keynote at SABPM '99: Software Architectures for Business Process Management, (Workshop at the CAiSE*99, Heidelberg, Germany, June 14-15, 2009.
http://www.informatik.uni-hamburg.de/cgi-bin/TGI/pnml/getpost?id=1999/04/1203
Related paper: http://knoesis.org/library/resource.php?id=00246
Introduction to Integration TechnologiesBizTalk360
In this presentation, Arunkumar Kumaresan highlights how the Integration Technologies have emerged over the last few years and cites few interesting examples.
Processes in the Networked Economies: Portal, Vortex, and Dynamic Trading Pro...Amit Sheth
Amit Sheth, Keynote at the Software Architectures for Business Process Management (SABPM'99) Workshop at CAiSE *99, Heidelberg, June 1999.
Processes will be chief differentiating and the competitive force indoing business in the networked economy. They will be deeply integrated with the way of doing business, and that they will be
critical components of almost all types of systems supporting enterprise-level and business critical activities.
http://knoesis.org/amit
Processes Driving the Networked Economy: Process Portals, Process Vortex and ...Amit Sheth
Amit Sheth's keynote at SABPM '99: Software Architectures for Business Process Management, (Workshop at the CAiSE*99, Heidelberg, Germany, June 14-15, 2009.
http://www.informatik.uni-hamburg.de/cgi-bin/TGI/pnml/getpost?id=1999/04/1203
Related paper: http://knoesis.org/library/resource.php?id=00246
Introduction to Integration TechnologiesBizTalk360
In this presentation, Arunkumar Kumaresan highlights how the Integration Technologies have emerged over the last few years and cites few interesting examples.
The Impact of SOA on Traditional Middleware Technologiesdigitallibrary
This presentation addresses the broad differences between traditional middleware and SOA and identifies how SOA renovates the approach to integration taken by traditional middleware technologies. Learn how to create an SOA adoption roadmap to existing customers of traditional middleware.
The document is for beginners who are going to make their careers in Middleware technologies. It will provide the information regarding implementation of integration before EAI and what were the disadvantages which are overcome by EAI.
The Eight Building Blocks of Enterprise Application ArchitectureTechAhead
Enterprises use multiple applications and sometimes they make a mess. Enterprise application architecture is a tool to bring semblance of order in this chaos
This Application Architecture presentation with voice overlay takes you through a number of fundamentals that remains relevant regardless of environment or technology.
This is the first presentation in a series that will cover each of the architectural domains and enterprise architecture to bind it all together.
Two-Tier ERP: Enabling the Future-Ready Global Enterprise with Better Innovat...Cognizant
Organizations that embrace two-tier ERP strategies are better positioned
to both navigate volatile global business conditions and acquire or divest operations that generate operational efficiency and growth.
Energy Trading and Risk Management (ETRM) solutions have now been a part of the broader wholesale energy trading application landscape for around 20-years, having evolved in step with both business and technology trends over that time period. As a result of this evolutionary process, there are a large number of diverse solutions on the market that address any number of combinations of industrial segments, energy commodities, geographic locations, and functional reach.
Architecture bridges the semantic gap between the requirements and software. The use of an architecture–centered development process for delivering information technology began with the introduction of client / server based systems.
The use of an architecture–centered development process for delivering information technology began with
the introduction of client / server based systems. Early client/server and legacy mainframe applications did not
provide the architectural flexibility needed to meet the changing business requirements of the modern
publishing organization. With the introduction of Object Oriented systems, the need for an architecture–
centered process became a critical success factor. Object reuse, layered system components, data
abstraction, web based user interfaces, CORBA, and rapid development and deployment processes all
provide economic incentives for object technologies. However, adopting the latest object oriented technology,
without an adequate understanding of how this technology fits a specific architecture, risks the creation of an
instant legacy system.
Publishing software systems must be architected in order to deal with the current and future needs of the
business organization. Managing software projects using architecture–centered methodologies must be an
intentional step in the process of deploying information systems – not an accidental by–product of the
software acquisition and integration process.
CTRM - The Next Generation - ComTechAdvisory Vendor Technical UpdateCTRM Center
There is no doubt that technology has undergone a sea-change over the last decade or so potentially making it possible to build and deploy software faster and more cost-effectively while offering a host of features that help users to work smarter, faster and with less opportunity for error. Additionally, the way that applications are designed and built has also changed to take better advantage of these technologies. While arguably there is no single technology that facilitates a paradigm shift in Commodity Trading and Risk Management (CTRM) software, when you combine advances in all areas of solution development and deployment technology, then such a leap forward is both likely and desirable.
Nowhere is the gap between the possibilities offered by these leaps in technology and what is available as commercial solutions more apparent than in the commodity trading and risk management software category. There are many aging, legacy, solutions still being utilized, marketed, and deployed and yet, this is an industry that is experiencing unprecedented demands and change, which in turn, are placing increasing demands on the software it utilizes. What most commodity firms are seeking is more agile software platforms that can allow them to adapt and evolve through these changes. This growing demand is also accentuated by the younger, more tech-savvy people entering the business whose expectations are not being met by many existing solutions.
In this White Paper we provide some insights into the differences between Live-Wireframe applications authoring and programming using traditional tools.
The Impact of SOA on Traditional Middleware Technologiesdigitallibrary
This presentation addresses the broad differences between traditional middleware and SOA and identifies how SOA renovates the approach to integration taken by traditional middleware technologies. Learn how to create an SOA adoption roadmap to existing customers of traditional middleware.
The document is for beginners who are going to make their careers in Middleware technologies. It will provide the information regarding implementation of integration before EAI and what were the disadvantages which are overcome by EAI.
The Eight Building Blocks of Enterprise Application ArchitectureTechAhead
Enterprises use multiple applications and sometimes they make a mess. Enterprise application architecture is a tool to bring semblance of order in this chaos
This Application Architecture presentation with voice overlay takes you through a number of fundamentals that remains relevant regardless of environment or technology.
This is the first presentation in a series that will cover each of the architectural domains and enterprise architecture to bind it all together.
Two-Tier ERP: Enabling the Future-Ready Global Enterprise with Better Innovat...Cognizant
Organizations that embrace two-tier ERP strategies are better positioned
to both navigate volatile global business conditions and acquire or divest operations that generate operational efficiency and growth.
Energy Trading and Risk Management (ETRM) solutions have now been a part of the broader wholesale energy trading application landscape for around 20-years, having evolved in step with both business and technology trends over that time period. As a result of this evolutionary process, there are a large number of diverse solutions on the market that address any number of combinations of industrial segments, energy commodities, geographic locations, and functional reach.
Architecture bridges the semantic gap between the requirements and software. The use of an architecture–centered development process for delivering information technology began with the introduction of client / server based systems.
The use of an architecture–centered development process for delivering information technology began with
the introduction of client / server based systems. Early client/server and legacy mainframe applications did not
provide the architectural flexibility needed to meet the changing business requirements of the modern
publishing organization. With the introduction of Object Oriented systems, the need for an architecture–
centered process became a critical success factor. Object reuse, layered system components, data
abstraction, web based user interfaces, CORBA, and rapid development and deployment processes all
provide economic incentives for object technologies. However, adopting the latest object oriented technology,
without an adequate understanding of how this technology fits a specific architecture, risks the creation of an
instant legacy system.
Publishing software systems must be architected in order to deal with the current and future needs of the
business organization. Managing software projects using architecture–centered methodologies must be an
intentional step in the process of deploying information systems – not an accidental by–product of the
software acquisition and integration process.
CTRM - The Next Generation - ComTechAdvisory Vendor Technical UpdateCTRM Center
There is no doubt that technology has undergone a sea-change over the last decade or so potentially making it possible to build and deploy software faster and more cost-effectively while offering a host of features that help users to work smarter, faster and with less opportunity for error. Additionally, the way that applications are designed and built has also changed to take better advantage of these technologies. While arguably there is no single technology that facilitates a paradigm shift in Commodity Trading and Risk Management (CTRM) software, when you combine advances in all areas of solution development and deployment technology, then such a leap forward is both likely and desirable.
Nowhere is the gap between the possibilities offered by these leaps in technology and what is available as commercial solutions more apparent than in the commodity trading and risk management software category. There are many aging, legacy, solutions still being utilized, marketed, and deployed and yet, this is an industry that is experiencing unprecedented demands and change, which in turn, are placing increasing demands on the software it utilizes. What most commodity firms are seeking is more agile software platforms that can allow them to adapt and evolve through these changes. This growing demand is also accentuated by the younger, more tech-savvy people entering the business whose expectations are not being met by many existing solutions.
In this White Paper we provide some insights into the differences between Live-Wireframe applications authoring and programming using traditional tools.
Addressing Common Misconceptions About Low-Code Platformsamogaio2023
In today’s fast-paced digital landscape, businesses constantly seek ways to innovate and streamline operations. Low-code platforms have emerged as a promising solution, offering a host of features like workflow automation, visual development and analytics reporting, among many others. These empower organizations to rapidly adapt to changing market demands and accelerate their digital transformation initiatives.
2008: "Case Study of an Enterprise System That Represents Rules Primarily as Relational Data Rather Than via Code". Published in Acta Systemica Vol. 8 No. 2 (2008) pp. 47‐54 available at http://iias.info/pdf_general/Booklisting.pdf
As the Vice President, Datacenter Architecture at Presidio, William Turner, PhD has more than 20 years of hands-on, full-project-cycle experience in strategizing, designing and deploying large-scale Fortune 500 networks and security solutions. His extensive background in banking, security,
and government has yielded several well regarded industry standards and noted reference models.
Dr. Turner envisions and drives a future in which sophisticated software provisions and de-provisions IT infrastructure automatically in response to business needs. The specialized appliances enterprises traditionally rely upon will be replaced by industry-standard hardware playing necessary roles on demand.
EAPJ conducted this interview from the perspective of an infrastructure architect considering a software-defined future for the networking, hosting and storage underlying a major upcoming application investment.
Thought Leader Interview: Dr. William Turner on the Software-Defined Future ...Iver Band
As the Vice President, Datacenter Architecture at Presidio,
William Turner, PhD has more than 20 years of hand-son,
full-project-cycle experience in strategizing, designing and
deploying large-scale Fortune 500 networks and security
solutions. His extensive background in banking, security,
and government has yielded several well regarded industry
standards and noted reference models.
Dr. Turner envisions and drives a future in which sophisticated software provisions and de-provisions IT infrastructure automatically in response to business needs. The specialized appliances enterprises traditionally rely upon will be replaced by industry-standard hardware playing necessary roles on demand.
EAPJ conducted this interview from the perspective of an infrastructure architect considering a software-defined future for the networking, hosting and storage underlying a
major upcoming application investment.
What is Application Architecture and Why Do You Need It?Lucy Zeniffer
Application architecture refers to the structured design and organization of software applications, including their components, interfaces, and data. It ensures efficient communication, scalability, and maintainability. Having a well-defined application architecture is crucial for delivering robust, high-performing, and adaptable software solutions that meet business requirements and can evolve with technological advancements.
The F5 Networks Application Services Reference Architecture (White Paper)F5 Networks
Build elastic, flexible application delivery fabrics that are ready to meet the challenges of optimizing and securing applications in a constantly evolving environment.
The F5 Networks Application Services Reference Architecture (White Paper)
System Integration is crucial for nowadays business management in evolving markets. Large companies with production chains need to make workflow as simple and as intuitive as possible. Every question has to have an easy answer.
Planning projects usually starts with tasks and milestones. The planner gathers this information from the participants – customers, engineers, subject matter experts. This information is usually arranged in the form of activities and milestones. PMBOK defines “project time management” in this manner. The activities are then sequenced according to the projects needs and mandatory dependencies.
Increasing the Probability of Project SuccessGlen Alleman
Risk Management is essential for development and production programs. Information about key cost, performance and schedule attributes are often uncertain or unknown until late in the program.
Risk issues that can be identified early in the program, which may potentially impact the program, termed Known Unknowns, can be alleviated with good risk management. -- Effective Risk Management 2nd Edition, Page 1, Edmund Conrow, American Institute of Aeronautics and Astronautics, 2003
Cost and schedule growth for complex projects is created when unrealistic technical performance expectations, unrealistic cost and schedule estimates, inadequate risk assessments, unanticipated technical issues, and poorly performed and ineffective risk management, contribute to project technical and programmatic shortfalls
From Principles to Strategies for Systems EngineeringGlen Alleman
From Principles to Strategies How to apply Principles, Practices, and Processes of Systems Engineering to solve complex technical, operational,
and organizational problems
Building a Credible Performance Measurement BaselineGlen Alleman
Establishing a credible Performance Measurement Baseline, with a risk adjusted Integrated Master Plan and Integrated Master Schedule, starts with the WBS and connects Technical Measures of progress to Earned Value
Capabilities‒Based Planning the capabilities needed to accomplish a mission or fulfill a business strategy
Only when capabilities are defined can we start with requirements elicitation
Starting with the development of a Rough Order of Magnitude (ROM) estimate of work and duration, creating the Product Roadmap and Release Plan, the Product and Sprint Backlogs, executing and statusing the Sprint, and informing the Earned Value Management Systems, using Physical Percent Complete of progress to plan.
Program Management Office Lean Software Development and Six SigmaGlen Alleman
Successfully combining a PMO, Agile, and Lean / 6 starts with understanding what benefit each paradigm brings to the table. Architecting a solution for the enterprise requires assembling a “Systems” with processes, people, and principles – all sharing the goal of business improvement.
This resource document describes the Program Governance Road map for product development, deployment, and sustainment of products and services in compliance with CMS guidance, ITIL IT management, CMMI best practices, and other guidance to assure high quality software is deployed for sustained operational success in mission critical domains.
UiPath Test Automation using UiPath Test Suite series, part 4DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 4. In this session, we will cover Test Manager overview along with SAP heatmap.
The UiPath Test Manager overview with SAP heatmap webinar offers a concise yet comprehensive exploration of the role of a Test Manager within SAP environments, coupled with the utilization of heatmaps for effective testing strategies.
Participants will gain insights into the responsibilities, challenges, and best practices associated with test management in SAP projects. Additionally, the webinar delves into the significance of heatmaps as a visual aid for identifying testing priorities, areas of risk, and resource allocation within SAP landscapes. Through this session, attendees can expect to enhance their understanding of test management principles while learning practical approaches to optimize testing processes in SAP environments using heatmap visualization techniques
What will you get from this session?
1. Insights into SAP testing best practices
2. Heatmap utilization for testing
3. Optimization of testing processes
4. Demo
Topics covered:
Execution from the test manager
Orchestrator execution result
Defect reporting
SAP heatmap example with demo
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
SAP Sapphire 2024 - ASUG301 building better apps with SAP Fiori.pdfPeter Spielvogel
Building better applications for business users with SAP Fiori.
• What is SAP Fiori and why it matters to you
• How a better user experience drives measurable business benefits
• How to get started with SAP Fiori today
• How SAP Fiori elements accelerates application development
• How SAP Build Code includes SAP Fiori tools and other generative artificial intelligence capabilities
• How SAP Fiori paves the way for using AI in SAP apps
A tale of scale & speed: How the US Navy is enabling software delivery from l...sonjaschweigert1
Rapid and secure feature delivery is a goal across every application team and every branch of the DoD. The Navy’s DevSecOps platform, Party Barge, has achieved:
- Reduction in onboarding time from 5 weeks to 1 day
- Improved developer experience and productivity through actionable findings and reduction of false positives
- Maintenance of superior security standards and inherent policy enforcement with Authorization to Operate (ATO)
Development teams can ship efficiently and ensure applications are cyber ready for Navy Authorizing Officials (AOs). In this webinar, Sigma Defense and Anchore will give attendees a look behind the scenes and demo secure pipeline automation and security artifacts that speed up application ATO and time to production.
We will cover:
- How to remove silos in DevSecOps
- How to build efficient development pipeline roles and component templates
- How to deliver security artifacts that matter for ATO’s (SBOMs, vulnerability reports, and policy evidence)
- How to streamline operations with automated policy checks on container images
Alt. GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using ...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Pushing the limits of ePRTC: 100ns holdover for 100 daysAdtran
At WSTS 2024, Alon Stern explored the topic of parametric holdover and explained how recent research findings can be implemented in real-world PNT networks to achieve 100 nanoseconds of accuracy for up to 100 days.
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
Removing Uninteresting Bytes in Software FuzzingAftab Hussain
Imagine a world where software fuzzing, the process of mutating bytes in test seeds to uncover hidden and erroneous program behaviors, becomes faster and more effective. A lot depends on the initial seeds, which can significantly dictate the trajectory of a fuzzing campaign, particularly in terms of how long it takes to uncover interesting behaviour in your code. We introduce DIAR, a technique designed to speedup fuzzing campaigns by pinpointing and eliminating those uninteresting bytes in the seeds. Picture this: instead of wasting valuable resources on meaningless mutations in large, bloated seeds, DIAR removes the unnecessary bytes, streamlining the entire process.
In this work, we equipped AFL, a popular fuzzer, with DIAR and examined two critical Linux libraries -- Libxml's xmllint, a tool for parsing xml documents, and Binutil's readelf, an essential debugging and security analysis command-line tool used to display detailed information about ELF (Executable and Linkable Format). Our preliminary results show that AFL+DIAR does not only discover new paths more quickly but also achieves higher coverage overall. This work thus showcases how starting with lean and optimized seeds can lead to faster, more comprehensive fuzzing campaigns -- and DIAR helps you find such seeds.
- These are slides of the talk given at IEEE International Conference on Software Testing Verification and Validation Workshop, ICSTW 2022.
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024Albert Hoitingh
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.
In his public lecture, Christian Timmerer provides insights into the fascinating history of video streaming, starting from its humble beginnings before YouTube to the groundbreaking technologies that now dominate platforms like Netflix and ORF ON. Timmerer also presents provocative contributions of his own that have significantly influenced the industry. He concludes by looking at future challenges and invites the audience to join in a discussion.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
FIDO Alliance Osaka Seminar: Passkeys at Amazon.pdf
Components of CORBA
1. Reprint from
newspaper techniques, July/August 2000
The monthly
publication
of Ifra
English edition
07-08/00 D20835E
In the July/August 2000 edition of “newspaper techniques”,
the cover story was dedicated to “Building a powerful
publishing platform.” One of the articles published was
entitled “Components, CORBA, EAI – keys to a complete
publishing system?” The article was an edited version of a
comprehensive report prepared by: Glen B. Alleman, Niwot
Ridge Consulting (www.niwotridge.com) an associate of Nilan
Sanders Associates (www.nilan-sanders.com) for System
Integrators Inc. (www.sii.com). For more on the report,
contact Alleman via e-mail: galleman@niwotridge.com.
2. Cover Story
18
comes, unpredictability, and the ability to
lock a market. Adapting software to today's
ever-shifting economy requires the same
processes as adapting a business: flexibility
and the ability to operate in the presence of
chaos. This environment requires adapt-
ability moreso than optimisation. Adapt-
ability means agility, flexibility, incremen-
talism, rapid development, interfaces that
are not formally defined, chaotic business
and product environments, managing the
state of the business rather than the flow of
the business. Believers in component soft-
ware say these systems provide the tools
and architecture to meet these require-
ments, and that traditional software tools
and architecture do not.
There are a lot of terms here, EAI,
CORBA, components, so here is a brief ex-
planation of how they each work together.
We will go into greater detail later. A com-
ponent-based system is composed of ob-
jects that interact through a standard inter-
face protocol. The connections between the
applications of this system are mediated by
CORBA (Common Object Request Broker
Architecture) in a platform- and program-
ming language-independent manner. EAI
(Enterprise Application Integration) is the
overarching concept of deploying these
components, where CORBA is the enabling
technology, forming one of the foundations
Nowadays we are seeing a num-
ber of technologies emerging in
the construction of software for
the publishing industry. One tech-
nology that is gaining interest
from the publishing world is the
use of component technologies,
with CORBA and EAI as the means
of assembling these components
into a complete system. This a
summary of a presentation given
at a recent IPTC meeting.
It's the value of information and
technology assets that drives business deci-
sions. How can the value of these assets be
increased in the presence of changing stan-
dards, increasing complexity, increasing
competition, and the Internet? One answer
is the better use of commercial off-the-
shelf components and reuse of these com-
ponents once they have been integrated
into a system. The Internet age has brought
change to nearly every industry that uses
software. In publishing the Internet means
multiple media, new standards, and new
architectures for the underlying systems.
The economics of the Internet Age
mean an increasing returns business strate-
gy, instability of markets, multiple out-
for the component technology used to im-
plement EAI.
Why component-based systems?
Why are CORBA component-based
systems different and better than tradition-
al integrated systems? How can the user
understand the differences and make an in-
formed decision about the technology
strategies needed to move into the next
generation of publishing systems?
In the traditional approach to assem-
bling a system from components, the indi-
vidual API's (Application Programmable
Interface), data formats, protocols, lan-
guages, operating systems, and application
locales create many barriers to the “seam-
less" construction of the system. Once these
connections have been made, any changes
in any component in the system will have
some impact on other components.
In the past, these brick walls have
been overcome with brute force, either
through the efforts of programming or the
use of intermediate database or format
translation software. This approach usually
resulted in client-server architectures that
were “fixed" in their construction, just like
the brick wall. With the introduction of
“middleware" interface, locality, program-
ming languages and operating systems is-
sues become the responsibility of CORBA.
Using component technologies, the appli-
cation domain and the services domain can
be connected with very little impact on the
other domains. This is done through COR-
BA’s standard distributed object architec-
tures.
Ins and outs of CORBA?
CORBA has several advantages, and
some disadvantages, over the alternatives.
It provides the services for fault tolerance,
scaling, quality of service, replication, and
its proponents say the technology enables:
> best of breed application components
to interoperate;
> distributed heterogeneous systems in-
tegration to take place in a transparent
manner;
Building a powerful publishing platform
Components, CORBA, EAI – keys
to a complete publishing system?
July/August 2000 newspaper techniques
Left: In the traditional approach to assembling a system from components, the connections between the various
data formats, protocols, languages, operating systems, etc., created many barriers or “brick walls” to the seam-
less construction of the system. Right: By using CORBA, when changes are made to these different objects in the
system, there is very little impact on each object.
3. 19
> legacy system integration strategies
to be implemented in the same manner as
new development;
> rapid development strategies using
standard interfaces;
> Internet-based strategies using Java;
> and platform- and language-inde-
pendent strategies.
These features come with a price, like
anything worthwhile, but they are provided
in a standard package. The price is the
technical competence and skills needed to
assemble the system into a product. In the
current business environment these skills
are in short supply.
How EAI applies?
In the publishing world the content
of the publication is usually located in a
variety of systems. Proponents of a compo-
nent-based system say the days of a single
monolithic system that does everything for
everyone are gone. Today's systems are in
fact systems of applications, each with a
special capability. The users of this system
want each of these specialised systems to
work together seamlessly without requiring
any changes to the underlying data or
processes in each domain.
Like we said before, EAI is the over-
arching concept of deploying components.
A more specific definition of EAI is “the in-
tegration of applications across the enter-
prise in a rational and centralised manner."
The transparent interoperation of commer-
cial off the shelf (COTS) products is what
distinguishes an EAI solution from the tra-
ditional integrated solution. As we said,
CORBA forms one of the foundations for
the component technology used to imple-
ment EAI, but EAI results in a seamless
integration of a variety of system appli-
cations to form a meta system. There are
others of course, but in the publishing
world EAI is an emerging concept. With
the introduction of ERP systems, the con-
nection between content creation and pub-
lishing and the business side of this process
can be made.
Demands of the market
should drive technology
Many of today's technology decisions
are driven by the market, not the vendor.
The Internet, CORBA, communications net-
works, programming languages, databases,
system architectures, are all defined to the
business needs of
the user. Adapting
to these standards
requires an archi-
tectural vision, not
just a product plan.
This vision must in-
clude the evolving
standards as well as
the evolving com-
ponent technologies
provided by exter-
nal suppliers. Build-
ing “purpose built"
applications moves
away from this vi-
sion and must be
considered careful-
ly.
We've heard it
all before: Change is
constant. Change is
disruptive. Change
is the engine that
drives innovation,
market share, prod-
uct displacement,
product obsoles-
cence. In order to survive in the presence of
change, the underlying system architecture
must not only support change but also
must thrive on change – that is, the cost of
change is not related to the size or com-
plexity of the application domain, but is a
function of the change. This is a linear
change cost model, rather than a non-lin-
ear (exponential or greater) models found
in API-based implementations.
The traditional processes of analysis,
design, development, and deployment have
difficulty dealing with rapid change, adap-
tive markets, and changing market require-
ments. Component-based systems provide
the means to develop products in the pres-
ence of these forces.
Out of the box
In order to design, develop and de-
ploy component-based systems, new skills
are needed. These include Object-Oriented
analysis and design, formal system archi-
tecture, understandings of fault tolerance,
scaling, and n-tier distributed processing.
These skills are the foundation of the Inter-
net. Searching for a product and vendor
with these skills is a critical success factor
in the acquisition of any modern system.
The alternatives to component-based
systems can be found in the market place.
They include traditional client-server based
systems, best-of-breed applications con-
nected to centralised databases, and tightly
integrated applications using programmatic
interfaces. Opponents say these fail to ad-
dress the fundamental issues with modern
software systems such as adaptive configu-
rations, isolation of functions, layering of
components, heterogeneous integration
strategies, and standards for integration.
As usual, change along these lines in
the publishing world is coming somewhat
late compared to other businesses. This is
an advantage that can be used to avoid
many of the past difficulties.
CORBA factors
The following are some critical suc-
cess factors to consider when thinking of
CORBA:
1) Adaptive platforms: Unix and NT
dominate here, but there are multiple
flavours of Unix as well as databases, and
there is always the Mac.
2) Agile application selection: the best
of breed list changes with every generation
of product. >
newspaper techniques July/August 2000 Cover Story
Here’s a simple picture of the business processes involved in publishing a news-
paper. The content creation and management within each domain can be provided
by a best of breed application. The connectivity between the domains is provided
through a layered set of objects which reside in a central clearing house. The state
and status of the content in each domain is communicated to other domains using
this meta object. The content remains in the application domain until it is assem-
bled on the published page for output.
4. Cover Story
20
3) Scalable resources: scalable in terms
of performance, capacity, users, locations.
4) Robust (fault tolerant) architectures:
Tandem-like behaviours are the bench-
mark.
5) Natural transition to the Internet:
CORBA and Java are “the natural path to
the net," anything less will become an “In-
stant Legacy" system.
These critical success factors could
be applied to any system integration archi-
tecture. So what makes CORBA unique
here? Proponents say CORBA provides
these in one package, external from the
business applications.
It provides them through a set of
standard interfaces, a standard processing
model, and a standard set of platforms and
programming languages.
Media companies using CORBA
A number of media companies have
used CORBA in their various workflows.
Here are a few.
CNN.com, a division of Cable News
Network that is responsible for non-broad-
cast dissemination of news for CNN and
provides content to more than 150 co-
branded sites, realised several benefits
through CORBA.
The company has been able to: build
both the clients and servers simultaneously,
while connecting them quickly and seam-
lessly, using IDL (Interface Definition Lan-
guage); shorten its development cycle
through Object Reuse and save time and
money by minimising the debugging of
integrated software.
deutsche presse agentur (dpa), the
press agency based in Germany that pro-
vides multimedia information facilities for
its correspondents and customers, created
true multi-media operations with the
help of CORBA and integrated new pro-
duction systems with legacy libraries and
workstations.
Britain's independent broadcasting
company sky.com says its associated or-
ganisations “are building more powerful
web-based solutions to deliver content.
To build these applications, developers
need to knit together their existing IT
infrastructure with the latest web tech-
nologies."
Newspapers are sure to get in on the
mix, but which path they choose is any-
one’s guess. <
July/August 2000 newspaper techniques
> newspaper techniques
is the Ifra membership magazine. It is
published monthly in English, French
and German.
Managing Director: Günther Böttcher
Managing Editor: Klaus von Prümmer
Editor, newspaper techniques: Dean
Roper. Deputy: Brian Veseling.
Editor, zeitungstechnik:
Michael Spinner-Just.
Deputy: Charlotte Janischewski.
Editor, techniques de presse:
Valérie Arnould (Paris).
Assistant Editor: Damienne Gallion.
Deputy: Sylvie Bier.
Translators: Birgit Becker, Sylvie Bier,
Paul Callaghan, Solange Domisse,
Regina Hansen, Katia Mandonnet.
Layout and production: Gordon
Steiger, Günter Raschke, Stephan
Leiß, Christiane Krumb.
No responsibility can be assumed for
unsolicited manuscripts. Signed contri-
butions do not necessarily express the
opinion of the editor.
e-mail news: editor@ifra.com
Director of Marketing and EXPO:
Jamie Davies.
Advertising Manager:
Bettina Damnig.
Advertising rates and general terms
and conditions published in Media
Information 2000 are applicable.
e-mail advertising: ads@ifra.com
Address: Ifra, Washingtonplatz 1,
64287 Darmstadt, Germany
Telephone +49 (6151) 733-6
Telefax +49 (6151) 733-800
Copyright: Republishing permitted with
acknowledgement of origin only.
Printed in Germany.
Ifra, the world’s
leading association
for newspaper and
media technology