In this document we present the main issues that we have to face in order to define a Software Product Line (SPL) for Broadcasting Systems. These issues were identified through requirement analysis and refactoring of SEDUITE which are described in two internal deliverables: a) D.2.2.1: Introduces the requirements (functional and non-functional) of a Broadcasting System by using a case study based on large gatherings (e.g., concerts, competitions, parties, etc.). b) D.2.1.1: Explains the definition of SEDUITE as a SPL by identifying the different assets and products that make part of it. In particular, from each deliverable different questions were raised. We use these questions to identify the issues that we need to face and to guide the redaction of this document. We classify the questions according to three main topics: (i) user assistance (cf. Section 2), (ii) building and evolution of the SPL (cf. Section 3) and (iii) kinds of variability (cf. Section 4) The questions from the D.2.2.1 deliverable are identified with I.x and those from D.2.1.1 with Q.x. In both cases, the 'x' represents the number of the question in the deliverable. Additionally, we include the results of two questionnaires intended for consumers of information (i.e., professor and students) from broadcasting system in academic institutions
