Exam (elaborations)
INCOSE Systems Engineering ASEP Exam|254 Q’s and A’s
- Course
- Institution
INCOSE Systems Engineering ASEP Exam|254 Q’s and A’s
[Show more]
Content preview
INCOSE Systems Engineering ASEPExam|254 Q’s and A’s
Why can't breaking a complex system down into parts help us understand
them? - - This approach does not help us understand complex systems
because emergent properties disappear when we examine the parts in
isolation.
- ConOps (formal def) - - addresses the leadership's intended way of
operating the organization
- ConOps (simple terms) - - how the system fits into the bigger system of
which it is a part and will be developed, tested, and operate
- OpsCon (formal) - - what the system will do and why (not how)
- OpsCon (simple terms) - - how system works from operators perspective
- what will the final OpsCon have in the business or mission analysis - -
business and stakeholder needs
- function - - to move
- state of execution/operational mode - - moving
- views and viewpoints are sometimes specified in architecture frameworks
as - - Zachman, DoDAF, MoDAF, The Open Group Architecture Framework
(TOGAF)
- viewpoint - - intended to address a particular stakeholder concern
- examples of emergent properties - - inhibition, interference, resonance or
reinforcement of any property
- physical interfaces - - inputs/outputs of functions are carried out by
physical elements
- N2 are formally called - - coupling matricies
- what are N2 diagrams - - define aggregates and the order of integration
- what technical process are N2 diagrams used during - - AD (architectural
definition)
, - what are N2 diagrams also used for - - optimizing the aggregate definition
and the verification of interfaces
- aggregate - - a whole formed by combining several (typically disparate)
elements
- partitioning and allocating - - separate, gather, or decompose logical
entities into partitions and then to make a correspondence between these
partitions and potential sys elements
- nonfunctional reqs and/or architectural characteristics are used as criteria
to - - analyze, assess, and select candidate sys elements and logical
partitions
- example assessment criteria for sys elements and logical partitions - -
similar transformations within the same technology, similar level of
efficiency, exchange of same type of I/O flows (Information, energy
materials), centralized or distributed controls, execution with close frequency
level, dependability conditions, environment resistance level
- certain analyses to get sufficient data that characterize the global or
detailed behavior of the candidate architectures with respect to eh
stakeholder and sys requirements - - performance, efficiency,
maintainability, cost (PEMC)
- design - - process of developing, expressing, documenting, and
communicating the realization of the architecture of the system through a
complete set of design characteristics described in a form suitable for
implementation
- design descriptor - - The set of generic design characteristics and of their
possible values
- holistic design - - considers the system being designed as an
interconnected whole
- system requirements are (pick verified or validated?) - - verified
- stakeholder requirements are (pick verified or validated?) - - validated
- MOEs - - measures of effectiveness
- MOSs - - measures of sustainability
- MOEs and MOSs are the - - operational measures of success
, - RFP - - Request for Proposal
- SOW - - Statement of Work
- techniques for requirements elicitation - - - Interviews
- Focus groups
- The Delphi method
- Soft systems methodology
- Delphi Method - - forecasts developed by asking a panel of experts to
individually and repeatedly respond to a series of questions
- IFWG - - interface working groups
- FFBD - - Functional Flow Block Diagram
- Life Cycle Model - - 1. Concept
2. Development
3. Production
4. Utilization
5. Support
6. Retirement
- life cycle concepts are essentially definitions of the - - functional concepts
and rationale from the stakeholder perspective
- MOPs - - measures of performance
- TPMs - - technical performance measures
- Implementation process - - system elements MEET REQUIREMENTS,
system architecture, and design
- acquisition concept - - way the system will be ACQUIRED (stakeholder
engagement, reqs def, design, production and verification)
- deployment concept - - way the system will be VALIDATED , delivered and
introduced to operations
- support concept - - desired support infrastructures and manpower
considerations for supporting the system after deployment
- retirement concept - - way the system will be removed from operating and
retired
The benefits of buying summaries with Stuvia:
Guaranteed quality through customer reviews
Stuvia customers have reviewed more than 700,000 summaries. This how you know that you are buying the best documents.
Quick and easy check-out
You can quickly pay through credit card or Stuvia-credit for the summaries. There is no membership needed.
Focus on what matters
Your fellow students write the study notes themselves, which is why the documents are always reliable and up-to-date. This ensures you quickly get to the core!
Frequently asked questions
What do I get when I buy this document?
You get a PDF, available immediately after your purchase. The purchased document is accessible anytime, anywhere and indefinitely through your profile.
Satisfaction guarantee: how does it work?
Our satisfaction guarantee ensures that you always find a study document that suits you well. You fill out a form, and our customer service team takes care of the rest.
Who am I buying these notes from?
Stuvia is a marketplace, so you are not buying this document from us, but from seller Nursephil2023. Stuvia facilitates payment to the seller.
Will I be stuck with a subscription?
No, you only buy these notes for $12.49. You're not tied to anything after your purchase.
Can Stuvia be trusted?
4.6 stars on Google & Trustpilot (+1000 reviews)
79373 documents were sold in the last 30 days
Founded in 2010, the go-to place to buy study notes for 14 years now