The focus of the Interior Enterprise Architecture is on
providing guidance for information technology (IT) issues and initiatives that
are Interior-wide or multi-bureau in scope.
The Applications Development and Acquisition architecture defines system
development and acquisition of (commercial-off-the-shelf/government-off-the-shelf
(COTS/GOTS)) lifecycle techniques for the enterprise.
Like most large public and private enterprises, the
Department of Interior relies heavily on computer applications to support its
business operations. Because Interior’s business processes change dynamically
in response to both legislation and new demands from citizens, it is important
that Interior’s computer applications also be able to change rapidly.
This existing inventory of “legacy” applications reflects
the tools available at the time the applications were developed or deployed and
how projects were funded and managed. In addition, many applications were
designed or procured to perform a specific operation for a specific agency on a
specific hardware platform. These legacy
applications were deployed without consideration to Interior as an Enterprise
and frequently were operated independently by the Bureaus. The ability to communicate with other
applications or systems across Interior or to adapt to changes in the business
processes was not typically a consideration.
Recently, Enterprise Application Integration tools and
technology has begun to evolve to help address these problems. A number of
options now exist to meet business needs and deliver information to people when
and where they need it.
If used correctly, the Interior Enterprise Architecture will
act as a catalyst for those looking to capitalize on its contents and better
understand the full meaning of its guidance. This understanding will permit IT
personnel to better engage the non-IT organization in discussions around
tradeoffs and priorities within the proper governance structure (e.g.,
Management Initiatives Team (MIT), Information Technology Management Council
(ITMC)). The Interior Enterprise Architecture is not intended to be the “last
word” (e.g., some automated checklist for product selection). It is intended to
be one of the “first words” to assure that Interior’s mission priorities and
its IT priorities remain closely aligned.
Because Interior is incorporating the OMB’s Federal
Enterprise Architecture (FEA) models, the technical guidance provided by the
subject area experts within a domain spans both the Service Component Reference
Model (SRM) as well as the Technical Reference Model (TRM). For the Application
Development and Acquisition domain, the SRM elements are as follows:
Service
Domain(s): The Back Office Services
Domain defines the set of capabilities that support the management of
enterprise planning and transactional-based functions.
Service
Type(s): Data Management -
defines the set of capabilities that support the usage, processing and general
administration of unstructured information.
Development and Integration -
defines the set of capabilities that support the communication between
hardware/software applications and the activities associated with deployment of
software applications.
Component(s): Data Exchange – defines the set of
capabilities that support the interchange of information between multiple
systems or applications.
Data Integration - defines the set
of capabilities that support the organization of data from separate data
sources into a single source using middleware or application integration as
well as the modification of system data models to capture new information
within a single system.
Legacy Integration – defines the
set of capabilities that support the communication between newer generation
hardware/software applications and the previous, major generation of
hardware/software applications.
Instrumentation and Testing –
defines the set of capabilities that support the validation of application or
system capabilities and requirements.
Software Development –defines the
set of capabilities that support the creation of both
graphical and process application or system software.
These SRM service elements are likewise supported by
Interior’s IT (technical) infrastructure (e.g., servers, networks). Within this
infrastructure are individual TRM components for which this domain team is
providing guidance. The graphic below outlines those TRM elements for this
domain that support the service needs of the SRM.
Additionally, it’s doubtful that a single domain chapter
from the TRM can be used to address a substantive issue. More realistically, a few architecture domains
may need to be reviewed when addressing an important IT decision. For example, if Interior was considering the
creation of a new Interior-wide Web application that could be used both by the
general public and Interior personnel, then the TRM chapters like Data
Management Technologies, Information Security, Distributed Systems Management
and Application Development might all need to be reviewed.
The
principles listed below provide guidance for the design and selection of
technology components that will support the application development needs of
Interior-wide IT initiatives.
|
|
|
|
Information is
valued as an Interior asset to accelerate decision-making, improve
management, and increase accountability to our stakeholders (e.g., citizens).
Rationale:
- Information is the foundation of a citizen-centric government.
- The value of information is not realized if it is held in isolated
pockets.
- Information must be shared to maximize effective decision-making
across lines of business and with partners.
- Information is necessary for decision making to support
accelerated business process cycles.
- Increased access leads to improved integrity and relevance of
data.
Implications:
- Supporting policies regarding security, privacy, confidentiality,
information sharing, information integrity, utility and data relevance
must be developed and implemented.
- Need to promote interoperable information management, such as data
warehouses and data access methods that facilitate information
availability.
- Data warehouses, metadata and data access methods may need to be
developed to facilitate information availability.
- Information needs to be structured for easy access and management,
timely availability, and use.
- Metadata (information about the data, such as source, units of
measurement, and collection methods) will need to be developed and made
available.
- To transport and share information, common operational rules are
necessary.
- Need to recognize that the “visual
identity” or “branding” of the Interior-wide web experience itself is an
information asset.
|
|
|
|
|
|
|
|
Applications must be designed to create, store, access and
present data meaningfully.
Rationale:
- Reduces
cost through code reuse and greater scalability of applications.
- Enhances
data value by promoting reuse, thereby avoiding bad data.
- Leads
to greater data consistency.
- Increased
access leads to improved integrity and relevance of data
- Reduces
unnecessary data redundancy.
Implications:
- Optimize application performance for the
environment in which the application will run.
- Require a common, reusable data access
method that promotes interoperability.
- Provide proper application program
interfaces (APIs) to the data.
- Analyze business functions from an
enterprise perspective.
- Standardize data definitions and business
rules.
- Create and maintain an active data
dictionary.
- Design and develop applications in
compliance with federal legislation and policies to assure appropriate
information availability, sharing, integrity, and utility.
- Document applications at all levels of the
system lifecycle and store in a repository and include version control.
|
|
|
|
|
|
|
|
Systems must be designed, acquired, developed, or enhanced
such that data and processes can be effectively shared, for appropriate
purposes, across Interior and with our partners.
Rationale:
- Better
serves our customers (e.g., the public, employees, etc.) through increased
efficiency.
- Reduces
costs by eliminating duplicate systems or processes.
- Ensures
more consistent information by reducing multiple sources of data.
- Supports
better decision-making and accountability through shared data and
processes.
Implications:
- Design
systems that allow future repartitioning to avoid difficult data
management, inefficient processes and to mirror changing business
processes.
2.
Plan for modularity in application functionality and
design.
- Design
for platform independence.
- Consider
enterprise wide impacts when designing enhancing, acquiring COTS/GOTS or
extending the scope or use of applications.
5.
Research and acquire new tools that enable data sharing
and provide training for their proper use.
- Utilize
a methodology to determine the appropriate balance between data and
process integration and interoperability.
- Implement
common data standards and consistent data management processes across
Interior.
|
|
|
|
|
|
|
|
Requirements must be thoroughly defined to determine
whether it is best to reuse, buy COTS/GOTS or build an application system.
Rationale:
·
Choosing the right approach,
based on clearly defined requirements, can save time and cost over the
lifecycle of the application system.
Implications:
- Balance the costs of providing
interoperability and customization as part of the total cost of
ownership in selecting application solutions.
- Do not select technical solutions before
fully understanding functional and technical requirements.
- Take the entire application architecture
into consideration during the selection process.
- Identify and maintain “reusable”
components.
- Good system specifications will be needed
early in the planning cycle to evaluate alternatives.
- Consider technology trends and technology
market direction.
- Select application tools that satisfy
requirements; do not select tools solely based on current skills.
- Involve all stakeholders in the definition
of systems requirements.
|
|
|
|
Principle 5: Ensure Security,
Integrity, Confidentiality and Privacy
|
|
|
IT systems should be designed and implemented in accordance
with security, integrity, confidentiality and privacy legislation and
policies to assure appropriate information availability.
Rationale:
·
Helps safeguard confidential
and proprietary information.
·
Enhances public trust.
·
Enhances the proper
stewardship over information.
·
Enhances the integrity of the
information.
·
Complies with the Computer
Security Act, the Privacy Act of 1974, and OMB Circular A-130 “Management of
Federal Information Resources.”
Implications:
- Train designers, developers, analysts and
operational personnel so they understand security, confidentiality and
privacy requirements.
- Identify, publish and keep the applicable
policies and attendant interpretations current.
- Interior may
need to develop classification schemes for information security.
|
|
|
|
|
|
|
|
Applications must be developed to provide easy and timely
access to data and information without security and privacy being
compromised.
Rationale:
- Productivity,
decision-making, and customer service are benefits from easy, direct,
and timely availability of information.
- Provide
employees and the public with efficient, effective, and economical
access to Government information in accordance with the Paperwork
Reduction Act (PRA, PL 104-13).
- Enable
information to be attainable in the appropriate place, time, format and
context.
·
Develop, acquire and use information
technology that is accessible to individuals with disabilities in accordance
with the Rehabilitation Act of 1998.
·
Make records
that are frequently requested under the FOIA available for public
inspection. Further, records created
on or after November 1, 1996 must be available via the Internet or other
electronic means.
·
Incorporate
privacy protections required by the Government Paperwork Elimination Act when
developing electronic processes.
·
Beyond the
legal requirements, easy and timely access to data and information makes
sound business sense.
Implications:
- Present
data in compliance with applicable data access statutes, regulations,
business, legal mandates, and public policy.
- Presumes
the right to know for unclassified information unless policy or law specify otherwise; however, for information like
“pre-decisional information”, access would still be controlled.
- Establish
the business necessity of sharing information.
- Deploy
technology to distribute and allow access to information.
- Clearly
state the classification of information and define the classification
rules well.
- Do
not permit sensitive information to be accidentally released.
- Provide
a variety of public and private access methods for public information in
accordance with E-FOIA.
- Make
information available in formats accessible to those with sensory
disabilities in accordance with Section 508.
9. Clearly
state the designation of data sensitivity.
|
|
|
|
|
|
|
Application development should adhere to industry
standards and open architecture.
Rationale:
- Systems are more likely
to be interoperable.
- Lessens the chance that
applications become technically obsolete.
- Lengthens the life of
applications and reduces overall cost.
- Allows flexibility and
adaptability in product enhancement, extensibility, and replacement.
- Reduces dependency on a
single vendor; i.e., vendor lock-in.
Implications:
- Develop an effective
management process to identify and assess industry standards and share
information across Interior.
- Promote participation in
the development of open standards.
- Establish and maintain a
mechanism to coordinate Interior participation in standards bodies.
- Provide training and
education to promote the use of open standards.
|
|
|
|
|
|
|
|
Use
industry standard Systems Life Cycle processes to accommodate multiple methodologies
and technologies.
Rationale:
- Reduces costs by creating
a common set of repeatable processes.
- Leads to a common set of
documentation that facilitates reuse, maintenance and reengineering.
- Spells out best
practices.
- Provides a flexible
framework for application development.
- Reduces maintenance and
reprogramming costs over the long term.
- Increases the likelihood
that stakeholders will deem an application a success.
Implications:
- Understand the
relationship between SDLC process and outputs and the full system
lifecycle.
- May extend the initial
phases of software development lifecycle, although the overall SDLC may
be shorter.
- Provide SDLC Methodology
training and education.
- Choose the appropriate
methodology for the scope of the system.
- SDLC includes
traceability of requirements from business requirements to technical
specifications to test cases.
|
|
|
|
|
|
Data and information must be managed and maintained as a
stewardship responsibility to support the mission of Interior.
Rationale:
- Since
information is an asset, it needs to be actively managed which is the
goal of a stewardship program.
- Data
is a resource important to the accomplishment of Interior’s work. In its broadest sense, it is
information including items like electronic and paper records, emails,
film, etc. Like natural
resources, information needs stewards who are responsible for its
valuation, preservation, security, access and utilization across Interior
and with the public.
- Stewardship
program will support common business rules, which would facilitate
information sharing and improve data integrity.
- Without
stewardship, data can lose its value.
- Without
stewardship, information may cause confusion and result in harm to the
department (e.g., litigation.)
Implications:
- Recognition
that business area personnel need to be responsible for stewardship of
the data (with the support of IT) and the commitment of the resources
necessary to make stewardship happen.
- Need
to recognize that stewardship includes things like:
·
Understanding of customer needs for the
information;
·
Understanding the entire “life cycle” of the
data (e.g., currency, obsolescence;)
·
Responsibility for clarification of the data’s
meaning, content, and reuse;
·
Responsibility and accountability for managing
data’s consistency, timeliness, accuracy and completeness;
·
Sensitivity to the sources and uses of the
information, ensuring security, confidentiality and privacy are protected.
- Need
to develop a data stewardship program that will transcend many
organizational boundaries (e.g., no current rewards for cross-bureau
cooperation) and include various levels of stewardship while leveraging
and adhering to Federal data programs and standards (e.g., FGDC, NIST).
- Need
for clarity around the role of the public as co-holders of
responsibility around stewardship of their information.
- Need
to recognize that the “visual identity” or “branding” of the
Interior-wide Web experience itself is an information asset.
- Recognition
of the need to manage “meta” data; that is data “about” the data.
- Recognition
that some information/data held by Interior but supplied by 3rd parties
may need to be maintained/archived even if the originating organization
disappears (e.g., oil lease information).
|
|
|
|
|
|
|
|
Business processes will be analyzed, simplified or
otherwise redesigned in preparation for and during systems enhancements,
development, and implementation.
Rationale:
- Work
processes should be streamlined, efficient, and cost-effective.
- Work
processes, activities, and associated business rules will be well
understood and documented.
- Enables
E-Government initiatives.
- Potentially
reduces the total cost of ownership.
- Provides
better customer service.
- Required
by Clinger-Cohen Act and OMB Circular A-130 “Management
of Federal Information Resources” before an IT investment can be made,
and promotes compliance with the Government Performance and Results Act
(GPRA).
- Internet
has become a common utility and the public expects government to provide
information and access using this utility.
Implications:
- Need
thorough understanding and documentation of current existing business
processes.
- New
technical capabilities will need to be considered in conjunction with
normal review of business processes.
- Need
agreed upon business process re-engineering scope and results to enable
continual improvement through analyzing, simplifying and redesigning
work processes.
- Business
processes must be optimized to align with business drivers.
- Additional
time and resources will have to be invested in business analysis early
in the systems life cycle.
- Organizational
change may be required to implement reengineered business processes.
- Requires
all organizational levels, especially senior leadership to sponsor and
support reengineering efforts.
- May
result in additional new process modifications and systems development
being initiated not long after the completion of a reengineered process
that includes the Web.
- May
result in new ways of relating/ linking our information.
|
|
|
|
|
|
|
|
IT solutions will use industry-proven and
“state-of-the-art” technologies.
Rationale:
- Avoids dependence on weak vendors.
- Ensures robust product support.
- Enables greater use of commercial-off-the-shelf
solutions.
- Complies with OMB Circular A-130
“Management of Federal Information Resources”, which requires the
application of up-to-date information technology to take advantage of
opportunities to promote fundamental changes in agency structures, work
processes, and ways of interacting with the public that improve the
effectiveness and efficiency of Federal agencies.
Implications:
- “Industry proven” may include
solutions that are not from recognized vendors and/or encompass “freeware”
(e.g., Apache servers).
- Need to establish the criteria to
identify the strongest technology solutions.
- Need resources to adequately manage
the life cycle of all application acquisition and development
technologies including the incorporation of new technologies.
- “State-of-the-art” implies a much
higher added level of service to customers.
- Requires the technology portfolio to
migrate away from existing weak products or products that are reaching
obsolescence.
- With the use of proven technologies,
we may be slower to adopt the latest technologies.
7.
The exploration of new
technology should be encouraged and the findings shared across the
department.
|
|
|
|
|
|
|
|
Interior will
adopt a total cost of ownership (TCO) model.
Rationale:
- Leads to
better-informed decisions through an improved understanding of trade
offs.
- Enables improved planning and budget
decision-making.
Implications:
- Need to develop a total cost of
ownership model that explicitly includes all software development and
acquisition aspects.
- Need for the TCO model to include all
affected stakeholders (to address their buy-in) and that addresses the
model’s boundaries (e.g., Bureau, Department).
|
- Integrated
Development Environment (IDE) – This consists of the hardware, software
and supporting services that facilitate the development of software
applications and systems.
- Software
Configuration Management – Applicable to all aspects of software
development from design to delivery specifically focused on the control of
all work products and artifacts generated during the development process.
- Test
Management – The consolidation of all testing activities and results. Test
Management activities include test planning, designing (test cases),
execution, reporting, code coverage, and heuristic and harness
development.
- Modeling
– The process of representing entities, data, business logic, and
capabilities for aiding in software engineering.
- Office
Automation – refers to the traditional suite of widely used applications
provided at the desktop (e.g., word processing, spreadsheet.)
- Desktop
Publishing – refers to those applications that permit a document designer
to manipulate text and graphics on screen (e.g., different typefaces,
embedded illustrations, etc.) before committing the design to paper and
generating a high-quality printed document (e.g., magazines, newsletters,
brochures.)
- Change
Management – Refers to the management of application code and content
changes across the software development lifecycles.
- Web
Service - Web services (sometimes called application services) are
services (usually including some combination of programming and data, but
possibly including human resources as well) that are made available from a
business's web server for Web users or other Web-connected programs.
The classifications for any products or standards within
this domain are:
Life Cycle Definition/
Classifications Meaning
Contained Develop solutions using
these standards or products only if there are no suitable alternatives
categorized as preferred; if a preferred product is available that will meet
the requirements, plans should be developed to move from contained to preferred
as soon as practical.
Obsolete Being phased out; (e.g.,
vendor support ending); plans should be developed to rapidly phase out and
replace (often to avoid substantial risks).
Research Product/standard
to be used in conjunction with technology research efforts only (e.g., testing,
pilots).
Rejected Product/standard has been
evaluated and found not to meet technical architecture needs.
- Use of Microsoft Internet Explorer (Version > 5.5) is classified as Preferred
- Use of Safari
(MAC OS-X) is classified as Contained
- Use of Lotus NOTES Web is classified as Contained
- Use of Netscape (communicator &/or navigator) is
classified as Contained
- Use of Opera is classified as Contained
- Use of Mozilla is classified as Contained
5.3.2 Wireless / Mobile
- Use of Microsoft .NET is classified as Research
- Use of Sun J2EE (Version > 1.4) is classified as Research
- Use of Sun J2ME
is classified as Research
- Use of Air
Panel 802.11G is classified as Research
- Use of C# is classified as Preferred
- Use of
ASP.Net is classified as Preferred
- Use of VB for
Apps is classified as Preferred
- Use of PL1 is
classified as Contained
- Use of VB is
classified as Contained
- Use of Lotus
Script is classified as Contained
- Use of Model
204 is classified as Contained
- Use of Progress
is classified as Contained
- Use of ASP is
classified as Contained
- Use of VB
Script is classified as Contained
- Use of J
Script is classified as Contained
- Use of Ingres
is classified as Contained
5.3.4 Platform Independent (J2EE)
- Use of IBM Websphere
is classified as Preferred
- Use of
Coldfusion ML is classified
as Preferred
- Use of
JAVA is classified as Preferred
- Use of Java
Script is classified as Preferred
- Use of
HTML is classified as Preferred
- Use of
Perl is classified as Preferred
- Use of ECMA
Script is classified as Preferred
- Use of Open Source PHP (Version > 1.4) is
classified as Preferred
- Use of COBOL
is classified as Contained
- Use of SQL
92+ is classified as Preferred
- Use of
VB.Net is classified as Preferred
- Use of FORTRAN
is classified as Contained
- Use of C is
classified as Contained
- Use of C++ is
classified as Contained
- Use of Power
Builder is classified as Contained
- Use of Python
is classified as Contained
- Use of SlickEdit, Inc Visual SlickEdit is classified
as Contained
5.3.5 Web Servers
- Use of Apache (Version > 1.3) is classified as Preferred
- Use of Microsoft IIS
(Version > 4.0) is classified as Preferred
- Use of Lotus Domino
is classified as Preferred
- Use of
Deerfield/Orielly is classified as Contained
- Use of IBM SunOne (formerly iPlanet) is classified as
Contained
- Use of Microsoft Proxy Server is classified as Contained
- Use of Netscape Enterprise Server is classified as Contained
5.3.6 Application Servers
- Use of Macromedia Cold Fusion Server (Version >
4.51) is classified as Preferred
- Use of Brio Ondemand Server is classified as Preferred
- Use of IBM Websphere (Version > 3.5) is classified
as Preferred
- Use of Oracle (Version > 8.1) is classified as Preferred
- Use of TOMCAT
(Version > 1.1) is classified as Preferred
- Use of CITRIX (Version > 2) is classified as Preferred
- Use of ESRI Tools
is classified as Preferred
- Use of JBOSS
(Version > 1.4) is classified as Preferred
- Use of Prolifics Tuxedo-Lite is classified as Contained
- Use of Lotus Domino is classified as Contained
- Use of Prolifics JAM is classified as Contained
- Use of BEA Weblogic is classified as Contained
- Use of Sybase EA Server is classified as Contained
- Use of
SigmaPlot is classified as Contained
- Use of Brio Server
is classified as Preferred
- Use of ESRI Tools
is classified as Preferred
- Use of Portal
software (many vendors for research) is classified as Contained
- Use of Oracle (Version > 8.1) is classified as Research
- Use of OGC
Spatial Portal is classified as Research
An Integrated Development Environment (IDE) consists of the
hardware, software and supporting services that facilitate the development of
software applications and systems.
- Use of Microsoft Visual Studio and .NET is classified as Preferred
- Use of Macromedia Studio/ Cold Fusion MX (Version
> 6.01) is classified as Preferred
- Use of IBM Websphere Studio App Developer is classified as Preferred
- Use of Prolifics Panther is classified as Contained
- Use of Prolifics is classified as Contained
- Use of Prolifics JAM is classified as Contained
- Use of Microsoft Visual Studio is classified as Contained
- Use of Oracle Development Suite is classified as Contained
- Use of Lotus Domino is classified as Contained
- Use of Visual
Slick Edit is classified as Contained
- Use of Sybase Power Builder is classified as Contained
- Use of
IntelliJ is classified as Contained
- Use of Borland J Builder is classified as Contained
Software Configuration Management includes all aspects of
software development from design to delivery specifically focused on the
control of all work products and artifacts generated during the development
process.
Standards:
- Use of
Regression Testing is
classified as Preferred
Products:
- Use of Microsoft Visual Source Safe (software change
management) is classified as Preferred
- Use of
CVS is classified as Preferred
- Use of Merant PVCS (software change management) is classified as Contained
- Use of Oracle is classified as Contained
- Use of Rational ClearCase is classified as Contained
- Use of
Bindview is classified as Contained
- Use of IBM Change Management is classified as Contained
- Use of Freeware SCCS is classified as Contained
- Use of
Peopletools is classified as Contained
- Use of
Serena is classified as Research
Test Management is the consolidation of all testing
activities and results. Test Management activities include test planning,
designing (test cases), execution, reporting, code coverage, and heuristic and
harness development.
- Use of J
Unit is classified as Preferred
- Use of Mercury Tesing Suite (Win Runner, Load runner,
etc.) is classified as Preferred
- Use of PreVueX
is classified as Contained
- Use of Rational Testing Suite is classified as Research
Modeling is the process of representing entities, data,
business logic, and capabilities for aiding in software engineering.
Standards:
- Use of
MVC is classified as Preferred
- Use of
UML is classified as Preferred
Products:
- Use of Popkin
System Architect is classified as Preferred
- Use of Evoke AXIO
is classified as Preferred
- Use of Rational Rose is classified as Contained
- Use of Computer Associates ERWIN is classified as Contained
- Use of Oracle Designer is classified as Contained
- Use of Sybase PB Power Designer is classified as Contained
- Use of Visable Analyst is classified as Contained
- Use of Microsoft Visio is classified as Contained
- Use of Casewise is classified as Contained
- Use of Model
Mart is classified as Contained
- Use of HumanConcepts OrgPlus is classified as Contained
Office Automation refers to the traditional suite of widely
used applications provided at the desktop (e.g., word processing, spreadsheet.)
- Use of Microsoft Office (Version > 2000) is
classified as Preferred
- Use of Open Source OpenOffice (Version > 1.2) is
classified as Preferred
- Use of Corel Word Perfect Office is classified as Contained
- Use of Novell Groupwise is classified as Contained
- Use of Lotus Suite is classified as Reject
Desktop Publishing – refers to those applications that
permit a document designer to manipulate text and graphics on screen (e.g.,
different typefaces, embedded illustrations, etc.) before committing the design
to paper and generating a high-quality printed document (e.g., magazines,
newsletters, brochures.)
- Use of Microsoft MS Office Suite (Version > 2000)
is classified as Preferred
- Use of Adobe Framemaker is classified as Preferred
- Use of Adobe Acrobat Suite (Version > 5) is
classified as Preferred
- Use of Microsoft Publisher is classified as Contained
- Use of Quark Express for Windows is classified as Contained
- Use of Macromedia / Dreamweaver (Version > MX) is classified as Research
Change Management refers to the management of application
code and content changes across the software development lifecycles.
- Use of Merant PVCS (software change management) (Version > 7.1) is
classified as Preferred
- Use of
CVS is classified as Preferred
- Use of Remedy (work request tracking) is classified
as Contained
- Use of Documentum Erooms is classified as Contained
- Use of Serena Changeman is classified as Research
Web services (sometimes called application services) are
services (usually including some combination of programming and data, but
possibly including human resources as well) that are made available from a
business's web server for Web users or other Web-connected programs.
Standards:
- Use of
SOAP is classified as Preferred
- Use of
XML is classified as Preferred
Products:
- Use of Microsoft .Net-based is classified as Preferred
- Use of SUN J2EE-based (Version > 1.4) is
classified as Preferred
- Use of Microsoft Project (Version > 2000) is
classified as Preferred
- Use of Microsoft Visio (Version > 2002) is
classified as Preferred
- Use of eHelp RoboHelp
is classified as Preferred
- Use of Skillsoft Courseware (Version > 4.3) is
classified as Preferred
- Use of
Primavera All is classified as Contained
- Use of Aperature is classified as Contained
- Use of Little Planet Course Development is classified
as Contained
- Use of NETQ
Course Player is classified as Contained
- Use of Microsoft Commercial Site Server is classified
as Contained
- Use of Delphi is classified as
Contained
- Use of Microsoft MS Sharepoint Server is classified as Research
Utilities - Graphical
Tools:
- Use of Adobe Suite
is classified as Preferred
- Use of Autodesk AutoCAD (Version > 2000i) is
classified as Preferred
- Use of JASC Paintshop Pro is classified as Contained
- Use of Corel Corel Draw is classified as Contained
- Use of Macromedia Graphical Design Tool is classified
as Contained
- Use of Evolution Computing FastCAD is classified as Contained
- Use of
Camtasia Studio is classified as Contained
- Use of VIAGRAFIX Design CAD LT is classified as Contained
- Use of
SYSTAT10 is classified as Contained
- Use of
Earthinfo is classified as Contained
- Use of
SmartDraw is classified as Contained
- Use of Boss International Hec_Ras is classified as Contained
- Use of Boss International SMS/RMS is classified as Contained
- Use of Hydrosphere is classified as Contained
- Use of Geo-Slope SlopeW is classified as Contained
- Use of West Consultants RipRap is classified as Contained
- Use of Dhi
MIKE11 1-D is classified as Contained
- Use of Dhi
MIKE21 2-D is classified as Contained
- Use of Mr. Sid
Geospatial Encoder is classified as Contained
- Use of
CE-QUAL-W2 is classified as Contained
- Use of
Splus-Windows is classified as Contained
- Use of Insightful S-Plus - Unix is classified as Contained
- Use of Open Source GIMP is classified as Contained
Utilities - Terminal Emulators: (All Terminal
Emulators are classified as contained. All bureaus currently have Terminal
Emulators deployed in their environment and it would not be technically or
economically feasible to migrate to a preferred tool.)
- Use of Rumba is classified as Contained
- Use of
Renaissance is classified as Contained
- Use of Viewnow
is classified as Contained
- Use of
Tinyterm is classified as Contained
- Use of Hummingbird is classified as Contained
- Use of
MochaSoft is classified as Contained
- Use of WQR is
classified as Contained
- Use of Web
Term is classified as Contained
- Use of Esker SmartTerm is classified as Contained
- Use of
Reflection X is classified as Contained
- Use of
Optivity is classified as Contained
Utilities – Miscellaneous:
- Use of Samba.org Samba (Version > 2.3) is
classified as Preferred
- Use of Hyena
is classified as Contained
- Use of Symantec PC Anywhere is classified as Contained
- Use of Expertcity Go To My PC is classified as Contained
- Use of
Integrated FAX is classified as Contained
- Use of HF
Netcheck is classified as Contained
- Use of Purify
is classified as Contained
- Use of Merotz CostXpert (Version >3.0) is
classified as Research
- Use of HTML
(Version > 4.) is classified as Preferred
- Use of PDF
(Version > 5.0) is classified as Preferred
- Use of Microsoft .NET (Incl. ASP, Visual BASIC, C#,
C++, etc.) is classified as Preferred
- Use of Versata
Logic Studio (Version > 5.1) is classified as Preferred
- Use of Prolifics Panther is classified as Contained
- Use of Prolifics is classified as Contained
- Use of Prolifics JAM is classified as Contained
- Use of Silverstream is classified as Contained
- Use of Oracle Toolkit is classified as Contained
- Use of SUN Chilisoft is classified as Contained
- Use of Appeon (Version > 2.5 for Powerbuilder) is
classified as Research
- Use of
XHTML is classified as Preferred
- Use of
DHTML is classified as Preferred
- Use of
CSS is classified as Preferred
- Use of
XSLT is classified as Preferred
- Use of SVG
(Scalable Vector Graphics) is
classified as Preferred
- Use of
JSP is classified as Preferred
- Use of
ASP is classified as Contained
- Use of PHP
(HTML generation) is classified as Preferred
- Use of
WML is classified as Research
- Use of
J2ME is classified as Research
- Use of
.NET is classified as Research
Standards:
- Use of
XML is classified as Preferred
Products:
- Use
of Crystal Decisions Seagate Crystal Reports (Version > 8.5) is
classified as Preferred
- Use of COGNOS Impromptu Web Reports (Version >
7.0) is classified as Preferred
- Use of Net IQ WebTrends (Version > 7.0) is
classified as Preferred
- Use of COGNOS Impromptu (Client Server) is classified
as Contained
- Use of Actuate is classified as Contained
- Use of Oracle Report Writer is classified as Contained
- Use of Sybase InfoMaker is classified as Contained
- Use of Datawatch Monarch is classified as Contained
- Use of SAS is classified as Contained
- Use of Lotus is classified as Contained
- Use of
SPSS is classified as Research
- Use of Microsoft Reporting Server is classified as Research
Standards:
- Use of
OGC is classified as Preferred
Products:
- Use of GOTS ESRI Connector is classified as Preferred
- Use of GOTS ESRI SDE
is classified as Preferred
- Use of IBM Websphere
is classified as Preferred
- Use of Informatica is classified as Preferred
- Use of GRID
Toolkit is classified as Contained
- Use of IBM MQSeries
is classified as Research
- Use of
XML-RPC is classified as Research
- Use of Microsoft MSMQ
is classified as Research
- Use of
COM+ is classified as Research
Middleware - Screen
Scrapers:
- Use of
Flashpoint is classified as Preferred
- Use of Pitney
Bose is classified as Contained
5.3.24 Enterprise Application Integration
- Use of Lotus Domino (workflow) is classified as Preferred
- Use of Mercury Suite is classified as Preferred
- Use of Remedy (workflow) is classified as Contained
- Use of EI Streams Viewstar (Workflow) is classified
as Contained
- Use of IBM Integrator is classified as Research
- Use
of DIIOP is classified as Research
The quality
of the Interior-wide guidance provided within this TRM chapter is a reflection
of the efforts of the Application Development Domain team. The members of the team are:
Organization Name
National Park
Service Lance
Gridley
US Geological
Survey Ken Moss
Fish and
Wildlife Service Mike
Brewer
Bureau of
Reclamation Angela Bolyard
Office of the
Secretary Brian Gallagher
Minerals
Management Service Jim Browning
National
Business Center Sharon Williams
Office of
Surface Mining Joy
Johnson
Bureau of Land
Management Bruce Allen
