Edition
We have prepared editions according to the scale and purpose of development.
There is a Professional Edition (hereafter Pro.) that supports distributed development by multiple teams, and an Enterprise Edition (hereafter Ent.) that supports variation development.
In addition, each edition has two types: Architect, which allows you to define profiles and customize design tools, and Designer, which allows you to design and model using predefined profiles.
| Scope of use | Support distributed development by multiple teams | Support variation development |
|---|
| Define a profile for design and modeling | Professional Edition/Architect | Enterprise Edition/Architect |
| Designing and modeling using predefined profiles | Professional Edition/Designer | Enterprise Edition/Designer |
As one use case, it is assumed that a senior designer or process definer defines a profile in Architect, and the on-site designer uses the profile in Designer to design and model.
Feature Comparison of Editions
| Feature | Description | Pro. | Ent. |
|---|
| Addition/Deletion of Entities | Entities can be added or deleted. | ✓ | ✓ |
| Adding/deleting elements to/from an entity | You can add/remove new fields to/from an entity. | ✓ | ✓ |
| Defining relationships between entities | You can define relationships (traceability relationships) between entities. | ✓ | ✓ |
view definition 1
| Feature | Description | Pro. | Ent. |
|---|
| Document | You can create a document representation like Word. | ✓ | ✓ |
| Tree Grid | You can view the design information hierarchically by creating a list similar to Excel. | ✓ | ✓ |
| ER Diagram | You can get a bird's-eye view of the relationships between design information using diagrams. | ✓ | ✓ |
| Tree Diagram | By partially collapsing the design information in the tree structure, you can narrow down and check the range you want to see. | ✓ | ✓ |
| Sequence Diagram | Exchanges between design information can be represented in chronological order. | ✓ | ✓ |
| Use Custom Shapes and Icons | Customize the look of your design information with any image. | ✓ | ✓ |
Standard diagram support
| Feature | Description | Pro. | Ent. |
|---|
| UML/SysML | You can express requirements diagrams, structure diagrams, and behavior diagrams according to UML/SysML | ✓ | ✓ |
| Mind Map | You can express your mind map, which is an expression method to organize your thoughts | ✓ | ✓ |
| GSN (Goal Structuring Notation) | GSN that can be used to describe dependability cases | ✓ | ✓ |
| Flow Chart | A series of flows, such as processing procedures, can be represented as a flow chart. | ✓ | ✓ |
| PFD (Process Flow Diagram) | PFD, which is a method of process design, can be expressed. | ✓ | ✓ |
Model Editing
| Feature | Description | Pro. | Ent. |
|---|
| Unlimited Undo/Redo | Achievement input operations can be undoed/redoed an unlimited number of times. | ✓ | ✓ |
| Model editing by drag & drop | Shapes can be placed and moved by mouse operation. | ✓ | ✓ |
| Editing support such as quick style and search/replace | Modeling and model appearance can be edited intuitively and efficiently. | ✓ | ✓ |
| Traceability display between editors | Traceability of design information between main and sub windows can be displayed. | ✓ | ✓ |
| Batch Editing of Models | You can batch edit the information of the selected models. | ✓ | ✓ |
Traceability
| Feature | Description | Pro. | Ent. |
|---|
| Traceability Tree | Tracing relationships across models can be displayed as a tree and listed. | ✓ | ✓ |
| Filtering of trace information | You can check the traceability with good visibility by filtering the display target. | ✓ | ✓ |
| Traceablity Matrix | You can view the traceability between models in tabular form and check the completeness. | ✓ | ✓ |
| Traceability Report | Traceability can be output to an Excel file in table format. | ✓ | ✓ |
| Tracing exclusion settings | You can enter the reason for excluding trace relationships when not connecting. | ✓ | ✓ |
Documentation output
| Feature | Description | Pro. | Ent. |
|---|
| Word output | You can output the design information as a document as a Word file. | ✓ | ✓ |
| HTML output | Design information can be output as a document as an HTML file. | ✓ | ✓ |
| PDF output | Design information can be output as a document as a PDF file. | ✓ | ✓ |
| Image output | Design information can be output as a document as an image file. | ✓ | ✓ |
Team Collaboration
| Feature | Description | Pro. | Ent. |
|---|
| Multiple file division | Design files can be divided into arbitrary units (eg, by design department). | ✓ | ✓ |
| Merge Split Files | Split design files can be merged. | ✓ | ✓ |
| Partial loading of model files | When a project is opened, only the specified model file can be loaded instead of all model files under the project. | － | ✓ |
| Linkage with configuration management tools | Links with configuration management tools to perform exclusive control on Next Design. | ✓ | ✓ |
| Model difference display | You can display the project files before and after changes and the differences between arbitrary revisions. | ✓ | ✓ |
Extensions
| Feature | Description | Pro. | Ent. |
|---|
| Developing extensions | Extensions can be developed using languages such as C# and JavaScript. | ✓ | ✓ |
| Extension execution | Extension can be installed and executed in Next Design. | ✓ | ✓ |
| Extension execution via CLI | Extensions can be executed with command line tools. | ✓ | ✓ |
| Package distribution | Download cloud-delivered extensions and profiles. | ✓ | ✓ |
Product line development
| Feature | Description | Pro. | Ent. |
|---|
| Feature Model Definition | Feature relationships between products can be modeled in a tree-like diagram. | － | ✓ |
| Registration and derivation of multiple products | You can define product lines and assign features to be used for each product. | － | ✓ |
| Variant assignment to design data | Features can be associated with design information by drag & drop. | － | ✓ |
| Export of design data | You can export the design information of fixed products. | － | ✓ |
Git integration
| Feature | Description | Pro. | Ent. |
|---|
| Switch file save format | You can select binary format or human readable file format. | ✓ | ✓ |
| Logical Merging of Models2 | Merge models while maintaining logical consistency with our unique merging tool. | ✓ | ✓ |
| Git operation on Next Design2 | Basic Git commands such as commit and push can be operated from Next Design. | ✓ | ✓ |
| Conflict resolution by 3-way merge 2 | Even if a conflict occurs, it can be resolved by 3-way merge on Next Design. | － | ✓ |