1.

Record Nr.

UNISA996467772303316

Titolo

Experience as philosophy : on the work of John J. McDermott / edited by James Campbell and Richard E. Hart

Pubbl/distr/stampa

New York, : Fordham University Press, 2006

ISBN

0-8232-2638-7

Descrizione fisica

Testo elettronico (PDF) (IX, 322 p.)

Collana

American philosophy series

Disciplina

191

Soggetti

McDermott, John J.

Lingua di pubblicazione

Inglese

Formato

Risorsa elettronica

Livello bibliografico

Monografia

Sommario/riassunto

Il filosofo John J. McDermott esce dalla lunga tradizione americana che vuole che l'obiettivo dell'indagine filosofica sia l'interpretazione dei significati aperti dell'esperienza, in modo che tutti noi possiamo vivere una vita più piena e ricca. Qui, gli autori di questi nove saggi esplorano le sue originalissime interpretazioni delle varie domande della filosofia sulla nostra esistenza. Come possiamo comprendere la natura della cultura americana e portare avanti i suoi importanti contributi? Qual è l'importanza personale dell'incarnazione, di vivere nella realizzazione della morte? In che modo il nostro ambiente fisico e personale nutre i corpi e gli spiriti? Cosa ci offre la ricerca deliberata di una moralità? Come portare avanti i compiti fondamentali dell'educazione per consentire a coloro che ci seguono di utilizzare il nostro passato condiviso per affrontare i problemi civili e spirituali? Quali sono le possibilità per la comunità? Insieme, questi saggi offrono una comprensione chiara e a più livelli della visione avvincente che McDermott ha presentato nel corso degli anni. In una postfazione, McDermott risponde alle domande e alle preoccupazioni degli autori. Questi saggi indicano che per lui la filosofia non è un'attività puramente cerebrale. La filosofia è, piuttosto, un mezzo intellettuale per esplorare la pienezza dell'esperienza umana, e funziona meglio quando opera nel contesto dell'ampio respiro delle discipline umanistiche. Allo stesso modo, per McDermott il sé non è un'entità sostanziale data. Al contrario, è relazionale, radicata geograficamente e



socialmente e danneggiata quando questi processi vitali falliscono. Il cammino umano è un progetto personale all'interno del quale devono essere creati significati provvisori per sostenere il nostro progresso.

2.

Record Nr.

UNINA9910795834203321

Autore

Buede Dennis M

Titolo

The Engineering Design of Systems : Models and Methods

Pubbl/distr/stampa

New York : , : John Wiley & Sons, Incorporated, , 2016

©2016

ISBN

9781119028062

9781119027904

Edizione

[3rd ed.]

Descrizione fisica

1 online resource (583 pages)

Collana

Wiley Series in Systems Engineering and Management Ser.

Altri autori (Persone)

MillerWilliam D

Disciplina

620.001/171

Soggetti

Systems engineering

Electronic books.

Lingua di pubblicazione

Inglese

Formato

Materiale a stampa

Livello bibliografico

Monografia

Nota di contenuto

The Engineering Design of Systems: Models and Methods -- Contents -- Preface -- About the Companion Website -- Part 1: Introduction, Overview, and Basic Knowledge -- Chapter 1: Introduction to Systems Engineering -- 1.1 Introduction -- 1.2 Overview of the Engineering of Systems -- 1.3 Approaches for Implementing Systems Engineering -- 1.3.1 TTDSE -- 1.3.2 The Waterfall Model of Software Engineering -- 1.3.3 The Spiral Model of Software Engineering -- 1.3.4 Object-Oriented Design -- 1.4 Modeling Approaches for Systems Engineering -- 1.4.1 Modeling Approaches for TTDSE -- 1.4.2 UML -- 1.4.3 DoDAF -- 1.4.4 SysML -- 1.5 Introducing the Concept of Architectures -- 1.6 Requirements -- 1.7 System's Life Cycle -- 1.8 Design and Integration Process -- 1.9 Types of Systems -- 1.10 Summary -- Chapter 2: Overview of the Systems Engineering Design Process -- 2.1 Introduction -- 2.2 Design Process -- 2.2.1 Key Terms -- 2.2.2 Design -- 2.2.3 Integration and Qualification -- 2.3 Key Systems Engineering Concepts -- 2.3.1 Operational Concept -- 2.3.2 External Systems



