ERICSSON ///
Internal Information
Minutes of Meeting
Uppgjord - Prepared
EPL/X/AX Anders Svensson 859-3116
Datum - Date
1998-04-27
Rev
A
Dokumentnr - Document no
5/0064-4/FCP 101 0211/1 Uen
Godkänd - Approved
EPL/X/AX (A. Svensson)
Kontr - Checked
EPAOES

Tillhör/referens - File/reference
req_ws
                                           DELTA at LMEL:
                                           V52ML: MANAGEMENT: M_MIN

Requirement Handling Brainstorm, V5.2ML/EPL

Meeting data

Time         Friday 1998-04-24, 9:30-11:30
Location     'Rottweilern' at EPL in Umeå

Participants from the V5.2 ML/EPL subproject:
Anna Jernberger, Edvard Drake (Technical Coordinators)
Anders Jansson, Pär Rudälv, Nicklas Hilmersson, Björn Edlund (Designers)
Anders Svensson (Quality Engineer, Brainstorm Leader)

Participants from V5.2 ML Project Management:
Hellis Mohlin (FT Leader)
Marie Dahlberg (Quality Coordinator)

Participants from EPL/X/A Line Organisation:
Lars Månsson, Clas Högvall (Managers)
Richard Lundström (Operational Development)
Dennis Bergman (R&I Champion)

1   Introduction

Anders welcomed all and noted very pleased that the participants almost formed a 'dream team' for this particular brainstorm. Anders also explained the purpose with and background for this brainstrom:

1.1   Purpose of the brainstorm

To decide the ambition level of the reqiurement handling/tracing in the Execution phase of the V5.2 ML/EPL subproject, and how to implement this ambition in the product and project documents that EPL/X/A is responsible for.

1.2   Background

Anders tried to illustrate the requirement tracing paths and document dependencies on the wyteboard, by using a graph from the EUS Guidelines [REQALL] including a proposed process for AXE 106 requirement allocation.

2   Brainstorm Decisions

During the stimulating brainstorm we managed to decide the ambition level of the reqiurement tracing for the documents below:

(1) As these ambition levels are stated very late in the project, the formal decisions may be necessary to take within the V5.2ML CCB.

2.1   Short-term FS ambition

Anna Jernberger shall prepare the FS for V5.2 ML at a general detail level [AP-1].

2.2   Long-term FS ambition

The FS for V5.2 ML shall later be updated in deeper detail level outside the project [AP-3]. The FS shall reference the EPL V5.2 Requirement [EPLV52], that needs a polish [AP-2].

(2) It will take a big effort to describe the sequence of V5 messages in detail, and the project has no resources for that. (A rough cost etimate mentioned was that the 'Blocking/Deblocking' part only would require 80-160 manh.)

2.3   FF ambition

The FFs shall reference the RS tags according to [TAGDOC] (the same way the IPs do).

(3) A FF may refine some requirements to a more detailed level than in the corresponding IP.

2.4   FD ambition

The FDs shall reference sources (e.g. IP/FFs) according to [TAGDOC] and common sense.

Tagging of statements is not required in FD Flow Charts, but may be used in FD text parts with common sense.

Tracing requirements in the FDs is beyond the ambition level of this project.

3   Action Point List

Action points, Req. Handl. Brainstorm, V5.2 ML/EPL
AP # Responsible Ready Action
AP-1 EPLANNA 980501? Prepare [FS-V52] at a general detail level.
AP-2 EPLRLM 980501? Shape up [EPLV52].
AP-3 EPLLMN 981231? Find a project external resources to update [FS-V52] with detailed descriptions of the sequences of V5 messages.

4   References

EPLV52
'EPL V5.2 Requirements'
EPL/X/A-97:085 Uen, Rev A
FS-V52
'V5.2 Multi Link Interface'
1/155 17-CRT 211 11 Uen
REQALL
'Guidelines for Requirement Allocation'
EUS/XT/BE-97:168
http://www.exu.ericsson.se/EUS/XT/E/ttm/TTM12/RHpage/reqalloc.htm
TAGDOC
'Polaris/EPL Tagging and Referencing Methods'
EPL/POLARIS-002 Uen