Lifecycle Modeling – A Quick Overview of a New Methodology for Simple, Rapid Development, Operations, and Support. Steven H. Dam, Ph.D., ESEP President, SPEC Innovations 571-485-7805 [email protected] May 15, 2012. Overview. What is Cloud Computing? Why a New Language? - PowerPoint PPT Presentation
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
• Definition from NIST: – Cloud computing is a model for enabling
convenient, on-demand network access to a shared pool of configurable computing resources that can be rapidly provisioned and released with minimal management effort or service provider interaction. This cloud model promotes availability and is composed of five essential characteristics, three service models, and four deployment models
From presentation by Jim Sweeney, GTSI at the Technology Leadership Series 2012 Seminar, January 19, 2012
Five Essential Characteristics• On-demand self-service. A consumer can unilaterally provision computing capabilities,
such as server time and network storage, as needed automatically without requiring human interaction with each service’s provider.
• Broad network access. Capabilities are available over the network and accessed through standard mechanisms that promote use by heterogeneous thin or thick client platforms (e.g., mobile phones, laptops, and PDAs).
• Resource pooling. The provider’s computing resources are pooled to serve multiple consumers using a multi-tenant model, with different physical and virtual resources dynamically assigned and reassigned according to consumer demand. There is a sense of location independence in that the customer generally has no control or knowledge over the exact location of the provided resources but may be able to specify location at a higher level of abstraction (e.g., country, state, or datacenter). Examples of resources include storage, processing, memory, network bandwidth, and virtual machines.
• Rapid elasticity. Capabilities can be rapidly and elastically provisioned, in some cases automatically, to quickly scale out and rapidly released to quickly scale in. To the consumer, the capabilities available for provisioning often appear to be unlimited and can be purchased in any quantity at any time.
• Measured Service. Cloud systems automatically control and optimize resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts). Resource usage can be monitored, controlled, and reported providing transparency for both the provider and consumer of the utilized service.
From presentation by Jim Sweeney, GTSI at the Technology Leadership Series 2012 Seminar, January 19, 2012
State of Current “Languages”• In the past decade, the Unified Modeling
Language (UML) and now the profile Systems Modeling Language (SySML) have dominated the discussion
• Why?– Perception that software is “the problem”– Hence need for an “object” approach
• SysML was designed to relate systems thinking to software development, thus improving communication between systems engineers (SE) and software developers
Why Objects Are Not the Answer• Although SysML may improve the communication
of design between SEs and the software developers it does not communicate well to anyone else– No other discipline in the lifecycle uses object oriented
design and analysis extensively– Users in particular have little interest/acceptance of
this technique– Software developers who have adopted Agile
programming techniques want functional requirements (and resent SEs trying to write software)
– Many software languages are hybrid object and functional
• In preparing for the cloud computing world of SE we:– Researched the variety of languages (ontologies)
in common use (DM2, SysML, BPMN, IDEF, SREM, etc.)
– Researched the variety of representations (FFBDs, N2, Behavior Diagrams, Class Diagrams, Electrical Engineering Diagrams, etc.)
– Took the best of each of these languages and representations and distilled them down to the essential elements, relationships, attributes, and diagramsThe result: Lifecycle Modeling Language
• LML combines the logical constructs with an ontology to capture information– SysML – mainly constructs – limited ontology– DoDAF Metamodel 2.0 (DM2) ontology only
• LML simplifies both the “constructs” and ontology to make them more complete, yet easier to use
• Goal: A language that works across the full lifecycle
No constructs – only special types of Actions – ones that enable the modeling of command and control/ information assurance to capture the critical decisions in your model