The Value of Twelve Systems Engineering Roles

Sheard, Sarah

doi:10.1002/j.2334-5837.1996.tb02100.x

Cited by 29 publications

(11 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Sheard [9] identifies twelve roles (see Table 2) of development from system engineering viewpoint while investigating the relationship between the roles and their importance for creating a value. This work not only suggests that the value is asserted in qualitative terms and it should be quantified in further research but it also claims that it should be observed as a requested improvement within a product by better (i) definition of the requirements, (ii) management strategies, (iii) ways for mitigating risks, (see [8] for details).…”

Section: Roles In Traditional Software Developmentmentioning

confidence: 96%

A Systematic Approach to the Comparison of Roles in the Software Development Processes

Yılmaz

O’Connor

Clarke

2012

Communications in Computer and Information Science

View full text Add to dashboard Cite

Abstract. The vision of building a successful software product requires teams of individuals equipped with a wide range of social and technical skills. Furthermore, by combining these skills with appropriate job roles, we should be able to improve the productivity of a software organization. In order to identify and compare different roles in software development activities, we conduct a systematic comparison of software development models, covering traditional approaches through to agile techniques. To compare the roles in the literature with industrial software landscapes, we use data from a survey conducted on 266 software practitioners to ascertain job roles in two middle size software companies, one of which uses traditional methods and in particular ISO/IEC 12207 for managing their software development activities while other uses a tailored agile methodology. In light of our interviews, we found that based on project specific needs, the roles used in industry vary significantly from the roles defined in literature.

show abstract

Section: Roles In Traditional Software Developmentmentioning

confidence: 96%

A Systematic Approach to the Comparison of Roles in the Software Development Processes

Yılmaz

O’Connor

Clarke

2012

Communications in Computer and Information Science

View full text Add to dashboard Cite

show abstract

“…An assessment as performed for issues, focusing on the specific roles that Systems Engineers play within the design and development of systems, would provide such insight. The SE roles (Sheard, 1996) provided a beneficial classification set for analysis and mapping against the implementation principles. The question was "As a Systems Engineer for a Constituent System within a SoS, does this Implementation Principle have a high impact on this role?"…”

Section: Principles Framework Utilitymentioning

confidence: 99%

Using the SoSE Principles Framework

Pratt

Cook

2017

INCOSE International Symp

View full text Add to dashboard Cite

This paper is concerned with the principles for successful System of Systems Engineering practice and their use. The paper opens with a description of the need for System‐of‐Systems Engineering (SoSE) within the Australian Defense context and the research underway to support its introduction. An overview of previous work by the authors follows describing the three‐layer framework used to hold the SoSE principles (Pratt & Cook, 2017) to provide context. This framework comprises an articulation of the worldview which makes SoSE meaningful, the concepts that drive SoSE methodology design and use (descriptive heuristics), and implementation principles (prescriptive heuristics). The paper discusses the need for substantiation of these principles and the framework, the methods by which this being conducted and some the initial work assessing coverage and applicability. Finally, the paper provides suggestions for how this framework and associated principles can be employed for its stated purpose (utility), with specific regards for different stakeholders and their varied roles and responsibilities.

show abstract

“… SE is an interdisciplinary, glue role (see both the INCOSE definition of SE, and Sheard, 1996). This means that when SE is implemented it cannot simply be setting up a specialist SE department, with everyone else carrying on "unchanged"rather the rest of the organization has to cooperate with and react to the Systems Engineers.…”

Section: Addressing Organizational Maturity To Conduct Systems Enginementioning

confidence: 99%

Selling Systems Engineering by Searching for the Sweet Spot

Beasley

O'Neil²

2016

INCOSE International Symp

View full text Add to dashboard Cite

Systems Engineering has the potential to be a ubiquitous discipline, adding value in a multitude of domains and organizations. However, there are problems in application and take‐up in any area where it is not already explicit. Part of the reason for this is the way INCOSE and others present Systems Engineering. From the outside it appears a rigid, process‐heavy approach with a strange terminology and a significant investment burden – rather than a liberating, thoughtful (applied Systems Thinking) approach to yield clearer problem understanding that leads to more successful outcomes. In this paper, based on case study evidence of the application of Systems Engineering in a number of domains, it is suggested a more flexible approach to Systems Engineering is needed to introduce it. The introduction occurs largely within organizations. The approach requires a balance between the type / variant of Systems Engineering required by the problem situation, and the level / potential of Systems Engineering capability in the organization – targeting the “sweet spot” is seeking to optimize these two elements. The implementation of Systems Engineering should be seen and planned as a journey rather than a “big bang” implementation. A flexible approach to implementing Systems Engineering will produce a far greater probability of successful take‐up and application. INCOSE must recognize this and generate guidance to organizations (beyond what it has produced for individuals) to establish capability in (an appropriate style of) Systems Engineering. If this is done, INCOSE can have the impact it desires, with the appropriate application of Systems Engineering leading to more successful projects, and the generation of solutions to the increasing difficult problems and challenges facing the world.

show abstract

The Value of Twelve Systems Engineering Roles

Cited by 29 publications

References 6 publications

A Systematic Approach to the Comparison of Roles in the Software Development Processes

A Systematic Approach to the Comparison of Roles in the Software Development Processes

Using the SoSE Principles Framework

Selling Systems Engineering by Searching for the Sweet Spot

Contact Info

Product

Resources

About