Model - Revision history

User at 16:20, 20 July 2023

2023-07-20T16:20:26Z

User at 15:04, 19 October 2022

2022-10-19T15:04:15Z

User at 15:03, 19 October 2022

2022-10-19T15:03:25Z

User at 14:59, 19 October 2022

2022-10-19T14:59:05Z

User at 14:32, 19 October 2022

2022-10-19T14:32:03Z

User at 14:28, 19 October 2022

2022-10-19T14:28:27Z

User at 14:05, 19 October 2022

2022-10-19T14:05:49Z

User: Created page with "'''Content Coming Soon'''"

2019-01-06T05:55:17Z

Created page with "'''Content Coming Soon'''"

New page

'''Content Coming Soon'''

@@ Line 40: / Line 40: @@
 ===See Also===
-[[Capability Maturity Model (CMM)]]<br />
+*[[Capability Maturity Model (CMM)]]
-[[Capability Maturity Model Integration (CMMI)]]<br />
+*[[Capability Maturity Model Integration (CMMI)]]
-[[AIDA Model]]<br />
+*[[AIDA Model]]
-[[Business Model]]<br />
+*[[Business Model]]
-[[Operating Model]]
+*[[Operating Model]]

@@ Line 20: / Line 20: @@
 There are many definitions of the word model. The following definitions refer to a model as a representation of selected aspects of a domain of interest to the modeler:
 *a physical, mathematical, or otherwise logical representation of a system, entity, phenomenon, or process (DoD 1998);
-*a representation of one or more concepts that may be realized in the physical world (Friedenthal, Moore, and Steiner 2009);
+*a representation of one or more concepts that may be realized in the physical world (Friedenthal, Moore, and Steiner 2009); a simplified representation of a system at some particular point in time or space intended to promote understanding of the real system (Bellinger 2004);
 *an abstraction of a system, aimed at understanding, communicating, explaining, or designing aspects of interest of that system (Dori 2002); and
 a selective representation of some system whose form and content are chosen based on a specific set of concerns; the model is related to the system by an explicit or implicit mapping (Object Management Group 2010).

@@ Line 4: / Line 4: @@
 According to Stachowiak, a model needs to possess three features:
 *Mapping feature: A model is based on an original.
-*Reduction feature: A model only reflects a (relevant) selection of the original’s
+*Reduction feature: A model only reflects a (relevant) selection of the original’s properties.
 *Pragmatic feature: A model needs to be usable in place of the original with respect to some purpose.
 The first two features are covered simultaneously if one speaks of a model as a “projection” as this implies both something that is projected (the original) and that some information is lost during the projection. Of course exactly what information is dropped—by an activity called “abstraction”—and what is retained depends on the ultimate purpose the model is going to be used for.
@@ Line 14: / Line 13: @@
 *for somebody (receiver)
 *or some purpose (usage context)
@@ Line 39: / Line 40: @@
-===See Also==
+===See Also===
 [[Capability Maturity Model (CMM)]]<br />
 [[Capability Maturity Model Integration (CMMI)]]<br />

