David Lemmer Log - Revision history

David Lemmer at 20:05, 30 April 2022

2022-04-30T20:05:50Z

← Older revision		Revision as of 20:05, 30 April 2022
Line 8:		Line 8:
	https://wiki.opensourceecology.org/images/c/c9/OSE_Requirements_decomposition_4-30-2022.png		https://wiki.opensourceecology.org/images/c/c9/OSE_Requirements_decomposition_4-30-2022.png

	The above diagram starts to decompose requirements that support the goals of OSE by identifying areas of critical function or performance that must be upheld if the objectives of OSE are to be achieved. In the MBSE(Model Based Systems Engineering) process these requirements are derived by examining and decomposing stakeholder needs or aspects of a system which must be achieved to deliver the performance needed. These requirements will then be used to compare against system components and the properties they posses to verify that these requirements met. Doing this allows for the design of the system to be more easily understood as it is going through early design phases. The MBSE approach also enables trade study to be conducted more easily through the ability to compare their cost schedule and performance within one model. SysML also enables systems engineering practitioners to model the components of the system in an environment or context while considering the system as it is engaged in particular processes. These are contexts are described by capturing the relevant inputs to the system and processes are described and documented in behavioral diagrams.		The above diagram starts to decompose requirements that support the goals of OSE by identifying areas of critical function or performance that must be upheld if the objectives of OSE are to be achieved. In the MBSE(Model Based Systems Engineering) process these requirements are derived by examining and decomposing stakeholder needs or aspects of a system which must be achieved to deliver the performance needed. These requirements will then be used to compare against system components and the properties they posses to verify that these requirements are met(satisfied). Doing this allows for the design of the system to be more easily understood as it is going through early design phases. The MBSE approach also enables trade study to be conducted more easily through the ability to compare their cost schedule and performance within one model. SysML also enables systems engineering practitioners to model the components of the system in an environment or context while considering the system as it is engaged in particular processes. These are contexts are described by capturing the relevant inputs to the system and processes are described and documented in behavioral diagrams. As this requirement decomposition is progressed updates will be posted here and Eclipse IDE SysM: 2/0 Script will be posted at the bottom of this post.

			The other diagram types in SysML are structural and behavioral diagrams(See https://www.omgsysml.org/what-is-sysml.htm). These structural diagrams enable the sub-systems(organizations, tools, ect [things]) to be described. The behavioral diagrams are all about describing the activities, processes, and states(Verbs) the various structural elements will be engaged in. The combination of a methodology and the SysML language allows for systems to be rigorously and intentionally designed; simultaneously with the validation of business and stakeholder concerns tied back to the analyses conducted based on the parameters and processes of the system being designed.

	=Mon Jan 25, 2021=		=Mon Jan 25, 2021=

David Lemmer at 17:30, 30 April 2022

2022-04-30T17:30:31Z

← Older revision		Revision as of 17:30, 30 April 2022
Line 6:		Line 6:
	SysML is used to describe systems of all types at the level of detail needed for its intended purpose. Methodologies such as OOSEM (object oriented systems engineering methodology , https://www.incose.org/incose-member-resources/working-groups/transformational/object-oriented-se-method) provide a structured approach to describe systems or systems of systems using SysML.		SysML is used to describe systems of all types at the level of detail needed for its intended purpose. Methodologies such as OOSEM (object oriented systems engineering methodology , https://www.incose.org/incose-member-resources/working-groups/transformational/object-oriented-se-method) provide a structured approach to describe systems or systems of systems using SysML.

	~~[[Image~~:~~filename~~.png]]		https://wiki.opensourceecology.org/images/c/c9/OSE_Requirements_decomposition_4-30-2022.png

	The above diagram starts to decompose requirements that support the goals of OSE by identifying areas of critical function or performance that must be upheld if the objectives of OSE are to be achieved. In the MBSE(Model Based Systems Engineering) process these requirements are derived by examining and decomposing stakeholder needs or aspects of a system which must be achieved to deliver the performance needed. These requirements will then be used to compare against system components and the properties they posses to verify that these requirements met. Doing this allows for the design of the system to be more easily understood as it is going through early design phases. The MBSE approach also enables trade study to be conducted more easily through the ability to compare their cost schedule and performance within one model. SysML also enables systems engineering practitioners to model the components of the system in an environment or context while considering the system as it is engaged in particular processes. These are contexts are described by capturing the relevant inputs to the system and processes are described and documented in behavioral diagrams.		The above diagram starts to decompose requirements that support the goals of OSE by identifying areas of critical function or performance that must be upheld if the objectives of OSE are to be achieved. In the MBSE(Model Based Systems Engineering) process these requirements are derived by examining and decomposing stakeholder needs or aspects of a system which must be achieved to deliver the performance needed. These requirements will then be used to compare against system components and the properties they posses to verify that these requirements met. Doing this allows for the design of the system to be more easily understood as it is going through early design phases. The MBSE approach also enables trade study to be conducted more easily through the ability to compare their cost schedule and performance within one model. SysML also enables systems engineering practitioners to model the components of the system in an environment or context while considering the system as it is engaged in particular processes. These are contexts are described by capturing the relevant inputs to the system and processes are described and documented in behavioral diagrams.

David Lemmer at 17:27, 30 April 2022

2022-04-30T17:27:34Z

← Older revision		Revision as of 17:27, 30 April 2022
Line 6:		Line 6:
	SysML is used to describe systems of all types at the level of detail needed for its intended purpose. Methodologies such as OOSEM (object oriented systems engineering methodology , https://www.incose.org/incose-member-resources/working-groups/transformational/object-oriented-se-method) provide a structured approach to describe systems or systems of systems using SysML.		SysML is used to describe systems of all types at the level of detail needed for its intended purpose. Methodologies such as OOSEM (object oriented systems engineering methodology , https://www.incose.org/incose-member-resources/working-groups/transformational/object-oriented-se-method) provide a structured approach to describe systems or systems of systems using SysML.

	[[Image:filename.~~jpg~~]]		[[Image:filename.png]]

	The above diagram starts to decompose requirements that support the goals of OSE by identifying areas of critical function or performance that must be upheld if the objectives of OSE are to be achieved. In the MBSE(Model Based Systems Engineering) process these requirements are derived by examining and decomposing stakeholder needs or aspects of a system which must be achieved to deliver the performance needed. These requirements will then be used to compare against system components and the properties they posses to verify that these requirements met. Doing this allows for the design of the system to be more easily understood as it is going through early design phases. The MBSE approach also enables trade study to be conducted more easily through the ability to compare their cost schedule and performance within one model. SysML also enables systems engineering practitioners to model the components of the system in an environment or context while considering the system as it is engaged in particular processes. These are contexts are described by capturing the relevant inputs to the system and processes are described and documented in behavioral diagrams.		The above diagram starts to decompose requirements that support the goals of OSE by identifying areas of critical function or performance that must be upheld if the objectives of OSE are to be achieved. In the MBSE(Model Based Systems Engineering) process these requirements are derived by examining and decomposing stakeholder needs or aspects of a system which must be achieved to deliver the performance needed. These requirements will then be used to compare against system components and the properties they posses to verify that these requirements met. Doing this allows for the design of the system to be more easily understood as it is going through early design phases. The MBSE approach also enables trade study to be conducted more easily through the ability to compare their cost schedule and performance within one model. SysML also enables systems engineering practitioners to model the components of the system in an environment or context while considering the system as it is engaged in particular processes. These are contexts are described by capturing the relevant inputs to the system and processes are described and documented in behavioral diagrams.

David Lemmer at 17:21, 30 April 2022

2022-04-30T17:21:06Z

← Older revision		Revision as of 17:21, 30 April 2022
Line 6:		Line 6:
	SysML is used to describe systems of all types at the level of detail needed for its intended purpose. Methodologies such as OOSEM (object oriented systems engineering methodology , https://www.incose.org/incose-member-resources/working-groups/transformational/object-oriented-se-method) provide a structured approach to describe systems or systems of systems using SysML.		SysML is used to describe systems of all types at the level of detail needed for its intended purpose. Methodologies such as OOSEM (object oriented systems engineering methodology , https://www.incose.org/incose-member-resources/working-groups/transformational/object-oriented-se-method) provide a structured approach to describe systems or systems of systems using SysML.

	~~<<Insert Diagram here>>~~		[[Image:filename.jpg]]

	The above diagram starts to decompose requirements that support the goals of OSE by identifying areas of critical function or performance that must be upheld if the objectives of OSE are to be achieved. In the MBSE(Model Based Systems Engineering) process these requirements are derived by examining and decomposing stakeholder needs or aspects of a system which must be achieved to deliver the performance needed. These requirements will then be used to compare against system components and the properties they posses to verify that these requirements met. Doing this allows for the design of the system to be more easily understood as it is going through early design phases. The MBSE approach also enables trade study to be conducted more easily through the ability to compare their cost schedule and performance within one model. SysML also enables systems engineering practitioners to model the components of the system in an environment or context while considering the system as it is engaged in particular processes. These are contexts are described by capturing the relevant inputs to the system and processes are described and documented in behavioral diagrams.		The above diagram starts to decompose requirements that support the goals of OSE by identifying areas of critical function or performance that must be upheld if the objectives of OSE are to be achieved. In the MBSE(Model Based Systems Engineering) process these requirements are derived by examining and decomposing stakeholder needs or aspects of a system which must be achieved to deliver the performance needed. These requirements will then be used to compare against system components and the properties they posses to verify that these requirements met. Doing this allows for the design of the system to be more easily understood as it is going through early design phases. The MBSE approach also enables trade study to be conducted more easily through the ability to compare their cost schedule and performance within one model. SysML also enables systems engineering practitioners to model the components of the system in an environment or context while considering the system as it is engaged in particular processes. These are contexts are described by capturing the relevant inputs to the system and processes are described and documented in behavioral diagrams.

David Lemmer at 23:48, 26 April 2022

2022-04-26T23:48:10Z

← Older revision		Revision as of 23:48, 26 April 2022
Line 5:		Line 5:

	SysML is used to describe systems of all types at the level of detail needed for its intended purpose. Methodologies such as OOSEM (object oriented systems engineering methodology , https://www.incose.org/incose-member-resources/working-groups/transformational/object-oriented-se-method) provide a structured approach to describe systems or systems of systems using SysML.		SysML is used to describe systems of all types at the level of detail needed for its intended purpose. Methodologies such as OOSEM (object oriented systems engineering methodology , https://www.incose.org/incose-member-resources/working-groups/transformational/object-oriented-se-method) provide a structured approach to describe systems or systems of systems using SysML.

			<<Insert Diagram here>>

			The above diagram starts to decompose requirements that support the goals of OSE by identifying areas of critical function or performance that must be upheld if the objectives of OSE are to be achieved. In the MBSE(Model Based Systems Engineering) process these requirements are derived by examining and decomposing stakeholder needs or aspects of a system which must be achieved to deliver the performance needed. These requirements will then be used to compare against system components and the properties they posses to verify that these requirements met. Doing this allows for the design of the system to be more easily understood as it is going through early design phases. The MBSE approach also enables trade study to be conducted more easily through the ability to compare their cost schedule and performance within one model. SysML also enables systems engineering practitioners to model the components of the system in an environment or context while considering the system as it is engaged in particular processes. These are contexts are described by capturing the relevant inputs to the system and processes are described and documented in behavioral diagrams.

	=Mon Jan 25, 2021=		=Mon Jan 25, 2021=

David Lemmer at 11:19, 25 April 2022

2022-04-25T11:19:36Z

← Older revision		Revision as of 11:19, 25 April 2022
Line 1:		Line 1:
	<html><iframe width="600" height="400" src="https://osedev.org/wiki/David?start=9/1/2019"></iframe></html>		<html><iframe width="600" height="400" src="https://osedev.org/wiki/David?start=9/1/2019"></iframe></html>
			=Mon Apr 25, 2022=

			SysML is the abbreviation for systems modeling language, which is a structured modeling language developed and maintained by the Object Management Group (OMG, https://www.omg.org/). SysML 2.0 is the new version of SysML currently under development and scheduled to have a full version release in 2022. The ongoing SysML 2.0 pre-release efforts are maintained at https://github.com/Systems-Modeling/SysML-v2-Release with 2 tools that allow practitioners to download and use the current pre-release (the tools are jupyter notebook and eclipse IDE).

			SysML is used to describe systems of all types at the level of detail needed for its intended purpose. Methodologies such as OOSEM (object oriented systems engineering methodology , https://www.incose.org/incose-member-resources/working-groups/transformational/object-oriented-se-method) provide a structured approach to describe systems or systems of systems using SysML.

	=Mon Jan 25, 2021=		=Mon Jan 25, 2021=

Marcin: Marcin moved page David Log to David Lemmer Log over a redirect without leaving a redirect

2021-07-03T21:05:23Z

Marcin moved page David Log to David Lemmer Log over a redirect without leaving a redirect

← Older revision	Revision as of 21:05, 3 July 2021
(No difference)

Brad: /* Mon Jan 25, 2021 */ fixed typo

2021-01-26T02:35:27Z

Mon Jan 25, 2021: fixed typo

← Older revision		Revision as of 02:35, 26 January 2021
Line 6:		Line 6:
	I wanted to ask - could you produce a template for an Operations Manual for the Seed Home 2 Enterprise? As we discussed, core is building state of art houses at low cost - and training for builders and entrepreneurs. A critical enabling asset is the Operations Manual. We don't have a template for an ops manual. See 6.5 at https://wiki.opensourceecology.org/wiki/Seed_Home_v2#Enterprise, it's not well organized. Do you think you could come up with a template? This could be applied then to any enterprise, such as 3D printer production. See all prior work at		I wanted to ask - could you produce a template for an Operations Manual for the Seed Home 2 Enterprise? As we discussed, core is building state of art houses at low cost - and training for builders and entrepreneurs. A critical enabling asset is the Operations Manual. We don't have a template for an ops manual. See 6.5 at https://wiki.opensourceecology.org/wiki/Seed_Home_v2#Enterprise, it's not well organized. Do you think you could come up with a template? This could be applied then to any enterprise, such as 3D printer production. See all prior work at
	https://wiki.opensourceecology.org/wiki/Operations_Manual		https://wiki.opensourceecology.org/wiki/Operations_Manual
	The point is to ~~produce~~ a turnkey guide that helps people start an OSE franchise. So this thus follows all the protocols of collaboration that we use. It would use all the best practices available, and would be substance for a highly replicable regional and international franchise.		The point is to produce a turnkey guide that helps people start an OSE franchise. So this thus follows all the protocols of collaboration that we use. It would use all the best practices available, and would be substance for a highly replicable regional and international franchise.
	I put this on your log.		I put this on your log.
	MJ		MJ

Marcin: /* Tues Jul 21, 2020 */

2021-01-25T20:35:46Z

Tues Jul 21, 2020

← Older revision		Revision as of 20:35, 25 January 2021
Line 1:		Line 1:
	<html><iframe width="600" height="400" src="https://osedev.org/wiki/David?start=9/1/2019"></iframe></html>		<html><iframe width="600" height="400" src="https://osedev.org/wiki/David?start=9/1/2019"></iframe></html>

			=Mon Jan 25, 2021=
			Hi David,
			I don't know what you are up to - but if you can, continue logging on your log.
			I wanted to ask - could you produce a template for an Operations Manual for the Seed Home 2 Enterprise? As we discussed, core is building state of art houses at low cost - and training for builders and entrepreneurs. A critical enabling asset is the Operations Manual. We don't have a template for an ops manual. See 6.5 at https://wiki.opensourceecology.org/wiki/Seed_Home_v2#Enterprise, it's not well organized. Do you think you could come up with a template? This could be applied then to any enterprise, such as 3D printer production. See all prior work at
			https://wiki.opensourceecology.org/wiki/Operations_Manual
			The point is to produce a turnkey guide that helps people start an OSE franchise. So this thus follows all the protocols of collaboration that we use. It would use all the best practices available, and would be substance for a highly replicable regional and international franchise.
			I put this on your log.
			MJ

	=Tues Jul 21, 2020=		=Tues Jul 21, 2020=

David Lemmer: /* Tues Jul 21, 2020 */

2020-07-21T12:38:40Z

Tues Jul 21, 2020

← Older revision		Revision as of 12:38, 21 July 2020
Line 28:		Line 28:
	''		''

	We want to start with all those roles in that. That to me includes things like: Legal, contracts, zoning issues and permits, marketing copy, web design, product strategy, product management, sourcing, logistics, video, documentation, distribution, production, economic analysis - the whole shebang.		We want to start with all those roles in that. That to me includes things like - Legal, contracts, zoning issues and permits, marketing copy, web design, product strategy, product management, sourcing, logistics, video, documentation, distribution, production, economic analysis - the whole shebang.

	''One heuristic from the first SE lectures I'd attended comes to mind here : "In SE how do we eat the elephant? One bite at a time". So with a prioritization I can get after what is most relevant, for us (I think you'd laid that out in the previous sentences).''		''One heuristic from the first SE lectures I'd attended comes to mind here : "In SE how do we eat the elephant? One bite at a time". So with a prioritization I can get after what is most relevant, for us (I think you'd laid that out in the previous sentences).''
Line 46:		Line 46:

	V/r - David		V/r - David


	=Mon Jul 20, 2020=		=Mon Jul 20, 2020=