Diagram -- 2.3.3 Objectives Hierarchy -- 2.3.4 Requirements -- 2.3.5 Functions -- 2.3.6 Items -- 2.3.7 Components -- 2.3.8 Interfaces -- 2.3.9 Verification -- 2.3.10 Validation -- 2.3.11 Acceptance -- 2.4 Introduction to Sysml -- 2.5 Use of Core (Systems Engineering Tool) -- 2.5.1 Classes -- 2.5.2 Relations -- 2.5.3 Documents -- 2.6 Summary -- Chapter 3: Modeling and Sysml Modeling -- 3.1 Introduction -- 3.2 Models and Modeling -- 3.3 Sysml Modeling -- 3.4 Meta-System Modeling -- 3.5 Static Behavioral Process Modeling With IDEF0 -- 3.5.1 IDEF0 Semantics or Elements -- 3.5.2 IDEF0 Diagram Syntax -- 3.5.3 IDEF0 Model Syntax -- 3.5.4 IDEF0 Advanced Concepts -- 3.5.5 Systems Engineering Use of IDEF0 Models -- 3.6 Dynamic Behavioral Process Modeling With EFFBDs.

3.7 Structural Modeling of the System'S Components -- 3.8 Requirements Modeling -- 3.9 Performance Modeling -- 3.10 Summary -- Chapter 4: Discrete Mathematics: Sets, Relations, and Functions -- 4.1 Introduction -- 4.2 Sets -- 4.2.1 Writing Set Membership -- 4.2.2 Describing Members of a Set -- 4.2.3 Special Sets -- 4.2.4 Operations on Sets -- 4.2.5 Partitions -- 4.2.6 Power Set -- 4.3 Relations -- 4.3.1 Ordered Pairs and Cartesian Products -- 4.3.2 Unary and Binary Relations -- 4.3.3 Properties of Unary Relations on A -- 4.3.4 Partial Ordering -- 4.3.5 Equivalence Relations -- 4.4 Functions -- 4.4.1 Definitions -- 4.4.2 Composition -- 4.5 Summary -- Chapter 5: Graphs and Directed Graphs (Digraphs) -- 5.1 Introduction -- 5.2 Terminology -- 5.3 Paths and Cycles -- 5.4 Connectedness -- 5.5 Adjacency and Reachability -- 5.6 Unary Relations and Digraphs -- 5.7 Ordering Relations -- 5.8 Isomorphisms -- 5.9 Trees -- 5.9.1 Spanning Trees -- 5.9.2 Directed Trees -- 5.9.3 Forest -- 5.10 Finding Cycles and Semicycles in a Graph -- 5.11 Revisiting IDEF0 Diagrams -- 5.12 Summary -- Part 2: Design and Integration -- Chapter 6: Requirements and Defining the Design Problem -- 6.1 Introduction -- 6.2 Requirements -- 6.3 Definitions -- 6.4 Stakeholders' Requirements Development: Defining the Design Problem -- 6.5 Requirements Categories -- 6.6 Requirements Partition -- 6.7 Stakeholders' Requirements Document (Stkhldrsrd) -- 6.8 Characteristics of Sound Requirements -- 6.9 Writing Requirements -- 6.10 Operational Concept -- 6.11 External Systems Diagram -- 6.12 Objectives Hierarchy for Performance Requirements -- 6.13 Prototyping, Analyses, and Usability Testing -- 6.14 Defining the Stakeholders' Requirements -- 6.14.1 Input/Output Requirements -- 6.14.2 System-Wide and Technology Requirements -- 6.14.3 Trade-Off Requirements -- 6.14.4 Qualification Requirements.

6.15 Requirements Management -- 6.16 Summary -- Chapter 7: Functional Architecture Development -- 7.1 Introduction -- 7.2 Defining Terminology for a Functional Architecture -- 7.3 Functional Architecture Development -- 7.3.1 Functional Architecture Process Model -- 7.3.2 Decomposition versus Composition -- 7.4 Defining a System'S Functions -- 7.4.1 Approaches for Defining Functions -- 7.4.2 Typical Functional Decompositions by Life Cycle Phase -- 7.4.3 Feedback and Control in Functional Design -- 7.4.4 Evaluation of a Functional Hierarchy -- 7.5 Development of the Functional Decomposition -- 7.6 Finishing the Functional Architecture -- 7.7 Tracing Requirements to Elements of the Functional Architecture -- 7.8 Summary -- Chapter 8: Physical Architecture Development -- 8.1 Introduction -- 8.2 Generic Versus Instantiated Physical Architectures -- 8.3 Overview of Physical Architecture Development -- 8.4 Creativity Techniques -- 8.4.1 Morphological Box -- 8.4.2 Option Creation Techniques -- 8.5 Graphic Representations of the Physical Architecture -- 8.6 Issues in Physical Architecture Development -- 8.6.1 Major



Concepts for Physical Architectures -- 8.6.2 Design Flexibility -- 8.6.3 Design Advantages of Product Platforms -- 8.6.4 Use of Redundancy to Achieve Fault Tolerance -- 8.7 Summary -- Chapter 9: Allocated Architecture Development -- 9.1 Introduction -- 9.2 Overview -- 9.3 Allocate Functions to Components -- 9.3.1 Define the Allocation Problem -- 9.3.2 Approaches for Solving the Allocation Problem -- 9.3.3 Finishing the Allocation Problem -- 9.4 Trace Non-Input/Output Requirements and Derive Requirements -- 9.4.1 Derive Internal Input/Output Requirements -- 9.4.2 Trace System-Wide Requirements and Derive Subsystem-Wide Requirements -- 9.4.3 Trace Trade-Off Requirements and Derive Subsystem Trade-Off Requirements.

