Template Navigators and Viewers

The primary purpose of Leap SE's template navigators is to provide a list of available templates, along with sample requirements composed using those templates, and a means of accessing them.

  1. Functional Navigator
  2. Structural Navigator
  3. Object Model Viewer
  4. Data Model Viewer

Contents     Requirements Central     Requirement Builder     Templates     Home


Functional Navigator

From Leap SE's main menu bar, this window is accessed via Compose->Functional Requirements.... It serves as a launching ground for composing functional system requirements. Features (a) a scratch pad for drafting requirements; (b) access to Leap SE's 18 functional templates; (c) provision of three examples for each template; and (d) access to the Requirement Builder.

functional

Contents    Back to Top    Home

Structural Navigator

From Leap SE's main menu bar, this window is accessed via Compose->Structural Requirements.... It serves as a launching ground for composing structural system requirements. Features (a) a scratch pad for drafting requirements; (b) access to Leap SE's 3 structural templates; and (c) provision of three examples for each template.

structural

Contents    Back to Top    Home

Object Model Viewer

From Leap SE's main menu bar, this window is accessed via Inspect-> Java Object Model.... or Inspect->C++ Object Model... The Object Model browser provides a convenient view of your object model in Java or C++ format, respectively. The actual .java and .h files are stored in your <System Name> <Java / C++> Files directory. The classes include enum-type attributes, data member attributes, association (pointer) attributes, composition (reference) attributes, constructors and destructors, accessor methods, and member functions.

objHdrFiles

Contents    Back to Top    Home

Data Model Viewer

From Leap SE's main menu bar, this window is accessed via Inspect->Data Model.... It provides a convenient view of your data model, which is available in your <System Name> SQL directory in the form of a .sql file. The .sql file can be run in an RDBMS, such as MS Access, to produce your domain data model schema and ERD. Entities include a primary key field, data attributes, and foreign key fields for: (a) inheritance, (b) composition, and (c) association relationships.

DataModel

Contents    Back to Top    Home

For product information and sales: sales@leapse.com


Leap SE.
Copyright © 2004, Leap Systems. All rights reserved.
Revised: 03/11/07.