Sarah A. Sheard
Research Subjects
Sarah A. Sheard has a total of 11 co-authors. Here are the top co-authors by number of shared publications:
Howard Lykins
Software Productivity Consortium, 2214 Rock Hill Road, Herndon, VA 20170
2 shared publicationsJames R. Armstrong
Software Productivity Consortium, 2214 Rock Hill Road, Herndon, VA 20170
2 shared publications- Arthur Pyster
Software Productivity Consortium 2214 Rock Hill Rd Herndon VA 20170
1 shared publication - Assad Moini
Software Productivity Consortium; 2214 Rock Hill Rd Herndon VA
1 shared publication - Jerry Lake
Systems Management international 281 So. Pickett Street #401 Alexandria VA 22304
1 shared publication - Linda Ibrahim
Federal Aviation Administration 800 Independence Ave. SW Washington DC 20591
1 shared publication
Latest Publications
- 1 June 2004
- Published by Wiley in INCOSE International Symposium
- Vol. 14 (1) , 1351-1361
6.6.1 Adapting Systems Engineering for Software‐Intensive Systems
- 1 June 2004
- Published by Wiley in INCOSE International Symposium
- Vol. 14 (1) , 1351-1361
6.6.1 Adapting Systems Engineering for Software‐Intensive Systems
- 1 June 2004
- Published by Wiley in INCOSE International Symposium
- Vol. 14 (1) , 354-364
2.4.3 Evolving Systems Engineering Processes: Moving from “What Systems Engineers Do” to “Engineering Systems“
Companies have documented systems engineering processes for years, in order to describe what the people they call “systems engineers” do to help product development. In an era of integrated processes, however, it becomes apparent that systems engineering is by its nature an integrating process. Therefore, true engineering of systems works better with an integrated set of engineering processes, within which are systems engineering roles. This paper describes why systems engineering processes are evolving in this manner, as well as how to evolve processes that describe what systems engineers do into an integrated set of processes for engineering systems.
- 1 June 2004
- Published by Wiley in INCOSE International Symposium
- Vol. 14 (1) , 354-364
2.4.3 Evolving Systems Engineering Processes: Moving from “What Systems Engineers Do” to “Engineering Systems“
Companies have documented systems engineering processes for years, in order to describe what the people they call “systems engineers” do to help product development. In an era of integrated processes, however, it becomes apparent that systems engineering is by its nature an integrating process. Therefore, true engineering of systems works better with an integrated set of engineering processes, within which are systems engineering roles. This paper describes why systems engineering processes are evolving in this manner, as well as how to evolve processes that describe what systems engineers do into an integrated set of processes for engineering systems.
- 1 June 2004
- Published by Wiley in INCOSE International Symposium
- Vol. 14 (1) , 139-148
1.4.3 Learning Organizational Lessons
- 1 June 2004
- Published by Wiley in INCOSE International Symposium
- Vol. 14 (1) , 139-148
1.4.3 Learning Organizational Lessons
- 1 July 2003
- Published by Wiley in INCOSE International Symposium
- Vol. 13 (1) , 1114-1124
3.7.1 Process Implementation
- 1 July 2003
- Published by Wiley in INCOSE International Symposium
- Vol. 13 (1) , 1114-1124
3.7.1 Process Implementation
- 1 July 2003
- Published by Wiley in INCOSE International Symposium
- Vol. 13 (1) , 832-846
2.6.3 Security Engineering Awareness for Systems Engineers
- 1 July 2003
- Published by Wiley in INCOSE International Symposium
- Vol. 13 (1) , 832-846
2.6.3 Security Engineering Awareness for Systems Engineers
- 1 August 2002
- Published by Wiley in INCOSE International Symposium
- Vol. 12 (1) , 546-553
2.3.5 Systems Engineering Beyond Capability Models
Capability models have been used for more than a decade to improve the ability of organizations to produce software and systems. The models themselves have matured and currently capture much industry wisdom. However, it is important to note that capability models1 do not and cannot include everything that an organization needs to know to do systems engineering well. This paper attempts to show where systems engineering is broader or deeper than is captured in capability models. Organizations that address these areas when implementing capability model‐based process improvement will make their systems engineering capability robust.
- 1 August 2002
- Published by Wiley in INCOSE International Symposium
- Vol. 12 (1) , 546-553
2.3.5 Systems Engineering Beyond Capability Models
Capability models have been used for more than a decade to improve the ability of organizations to produce software and systems. The models themselves have matured and currently capture much industry wisdom. However, it is important to note that capability models1 do not and cannot include everything that an organization needs to know to do systems engineering well. This paper attempts to show where systems engineering is broader or deeper than is captured in capability models. Organizations that address these areas when implementing capability model‐based process improvement will make their systems engineering capability robust.
- 1 July 2001
- Published by Wiley in INCOSE International Symposium
- Vol. 11 (1) , 651-658
5.4.3 What Is Senior Management Commitment?
Almost all change management guidance emphasizes that without senior management commitment, true change is difficult or impossible. Yet little guidance is available that describes in detailed terms what actions senior managers must take to demonstrate such commitment. This paper draws on the author's experiences in change management (primarily in implementing capability models) to discuss what senior management commitment means in practice. Senior managers must understand and then act upon five principles. Senior managers establish a common vision of an improved organization, demonstrate their commitment by actions that are taken “in the heat of battle,” engage other managers, provide resources, and actively address organizational incompetence. Examples are given of actions that demonstrate strong commitment and of actions that convey a different message. Change programs are most likely to succeed when the commitment is strong and clear.
- 1 July 2001
- Published by Wiley in INCOSE International Symposium
- Vol. 11 (1) , 651-658
5.4.3 What Is Senior Management Commitment?
Almost all change management guidance emphasizes that without senior management commitment, true change is difficult or impossible. Yet little guidance is available that describes in detailed terms what actions senior managers must take to demonstrate such commitment. This paper draws on the author's experiences in change management (primarily in implementing capability models) to discuss what senior management commitment means in practice. Senior managers must understand and then act upon five principles. Senior managers establish a common vision of an improved organization, demonstrate their commitment by actions that are taken “in the heat of battle,” engage other managers, provide resources, and actively address organizational incompetence. Examples are given of actions that demonstrate strong commitment and of actions that convey a different message. Change programs are most likely to succeed when the commitment is strong and clear.
- 1 July 2001
- Published by Wiley in INCOSE International Symposium
- Vol. 11 (1) , 324-331
7.2.1 Help! How Do I Make My Organization Comply With Yet Another New Model?
- 1 July 2001
- Published by Wiley in INCOSE International Symposium
- Vol. 11 (1) , 324-331
7.2.1 Help! How Do I Make My Organization Comply With Yet Another New Model?