Update models/Application_examples/Knapsack_Weight_Limit.mp,...

Update models/Application_examples/Knapsack_Weight_Limit.mp, models/Application_examples/MP_Architecture_Specification.mp, models/Application_examples/Manufacturing_Process.mp, models/Application_examples/Martian_Lander.mp files

models/Application_examples/Knapsack_Weight_Limit.mp

 /* Model of Knapsack Weight Limit
 
-Created by Mikhail Auguston.
+Created by Mikhail Auguston in 2019.
 Edited by Keane Reynolds in July, 2021.
 Edited by Pamela Dyer in July and August, 2021.
 
@@ -27,15 +27,17 @@ Users can reference this model to learn about solving
 logic problems with MP constraints.
 
 References:
+"Example 47: “Brute force” search over the set of traces 
+for optimal value." from Auguston, M. "Monterey Phoenix 
+System and Software Architecture and Workflow Modeling 
+Language Manual" (Version 4). 2020. 
+Available online: 
+https://wiki.nps.edu/display/MP/Documentation
+
 "Knapsack problem." Wikipedia. Wikimedia Foundation, 
 August 26, 2021.
 https://en.wikipedia.org/wiki/Knapsack_problem
 
-
-**** Remove this part ****
-Information on computational complexity from Wikipedia at https://en.wikipedia.org/wiki/Knapsack_problem 
-********
-
 Search terms: event attribute, number; optimization, weight; 
 BUILD block; WITHIN command; report, global
 

models/Application_examples/MP_Architecture_Specification.mp

 /* Model of MP Architecture Specification
 
-Created by Mikhail Auguston.
+Created by Mikhail Auguston in 2018.
 Edited by Keane Reynolds in July, 2021.
 Edited by Pamela Dyer in July and August, 2021.
 
-Purpose: To illustrate an architecture model surrounding 
-the MP compiler/trace generator process.
+Purpose: To illustrate a physical architecture model of 
+the MP compiler/trace generator components built from the
+component behaviors.
 
 Description: This model demonstrates how a user might use 
-an MP IDE to develop an MP model. This model contains many 
-types of interactions and goes through the process of 
-making a model, so beginner and intermediate users may 
-find this model helpful for learning about the modeling 
-process or how specific MP statements (COORDINATE, IF, 
-SHARE ALL, SAY, GRAPH, etc.) can create relationships.
+an MP IDE to extract a component diagram from an MP model.
+It includes reusable code for building a component diagram.
 
-References:
+References: 
+Auguston, M. "Monterey Phoenix System and Software 
+Architecture and Workflow Modeling Language Manual" 
+(Version 4). 2020. Available online: 
+https://wiki.nps.edu/display/MP/Documentation
 
-Search terms: architecture; trace annotation; 
+Search terms: MP architecture; trace annotation; 
 behavior, compiler; behavior, parser; 
 graph, component diagram; report, global; isomorphism
 

models/Application_examples/Manufacturing_Process.mp

@@ -5,29 +5,27 @@ Edited by Keane Reynolds in July, 2021.
 Edited by Pamela Dyer in July and August, 2021.
 
 Purpose: To demonstrate a model of a system manufacturing 
-process, while taking advantage of being able to use 
-local scopes.
+process.
 
 Description: This model demonstrates application of Monterey 
 Phoenix Modeling to Manufacturing Product Systems. This is 
-an example pre-dating MP-Firebird application that was used 
-to generate scenarios for separately estimating probability, 
-time, and cost of each of these scenarios. MP version 4 
-may be used to conduct such analysis with its 
+an example pre-dating the MP-Firebird application that was 
+used to generate scenarios for separately estimating 
+probability, time, and cost of each of these scenarios. MP 
+version 4 may be used to conduct such analysis with its 
 native capabilities.
 
 Ultimately, this model demonstrates a manufacturing system 
-made from only standard ROOT statements, "or" blocks, 
-SHARE ALL statements, iteration, and scope limits. This 
-manufacturing system has several actors simultaniously 
-performing jobs, so users may look to this model for 
-a simple way of designing a system.
+made from standard ROOT statements, "or" logic, SHARE ALL 
+statements, iteration, and scope limits. This manufacturing 
+system has several actors simultaniously performing jobs, 
+so users may look to this model for a simple way of 
+designing a system.
 
 References:
 
-Search terms: behavior, manufacturing process; 
-manufacturing system; event sharing; probability analysis; 
-nested iteration
+Search terms: behavior, manufacturing process; event sharing; 
+local scope; nested iteration
 
 Instructions: Run for Scope 1.
 	Scope 1: 8 traces in approx. 1.4 min.

models/Application_examples/Martian_Lander.mp

@@ -58,12 +58,11 @@ CKDT 	10
 RRM 	10
 
 In summary, this model demonstrates the use of COORDINATE 
-statements to model the relationships of an unlikely and 
-unfamiliar situation, and then make the situation easier 
-to understand using charts and "comments" from 
-SAY statements. Users can reference this model for advice 
-on COORDINATE statements and using MP to add graphs and 
-commentary to traces automatically.
+statements to model the relationships of landing events
+and make those events easier to understand using charts 
+and "comments" from SAY statements. Users can reference 
+this model for advice on COORDINATE statements and using 
+MP to add graphs and commentary to traces automatically.
 
 References:
 Jahanian, Farnam, and Aloysius Ka-Lau Mok. "Safety Analysis 
@@ -73,18 +72,9 @@ Transactions on Software Engineering SE-12, no. 9 (1986):
 https://doi.org/10.1109/tse.1986.6313045
 https://ieeexplore.ieee.org/document/6313045
 
-
-**** Remove this part ****
-Farnam Jahanian, Aloysius Ka-Lau Mok 
-"Safety analysis of timing properties in real-time systems",
-IEEE Transactions on Software Engineering
-Year: 1986, Volume SE-12, Issue 9, pp.890-904
-********
-
-Search terms: Martian Lander system; 
-behavior, landing system; event attribute, timing; 
-trace annotation; table; graph, Gantt chart; 
-graph, bar chart
+Search terms: behavior, Martian Lander system; 
+event attribute, timing; trace annotation; 
+table; graph, Gantt chart; graph, bar chart
 
 Instructions: Run for Scopes 1 and up.
 	Scope 1: 3 traces in less than 1 sec.