Systems engineering training and consulting
Portuguese Chinese

Systems Engineering FAQ


Answers by Robert Halligan FIE Aust CPEng IntPE(Aus)

An executive professional engineer, manager and engineering practitioner, Robert is internationally renowned for his role in the practice and improvement of technology-based projects. Since earning his qualifications in communications engineering at the Royal Melbourne Institute of Technology (now RMIT University), Mr. Halligan has gained experience in almost every definable business sector, over a broad spectrum of technologies. He has performed engineering, engineering management and project management roles in private enterprise, including large transnational corporations (Rockwell, Andrew Corporation), and in the intelligence area of the public sector. Mr. Halligan has also served as Director (International) of INCOSE, and for several years was an INCOSE Ambassador. View full biography here.

Q. What is Systems Engineering?

Q. How do Product Lifecycle Management (PLM) and Enterprise Resource Planning relate to one another, and to Systems Engineering Management?

Q. Can you have multiple parent requirements to a single child requirement?

Q. What is the relationship of Cognitive Systems Engineering to Systems Engineering?

Q. Do you have any comments on the book “Managing Complex Technical Projects”?

Q. What is the relationship between a System Requirements Specification, an Operational Concept Description, and a System/Subsystem Design Description?

E. Basis of Justifiable Verification Costs – Example

Q. What are some pointers in managing technical projects for success?

Q. Do you have any advice on the use of ISO/IEC 15288 (IEEE Std 15288-2008), Second Edition 2008-02-01, Systems and software engineering – System Life Cycle Processes?

Q. What is the significance of different types of requirements such as states and modes, functional, performance, external interface, environmental, resource, physical, other qualities and design?

Q. Your System Requirements Specification and Software Requirements Specification templates start off in a “4. Requirements” section with “4.1 Identification of External Interfaces”, and “4.2 Identification of States and Modes”. Why is that?

Q. What are Interface Requirements Specifications, Interface Design Descriptions, Interface Control Documents, and how do they relate?

Q. Would you agree that requirements engineering is a wicked problem as defined in Wikipedia?

Q. How do all these terms relating to requirements figure?

Q. What are some of the important terms relating to problem definition and stakeholder satisfaction?

Q. What are the various types of interface information used in systems and software engineering, and how do these types of information relate to one another?

Q. Do you have any application advice on ECSS-E-ST-10C, 6 March 2009, titled “Space engineering – System engineering general requirements”, from the European Space Agency?

Q. What are the traceability relationships between SSS/SSDD/SRS?

Q. How can quality system breakdown structures be produced?

Q. What is the difference between requirements and specifications?

Q. Do you have any advice on the systems engineering standard ISO/IEC 15288 (IEEE Std 15288-2008) – 2nd Edition “Systems and software engineering – System Life Cycle Processes”?

Q. Why would you want to measure requirements quality?

Q. SCRUM is an iterative and incremental agile software development method for managing software projects and conducting product or application development. What are the pros & cons of SCRUM? Does it really shorten product development?

Q. What is the difference between an Operational Concept Description (OCD) and a Concept of Operations (CONOPS)?

Q. I need to write and verify a requirement for the lifetime of our device. I am unclear about what lifetime means. I have heard words like service life, useful life, design life. I am wondering if you have any advice, or resources that I can refer to, to properly write the lifetime requirement?

Q. Can Measures of Effectiveness (MOEs) be highly coupled in value, and how many should there be?

Q. How do we assess whether our design (problem-solving) processes are already good enough?