Projects:2016s1-126 A Trash Collecting Robot - Revision history

A1627823: /* Cost Analysis */

2016-10-26T03:48:13Z

‎Cost Analysis

A1627823: /* Cost Analysis */

2016-10-26T03:47:33Z

‎Cost Analysis

A1627823: /* Cost Analysis */

2016-10-26T03:46:58Z

‎Cost Analysis

A1627823: /* Cost Analysis */

2016-10-26T03:46:26Z

‎Cost Analysis

A1627823: /* Cost Analysis */

2016-10-26T03:36:34Z

‎Cost Analysis

A1627823: /* Cost Analysis */

2016-10-26T03:35:05Z

‎Cost Analysis

A1627823: /* Cost Analysis */

2016-10-26T03:32:22Z

‎Cost Analysis

A1627823: /* Cost analysis */

2016-10-26T03:31:51Z

‎Cost analysis

A1628411: /* Trust and Testing */

2016-10-26T01:35:15Z

‎Trust and Testing

A1628411: /* Trust and Testing */

2016-10-26T01:34:28Z

‎Trust and Testing

← Older revision		Revision as of 03:48, 26 October 2016
Line 51:		Line 51:

	In the traditional systems engineering process, there is often disconnect between what designers decide and what is actually feasible. This usually leads to decision makers having a hard time dealing with a limited budget. Thus, system costs should be considered iteratively and should influence design decisions from the very start of development to find cost-effective solutions to requirements. However, it is often hard to make accurate cost estimates in the early phases due to the lack of design information. In addition, in formal contract projects, when system costs and schedules are in place, system trades become limited. This leads to less options for system candidates and alternatives.		In the traditional systems engineering process, there is often disconnect between what designers decide and what is actually feasible. This usually leads to decision makers having a hard time dealing with a limited budget. Thus, system costs should be considered iteratively and should influence design decisions from the very start of development to find cost-effective solutions to requirements. However, it is often hard to make accurate cost estimates in the early phases due to the lack of design information. In addition, in formal contract projects, when system costs and schedules are in place, system trades become limited. This leads to less options for system candidates and alternatives.
		+
	[[File:cost_graph.jpg\|600px]]		[[File:cost_graph.jpg\|600px]]

@@ Line 51: / Line 51: @@
 In the traditional systems engineering process, there is often disconnect between what designers decide and what is actually feasible. This usually leads to decision makers having a hard time dealing with a limited budget. Thus, system costs should be considered iteratively and should influence design decisions from the very start of development to find cost-effective solutions to requirements. However, it is often hard to make accurate cost estimates in the early phases due to the lack of design information. In addition, in formal contract projects, when system costs and schedules are in place, system trades become limited. This leads to less options for system candidates and alternatives.
-[[File:cost_graph.jpg]]
+[[File:cost_graph.jpg|600px]]
 ===Control and Simulation====

@@ Line 51: / Line 51: @@
 In the traditional systems engineering process, there is often disconnect between what designers decide and what is actually feasible. This usually leads to decision makers having a hard time dealing with a limited budget. Thus, system costs should be considered iteratively and should influence design decisions from the very start of development to find cost-effective solutions to requirements. However, it is often hard to make accurate cost estimates in the early phases due to the lack of design information. In addition, in formal contract projects, when system costs and schedules are in place, system trades become limited. This leads to less options for system candidates and alternatives.
-[[File:cost_analysis.jpg]]
+[[File:cost_graph.jpg]]
 ===Control and Simulation====

@@ Line 51: / Line 51: @@
 In the traditional systems engineering process, there is often disconnect between what designers decide and what is actually feasible. This usually leads to decision makers having a hard time dealing with a limited budget. Thus, system costs should be considered iteratively and should influence design decisions from the very start of development to find cost-effective solutions to requirements. However, it is often hard to make accurate cost estimates in the early phases due to the lack of design information. In addition, in formal contract projects, when system costs and schedules are in place, system trades become limited. This leads to less options for system candidates and alternatives.
