Requirement templates for distributed 3D graphics

Requirements are the basis upon which software architecture lies. As a consequence they should be expressed as precisely as possible in order to propose the best compromise between stakeholder needs and engineering constraints. While some measurements such as frame rate or latency are a widely known mean of expressing requirements in the 3D community, they often are loosely defined. This leads to software engineering decisions which exclude some of the most promising options. This paper proposes to adapt a non-functional requirements expression template used in general software architecture to the specific case of 3D based systems engineering. It shows that in the process some interesting proposals appear as a straightforward consequence of the better definition of the system to be built.