Hi,

We got through reviewing section 1 of N 226. Thank you for your help. I was
able to begin a first draft with your comments.

I would like to continue reviewing the contents of N 226 and see what we
should include, update or delete.

I am skipping Section 2 Definitions for now. Once we see the terminology
that is being used, I will add the definitions later on.

I would like to begin collecting functional requirements from you. I use
some of the content of section 3.1 N226 as an example which is in the next
mail from me. Please comment on the contents as well as the structure.

If you would like to submit a requirement, please use the same structure,
and post it in a separate thread like this:
(see the my following post for an example.

-- Mary

-------------------------------

FR RB No. 1 (title of mail post)

Functional Requirement RB No. 1

Source: Robert Barta

Criticality: "MUST," "MUST NOT," "REQUIRED," "SHALL," "SHALL NOT,"
"SHOULD," "SHOULD NOT," "RECOMMEND," "MAY," and "OPTIONAL (select one)

Definition: (Give a brief sdescription of the requirement here)

Information flow: (how is the information flowing between parts?)

Process Description: (usage scenario)

Data Constructs: if any (data types, arrays, class fields, etc.)

Data Dictionary: If any (A list of all data items in the function. Should
at least have name and data type -- short explanation, life span acuracy,
which functions or processes the data is used in.)

-------------------------------------