{
"name": "Engineering",
"data": {
"monitor system performance": {
"id": 1150,
"nterm": "operation"
},
"verification constraint": {
"id": 1089,
"nterm": "life cycle constraints"
},
"@apress source code": {
"id": 78,
"nterm": "@apress source code"
},
"interconnected multi-domain interactive cyber-physical intelligent system": {
"id": 1351,
"nterm": "validated system"
},
"life cycle framework": {
"id": 1093,
"nterm": "life cycle models"
},
"@iec 62890": {
"id": 349,
"nterm": "@iec 62890"
},
"@reengineering the corporation manifesto for business revolution": {
"id": 633,
"nterm": "@reengineering the corporation manifesto for business revolution"
},
"@relational contract": {
"id": 636,
"nterm": "@relational contract"
},
"@activity diagram editor": {
"id": 46,
"nterm": "@activity diagram editor"
},
"@situations and attitudes": {
"id": 691,
"nterm": "@situations and attitudes"
},
"@a cultural-historical approach to distributed cognition": {
"id": 30,
"nterm": "@a cultural-historical approach to distributed cognition"
},
"measurement": {
"id": 1134,
"nterm": "measurement"
},
"define the problem or opportunity space": {
"id": 1008,
"nterm": "define the problem or opportunity space"
},
"manual production diagnosis": {
"id": 1149,
"nterm": "operation strategy"
},
"@which are the wastes of construction": {
"id": 910,
"nterm": "@which are the wastes of construction"
},
"configuration management": {
"id": 989,
"nterm": "configuration management"
},
"@major bridge projects—a multi-disciplinary approach": {
"id": 473,
"nterm": "@major bridge projects—a multi-disciplinary approach"
},
"quality management": {
"id": 1249,
"nterm": "quality management"
},
"asset management": {
"id": 964,
"nterm": "asset management"
},
"@37 things one architect knows about it transformation a chief architect journey": {
"id": 4,
"nterm": "@37 things one architect knows about it transformation a chief architect journey"
},
"plan configuration management": {
"id": 1186,
"nterm": "plan configuration management"
},
"rfq": {
"id": 934,
"nterm": "acquisition need"
},
"@patterns of success in systems engineering acquisition of it-intensive government systems": {
"id": 562,
"nterm": "@patterns of success in systems engineering acquisition of it-intensive government systems"
},
"@fundamental uncertainties in projects and the scope of project management": {
"id": 297,
"nterm": "@fundamental uncertainties in projects and the scope of project management"
},
"@the nature of product": {
"id": 784,
"nterm": "@the nature of product"
},
"@measuring vulnerabilities and their exploitation cycle": {
"id": 496,
"nterm": "@measuring vulnerabilities and their exploitation cycle"
},
"information repository": {
"id": 1064,
"nterm": "information repository"
},
"@the national system of scientific measurement": {
"id": 783,
"nterm": "@the national system of scientific measurement"
},
"@toward an understanding of how post- deployment user- developer interactions influence system utilization": {
"id": 868,
"nterm": "@toward an understanding of how post- deployment user- developer interactions influence system utilization"
},
"maintenance constraints": {
"id": 1103,
"nterm": "maintenance constraints"
},
"@corbin on contracts": {
"id": 171,
"nterm": "@corbin on contracts"
},
"@developing high quality data models": {
"id": 208,
"nterm": "@developing high quality data models"
},
"@actor-network theory. objects and actants, networks and narratives": {
"id": 47,
"nterm": "@actor-network theory. objects and actants, networks and narratives"
},
"enhance the level of maintenance management": {
"id": 1149,
"nterm": "operation strategy"
},
"@modularity as a support for frugal product and supplier network co-definition": {
"id": 514,
"nterm": "@modularity as a support for frugal product and supplier network co-definition"
},
"@reference ontology for semantic service oriented architectures": {
"id": 634,
"nterm": "@reference ontology for semantic service oriented architectures"
},
"@formalizing requirements verification and validation": {
"id": 286,
"nterm": "@formalizing requirements verification and validation"
},
"@exploring the structure of complex software designs an empirical study of open source and proprietary code": {
"id": 269,
"nterm": "@exploring the structure of complex software designs an empirical study of open source and proprietary code"
},
"@the business case for systems engineering study results of the systems engineering effectiveness survey": {
"id": 808,
"nterm": "@the business case for systems engineering study results of the systems engineering effectiveness survey"
},
"project timeline": {
"id": 1243,
"nterm": "project schedule"
},
"@corbin on contracts volume two": {
"id": 170,
"nterm": "@corbin on contracts volume two"
},
"@perfection by subtraction – the minimum feature set": {
"id": 565,
"nterm": "@perfection by subtraction – the minimum feature set"
},
"@pro excel financial modeling": {
"id": 583,
"nterm": "@pro excel financial modeling"
},
"project schedule": {
"id": 1243,
"nterm": "project schedule"
},
"@the product manager toolkit": {
"id": 792,
"nterm": "@the product manager toolkit"
},
"assess quality management": {
"id": 962,
"nterm": "assess quality management"
},
"maintenance service module": {
"id": 1351,
"nterm": "validated system"
},
"@magma core": {
"id": 472,
"nterm": "@magma core"
},
"@dstl ies4": {
"id": 926,
"nterm": "@dstl ies4"
},
"preventive measure": {
"id": 1246,
"nterm": "qm corrective actions"
},
"@the digital twin capabilities periodic table (cpt)": {
"id": 762,
"nterm": "@the digital twin capabilities periodic table (cpt)"
},
"@the innovator's dilemma when new technologies cause great firms to fail": {
"id": 775,
"nterm": "@the innovator's dilemma when new technologies cause great firms to fail"
},
"@managing knowledge in loosely coupled networks exploring the links between product and knowledge dynamics": {
"id": 486,
"nterm": "@managing knowledge in loosely coupled networks exploring the links between product and knowledge dynamics"
},
"@corbin on contracts volume five": {
"id": 167,
"nterm": "@corbin on contracts volume five"
},
"high operation and maintenance risk": {
"id": 1145,
"nterm": "operation constraints"
},
"@five worlds – joel on software": {
"id": 281,
"nterm": "@five worlds – joel on software"
},
"stakeholder requirements traceability": {
"id": 1293,
"nterm": "stakeholder requirements traceability"
},
"perform configuration change management": {
"id": 1164,
"nterm": "perform configuration change management"
},
"@handbook of research on electronic collaboration and organizational synergy": {
"id": 317,
"nterm": "@handbook of research on electronic collaboration and organizational synergy"
},
"@contracting for innovation vertical disintegration and interfirm collaboration": {
"id": 161,
"nterm": "@contracting for innovation vertical disintegration and interfirm collaboration"
},
"@reminiscences of the vlsi revolution how a series of failures triggered a paradigm shift in digital design": {
"id": 640,
"nterm": "@reminiscences of the vlsi revolution how a series of failures triggered a paradigm shift in digital design"
},
"@sbvr business rules generation from natural language specification": {
"id": 671,
"nterm": "@sbvr business rules generation from natural language specification"
},
"@handbook of service science, volume ii": {
"id": 316,
"nterm": "@handbook of service science, volume ii"
},
"mbse": {
"id": 1099,
"nterm": "mbse"
},
"@an introduction to the history of project management from the earliest times to ad 1900": {
"id": 68,
"nterm": "@an introduction to the history of project management from the earliest times to ad 1900"
},
"project funds": {
"id": 1227,
"nterm": "project budget"
},
"prepare for business or mission analysis": {
"id": 1203,
"nterm": "prepare for business or mission analysis"
},
"@mastering archimate edition iii a serious introduction to the archimate enterprise architecture modeling language": {
"id": 493,
"nterm": "@mastering archimate edition iii a serious introduction to the archimate enterprise architecture modeling language"
},
"@everyday engineering an ethnography of design and innovation": {
"id": 256,
"nterm": "@everyday engineering an ethnography of design and innovation"
},
"life cycle methodology": {
"id": 1093,
"nterm": "life cycle models"
},
"daily checks": {
"id": 1172,
"nterm": "perform maintenance"
},
"@text into obsidian without the app at last": {
"id": 745,
"nterm": "@text into obsidian without the app at last"
},
"@requirements engineering in the problem domain": {
"id": 645,
"nterm": "@requirements engineering in the problem domain"
},
"integration constraints": {
"id": 1073,
"nterm": "integration constraints"
},
"@the inconvenient truth about product": {
"id": 774,
"nterm": "@the inconvenient truth about product"
},
"trade studies": {
"id": 1336,
"nterm": "trade studies"
},
"@finding the next company to work at": {
"id": 279,
"nterm": "@finding the next company to work at"
},
"@evaluating fair maturity through a scalable, automated, community-governed framework": {
"id": 254,
"nterm": "@evaluating fair maturity through a scalable, automated, community-governed framework"
},
"@dr walid saba - why machines will never rule the world": {
"id": 231,
"nterm": "@dr walid saba - why machines will never rule the world"
},
"@institutions, information processing, and organization structure in research and development evidence from the semiconductor industry": {
"id": 413,
"nterm": "@institutions, information processing, and organization structure in research and development evidence from the semiconductor industry"
},
"architecture definition": {
"id": 954,
"nterm": "architecture definition"
},
"explicit management support": {
"id": 1041,
"nterm": "explicit management support"
},
"@network structure and business survival the case of us automobile component suppliers": {
"id": 525,
"nterm": "@network structure and business survival the case of us automobile component suppliers"
},
"@brownfield systems development moving from the vee model to the n model for legacy systems": {
"id": 106,
"nterm": "@brownfield systems development moving from the vee model to the n model for legacy systems"
},
"conceptual design using mbse": {
"id": 987,
"nterm": "conceptual design using mbse"
},
"@xaas (anything as a service) glossary": {
"id": 922,
"nterm": "@xaas (anything as a service) glossary"
},
"safety assurance of the oil and gas production system": {
"id": 1149,
"nterm": "operation strategy"
},
"report on performance during operations": {
"id": 1116,
"nterm": "manage results of operation"
},
"@a comprehensive review of digital twin–part 1 modeling and twinning enabling technologies": {
"id": 10,
"nterm": "@a comprehensive review of digital twin–part 1 modeling and twinning enabling technologies"
},
"@steve jobs - the lost interview": {
"id": 708,
"nterm": "@steve jobs - the lost interview"
},
"@using the sose principles framework": {
"id": 892,
"nterm": "@using the sose principles framework"
},
"@how to infrastructure": {
"id": 344,
"nterm": "@how to infrastructure"
},
"mission and vision": {
"id": 1296,
"nterm": "strategy documents"
},
"@the many lies about reducing complexity part 2 cloud": {
"id": 828,
"nterm": "@the many lies about reducing complexity part 2 cloud"
},
"problem management": {
"id": 1220,
"nterm": "problem management"
},
"@rules and implements investment in forms": {
"id": 669,
"nterm": "@rules and implements investment in forms"
},
"prepare for operation": {
"id": 1210,
"nterm": "prepare for operation"
},
"@characterizing design process interfaces as organization networks insights for engineering systems management": {
"id": 132,
"nterm": "@characterizing design process interfaces as organization networks insights for engineering systems management"
},
"capability characteristic.": {
"id": 1196,
"nterm": "preliminary moe needs"
},
"sales order": {
"id": 1288,
"nterm": "source documents"
},
"@digital twin consortium": {
"id": 218,
"nterm": "@digital twin consortium"
},
"transition report": {
"id": 1342,
"nterm": "transition report"
},
"@failure doesnt respect abstraction": {
"id": 274,
"nterm": "@failure doesnt respect abstraction"
},
"manage qa records and reports": {
"id": 1111,
"nterm": "manage qa records and reports"
},
"@capabilities, transaction costs, and firm boundaries": {
"id": 123,
"nterm": "@capabilities, transaction costs, and firm boundaries"
},
"@mbse methodologies": {
"id": 468,
"nterm": "@mbse methodologies"
},
"system performance test result": {
"id": 1197,
"nterm": "preliminary tpm data"
},
"unified processing of the oil and gas production system": {
"id": 1149,
"nterm": "operation strategy"
},
"service parts provisioning": {
"id": 1171,
"nterm": "perform logistics support"
},
"virtual environment for drilling and development": {
"id": 1146,
"nterm": "operation enabling system requirements"
},
"@let bury nists outdated definition of cloud computing": {
"id": 458,
"nterm": "@let bury nists outdated definition of cloud computing"
},
"@is agile project management applicable to construction": {
"id": 433,
"nterm": "@is agile project management applicable to construction"
},
"wbs": {
"id": 1372,
"nterm": "work breakdown structure"
},
"evolving needs of owning and operating": {
"id": 1145,
"nterm": "operation constraints"
},
"@survey report improving integration of program management and systems engineering": {
"id": 718,
"nterm": "@survey report improving integration of program management and systems engineering"
},
"@platform and ecosystem transitions strategic and organizational implications": {
"id": 571,
"nterm": "@platform and ecosystem transitions strategic and organizational implications"
},
"@how i prepared for meta pm interviews": {
"id": 327,
"nterm": "@how i prepared for meta pm interviews"
},
"@the accidental taxonomist, third edition": {
"id": 748,
"nterm": "@the accidental taxonomist, third edition"
},
"real-time monitoring": {
"id": 1146,
"nterm": "operation enabling system requirements"
},
"@theory of the border": {
"id": 861,
"nterm": "@theory of the border"
},
"cause and evolution process of risk": {
"id": 1149,
"nterm": "operation strategy"
},
"re-configuration of the system": {
"id": 1172,
"nterm": "perform maintenance"
},
"support and test equipment (ste)": {
"id": 1104,
"nterm": "maintenance enabling system"
},
"@integration of cost and work breakdown structures in the management of construction projects": {
"id": 423,
"nterm": "@integration of cost and work breakdown structures in the management of construction projects"
},
"@guide to writing requirements rev 4": {
"id": 313,
"nterm": "@guide to writing requirements rev 4"
},
"risk management": {
"id": 1267,
"nterm": "risk management"
},
"plan knowledge management": {
"id": 1187,
"nterm": "plan knowledge management"
},
"performance standard": {
"id": 1184,
"nterm": "performance standard"
},
"@storytelling as a key enabler for systems engineering": {
"id": 709,
"nterm": "@storytelling as a key enabler for systems engineering"
},
"organization responsible for maintaining the system": {
"id": 1337,
"nterm": "trained operators and maintainers"
},
"@in software, the product is the experience": {
"id": 403,
"nterm": "@in software, the product is the experience"
},
"validation strategy": {
"id": 1358,
"nterm": "validation strategy"
},
"@applying product usage information to optimise the product lifecycle in the clothing and textiles industry": {
"id": 75,
"nterm": "@applying product usage information to optimise the product lifecycle in the clothing and textiles industry"
},
"@aditi a systems view of knowledge processes": {
"id": 50,
"nterm": "@aditi a systems view of knowledge processes"
},
"requirements flowdown and traceability": {
"id": 1265,
"nterm": "requirements flowdown and traceability"
},
"@mission engineering, digital engineering, mbse, and the like": {
"id": 507,
"nterm": "@mission engineering, digital engineering, mbse, and the like"
},
"@iso 81346-12": {
"id": 360,
"nterm": "@iso 81346-12"
},
"initial requirements for maintenance": {
"id": 1088,
"nterm": "life cycle concepts"
},
"qualified personnel": {
"id": 1247,
"nterm": "qualified personnel"
},
"@shortening the product development cycle": {
"id": 683,
"nterm": "@shortening the product development cycle"
},
"intelligent inspection": {
"id": 1149,
"nterm": "operation strategy"
},
"perform disposal": {
"id": 1168,
"nterm": "perform disposal"
},
"measurement repository": {
"id": 1132,
"nterm": "measurement repository"
},
"@a 4-dimensionalist top level ontology (tlo) mereotopology and space-time": {
"id": 6,
"nterm": "@a 4-dimensionalist top level ontology (tlo) mereotopology and space-time"
},
"organisational capability development": {
"id": 1152,
"nterm": "organisational capability development"
},
"verification constraints": {
"id": 1360,
"nterm": "verification constraints"
},
"respond to a tender": {
"id": 1266,
"nterm": "respond to a tender"
},
"@machine interpretable representation of commander intent": {
"id": 471,
"nterm": "@machine interpretable representation of commander intent"
},
"efficiency improvement of the oil and gas production system": {
"id": 1149,
"nterm": "operation strategy"
},
"@here’s why enterprise it is so complex": {
"id": 320,
"nterm": "@here’s why enterprise it is so complex"
},
"@why enterprise search fails in most cases and how to fix it": {
"id": 912,
"nterm": "@why enterprise search fails in most cases and how to fix it"
},
"@designed for digital how to architect your business for sustained success": {
"id": 199,
"nterm": "@designed for digital how to architect your business for sustained success"
},
"@iso iec 25010": {
"id": 366,
"nterm": "@iso iec 25010"
},
"strategic map": {
"id": 1296,
"nterm": "strategy documents"
},
"@iso iec 24773-1": {
"id": 364,
"nterm": "@iso iec 24773-1"
},
"disposal": {
"id": 1028,
"nterm": "disposal"
},
"@requirements interchange format reqif": {
"id": 643,
"nterm": "@requirements interchange format reqif"
},
"@ontology goodness measurement": {
"id": 539,
"nterm": "@ontology goodness measurement"
},
"@metadata encoding and transmission standard schema and documentation": {
"id": 505,
"nterm": "@metadata encoding and transmission standard schema and documentation"
},
"@documenting software architectures in an agile world": {
"id": 227,
"nterm": "@documenting software architectures in an agile world"
},
"@the structure of agile development under scaled planning and coordination": {
"id": 799,
"nterm": "@the structure of agile development under scaled planning and coordination"
},
"state the project": {
"id": 1009,
"nterm": "define the project"
},
"@the value and costs of modularity a problem-solving perspective": {
"id": 852,
"nterm": "@the value and costs of modularity a problem-solving perspective"
},
"performance review": {
"id": 1183,
"nterm": "performance review"
},
"@software architecture metrics a literature review": {
"id": 695,
"nterm": "@software architecture metrics a literature review"
},
"@framework for a generic work breakdown structure for building projects": {
"id": 289,
"nterm": "@framework for a generic work breakdown structure for building projects"
},
"@reverse engineer to go farther and faster": {
"id": 655,
"nterm": "@reverse engineer to go farther and faster"
},
"verification procedure": {
"id": 1365,
"nterm": "verification procedure"
},
"program budget": {
"id": 1227,
"nterm": "project budget"
},
"acceptance testing": {
"id": 929,
"nterm": "acceptance testing"
},
"tpm needs": {
"id": 1332,
"nterm": "tpm needs"
},
"@hire a top performer every time with these interview questions": {
"id": 321,
"nterm": "@hire a top performer every time with these interview questions"
},
"@the association of international product marketing & management (aipmm)": {
"id": 752,
"nterm": "@the association of international product marketing & management (aipmm)"
},
"@transaction cost economics in the digital economy a research agenda": {
"id": 874,
"nterm": "@transaction cost economics in the digital economy a research agenda"
},
"@level 1 document object model specification": {
"id": 461,
"nterm": "@level 1 document object model specification"
},
"problem definition": {
"id": 973,
"nterm": "business or mission analysis"
},
"infrastructure management": {
"id": 1066,
"nterm": "infrastructure management"
},
"documentation hierarchy": {
"id": 1031,
"nterm": "documentation tree"
},
"@the entrepreneurs and engineers in china the situation in the long 1980s": {
"id": 765,
"nterm": "@the entrepreneurs and engineers in china the situation in the long 1980s"
},
"@a design framework and exemplar metrics for fairness": {
"id": 32,
"nterm": "@a design framework and exemplar metrics for fairness"
},
"@calling bullshit the art of skepticism in a data-driven world": {
"id": 118,
"nterm": "@calling bullshit the art of skepticism in a data-driven world"
},
"@company business model": {
"id": 145,
"nterm": "@company business model"
},
"@the guide to the product management and marketing body of knowledge": {
"id": 770,
"nterm": "@the guide to the product management and marketing body of knowledge"
},
"credit card sales voucher": {
"id": 1288,
"nterm": "source documents"
},
"@taming the unpredictable real world adaptive case management case studies and practical guidance": {
"id": 734,
"nterm": "@taming the unpredictable real world adaptive case management case studies and practical guidance"
},
"supporting documents": {
"id": 1288,
"nterm": "source documents"
},
"@azure annual devops report - enterprise devops reporе 2020-21": {
"id": 90,
"nterm": "@azure annual devops report - enterprise devops reporе 2020-21"
},
"@the myth of the line fords production of the model t at highland park, 1909–16": {
"id": 832,
"nterm": "@the myth of the line fords production of the model t at highland park, 1909–16"
},
"@iso iec 26580": {
"id": 371,
"nterm": "@iso iec 26580"
},
"@work breakdown structure (wbs) - acqnotes": {
"id": 918,
"nterm": "@work breakdown structure (wbs) - acqnotes"
},
"describe the project": {
"id": 1009,
"nterm": "define the project"
},
"@technical aspects of cyber kill chain": {
"id": 736,
"nterm": "@technical aspects of cyber kill chain"
},
"stakeholder needs and requirements definition": {
"id": 1289,
"nterm": "stakeholder needs and requirements definition"
},
"@software and organisations the biography of the enterprise-wide system or how sap conquered the world": {
"id": 698,
"nterm": "@software and organisations the biography of the enterprise-wide system or how sap conquered the world"
},
"validation enabling system requirements": {
"id": 1354,
"nterm": "validation enabling system requirements"
},
"@from dark scrum to broken safe — some real problems of agile-at-scale and a way out": {
"id": 291,
"nterm": "@from dark scrum to broken safe — some real problems of agile-at-scale and a way out"
},
"@critical chain": {
"id": 177,
"nterm": "@critical chain"
},
"installed system": {
"id": 1071,
"nterm": "installed system"
},
"@global product strategy, product lifecycle management and the billion customer question": {
"id": 304,
"nterm": "@global product strategy, product lifecycle management and the billion customer question"
},
"@beyond the mirroring hypothesis product modularity and interorganizational relations in the air conditioning industry": {
"id": 98,
"nterm": "@beyond the mirroring hypothesis product modularity and interorganizational relations in the air conditioning industry"
},
"credit note": {
"id": 1288,
"nterm": "source documents"
},
"risk record": {
"id": 1269,
"nterm": "risk record"
},
"@secrets to mastering the wbs in real-world projects": {
"id": 678,
"nterm": "@secrets to mastering the wbs in real-world projects"
},
"@the mirroring hypothesis theory, evidence and exceptions": {
"id": 829,
"nterm": "@the mirroring hypothesis theory, evidence and exceptions"
},
"@a framework for describing project management office (pmo) functions and types": {
"id": 12,
"nterm": "@a framework for describing project management office (pmo) functions and types"
},
"rfp": {
"id": 934,
"nterm": "acquisition need"
},
"@causal relata tokens, types, or variables": {
"id": 127,
"nterm": "@causal relata tokens, types, or variables"
},
"implementation strategy": {
"id": 1296,
"nterm": "strategy documents"
},
"service life extension program": {
"id": 1150,
"nterm": "operation"
},
"@unique, persistent, resolvable identifiers as the foundation of fair": {
"id": 887,
"nterm": "@unique, persistent, resolvable identifiers as the foundation of fair"
},
"@unpacking the black box of modularity technologies, products and organizations": {
"id": 888,
"nterm": "@unpacking the black box of modularity technologies, products and organizations"
},
"@skills foresighting – automotive industrial digitisation case study": {
"id": 692,
"nterm": "@skills foresighting – automotive industrial digitisation case study"
},
"system architecture description": {
"id": 1313,
"nterm": "system architecture description"
},
"@manufacturing the future workforce": {
"id": 489,
"nterm": "@manufacturing the future workforce"
},
"system characteristic": {
"id": 1196,
"nterm": "preliminary moe needs"
},
"@personal knowledge models with semantic technologies": {
"id": 566,
"nterm": "@personal knowledge models with semantic technologies"
},
"process safety": {
"id": 1149,
"nterm": "operation strategy"
},
"decision management strategy": {
"id": 1296,
"nterm": "strategy documents"
},
"plan project and technical management": {
"id": 1188,
"nterm": "plan project and technical management"
},
"@are really new product development projects harder to shut down": {
"id": 84,
"nterm": "@are really new product development projects harder to shut down"
},
"@organisational design the work-levels approach": {
"id": 543,
"nterm": "@organisational design the work-levels approach"
},
"prepare for maintenance": {
"id": 1209,
"nterm": "prepare for maintenance"
},
"@the fair guiding principles for scientific data management and stewardship": {
"id": 767,
"nterm": "@the fair guiding principles for scientific data management and stewardship"
},
"@using pmfsurvey product-market fit 40 principle": {
"id": 891,
"nterm": "@using pmfsurvey product-market fit 40 principle"
},
"measures of effectiveness needs": {
"id": 1101,
"nterm": "moe needs"
},
"organizational process performance measures needs": {
"id": 1161,
"nterm": "organizational process performance measures needs"
},
"@iso iec 24773-3": {
"id": 365,
"nterm": "@iso iec 24773-3"
},
"acquisition payment": {
"id": 935,
"nterm": "acquisition payment"
},
"develop models and views of candidate architectures": {
"id": 1019,
"nterm": "develop models and views of candidate architectures"
},
"qm corrective actions": {
"id": 1246,
"nterm": "qm corrective actions"
},
"moe needs": {
"id": 1101,
"nterm": "moe needs"
},
"@the death of contract": {
"id": 812,
"nterm": "@the death of contract"
},
"@thomas kuhn on paradigms": {
"id": 863,
"nterm": "@thomas kuhn on paradigms"
},
"moe data": {
"id": 1128,
"nterm": "measurement data"
},
"operation constraint": {
"id": 1089,
"nterm": "life cycle constraints"
},
"deployment concept draft": {
"id": 1200,
"nterm": "preliminary life cycle concepts"
},
"skilled staff": {
"id": 1247,
"nterm": "qualified personnel"
},
"@knowledge networks innovation through communities of practice": {
"id": 444,
"nterm": "@knowledge networks innovation through communities of practice"
},
"unclear coupling mechanism": {
"id": 1145,
"nterm": "operation constraints"
},
"industrial chain": {
"id": 1351,
"nterm": "validated system"
},
"@dont become an enterprise it architect": {
"id": 230,
"nterm": "@dont become an enterprise it architect"
},
"refinement of an operation strategy": {
"id": 1149,
"nterm": "operation strategy"
},
"@an enterprise feature ontology for feature-based product line engineering": {
"id": 64,
"nterm": "@an enterprise feature ontology for feature-based product line engineering"
},
"@iso iec 29110-4-1": {
"id": 373,
"nterm": "@iso iec 29110-4-1"
},
"@model-based system architecture": {
"id": 509,
"nterm": "@model-based system architecture"
},
"perform system analysis": {
"id": 1178,
"nterm": "perform system analysis"
},
"@bfo 2 classifier": {
"id": 91,
"nterm": "@bfo 2 classifier"
},
"project roadmap": {
"id": 1243,
"nterm": "project schedule"
},
"@bleeding edge epistemology practical problem solving in software support hot lines": {
"id": 101,
"nterm": "@bleeding edge epistemology practical problem solving in software support hot lines"
},
"maintenance report": {
"id": 1262,
"nterm": "reports"
},
"@cause and impact analysis of cost and schedule overruns in subsea oil and gas projects – a supplier's perspective": {
"id": 129,
"nterm": "@cause and impact analysis of cost and schedule overruns in subsea oil and gas projects – a supplier's perspective"
},
"@design structure matrix methods and applications": {
"id": 197,
"nterm": "@design structure matrix methods and applications"
},
"incident management": {
"id": 1062,
"nterm": "incident management"
},
"@actual causality in a logical setting.___": {
"id": 48,
"nterm": "@actual causality in a logical setting.___"
},
"qa corrective action": {
"id": 1246,
"nterm": "qm corrective actions"
},
"@the øresund fixed link evaluation issues and development of new methodology": {
"id": 858,
"nterm": "@the øresund fixed link evaluation issues and development of new methodology"
},
"@the innovators the engineering pioneers who made america modern": {
"id": 824,
"nterm": "@the innovators the engineering pioneers who made america modern"
},
"decision record": {
"id": 1002,
"nterm": "decision record"
},
"@improved — the bfo classifier": {
"id": 400,
"nterm": "@improved — the bfo classifier"
},
"@our 6 must reads if you are hiring a product manager": {
"id": 549,
"nterm": "@our 6 must reads if you are hiring a product manager"
},
"preliminary moe needs": {
"id": 1196,
"nterm": "preliminary moe needs"
},
"life cycle models": {
"id": 1093,
"nterm": "life cycle models"
},
"@a garbage can model at forty a solution that still attracts problems": {
"id": 13,
"nterm": "@a garbage can model at forty a solution that still attracts problems"
},
"@relational contracts in strategic alliances": {
"id": 638,
"nterm": "@relational contracts in strategic alliances"
},
"activate the project": {
"id": 941,
"nterm": "activate the project"
},
"@control through communication the rise of system in american management": {
"id": 164,
"nterm": "@control through communication the rise of system in american management"
},
"waterfall": {
"id": 1093,
"nterm": "life cycle models"
},
"system requirements definition": {
"id": 1309,
"nterm": "system requirements definition"
},
"@state-of-practice survey of model-based systems engineering": {
"id": 707,
"nterm": "@state-of-practice survey of model-based systems engineering"
},
"budget of a program": {
"id": 1227,
"nterm": "project budget"
},
"@providing clarity and a common language to the fuzzy front end": {
"id": 618,
"nterm": "@providing clarity and a common language to the fuzzy front end"
},
"disposal enabling system requirements": {
"id": 1023,
"nterm": "disposal enabling system requirements"
},
"@secular discernment a process of individual unlearning and collective relearning": {
"id": 679,
"nterm": "@secular discernment a process of individual unlearning and collective relearning"
},
"analyze the decision information": {
"id": 951,
"nterm": "analyze the decision information"
},
"@making design rules a multidomain perspective": {
"id": 475,
"nterm": "@making design rules a multidomain perspective"
},
"terminate projects": {
"id": 1335,
"nterm": "terminate projects"
},
"systems function decomposition": {
"id": 1321,
"nterm": "system function identification"
},
"project deliverable": {
"id": 1240,
"nterm": "project planning record"
},
"@projects-as-practice": {
"id": 616,
"nterm": "@projects-as-practice"
},
"requirements flowdown and traceability using mbse": {
"id": 1264,
"nterm": "requirements flowdown and traceability using mbse"
},
"@incose nz meet-up 2022-11 requirements schemas for large multidisciplinary projects": {
"id": 354,
"nterm": "@incose nz meet-up 2022-11 requirements schemas for large multidisciplinary projects"
},
"@the dynamo and the computer an historical perspective on the modern productivity paradox": {
"id": 813,
"nterm": "@the dynamo and the computer an historical perspective on the modern productivity paradox"
},
"define stakeholder needs": {
"id": 1006,
"nterm": "define stakeholder needs"
},
"breakdown in services": {
"id": 1150,
"nterm": "operation"
},
"@systems engineering measurement primer a basic introduction to measurement concepts and use for systems engineering": {
"id": 724,
"nterm": "@systems engineering measurement primer a basic introduction to measurement concepts and use for systems engineering"
},
"system function identification": {
"id": 1321,
"nterm": "system function identification"
},
"@how tenacity, a wall saved a japanese nuclear plant from meltdown after tsunami": {
"id": 338,
"nterm": "@how tenacity, a wall saved a japanese nuclear plant from meltdown after tsunami"
},
"@shielding production an essential step in production control": {
"id": 682,
"nterm": "@shielding production an essential step in production control"
},
"multi-dimensional risk evolution in oil and gas fields": {
"id": 1148,
"nterm": "operation report"
},
"@what is enterprise ontology": {
"id": 904,
"nterm": "@what is enterprise ontology"
},
"8d": {
"id": 1246,
"nterm": "qm corrective actions"
},
"@layering — is it really a useful approach in business it enterprise architecture": {
"id": 448,
"nterm": "@layering — is it really a useful approach in business it enterprise architecture"
},
"@practical software and systems measurement (psm) digital engineering measurement framework": {
"id": 576,
"nterm": "@practical software and systems measurement (psm) digital engineering measurement framework"
},
"@ford versus fordism the beginning of mass production": {
"id": 284,
"nterm": "@ford versus fordism the beginning of mass production"
},
"@el arbol del conocimiento las bases biológicas del conocimiento humano": {
"id": 236,
"nterm": "@el arbol del conocimiento las bases biológicas del conocimiento humano"
},
"@business thinking and financial modeling for technology startups": {
"id": 113,
"nterm": "@business thinking and financial modeling for technology startups"
},
"@reverse engineering a decision and roadmap baseline": {
"id": 657,
"nterm": "@reverse engineering a decision and roadmap baseline"
},
"@a tutorial on using the wambs checklist to avoid the misuse of bayesian statistics": {
"id": 26,
"nterm": "@a tutorial on using the wambs checklist to avoid the misuse of bayesian statistics"
},
"transition constraint.": {
"id": 1089,
"nterm": "life cycle constraints"
},
"@designing data-intensive applications the big ideas behind reliable, scalable, and maintainable systems": {
"id": 200,
"nterm": "@designing data-intensive applications the big ideas behind reliable, scalable, and maintainable systems"
},
"solution alternative": {
"id": 946,
"nterm": "alternative solution classes"
},
"@enterprise architecture at work": {
"id": 249,
"nterm": "@enterprise architecture at work"
},
"@product management organizational placement": {
"id": 592,
"nterm": "@product management organizational placement"
},
"evaluate operationally relevant attributes and trends": {
"id": 1173,
"nterm": "perform operation"
},
"@understanding the ethical cost of organizational goal-setting a review and theory development": {
"id": 885,
"nterm": "@understanding the ethical cost of organizational goal-setting a review and theory development"
},
"failure reporting and corrective actions": {
"id": 1116,
"nterm": "manage results of operation"
},
"@laboratory life the construction of scientific facts": {
"id": 447,
"nterm": "@laboratory life the construction of scientific facts"
},
"mbse roi management": {
"id": 1094,
"nterm": "mbse roi management"
},
"scheduled servicing": {
"id": 1172,
"nterm": "perform maintenance"
},
"conceptual design": {
"id": 988,
"nterm": "conceptual design"
},
"maintenance procedure": {
"id": 1105,
"nterm": "maintenance procedure"
},
"retirement concept": {
"id": 1088,
"nterm": "life cycle concepts"
},
"validation record": {
"id": 1356,
"nterm": "validation record"
},
"predictive maintenance platform": {
"id": 1146,
"nterm": "operation enabling system requirements"
},
"@a new framework for modelling schedules in complex and uncertain npd projects": {
"id": 17,
"nterm": "@a new framework for modelling schedules in complex and uncertain npd projects"
},
"@crafting science standardized packages, boundary objects, and translation": {
"id": 175,
"nterm": "@crafting science standardized packages, boundary objects, and translation"
},
"fragmentation of data": {
"id": 1145,
"nterm": "operation constraints"
},
"@from the american system to mass production, 1800-1932 the development of manufacturing technology in the united states": {
"id": 295,
"nterm": "@from the american system to mass production, 1800-1932 the development of manufacturing technology in the united states"
},
"@defining quality aspects for conceptual models": {
"id": 191,
"nterm": "@defining quality aspects for conceptual models"
},
"cash memo": {
"id": 1288,
"nterm": "source documents"
},
"quality assurance report": {
"id": 1262,
"nterm": "reports"
},
"service acceptance": {
"id": 1280,
"nterm": "service acceptance"
},
"@the lean startup how today's entrepreneurs use continuous innovation to create radically successful businesses": {
"id": 825,
"nterm": "@the lean startup how today's entrepreneurs use continuous innovation to create radically successful businesses"
},
"@managing technology and product development programmes a framework for success": {
"id": 484,
"nterm": "@managing technology and product development programmes a framework for success"
},
"@the software architect elevator redefining the architect role in the digital enterprise": {
"id": 798,
"nterm": "@the software architect elevator redefining the architect role in the digital enterprise"
},
"@iso pas 19450": {
"id": 390,
"nterm": "@iso pas 19450"
},
"@integrated cost and schedule control in the korean construction industry based on a modified work-packaging model": {
"id": 415,
"nterm": "@integrated cost and schedule control in the korean construction industry based on a modified work-packaging model"
},
"project performance measures needs": {
"id": 1238,
"nterm": "project performance measures needs"
},
"acquisition record": {
"id": 936,
"nterm": "acquisition record"
},
"measurement report": {
"id": 1262,
"nterm": "reports"
},
"@documenting software architecture documenting interfaces": {
"id": 226,
"nterm": "@documenting software architecture documenting interfaces"
},
"reliability-centered maintenance strategy": {
"id": 1103,
"nterm": "maintenance constraints"
},
"@office of career services - resumes and cover letters": {
"id": 529,
"nterm": "@office of career services - resumes and cover letters"
},
"@exploring the miracle strategy and management of the knowledge base in the aeronautics industry": {
"id": 268,
"nterm": "@exploring the miracle strategy and management of the knowledge base in the aeronautics industry"
},
"@contexts a formalization and some applications": {
"id": 157,
"nterm": "@contexts a formalization and some applications"
},
"business object": {
"id": 972,
"nterm": "business object"
},
"@product lifecycle management": {
"id": 599,
"nterm": "@product lifecycle management"
},
"@alternatives and assessment in large-scale projects the öresund bridge case": {
"id": 61,
"nterm": "@alternatives and assessment in large-scale projects the öresund bridge case"
},
"life cycle model management report": {
"id": 1262,
"nterm": "reports"
},
"plan quality management": {
"id": 1189,
"nterm": "plan quality management"
},
"replace a legacy system": {
"id": 1344,
"nterm": "transition"
},
"@five misunderstandings about case-study research": {
"id": 282,
"nterm": "@five misunderstandings about case-study research"
},
"@iso iec 15940": {
"id": 361,
"nterm": "@iso iec 15940"
},
"@organisational design what your university forgot to teach you": {
"id": 544,
"nterm": "@organisational design what your university forgot to teach you"
},
"@crafting definitions conceptspeak primer": {
"id": 174,
"nterm": "@crafting definitions conceptspeak primer"
},
"@agile product development managing development flexibility in uncertain environments": {
"id": 55,
"nterm": "@agile product development managing development flexibility in uncertain environments"
},
"@to engineer is human the role of failure in successful design": {
"id": 864,
"nterm": "@to engineer is human the role of failure in successful design"
},
"@ebook product design and development": {
"id": 232,
"nterm": "@ebook product design and development"
},
"@applying good eia practice criteria to sea the öresund bridge as a case": {
"id": 77,
"nterm": "@applying good eia practice criteria to sea the öresund bridge as a case"
},
"@iso iec ieee 42010": {
"id": 387,
"nterm": "@iso iec ieee 42010"
},
"@causal models, token causation, and processes": {
"id": 126,
"nterm": "@causal models, token causation, and processes"
},
"technical constraint": {
"id": 1089,
"nterm": "life cycle constraints"
},
"overall safe production situation": {
"id": 1147,
"nterm": "operation record"
},
"reports": {
"id": 1262,
"nterm": "reports"
},
"mbse value management": {
"id": 1098,
"nterm": "mbse value management"
},
"regulation": {
"id": 1229,
"nterm": "project constraints"
},
"@everything is in the lab book multimodal writing, activity, and genre analysis of symbolic mediation in medical physics": {
"id": 258,
"nterm": "@everything is in the lab book multimodal writing, activity, and genre analysis of symbolic mediation in medical physics"
},
"@product fail": {
"id": 588,
"nterm": "@product fail"
},
"@integrating four-dimensional ontology and systems requirements modelling": {
"id": 421,
"nterm": "@integrating four-dimensional ontology and systems requirements modelling"
},
"pipeline of projects": {
"id": 1242,
"nterm": "project portfolio"
},
"document-based regulatory system": {
"id": 1030,
"nterm": "document-based regulatory system"
},
"perform configuration status accounting": {
"id": 1167,
"nterm": "perform configuration status accounting"
},
"@resolving work breakdown structure problems": {
"id": 649,
"nterm": "@resolving work breakdown structure problems"
},
"robert cloutier": {
"id": 1271,
"nterm": "robert cloutier"
},
"preliminary tpm data": {
"id": 1197,
"nterm": "preliminary tpm data"
},
"perform implementation": {
"id": 1169,
"nterm": "perform implementation"
},
"purchase order": {
"id": 1288,
"nterm": "source documents"
},
"@learning by expanding": {
"id": 454,
"nterm": "@learning by expanding"
},
"identify operational problems": {
"id": 1173,
"nterm": "perform operation"
},
"@iso iec 26550": {
"id": 367,
"nterm": "@iso iec 26550"
},
"disposal constraints": {
"id": 1022,
"nterm": "disposal constraints"
},
"system trouble report": {
"id": 1148,
"nterm": "operation report"
},
"@systems engineering vision 2035": {
"id": 726,
"nterm": "@systems engineering vision 2035"
},
"@mereology": {
"id": 502,
"nterm": "@mereology"
},
"program portfolio": {
"id": 1242,
"nterm": "project portfolio"
},
"@the age of cargo cult agile must end": {
"id": 805,
"nterm": "@the age of cargo cult agile must end"
},
"operation report": {
"id": 1262,
"nterm": "reports"
},
"@the emergence of a visual language for geological science 1760-1840": {
"id": 763,
"nterm": "@the emergence of a visual language for geological science 1760-1840"
},
"specify the project": {
"id": 1009,
"nterm": "define the project"
},
"@quantification of the value of systems engineering": {
"id": 622,
"nterm": "@quantification of the value of systems engineering"
},
"@complementarity and evolution of contractual provisions an empirical study of it services contracts": {
"id": 147,
"nterm": "@complementarity and evolution of contractual provisions an empirical study of it services contracts"
},
"perform quality management corrective action and preventive action": {
"id": 1176,
"nterm": "perform quality management corrective action and preventive action"
},
"@information acquisition, decision making, and implementation in organizations": {
"id": 406,
"nterm": "@information acquisition, decision making, and implementation in organizations"
},
"demand management": {
"id": 1011,
"nterm": "demand management"
},
"@exploring the duality between product and organizational architectures a test of the mirroring hypothesis": {
"id": 267,
"nterm": "@exploring the duality between product and organizational architectures a test of the mirroring hypothesis"
},
"@engineering texts a study of a community of aerospace engineers, their writing practices, and technical proposals": {
"id": 244,
"nterm": "@engineering texts a study of a community of aerospace engineers, their writing practices, and technical proposals"
},
"derivative disaster assessment models for oil and gas pipelines and stations": {
"id": 1149,
"nterm": "operation strategy"
},
"maintenance": {
"id": 1108,
"nterm": "maintenance"
},
"sensory-based equipment condition identification": {
"id": 1146,
"nterm": "operation enabling system requirements"
},
"system architecture rationale": {
"id": 1314,
"nterm": "system architecture rationale"
},
"verification": {
"id": 1369,
"nterm": "verification"
},
"information management": {
"id": 1063,
"nterm": "information management"
},
"oosem": {
"id": 1140,
"nterm": "oosem"
},
"@challenges of coordination using electronics health records a genre analysis": {
"id": 130,
"nterm": "@challenges of coordination using electronics health records a genre analysis"
},
"@towards a theory of part": {
"id": 870,
"nterm": "@towards a theory of part"
},
"system requirements definition record": {
"id": 1324,
"nterm": "system requirements definition record"
},
"@rethinking organizational design": {
"id": 652,
"nterm": "@rethinking organizational design"
},
"@systems engineering for capabilities": {
"id": 730,
"nterm": "@systems engineering for capabilities"
},
"@a proposed conceptual framework for a representational approach to information retrieval": {
"id": 19,
"nterm": "@a proposed conceptual framework for a representational approach to information retrieval"
},
"acquired system": {
"id": 932,
"nterm": "acquired system"
},
"@the evolution of research on coordination mechanisms in multinational corporations": {
"id": 818,
"nterm": "@the evolution of research on coordination mechanisms in multinational corporations"
},
"supply record": {
"id": 1300,
"nterm": "supply record"
},
"@cyber kill chain understanding mitigating advanced threats": {
"id": 181,
"nterm": "@cyber kill chain understanding mitigating advanced threats"
},
"@calling bullshit": {
"id": 117,
"nterm": "@calling bullshit"
},
"@a history of project management models from pre-models to the standard models": {
"id": 35,
"nterm": "@a history of project management models from pre-models to the standard models"
},
"@rebl entity linking at scale": {
"id": 627,
"nterm": "@rebl entity linking at scale"
},
"dispose of components": {
"id": 1173,
"nterm": "perform operation"
},
"@reverse engineering stakeholder decisions from their requirements": {
"id": 656,
"nterm": "@reverse engineering stakeholder decisions from their requirements"
},
"knowledge management system": {
"id": 1085,
"nterm": "knowledge management system"
},
"@systems architecture. strategy and product development for complex systems": {
"id": 723,
"nterm": "@systems architecture. strategy and product development for complex systems"
},
"@the lean startup": {
"id": 826,
"nterm": "@the lean startup"
},
"@patterned interactions in complex systems implications for exploration": {
"id": 561,
"nterm": "@patterned interactions in complex systems implications for exploration"
},
"deployment concept": {
"id": 1088,
"nterm": "life cycle concepts"
},
"manage results of operation": {
"id": 1116,
"nterm": "manage results of operation"
},
"@a tipping point in the information revolution": {
"id": 43,
"nterm": "@a tipping point in the information revolution"
},
"@coming up with research ideas": {
"id": 143,
"nterm": "@coming up with research ideas"
},
"rfp response": {
"id": 1302,
"nterm": "supply response"
},
"@the role of spreadsheet knowledge in user-developed application success": {
"id": 842,
"nterm": "@the role of spreadsheet knowledge in user-developed application success"
},
"@the project management - systems engineering dichotomy": {
"id": 839,
"nterm": "@the project management - systems engineering dichotomy"
},
"human capital requirements": {
"id": 1232,
"nterm": "project human resources needs"
},
"@incose competency framework": {
"id": 352,
"nterm": "@incose competency framework"
},
"project planning": {
"id": 1241,
"nterm": "project planning"
},
"@industrial r&d in japan and the united states a comparative study": {
"id": 404,
"nterm": "@industrial r&d in japan and the united states a comparative study"
},
"budget of a project": {
"id": 1227,
"nterm": "project budget"
},
"service catalogue management": {
"id": 1281,
"nterm": "service catalogue management"
},
"@the theory of project management explanation to novel methods": {
"id": 849,
"nterm": "@the theory of project management explanation to novel methods"
},
"maintenance constraint": {
"id": 1089,
"nterm": "life cycle constraints"
},
"@markets are peaceful but the state is not": {
"id": 490,
"nterm": "@markets are peaceful but the state is not"
},
"@the zimbabwe bush pump mechanics of a fluid technology": {
"id": 804,
"nterm": "@the zimbabwe bush pump mechanics of a fluid technology"
},
"project proposal": {
"id": 1302,
"nterm": "supply response"
},
"develop architecture viewpoints": {
"id": 1018,
"nterm": "develop architecture viewpoints"
},
"knowledge management": {
"id": 1082,
"nterm": "knowledge management"
},
"integrated system or system elements": {
"id": 1072,
"nterm": "integrated system or system elements"
},
"validation criteria": {
"id": 1353,
"nterm": "validation criteria"
},
"prepare for system analysis": {
"id": 1214,
"nterm": "prepare for system analysis"
},
"@wikidata a new platform for collaborative data collection": {
"id": 917,
"nterm": "@wikidata a new platform for collaborative data collection"
},
"@sorting things out classification and its consequences": {
"id": 700,
"nterm": "@sorting things out classification and its consequences"
},
"@a time to speak, a time to act a rhetorical genre analysis of a novice engineers calculated risk taking": {
"id": 25,
"nterm": "@a time to speak, a time to act a rhetorical genre analysis of a novice engineers calculated risk taking"
},
"integration enabling system requirements": {
"id": 1074,
"nterm": "integration enabling system requirements"
},
"@the design sprint — gv": {
"id": 760,
"nterm": "@the design sprint — gv"
},
"@front end innovation - what is the new concept development (ncd) model": {
"id": 296,
"nterm": "@front end innovation - what is the new concept development (ncd) model"
},
"@modeling framework for integrated, model-based development of product-service systems": {
"id": 512,
"nterm": "@modeling framework for integrated, model-based development of product-service systems"
},
"@the architecture and design of organizational capabilities": {
"id": 806,
"nterm": "@the architecture and design of organizational capabilities"
},
"@extension to a guide to the project management body of knowledge (pmbok guide)": {
"id": 270,
"nterm": "@extension to a guide to the project management body of knowledge (pmbok guide)"
},
"@specialized assets and organizational rent": {
"id": 702,
"nterm": "@specialized assets and organizational rent"
},
"@process institutionalism toward an action-centric approach to state extraction": {
"id": 585,
"nterm": "@process institutionalism toward an action-centric approach to state extraction"
},
"@toward a nasa-specific project management framework": {
"id": 866,
"nterm": "@toward a nasa-specific project management framework"
},
"@complexities social studies of knowledge practices": {
"id": 148,
"nterm": "@complexities social studies of knowledge practices"
},
"configuration management strategy": {
"id": 1296,
"nterm": "strategy documents"
},
"@requirements engineering fundamentals, principles, and techniques": {
"id": 644,
"nterm": "@requirements engineering fundamentals, principles, and techniques"
},
"@the limits to specialization problem solving and coordination in modular networks": {
"id": 827,
"nterm": "@the limits to specialization problem solving and coordination in modular networks"
},
"@history of engineering drawing": {
"id": 322,
"nterm": "@history of engineering drawing"
},
"monitor the agreement": {
"id": 1138,
"nterm": "monitor the agreement"
},
"@digital systems engineering process model version 1": {
"id": 217,
"nterm": "@digital systems engineering process model version 1"
},
"@ontological representation of fair principles a blueprint for fairer data sources": {
"id": 536,
"nterm": "@ontological representation of fair principles a blueprint for fairer data sources"
},
"@information flow through stages of complex engineering design projects a dynamic network analysis approach": {
"id": 407,
"nterm": "@information flow through stages of complex engineering design projects a dynamic network analysis approach"
},
"skilled personnel": {
"id": 1247,
"nterm": "qualified personnel"
},
"@product ops overview": {
"id": 595,
"nterm": "@product ops overview"
},
"validated system": {
"id": 1351,
"nterm": "validated system"
},
"@definition of product management - blackblot pmtk book chapter": {
"id": 193,
"nterm": "@definition of product management - blackblot pmtk book chapter"
},
"@modern software engineering doing what works to build better software faster": {
"id": 513,
"nterm": "@modern software engineering doing what works to build better software faster"
},
"@diagnosing risks in product-innovation projects": {
"id": 215,
"nterm": "@diagnosing risks in product-innovation projects"
},
"@product market fit": {
"id": 593,
"nterm": "@product market fit"
},
"@the new future of work. research from microsoft into the pandemic’s impact on work practices": {
"id": 786,
"nterm": "@the new future of work. research from microsoft into the pandemic’s impact on work practices"
},
"@pmp exam prep": {
"id": 558,
"nterm": "@pmp exam prep"
},
"@relational contracts and organizational capabilities": {
"id": 637,
"nterm": "@relational contracts and organizational capabilities"
},
"acquisition report": {
"id": 1262,
"nterm": "reports"
},
"selling systems engineering and mbse": {
"id": 1278,
"nterm": "selling systems engineering and mbse"
},
"technical personnel maintaining the system": {
"id": 1337,
"nterm": "trained operators and maintainers"
},
"@explaining actual causation via reasoning about actions and change": {
"id": 265,
"nterm": "@explaining actual causation via reasoning about actions and change"
},
"@structuring a lean engineering ontology for managing the product lifecycle": {
"id": 714,
"nterm": "@structuring a lean engineering ontology for managing the product lifecycle"
},
"@the application of workflow technology in semantic b2b integration": {
"id": 749,
"nterm": "@the application of workflow technology in semantic b2b integration"
},
"@enterprise search solutions — ontology, knowledge graph & semantic search": {
"id": 247,
"nterm": "@enterprise search solutions — ontology, knowledge graph & semantic search"
},
"@what constitutes a theoretical contribution": {
"id": 901,
"nterm": "@what constitutes a theoretical contribution"
},
"@integrated project team performance in early design stages – performance indicators influencing effectiveness in bridge design": {
"id": 416,
"nterm": "@integrated project team performance in early design stages – performance indicators influencing effectiveness in bridge design"
},
"architecture definition record": {
"id": 955,
"nterm": "architecture definition record"
},
"major repairs": {
"id": 1172,
"nterm": "perform maintenance"
},
"updated rvtm": {
"id": 1349,
"nterm": "updated rvtm"
},
"functional system decomposition": {
"id": 1321,
"nterm": "system function identification"
},
"@apollo-protocol 4d-activity-editor": {
"id": 74,
"nterm": "@apollo-protocol 4d-activity-editor"
},
"@solid": {
"id": 699,
"nterm": "@solid"
},
"@between craft and science technical work in the united states": {
"id": 95,
"nterm": "@between craft and science technical work in the united states"
},
"preliminary interface definition": {
"id": 1199,
"nterm": "preliminary interface definition"
},
"@technological knowledge without science the innovation of flush riveting in american airplanes, 1930-1950": {
"id": 738,
"nterm": "@technological knowledge without science the innovation of flush riveting in american airplanes, 1930-1950"
},
"@the secrets of consulting": {
"id": 843,
"nterm": "@the secrets of consulting"
},
"manage the business or mission analysis": {
"id": 1122,
"nterm": "manage the business or mission analysis"
},
"quality management plan": {
"id": 1256,
"nterm": "quality management plan"
},
"configuration baselines": {
"id": 990,
"nterm": "configuration baselines"
},
"@significance of cloud plm in industry 4": {
"id": 687,
"nterm": "@significance of cloud plm in industry 4"
},
"stakeholder needs and requirements definition record": {
"id": 1290,
"nterm": "stakeholder needs and requirements definition record"
},
"database administration": {
"id": 998,
"nterm": "database administration"
},
"@engineering rules global standard setting since 1880": {
"id": 240,
"nterm": "@engineering rules global standard setting since 1880"
},
"sell mbse": {
"id": 1277,
"nterm": "sell mbse"
},
"disposal report": {
"id": 1262,
"nterm": "reports"
},
"evaluate operational effectiveness": {
"id": 1116,
"nterm": "manage results of operation"
},
"@effective sizing and content definition of work packages": {
"id": 234,
"nterm": "@effective sizing and content definition of work packages"
},
"solution architecture": {
"id": 1287,
"nterm": "solution architecture"
},
"@technology readiness levels at 40 a study of state-of-the-art use, challenges, and opportunities": {
"id": 742,
"nterm": "@technology readiness levels at 40 a study of state-of-the-art use, challenges, and opportunities"
},
"implementation report": {
"id": 1262,
"nterm": "reports"
},
"tpm data": {
"id": 1331,
"nterm": "tpm data"
},
"@does decision process matter - a study of strategic decision-making effectiveness": {
"id": 228,
"nterm": "@does decision process matter - a study of strategic decision-making effectiveness"
},
"retirement concept draft.": {
"id": 1200,
"nterm": "preliminary life cycle concepts"
},
"system requirements definition strategy": {
"id": 1325,
"nterm": "system requirements definition strategy"
},
"portfolio management plan": {
"id": 1192,
"nterm": "portfolio management plan"
},
"@varieties of parthood ontology learns from engineering": {
"id": 897,
"nterm": "@varieties of parthood ontology learns from engineering"
},
"@the organization of innovation in ecosystems problem framing, problem solving, and patterns of coupling": {
"id": 836,
"nterm": "@the organization of innovation in ecosystems problem framing, problem solving, and patterns of coupling"
},
"@applying systems engineering to in-service systems": {
"id": 76,
"nterm": "@applying systems engineering to in-service systems"
},
"disposal constraint": {
"id": 1089,
"nterm": "life cycle constraints"
},
"prepare for stakeholder needs and requirements definition": {
"id": 1212,
"nterm": "prepare for stakeholder needs and requirements definition"
},
"@documenting software architectures views and beyond": {
"id": 225,
"nterm": "@documenting software architectures views and beyond"
},
"verification enabling system requirements": {
"id": 1362,
"nterm": "verification enabling system requirements"
},
"including implementation enabling system requirements": {
"id": 1032,
"nterm": "enabling system requirements"
},
"identify skills": {
"id": 1053,
"nterm": "identify skills"
},
"selling systems engineering": {
"id": 1279,
"nterm": "selling systems engineering"
},
"@technology readiness levels shortcomings and improvement opportunities": {
"id": 741,
"nterm": "@technology readiness levels shortcomings and improvement opportunities"
},
"@the box how the shipping container made the world smaller and the world economy bigger": {
"id": 755,
"nterm": "@the box how the shipping container made the world smaller and the world economy bigger"
},
"@systems engineering guidebook a process for developing systems and products": {
"id": 731,
"nterm": "@systems engineering guidebook a process for developing systems and products"
},
"project calendar": {
"id": 1243,
"nterm": "project schedule"
},
"@design management managing design strategy, process and implementation": {
"id": 194,
"nterm": "@design management managing design strategy, process and implementation"
},
"records": {
"id": 1260,
"nterm": "records"
},
"equipment safety": {
"id": 1149,
"nterm": "operation strategy"
},
"@its price before product": {
"id": 436,
"nterm": "@its price before product"
},
"@development of work breakdown structure basis for mega-project": {
"id": 212,
"nterm": "@development of work breakdown structure basis for mega-project"
},
"@architectural coordination of enterprise transformation": {
"id": 80,
"nterm": "@architectural coordination of enterprise transformation"
},
"@iso iec ieee 24765": {
"id": 385,
"nterm": "@iso iec ieee 24765"
},
"system maintenance": {
"id": 1377,
"nterm": "system maintenance"
},
"@intelligent safe operation and maintenance of ogps": {
"id": 425,
"nterm": "@intelligent safe operation and maintenance of ogps"
},
"response to rfq": {
"id": 1302,
"nterm": "supply response"
},
"@building theories of project management past research, questions for the future": {
"id": 110,
"nterm": "@building theories of project management past research, questions for the future"
},
"@software engineering research the need to strengthen and broaden the classical scientific method": {
"id": 697,
"nterm": "@software engineering research the need to strengthen and broaden the classical scientific method"
},
"@product–service systems engineering state of the art and research challenges": {
"id": 604,
"nterm": "@product–service systems engineering state of the art and research challenges"
},
"minor damage repairs": {
"id": 1172,
"nterm": "perform maintenance"
},
"prepare for verification": {
"id": 1219,
"nterm": "prepare for verification"
},
"@an overall guidance and proposition of a wbs template for construction planning of the template (jacket) platforms": {
"id": 72,
"nterm": "@an overall guidance and proposition of a wbs template for construction planning of the template (jacket) platforms"
},
"@the history of project management": {
"id": 772,
"nterm": "@the history of project management"
},
"@iw2022 gaps in tools panel discussion": {
"id": 392,
"nterm": "@iw2022 gaps in tools panel discussion"
},
"@a generic workflow for the data fairification process": {
"id": 14,
"nterm": "@a generic workflow for the data fairification process"
},
"@plm applied to manufacturing problem solving a case study at exide technologies": {
"id": 553,
"nterm": "@plm applied to manufacturing problem solving a case study at exide technologies"
},
"@the role of command-and-control management and governance in systems engineering": {
"id": 841,
"nterm": "@the role of command-and-control management and governance in systems engineering"
},
"system anomaly report": {
"id": 1148,
"nterm": "operation report"
},
"pipeline leakages are generally identified": {
"id": 1148,
"nterm": "operation report"
},
"@a review towards the new japanese project management p2m and kpm": {
"id": 40,
"nterm": "@a review towards the new japanese project management p2m and kpm"
},
"take actions to prevent degradation of performance": {
"id": 1173,
"nterm": "perform operation"
},
"@debunking contemporary myths concerning engineering": {
"id": 184,
"nterm": "@debunking contemporary myths concerning engineering"
},
"swot": {
"id": 1296,
"nterm": "strategy documents"
},
"@enabling the digital thread for smart manufacturing": {
"id": 237,
"nterm": "@enabling the digital thread for smart manufacturing"
},
"system design rationale": {
"id": 1316,
"nterm": "system design rationale"
},
"mbse effort in collaboration with customer or prime contractors or subcontractors": {
"id": 1096,
"nterm": "mbse effort in collaboration with customer or prime contractors or subcontractors"
},
"acquisition concept draft": {
"id": 1200,
"nterm": "preliminary life cycle concepts"
},
"verification planning and execution": {
"id": 1364,
"nterm": "verification planning and execution"
},
"prepare for validation": {
"id": 1218,
"nterm": "prepare for validation"
},
"@vse 101 – who, what, when, where, why, how": {
"id": 893,
"nterm": "@vse 101 – who, what, when, where, why, how"
},
"system performance reports": {
"id": 1148,
"nterm": "operation report"
},
"manpower requirements": {
"id": 1232,
"nterm": "project human resources needs"
},
"@reconceptualizing plural sourcing": {
"id": 629,
"nterm": "@reconceptualizing plural sourcing"
},
"@formal scenario definition language for aviation aircraft landing case study": {
"id": 285,
"nterm": "@formal scenario definition language for aviation aircraft landing case study"
},
"@developing a systems engineering capability that meets the needs of your organization": {
"id": 206,
"nterm": "@developing a systems engineering capability that meets the needs of your organization"
},
"@continuous innovation blog": {
"id": 158,
"nterm": "@continuous innovation blog"
},
"@enterprise integration patterns designing, building, and deploying messaging solutions": {
"id": 246,
"nterm": "@enterprise integration patterns designing, building, and deploying messaging solutions"
},
"@how do elephants and ants tango": {
"id": 325,
"nterm": "@how do elephants and ants tango"
},
"accept the product or service": {
"id": 928,
"nterm": "accept the product or service"
},
"project infrastructure": {
"id": 1234,
"nterm": "project infrastructure"
},
"project lessons learned": {
"id": 1235,
"nterm": "project lessons learned"
},
"@computer and dynamo the modern productivity paradox in a not-too distant mirror": {
"id": 151,
"nterm": "@computer and dynamo the modern productivity paradox in a not-too distant mirror"
},
"corporate strategy": {
"id": 1296,
"nterm": "strategy documents"
},
"@how to develop work breakdown structures": {
"id": 339,
"nterm": "@how to develop work breakdown structures"
},
"@the seven samurai of systems engineering dealing with the complexity of 7 interrelated systems": {
"id": 844,
"nterm": "@the seven samurai of systems engineering dealing with the complexity of 7 interrelated systems"
},
"buried in the issues of managing their current systems": {
"id": 968,
"nterm": "buried in the issues of managing their current systems"
},
"perform configuration identification": {
"id": 1166,
"nterm": "perform configuration identification"
},
"maintenance technology system of oil and gas production system": {
"id": 1351,
"nterm": "validated system"
},
"@camels and rubber duckies": {
"id": 119,
"nterm": "@camels and rubber duckies"
},
"@how meta uses analytics to assess product market fit": {
"id": 329,
"nterm": "@how meta uses analytics to assess product market fit"
},
"@use of a wbs matrix to improve interface management in projects": {
"id": 890,
"nterm": "@use of a wbs matrix to improve interface management in projects"
},
"maintenance allocation chart": {
"id": 1337,
"nterm": "trained operators and maintainers"
},
"and disposal enabling system requirements.": {
"id": 1032,
"nterm": "enabling system requirements"
},
"minor modifications": {
"id": 1172,
"nterm": "perform maintenance"
},
"preliminary validation criteria": {
"id": 1201,
"nterm": "preliminary validation criteria"
},
"@a practical guide to building an online recommendation system": {
"id": 18,
"nterm": "@a practical guide to building an online recommendation system"
},
"competent staff": {
"id": 1247,
"nterm": "qualified personnel"
},
"development of training for operational and support personnel": {
"id": 1116,
"nterm": "manage results of operation"
},
"candidate configuration items": {
"id": 979,
"nterm": "candidate configuration items"
},
"@the contradictory structure of systems development methodologies deconstructing the is-user relationship in information engineering": {
"id": 809,
"nterm": "@the contradictory structure of systems development methodologies deconstructing the is-user relationship in information engineering"
},
"define and authorize projects": {
"id": 1005,
"nterm": "define and authorize projects"
},
"sysml": {
"id": 1307,
"nterm": "sysml"
},
"plan risk management": {
"id": 1190,
"nterm": "plan risk management"
},
"@a model of enterprise systems engineering contributions to acquisition success": {
"id": 37,
"nterm": "@a model of enterprise systems engineering contributions to acquisition success"
},
"verification criteria": {
"id": 1361,
"nterm": "verification criteria"
},
"@series practical guidance to qualitative research part 4 trustworthiness and publishing": {
"id": 680,
"nterm": "@series practical guidance to qualitative research part 4 trustworthiness and publishing"
},
"@a theory of the early growth of the firm": {
"id": 42,
"nterm": "@a theory of the early growth of the firm"
},
"@making data and workflows findable for machines": {
"id": 474,
"nterm": "@making data and workflows findable for machines"
},
"@towards the tipping point for fair implementation": {
"id": 873,
"nterm": "@towards the tipping point for fair implementation"
},
"@success determinants to product lifecycle management (plm) performance": {
"id": 716,
"nterm": "@success determinants to product lifecycle management (plm) performance"
},
"share knowledge and skills throughout the organization": {
"id": 1283,
"nterm": "share knowledge and skills throughout the organization"
},
"perform verification": {
"id": 1181,
"nterm": "perform verification"
},
"@nasa sp-2010-576 risk-informed decision making handbook": {
"id": 519,
"nterm": "@nasa sp-2010-576 risk-informed decision making handbook"
},
"business requirements traceability": {
"id": 977,
"nterm": "business requirements traceability"
},
"project change requests": {
"id": 1228,
"nterm": "project change requests"
},
"sustain service": {
"id": 1150,
"nterm": "operation"
},
"@architecture, design, implementation": {
"id": 81,
"nterm": "@architecture, design, implementation"
},
"@the project manager": {
"id": 794,
"nterm": "@the project manager"
},
"project control requests": {
"id": 1230,
"nterm": "project control requests"
},
"@a value-seeking approach to the engineering of systems": {
"id": 44,
"nterm": "@a value-seeking approach to the engineering of systems"
},
"@practice standard for work breakdown structures": {
"id": 578,
"nterm": "@practice standard for work breakdown structures"
},
"@psychology of intelligence analysis": {
"id": 619,
"nterm": "@psychology of intelligence analysis"
},
"@npd frameworks a holistic examination": {
"id": 521,
"nterm": "@npd frameworks a holistic examination"
},
"@chess and the art of enterprise architecture": {
"id": 133,
"nterm": "@chess and the art of enterprise architecture"
},
"@free archimate 3 overview pdfs in multiple languages": {
"id": 290,
"nterm": "@free archimate 3 overview pdfs in multiple languages"
},
"@a comprehensive review of digital twin–part 2": {
"id": 11,
"nterm": "@a comprehensive review of digital twin–part 2"
},
"@a definition of intelligence for the real world": {
"id": 31,
"nterm": "@a definition of intelligence for the real world"
},
"@capabilities, technological diversification and divisionalization": {
"id": 122,
"nterm": "@capabilities, technological diversification and divisionalization"
},
"@assessment of back-up plan, delay, and waiver options at project gate reviews": {
"id": 87,
"nterm": "@assessment of back-up plan, delay, and waiver options at project gate reviews"
},
"manage results of verification": {
"id": 1119,
"nterm": "manage results of verification"
},
"production process model": {
"id": 1088,
"nterm": "life cycle concepts"
},
"design traceability": {
"id": 1015,
"nterm": "design traceability"
},
"project assessment and control": {
"id": 1224,
"nterm": "project assessment and control"
},
"@can digital innovations help reduce suffering a crowd-based digital innovation framework of compassion venturing": {
"id": 120,
"nterm": "@can digital innovations help reduce suffering a crowd-based digital innovation framework of compassion venturing"
},
"@introducing engineering students to intellectual teamwork": {
"id": 430,
"nterm": "@introducing engineering students to intellectual teamwork"
},
"@iw2022 success in absence of requirements ron carson": {
"id": 395,
"nterm": "@iw2022 success in absence of requirements ron carson"
},
"@iw2022 digital thread for requirement quality assessment": {
"id": 391,
"nterm": "@iw2022 digital thread for requirement quality assessment"
},
"@how to move beyond a monolithic data lake to a distributed data mesh": {
"id": 340,
"nterm": "@how to move beyond a monolithic data lake to a distributed data mesh"
},
"perform validation": {
"id": 1180,
"nterm": "perform validation"
},
"@a framework for modeling evidence-based, context-influenced reasoning": {
"id": 33,
"nterm": "@a framework for modeling evidence-based, context-influenced reasoning"
},
"@iso iec 29110-4-2": {
"id": 374,
"nterm": "@iso iec 29110-4-2"
},
"@decision tables – a primer": {
"id": 188,
"nterm": "@decision tables – a primer"
},
"integration procedure": {
"id": 1075,
"nterm": "integration procedure"
},
"on-site situation": {
"id": 1147,
"nterm": "operation record"
},
"evaluate the portfolio of projects": {
"id": 1038,
"nterm": "evaluate the portfolio of projects"
},
"perform product or service evaluation": {
"id": 1175,
"nterm": "perform product or service evaluation"
},
"approved maintenance subcontractors": {
"id": 1104,
"nterm": "maintenance enabling system"
},
"@a study analysing individual perceptions of plm benefits": {
"id": 23,
"nterm": "@a study analysing individual perceptions of plm benefits"
},
"organizational infrastructure needs": {
"id": 1158,
"nterm": "organizational infrastructure needs"
},
"requirements traceability": {
"id": 1293,
"nterm": "stakeholder requirements traceability"
},
"@meta-organization design rethinking design in interorganizational and community contexts": {
"id": 504,
"nterm": "@meta-organization design rethinking design in interorganizational and community contexts"
},
"acquisition": {
"id": 940,
"nterm": "acquisition"
},
"technical performance measurement result": {
"id": 1197,
"nterm": "preliminary tpm data"
},
"@normal accidents": {
"id": 527,
"nterm": "@normal accidents"
},
"@personal observations on reliability of shuttle": {
"id": 567,
"nterm": "@personal observations on reliability of shuttle"
},
"business analysis": {
"id": 973,
"nterm": "business or mission analysis"
},
"@structuring a product development organization based on the product architecture and communication": {
"id": 715,
"nterm": "@structuring a product development organization based on the product architecture and communication"
},
"project guidance": {
"id": 1231,
"nterm": "project direction"
},
"support the customer": {
"id": 1305,
"nterm": "support the customer"
},
"@the opportunity backlog": {
"id": 787,
"nterm": "@the opportunity backlog"
},
"@megamistakes forecasting and the myth of rapid technological change": {
"id": 470,
"nterm": "@megamistakes forecasting and the myth of rapid technological change"
},
"@how plm drives innovation in the curriculum and pedagogy of fashion business education a case study of a uk undergraduate programme": {
"id": 331,
"nterm": "@how plm drives innovation in the curriculum and pedagogy of fashion business education a case study of a uk undergraduate programme"
},
"operating product data": {
"id": 1144,
"nterm": "operating product data"
},
"@rcda agile architecture making big engineering decisions with agile teams": {
"id": 626,
"nterm": "@rcda agile architecture making big engineering decisions with agile teams"
},
"@transformer models an introduction and catalog — 2023 edition": {
"id": 877,
"nterm": "@transformer models an introduction and catalog — 2023 edition"
},
"perform logistics support": {
"id": 1171,
"nterm": "perform logistics support"
},
"@work and infrastructure": {
"id": 920,
"nterm": "@work and infrastructure"
},
"@effective work breakdown structures": {
"id": 235,
"nterm": "@effective work breakdown structures"
},
"perform configuration evaluation": {
"id": 1165,
"nterm": "perform configuration evaluation"
},
"maintaining operational capability": {
"id": 1108,
"nterm": "maintenance"
},
"@interviewing product managers for product sense": {
"id": 429,
"nterm": "@interviewing product managers for product sense"
},
"@contracts legal overview": {
"id": 162,
"nterm": "@contracts legal overview"
},
"@internet technology in support of the concept of communities-of-practice the case of xerox": {
"id": 426,
"nterm": "@internet technology in support of the concept of communities-of-practice the case of xerox"
},
"@enterprise integration patterns - messaging patterns overview": {
"id": 245,
"nterm": "@enterprise integration patterns - messaging patterns overview"
},
"unified judgment of the oil and gas production system": {
"id": 1149,
"nterm": "operation strategy"
},
"@requirements development, verification, and validation exhibited in famous failures": {
"id": 641,
"nterm": "@requirements development, verification, and validation exhibited in famous failures"
},
"prevalence of information silos": {
"id": 1145,
"nterm": "operation constraints"
},
"perform operational analysis": {
"id": 1116,
"nterm": "manage results of operation"
},
"remote monitoring platform": {
"id": 1146,
"nterm": "operation enabling system requirements"
},
"@computational representation for a simulation scenario definition language": {
"id": 150,
"nterm": "@computational representation for a simulation scenario definition language"
},
"measurement data": {
"id": 1128,
"nterm": "measurement data"
},
"manage the migration between systems": {
"id": 1150,
"nterm": "operation"
},
"maintenance actions": {
"id": 1150,
"nterm": "operation"
},
"@modularity, value and exceptions to the mirroring hypothesis": {
"id": 516,
"nterm": "@modularity, value and exceptions to the mirroring hypothesis"
},
"@organizing global product development for complex engineered systems": {
"id": 547,
"nterm": "@organizing global product development for complex engineered systems"
},
"@mechanizing proof computing, risk, and trust": {
"id": 497,
"nterm": "@mechanizing proof computing, risk, and trust"
},
"key facility health monitoring": {
"id": 1149,
"nterm": "operation strategy"
},
"monitor risks": {
"id": 1137,
"nterm": "monitor risks"
},
"information management strategy": {
"id": 1296,
"nterm": "strategy documents"
},
"manual production scheduling": {
"id": 1149,
"nterm": "operation strategy"
},
"@fifty shades of requirements, part one – the spiral of death": {
"id": 276,
"nterm": "@fifty shades of requirements, part one – the spiral of death"
},
"@on company size": {
"id": 531,
"nterm": "@on company size"
},
"knowledge-based decision-making": {
"id": 1149,
"nterm": "operation strategy"
},
"disposal procedure": {
"id": 1024,
"nterm": "disposal procedure"
},
"@playing to win": {
"id": 573,
"nterm": "@playing to win"
},
"@a work breakdown structure that integrates different views in aircraft modification projects": {
"id": 45,
"nterm": "@a work breakdown structure that integrates different views in aircraft modification projects"
},
"@pre-milestone a and early-phase systems engineering a retrospective review and benefits for future air force systems acquisition": {
"id": 580,
"nterm": "@pre-milestone a and early-phase systems engineering a retrospective review and benefits for future air force systems acquisition"
},
"project portfolio": {
"id": 1242,
"nterm": "project portfolio"
},
"manage the design": {
"id": 1123,
"nterm": "manage the design"
},
"@contract-based requirements engineering": {
"id": 160,
"nterm": "@contract-based requirements engineering"
},
"operation enabling system requirements": {
"id": 1146,
"nterm": "operation enabling system requirements"
},
"@evidence on the role of firm capabilities in vertical integration decisions": {
"id": 260,
"nterm": "@evidence on the role of firm capabilities in vertical integration decisions"
},
"@coaching tools - the assessment": {
"id": 140,
"nterm": "@coaching tools - the assessment"
},
"@on the measure of intelligence": {
"id": 534,
"nterm": "@on the measure of intelligence"
},
"@integrated data as the foundation of systems engineering": {
"id": 414,
"nterm": "@integrated data as the foundation of systems engineering"
},
"@stretch goals the dark side of asking for miracles": {
"id": 712,
"nterm": "@stretch goals the dark side of asking for miracles"
},
"intelligent analysis and decision-making": {
"id": 1148,
"nterm": "operation report"
},
"@project governance": {
"id": 607,
"nterm": "@project governance"
},
"adopting mbse": {
"id": 942,
"nterm": "adopting mbse"
},
"@the one device the secret history of the iphone": {
"id": 834,
"nterm": "@the one device the secret history of the iphone"
},
"@incose systems engineering handbook a guide for system life cycle processes and activities": {
"id": 355,
"nterm": "@incose systems engineering handbook a guide for system life cycle processes and activities"
},
"@analyzing due process in the workplace": {
"id": 73,
"nterm": "@analyzing due process in the workplace"
},
"documentation map": {
"id": 1031,
"nterm": "documentation tree"
},
"verification planning and execution using mbse": {
"id": 1363,
"nterm": "verification planning and execution using mbse"
},
"@architectures of knowledge the european open science cloud": {
"id": 82,
"nterm": "@architectures of knowledge the european open science cloud"
},
"@engineering knowledge, type of design, and level of hierarchy further thoughts about what engineers know": {
"id": 242,
"nterm": "@engineering knowledge, type of design, and level of hierarchy further thoughts about what engineers know"
},
"improve the process": {
"id": 1061,
"nterm": "improve the process"
},
"verification report": {
"id": 1367,
"nterm": "verification report"
},
"@requirements schemas for large multidisciplinary projects": {
"id": 647,
"nterm": "@requirements schemas for large multidisciplinary projects"
},
"detail design and analysis using mbse": {
"id": 1016,
"nterm": "detail design and analysis using mbse"
},
"@the information structure of engineering proposals": {
"id": 823,
"nterm": "@the information structure of engineering proposals"
},
"@everyday engineering what engineers see": {
"id": 255,
"nterm": "@everyday engineering what engineers see"
},
"system operationally effective": {
"id": 1150,
"nterm": "operation"
},
"quality management evaluation report": {
"id": 1262,
"nterm": "reports"
},
"ensuring explicit management support for mbse": {
"id": 1033,
"nterm": "ensuring explicit management support for mbse"
},
"manage results of transition": {
"id": 1117,
"nterm": "manage results of transition"
},
"@project the just necessary structure to reach your goals": {
"id": 609,
"nterm": "@project the just necessary structure to reach your goals"
},
"@making infrastructure the dream of a common language": {
"id": 477,
"nterm": "@making infrastructure the dream of a common language"
},
"@communication and social order risk a sociological theory": {
"id": 144,
"nterm": "@communication and social order risk a sociological theory"
},
"manage the selected architecture": {
"id": 1125,
"nterm": "manage the selected architecture"
},
"supplied system": {
"id": 1297,
"nterm": "supplied system"
},
"@handbook of research on internationalization of entrepreneurial innovation in the global economy": {
"id": 318,
"nterm": "@handbook of research on internationalization of entrepreneurial innovation in the global economy"
},
"@first round review -- product articles": {
"id": 280,
"nterm": "@first round review -- product articles"
},
"@developing information infrastructure the tension between standardization and flexibility": {
"id": 209,
"nterm": "@developing information infrastructure the tension between standardization and flexibility"
},
"@competitive positioning, dominant design and vertical integration over the industry lifecycle": {
"id": 146,
"nterm": "@competitive positioning, dominant design and vertical integration over the industry lifecycle"
},
"@strategy survival guide": {
"id": 711,
"nterm": "@strategy survival guide"
},
"@pretrained transformers for text ranking bert and beyond": {
"id": 581,
"nterm": "@pretrained transformers for text ranking bert and beyond"
},
"@when will you think differently about programme delivery 4th global portfolio and programme management survey": {
"id": 907,
"nterm": "@when will you think differently about programme delivery 4th global portfolio and programme management survey"
},
"transition record": {
"id": 1341,
"nterm": "transition record"
},
"project plan": {
"id": 1243,
"nterm": "project schedule"
},
"@a model of new product development an empirical test": {
"id": 38,
"nterm": "@a model of new product development an empirical test"
},
"@product metrics cheat sheet": {
"id": 594,
"nterm": "@product metrics cheat sheet"
},
"quality assurance plan": {
"id": 1251,
"nterm": "quality assurance plan"
},
"@scientists' views of science, models of writing, and science writing practices": {
"id": 677,
"nterm": "@scientists' views of science, models of writing, and science writing practices"
},
"replacement system elements": {
"id": 1104,
"nterm": "maintenance enabling system"
},
"@ontology, ontologies and the i of fair": {
"id": 540,
"nterm": "@ontology, ontologies and the i of fair"
},
"trained operators and maintainers": {
"id": 1337,
"nterm": "trained operators and maintainers"
},
"validated requirements": {
"id": 1350,
"nterm": "validated requirements"
},
"maintenance record": {
"id": 1106,
"nterm": "maintenance record"
},
"@what color is your backlog": {
"id": 900,
"nterm": "@what color is your backlog"
},
"quality management record": {
"id": 1257,
"nterm": "quality management record"
},
"@perspectives on the information revolution": {
"id": 570,
"nterm": "@perspectives on the information revolution"
},
"unified monitoring of the oil and gas production system": {
"id": 1149,
"nterm": "operation strategy"
},
"@how technical communication textbooks fail engineering students": {
"id": 332,
"nterm": "@how technical communication textbooks fail engineering students"
},
"system elements": {
"id": 1319,
"nterm": "system elements"
},
"methods and tools": {
"id": 1135,
"nterm": "methods and tools"
},
"infrastructure management plan": {
"id": 1233,
"nterm": "project infrastructure needs"
},
"prepare for decisions": {
"id": 1204,
"nterm": "prepare for decisions"
},
"@is the current theory of construction a hindrance to innovation": {
"id": 434,
"nterm": "@is the current theory of construction a hindrance to innovation"
},
"@institutional work as logics shift the case of intel transformation to platform leader": {
"id": 412,
"nterm": "@institutional work as logics shift the case of intel transformation to platform leader"
},
"portfolio of projects": {
"id": 1242,
"nterm": "project portfolio"
},
"failure and lifetime data": {
"id": 1106,
"nterm": "maintenance record"
},
"unified linkage of the oil and gas production system": {
"id": 1149,
"nterm": "operation strategy"
},
"@how not to win a tech war": {
"id": 330,
"nterm": "@how not to win a tech war"
},
"@death hurts, but it is not fatal the postexit diffusion of knowledge created by innovative companies": {
"id": 183,
"nterm": "@death hurts, but it is not fatal the postexit diffusion of knowledge created by innovative companies"
},
"supply": {
"id": 1304,
"nterm": "supply"
},
"@sysml-v2-api-cookbook": {
"id": 719,
"nterm": "@sysml-v2-api-cookbook"
},
"@what is the future of systems engineering": {
"id": 905,
"nterm": "@what is the future of systems engineering"
},
"@chronicle of the death of a laboratory douglas engelbart and the failure of the knowledge workshop": {
"id": 135,
"nterm": "@chronicle of the death of a laboratory douglas engelbart and the failure of the knowledge workshop"
},
"@engineering philosophy": {
"id": 243,
"nterm": "@engineering philosophy"
},
"@the spatial and hierarchical organization of japanese and us multinational semiconductor firms": {
"id": 845,
"nterm": "@the spatial and hierarchical organization of japanese and us multinational semiconductor firms"
},
"@the challenger launch decision risky technology, culture, and deviance at nasa": {
"id": 757,
"nterm": "@the challenger launch decision risky technology, culture, and deviance at nasa"
},
"@causal reasoning in a logic with possible causal process semantics": {
"id": 128,
"nterm": "@causal reasoning in a logic with possible causal process semantics"
},
"@realizing the value of systems engineering": {
"id": 628,
"nterm": "@realizing the value of systems engineering"
},
"@designing software architectures a practical approach": {
"id": 202,
"nterm": "@designing software architectures a practical approach"
},
"mission analysis": {
"id": 973,
"nterm": "business or mission analysis"
},
"work breakdown structure, wbs": {
"id": 1371,
"nterm": "work breakdown structure, wbs"
},
"capturing and tracking of operating and maintenance activities": {
"id": 1106,
"nterm": "maintenance record"
},
"high-risk operations": {
"id": 1145,
"nterm": "operation constraints"
},
"call for proposals": {
"id": 934,
"nterm": "acquisition need"
},
"operation constraints": {
"id": 1145,
"nterm": "operation constraints"
},
"system element description": {
"id": 1317,
"nterm": "system element description"
},
"@requirements engineering": {
"id": 642,
"nterm": "@requirements engineering"
},
"decommission the system": {
"id": 1173,
"nterm": "perform operation"
},
"transition enabling system requirements": {
"id": 1340,
"nterm": "transition enabling system requirements"
},
"@why isn’t there a super-app in the west yet": {
"id": 915,
"nterm": "@why isn’t there a super-app in the west yet"
},
"define the project": {
"id": 1009,
"nterm": "define the project"
},
"@tacit knowledge, trust and the q of sapphire": {
"id": 732,
"nterm": "@tacit knowledge, trust and the q of sapphire"
},
"@iso iec 29155-4": {
"id": 379,
"nterm": "@iso iec 29155-4"
},
"@systematic sources of suboptimal interface design in large product development organizations": {
"id": 722,
"nterm": "@systematic sources of suboptimal interface design in large product development organizations"
},
"@ontologies in neo4j semantics and knowledge graphs": {
"id": 537,
"nterm": "@ontologies in neo4j semantics and knowledge graphs"
},
"prepare for implementation": {
"id": 1207,
"nterm": "prepare for implementation"
},
"production scenario": {
"id": 1149,
"nterm": "operation strategy"
},
"organization portfolio direction and constraints": {
"id": 1155,
"nterm": "organization portfolio direction and constraints"
},
"@plm strategy for developing specific medical devices and lower limb prosthesis at healthcare sector case reports from the academia": {
"id": 555,
"nterm": "@plm strategy for developing specific medical devices and lower limb prosthesis at healthcare sector case reports from the academia"
},
"disposed system": {
"id": 1029,
"nterm": "disposed system"
},
"limitation": {
"id": 1229,
"nterm": "project constraints"
},
"industrial chain upstream": {
"id": 1351,
"nterm": "validated system"
},
"@iso iec 26551": {
"id": 368,
"nterm": "@iso iec 26551"
},
"@a memetic paradigm of project management": {
"id": 36,
"nterm": "@a memetic paradigm of project management"
},
"maintenance agencies": {
"id": 1337,
"nterm": "trained operators and maintainers"
},
"human resource management report": {
"id": 1262,
"nterm": "reports"
},
"operation": {
"id": 1150,
"nterm": "operation"
},
"@roman pichler's product management blog": {
"id": 668,
"nterm": "@roman pichler's product management blog"
},
"@business motivation model (bmm)": {
"id": 112,
"nterm": "@business motivation model (bmm)"
},
"@the myths and the reality of problem-solving": {
"id": 833,
"nterm": "@the myths and the reality of problem-solving"
},
"@learning by shipping": {
"id": 453,
"nterm": "@learning by shipping"
},
"@the future of knowledge graphs in a world of large language models": {
"id": 769,
"nterm": "@the future of knowledge graphs in a world of large language models"
},
"@platforms, open user innovation, and ecosystems a strategic leadership perspective": {
"id": 572,
"nterm": "@platforms, open user innovation, and ecosystems a strategic leadership perspective"
},
"perform process evaluations": {
"id": 1174,
"nterm": "perform process evaluations"
},
"@benefitting from contributions to the android open source community": {
"id": 94,
"nterm": "@benefitting from contributions to the android open source community"
},
"systems installation and removal": {
"id": 1329,
"nterm": "systems installation and removal"
},
"@defining scenario": {
"id": 192,
"nterm": "@defining scenario"
},
"@the electrification of america the system builders": {
"id": 814,
"nterm": "@the electrification of america the system builders"
},
"quality assurance": {
"id": 1248,
"nterm": "quality assurance"
},
"@project management for construction fundamental concepts for owners, engineers, architects, and builders": {
"id": 611,
"nterm": "@project management for construction fundamental concepts for owners, engineers, architects, and builders"
},
"@helping the consumers and producers of standards, repositories and policies to enable fair data": {
"id": 319,
"nterm": "@helping the consumers and producers of standards, repositories and policies to enable fair data"
},
"@systems engineering and analysis": {
"id": 729,
"nterm": "@systems engineering and analysis"
},
"@entrepreneurs, contracts, and the failure of young firms": {
"id": 251,
"nterm": "@entrepreneurs, contracts, and the failure of young firms"
},
"organizational process performance measures data": {
"id": 1160,
"nterm": "organizational process performance measures data"
},
"@megaproject management lessons on risk and project management from the big dig": {
"id": 499,
"nterm": "@megaproject management lessons on risk and project management from the big dig"
},
"success metric": {
"id": 1196,
"nterm": "preliminary moe needs"
},
"great accident influence": {
"id": 1145,
"nterm": "operation constraints"
},
"interface definition": {
"id": 1081,
"nterm": "interface definition"
},
"@prince2 a practical handbook": {
"id": 582,
"nterm": "@prince2 a practical handbook"
},
"@perspectives on activity theory": {
"id": 569,
"nterm": "@perspectives on activity theory"
},
"personnel needs": {
"id": 1232,
"nterm": "project human resources needs"
},
"diagnostic evaluation": {
"id": 1146,
"nterm": "operation enabling system requirements"
},
"major stakeholder identification": {
"id": 1109,
"nterm": "major stakeholder identification"
},
"translating legacy document-centric product data to a model-centric approach": {
"id": 1346,
"nterm": "translating legacy document-centric product data to a model-centric approach"
},
"@measuring modularity engineering and management effects of different approaches": {
"id": 494,
"nterm": "@measuring modularity engineering and management effects of different approaches"
},
"quality assurance process": {
"id": 1251,
"nterm": "quality assurance plan"
},
"@arguing about causes in law a semi-formal framework for causal arguments": {
"id": 85,
"nterm": "@arguing about causes in law a semi-formal framework for causal arguments"
},
"monitor certification of operators": {
"id": 1173,
"nterm": "perform operation"
},
"staff resources needs": {
"id": 1232,
"nterm": "project human resources needs"
},
"@simplifying managing stakeholder expectations using the nine-system model and the holistic thinking perspectives": {
"id": 688,
"nterm": "@simplifying managing stakeholder expectations using the nine-system model and the holistic thinking perspectives"
},
"document system status": {
"id": 1173,
"nterm": "perform operation"
},
"sustainability": {
"id": 1306,
"nterm": "sustainability"
},
"certification scheme operation": {
"id": 983,
"nterm": "certification scheme operation"
},
"@service engineering—methodical development of new service products": {
"id": 681,
"nterm": "@service engineering—methodical development of new service products"
},
"intelligent safe operation of oil and gas production system": {
"id": 1351,
"nterm": "validated system"
},
"facilities management": {
"id": 1044,
"nterm": "facilities management"
},
"@managing successful proposals with prince2": {
"id": 483,
"nterm": "@managing successful proposals with prince2"
},
"technical performance data": {
"id": 1197,
"nterm": "preliminary tpm data"
},
"@medium-sized firms and the limits to growth a case study in the evolution of a spin-off firm": {
"id": 498,
"nterm": "@medium-sized firms and the limits to growth a case study in the evolution of a spin-off firm"
},
"@should project management be based on theories of economics or production": {
"id": 684,
"nterm": "@should project management be based on theories of economics or production"
},
"@fair principles interpretations and implementation considerations": {
"id": 271,
"nterm": "@fair principles interpretations and implementation considerations"
},
"r&d plan": {
"id": 1272,
"nterm": "semp"
},
"@guide to verification and validation may 2022": {
"id": 312,
"nterm": "@guide to verification and validation may 2022"
},
"manage the risk profile": {
"id": 1124,
"nterm": "manage the risk profile"
},
"@integrated quality of models and quality of maps": {
"id": 417,
"nterm": "@integrated quality of models and quality of maps"
},
"@value and benefits of model-based systems engineering (mbse) evidence from the literature": {
"id": 896,
"nterm": "@value and benefits of model-based systems engineering (mbse) evidence from the literature"
},
"detail design and analysis": {
"id": 1017,
"nterm": "detail design and analysis"
},
"@the structure of scientific revolutions": {
"id": 846,
"nterm": "@the structure of scientific revolutions"
},
"quality policy": {
"id": 1251,
"nterm": "quality assurance plan"
},
"@øresund bridge": {
"id": 927,
"nterm": "@øresund bridge"
},
"@a study on the model-based systems engineering process for developing the naval combat system": {
"id": 24,
"nterm": "@a study on the model-based systems engineering process for developing the naval combat system"
},
"manage results of implementation": {
"id": 1113,
"nterm": "manage results of implementation"
},
"acquisition agreement": {
"id": 933,
"nterm": "acquisition agreement"
},
"@lean startups aren’t cheap startups": {
"id": 452,
"nterm": "@lean startups aren’t cheap startups"
},
"@process people continued": {
"id": 584,
"nterm": "@process people continued"
},
"prepare for transition": {
"id": 1217,
"nterm": "prepare for transition"
},
"@core constructional ontology (cco) a constructional theory of parts, sets, and relations": {
"id": 172,
"nterm": "@core constructional ontology (cco) a constructional theory of parts, sets, and relations"
},
"@iso 18629 psl a standardised language for specifying and exchanging process information": {
"id": 359,
"nterm": "@iso 18629 psl a standardised language for specifying and exchanging process information"
},
"@a comprehensive survey of the actual causality literature": {
"id": 28,
"nterm": "@a comprehensive survey of the actual causality literature"
},
"perceived value of mbse": {
"id": 1162,
"nterm": "perceived value of mbse"
},
"@collaboration structure, communication media, and problems in scientific work teams": {
"id": 142,
"nterm": "@collaboration structure, communication media, and problems in scientific work teams"
},
"outline the project": {
"id": 1009,
"nterm": "define the project"
},
"@the technical shaping of technology real-world constraints and technical logic in edison electrical lighting system": {
"id": 848,
"nterm": "@the technical shaping of technology real-world constraints and technical logic in edison electrical lighting system"
},
"professional development": {
"id": 1223,
"nterm": "professional development"
},
"project constraints": {
"id": 1229,
"nterm": "project constraints"
},
"@visual-meta an approach to surfacing metadata": {
"id": 898,
"nterm": "@visual-meta an approach to surfacing metadata"
},
"@model-based systems engineering with opm and sysml": {
"id": 511,
"nterm": "@model-based systems engineering with opm and sysml"
},
"@enterprise ontology a human-centric approach to understanding the essence of organisation": {
"id": 250,
"nterm": "@enterprise ontology a human-centric approach to understanding the essence of organisation"
},
"project management process tailoring": {
"id": 1245,
"nterm": "project tailoring strategy"
},
"support concept": {
"id": 1088,
"nterm": "life cycle concepts"
},
"@hypothesis-driven entrepreneurship the lean startup": {
"id": 346,
"nterm": "@hypothesis-driven entrepreneurship the lean startup"
},
"@exploring modularity in services cases from tourism": {
"id": 266,
"nterm": "@exploring modularity in services cases from tourism"
},
"prepare for architecture definition": {
"id": 1202,
"nterm": "prepare for architecture definition"
},
"@science as a process an evolutionary account of the social and conceptual development of science": {
"id": 674,
"nterm": "@science as a process an evolutionary account of the social and conceptual development of science"
},
"maintenance planning": {
"id": 1209,
"nterm": "prepare for maintenance"
},
"@networks of power electrification in western society 1880-1930": {
"id": 526,
"nterm": "@networks of power electrification in western society 1880-1930"
},
"maintenance management": {
"id": 1108,
"nterm": "maintenance"
},
"operational availability constraints": {
"id": 1145,
"nterm": "operation constraints"
},
"execute the agreement": {
"id": 1040,
"nterm": "execute the agreement"
},
"@feature-based systems and software product line engineering a primer": {
"id": 275,
"nterm": "@feature-based systems and software product line engineering a primer"
},
"implementation constraint": {
"id": 1089,
"nterm": "life cycle constraints"
},
"@say it with charts the executive's guide to visual communication": {
"id": 672,
"nterm": "@say it with charts the executive's guide to visual communication"
},
"@iso iec tr 29110-1": {
"id": 389,
"nterm": "@iso iec tr 29110-1"
},
"system analysis report": {
"id": 1311,
"nterm": "system analysis report"
},
"oil and gas production system": {
"id": 1351,
"nterm": "validated system"
},
"@megaprojects and risk an anatomy of ambition": {
"id": 500,
"nterm": "@megaprojects and risk an anatomy of ambition"
},
"unscheduled servicing": {
"id": 1172,
"nterm": "perform maintenance"
},
"@more secrets of consulting the consultant tool kit": {
"id": 517,
"nterm": "@more secrets of consulting the consultant tool kit"
},
"@fairsharing as a community approach to standards, repositories and policies": {
"id": 272,
"nterm": "@fairsharing as a community approach to standards, repositories and policies"
},
"@a network approach to define modularity of components in complex products": {
"id": 16,
"nterm": "@a network approach to define modularity of components in complex products"
},
"@building information infrastructures for social worlds—the role of classifications and standards": {
"id": 109,
"nterm": "@building information infrastructures for social worlds—the role of classifications and standards"
},
"solution proposal": {
"id": 1302,
"nterm": "supply response"
},
"vee": {
"id": 1093,
"nterm": "life cycle models"
},
"@getting context back in engineering education": {
"id": 303,
"nterm": "@getting context back in engineering education"
},
"storage management": {
"id": 1295,
"nterm": "storage management"
},
"conversion of the mbse models into system simulations": {
"id": 995,
"nterm": "conversion of the mbse models into system simulations"
},
"prepare for design definition": {
"id": 1205,
"nterm": "prepare for design definition"
},
"@towards a methodology for knowledge reuse based on semantic repositories": {
"id": 869,
"nterm": "@towards a methodology for knowledge reuse based on semantic repositories"
},
"@rethinking organizational design for managing multiple projects": {
"id": 651,
"nterm": "@rethinking organizational design for managing multiple projects"
},
"@list of megaprojects": {
"id": 463,
"nterm": "@list of megaprojects"
},
"@system maintenance": {
"id": 720,
"nterm": "@system maintenance"
},
"@archimate 3 specification": {
"id": 79,
"nterm": "@archimate 3 specification"
},
"risk monitoring to proactive prevention": {
"id": 1149,
"nterm": "operation strategy"
},
"@the customer factory manifesto": {
"id": 758,
"nterm": "@the customer factory manifesto"
},
"@iso iec ieee 42020": {
"id": 388,
"nterm": "@iso iec ieee 42020"
},
"major scheduled servicing": {
"id": 1172,
"nterm": "perform maintenance"
},
"@how engineers write an empirical study of engineering report writing": {
"id": 326,
"nterm": "@how engineers write an empirical study of engineering report writing"
},
"system functional interface identification": {
"id": 1322,
"nterm": "system functional interface identification"
},
"system operator": {
"id": 1323,
"nterm": "system operator"
},
"macro decision analysis ability": {
"id": 1149,
"nterm": "operation strategy"
},
"manage operational support logistics": {
"id": 1173,
"nterm": "perform operation"
},
"@impact of various work-breakdown structures on project conceptualization": {
"id": 399,
"nterm": "@impact of various work-breakdown structures on project conceptualization"
},
"@an analysis of positionalism’s roles in use": {
"id": 69,
"nterm": "@an analysis of positionalism’s roles in use"
},
"real-time risk perception": {
"id": 1148,
"nterm": "operation report"
},
"@the model t a centennial history by robert casey": {
"id": 781,
"nterm": "@the model t a centennial history by robert casey"
},
"preliminary life cycle concepts": {
"id": 1200,
"nterm": "preliminary life cycle concepts"
},
"@choice and performance of governance mechanisms matching alliance governance to asset type": {
"id": 134,
"nterm": "@choice and performance of governance mechanisms matching alliance governance to asset type"
},
"@model based engineering and product line engineering combining two powerful approaches at raytheon": {
"id": 508,
"nterm": "@model based engineering and product line engineering combining two powerful approaches at raytheon"
},
"analyze operational problems": {
"id": 1173,
"nterm": "perform operation"
},
"@boeing 747 a history delivering the dream": {
"id": 102,
"nterm": "@boeing 747 a history delivering the dream"
},
"@when is a tool - multiple meanings of artifacts in human activity": {
"id": 906,
"nterm": "@when is a tool - multiple meanings of artifacts in human activity"
},
"project human resources needs": {
"id": 1232,
"nterm": "project human resources needs"
},
"@blame the mathematicians!": {
"id": 100,
"nterm": "@blame the mathematicians!"
},
"@iso iec 26556": {
"id": 369,
"nterm": "@iso iec 26556"
},
"life cycle stages": {
"id": 1093,
"nterm": "life cycle models"
},
"support concept draft": {
"id": 1200,
"nterm": "preliminary life cycle concepts"
},
"@how communities support innovative activities an exploration of assistance and sharing among end-users": {
"id": 334,
"nterm": "@how communities support innovative activities an exploration of assistance and sharing among end-users"
},
"@rogers commission report (space shuttle challenger disaster)": {
"id": 666,
"nterm": "@rogers commission report (space shuttle challenger disaster)"
},
"operating document-centric product data": {
"id": 1143,
"nterm": "operating document-centric product data"
},
"schedule constraint": {
"id": 1089,
"nterm": "life cycle constraints"
},
"capacity management": {
"id": 981,
"nterm": "capacity management"
},
"@business case analysis in new product development": {
"id": 114,
"nterm": "@business case analysis in new product development"
},
"track system performance": {
"id": 1173,
"nterm": "perform operation"
},
"knowledge management report": {
"id": 1262,
"nterm": "reports"
},
"operation strategy": {
"id": 1296,
"nterm": "strategy documents"
},
"@the printing press as an agent of change": {
"id": 838,
"nterm": "@the printing press as an agent of change"
},
"define system requirements": {
"id": 1007,
"nterm": "define system requirements"
},
"@the death of contract law": {
"id": 811,
"nterm": "@the death of contract law"
},
"procedures": {
"id": 1222,
"nterm": "procedures"
},
"@yes, 2-speed it is real, but not like you think": {
"id": 923,
"nterm": "@yes, 2-speed it is real, but not like you think"
},
"@the oxford handbook of project management": {
"id": 788,
"nterm": "@the oxford handbook of project management"
},
"problem description": {
"id": 1221,
"nterm": "problem or opportunity statement"
},
"@rethinking project management a structured literature review with a critical look at the brave new world": {
"id": 653,
"nterm": "@rethinking project management a structured literature review with a critical look at the brave new world"
},
"organizational policies, procedures, and assets": {
"id": 1159,
"nterm": "organizational policies, procedures, and assets"
},
"@cycraft classroom mitre attack vs cyber kill chain vs diamond model": {
"id": 180,
"nterm": "@cycraft classroom mitre attack vs cyber kill chain vs diamond model"
},
"@sprint how to solve big problems and test new ideas in just five days": {
"id": 705,
"nterm": "@sprint how to solve big problems and test new ideas in just five days"
},
"it strategy": {
"id": 1296,
"nterm": "strategy documents"
},
"project budget": {
"id": 1227,
"nterm": "project budget"
},
"@agendas, alternatives, and public policies": {
"id": 53,
"nterm": "@agendas, alternatives, and public policies"
},
"@how much you know versus how well i know you selecting a supplier for a technically innovative component": {
"id": 336,
"nterm": "@how much you know versus how well i know you selecting a supplier for a technically innovative component"
},
"@how does knowledge flow - interfirm patterns in the semiconductor industry": {
"id": 335,
"nterm": "@how does knowledge flow - interfirm patterns in the semiconductor industry"
},
"@a single garbage can model and the degree of anarchy in japanese firms": {
"id": 22,
"nterm": "@a single garbage can model and the degree of anarchy in japanese firms"
},
"@organizational records as genres": {
"id": 546,
"nterm": "@organizational records as genres"
},
"modeling the changes from a prior project": {
"id": 1136,
"nterm": "modeling the changes from a prior project"
},
"work breakdown structure": {
"id": 1372,
"nterm": "work breakdown structure"
},
"@examining adaptive case management to support processes for enterprise architecture management": {
"id": 262,
"nterm": "@examining adaptive case management to support processes for enterprise architecture management"
},
"design definition record": {
"id": 1013,
"nterm": "design definition record"
},
"@managed ecosystems and translucent institutional logics engaging communities": {
"id": 480,
"nterm": "@managed ecosystems and translucent institutional logics engaging communities"
},
"mbse piloting": {
"id": 1097,
"nterm": "mbse piloting"
},
"@20 years of quality of models": {
"id": 3,
"nterm": "@20 years of quality of models"
},
"@innovation, modularity, and vertical deintegration evidence from the early us auto industry": {
"id": 410,
"nterm": "@innovation, modularity, and vertical deintegration evidence from the early us auto industry"
},
"characterize the solution space": {
"id": 985,
"nterm": "characterize the solution space"
},
"@understanding the role of objects in cross-disciplinary collaboration": {
"id": 886,
"nterm": "@understanding the role of objects in cross-disciplinary collaboration"
},
"multi-scale risk evolution in oil and gas fields": {
"id": 1148,
"nterm": "operation report"
},
"@scientific theory and technological testability science, dynamometers, and water turbines in the 19th century": {
"id": 676,
"nterm": "@scientific theory and technological testability science, dynamometers, and water turbines in the 19th century"
},
"advertise the acquisition and select the supplier": {
"id": 944,
"nterm": "advertise the acquisition and select the supplier"
},
"execute mbse-based projects": {
"id": 1039,
"nterm": "execute mbse-based projects"
},
"@project-as-practice applying bourdieu theory of practice on project managers": {
"id": 615,
"nterm": "@project-as-practice applying bourdieu theory of practice on project managers"
},
"@lost roots how project management came to emphasize control over flexibility and novelty": {
"id": 466,
"nterm": "@lost roots how project management came to emphasize control over flexibility and novelty"
},
"@why are institutions the carriers of history path dependence and the evolution of conventions, organizations and institutions": {
"id": 913,
"nterm": "@why are institutions the carriers of history path dependence and the evolution of conventions, organizations and institutions"
},
"report malfunctions": {
"id": 1173,
"nterm": "perform operation"
},
"@should we use sysml modeling tools for requirements management": {
"id": 685,
"nterm": "@should we use sysml modeling tools for requirements management"
},
"design definition": {
"id": 1012,
"nterm": "design definition"
},
"systems engineering management plan": {
"id": 1272,
"nterm": "semp"
},
"pbs": {
"id": 1372,
"nterm": "work breakdown structure"
},
"@work packages - acqnotes": {
"id": 919,
"nterm": "@work packages - acqnotes"
},
"@software architecture metrics case studies to improve the quality of your architecture": {
"id": 694,
"nterm": "@software architecture metrics case studies to improve the quality of your architecture"
},
"@how digital information transforms project delivery models": {
"id": 324,
"nterm": "@how digital information transforms project delivery models"
},
"risk evolution status": {
"id": 1149,
"nterm": "operation strategy"
},
"candidate risks and opportunities": {
"id": 980,
"nterm": "candidate risks and opportunities"
},
"@the theory of the growth of the firm": {
"id": 801,
"nterm": "@the theory of the growth of the firm"
},
"@the art of product management with sachin rekhi": {
"id": 751,
"nterm": "@the art of product management with sachin rekhi"
},
"@processes for engineering a system": {
"id": 586,
"nterm": "@processes for engineering a system"
},
"forms and rules of risk propagation across space": {
"id": 1149,
"nterm": "operation strategy"
},
"functions tree": {
"id": 1321,
"nterm": "system function identification"
},
"@coaching - managing time": {
"id": 138,
"nterm": "@coaching - managing time"
},
"@the high cost of low performance. how will you improve business results": {
"id": 771,
"nterm": "@the high cost of low performance. how will you improve business results"
},
"certification standards": {
"id": 1151,
"nterm": "operator or maintainer training material"
},
"@its not luck": {
"id": 437,
"nterm": "@its not luck"
},
"@taking the fuzziness out of the fuzzy front end": {
"id": 733,
"nterm": "@taking the fuzziness out of the fuzzy front end"
},
"relate the architecture to design": {
"id": 1261,
"nterm": "relate the architecture to design"
},
"@product lifecycle management at viking range llc": {
"id": 591,
"nterm": "@product lifecycle management at viking range llc"
},
"@personal data stores building and trialling trusted data services": {
"id": 568,
"nterm": "@personal data stores building and trialling trusted data services"
},
"quality plan": {
"id": 1251,
"nterm": "quality assurance plan"
},
"@project portfolio selection from past to present": {
"id": 614,
"nterm": "@project portfolio selection from past to present"
},
"@the trimodal nature of software engineering salaries in the netherlands and europe": {
"id": 802,
"nterm": "@the trimodal nature of software engineering salaries in the netherlands and europe"
},
"@r&d organization in japanese": {
"id": 623,
"nterm": "@r&d organization in japanese"
},
"@the integrated program management report (ipmr) data item description (did) di-mgmt-81861a": {
"id": 776,
"nterm": "@the integrated program management report (ipmr) data item description (did) di-mgmt-81861a"
},
"@prince2 wiki project management": {
"id": 559,
"nterm": "@prince2 wiki project management"
},
"human resource management": {
"id": 1048,
"nterm": "human resource management"
},
"preliminary moe data": {
"id": 1195,
"nterm": "preliminary moe data"
},
"human resource management plan": {
"id": 1049,
"nterm": "human resource management plan"
},
"supply report": {
"id": 1301,
"nterm": "supply report"
},
"@the hubble space telescope optical systems failure report technical memorandum (tm)": {
"id": 773,
"nterm": "@the hubble space telescope optical systems failure report technical memorandum (tm)"
},
"establish and maintain an agreement": {
"id": 1034,
"nterm": "establish and maintain an agreement"
},
"invoice or bill": {
"id": 1288,
"nterm": "source documents"
},
"manage results of integration": {
"id": 1114,
"nterm": "manage results of integration"
},
"experience-based decision-making": {
"id": 1149,
"nterm": "operation strategy"
},
"data collection": {
"id": 1116,
"nterm": "manage results of operation"
},
"enhance the level of operation": {
"id": 1149,
"nterm": "operation strategy"
},
"@iso iec 29155-1": {
"id": 376,
"nterm": "@iso iec 29155-1"
},
"@lean design management in a major infrastructure project in uk": {
"id": 449,
"nterm": "@lean design management in a major infrastructure project in uk"
},
"@a history of design methodology": {
"id": 34,
"nterm": "@a history of design methodology"
},
"enabling system requirements from all applicable life cycle processes": {
"id": 1032,
"nterm": "enabling system requirements"
},
"@chapter 1 - corporate governance and control": {
"id": 131,
"nterm": "@chapter 1 - corporate governance and control"
},
"@twitter and slack product leader on eliminating doubt from decision-making": {
"id": 880,
"nterm": "@twitter and slack product leader on eliminating doubt from decision-making"
},
"maintenance enabling system": {
"id": 1104,
"nterm": "maintenance enabling system"
},
"@designing and learning a disjunction in contexts": {
"id": 204,
"nterm": "@designing and learning a disjunction in contexts"
},
"@ckh causal knowledge hierarchy for estimating structural causal models from data and priors": {
"id": 115,
"nterm": "@ckh causal knowledge hierarchy for estimating structural causal models from data and priors"
},
"@boeing 747 design and development since 1969": {
"id": 103,
"nterm": "@boeing 747 design and development since 1969"
},
"@the evolution of project management research": {
"id": 766,
"nterm": "@the evolution of project management research"
},
"@the book of why the new science of cause and effect": {
"id": 807,
"nterm": "@the book of why the new science of cause and effect"
},
"replace an existing system": {
"id": 1344,
"nterm": "transition"
},
"@how institutions think": {
"id": 328,
"nterm": "@how institutions think"
},
"account for operational availability": {
"id": 1173,
"nterm": "perform operation"
},
"@r&d and marketing communication during the fuzzy front-end": {
"id": 624,
"nterm": "@r&d and marketing communication during the fuzzy front-end"
},
"@management of virtual models with provenance information in the context of product lifecycle management industrial case studies": {
"id": 481,
"nterm": "@management of virtual models with provenance information in the context of product lifecycle management industrial case studies"
},
"@information security policies and procedures development framework for government agencies first edition - 1432 ah": {
"id": 408,
"nterm": "@information security policies and procedures development framework for government agencies first edition - 1432 ah"
},
"@the misalignment of product architecture and organizational structure in complex product development": {
"id": 830,
"nterm": "@the misalignment of product architecture and organizational structure in complex product development"
},
"@case management model and notation (cmmn)": {
"id": 124,
"nterm": "@case management model and notation (cmmn)"
},
"job safety": {
"id": 1149,
"nterm": "operation strategy"
},
"system software": {
"id": 1328,
"nterm": "system software"
},
"verified system": {
"id": 1370,
"nterm": "verified system"
},
"@iso iec 9126-1": {
"id": 380,
"nterm": "@iso iec 9126-1"
},
"@modularity in technology and organization": {
"id": 515,
"nterm": "@modularity in technology and organization"
},
"@afrl-ml-wp-tr-2001-4116 mereos final report for period 09 june 1995 - 18 july 2000": {
"id": 52,
"nterm": "@afrl-ml-wp-tr-2001-4116 mereos final report for period 09 june 1995 - 18 july 2000"
},
"hls__intelligent_safe_operation_and_maintenance_of_oil_and_gas_production_systems_1696499001760_0": {
"id": 1376,
"nterm": "hls__intelligent_safe_operation_and_maintenance_of_oil_and_gas_production_systems_1696499001760_0"
},
"decision report": {
"id": 1262,
"nterm": "reports"
},
"monitor qualification of operators": {
"id": 1173,
"nterm": "perform operation"
},
"@the lessons of forced distance learning software engineering approach in the gap of generations of educational software": {
"id": 780,
"nterm": "@the lessons of forced distance learning software engineering approach in the gap of generations of educational software"
},
"implementation": {
"id": 1060,
"nterm": "implementation"
},
"@designing a cyber attack information system for national situational awareness": {
"id": 203,
"nterm": "@designing a cyber attack information system for national situational awareness"
},
"satisfactory completion of corrective action requests": {
"id": 1147,
"nterm": "operation record"
},
"project management methodology tailoring": {
"id": 1245,
"nterm": "project tailoring strategy"
},
"@overview of an emerging standard on architecture evaluation – iso iec 42030": {
"id": 550,
"nterm": "@overview of an emerging standard on architecture evaluation – iso iec 42030"
},
"@lost in translation examining the complex relationship between prototyping and communication": {
"id": 465,
"nterm": "@lost in translation examining the complex relationship between prototyping and communication"
},
"perform operation": {
"id": 1173,
"nterm": "perform operation"
},
"semp": {
"id": 1272,
"nterm": "semp"
},
"maintenance decision": {
"id": 1147,
"nterm": "operation record"
},
"@coordination without hierarchy informal structures in multiorganizational systems": {
"id": 166,
"nterm": "@coordination without hierarchy informal structures in multiorganizational systems"
},
"@foundations of project management research an explicit and six-facet ontological framework": {
"id": 287,
"nterm": "@foundations of project management research an explicit and six-facet ontological framework"
},
"installation procedure": {
"id": 1070,
"nterm": "installation procedure"
},
"strategy documents": {
"id": 1296,
"nterm": "strategy documents"
},
"validation": {
"id": 1359,
"nterm": "validation"
},
"treat incidents and problems": {
"id": 1347,
"nterm": "treat incidents and problems"
},
"@astronomers mark time discipline and the personal equation": {
"id": 89,
"nterm": "@astronomers mark time discipline and the personal equation"
},
"@iso iec 26562": {
"id": 370,
"nterm": "@iso iec 26562"
},
"david dorgan": {
"id": 999,
"nterm": "david dorgan"
},
"maintenance concept": {
"id": 1088,
"nterm": "life cycle concepts"
},
"@the 2023 state of product management report": {
"id": 746,
"nterm": "@the 2023 state of product management report"
},
"perform integration": {
"id": 1170,
"nterm": "perform integration"
},
"@the product manager's desk reference, third edition": {
"id": 793,
"nterm": "@the product manager's desk reference, third edition"
},
"@designing engineers": {
"id": 205,
"nterm": "@designing engineers"
},
"@toward a contingent model of mirroring between product and organization a knowledge management perspective": {
"id": 867,
"nterm": "@toward a contingent model of mirroring between product and organization a knowledge management perspective"
},
"@software development effort estimation formal models or expert judgment": {
"id": 696,
"nterm": "@software development effort estimation formal models or expert judgment"
},
"document actions taken": {
"id": 1173,
"nterm": "perform operation"
},
"@coaching - thinking": {
"id": 139,
"nterm": "@coaching - thinking"
},
"perform maintenance": {
"id": 1172,
"nterm": "perform maintenance"
},
"@decision management (dm) as the engine for scalable cross domain systems engineering (se)": {
"id": 186,
"nterm": "@decision management (dm) as the engine for scalable cross domain systems engineering (se)"
},
"@an improved set of products for measuring systems engineering": {
"id": 67,
"nterm": "@an improved set of products for measuring systems engineering"
},
"information security": {
"id": 1065,
"nterm": "information security"
},
"@an engineer's writing and the corporate construction of knowledge": {
"id": 63,
"nterm": "@an engineer's writing and the corporate construction of knowledge"
},
"@manager survival guide to engineering laboratory automation": {
"id": 482,
"nterm": "@manager survival guide to engineering laboratory automation"
},
"operation record": {
"id": 1147,
"nterm": "operation record"
},
"@design management in building construction from theory to practice": {
"id": 196,
"nterm": "@design management in building construction from theory to practice"
},
"@business agility manifesto": {
"id": 111,
"nterm": "@business agility manifesto"
},
"project pipeline": {
"id": 1242,
"nterm": "project portfolio"
},
"@situational method engineering state-of-the-art review": {
"id": 690,
"nterm": "@situational method engineering state-of-the-art review"
},
"health management": {
"id": 1337,
"nterm": "trained operators and maintainers"
},
"@project governance and path creation in the early stages of finnish nuclear power projects": {
"id": 610,
"nterm": "@project governance and path creation in the early stages of finnish nuclear power projects"
},
"@moving towards an integrated set of products for measuring systems engineering": {
"id": 518,
"nterm": "@moving towards an integrated set of products for measuring systems engineering"
},
"@identifiers for the 21st century": {
"id": 396,
"nterm": "@identifiers for the 21st century"
},
"@specialisations of sequal": {
"id": 701,
"nterm": "@specialisations of sequal"
},
"@product design and development, 5th edition": {
"id": 587,
"nterm": "@product design and development, 5th edition"
},
"detail the project": {
"id": 1009,
"nterm": "define the project"
},
"@organizational capabilities in a government r&d enterprise": {
"id": 545,
"nterm": "@organizational capabilities in a government r&d enterprise"
},
"implementation record": {
"id": 1056,
"nterm": "implementation record"
},
"@generating a knowledge graph comprising linked data from a tweet — using nanotation": {
"id": 300,
"nterm": "@generating a knowledge graph comprising linked data from a tweet — using nanotation"
},
"@a survey of top-level ontologies to inform the ontological choices for a foundation data model version 1": {
"id": 41,
"nterm": "@a survey of top-level ontologies to inform the ontological choices for a foundation data model version 1"
},
"quality assurance evaluation report": {
"id": 1262,
"nterm": "reports"
},
"@clarivate global research report examines role of research assessment with a review of six regional systems": {
"id": 136,
"nterm": "@clarivate global research report examines role of research assessment with a review of six regional systems"
},
"manage system requirements": {
"id": 1121,
"nterm": "manage system requirements"
},
"@model-based development and evolution of information systems a quality approach": {
"id": 510,
"nterm": "@model-based development and evolution of information systems a quality approach"
},
"@ontology-versus pattern-based evaluation of process modeling languages a comparison": {
"id": 542,
"nterm": "@ontology-versus pattern-based evaluation of process modeling languages a comparison"
},
"daily inspection": {
"id": 1172,
"nterm": "perform maintenance"
},
"@experiment guide – accelerate innovation using trustworthy online controlled experiments": {
"id": 264,
"nterm": "@experiment guide – accelerate innovation using trustworthy online controlled experiments"
},
"@japan increasing organizational capabilities of large industrial enterprises 1880s–1980s": {
"id": 438,
"nterm": "@japan increasing organizational capabilities of large industrial enterprises 1880s–1980s"
},
"@structuring work distribution for global product development organizations": {
"id": 713,
"nterm": "@structuring work distribution for global product development organizations"
},
"@aircraft stories decentering the object in technoscience": {
"id": 57,
"nterm": "@aircraft stories decentering the object in technoscience"
},
"organization lesson learned": {
"id": 1154,
"nterm": "organization lesson learned"
},
"@offices are open systems": {
"id": 530,
"nterm": "@offices are open systems"
},
"@japanese project management kpm-innovation, development and improvement": {
"id": 439,
"nterm": "@japanese project management kpm-innovation, development and improvement"
},
"@the knowledge organization": {
"id": 778,
"nterm": "@the knowledge organization"
},
"@coaching - collaboration": {
"id": 137,
"nterm": "@coaching - collaboration"
},
"measurement sfia": {
"id": 1127,
"nterm": "measurement sfia"
},
"availability management": {
"id": 966,
"nterm": "availability management"
},
"@do artifacts have politics": {
"id": 222,
"nterm": "@do artifacts have politics"
},
"project performance measures data": {
"id": 1237,
"nterm": "project performance measures data"
},
"ishikawa diagram": {
"id": 1246,
"nterm": "qm corrective actions"
},
"@systems engineering and system definitions": {
"id": 727,
"nterm": "@systems engineering and system definitions"
},
"cost constraint": {
"id": 1089,
"nterm": "life cycle constraints"
},
"integration strategy": {
"id": 1296,
"nterm": "strategy documents"
},
"autonomy given to the mbse team": {
"id": 965,
"nterm": "autonomy given to the mbse team"
},
"transition constraints": {
"id": 1339,
"nterm": "transition constraints"
},
"project infrastructure requirements": {
"id": 1233,
"nterm": "project infrastructure needs"
},
"accepted system or system element": {
"id": 930,
"nterm": "accepted system or system element"
},
"@building a great work breakdown structure": {
"id": 108,
"nterm": "@building a great work breakdown structure"
},
"experienced personnel": {
"id": 1247,
"nterm": "qualified personnel"
},
"hls__insight_v18-2_0815_(model-based_systems_engineering)_1688551819185_0": {
"id": 1375,
"nterm": "hls__insight_v18-2_0815_(model-based_systems_engineering)_1688551819185_0"
},
"object-oriented systems engineering methodology (oosem)": {
"id": 1141,
"nterm": "object-oriented systems engineering methodology (oosem)"
},
"business or mission analysis": {
"id": 973,
"nterm": "business or mission analysis"
},
"system element documentation": {
"id": 1318,
"nterm": "system element documentation"
},
"@science in action how to follow scientists and engineers through society": {
"id": 675,
"nterm": "@science in action how to follow scientists and engineers through society"
},
"supply strategy": {
"id": 1303,
"nterm": "supply strategy"
},
"@interoperability for digital engineering systems": {
"id": 427,
"nterm": "@interoperability for digital engineering systems"
},
"@why big companies keep failing the stack fallacy": {
"id": 911,
"nterm": "@why big companies keep failing the stack fallacy"
},
"architecture modeling using mbse": {
"id": 957,
"nterm": "architecture modeling using mbse"
},
"system design description": {
"id": 1315,
"nterm": "system design description"
},
"@managing complexity the nine-system model": {
"id": 485,
"nterm": "@managing complexity the nine-system model"
},
"@rules of engagement, credibility and the political economy of organizational dissent": {
"id": 670,
"nterm": "@rules of engagement, credibility and the political economy of organizational dissent"
},
"@understanding engineering work and identity a cross-case analysis of engineers within six firms": {
"id": 884,
"nterm": "@understanding engineering work and identity a cross-case analysis of engineers within six firms"
},
"competitive bid request": {
"id": 934,
"nterm": "acquisition need"
},
"@criteria employed for go no-go decisions when developing successful highly innovative products": {
"id": 176,
"nterm": "@criteria employed for go no-go decisions when developing successful highly innovative products"
},
"self assessment of the performance level": {
"id": 1276,
"nterm": "self assessment of the performance level"
},
"@bottlenecks, modules and dynamic architectural capabilities": {
"id": 104,
"nterm": "@bottlenecks, modules and dynamic architectural capabilities"
},
"projects roadmap": {
"id": 1242,
"nterm": "project portfolio"
},
"documentation archive": {
"id": 1031,
"nterm": "documentation tree"
},
"@theoretical foundations of project management": {
"id": 859,
"nterm": "@theoretical foundations of project management"
},
"adoption of mbse": {
"id": 943,
"nterm": "adoption of mbse"
},
"@product scoping decisions": {
"id": 596,
"nterm": "@product scoping decisions"
},
"definition of an operation strategy": {
"id": 1149,
"nterm": "operation strategy"
},
"set of projects": {
"id": 1242,
"nterm": "project portfolio"
},
"translating legacy document-centric product data to mbse model": {
"id": 1345,
"nterm": "translating legacy document-centric product data to mbse model"
},
"@reconstructing project management": {
"id": 630,
"nterm": "@reconstructing project management"
},
"@ten insights on the interplay between evidence and policy": {
"id": 744,
"nterm": "@ten insights on the interplay between evidence and policy"
},
"@essence – kernel and language for software engineering methods version 1.2": {
"id": 253,
"nterm": "@essence – kernel and language for software engineering methods version 1.2"
},
"@enterprise systems engineering advances in the theory and practice": {
"id": 248,
"nterm": "@enterprise systems engineering advances in the theory and practice"
},
"disposal record": {
"id": 1025,
"nterm": "disposal record"
},
"@ontology-based access control for fair data": {
"id": 541,
"nterm": "@ontology-based access control for fair data"
},
"@the big dig project background": {
"id": 754,
"nterm": "@the big dig project background"
},
"@patterns of modularization the dynamics of product architecture in complex systems": {
"id": 563,
"nterm": "@patterns of modularization the dynamics of product architecture in complex systems"
},
"@web architecture metadata": {
"id": 899,
"nterm": "@web architecture metadata"
},
"life cycle concept draft": {
"id": 1200,
"nterm": "preliminary life cycle concepts"
},
"@the failure of risk management why it is broken and how to fix it": {
"id": 768,
"nterm": "@the failure of risk management why it is broken and how to fix it"
},
"@guide to needs and requirements may 2022": {
"id": 311,
"nterm": "@guide to needs and requirements may 2022"
},
"@agile 2008 - money for nothing and your change for free": {
"id": 54,
"nterm": "@agile 2008 - money for nothing and your change for free"
},
"project planning record": {
"id": 1240,
"nterm": "project planning record"
},
"@dominant designs, innovation shocks, and the follower's dilemma": {
"id": 229,
"nterm": "@dominant designs, innovation shocks, and the follower's dilemma"
},
"@knowledge based decision model for architecting and evolving complex system-of-systems": {
"id": 443,
"nterm": "@knowledge based decision model for architecting and evolving complex system-of-systems"
},
"knowledge management plan": {
"id": 1083,
"nterm": "knowledge management plan"
},
"manage knowledge, skills and knowledge assets": {
"id": 1112,
"nterm": "manage knowledge, skills and knowledge assets"
},
"technical management plan": {
"id": 1272,
"nterm": "semp"
},
"cheque": {
"id": 1288,
"nterm": "source documents"
},
"@paying people to lie the truth about the budgeting process": {
"id": 564,
"nterm": "@paying people to lie the truth about the budgeting process"
},
"competent personnel": {
"id": 1247,
"nterm": "qualified personnel"
},
"@how smart, connected products are transforming competition": {
"id": 337,
"nterm": "@how smart, connected products are transforming competition"
},
"@enacting the lean startup methodology": {
"id": 238,
"nterm": "@enacting the lean startup methodology"
},
"acquire and provide skills": {
"id": 931,
"nterm": "acquire and provide skills"
},
"@why is open access development so successful stigmergic organization and the economics of information": {
"id": 914,
"nterm": "@why is open access development so successful stigmergic organization and the economics of information"
},
"@deep learning with python": {
"id": 189,
"nterm": "@deep learning with python"
},
"@introduction to decision patterns": {
"id": 431,
"nterm": "@introduction to decision patterns"
},
"intelligent diagnosis": {
"id": 1149,
"nterm": "operation strategy"
},
"@project management toolbox tools and techniques for the practicing project manager": {
"id": 613,
"nterm": "@project management toolbox tools and techniques for the practicing project manager"
},
"@on the agenda of design management research": {
"id": 533,
"nterm": "@on the agenda of design management research"
},
"@do modular products lead to modular organizations": {
"id": 224,
"nterm": "@do modular products lead to modular organizations"
},
"project artifacts": {
"id": 1240,
"nterm": "project planning record"
},
"@leveraging decision patterns, a talk by john fitch": {
"id": 462,
"nterm": "@leveraging decision patterns, a talk by john fitch"
},
"@iw2022 ontologies usage in requirements": {
"id": 393,
"nterm": "@iw2022 ontologies usage in requirements"
},
"@integrative capabilities, vertical integration, and innovation over successive technology lifecycles": {
"id": 424,
"nterm": "@integrative capabilities, vertical integration, and innovation over successive technology lifecycles"
},
"prepare for supply": {
"id": 1213,
"nterm": "prepare for supply"
},
"@agile project management —agilism versus traditional approaches": {
"id": 56,
"nterm": "@agile project management —agilism versus traditional approaches"
},
"@the rework cycle why projects are mismanaged": {
"id": 796,
"nterm": "@the rework cycle why projects are mismanaged"
},
"@adaptive case management overview and research challenges": {
"id": 49,
"nterm": "@adaptive case management overview and research challenges"
},
"@knowledge and social imagery": {
"id": 445,
"nterm": "@knowledge and social imagery"
},
"@the engineering method and its implications for scientific, philosophical, and universal methods": {
"id": 764,
"nterm": "@the engineering method and its implications for scientific, philosophical, and universal methods"
},
"industrial chain midstream": {
"id": 1351,
"nterm": "validated system"
},
"@team of teams new rules of engagement for a complex world": {
"id": 735,
"nterm": "@team of teams new rules of engagement for a complex world"
},
"radio frequency engineering": {
"id": 1259,
"nterm": "radio frequency engineering"
},
"stakeholder requirements": {
"id": 1294,
"nterm": "stakeholder requirements"
},
"@guide to the systems engineering body of knowledge (sebok)": {
"id": 314,
"nterm": "@guide to the systems engineering body of knowledge (sebok)"
},
"portfolio management record": {
"id": 1193,
"nterm": "portfolio management record"
},
"@configuration of value chain activities": {
"id": 154,
"nterm": "@configuration of value chain activities"
},
"system functionality": {
"id": 1321,
"nterm": "system function identification"
},
"@rethinking organizational design for complex endeavors": {
"id": 650,
"nterm": "@rethinking organizational design for complex endeavors"
},
"@how to read & take notes like a phd student tips for reading fast efficiently for slow readers": {
"id": 341,
"nterm": "@how to read & take notes like a phd student tips for reading fast efficiently for slow readers"
},
"@fundamentals of service systems": {
"id": 298,
"nterm": "@fundamentals of service systems"
},
"@iec 81346-2": {
"id": 351,
"nterm": "@iec 81346-2"
},
"technical performance measurement": {
"id": 1198,
"nterm": "preliminary tpm needs"
},
"scott jackson": {
"id": 1274,
"nterm": "scott jackson"
},
"@the unreluctant litigant - an empirical analysis of japan turn to litigation": {
"id": 851,
"nterm": "@the unreluctant litigant - an empirical analysis of japan turn to litigation"
},
"@guide for the application of systems engineering in large infrastructure projects incose-tp-2010-007-01": {
"id": 310,
"nterm": "@guide for the application of systems engineering in large infrastructure projects incose-tp-2010-007-01"
},
"@the work breakdown structure in government contracting": {
"id": 855,
"nterm": "@the work breakdown structure in government contracting"
},
"@blackblot pmtk methodology product management glossary": {
"id": 99,
"nterm": "@blackblot pmtk methodology product management glossary"
},
"integration report": {
"id": 1262,
"nterm": "reports"
},
"@iso iec 29110-4-3": {
"id": 375,
"nterm": "@iso iec 29110-4-3"
},
"@man-made disasters why technology and organizations (sometimes) fail": {
"id": 479,
"nterm": "@man-made disasters why technology and organizations (sometimes) fail"
},
"@developing the requirements of a plm alm integration an industrial case study": {
"id": 210,
"nterm": "@developing the requirements of a plm alm integration an industrial case study"
},
"@integrating systems engineering with project management a current challenge": {
"id": 420,
"nterm": "@integrating systems engineering with project management a current challenge"
},
"operation service module": {
"id": 1351,
"nterm": "validated system"
},
"@the emergence of the memo as a managerial genre": {
"id": 815,
"nterm": "@the emergence of the memo as a managerial genre"
},
"cross-domain risk evolution": {
"id": 1148,
"nterm": "operation report"
},
"manage results of maintenance and logistics": {
"id": 1115,
"nterm": "manage results of maintenance and logistics"
},
"@graduate reference curriculum for systems engineering": {
"id": 308,
"nterm": "@graduate reference curriculum for systems engineering"
},
"documented and approved architecture": {
"id": 1145,
"nterm": "operation constraints"
},
"analyze stakeholder requirements": {
"id": 949,
"nterm": "analyze stakeholder requirements"
},
"system requirements": {
"id": 1327,
"nterm": "system requirements"
},
"solution class": {
"id": 946,
"nterm": "alternative solution classes"
},
"performance test result": {
"id": 1197,
"nterm": "preliminary tpm data"
},
"@the visible hand": {
"id": 853,
"nterm": "@the visible hand"
},
"@pmi lexicon of project management terms": {
"id": 557,
"nterm": "@pmi lexicon of project management terms"
},
"@discussion of the method conducting the engineer's approach to problem solving": {
"id": 221,
"nterm": "@discussion of the method conducting the engineer's approach to problem solving"
},
"@measuring myths cost reduction and the model t the assembly line and other stories": {
"id": 495,
"nterm": "@measuring myths cost reduction and the model t the assembly line and other stories"
},
"@specification integration facility (specif)": {
"id": 703,
"nterm": "@specification integration facility (specif)"
},
"@aligning systems engineering and project management standards to improve the management of processes": {
"id": 59,
"nterm": "@aligning systems engineering and project management standards to improve the management of processes"
},
"@construction management traditional versus bureaucratic methods": {
"id": 156,
"nterm": "@construction management traditional versus bureaucratic methods"
},
"@a brief history of project management": {
"id": 7,
"nterm": "@a brief history of project management"
},
"treat risks": {
"id": 1348,
"nterm": "treat risks"
},
"@iso iec 29110-2-1": {
"id": 372,
"nterm": "@iso iec 29110-2-1"
},
"high susceptibility to accidents": {
"id": 1145,
"nterm": "operation constraints"
},
"@the design of everyday things revised and expanded edition": {
"id": 761,
"nterm": "@the design of everyday things revised and expanded edition"
},
"acquisition need": {
"id": 934,
"nterm": "acquisition need"
},
"@from problem solvers to solution seekers dismantling knowledge boundaries at nasa": {
"id": 294,
"nterm": "@from problem solvers to solution seekers dismantling knowledge boundaries at nasa"
},
"@advanced project management best practices on implementation": {
"id": 51,
"nterm": "@advanced project management best practices on implementation"
},
"@product manager's desk reference": {
"id": 600,
"nterm": "@product manager's desk reference"
},
"@trustworthy product lifecycle management using blockchain technology—experience from the automotive ecosystem": {
"id": 879,
"nterm": "@trustworthy product lifecycle management using blockchain technology—experience from the automotive ecosystem"
},
"@causal decision theory": {
"id": 125,
"nterm": "@causal decision theory"
},
"transform stakeholder needs into stakeholder requirements": {
"id": 1338,
"nterm": "transform stakeholder needs into stakeholder requirements"
},
"@why the abstraction and reasoning corpus is interesting and important for ai": {
"id": 916,
"nterm": "@why the abstraction and reasoning corpus is interesting and important for ai"
},
"@pbs a major enabler for systems engineering": {
"id": 552,
"nterm": "@pbs a major enabler for systems engineering"
},
"project governance": {
"id": 1231,
"nterm": "project direction"
},
"maintenance process": {
"id": 1108,
"nterm": "maintenance"
},
"quality assurance of the oil and gas production system": {
"id": 1149,
"nterm": "operation strategy"
},
"@the essence of engineering and meta-engineering a work in progress": {
"id": 816,
"nterm": "@the essence of engineering and meta-engineering a work in progress"
},
"@system operation": {
"id": 721,
"nterm": "@system operation"
},
"@corbin on contracts volume three": {
"id": 169,
"nterm": "@corbin on contracts volume three"
},
"@minimum viable product a guide": {
"id": 506,
"nterm": "@minimum viable product a guide"
},
"@risk analysis and assessment modeling language (raaml) specification": {
"id": 663,
"nterm": "@risk analysis and assessment modeling language (raaml) specification"
},
"@slowed canonical progress in large fields of science": {
"id": 693,
"nterm": "@slowed canonical progress in large fields of science"
},
"identify on performance during operations": {
"id": 1116,
"nterm": "manage results of operation"
},
"petty cash voucher": {
"id": 1288,
"nterm": "source documents"
},
"@the writing consultant as cultural interpreter bridging cultural perspectives on the genre of the periodic engineering report": {
"id": 857,
"nterm": "@the writing consultant as cultural interpreter bridging cultural perspectives on the genre of the periodic engineering report"
},
"@iso iec 19770-5": {
"id": 363,
"nterm": "@iso iec 19770-5"
},
"life cycle concepts": {
"id": 1088,
"nterm": "life cycle concepts"
},
"risk propagation mechanism": {
"id": 1149,
"nterm": "operation strategy"
},
"maintenance plans": {
"id": 1107,
"nterm": "maintenance report"
},
"supply agreement": {
"id": 1298,
"nterm": "supply agreement"
},
"@natural symbols": {
"id": 523,
"nterm": "@natural symbols"
},
"self-operation and maintenance of the system": {
"id": 1149,
"nterm": "operation strategy"
},
"@lean startup a comprehensive historical review": {
"id": 451,
"nterm": "@lean startup a comprehensive historical review"
},
"failure of a single item of production equipment": {
"id": 1147,
"nterm": "operation record"
},
"@integrating plm into engineering education": {
"id": 418,
"nterm": "@integrating plm into engineering education"
},
"system analysis record": {
"id": 1310,
"nterm": "system analysis record"
},
"@marking the mind a history of memory": {
"id": 491,
"nterm": "@marking the mind a history of memory"
},
"quality control plan": {
"id": 1251,
"nterm": "quality assurance plan"
},
"make and manage decisions": {
"id": 1110,
"nterm": "make and manage decisions"
},
"validation constraint": {
"id": 1089,
"nterm": "life cycle constraints"
},
"configuration management record": {
"id": 991,
"nterm": "configuration management record"
},
"response to rfp": {
"id": 1302,
"nterm": "supply response"
},
"@digital twin to accelerate vaccine production": {
"id": 219,
"nterm": "@digital twin to accelerate vaccine production"
},
"@how buildings learn what happens after they are built": {
"id": 323,
"nterm": "@how buildings learn what happens after they are built"
},
"prepare for quality assurance": {
"id": 1211,
"nterm": "prepare for quality assurance"
},
"@transformation in action": {
"id": 876,
"nterm": "@transformation in action"
},
"assess architecture candidates": {
"id": 961,
"nterm": "assess architecture candidates"
},
"functional tree": {
"id": 1321,
"nterm": "system function identification"
},
"@essence of decision explaining the cuban missile crisis": {
"id": 252,
"nterm": "@essence of decision explaining the cuban missile crisis"
},
"project assessment and control record": {
"id": 1225,
"nterm": "project assessment and control record"
},
"brian gallagher": {
"id": 967,
"nterm": "brian gallagher"
},
"it infrastructure": {
"id": 1052,
"nterm": "it infrastructure"
},
"perform release control": {
"id": 1177,
"nterm": "perform release control"
},
"@a semiotic approach for guiding the visualizing of time and space in enterprise models": {
"id": 21,
"nterm": "@a semiotic approach for guiding the visualizing of time and space in enterprise models"
},
"prepare for disposal": {
"id": 1206,
"nterm": "prepare for disposal"
},
"service level management": {
"id": 1282,
"nterm": "service level management"
},
"analyze risks": {
"id": 948,
"nterm": "analyze risks"
},
"@insight_v18-2_0815 (model-based systems engineering)": {
"id": 357,
"nterm": "@insight_v18-2_0815 (model-based systems engineering)"
},
"@contract design as a firm capability an integration of learning and transaction cost perspectives": {
"id": 159,
"nterm": "@contract design as a firm capability an integration of learning and transaction cost perspectives"
},
"@plm case studies in japan": {
"id": 554,
"nterm": "@plm case studies in japan"
},
"@knowledge specialization, organizational coupling, and the boundaries of the firm why do firms know more than they make": {
"id": 446,
"nterm": "@knowledge specialization, organizational coupling, and the boundaries of the firm why do firms know more than they make"
},
"@corbin on contracts volume four": {
"id": 168,
"nterm": "@corbin on contracts volume four"
},
"predictive maintenance": {
"id": 1107,
"nterm": "maintenance report"
},
"deliver and support the product or service": {
"id": 1010,
"nterm": "deliver and support the product or service"
},
"goals and objectives": {
"id": 1296,
"nterm": "strategy documents"
},
"@prof michael levin prof irina rish - emergence, intelligence, transhumanism": {
"id": 605,
"nterm": "@prof michael levin prof irina rish - emergence, intelligence, transhumanism"
},
"@how to start a successful program. a panel discussion for midwest gateway incose chapter": {
"id": 342,
"nterm": "@how to start a successful program. a panel discussion for midwest gateway incose chapter"
},
"project retrospective": {
"id": 1235,
"nterm": "project lessons learned"
},
"@lets stop demonizing projects": {
"id": 459,
"nterm": "@lets stop demonizing projects"
},
"technical performance measures": {
"id": 1332,
"nterm": "tpm needs"
},
"manage system analysis": {
"id": 1120,
"nterm": "manage system analysis"
},
"validation procedure": {
"id": 1355,
"nterm": "validation procedure"
},
"@a comparative approach of japanese project management in construction, manufacturing and it industries": {
"id": 8,
"nterm": "@a comparative approach of japanese project management in construction, manufacturing and it industries"
},
"@development of risk-based work breakdown structure (wbs) standard to improve scheduling planning of airport construction work": {
"id": 214,
"nterm": "@development of risk-based work breakdown structure (wbs) standard to improve scheduling planning of airport construction work"
},
"evaluate alternative solution classes": {
"id": 1037,
"nterm": "evaluate alternative solution classes"
},
"@improving the systems engineering process with multilevel analysis of interactions": {
"id": 402,
"nterm": "@improving the systems engineering process with multilevel analysis of interactions"
},
"@the impact of information technology on coordination evidence from the b-2 stealth bomber": {
"id": 822,
"nterm": "@the impact of information technology on coordination evidence from the b-2 stealth bomber"
},
"@knowingly taking risk investment decision making in real estate development": {
"id": 442,
"nterm": "@knowingly taking risk investment decision making in real estate development"
},
"@evolution of information control and centralisation through stages of complex engineering design projects": {
"id": 261,
"nterm": "@evolution of information control and centralisation through stages of complex engineering design projects"
},
"@strategic planning at royal dutch shell": {
"id": 710,
"nterm": "@strategic planning at royal dutch shell"
},
"predictive warning": {
"id": 1146,
"nterm": "operation enabling system requirements"
},
"@systems engineering prozessmodell": {
"id": 725,
"nterm": "@systems engineering prozessmodell"
},
"documentation tree": {
"id": 1031,
"nterm": "documentation tree"
},
"@requirements engineering paper classification and evaluation criteria%3a a proposal and a discussion": {
"id": 646,
"nterm": "@requirements engineering paper classification and evaluation criteria%3a a proposal and a discussion"
},
"@reconstructing engineering from practice": {
"id": 631,
"nterm": "@reconstructing engineering from practice"
},
"@learning to communicate in science and engineering case studies from mit": {
"id": 455,
"nterm": "@learning to communicate in science and engineering case studies from mit"
},
"@building ontologies an introduction for engineers (part 1)": {
"id": 107,
"nterm": "@building ontologies an introduction for engineers (part 1)"
},
"prepare for integration": {
"id": 1208,
"nterm": "prepare for integration"
},
"qualified staff": {
"id": 1247,
"nterm": "qualified personnel"
},
"@ariadne towards a technology of coordination": {
"id": 86,
"nterm": "@ariadne towards a technology of coordination"
},
"@how to (actually) calculate cac": {
"id": 333,
"nterm": "@how to (actually) calculate cac"
},
"@work breakdown structures for projects, programs, and enterprises": {
"id": 921,
"nterm": "@work breakdown structures for projects, programs, and enterprises"
},
"goals and objectives.": {
"id": 1156,
"nterm": "organization strategic plan"
},
"@747 creating the world's first jumbo jet and other adventures from a life in aviation": {
"id": 5,
"nterm": "@747 creating the world's first jumbo jet and other adventures from a life in aviation"
},
"lifecycle model": {
"id": 1093,
"nterm": "life cycle models"
},
"@top 10 mistakes companies make": {
"id": 865,
"nterm": "@top 10 mistakes companies make"
},
"integration record": {
"id": 1076,
"nterm": "integration record"
},
"@proofs and refutations the logic of mathematical discovery": {
"id": 617,
"nterm": "@proofs and refutations the logic of mathematical discovery"
},
"@roles - how are they used in modelling": {
"id": 667,
"nterm": "@roles - how are they used in modelling"
},
"@systems opportunities and requirements": {
"id": 728,
"nterm": "@systems opportunities and requirements"
},
"validation constraints": {
"id": 1352,
"nterm": "validation constraints"
},
"organization infrastructure": {
"id": 1153,
"nterm": "organization infrastructure"
},
"@the guide to lean enablers for managing engineering programs": {
"id": 821,
"nterm": "@the guide to lean enablers for managing engineering programs"
},
"@find, vet and close the best product managers": {
"id": 277,
"nterm": "@find, vet and close the best product managers"
},
"prepare for system requirements definition": {
"id": 1215,
"nterm": "prepare for system requirements definition"
},
"process risk evolution": {
"id": 1148,
"nterm": "operation report"
},
"@the successful management of design a handbook of building design management": {
"id": 847,
"nterm": "@the successful management of design a handbook of building design management"
},
"@iso iec cd 24773-2": {
"id": 381,
"nterm": "@iso iec cd 24773-2"
},
"risk formation": {
"id": 1148,
"nterm": "operation report"
},
"business or mission analysis strategy": {
"id": 1296,
"nterm": "strategy documents"
},
"@from titanic to costa concordia—a century of lessons not learned": {
"id": 292,
"nterm": "@from titanic to costa concordia—a century of lessons not learned"
},
"@glossary of digital twins": {
"id": 306,
"nterm": "@glossary of digital twins"
},
"quality assurance record": {
"id": 1252,
"nterm": "quality assurance record"
},
"@how to develop product sense": {
"id": 343,
"nterm": "@how to develop product sense"
},
"@development of risk-based standardized work breakdown structure for quality planning of airport construction project": {
"id": 213,
"nterm": "@development of risk-based standardized work breakdown structure for quality planning of airport construction project"
},
"strategic plan": {
"id": 1296,
"nterm": "strategy documents"
},
"manage the stakeholder needs and requirements definition": {
"id": 1126,
"nterm": "manage the stakeholder needs and requirements definition"
},
"@technical coordination in engineering practice": {
"id": 737,
"nterm": "@technical coordination in engineering practice"
},
"preliminary tpm needs": {
"id": 1198,
"nterm": "preliminary tpm needs"
},
"share knowledge assets throughout the organization": {
"id": 1284,
"nterm": "share knowledge assets throughout the organization"
},
"full life cycle of operation and maintenance of oil and gas production systems": {
"id": 1088,
"nterm": "life cycle concepts"
},
"@project management a systems approach to planning, scheduling, and controlling": {
"id": 608,
"nterm": "@project management a systems approach to planning, scheduling, and controlling"
},
"measure of effectiveness": {
"id": 1196,
"nterm": "preliminary moe needs"
},
"implementation traceability": {
"id": 1059,
"nterm": "implementation traceability"
},
"risk interference effects": {
"id": 1145,
"nterm": "operation constraints"
},
"@identifying the criteria used for establishing work package size for project wbs": {
"id": 398,
"nterm": "@identifying the criteria used for establishing work package size for project wbs"
},
"@ontology for systems engineering - part 1 introduction to ontology": {
"id": 538,
"nterm": "@ontology for systems engineering - part 1 introduction to ontology"
},
"external condition": {
"id": 1229,
"nterm": "project constraints"
},
"measures of effectiveness data": {
"id": 1100,
"nterm": "moe data"
},
"@risk a user guide": {
"id": 661,
"nterm": "@risk a user guide"
},
"project infrastructure needs": {
"id": 1233,
"nterm": "project infrastructure needs"
},
"integration": {
"id": 1079,
"nterm": "integration"
},
"business requirements": {
"id": 978,
"nterm": "business requirements"
},
"@reviewing the ijpm for wbs the search for planning and control": {
"id": 659,
"nterm": "@reviewing the ijpm for wbs the search for planning and control"
},
"continuity management": {
"id": 994,
"nterm": "continuity management"
},
"business rule": {
"id": 978,
"nterm": "business requirements"
},
"@requisite organization a total system for effective managerial organization and managerial leadership for the 21st century": {
"id": 648,
"nterm": "@requisite organization a total system for effective managerial organization and managerial leadership for the 21st century"
},
"initial rvtm": {
"id": 1069,
"nterm": "initial rvtm"
},
"@the roadmap conundrum": {
"id": 797,
"nterm": "@the roadmap conundrum"
},
"security operations": {
"id": 1275,
"nterm": "security operations"
},
"@managing the design factory": {
"id": 488,
"nterm": "@managing the design factory"
},
"@framework for problem definition – a joint method of design thinking and systems thinking": {
"id": 288,
"nterm": "@framework for problem definition – a joint method of design thinking and systems thinking"
},
"assess the process": {
"id": 963,
"nterm": "assess the process"
},
"abnormality of a single item of production equipment": {
"id": 1147,
"nterm": "operation record"
},
"unclear control factors": {
"id": 1145,
"nterm": "operation constraints"
},
"fraca": {
"id": 1116,
"nterm": "manage results of operation"
},
"@technology and heterogeneous engineering the case of portuguese expansion": {
"id": 740,
"nterm": "@technology and heterogeneous engineering the case of portuguese expansion"
},
"@calling all systems - product line engineering (ple)": {
"id": 116,
"nterm": "@calling all systems - product line engineering (ple)"
},
"@records as genre": {
"id": 632,
"nterm": "@records as genre"
},
"success criteria": {
"id": 1196,
"nterm": "preliminary moe needs"
},
"certsafe": {
"id": 982,
"nterm": "certsafe"
},
"@the network of global corporate control": {
"id": 785,
"nterm": "@the network of global corporate control"
},
"supply response": {
"id": 1302,
"nterm": "supply response"
},
"@understanding metadata what is metadata, and what is it for a primer": {
"id": 882,
"nterm": "@understanding metadata what is metadata, and what is it for a primer"
},
"opportunity": {
"id": 1221,
"nterm": "problem or opportunity statement"
},
"@technology strategy, governance structure and interdivisional coordination": {
"id": 743,
"nterm": "@technology strategy, governance structure and interdivisional coordination"
},
"quality management report": {
"id": 1262,
"nterm": "reports"
},
"@a reverse engineering role-play to teach systems engineering methods": {
"id": 20,
"nterm": "@a reverse engineering role-play to teach systems engineering methods"
},
"@spreadsheet analysis and design": {
"id": 704,
"nterm": "@spreadsheet analysis and design"
},
"@the labyrinths of information challenging the wisdom of systems": {
"id": 779,
"nterm": "@the labyrinths of information challenging the wisdom of systems"
},
"@beyond mbse looking towards the next evolution in systems engineering": {
"id": 96,
"nterm": "@beyond mbse looking towards the next evolution in systems engineering"
},
"operate the system": {
"id": 1150,
"nterm": "operation"
},
"implement mbse before starting the projects": {
"id": 1054,
"nterm": "implement mbse before starting the projects"
},
"@an experiential approach to organization development, 8th edition": {
"id": 65,
"nterm": "@an experiential approach to organization development, 8th edition"
},
"@grounding the mirroring hypothesis towards a general theory of organization design in new product development": {
"id": 309,
"nterm": "@grounding the mirroring hypothesis towards a general theory of organization design in new product development"
},
"@integrating knowledge management with project management for project success": {
"id": 422,
"nterm": "@integrating knowledge management with project management for project success"
},
"program governance": {
"id": 1231,
"nterm": "project direction"
},
"@practice of case management": {
"id": 579,
"nterm": "@practice of case management"
},
"project chart": {
"id": 1243,
"nterm": "project schedule"
},
"develop skills": {
"id": 1020,
"nterm": "develop skills"
},
"@notes on formalizing context": {
"id": 528,
"nterm": "@notes on formalizing context"
},
"intelligent analysis": {
"id": 1149,
"nterm": "operation strategy"
},
"@comprehensive laboratory informatics a multilayer approach": {
"id": 149,
"nterm": "@comprehensive laboratory informatics a multilayer approach"
},
"problem or opportunity statement": {
"id": 1221,
"nterm": "problem or opportunity statement"
},
"@policy in 500 words uncertainty versus ambiguity": {
"id": 574,
"nterm": "@policy in 500 words uncertainty versus ambiguity"
},
"solution comparison": {
"id": 946,
"nterm": "alternative solution classes"
},
"@public policy analysis": {
"id": 620,
"nterm": "@public policy analysis"
},
"@decision making in systems engineering and management": {
"id": 185,
"nterm": "@decision making in systems engineering and management"
},
"@making do - the eighth category of waste": {
"id": 476,
"nterm": "@making do - the eighth category of waste"
},
"infrastructure management report": {
"id": 1262,
"nterm": "reports"
},
"@review of drawings in greek and roman architecture": {
"id": 658,
"nterm": "@review of drawings in greek and roman architecture"
},
"project tailoring strategy": {
"id": 1296,
"nterm": "strategy documents"
},
"capability metric": {
"id": 1196,
"nterm": "preliminary moe needs"
},
"piloting mbse": {
"id": 1185,
"nterm": "piloting mbse"
},
"@alfa laval’s oneplm": {
"id": 58,
"nterm": "@alfa laval’s oneplm"
},
"@engineering documentation control handbook configuration management and product lifecycle management 4th edition": {
"id": 239,
"nterm": "@engineering documentation control handbook configuration management and product lifecycle management 4th edition"
},
"monitor job performance": {
"id": 1173,
"nterm": "perform operation"
},
"@survey of model-based systems engineering (mbse) methodologies": {
"id": 717,
"nterm": "@survey of model-based systems engineering (mbse) methodologies"
},
"@iec 81346-1": {
"id": 350,
"nterm": "@iec 81346-1"
},
"@you and your research. transcription of the bell communications research": {
"id": 924,
"nterm": "@you and your research. transcription of the bell communications research"
},
"recommendations for appropriate action": {
"id": 1148,
"nterm": "operation report"
},
"the need for corrective design changes": {
"id": 1107,
"nterm": "maintenance report"
},
"recommend improvement": {
"id": 1173,
"nterm": "perform operation"
},
"@the big dig learning from a mega project": {
"id": 753,
"nterm": "@the big dig learning from a mega project"
},
"@inscribing behaviour in information infrastructure standards": {
"id": 411,
"nterm": "@inscribing behaviour in information infrastructure standards"
},
"preventive maintenance": {
"id": 1108,
"nterm": "maintenance"
},
"@an engine, not a camera how financial models shape markets": {
"id": 71,
"nterm": "@an engine, not a camera how financial models shape markets"
},
"kpi": {
"id": 1196,
"nterm": "preliminary moe needs"
},
"qa plan": {
"id": 1251,
"nterm": "quality assurance plan"
},
"@the waterfall model in large-scale development": {
"id": 854,
"nterm": "@the waterfall model in large-scale development"
},
"operational concept (opscon)": {
"id": 1088,
"nterm": "life cycle concepts"
},
"project review": {
"id": 1235,
"nterm": "project lessons learned"
},
"system requirements traceability": {
"id": 1326,
"nterm": "system requirements traceability"
},
"continued stakeholder satisfaction": {
"id": 1147,
"nterm": "operation record"
},
"documentation chart": {
"id": 1031,
"nterm": "documentation tree"
},
"@beyond representations towards an action-centric perspective on tangible interaction": {
"id": 97,
"nterm": "@beyond representations towards an action-centric perspective on tangible interaction"
},
"long-term vision of the system": {
"id": 1088,
"nterm": "life cycle concepts"
},
"comprehensive safety": {
"id": 1149,
"nterm": "operation strategy"
},
"measurement needs": {
"id": 1129,
"nterm": "measurement needs"
},
"@the dark side of modularity how decomposing problems can increase system complexity": {
"id": 759,
"nterm": "@the dark side of modularity how decomposing problems can increase system complexity"
},
"establish design characteristics and design enablers related to each system element": {
"id": 1035,
"nterm": "establish design characteristics and design enablers related to each system element"
},
"@making sense of the multi-party contractual arrangements of project partnering, project alliancing and integrated project delivery": {
"id": 478,
"nterm": "@making sense of the multi-party contractual arrangements of project partnering, project alliancing and integrated project delivery"
},
"@towards an epistemology of scientific illustration": {
"id": 871,
"nterm": "@towards an epistemology of scientific illustration"
},
"mop data": {
"id": 1128,
"nterm": "measurement data"
},
"risk management strategy": {
"id": 1296,
"nterm": "strategy documents"
},
"@join the readi revolution – readi": {
"id": 440,
"nterm": "@join the readi revolution – readi"
},
"elucidate the risk propagation mechanism across devices": {
"id": 1149,
"nterm": "operation strategy"
},
"@understanding complex systems through mental models and shared experiences a case study": {
"id": 883,
"nterm": "@understanding complex systems through mental models and shared experiences a case study"
},
"@incose model-based capabilities matrix and user’s guide version 1": {
"id": 353,
"nterm": "@incose model-based capabilities matrix and user’s guide version 1"
},
"data perception": {
"id": 1146,
"nterm": "operation enabling system requirements"
},
"alternative solution classes": {
"id": 946,
"nterm": "alternative solution classes"
},
"@amateurs talk strategy, professionals talk logistics — that is kind of true in it as well": {
"id": 62,
"nterm": "@amateurs talk strategy, professionals talk logistics — that is kind of true in it as well"
},
"@bfo classifier aligning domain ontologies to bfo": {
"id": 92,
"nterm": "@bfo classifier aligning domain ontologies to bfo"
},
"@from page to stage how theories of genre and situated learning help introduce engineering students to discipline‐specific communication": {
"id": 293,
"nterm": "@from page to stage how theories of genre and situated learning help introduce engineering students to discipline‐specific communication"
},
"@the model thinker what you need to know to make data work for you": {
"id": 782,
"nterm": "@the model thinker what you need to know to make data work for you"
},
"restriction": {
"id": 1229,
"nterm": "project constraints"
},
"@interorganizational alliances and the performance of firms a study of growth and innovation rates in a high-technology industry": {
"id": 428,
"nterm": "@interorganizational alliances and the performance of firms a study of growth and innovation rates in a high-technology industry"
},
"@product team faq": {
"id": 597,
"nterm": "@product team faq"
},
"@iec 62264 enterprise-control system integration": {
"id": 348,
"nterm": "@iec 62264 enterprise-control system integration"
},
"life cycle model management": {
"id": 1087,
"nterm": "life cycle model management"
},
"assess alternatives for obtaining system elements": {
"id": 960,
"nterm": "assess alternatives for obtaining system elements"
},
"project direction": {
"id": 1231,
"nterm": "project direction"
},
"edge-cloud collaborative safe operation": {
"id": 1149,
"nterm": "operation strategy"
},
"data-based equipment condition identification": {
"id": 1146,
"nterm": "operation enabling system requirements"
},
"@genres of organizational communication a structurational approach to studying communication and media": {
"id": 302,
"nterm": "@genres of organizational communication a structurational approach to studying communication and media"
},
"@localization of industry and vertical disintegration": {
"id": 464,
"nterm": "@localization of industry and vertical disintegration"
},
"final rvtm": {
"id": 1046,
"nterm": "final rvtm"
},
"@stakeholder needs definition - sebok": {
"id": 706,
"nterm": "@stakeholder needs definition - sebok"
},
"@iw2022 requirements management with sharepoint": {
"id": 394,
"nterm": "@iw2022 requirements management with sharepoint"
},
"@meshing agile and plan-driven development in safety-critical software a case study": {
"id": 503,
"nterm": "@meshing agile and plan-driven development in safety-critical software a case study"
},
"@a waterfall systems development methodology seriously": {
"id": 27,
"nterm": "@a waterfall systems development methodology seriously"
},
"@diffusion of innovations": {
"id": 216,
"nterm": "@diffusion of innovations"
},
"measurement strategy": {
"id": 1296,
"nterm": "strategy documents"
},
"@quality of business process models": {
"id": 621,
"nterm": "@quality of business process models"
},
"@use of industry 4.0 concepts to use the voice of the product in the product development process in the automotive industry": {
"id": 889,
"nterm": "@use of industry 4.0 concepts to use the voice of the product in the product development process in the automotive industry"
},
"system function definition": {
"id": 1320,
"nterm": "system function definition"
},
"project status report": {
"id": 1262,
"nterm": "reports"
},
"life cycle model management record": {
"id": 1091,
"nterm": "life cycle model management record"
},
"@cross-pacific internationalization of r&d by us and japanese firms": {
"id": 178,
"nterm": "@cross-pacific internationalization of r&d by us and japanese firms"
},
"system maintains key functions": {
"id": 1150,
"nterm": "operation"
},
"@learning to contract evidence from the personal computer industry": {
"id": 457,
"nterm": "@learning to contract evidence from the personal computer industry"
},
"@r&d, organization structure, and the development of corporate technological knowledge": {
"id": 625,
"nterm": "@r&d, organization structure, and the development of corporate technological knowledge"
},
"@prof noam chomsky (special edition)": {
"id": 606,
"nterm": "@prof noam chomsky (special edition)"
},
"@situation calculus semantics for actual causality": {
"id": 689,
"nterm": "@situation calculus semantics for actual causality"
},
"@defining system a comprehensive approach": {
"id": 190,
"nterm": "@defining system a comprehensive approach"
},
"@the politics of formal representations wizards, gurus, and organizational complexity": {
"id": 837,
"nterm": "@the politics of formal representations wizards, gurus, and organizational complexity"
},
"perception of roi from mbse": {
"id": 1163,
"nterm": "perception of roi from mbse"
},
"portfolio management report": {
"id": 1262,
"nterm": "reports"
},
"bottleneck": {
"id": 1229,
"nterm": "project constraints"
},
"finalize the disposal": {
"id": 1047,
"nterm": "finalize the disposal"
},
"@the pmte paradigm exploring the relationship between systems engineering process and tools": {
"id": 789,
"nterm": "@the pmte paradigm exploring the relationship between systems engineering process and tools"
},
"@the global skills and competency framework for a digital world": {
"id": 819,
"nterm": "@the global skills and competency framework for a digital world"
},
"@design sprint for complex system architecture analysis": {
"id": 195,
"nterm": "@design sprint for complex system architecture analysis"
},
"@the value proposition of systems engineering": {
"id": 803,
"nterm": "@the value proposition of systems engineering"
},
"documentation outline": {
"id": 1031,
"nterm": "documentation tree"
},
"maintenance strategy": {
"id": 1103,
"nterm": "maintenance constraints"
},
"project assessment and control strategy": {
"id": 1296,
"nterm": "strategy documents"
},
"@tricks of the trade how to think about your research while you're doing it": {
"id": 878,
"nterm": "@tricks of the trade how to think about your research while you're doing it"
},
"@effective model-based systems engineering": {
"id": 233,
"nterm": "@effective model-based systems engineering"
},
"prohibition": {
"id": 1229,
"nterm": "project constraints"
},
"verification strategy": {
"id": 1368,
"nterm": "verification strategy"
},
"@computerized systems in the modern laboratory a practical guide": {
"id": 152,
"nterm": "@computerized systems in the modern laboratory a practical guide"
},
"operator or maintainer training material": {
"id": 1151,
"nterm": "operator or maintainer training material"
},
"technical performance": {
"id": 1198,
"nterm": "preliminary tpm needs"
},
"@nasa systems engineering handbook": {
"id": 520,
"nterm": "@nasa systems engineering handbook"
},
"@capabilities structure, agency, and evolution": {
"id": 121,
"nterm": "@capabilities structure, agency, and evolution"
},
"spiral": {
"id": 1093,
"nterm": "life cycle models"
},
"@lean enterprise how high performance organizations innovate at scale": {
"id": 450,
"nterm": "@lean enterprise how high performance organizations innovate at scale"
},
"@examining the role of model texts in writing instruction": {
"id": 263,
"nterm": "@examining the role of model texts in writing instruction"
},
"establish the process": {
"id": 1036,
"nterm": "establish the process"
},
"@conceptualizing and exploring the organizational effects of iso 9000 insights from the øresund bridge project": {
"id": 153,
"nterm": "@conceptualizing and exploring the organizational effects of iso 9000 insights from the øresund bridge project"
},
"@information access in the era of large pretrained neural models": {
"id": 405,
"nterm": "@information access in the era of large pretrained neural models"
},
"@identifying value in the engineering enterprise": {
"id": 397,
"nterm": "@identifying value in the engineering enterprise"
},
"change control": {
"id": 984,
"nterm": "change control"
},
"aleksandr turkhanov": {
"id": 945,
"nterm": "aleksandr turkhanov"
},
"judge external information through mechanism models": {
"id": 1146,
"nterm": "operation enabling system requirements"
},
"risk report": {
"id": 1270,
"nterm": "risk report"
},
"develop the operational concept and other lifecycle concepts": {
"id": 1021,
"nterm": "develop the operational concept and other lifecycle concepts"
},
"customer satisfaction inputs": {
"id": 997,
"nterm": "customer satisfaction inputs"
},
"delivery of services": {
"id": 1147,
"nterm": "operation record"
},
"@risk acceptability according to the social sciences": {
"id": 662,
"nterm": "@risk acceptability according to the social sciences"
},
"@master or servant — insight in and consequences of the it revolution": {
"id": 492,
"nterm": "@master or servant — insight in and consequences of the it revolution"
},
"@the organization and geography of japanese rnd results from a survey of japanese electronics and biotechnology firms": {
"id": 835,
"nterm": "@the organization and geography of japanese rnd results from a survey of japanese electronics and biotechnology firms"
},
"@the principles of product development flow second generation lean product development": {
"id": 791,
"nterm": "@the principles of product development flow second generation lean product development"
},
"process safety warning": {
"id": 1147,
"nterm": "operation record"
},
"@the brittania bridge the generation and diffusion of technical knowledge": {
"id": 756,
"nterm": "@the brittania bridge the generation and diffusion of technical knowledge"
},
"@an exploration towards a production theory and its application to construction": {
"id": 66,
"nterm": "@an exploration towards a production theory and its application to construction"
},
"@the museum conscience": {
"id": 831,
"nterm": "@the museum conscience"
},
"@the psychology of everyday things": {
"id": 840,
"nterm": "@the psychology of everyday things"
},
"@product lifecycle management (volume 3) the executive summary": {
"id": 598,
"nterm": "@product lifecycle management (volume 3) the executive summary"
},
"manage results of validation": {
"id": 1118,
"nterm": "manage results of validation"
},
"solution benchmark": {
"id": 946,
"nterm": "alternative solution classes"
},
"network support": {
"id": 1139,
"nterm": "network support"
},
"@governing engineering": {
"id": 307,
"nterm": "@governing engineering"
},
"@iso iec 29155-3": {
"id": 378,
"nterm": "@iso iec 29155-3"
},
"analysis situations": {
"id": 947,
"nterm": "analysis situations"
},
"evolution propagation": {
"id": 1148,
"nterm": "operation report"
},
"@product lifecycle management (plm)": {
"id": 589,
"nterm": "@product lifecycle management (plm)"
},
"@relining the garbage can of organizational decision-making modeling the arrival of problems and solutions as queues": {
"id": 639,
"nterm": "@relining the garbage can of organizational decision-making modeling the arrival of problems and solutions as queues"
},
"@what engineers know and how they know it": {
"id": 902,
"nterm": "@what engineers know and how they know it"
},
"@necessary and sufficient conditions for actual root causes": {
"id": 524,
"nterm": "@necessary and sufficient conditions for actual root causes"
},
"life cycle constraints": {
"id": 1089,
"nterm": "life cycle constraints"
},
"analyze system requirements": {
"id": 950,
"nterm": "analyze system requirements"
},
"@science and design methodology a review": {
"id": 673,
"nterm": "@science and design methodology a review"
},
"@design thinking vs lean startup a comparison of two user-driven innovation strategies": {
"id": 198,
"nterm": "@design thinking vs lean startup a comparison of two user-driven innovation strategies"
},
"@a principled approach to defining actual causation": {
"id": 39,
"nterm": "@a principled approach to defining actual causation"
},
"@being the (pareto) best in the world - lesswrong": {
"id": 93,
"nterm": "@being the (pareto) best in the world - lesswrong"
},
"@global infrastructure investment pwc the role of private capital in the delivery of essential assets and services": {
"id": 305,
"nterm": "@global infrastructure investment pwc the role of private capital in the delivery of essential assets and services"
},
"fault propagation": {
"id": 1147,
"nterm": "operation record"
},
"@habits of highly mathematical people": {
"id": 315,
"nterm": "@habits of highly mathematical people"
},
"@revenge of the pmo": {
"id": 654,
"nterm": "@revenge of the pmo"
},
"supply payment": {
"id": 1299,
"nterm": "supply payment"
},
"@technological overlap, technological capabilities, and resource recombination in technological acquisitions": {
"id": 739,
"nterm": "@technological overlap, technological capabilities, and resource recombination in technological acquisitions"
},
"@coaching tools - the plan": {
"id": 141,
"nterm": "@coaching tools - the plan"
},
"@investigation of challenger accident. report of the comittee on science and technology house of representatives": {
"id": 432,
"nterm": "@investigation of challenger accident. report of the comittee on science and technology house of representatives"
},
"life cycle processes": {
"id": 1093,
"nterm": "life cycle models"
},
"@contractual commitments, bargaining power, and governance inseparability%3a incorporating history into transaction cost theory": {
"id": 163,
"nterm": "@contractual commitments, bargaining power, and governance inseparability%3a incorporating history into transaction cost theory"
},
"@you thought you bought software – all you bought was a lie": {
"id": 925,
"nterm": "@you thought you bought software – all you bought was a lie"
},
"@the practice standard for earned value management—second edition": {
"id": 790,
"nterm": "@the practice standard for earned value management—second edition"
},
"@what firms do - coordination, identity, and learning": {
"id": 903,
"nterm": "@what firms do - coordination, identity, and learning"
},
"monitor the services": {
"id": 1150,
"nterm": "operation"
},
"mbse adoption": {
"id": 1095,
"nterm": "mbse adoption"
},
"strategy development": {
"id": 1296,
"nterm": "strategy documents"
},
"@value delivery modeling language specification": {
"id": 894,
"nterm": "@value delivery modeling language specification"
},
"acquisition concept": {
"id": 1088,
"nterm": "life cycle concepts"
},
"@inspired how to create tech products customers love": {
"id": 358,
"nterm": "@inspired how to create tech products customers love"
},
"rfq response": {
"id": 1302,
"nterm": "supply response"
},
"system scheduled maintenance": {
"id": 1108,
"nterm": "maintenance"
},
"@product work breakdown structure": {
"id": 602,
"nterm": "@product work breakdown structure"
},
"unified emergency response of the oil and gas production system": {
"id": 1149,
"nterm": "operation strategy"
},
"interface definition update identification": {
"id": 1080,
"nterm": "interface definition update identification"
},
"integration constraint": {
"id": 1089,
"nterm": "life cycle constraints"
},
"@finding language-market fit how to make customers feel like you ve read their minds": {
"id": 278,
"nterm": "@finding language-market fit how to make customers feel like you ve read their minds"
},
"template": {
"id": 1379,
"nterm": "template"
},
"@a conceptual model of agile software development in a safety-critical context a systematic literature review": {
"id": 29,
"nterm": "@a conceptual model of agile software development in a safety-critical context a systematic literature review"
},
"@the cost of poor software quality in the us a 2020 report": {
"id": 810,
"nterm": "@the cost of poor software quality in the us a 2020 report"
},
"human resource management record": {
"id": 1050,
"nterm": "human resource management record"
},
"@flexible work breakdown structure for integrated cost and schedule control": {
"id": 283,
"nterm": "@flexible work breakdown structure for integrated cost and schedule control"
},
"system analysis strategy": {
"id": 1312,
"nterm": "system analysis strategy"
},
"preventive action": {
"id": 1246,
"nterm": "qm corrective actions"
},
"@thinking clearly with data a guide to quantitative reasoning and analysis": {
"id": 862,
"nterm": "@thinking clearly with data a guide to quantitative reasoning and analysis"
},
"@assuring data integrity for life sciences": {
"id": 88,
"nterm": "@assuring data integrity for life sciences"
},
"@how to measure anything finding the value of intangibles in business": {
"id": 345,
"nterm": "@how to measure anything finding the value of intangibles in business"
},
"risk assessment": {
"id": 1148,
"nterm": "operation report"
},
"architecture definition strategy": {
"id": 1296,
"nterm": "strategy documents"
},
"@gantt charts revisited a critical analysis of its roots and implications to the management of projects today": {
"id": 299,
"nterm": "@gantt charts revisited a critical analysis of its roots and implications to the management of projects today"
},
"project evaluation": {
"id": 1235,
"nterm": "project lessons learned"
},
"measurement record": {
"id": 1130,
"nterm": "measurement record"
},
"prepare for the acquisition": {
"id": 1216,
"nterm": "prepare for the acquisition"
},
"organization strategic plan": {
"id": 1296,
"nterm": "strategy documents"
},
"@the theory of the firm critical perspectives on business and management": {
"id": 800,
"nterm": "@the theory of the firm critical perspectives on business and management"
},
"@the pyramid principle logic in writing and thinking": {
"id": 795,
"nterm": "@the pyramid principle logic in writing and thinking"
},
"business process": {
"id": 976,
"nterm": "business process"
},
"judge external information through data-driven models": {
"id": 1146,
"nterm": "operation enabling system requirements"
},
"documentation structure": {
"id": 1031,
"nterm": "documentation tree"
},
"@risk and culture an essay on the selection of technological and environmental dangers": {
"id": 664,
"nterm": "@risk and culture an essay on the selection of technological and environmental dangers"
},
"@integrating program management and systems engineering methods, tools, and organizational systems for improving performance": {
"id": 419,
"nterm": "@integrating program management and systems engineering methods, tools, and organizational systems for improving performance"
},
"@melanie mitchell - the collapse of artificial intelligence": {
"id": 501,
"nterm": "@melanie mitchell - the collapse of artificial intelligence"
},
"@developing a framework for describing and comparing indoor maps": {
"id": 207,
"nterm": "@developing a framework for describing and comparing indoor maps"
},
"@development and comparative analysis of the project management bodies of knowledge": {
"id": 211,
"nterm": "@development and comparative analysis of the project management bodies of knowledge"
},
"human assets requirements": {
"id": 1232,
"nterm": "project human resources needs"
},
"@power, technology and the phenomenology of conventions on being allergic to onions": {
"id": 575,
"nterm": "@power, technology and the phenomenology of conventions on being allergic to onions"
},
"acquisition strategy": {
"id": 1296,
"nterm": "strategy documents"
},
"lessons learned": {
"id": 1235,
"nterm": "project lessons learned"
},
"architecture traceability": {
"id": 959,
"nterm": "architecture traceability"
},
"@mapqual understanding quality in cartographic maps": {
"id": 467,
"nterm": "@mapqual understanding quality in cartographic maps"
},
"project post-mortem": {
"id": 1235,
"nterm": "project lessons learned"
},
"@improving performance how to manage the white space on the organization chart": {
"id": 401,
"nterm": "@improving performance how to manage the white space on the organization chart"
},
"@towards an ontology for scenario definition for the assessment of automated vehicles an object-oriented framework": {
"id": 872,
"nterm": "@towards an ontology for scenario definition for the assessment of automated vehicles an object-oriented framework"
},
"evolve the system to meet changing mission or business needs": {
"id": 1173,
"nterm": "perform operation"
},
"@theory of constraints": {
"id": 860,
"nterm": "@theory of constraints"
},
"@iso iec ieee 21839": {
"id": 383,
"nterm": "@iso iec ieee 21839"
},
"application support": {
"id": 952,
"nterm": "application support"
},
"@where the big bucks (will) come from – implementing product line engineering for railway rolling stock": {
"id": 909,
"nterm": "@where the big bucks (will) come from – implementing product line engineering for railway rolling stock"
},
"@cracking the pm interview how to land a product manager job in technology": {
"id": 173,
"nterm": "@cracking the pm interview how to land a product manager job in technology"
},
"operation of system": {
"id": 1150,
"nterm": "operation"
},
"maintenance activities": {
"id": 1108,
"nterm": "maintenance"
},
"decision management": {
"id": 1000,
"nterm": "decision management"
},
"@everyday problem solving in engineering lessons for engineering educators": {
"id": 257,
"nterm": "@everyday problem solving in engineering lessons for engineering educators"
},
"@do firms learn to create value - the case of alliances": {
"id": 223,
"nterm": "@do firms learn to create value - the case of alliances"
},
"@decision theory": {
"id": 187,
"nterm": "@decision theory"
},
"portfolio management": {
"id": 1191,
"nterm": "portfolio management"
},
"corrective maintenance": {
"id": 1108,
"nterm": "maintenance"
},
"@the accidental taxonomist taxonomies vs ontologies": {
"id": 747,
"nterm": "@the accidental taxonomist taxonomies vs ontologies"
},
"organization tailoring strategy": {
"id": 1296,
"nterm": "strategy documents"
},
"problem statement": {
"id": 1221,
"nterm": "problem or opportunity statement"
},
"@coordination mechanisms in a multi-agent perspective": {
"id": 165,
"nterm": "@coordination mechanisms in a multi-agent perspective"
},
"@iterative and incremental developments a brief history": {
"id": 435,
"nterm": "@iterative and incremental developments a brief history"
},
"fault prediction analysis": {
"id": 1148,
"nterm": "operation report"
},
"@iso iec dis 24773-4": {
"id": 382,
"nterm": "@iso iec dis 24773-4"
},
"@incose systems engineering measurement primer document no incose‐tp‐2010‐005‐02": {
"id": 356,
"nterm": "@incose systems engineering measurement primer document no incose‐tp‐2010‐005‐02"
},
"@on the methods of long-distance control vessels, navigation and the portuguese route to india": {
"id": 535,
"nterm": "@on the methods of long-distance control vessels, navigation and the portuguese route to india"
},
"project management (sfia)": {
"id": 1236,
"nterm": "project management (sfia)"
},
"manual production inspection": {
"id": 1149,
"nterm": "operation strategy"
},
"@database ethnographies using social science methodologies to enhance data analysis and interpretation": {
"id": 182,
"nterm": "@database ethnographies using social science methodologies to enhance data analysis and interpretation"
},
"business or mission analysis record": {
"id": 974,
"nterm": "business or mission analysis record"
},
"request for supply": {
"id": 1263,
"nterm": "request for supply"
},
"@iso iec ieee 29119-1": {
"id": 386,
"nterm": "@iso iec ieee 29119-1"
},
"@mece thinking engine for mbse": {
"id": 469,
"nterm": "@mece thinking engine for mbse"
},
"@are ideas getting harder to find": {
"id": 83,
"nterm": "@are ideas getting harder to find"
},
"@revisions, repairs, and rework on large projects": {
"id": 660,
"nterm": "@revisions, repairs, and rework on large projects"
},
"system analysis": {
"id": 1308,
"nterm": "system analysis"
},
"industrial chain downstream": {
"id": 1351,
"nterm": "validated system"
},
"@engineering and sociology in a military aircraft project a network analysis of technological change": {
"id": 241,
"nterm": "@engineering and sociology in a military aircraft project a network analysis of technological change"
},
"@organizing and evaluating research ideas": {
"id": 548,
"nterm": "@organizing and evaluating research ideas"
},
"@customer development, innovation, and decision-making biases int he lean startup": {
"id": 179,
"nterm": "@customer development, innovation, and decision-making biases int he lean startup"
},
"@plm at groupe psa": {
"id": 556,
"nterm": "@plm at groupe psa"
},
"@13 social studies of scientific imaging and visualization": {
"id": 2,
"nterm": "@13 social studies of scientific imaging and visualization"
},
"@a historical perspective on development of systems engineering discipline%3a a review and analysis": {
"id": 15,
"nterm": "@a historical perspective on development of systems engineering discipline%3a a review and analysis"
},
"@where do transactions come from modularity, transactions, and the boundaries of firms": {
"id": 908,
"nterm": "@where do transactions come from modularity, transactions, and the boundaries of firms"
},
"@an empirical study on the use of project management tools and techniques across project life-cycle and their impact on project success": {
"id": 70,
"nterm": "@an empirical study on the use of project management tools and techniques across project life-cycle and their impact on project success"
},
"@should you derive your it strategy from your business strategy": {
"id": 686,
"nterm": "@should you derive your it strategy from your business strategy"
},
"project management framework tailoring": {
"id": 1245,
"nterm": "project tailoring strategy"
},
"transition": {
"id": 1344,
"nterm": "transition"
},
"@confronting context effects in intelligence analysis how can mathematics help": {
"id": 155,
"nterm": "@confronting context effects in intelligence analysis how can mathematics help"
},
"@iso iec ieee 21840": {
"id": 384,
"nterm": "@iso iec ieee 21840"
},
"technology service management": {
"id": 1334,
"nterm": "technology service management"
},
"normal and stable operation of production equipment and facilities": {
"id": 1149,
"nterm": "operation strategy"
},
"@product lifecycle management business transformation in an engineering technology company": {
"id": 590,
"nterm": "@product lifecycle management business transformation in an engineering technology company"
},
"implementation constraints": {
"id": 1055,
"nterm": "implementation constraints"
},
"@the japanese firm the sources of competitive strength": {
"id": 777,
"nterm": "@the japanese firm the sources of competitive strength"
},
"@bracketing off the actors towards an action-centric research agenda": {
"id": 105,
"nterm": "@bracketing off the actors towards an action-centric research agenda"
},
"@designing decision tables part 2 fundamental styles": {
"id": 201,
"nterm": "@designing decision tables part 2 fundamental styles"
},
"@a complete set of systems thinking skills": {
"id": 9,
"nterm": "@a complete set of systems thinking skills"
},
"concept of operations (conops)": {
"id": 986,
"nterm": "concept of operations (conops)"
},
"operating data": {
"id": 1142,
"nterm": "operating data"
},
"enabling system requirements": {
"id": 1032,
"nterm": "enabling system requirements"
},
"sustain a pool of operators": {
"id": 1210,
"nterm": "prepare for operation"
},
"systems engineering plan": {
"id": 1272,
"nterm": "semp"
},
"@ict in health care sociotechnical approaches": {
"id": 347,
"nterm": "@ict in health care sociotechnical approaches"
},
"@just the boys playing on computers an activity theory analysis of differences in the cultures of two engineering firms": {
"id": 441,
"nterm": "@just the boys playing on computers an activity theory analysis of differences in the cultures of two engineering firms"
},
"cumbersome to maintain the models": {
"id": 996,
"nterm": "cumbersome to maintain the models"
},
"@product vs. feature teams": {
"id": 601,
"nterm": "@product vs. feature teams"
},
"@iso iec 29155-2": {
"id": 377,
"nterm": "@iso iec 29155-2"
},
"@falcon h2020": {
"id": 273,
"nterm": "@falcon h2020"
},
"acquisition reply": {
"id": 937,
"nterm": "acquisition reply"
},
"engineering plan": {
"id": 1272,
"nterm": "semp"
},
"@managing risk in large projects and complex procurements": {
"id": 487,
"nterm": "@managing risk in large projects and complex procurements"
},
"@on hidden heterogeneities complexity, formalism, and aircraft design": {
"id": 532,
"nterm": "@on hidden heterogeneities complexity, formalism, and aircraft design"
},
"transition strategy": {
"id": 1343,
"nterm": "transition strategy"
},
"@value streams": {
"id": 895,
"nterm": "@value streams"
},
"technical performance measurement data": {
"id": 1197,
"nterm": "preliminary tpm data"
},
"@10 best saas metrics for saas business growth in 2022": {
"id": 1,
"nterm": "@10 best saas metrics for saas business growth in 2022"
},
"@the translucent hand of managed ecosystems engaging communities for value creation and capture": {
"id": 850,
"nterm": "@the translucent hand of managed ecosystems engaging communities for value creation and capture"
},
"decision situation": {
"id": 1004,
"nterm": "decision situation"
},
"opscon draft": {
"id": 1200,
"nterm": "preliminary life cycle concepts"
},
"architecture modeling": {
"id": 958,
"nterm": "architecture modeling"
},
"maintenance knowledge generation on industrial internet": {
"id": 1149,
"nterm": "operation strategy"
},
"design definition strategy": {
"id": 1296,
"nterm": "strategy documents"
},
"disposal strategy": {
"id": 1296,
"nterm": "strategy documents"
},
"extracting models from code": {
"id": 1043,
"nterm": "extracting models from code"
},
"@project management in a long-term and global one-of-a-kind project": {
"id": 612,
"nterm": "@project management in a long-term and global one-of-a-kind project"
},
"performance management": {
"id": 1182,
"nterm": "performance management"
},
"@practice standard for scheduling - third edition": {
"id": 577,
"nterm": "@practice standard for scheduling - third edition"
},
"@transdisciplinary variation in engineering curricula. problems and means for solutions": {
"id": 875,
"nterm": "@transdisciplinary variation in engineering curricula. problems and means for solutions"
},
"capa": {
"id": 1246,
"nterm": "qm corrective actions"
},
"perform the transition": {
"id": 1179,
"nterm": "perform the transition"
},
"configuration management report": {
"id": 1262,
"nterm": "reports"
},
"extracting mbse models from program code": {
"id": 1042,
"nterm": "extracting mbse models from program code"
},
"@the evolution of large technological systems": {
"id": 817,
"nterm": "@the evolution of large technological systems"
},
"strategic roadmap": {
"id": 1296,
"nterm": "strategy documents"
},
"contract requirement": {
"id": 978,
"nterm": "business requirements"
},
"@natural systems and the systems engineering process a primer v4": {
"id": 522,
"nterm": "@natural systems and the systems engineering process a primer v4"
},
"@risk as a forensic resource": {
"id": 665,
"nterm": "@risk as a forensic resource"
},
"@production of large computer programs": {
"id": 603,
"nterm": "@production of large computer programs"
},
"identify analyze operational problems": {
"id": 1150,
"nterm": "operation"
},
"life cycle model management plan": {
"id": 1090,
"nterm": "life cycle model management plan"
},
"@innovating without information constraints organizations, communities, and innovation when information costs approach zero": {
"id": 409,
"nterm": "@innovating without information constraints organizations, communities, and innovation when information costs approach zero"
},
"system performance result": {
"id": 1197,
"nterm": "preliminary tpm data"
},
"stakeholder needs and requirements definition strategy": {
"id": 1296,
"nterm": "strategy documents"
},
"strategy execution": {
"id": 1296,
"nterm": "strategy documents"
},
"evaluate job performance": {
"id": 1173,
"nterm": "perform operation"
},
"project planner iso15288": {
"id": 1239,
"nterm": "project planner iso15288"
},
"@evidence & policy blog": {
"id": 259,
"nterm": "@evidence & policy blog"
},
"@overview regarding the main guidelines, standards and methodologies used in project management": {
"id": 551,
"nterm": "@overview regarding the main guidelines, standards and methodologies used in project management"
},
"@digital twin in industry state-of-the-art": {
"id": 220,
"nterm": "@digital twin in industry state-of-the-art"
},
"@promont – a project management ontology as a reference for virtual project organizations": {
"id": 560,
"nterm": "@promont – a project management ontology as a reference for virtual project organizations"
},
"stakeholder needs": {
"id": 1292,
"nterm": "stakeholder needs"
},
"source documents": {
"id": 1288,
"nterm": "source documents"
},
"maintenance enabling system requirements": {
"id": 1032,
"nterm": "enabling system requirements"
},
"@learning to teach writing to engineers": {
"id": 456,
"nterm": "@learning to teach writing to engineers"
},
"@iso iec 19770-2": {
"id": 362,
"nterm": "@iso iec 19770-2"
},
"verification record": {
"id": 1366,
"nterm": "verification record"
},
"system functions tree": {
"id": 1321,
"nterm": "system function identification"
},
"@usdl xg final report - w3c unified service description language": {
"id": 881,
"nterm": "@usdl xg final report - w3c unified service description language"
},
"@the art of doing science and engineering learning to learn": {
"id": 750,
"nterm": "@the art of doing science and engineering learning to learn"
},
"@lets talk about product management": {
"id": 460,
"nterm": "@lets talk about product management"
},
"usage data": {
"id": 1148,
"nterm": "operation report"
},
"project enabler": {
"id": 1233,
"nterm": "project infrastructure needs"
},
"@genesis and development of a scientific fact": {
"id": 301,
"nterm": "@genesis and development of a scientific fact"
},
"quality management guidelines": {
"id": 1255,
"nterm": "quality management guidelines"
},
"business function": {
"id": 971,
"nterm": "business function"
},
"validation report": {
"id": 1357,
"nterm": "validation report"
},
"@relational contracts and the theory of the firm": {
"id": 635,
"nterm": "@relational contracts and the theory of the firm"
},
"@the goal a process of ongoing improvement": {
"id": 820,
"nterm": "@the goal a process of ongoing improvement"
},
"risk evolution model": {
"id": 1149,
"nterm": "operation strategy"
},
"risk of unplanned downtime": {
"id": 1148,
"nterm": "operation report"
},
"@the work breakdown structure in software project management": {
"id": 856,
"nterm": "@the work breakdown structure in software project management"
},
"@all the best engineering advice i stole from non-technical people": {
"id": 60,
"nterm": "@all the best engineering advice i stole from non-technical people"
},
"slep": {
"id": 1150,
"nterm": "operation"
},
"operational cost data": {
"id": 1148,
"nterm": "operation report"
}
}
}