This assessment form is an architectural tool intended to determine the “readiness” level of interoperability, functionality, scalability, and adaptability of existing software relative to enabling new business opportunities and providing new e-government solutions for delivering service in the future. It is designed to support the planning and implementation of Target Software Architecture principles, recommended standards, and best practices. It addresses the alignment of the software applications and associated programming, database, productivity, and utility software proposed in a PIJ with Enterprise Architecture. It describes major attributes and characteristics derived from Statewide Policy P100, Information Technology, and the principles and recommended standards and best practices contained in the Target Software Architecture.
Ratings for programming, database, and productivity software are based on the latest production release of the software. Utility software products used in conjunction with target network and platform architectures are considered target.
This assessment form is applicable for all software reported to the Information Services Inventory System (ISIS) as defined by Statewide Standard P800-S815, Configuration Management.
Score. Questions for the four (4) software categories
are scored with one (1) point for a “Yes” answer and zero (0) for a “No”
answer. Maximum possible is the total number of questions for each
category.
Agency/Community
of Interest:
Software
Application:
|
Attributes/Characteristics |
Maximum Possible |
Score |
Description |
|
A.
Functionality, scalability, and adaptability, emphasizing client interaction (Software
Applications only) |
5 |
|
Software Applications designed to fulfill business
requirements and
maximize the
efficiency and effectiveness of business functions with the ability to scale
and adapt as business requirements change and expand; that are interoperable,
modular, and deployable across the State enterprise; and that support e-government
and client self-sufficiency through browser-based access, regardless of
location. |
|
B.
Platform independence and use of non-proprietary technologies |
5 |
|
Addresses interoperability, portability, and
integration across platforms utilizing open and/or de-facto standard
protocols, programming languages, middleware, development tools, databases,
utilities, etc. |
|
C. Exchange of
information, integration with other software |
5 |
|
Utilizes common, standard interfaces and/or
middleware having the ability to interoperate and integrate with other
software without requiring custom programming or intermediate,
interface-specific applications. |
|
D.
Ability to maximize (take full advantage of) Target Network, Security, and
Platform Architectures |
5 |
|
Has the capability to conform to, and adhere to,
the standards and best practices delineated in the other domain architectures
without requiring substantial modifications. |
|
Total Rating Points |
20/15 |
|
|
Software when italicized in
an assessment form question encompasses all five (5) categories of Software
Architecture, including:
1.
Software Applications 4.
Database Software
2.
Programming Software 5. Utility
Software
3.
Productivity Software
Agency/Community
of Interest:
Software
Application:
A. Functionality, scalability, and adaptability refer to software
applications that maximize the efficiency and effectiveness of business
functions and have the ability to scale and adapt as business requirements
change and expand; are interoperable, modular, and deployable across the State
enterprise; and that emphasize e-government and client self-sufficiency
through browser-based access, regardless of location. (Software
Applications only) |
Yes |
|
1.
Is the software application extensible (capable of being expanded or customized), adaptive (the adjustment
or modification that makes something more fit given the conditions of its
environment), and capable of accommodating increased demands for service
without substantial modifications and additional costs? |
|
|
2.
Is the software application developed and deployed utilizing open and/or
de-facto standard protocols, languages, development tools, databases, etc.? |
|
|
3.
Is a browser or GUI presentation layer available for the software
application? |
|
|
4.
Does the software application emulate the “look and feel” of the client
device’s operating system and productivity software? |
|
|
5.
Does the software application support e-government solutions and/or end user
self-sufficiency or self-service? |
|
|
B. Platform independence and use of non-proprietary technologies addresses
interoperability and portability across platforms utilizing open and/or
de-facto standard protocols, programming languages, middleware, development
tools, databases, utilities, etc. |
|
|
1. Is the software,
as configured, portable, and accessible across platforms in use within the
subject agencies or community of interest? |
|
|
2. Is the software,
including version levels, consistent with current deployments of like or
similar software within the subject agencies or community of interest? |
|
|
3. Is the software,
as configured, platform independent, without proprietary issues and
requirements? |
|
|
4. Is the software
designed for, and/or supports, n-tier-oriented architecture deployment and
implementation? |
|
|
5.
Does the software allow for, or provide open and/or de-facto standard
interfaces for, a variety of end-user client devices, server and storage
platforms, and database products? |
|
|
C.
Exchange of information, integration with other software emphasizes common
standard interfaces and/or middleware having the ability to interoperate and
integrate with other software without requiring custom programming and
intermediate interface-specific applications. |
|
|
1.
Does the software, as configured, provide for and/or support (directly
or through extensions) the transparent transfer and exchange of information
with other software products through open or de-facto industry standards? |
|
|
2.
Does the software utilize target middleware technologies or open or
de-facto industry standards for communicating and exchanging information with
other software products? |
|
|
3.
Does the software provide for and/or support the integration of, or
interfacing with, productivity software currently deployed within the subject
agencies or community of interest? |
|
|
4.
Does the software provide the capability for sharing common software
services and potential reuse of components? |
|
|
5.
Is the software, as configured, unrestricted by any proprietary or
vendor-specific integration requirements? |
|
|
D.
Ability to maximize Target Network, Security, and Platform Architectures addresses the capability
to conform to, and adhere to, the standards and best practices delineated in
the other domain architectures, without requiring substantial modifications. |
|
|
1.
Is the software capable of providing and/or supporting secure (as
defined by the State of Arizona Target
Security Architecture) end-user interface access without substantial
modifications, regardless of end-user location? |
|
|
2.
Does the software, as configured, utilize target Network and Platform
operating systems? |
|
|
3.
Are the versions of the target Network and Platform operating systems
utilized by the software consistent with current deployments within
the subject agencies or community of interest? |
|
|
4.
Do the security services included with the software align with Target
Security Architecture and adhere with all security, confidentiality, and
privacy policies as well as applicable statutes? If no security services are
included, is the software unrestricted to align with Target Security
Architecture? |
|
|
5.
Is the software capable of being managed and maintained with standard
SNMP-based management tools? |
|
|
Total Rating Points |
|