Approved for public release, distribution is unlimited / A thorough examination of the Secure Application Integration Methodology (SAIM) for applicability in the Department of the Navy (DON) would provide useful information about a beneficial methodology. SAIM is analyzed, by accessing its step by step directions, for suitability in the integration of the Enterprise Resource Planning (ERP) projects implemented by the SYSTEMS COMMANDS (SYSCOMS). The Navy Enterprise Convergence Team (NECT) that leads the ERP integration effort could benefit from a sound Enterprise Application Integration methodology. Results do not support SAIM as the sole guiding EAI methodology however it could have some value to the NECT. SAIM has three primary benefits which NECT could employ: 1) It provides a complete walkthrough of the EAI process, 2) It emphasizes the importance of an Enterprise Architecture, and 3) It provides useful management checklists along with other important considerations. SAIM also has some significant shortcomings: 1) It does not support all the DON Chief Information Officer requirements, 2) It does not provide Change Management Guidance, 3) It does not take into account the uniqueness of the Navy's environment, and finally 4) SAIM relies on an Enterprise Architecture as its foundation which the Navy does not currently have. / Lieutenant Commander, United States Navy
Identifer | oai:union.ndltd.org:nps.edu/oai:calhoun.nps.edu:10945/1651 |
Date | 03 1900 |
Creators | Marin, Ramon O. |
Contributors | Cook, Glenn R., Brinkley, Douglas E., Naval Postgraduate School (U.S.)., Department of Information Science |
Publisher | Monterey, California. Naval Postgraduate School |
Source Sets | Naval Postgraduate School |
Detected Language | English |
Type | Thesis |
Format | xvi, 101 p., application/pdf |
Rights | This publication is a work of the U.S. Government as defined in Title 17, United States Code, Section 101. As such, it is in the public domain, and under the provisions of Title 17, United States Code, Section 105, may not be copyrighted. |
Page generated in 0.0679 seconds