← Older revision		Revision as of 14:59, 19 October 2022
Line 1:		Line 1:
−	===Why use a model?<ref>[https://learn.microsoft.com/en-us/azure/devops/boards/work-items/guidance/cmmi/guidance-background-to-cmmi?view=azure-devops Why use a model?]===	+	===What is a Model?===
		+	A '''Model''' is a representation of a particular thing with a particular purpose. A model may be physical or just an idea, but it is always a representation with a purpose.
		+
		+	According to Stachowiak, a model needs to possess three features:
		+	*Mapping feature: A model is based on an original.
		+	*Reduction feature: A model only reflects a (relevant) selection of the original’s
		+	properties.
		+	*Pragmatic feature: A model needs to be usable in place of the original with respect to some purpose.
		+	The first two features are covered simultaneously if one speaks of a model as a “projection” as this implies both something that is projected (the original) and that some information is lost during the projection. Of course exactly what information is dropped—by an activity called “abstraction”—and what is retained depends on the ultimate purpose the model is going to be used for.
		+
		+	The third feature can be further elaborated by detailing what the pragmatic use of the model is. According to Steinmuller ¨ (1993): A model is information:
		+	*on something (content, meaning)
		+	*created by someone (sender)
		+	*for somebody (receiver)
		+	*or some purpose (usage context)
		+
		+
		+	===Various Definitions of a Model<ref>[https://www.sebokwiki.org/wiki/What_is_a_Model%3F Various Definitions of a Model]</ref>===
		+	There are many definitions of the word model. The following definitions refer to a model as a representation of selected aspects of a domain of interest to the modeler:
		+	*a physical, mathematical, or otherwise logical representation of a system, entity, phenomenon, or process (DoD 1998);
		+	*a representation of one or more concepts that may be realized in the physical world (Friedenthal, Moore, and Steiner 2009);
		+	a simplified representation of a system at some particular point in time or space intended to promote understanding of the real system (Bellinger 2004);
		+	*an abstraction of a system, aimed at understanding, communicating, explaining, or designing aspects of interest of that system (Dori 2002); and
		+	a selective representation of some system whose form and content are chosen based on a specific set of concerns; the model is related to the system by an explicit or implicit mapping (Object Management Group 2010).
		+	In the context of systems engineering, a model that represents a system and its environment is of particular importance to the system engineer who must specify, design, analyze, and verify systems, as well as share information with other stakeholders. A variety of system models are used to represent different types of systems for different modeling purposes. Some of the purposes for modeling systems are summarized in the topic Why Model?, and a simple taxonomy of the different types of models is described in the topic Types of Models. The modeling standards topic refers to some of the standard system modeling languages and other modeling standards that support MBSE.
		+
		+	A model can have different forms as indicated in the first definition above, including a physical, mathematical, or logical representation. A physical model can be a mockup that represents an actual system, such as a model airplane. A mathematical model may represent possible flight trajectories in terms of acceleration, speed, position, and orientation. A logical model may represent logical relationships that describe potential causes of airplane failure, such as how an engine failure can result in a loss of power and cause the airplane to lose altitude, or how the parts of the system are interconnected. It is apparent that many different models may be required to represent a system-of-interest (SoI).
		+
		+
		+	===Why use a model?<ref>[https://learn.microsoft.com/en-us/azure/devops/boards/work-items/guidance/cmmi/guidance-background-to-cmmi?view=azure-devops Why use a model?]</ref>===
	Improvement efforts require a model of how your organization works, which functions they need, and how those functions interact. A model gives you an understanding of organizational elements and assists in discussions of how and what can and should be improved.		Improvement efforts require a model of how your organization works, which functions they need, and how those functions interact. A model gives you an understanding of organizational elements and assists in discussions of how and what can and should be improved.

@@ Line 1: / Line 1: @@
-===Why use a model?<ref>Why use a model?
+===Why use a model?<ref>[https://learn.microsoft.com/en-us/azure/devops/boards/work-items/guidance/cmmi/guidance-background-to-cmmi?view=azure-devops Why use a model?]===
 Improvement efforts require a model of how your organization works, which functions they need, and how those functions interact. A model gives you an understanding of organizational elements and assists in discussions of how and what can and should be improved.
@@ Line 8: / Line 8: @@
 *Is often supported by trainers and consultants
 *Can help solve disagreements by providing agreed-upon standards

← Older revision		Revision as of 14:28, 19 October 2022
Line 1:		Line 1:
−	===Why use a model?<ref>~~[https://learn.microsoft.com/en-us/azure/devops/boards/work-items/guidance/cmmi/guidance-background-to-cmmi?view=azure-devops~~ Why use a model?~~]</ref>===~~	+	===Why use a model?<ref>Why use a model?
	Improvement efforts require a model of how your organization works, which functions they need, and how those functions interact. A model gives you an understanding of organizational elements and assists in discussions of how and what can and should be improved.		Improvement efforts require a model of how your organization works, which functions they need, and how those functions interact. A model gives you an understanding of organizational elements and assists in discussions of how and what can and should be improved.

← Older revision		Revision as of 14:05, 19 October 2022
Line 1:		Line 1:
−	~~'''Content Coming Soon'''~~	+	===Why use a model?<ref>[https://learn.microsoft.com/en-us/azure/devops/boards/work-items/guidance/cmmi/guidance-background-to-cmmi?view=azure-devops Why use a model?]</ref>===
		+	Improvement efforts require a model of how your organization works, which functions they need, and how those functions interact. A model gives you an understanding of organizational elements and assists in discussions of how and what can and should be improved.
		+
		+	A model offers the following benefits:
		+	*Provides a common framework and language to help communicate
		+	*Leverages years of experience
		+	*Helps users consider the large picture while focusing n improvement
		+	*Is often supported by trainers and consultants
		+	*Can help solve disagreements by providing agreed-upon standards