Professional Documents
Culture Documents
The Role of Open-Source Software: Enterprise Architecture - Chapter 6
The Role of Open-Source Software: Enterprise Architecture - Chapter 6
Open-Source Software
Enterprise Architecture | Chapter 6
The Role of Open-Source Software
Enterprise Architecture | Chapter 6
Open-Source Software
is a type of computer software in which
source code is released under a license in
which the copyright holder grants users the
rights to use, study, change, and distribute
the software to anyone and for any purpose.
Open-source software may be developed in
a collaborative public manner.
Building reputation
Most people want to work for organizations they can boast about. Adopting open source
—both the code and the practices that go with it—shows that your organization is cool.
And if you can release your own code as open source and win adoption for it, you prove
that your organization is a leader in your field, adept at the best development practices.
Code quality
You can assess this by examining the code, checking the ratings (stars) if the project is on
GitHub, looking at the number of reported bugs, and seeing what people say about the
project online. All code has errors, and you want to see that people report them, so the
presence of bug reports is a good thing —so long as the important bugs get fixed.
Active development
Has the project put out any new releases recently, or at least bug fixes? Are there many
pull requests, which indicate interest in the code?
Project maturity
How long has the project been in existence? Is there an active community? Are there a
number of people maintaining the code? Does it have funding? Are books, videos, and
other forms of education available?
Level of support
Can you get help to install and maintain the software? Is there good docu‐ mentation for
the project?
Governance/commit access
Is there a documented way for new contributors to gain commit access? If you invested
your time and expertise in contributing to the project, you will want it to support an
increase in your responsibilities.
Disaster recovery
is a term reserved for the recovery and resumption of critical technology assets in the
event of a disaster. Disaster recovery can include tasks such as resuming individual
systems or recovering all critical aspects of the IT environment. Disaster recovery is a
component of an overall BCM program.
Resumption planning
is reserved for the recovery of critical business functions separate from IT. Examples of
resumption planning include resuming call center functions, manufacturing processes or
payroll operations after a serious incident has occurred.
Contingency planning
refers to tactical solutions addressing a core resource or process. As opposed to BCM,
contingency planning is typically an isolated action and does not resemble a program or
a series of related actions. An example of contingency planning is determining how to
handle the loss of a specific vendor, or creating processes to work around the loss of a
key piece of equipment on an assembly line.
Recovery planning
is most closely related to BCM. These two terms can be used interchangeably.
Emergency response
includes the immediate actions taken to preserve lives and safeguard property and
assets. Emergency response is often a subset of a broader crisis management program.
An example of an emergency response action is an evacuation plan.
Risk assessment
identifying and prioritizing threats and failure scenarios to which the organization may
be vulnerable.
Plan documentation
documenting response, recovery and restoration procedures to enable
effective business continuity operations.
Testing
validating and continuously improving business continuity strategies and plans.
Organizations typically provide leadership to the BCM program through three roles:
Finance – The chief financial officer (CFO) or a direct report, to include risk
management or loss prevention.
• Regulatory risk
• Financial risk
• Reputation risk
Financial risk
The next risk category that drives BCM programs is financial risk.
Companies choose to mitigate financial risk by focusing on factors that
minimize financial loss and maintain market share, including:
• Responding to customer demands
• Understanding officer liability
• Minimizing single points of failure and critical external dependencies
If the company’s directors and officers can be held liable for a company’s
response to a business interruption, they are more likely to develop and
enforce an effective BCM program. Companies want to minimize the
existence of single points of failure and critical external dependencies.
For example, a company can face huge costs if it utilizes only one supplier
and that supplier is suddenly unable to provide core products or services. A
company may implement BCM solutions to make sure operations can be
resumed quickly in this case.
Key elements:
Key elements:
Analysis – Establishes the need for and standards associated with risk
assessments and business impact analyses (the cornerstones of the
planning effort). Also establishes the criteria for the type and scale of
incidents to be addressed.
Key elements:
Key elements:
Key elements:
Detectability
Will the organization have advance warning of the threat with enough
time to react, or is there a control in place to prevent or mitigate this
risk?
Velocity to impact
How quickly will downtime lead to a high-severity impact?
Documents are more than just files. They are files that are uniquely
characterized and named such that they may be unambiguously identified,
referred to, and retrieved. Consider the term “documentary evidence” as a
clue to their uniqueness and status.
The key to a successful compliance strategy is integrating the idea of compliance success
into your business-not viewing compliance as a project that can be completed and then
considered "finished." While painful, complying with regulations should be viewed as an
opportunity to improve common business processes and not just an ongoing cost to the
business.
The tools of ECM, if properly used, can help reduce the overall cost of compliance to the
business.
Collaboration is the art of working together. The key to strong collaboration is utilizing the
set of technologies-instant messaging, whiteboards, online meetings, email, etc.-that allow
work to take place wherever and whenever needed. It's good business; groups can
accomplish more than individuals
While ECM can be a costly initiative, what are the costs of not properly managing your
content? The cost of not implementing ECM tools is too often left unmeasured until too
late. Things like the cost of long legal proceedings, the loss of repeat business through the
inability to perform simple customer service interactions, and the cost of typical business
process delays are easy to measure after the fact-lawyers' time, the cost to acquire new
customers, and FTE salaries.
Many companies are seeking to deploy ECM to support a reduction of paper end-to-end.
In some industries this is expressed as a desire to become ‘paperless’. Clearly in industries
where the paper document is the information transport medium or method of interacting
with the end customer, e.g. insurance claims processing, then parallel processing of the
claim cannot occur while there is still paper in the loop. In this mode the document
interface on the front and the back end may be hardcopy, but the intermediate processing
may be entirely electronic.
Keeping a business going 24x7 is the task of business continuity planning. While often
mentioned with disaster recovery, business continuity planning is the overall strategy for
ensuring that operations continue in the event of any disruption-natural or man-made.
Disaster recovery is more Paperless or Paper-efficient Many companies are seeking to
deploy ECM to support a reduction of paper end-to-end.
1. Electronic Unstructured Data: email, instant message, text document, spreadsheet, etc.
2. Electronic Forms
3. Paper Documents/Forms
A taxonomy provides a formal structure for information, based on the individual needs of
a business. Categorization tools automate the placement of content (document images,
email, text documents, i.e., all electronic content) for future retrieval based on the
taxonomy.
An essential part of the capture process that creates metadata from scanned documents
(customer ID number, for example) so the document can be found. Indexing can be based
on keywords or fulltext.
Structured and unstructured - the core of many ECM systems. This is where the data
resides and where much of a company's investment in ECM resides. A repository can be a
sophisticated system that costs hundreds of thousands of dollars, or as simple as a file
folder system in a smaller company. The key is to have information that can be found once
it is placed in the system.
Content needs to "live" somewhere. Storage technology (optical disks, magnetic, tape,
microfilm, RAID, paper) provide options for storing content online for rapid access or near-
or off-line for content that isn't needed often.
Content Integration
As storage media ages, content must be moved to new media for continued accessibility.
Backup/Recovery
Backing up content in various formats and/or locations helps to ensure business viability
in the face of a disaster.
One of the greatest benefits of a strong ECM system is the ability to get out what you put
in. By having strong indexing, taxonomy, and repository services, locating the information
in your system should be a snap.
Syndication
Recasting content based on the needs and cultural mores of different global markets.
Personalization
Drawing on a taxonomy and based on established user preferences, various types and
subjects of content can be delivered via user-defined preferences.
Contents gets where and to whom it needs to go through a number of tools. Content can
be delivered via print, email, websites, portals, text messages, RSS feeds.
Paper Electronic
Restricts access to content, both during its creation and management as well as when
delivered.
2. Digital Signatures - ensures the identity of a document sender, and the authenticity of
the message.
3. PKI - uses a public and private key pair held by a trusted third party to transact business
over the public Internet.
Enterprise Content Management
| Enterprise Architecture
Collaboration
Known as the “other” ECM, Engineering Document Management Systems (EDMS) were
primarily conceived to fulfill the same “container management” requirements as the more
traditional office document management systems, except that they specialized in the
unique requirements of engineering users.
In the same way that DMS systems evolved to ECM, EDMS systems have also evolved over
time to manage the engineering content, not just the engineering documents.
One of the primary and most obvious differences between an ECM and an EngCM is that
the ECM is geared towards supporting unstructured information and
EngCM is geared towards structured information.
Of course, each of these types of systems may, to a greater or lesser extent, support both
unstructured and structured information, but it is their primary focus that determines the
features/functions that they support.