WARNING:
JavaScript is turned OFF. None of the links on this concept map will
work until it is reactivated.
If you need help turning JavaScript On, click here.
This Concept Map, created with IHMC CmapTools, has information related to: Ohmes-Systems Engineering_rev2, Software Engineering Perspective on UPS Moving to Cloud Computing, Deployment Models Including Hybrid Clouds, Lack of standards for data portability Hybrid concern Increase threat exposure (inet), Data back up Responsibility's transfered to provider Data loss, Mobility Logs Cloud visibility, Functional Architecture Such As ITIL Service Design Package, UPS Systems Engineering Processes & Lifecycle Includes Requirements Analysis, Enterprise Architecture Framework Such As TOGAF, Audit expectations not bound in general contracts Concepts lacking IA maturity Forfeiture of ownership, Anti Virus Responsibility's transfered to provider Data loss, Equipment theft like Standard risks (cloud / Non-cloud), Malicious code detections / prevention Responsibility's transfered to provider incident response, Enterprise Architecture Framework Such As Zachman, Services Model Including Infrastructure As A Service, Provider Remote Access Policy Responsibility's transfered to provider Residual data risks (elastic reduction), scalability Logs Cloud How UPS can move to cloud computing, SE Process Outputs Includes Physical Architecture, Cloud Computing Model leveraging Existing Computing Framework, Anti Virus Responsibility's transfered to provider Residual data risks (elastic reduction), Existing Software Reprogrammed to Take advantage of a scalable infustructure