Thanks for the link. Based on the definition of systems engineering from the linked pdf, I would say that the system engineering role looks like a combination of the “lead dev” role and project management.

Part of my job is systems engineering, and job is requirements development(RD) and requirements management(REQM).

Bikram, when you say ‘Systems Engineer’, what do you mean? I haven’t worked on any projects that had that specific title. Can you describe some of the responsibilities this person would normally have?

Hill, the ownership is going to be a function of the skills of the people on the project.

The MRD captures the results of strategic analysis of the market. The primary focus of the (inbound) product manager is synthesis and prioritization of market requirements.

The SRS captures the user-perspective of how the software will work. Use Cases, for example, show how people are intended to achieve the requirements spelled out in the MRD. Designing the use case requires us to apply business analysis skills – essentially a process design step. Interaction designers will apply insight into how people would ideally interact with the user interface. Ideally, this document would be created by the interaction designer and (product manager | program manager | business analyst). On smaller teams, I’ve seen this role work with a program manager working in conjunction with inputs from interface designers.

The design document focuses on what Alan Cooper would call ‘program design’. The senior implementation people will design the architecture for the implementation.

When faced with the tough “who own’s it?” question (because there isn’t a person on the team who is an obvious choice), I would always defer to the person “upstream” in the process. The upstream person (product manager, for the spec) will have the strongest handle on the driving “why” of the particular “what”. Mistakes in direction can mess up a project more than mistakes in execution – so I would use that approach when there isn’t a clear owner.

One query, what role do “Systems engineers” play in the whole process?

Long time reader, first time poster here. Just curious as to your opinion on who should own each of the documents in your process above. For example, who owns the Spec? Is it the PM or the Lead Dev?

Thanks,
Hill