Project: EVS API



1. Key Accomplishments

For each Subproject list all accomplishments with associated GForge Reference

1. Report Writer

▪ [GF# 17713] BDA Process

o Installing RW software in preparation for converting current application to fit BDA file layout.

▪ [GF#17707] Generate Object Model

o Removed the StandardReportService object from the model.

▪ [GF#17708] Generate Entity Relationship (ER) Model

o Increased field length for coding scheme name.

o Regenerate SDK writable API.

o Synchronize User tables in report writer and CSM databases.

▪ [GF#17714] Implement User Interface

o Synchronize User tables in report writer and CSM databases.

o Implemented a message page for informing user of completion of an action.

o Added a new ColumnNumber field to StandardReportColumn.jsp.

o Implemented script for prompting user for confirmation at all deletion actions.

o Started to add UI components for allowing an administrator to maintain report status (DRAFT, APPROVED, etc).

▪ [GF#17716] Implement Criteria Submission

o Refining server side code for adding and deleting criteria data to and from the report writer database through SDK API.

▪ [GF#17715] Implement the Server-side Interface to LexBIG

o Resolved a conflicting application-config-client configuration file issue. Both distributed LexBIG API and SDK writable API for accessing data from LexBIG server and report writer database respectively require a configuration file called application-config-client.java.

o Started to implement a StandardReportSevice.

▪ Wrote up a document on how to setup ncireportwriter for development and testing (draft).

2. NCIT Thesaurus Browser

▪ Started requirements gathering. Initially I’m creating a Confluence requirements document to be later converted to MSWord for storage in gForge.

▪ Installed LexBig locally in preparation for coding.

1. Production Support

For each Subproject list ANY Production support and along with the associated GForge Reference

▪ None

2. Meetings

List ALL Meeting attended in support of all associated Subprojects

▪ 01/06/2009 Report Writer Weekly Status Meeting

▪ 01/09/2009 Report Writer Demo.

3. Planned Activities:

For each Subproject list the activities/tasks (with associated GForge Trackers where appropriate) planned for the upcoming weeks.

▪ [GF#17713] Implement the BDA Process - Update the ant build script to handle the generation of single war file from the integrated system

▪ [GF#17715] Implement the Server-side Interface to LexBIG (Report Generation using LexBIG API)

▪ [GF#17716] Implement Criteria Submission

4. Issues and Recommended Resolutions:

List general issues/concerns/risks associated this project team. Items could cross all subprojects or may specific to an individual subproject. Proposed recommendation should be described when available.

▪ None.

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download