Difference between revisions of "Enabling Systems Engineering"
Line 1: | Line 1: | ||
+ | [[File:Concept_map_for_businesses_and_enterprises_topics.png|800px|Concept Map for Businesses and Enterprises Topics]] | ||
+ | |||
SE activities that support an organization's needs and deliver intended value are enabled by many factors such as the organization's culture, SE workforce competencies, and how the organization grows and deploys its workforce armed with those competencies. There are as many different ways to enable SE performance as there are organizations - every organization's approach is, in detail, unique. Nevertheless, there are many common practices, methods, and considerations that organizations use, providing a framework to structure the relevant knowledge. | SE activities that support an organization's needs and deliver intended value are enabled by many factors such as the organization's culture, SE workforce competencies, and how the organization grows and deploys its workforce armed with those competencies. There are as many different ways to enable SE performance as there are organizations - every organization's approach is, in detail, unique. Nevertheless, there are many common practices, methods, and considerations that organizations use, providing a framework to structure the relevant knowledge. | ||
Revision as of 21:52, 13 July 2011
SE activities that support an organization's needs and deliver intended value are enabled by many factors such as the organization's culture, SE workforce competencies, and how the organization grows and deploys its workforce armed with those competencies. There are as many different ways to enable SE performance as there are organizations - every organization's approach is, in detail, unique. Nevertheless, there are many common practices, methods, and considerations that organizations use, providing a framework to structure the relevant knowledge.
Beyond individuals, there are two levels of organizations defined in the SEBoK: team (which includes projects and programs among other types of teams) and business /enterprise (BE). Teams are usually formed for a specific limited duration purpose, such as creating a new system or upgrading an existing service or product. Once the new system has been created and delivered or the existing service or product has been upgraded and fielded, the team responsible for that effort is usually disbanded and the resources associated with that effort go on to new tasks. For example, the U.S. Federal Aviation Administration formed a team in the last decade to create a new enterprise resource planning system for its operations and dispersed the team after the system was fielded. However, there are exceptions; e.g., the Air Force's SE Center of Excellence persists indefinitely. On the other hand, BEs typically have permanence. They usually offer a portfolio of products and services, introducing new ones, retiring old ones, and otherwise taking steps to grow the value of the business or enterprise, however value is defined. Sometimes a single product or service has such value and longevity that it spawns a BE just for its creation, maintenance, and support; e.g., the Eurofighter Typhoon aircraft was developed by a consortium of three companies that formed a holding company specifically for this purpose. That holding company is expected to persist throughout the in-service life of the aircraft, providing support and upgrade services to the operators.
The primary structure of this Part is around BEs, teams, and individuals, with a fourth section at the beginning of the Part that articulates the overall strategy to enable SE:
Knowledge Areas in Part 5
- Systems Engineering Organizational Strategy
- Enabling Businesses and Enterprises to Perform Systems Engineering
- Enabling Teams to Perform Systems Engineering
- Enabling Individuals to Perform Systems Engineering
References
Please make sure all references are listed alphabetically and are formatted according to the Chicago Manual of Style (15th ed). See the BKCASE Reference Guidance for additional information.
Citations
List all references cited in the article. Note: SEBoK 0.5 uses Chicago Manual of Style (15th ed). See the BKCASE Reference Guidance for additional information.
Primary References
All primary references should be listed in alphabetical order. Remember to identify primary references by creating an internal link using the ‘’’reference title only’’’ (title). Please do not include version numbers in the links.
Additional References
All additional references should be listed in alphabetical order.