-[[File:graph1.jpg]]
+[[File:cost_analysis.jpg]]
 ===Control and Simulation====

@@ Line 51: / Line 51: @@
 In the traditional systems engineering process, there is often disconnect between what designers decide and what is actually feasible. This usually leads to decision makers having a hard time dealing with a limited budget. Thus, system costs should be considered iteratively and should influence design decisions from the very start of development to find cost-effective solutions to requirements. However, it is often hard to make accurate cost estimates in the early phases due to the lack of design information. In addition, in formal contract projects, when system costs and schedules are in place, system trades become limited. This leads to less options for system candidates and alternatives.
-[[File:Example.jpg]]
+[[File:graph1.jpg]]
 ===Control and Simulation====

← Older revision		Revision as of 03:35, 26 October 2016
Line 51:		Line 51:

	In the traditional systems engineering process, there is often disconnect between what designers decide and what is actually feasible. This usually leads to decision makers having a hard time dealing with a limited budget. Thus, system costs should be considered iteratively and should influence design decisions from the very start of development to find cost-effective solutions to requirements. However, it is often hard to make accurate cost estimates in the early phases due to the lack of design information. In addition, in formal contract projects, when system costs and schedules are in place, system trades become limited. This leads to less options for system candidates and alternatives.		In the traditional systems engineering process, there is often disconnect between what designers decide and what is actually feasible. This usually leads to decision makers having a hard time dealing with a limited budget. Thus, system costs should be considered iteratively and should influence design decisions from the very start of development to find cost-effective solutions to requirements. However, it is often hard to make accurate cost estimates in the early phases due to the lack of design information. In addition, in formal contract projects, when system costs and schedules are in place, system trades become limited. This leads to less options for system candidates and alternatives.
		+	[[File:Example.jpg]]

	===Control and Simulation====		===Control and Simulation====

@@ Line 48: / Line 48: @@
 ===Cost Analysis===
-According to the NASA Langley Research Center, critical concept assumptions and choices made during the initial phase of projects determine roughly 70% of the final system life cycle cost. However, cost is usually estimated only after an engineering design process is completed [12]. This often results in difficulty in acquiring cost-effective, high performance systems, as well as cost overruns- which may lead to cancellation of projects.
+According to the NASA Langley Research Center, critical concept assumptions and choices made during the initial phase of projects determine roughly 70% of the final system life cycle cost. However, cost is usually estimated only after an engineering design process is completed. This often results in difficulty in acquiring cost-effective, high performance systems, as well as cost overruns- which may lead to cancellation of projects.
 In the traditional systems engineering process, there is often disconnect between what designers decide and what is actually feasible. This usually leads to decision makers having a hard time dealing with a limited budget. Thus, system costs should be considered iteratively and should influence design decisions from the very start of development to find cost-effective solutions to requirements. However, it is often hard to make accurate cost estimates in the early phases due to the lack of design information. In addition, in formal contract projects, when system costs and schedules are in place, system trades become limited. This leads to less options for system candidates and alternatives.

@@ Line 47: / Line 47: @@
 It was discovered later that a legal hierarchy made up the building blocks to address these fields. This helped to further refine research until specific measures could be derived. The bottom two tiers are documents/methods to ensure compliance, whereas the top two tiers are ways governance is shown.
-===Cost analysis===
+===Cost Analysis===
 ===Control and Simulation====

@@ Line 41: / Line 41: @@
 Derived measures:
-[[File:Capture.png|600px]]]
+[[File:Capture.png|600px]]] [[File:illuminati.png|400px|thumb]]
 The cells in grey are those measures that are common with collated research and those developed by the project group.
-It was discovered later that a legal hierarchy made up the building blocks to address these fields. This helped to further refine research until specific measures could be derived.
+It was discovered later that a legal hierarchy made up the building blocks to address these fields. This helped to further refine research until specific measures could be derived. The bottom two tiers are documents/methods to ensure compliance, whereas the top two tiers are ways governance is shown.
 ===Cost analysis===