Enterprise_Achitectual_Functional_Requirements.docx

COMMERCIAL OFF THE SHELF SOFTWARE - ENTERPRISE ARCHITECTURE REPOSITORY AND MODELING TOOL

Functional Requirements The Navy sits in a unique spot reporting to multiple entities using different means therefor we have a unique list of requirements. Functional requirements are absolute must haves and are basic functionalities of a product to accomplish the mission.

Frameworks/Methodologies/Notational Languages/Reference Models Any Enterprise Architectural Repository Modeling Suite product must support our required unique blend of Frameworks, Methodologies, Notational Languages, and Reference Models. Below is a list of must haves support for:

Frameworks:

· DODAF version 2 – Department of Defense Architecture Framework

· REQUIRED: for reporting to Department of Navy and other Department of Defense Agencies

· See Appendix for more details

· FEAF version 2 – Federal Enterprise Architecture Framework

· REQUIRED: for reporting to IC Community & Federal Agencies, including Office of Management and Budget

· See Appendix for more details

· TOGAF version 9 – The Open Group Architecture Framework

· Optional: Used for some reporting to Federal Agencies, including Office of Management and Budget

· See Appendix for more details

Methodology:

· ITIL version 3 – Information Technology Infrastructure Library

· REQUIRED: for consistency within the Navy

· See Appendix for more details

Notational Languages:

· BPMN version 2 – Business Process Modeling Notation

· REQUIRED: for reporting and consistency within the Navy, Department of Navy, Department of Defense, IC Community, Federal Agencies including Office of Management and Budget

· See Appendix for more details

· UML version 2.5 – Unified Modeling Language

· Optional: Used for some reporting within the Navy and Federal Agencies, including Office of Management and Budget

· See Appendix for more details

· IE Data Modeling – Information Engineering

· REQUIRED: for reporting and consistency within the Navy, Department of Navy, Department of Defense, IC Community, Federal Agencies including Office of Management and Budget

· See Appendix for more details

· IDEF1X version– Integrated Definition Data Modeling – 1X

· Optional: Used for some reporting within the Navy and some Department of Defense agencies

· See Appendix for more details

Reference Models:

· JARM – Joint Architecture Reference Model

· Optional: The IC JARM represents the IC’s extension to the FEA.

· See Appendix for more details

· CRM – Common Reference Model

· Optional: An extension of the FEAF to expand its inclusion of multiple Federal Entities

· See Appendix for more details

· CRA – Collaboration Reference Model

· Optional: developed by the IC Community, it has multiple sub parts.

· ICAM-RA – Identity, Credential, Authorization, Management Reference Architecture

· DRA – Data Reference Architecture

· See Appendix for more details

Repository and Modeling Any Enterprise Architectural Repository Modeling Suite product must support our requirement of being a Repository and Modeling Suite for all current and future state architectural diagrams, reports and enterprise architecture artifacts. Below is a list of must haves support for:

· Relational Database Management System (Backend)

· Object oriented repository with inter-object relationships

· Structured Meta-Model and is fully customizable

· Relationships must be searchable

· Objects must have attributes and Meta-Data for each object

· Meta-Data must be searchable

· Robust Modeling capabilities

· Strategic Modeling

· Roadmap Modeling

· Organizational Chart

· Business Glossary

· Investment & Capital Management

· Business Process Modeling

· Business Case

· Capability Modeling

· Functionality Mapping

· Data Modeling

· System and Application Modeling

· Services Mapping

· Technical & Infrastructure Modeling

· Portfolio Management

· Document Management

Hardware/Technical Requirements Any Enterprise Architectural Repository Modeling Suite product must support our Hardware and Technical requirements. Below is a list of must haves:

· Compatible with Intel-Based Computers

· Compatible with Microsoft Windows based operating systems

· Relational Database Management System (Backend)

· Microsoft SQL Server 2014 or higher

· Compatible with Client-Server installation format

· One centralized location, with multiple users accessing it

· Not installed locally on individual workstations

· Compatible with Virtual/Cloud migration options

· i.e. Does not require local standalone installation

Usability/Connectivity Requirements Any Enterprise Architectural Repository Modeling Suite product must support our Usability and Connectivity requirements. Below is a list of must haves:

· Compliant with Section 508

· Compatible with Microsoft Active Directory

· Compatible with Microsoft Exchange

· Compatible with Microsoft Internet Information Service (IIS)

· Compatible with Simultaneous Multi-User Support (2-50)

· Web- Modeling Capability

· Capability to generate reports

· Built-in Workflow engine for Diagram creation/updating

· Customer Feedback/Input capability

· Must be able to function without Internet Connection

· Product and Updates must be made available on CD’s/DVD’s

Non-Functional Requirements A non-functional requirement is essential to ensure the usability and effectiveness of the entire software system. Failing to meet non-functional requirements can result in systems that fail.

Import and Export Requirements Any Enterprise Architectural Repository Modeling Suite product must support our Import and Export requirements. Below is a list of must haves:

· Ability to Import and Export MS Excel Documents

· Ability to Import MS Visio Documents

· Ability to Export XML Documents

· Ability to Import and Export using REST API Reporting and Web Access Requirements Any Enterprise Architectural Repository Modeling Suite product must support our Usability and Connectivity requirements. Below is a list of must haves:

· Must support Web-based Modeling

· Must support a built-in Query Engine

· Ability to create Graphical reports

· Ability to have Web-Based Read-Only mode

· Ability to generate Static Web-Pages

· Ability to create Ad-hoc Discovery Analysis Reports

· Ability to create Reports in RTF format

· Ability to create Reports in HTML format

· Ability to create Reports in DOC (MS Word) format

· Ability to create Reports in XLS (MS Excel) format

· Ability to create Reports in PDF format

· Ability to save Diagrams in JPG format

· Ability to save Diagrams in PNG format

· Ability to save Diagrams in GIF format

· Ability to save Diagrams in TIFF format Vendor Service Level Agreement Requirements Any Enterprise Architectural Repository Modeling Suite product must be supported by the vendor/manufacture. Below is a list of must haves:

· Product support must be available via Phone

· Product support must be available via Online Chat

· Product support must be available via Community (Blog/Forums)

· Product support must be available via Email

· Product support must be responsive in a timely manner

· Product must be kept current and adapt to Industry shifts Training Requirements Any Enterprise Architectural Repository Modeling Suite product must support our Usability and Connectivity requirements. Below is a list of must haves:

· Training must be available in multiple formats