Editions and features
Edition
We prepare editions according to the scale and purpose of development.
There are Professional Edition (hereinafter Pro.) that supports distributed development in multiple teams and Enterprise Edition (hereinafter Ent.) that supports variation development.
In addition, two editions are available for each edition: Architect, which allows you to customize the design tool by defining a profile, and Designer, which allows you to design and model using the defined profile.
| Scope of use |
Support for distributed development by multiple teams |
Support for development of variations |
Define Profile
Design/Modeling |
Professional Edition/Architect |
Enterprise Edition/Architect |
| Design and Modeling with Predefined Profiles |
Professional Edition/Designer |
Enterprise Edition/Designer |
As one use case, it is assumed that a high-level designer or process definer defines a profile in Architect, and a designer in the field uses the profile in Designer to design and model.
Edition feature comparison
*: Architect only
| Feature |
Description |
Pro. |
Ent. |
| Add/Delete Entity |
You can add or delete new entity. |
✓ |
✓ |
| Add/Delete element to/from entity |
You can add/delete new field to/from entity. |
✓ |
✓ |
| Relationship definition between entities |
A relationship (traceability relationship) between entities can be defined. |
✓ |
✓ |
view definition *
| Feature |
Description |
Pro. |
Ent. |
| Document |
You can express a document like Word. |
✓ |
✓ |
| Tree Grid |
You can view design information hierarchically by creating a list like Excel. |
✓ |
✓ |
| ER Diagram |
You can get a bird's eye view of the relationship between design information using diagrammatic representation. |
✓ |
✓ |
| Tree Diagram |
By partially folding the design information of the tree structure, you can check it by focusing on the area you want to see. |
✓ |
✓ |
| Sequence Diagram |
The exchange of design information can be expressed in time series. |
✓ |
✓ |
| Use custom shapes and icons |
You can customize the look of design information using any image. |
✓ |
✓ |
Standard diagram support
| Feature |
Description |
Pro. |
Ent. |
| UML/SysML |
UML/SysML-based requirements diagram, structure diagram, behavior diagram-like representation |
✓ |
✓ |
| Mind map |
Mind map, which is an expression method to organize thoughts, can be expressed |
✓ |
✓ |
| GSN (Goal Structuring Notation) |
GSN that can be used to describe dependability cases can be expressed |
✓ |
✓ |
| Flow Chart |
A series of flows such as processing procedures can be expressed as a flowchart. |
✓ |
✓ |
| PFD (Process Flow Diagram) |
PFD, which is a process design diagram, can be expressed. |
✓ |
✓ |
model editing
| Feature |
Description |
Pro. |
Ent. |
| Unlimited Undo/Redo |
You can undo/redo your achievements with unlimited number of times. |
✓ |
✓ |
| Model editing by dragging and dropping |
You can place and move shapes by operating the mouse. |
✓ |
✓ |
| Editing support such as quick style and search/replace |
You can intuitively and efficiently edit the appearance of models and models. |
✓ |
✓ |
| Traceability display between editors |
Traceability of design information between main and sub windows can be displayed. |
✓ |
✓ |
| Batch edit model |
You can edit the information of selected models at once. |
✓ |
✓ |
Traceability
| Feature |
Description |
Pro. |
Ent. |
| Traceability Tree |
Trace relationships across models can be displayed in a tree and listed. |
✓ |
✓ |
| Traceablity Matrix |
You can display traces between models in tabular format to check completeness. |
✓ |
✓ |
| Traceability Report |
Traceability can be output to Excel file in tabular format. |
✓ |
✓ |
| Settings for excluding the trace target |
You can enter the reason for excluding the trace when a trace relationship is not established. |
✓ |
✓ |
Document output
| Feature |
Description |
Pro. |
Ent. |
| Word output |
Design information can be output as a Word file as a document. |
✓ |
✓ |
| HTML output |
Design information can be output as a document as an HTML file. |
✓ |
✓ |
| PDF output |
You can output the design information as a PDF file as a document. |
✓ |
✓ |
| Image output |
Design information can be output as a document as an image file. |
✓ |
✓ |
Team Collaboration
| Feature |
Description |
Pro. |
Ent. |
| Multiple file division |
The design file can be divided into arbitrary units (for example, each designer). |
✓ |
✓ |
| Split File Integration |
You can integrate split design files. |
✓ |
✓ |
| Configuration management tool linkage |
Exclusive control is performed on NextDesign by linking with the configuration management tool. |
✓ |
✓ |
| Model difference display |
You can display the difference between the project file before and after the change and any revision. |
✓ |
✓ |
Extension
| Feature |
Description |
Pro. |
Ent. |
| Extension development |
You can develop extensions using languages such as C# and JavaScript. |
✓ |
✓ |
| Execution of extension |
You can execute the extension by installing it in NextDesign. |
✓ |
✓ |
| Packaged distribution |
You can download extensions and profiles delivered in the cloud. |
✓ |
✓ |
Product line development
| Feature |
Description |
Pro. |
Ent. |
| Define Feature Model |
You can model feature relationships between products in a tree-like diagram. |
－ |
✓ |
| Multiple product registration and derivation |
You can define product lines and assign features to use for each product. |
－ |
✓ |
| Variant assignment to design data |
You can associate features with design information by dragging and dropping. |
－ |
✓ |
| Export Design Data |
You can export the design information of the fixed product. |
－ |
✓ |