A description of the value of systems engineering, long sought by practitioners in order to justify funding for systems engineering, must be explained in the context of clear systems engineering roles. Twelve roles are described which are frequently assumed to constitute the practice of systems engineering. Some roles fit naturally as life-cycle roles; others fit the Program Management set of roles, while still others are not normally thought of in either group. This presentation suggests a more robust definition of value added that applies to the systems engineering environment, including managing work, defining the problem, and reducing risk. Then, this presentation explores the value of each of the twelve systems engineering roles in terms of this definition of value added and other considerations.

Sarah Sheard, of Software Productivity Consortium Computer Society meetings are free and open to all.

If you would like to contact the Rochester Chapter of the IEEE Computer Society Webmaster, email to Webmaster. (Modified:  17-Feb-2003)