FIXM TECHNICAL REVIEW MEETING 11/27/12 TOPICS DISUSSED ...

1


FIXM TECHNICAL REVIEW MEETING

11/27/12


TOPICS DISUSSED

1.

Model / Schema

a.

Will the v1.1 model / schema include v1.0 data?


If so, will
the
v1.0

data dictionary

reflect recent comments?

Yes, and yes…v1.1 model / schema will include v1.0 data. Yes…the v1.0 dat
a
dictionary
will
be updated to reflect recent comments.

Since the new Drupal
capability may not be ready at FIXM.aero for the delivery of v1.1, the v1.0 data
dictionary will reside at test.fixm.aero
and
any necessary
updates
will
be made there
(if needed
) and then a new W
ord doc for v
1.1

would be created for the v
1.1

deliverable.

b.

Are we producing
and second data dictionary
that will be a report of DEs that reflect the
model / schema?

Bruce will produce an HTML version of the schema in graphical form only
. From there,
BAH will bridge the gap to produce a document that maps data elements back to the
FIXM model / schema.

This process will begin with v1.1

(but won’t be seen until v2.0
timeframe)

and move forward, not reflecting v1.0.

Bruce is still investi
gating this.

2.

What are the requirements to transfer Bruce’s JIRA functionality to the Drupal tool that will be
managed by BAH and used on the FIXM website? Do we want to do this?

The FIXM website will continue to track only data dictionary comments and issu
es. However,
for comments and issues against the model and schema, we will add a link to the FIXM
website that directs the
user to the JIRA tool that
has been tailored by MIT
-
LL to track these
types of issues. Bruce is managing this tool.

Current users o
f JIRA tool will be undisturbed.
This will require users
to have two

log
-
ins (i.e. fixm.aero, JIRA tool).

3.

Where will contributors record format information for the data elements that they will be
submitting?

Contributors will
record format information i
n the
Notes

dat
a field in the Data Dictionary. In
other words, the format will not have its own attribute in the data dictionary.

4.

Producing xml schemas from the FIXM UML

Bruce is investigating technology that may allow this. Bruce may present information

on this
during one of the upcoming TIMs. More to come.

5.

Extension Management

Will be discussed at the next TIM

(11/29/12)
.


MEETING ATTENDEES

FIRST

LAST

ORGANIZATION

EMAIL

Rod

Little

BAH

Little_roderick@bah
.com

Cris

Ianculescu

BAH

ianculescu_cristian@bah.com

Jay

Zimmer

BAH

zimmer_john@bah.com

2


Patty

Swenor

BAH

swenor_
patricia@bah.com

Anita

Nicholson

BAH

nicholson_anita@bah.com

Mary

Yee

BAH

Yee.mary@bah.com

Judith

Klein

Lockheed Martin

j
udith.klein@lmco.com

Dee

Llewelyn

Lockheed Martin

dee.llewellyn@lmco.com

Marina

Brabham

Lockheed Martin

marina.brabham@lmco.com

Bruce

Taylor

MIT
-
LL

bruce.taylor@ll.mit.edu

Alex

Proschitsky

MIT
-
LL

alexp@ll.mit.edu



ACTION ITEMS

ITEM

ASSIGNED TO

DESCRIPTION

STATUS

1.

Cris
Ianculescu

During the upcoming TIM (11/29/12), discus
s current thoughts
on how FIXM will manage extensions

CLOSED


Cris
Ianculescu

Incorporate a JIRA link
on

the FIXM website that will
link the
user to Bruce’s JIRA to
allow users to comment
on
model/schema

just as before

OPEN

2.

Bruce Taylor

At one of the

upcoming
TIMs, present possibilities of how
technology will allow the development of schemas directly
from the FIXM model

OPEN

3.

Bruce Taylor

Provide HTML version of FIXM data to BAH to allow for the
development of a FIXM
-
based DD

OPEN



DECISIONS MAD
E

ITEM

TOPIC

DECISION

1.

Contents of v1.1

The contents of v1.1 (DD, model / schema) will include Hazardous
Cargo Data (original v1.1), and updated v1.0 data.

2.

Generating a DD that
reflects the schema

Bruce will produce an HTML version of the schema in
graphical form
only. From there, BAH will bridge the gap to produce a document
that maps data elements back to the FIXM model / schema. This
process will begin with v1.1 (but won’t be seen until v2.0 timeframe)
and move forward, not reflecting v1.0. Bru
ce is still investigating
this.

3.

Tracking
comments/issues
against FIXM

The FIXM website will continue to track only data dictionary
comments and issues. However, for comments and issues against
the model and schema, we will add a link to the FIXM webs
ite that
directs the
user to the JIRA tool that
has been tailored by MIT
-
LL to
track these types of issues. Bruce is managing this tool. Current
users of JIRA tool will be undisturbed. T
his will require users to have
two

log
-
ins (i.e. fixm.aero, JIRA too
l).

4.

Where will contributors
record format
information for the data
elements that they will
be submitting?

Contributors will
record format information in the
Notes

data field in
the Data Dictionary.


3


5.

Extension Management

Will be discussed at next

TIM (11/29/12).