Search results

Jump to navigation Jump to search
Results 1 – 17 of 17
Advanced search

Search in namespaces:

  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  

Page title matches

Page text matches

  • ...lated Disciplines|Parent Article]] | [[Systems Engineering and Electrical Engineering|Next Article >]]</center>
    573 bytes (61 words) - 23:40, 18 November 2023
  • ...es]].) Good systems engineering is a key factor in enabling good software engineering. ...the Guide to the Software Engineering Body of Knowledge (SWEBOK) (Bourque, and Fairley 2014; IEEE Computer Society 2022).
    7 KB (903 words) - 23:46, 18 November 2023
  • ...h in methods, models, tools, metrics and standards, which support software engineering. ...SEBoK there is a [[Representing Systems with Models|discussion of models]] and the following is one of the definitions offered: “an abstraction of a sys
    10 KB (1,297 words) - 23:27, 18 November 2023
  • <div id="outline-tree">{{#tree:root=Outline| **[[Introduction to Systems Engineering]]
    11 KB (1,125 words) - 19:54, 19 November 2023
  • {| class="wikitable" style="float:right; margin-left: 10px; width: 40%;" * [[Introduction to Systems Engineering]]
    12 KB (1,324 words) - 20:41, 19 November 2023
  • ...w case studies, as well as a number of corrections of typographical errors and updates of outdated references throughout the SEBoK. The micro release adds == Content and Feature Updates for v. 1.5.1 ==
    9 KB (1,262 words) - 15:29, 15 January 2016
  • ...mmon way to talk about the concepts underlying the many different types of models (e.g., many modeling techniques enable the understanding of system {{Term|B ...g methods are the most widely recognized, different modeling languages and tools employ other techniques as well.
    9 KB (1,342 words) - 23:57, 18 November 2023
  • ...ering. It is part of the [[Systems Engineering and Quality Attributes | SE and Quality Attributes]] Knowledge Area. ...d integrated into subcomponents, subsystems, and systems – have weaknesses and vulnerabilities enabling exploitation. Weaknesses are flaws, bugs, or error
    22 KB (2,994 words) - 22:38, 18 November 2023
  • ...lementable through technologies (e.g., mechanics, electronics, hydraulics, software, services, procedures, human activity). ...more than one system, in some cases forming the common structure, pattern, and set of requirements for classes or families of similar or related systems.
    32 KB (4,372 words) - 23:40, 18 November 2023
  • ...ct resulting from the activity. The activities of every life cycle process and those of the verification process can work together. For example, the {{Ter ==Definition and Purpose==
    26 KB (3,648 words) - 22:01, 18 November 2023
  • ...tudy, just as V&V would be conducted on other subsystems. That is, the high-level definitions of V&V do not change for systems containing one or more AI ...systems that create challenges in their V&V, illuminates those challenges, and provides some potential solutions while noting open or continuing areas of
    29 KB (3,964 words) - 23:57, 18 November 2023
  • [[File:PPI.png|thumb|250px|right|<center>The "Product Systems Engineering" knowledge area is graciously sponsored by PPI.<center>]] ...provided by suppliers based on opportunities to develop and offer products and services to potential users of the product based on business objectives usu
    32 KB (4,642 words) - 23:27, 18 November 2023
  • ...m|Verification (glossary)|verification}}, the activities are complementary and intended to be performed in conjunction. ==Definition and Purpose==
    28 KB (3,883 words) - 23:33, 18 November 2023
  • ...nizational Strategy]] and reflect the nature of the business, its products and services, various stakeholders, business leadership focus, etc. ...ity]], and individual SE competencies are discussed in the article [[Roles and Competencies]].
    25 KB (3,596 words) - 21:57, 18 November 2023
  • ...to meet SoS objectives and considers the details of the individual systems and their impact the SoS performance or functionality. ...ples and guidelines governing their design evolution over time (IEEE 610.12-1990).
    23 KB (3,243 words) - 21:57, 18 November 2023
  • [[File:PPI.png|thumb|250px|right|<center>The "Product Systems Engineering" knowledge area is graciously sponsored by PPI.<center>]] Product systems engineering has activities that are unique to products. This article discusses many of
    24 KB (3,484 words) - 23:21, 18 November 2023