Dieses Wiki befindet sich noch im Aufbau. Das Kopieren sowie Weiterverwenden von Inhalten ist nicht erlaubt.
INCO15
Aus GfSE-Wiki
| INCOSE Systems Engineering Handbook: A Guide for System Life Cycle Processes and Activities | |
|---|---|
| Autor(en) | INCOSE |
| Verlag | Wiley, Hoboken, New Jersey |
| Datum | 2015-08-11, 4. Ausgabe |
| Reihe | |
| ISBN | 978-1-118-99941-7 |
| URL | |
Zitatliste
Nachfolgend wird automatisch eine Liste an Zitaten generiert, sofern im Wiki bereits Zitate zu der Quelle vorhanden sind.
Es existieren bereits 71 Zitate aus INCO15:
| Zitattext | Seite-Nr. | Wikiseite |
|---|---|---|
| "Detailed characteristics of the system of interest (SOI) that typically are identified during elicitation of stakeholder requirements, requirements analysis, trade studies, or validation." | 262 | Abgeleitete Anforderungen |
| "Project execution methods can be described on a continuum from 'adaptive' to 'predictive.' Agile methods exist on the 'adaptive' side of this continuum, which is not the same as saying that agile methods are 'unplanned' or 'undisciplined'." | 261 | Agil |
| "A set of cohesive tasks of a process." | 261 | Aktivität |
| "A statement that identifis a system, product, or process characteristic or constraint, which is unambiguous, clear, unique, consistent, stand‐alone (not grouped), and verifible, and is deemed necessary for stakeholder acceptability." | 264 | Anforderung |
| "The manner in which any selected issue is addressed in a particular project. Tailoring may be applied to various aspects of the project, including project documentation, processes and activities performed in each life cycle stage, the time and scope of reviews, analysis, and decision making consistent with all applicable statutory requirements." | 265 | Anpassung |
| "The manner in which any selected issue is addressed in a particular project. Tailoring may be applied to various aspects of the project, including project documentation, processes and activities performed in each life cycle stage, the time and scope of reviews, analysis, and decision making consistent with all applicable statutory requirements." | 265 | Anpassungen |
| "(System) fundamental concepts or properties of a system in its environment embodied in its elements, relationships, and in the principles of its design and evolution (see ISO 42010)." | 261 | Architektur |
| "An individual who, or an organization that, contributes to the functionality of a system and draws on knowledge, skills, and procedures to contribute the function." | 264 | Bediener |
| "Individual who or group that benefis from a system during its utilization." | 266 | Benutzer |
| "Technical and management activities conducted to ensure supportability implications are considered early and throughout the acquisition process to minimize support costs and to provide the user with the resources to sustain the system in the field." | 261 | Beschaffungslogistik |
| "Black box represents an external view of the system (attributes)." | 262 | Black box |
| "Is the output of a subprocess of domain engineering that is reused for producing two or more products in a product line.A domain asset may be a variability model, an architectural design, a software component, a domain model,a requirements statement or specifiation, a plan, a test case, a process description, or any other element useful for producing products and services.
Note: In systems engineering, domain assets may be subsystems or components to be reused in further system designs. Domain assets are considered through their original requirements and technical characteristics. Domain assets include, but are not limited to, use cases, logical principles, environmental behavioral data, and risks or opportunities learned from the previous projects Domain assets are not physical products available off‐the‐shelf and ready for commissioning. Physical products (e.g., mechanical parts, electronic components, harnesses, optic lenses) are stored and managed according to the best practices of their respective disciplines Note: In software engineering, domain assets can include source or object code to be reused during the implementation Note: Domain assets have their own life cycles. ISO/IEC/IEEE 15288 may be used to manage a life cycle.." | 262 | Domänenbestand |
| "Identifis and bounds the functional domains that are important to an envisioned product line and provide suffiient reuse potential to justify the product line creation. domain scoping builds on the defiitions of the product scoping (ISO 26550 2nd Cd)." | 263 | Domänenbestimmung |
| "The physical means or equipment for facilitating the performance of an action, for example, buildings, instruments, and tools." | 263 | Einrichtung |
| "A decision gate is an approval event (often associated with a review meeting). Entry and exit criteria are established for each decision gate; continuation beyond the decision gate is contingent on the agreement of decision makers." | 262 | Entscheidungsschwelle |
| "The boundary conditions, externally or internally imposed, for the SOI within which the organization must remain when executing the processes during the concept and development stages." | 262 | Entwurfseinschränkungen |
| "The stakeholder that acquires or procures a product or service from a supplier." | 261 | Erwerber |
| "Analysis of specifi features of a system that requires special skills to identify requirements and assess their impact on the system life cycle." | 265 | Fachingenieurwesen |
| "The event in which any part of an item does not perform as required by ist specifiation. The failure may occur at a value in excess of the minimum required in the specifiation, that is, past design limits or beyond the margin of safety." | 263 | Fehler |
| "An evaluation to ensure that the product meets baseline functional and performance capabilities (adapted from ISO/IEC/IEEE 15288)." | 263 | Funktionales Konfigurationsaudit |
| ... alle Seiten mit 71 Zitaten anzeigen | ||