Personal tools

Systems Engineering Activities

Systems Engineering Activities_092023A
[The Scope of Systems Engineering Activities - Wikipedia]

- Overview

"Systems Engineering" is defined as a systematic, multidisciplinary approach to the design, implementation, technical management, operation, and decommissioning of systems. 

A "system" is a combination of multiple elements that work together to produce required capabilities. These elements include all hardware, software, equipment, facilities, personnel, processes, and procedures required for this purpose; that is, everything necessary to produce system-level results. 

Results include system-level qualities, attributes, Characteristics, functionality, behavior, and performance. 

 

The Big Picture Decision Making

The value added by the system as a whole, in addition to the value contributed independently by its parts, is primarily created by the relationships between the parts; that is, how they relate to each other.  

This Is a way of looking at the "big picture" when making technology decisions. It is the achievement of stakeholder functional, physical and operational performance requirements in the intended use environment within the planned life cycle of the system, within cost, schedule and other constraints. It is a method that supports the control of system life cycle costs. In other words, systems engineering is a logical way of thinking. 

Big picture thinking refers to the thinking strategy of focusing on the entire concept or idea rather than each individual detail. People who use big-picture thinking can often see a plan's long-term possibilities and overall potential for success.

 

- Systems Engineering Management

Systems engineering is the art and science of developing operational systems that meet requirements within often opposing constraints. Systems engineering is a comprehensive, integrated discipline in which the contributions of structural engineers, electrical engineers, institutional designers, electrical engineers, human factors engineers and many other disciplines are evaluated and balanced against each other to produce a coherent whole rather than a monolith, dominated by a single disciplinary perspective. 

Systems engineering seeks safe and balanced designs in the face of opposing interests and multiple and sometimes conflicting constraints. Systems engineers should develop the skills to identify and focus their evaluation efforts to optimize the overall design, rather than favoring one system/subsystem at the expense of another, while constantly verifying that the objectives of the operating system are being met. 

The art is knowing when and where to explore. People with these skills are often labeled "systems engineers." They may have other titles - principal systems engineer, technical manager, chief engineer. 

 

- The Tasks of Systems Engineers

The exact roles and responsibilities of a systems engineer may vary depending on the size and complexity of the project and the different stages of its life cycle. For large projects, there may be one or more systems engineers. For small projects, project managers may sometimes implement these practices. But whoever assumes these responsibilities should perform systems engineering functions. Therefore, the actual distribution of roles and responsibilities of a designated systems engineer may also vary. 

The Principal Systems Engineer ensures that systems technically meet defined needs and requirements and follows correct systems engineering methodologies. Systems Engineers oversee project systems engineering activities performed by technical teams and direct, communicate, monitor, and coordinate tasks. 

Systems Engineers review and evaluate the technical aspects of projects to ensure the system/subsystem engineering process is functioning properly and to develop systems from concept to product. The entire technical team is involved in the systems engineering process.

Systems engineers typically lead the development of concepts of operations (ConOps) and final system architecture, define boundaries, define and assign requirements, evaluate design trade-offs, balance technical risks between systems, define and evaluate interfaces, and provide oversight verification and validation activities, among many others. 

Systems engineers typically lead technical planning efforts and are primarily responsible for documenting many technical plans, requirements and specification documents, verification and validation documents, certification packages, and other technical documentation.

 

[More to come ...]

 

 

Document Actions