Tips | ||
---|---|---|
![]() |
||
Branch Manager |
Quick Answer: No
The OSEE Architecture Framework uses a common table structure to store all types of artifacts, attributes and relations. This allows the users to dynamically create and start using new objects without major database modification.
Quick Answer: No
All Artifact Types, Attribute Types and Relation Types (with a few exceptions) are fully customizable. Although OSEE was initially built for capturing all data throughout the lifecycle of a large avionics systems engineering project, it was architected to store any data by simply defining a different data model to use.
In addition, these data models can be dynamically modified. New Artifacts, Attributes and Relations can be specified at anytime (and even by end users if allowed). Modification and deletion of these can be performed with some administrative back-end tools with the understanding that you would need to determine what to do with the removed data.
There is a BLAM called "Purge Artifact Type" that is used to permanently remove all traces of an artifact type from the OSEE database. The BLAM allows the user to select one or more artifact types to purge. If any artifact instances of the doomed artifact type exist, a different artifact type can be specified; these artifacts will be converted to the new type. Otherwise, the BLAM will abort upon discovering an artifact that is of a type to be purged; that is, the BLAM will never delete any artifacts.
Although OSEE does not currently provide the capability to download database artifacts, work offline and then sync up when re-connected, it was certainly a consideration in the design. The most complex part would be resolving conflicts that may occur to artifacts edited in both disconnected OSEE's. Since OSEE already has the capability to run on multiple databases and the capability to export and import artifacts, it would just take some effort to provide the first versions of this feature. This would be a great area for collaboration.
Quick Answer: Yes
Since traceability is usually defined in a way that is specific to it's use and the objects that are being traced, there is currently no "generic" traceability importing in OSEE, however OSEE provides BLAM that would enable traceability to be imported from existing applications, documents, excel spreadsheets. This capability has already been used a number of times to successfully import traceability from legacy documents and systems on projects OSEE has been deployed to.
Quick Answer: Yes
Through OSEE's BLAM tool, users can import from other applications, documents and spreadsheets.
The majority of the work in publishing out of OSEE has been in the format of Microsoft Word© documents. The user can create a Word template that "describes" the format, headers, footers and what data maps into the specified areas in the template. A BLAM is then run where the user can specify the branch and what artifacts are to be published. Upon execution, the documents are created. This method has successfully generated documents in excess of 10,000 pages that were delivered to the customer.
The OSEE architecture also supports other methods of publishing including web and open document formats. Depending on the level of complexity, some work would be done to provide further export capabilities.
Another form of publishing that OSEE was architected for is delivery of OSEE and the database. Although OSEE can publish documents and reports, it was decided early on that the vendors and customers would want and need the same navigation and exportation capabilities that OSEE provides. Instead of delivering generated documents, one of the projects that OSEE is deployed on delivers a copy of OSEE with a sanitized database (confidential data removed). This has been very successful from both the program and customer's point of view.
OSEE was architected to be database independent and should run on any SQL-99 compliant DB that has a JDBC driver. It is currently runs on Oracle 10g and 11g and PostgreSQL 8.2. In the past, OSEE has also been run on Derby and MySQL. The current release of OSEE would need to be tested for compatibility with Derby, MySQL, or any other database. If desired, the OSEE Team could work with the user/developers to help perform this task.
Yes, OSEE is compatible. When storing word content in XML format make sure to use Word 2003 XML Document (*.xml) format.
![]() |
||
Branch Manager |