9.4.4 Trace Qualification Requirements and Derive Subsystem Qualification Requirements -- 9.5 Define and Analyze Functional Activation and Control Structure -- 9.6 Conduct Performance and Risk Analyses -- 9.7 Document Architectures and Obtain Approval -- 9.8 Document Subsystem Specifications -- 9.9 Summary -- Chapter 10: Interface Design -- 10.1 Introduction -- 10.2 Overview of Interface Development -- 10.3 Interface Architectures -- 10.3.1 Message Passing Architectures -- 10.3.2 Shared Memory Architectures -- 10.3.3 Network Architectures -- 10.4 Standards -- 10.5 Open Systems Interconnection Architecture -- 10.6 Common Object Request Broker Architecture -- 10.7 Interface Design Process -- 10.8 Summary -- Chapter 11: Integration and Qualification -- 11.1 Introduction -- 11.2 Distinctions Among Acceptance, Validation, and Verification Testing -- 11.3 Overview of Integration -- 11.4 Alternate Integration Processes -- 11.5 Some Qualification Terminology -- 11.6 Defining the Qualification System -- 11.7 Qualification Methods -- 11.8 Acceptance Testing -- 11.8.1 Deciding What to Test -- 11.8.2 Usability -- 11.9 Summary -- Chapter 12: A Complete Exercise of the Systems Engineering Process -- 12.1 Introduction -- 12.2 Operational Concept -- 12.3 External Systems Diagram -- 12.4 Fundamental Objectives -- 12.5 Stakeholders' Requirements -- 12.6 Functional Architecture -- 12.7 Physical and Allocated Architectures -- 12.8 Interface Design -- 12.9 Integration and Qualification -- 12.10 Beginning the Subsystem Layer -- Part 3: Supplemental Topics -- Chapter 13: Graphical Modeling Techniques -- 13.1 Introduction -- 13.2 Data Modeling -- 13.2.1 Entity-Relationship Diagrams -- 13.2.2 Higraphs -- 13.3 Process Modeling -- 13.3.1 Data Flow Diagrams -- 13.3.2 N-Squared (N) Charts -- 13.4 Behavior Modeling -- 13.4.1 Behavior Diagrams.

13.4.2 Finite-State Machines and State Transition Diagrams -- 13.4.3 Statecharts -- 13.4.4 Control Flow Diagrams -- 13.4.5 Petri Nets -- 13.5 Summary -- Chapter 14: Decision Analysis for Design Trades -- 14.1 Introduction -- 14.2 Elements of Decision Problems -- 14.3 Axioms of Decision Analysis -- 14.4 Multiattribute Value Analysis -- 14.4.1 Eliciting Value Functions -- 14.4.2 Eliciting Value Weights -- 14.4.2.1 Direct Weight Elicitation Techniques -- 14.4.2.2 Indirect Weight Elicitation Techniques -- 14.5 Uncertainty in Decisions -- 14.5.1 Probability Theory -- 14.5.2 Relevance Diagrams -- 14.5.3 Influence Diagrams and Decision Trees -- 14.5.4 Risk Preference and Expected Utility -- 14.5.4.1 Assessing a Risk Preference Function -- 14.5.4.2 Exponential Risk Preference -- 14.6 Sample Application -- 14.6.1 MPWS Overview -- 14.6.2 Operational Concept for MPWS -- 14.6.3 External Systems Diagram -- 14.6.4 Requirements -- 14.6.4.1 Utility Curves -- 14.6.4.2 Weights -- 14.6.5 Use of Utility Curves and Weights -- 14.6.6 Conclusions -- 14.7 Summary -- Chapter 15: The Science and Analysis of Systems -- 15.1 Introduction -- 15.2 General System Theory -- 15.3 Systems Science -- 15.4 Natural Systems -- 15.5 Cybernetics -- 15.6 Systems Thinking -- 15.7 Quantitative



Characterization of Systems -- 15.7.1 Elevator -- 15.7.2 Soda Machine -- 15.7.3 Aircraft -- 15.8 System Dynamics -- 15.9 Constraint Theory -- 15.10 Fermi Problems and Guesstimation -- 15.11 Summary -- Chapter 16: The Value of Systems Engineering -- 16.1 Introduction -- 16.2 Value Propositions for Systems Engineering -- 16.2.1 Systems Engineering as a Goal-Seeking System -- 16.2.2 Systems Engineering as a Communications Interface -- 16.2.3 Systems Engineering to Avert Showstoppers -- 16.2.4 Systems Engineering to Find and Fix Errors -- 16.2.5 Systems Engineering as Risk Mitigation.

16.2.6 Continuous Improvement.