The following sections provide an overview of Leap SE and its main window, Requirements Central.
Contents Requirement Builder Template Navigators Templates Home
This is the main window of Leap SE. It is used for querying your requirements database and as an access point to other features.
From Leap SE's main menu bar, this dialog is accessed via View->Entities... System Entities are those entities entered in the "what entity?" fields of templates and the Requirement Builder. It is important to ensure that an entity is not being referenced by different names in a system specification. For instance, consider an airplane. It may be called a "plane" in one requirement, an "airplane" in another, and an "aircraft" in yet a third. Leap SE exposes this inconsistency and enables the user to correct it. If the inconsistency is not corrected, separate header files will be generated for each entity, which is not desired. Object Model Entities are the names of the actual class header files produced by Leap SE, where underscores represent inheritance.
From Leap SE's main menu bar, this dialog is accessed via View->Attributes... Those entities derived from the System Entities (or "domain" entities) appear to the left as Object Model Entities that comprise the logical object model of the system. Selecting an entity and choosing See Attributes >> yields a listing of its data members and relationships. Associations are modeled as pointers to objects used by the entity, while composition relationships are modeled as references to objects that comprise the entity.
From Leap SE's main menu bar, this dialog is accessed via View->Methods... Those entities derived from the System Entities (or "domain" entities) appear to the left as Object Model Entities that comprise the logical object model of the system. Selecting an entity and choosing See Methods >> yields a listing of its member functions. These member functions, or methods, are directly derived from verbs that appear in system requirements that reference the original System Entity from which the Object Model Entity is derived, in most cases. Those methods that are not directly linked to a system requirement verb are extrapolated from Leap SE's Deterministic Phraseology.
From Leap SE's main menu bar, this dialog is accessed via Generate->Object Model.... Use this dialog to generate the system object model in the form of .java or .h (C++ header) files. The Verbose check box is checked by default. When checked, Leap SE produces a comprehensive set of class header files with constructors, set( ) and get( ) methods, support for enumerated types, and a destructor as needed. When not checked, Leap SE produces a simple set of header files. If functional or structural requirements have been added or deleted from the database repository, use this dialog to bring the object model up to date. Note: If requirements have been deleted, be sure to perform Generate->Object Model Database... before generating your files.
From Leap SE's main menu bar, this dialog is accessed via Generate->Data Model....Use this dialog to generate the system data model in the form of an SQL (.sql) file. If functional or structural requirements have been added or deleted from the database repository, use this dialog to bring the data model up to date. Note: If requirements have been deleted, be sure to perform Generate->Object Model Database... first.
From Leap SE's main menu bar, this dialog is accessed via Generate->Object Model Database.... Use this function when one or more functional or structural requirements have been deleted. This function regenerates the database tables from which your object and data models are created, ensuring that deleted requirements are no longer considered in your Header File and SQL output.
From Leap SE's main menu bar, this dialog is accessed via Compose->Technical Requirements.... It serves as an editor for composing technical system requirements. See Template Navigators for composing functional and structural system requirements.
For product information and sales: sales@leapse.com