We have editions to suit the scale and purpose of your development.
There is a Professional Edition to support distributed development with multiple teams and an Enterprise Edition to support variation development.
Each edition includes two types of design tools: Architect, which allows customization of design tools, and Designer, which allows design on customized design tools. Architect is intended for use by senior designers and process definers, while Designer is intended for use by design members in the field.
-
Professional Edition
This is a design tool that supports development by multiple teams.
With Subversion integration and the ability to split and merge design files, it supports development by multiple teams across companies and departments.- Learn more about the team development function
-
Enterprise Edition
This design tool manages design information for multiple products and supports variation development.
features product line development for defining variants by feature model and switching between variants for each product.- Click here for more information on the product line development function.
List of features
Here is a list of features by edition for Next Design (latest version).
| Category | Function | Description | Pro | Ent |
|---|---|---|---|---|
| Metamodel definition | Adding and deleting entities | You can add new entities or delete entities. | Fat | Fat |
| Adding and removing elements to and from entities | You can add or remove new fields to an entity. | Fat | Fat | |
| Definition of relationships between entities | It is possible to define relationships between entities (traceability relationships). | Fat | Fat | |
| View definition | Documentation | You can use Word-like document representation. | Fat | Fat |
| Tree grid | It allows you to view design information in a hierarchical manner, in an Excel-like list. | Fat | Fat | |
| ER DIAGRAM | The graphical representation provides a bird's eye view of the relationships between design information. | Fat | Fat | |
| Sequence diagram | The exchange of design information can be represented in chronological order. | Fat | Fat | |
| Use of custom shapes and icons | You can customise the look and feel of your design information using any image. | Fat | Fat | |
| Standard diagram support | UML/SysML | UML/SysML based representations such as requirement diagrams, structure diagrams and behavioural diagrams | Fat | Fat |
| Mind mapping | You will be able to use mind mapping, a way of expressing and organising your thoughts. | Fat | Fat | |
| GSN (Goal Structuring Notation) | GSNS THAT CAN BE USED TO DESCRIBE DEPENDABILITY CASES CAN BE EXPRESSED | Fat | Fat | |
| Flow chart | A flowchart can be used to represent a series of steps in a process. | Fat | Fat | |
| PFD (Process Flow Diagram) | THE PFD IS A GRAPHICAL REPRESENTATION OF THE PROCESS DESIGN. | Fat | Fat | |
| Model editing | Unlimited undo/redo | There is no limit to the number of undo/redo operations you can perform on your results. | Fat | Fat |
| Drag and drop model editing | You can use the mouse to place and move shapes. | Fat | Fat | |
| Editing aids such as quick styles and search and replace | You can edit the model ring and the appearance of your models intuitively and efficiently. | Fat | Fat | |
| Display of traceability between editors | You can view the traceability of design information between the main and sub windows. | Fat | Fat | |
| Bulk editing of models | You can edit the information of the selected models at once. | Fat | Fat | |
| Switch file saving format | You can choose between binary and human readable file formats. | Fat | Fat | |
| Traceability | Traceability tree | Trace relationships across the model can be displayed and listed in a tree view. | Fat | Fat |
| Traceability matrix | A tabular representation of the traces between models, allowing you to check their comprehensiveness. | Fat | Fat | |
| Traceability Report | Traceability can be exported to an Excel file in tabular form. | Fat | Fat | |
| Setting not to be traced | You can enter a reason to exclude a trace relationship if you do not wish to establish one. | Fat | Fat | |
| Document output | Word output | Design information can be documented as a Word file. | Fat | Fat |
| HTML OUTPUT | DESIGN INFORMATION CAN BE DOCUMENTED AS HTML FILES. | Fat | Fat | |
| PDF OUTPUT | DESIGN INFORMATION CAN BE DOCUMENTED AS A PDF FILE. | Fat | Fat | |
| Image output | Design information can be documented as image files. | Fat | Fat | |
| Team development | Multiple file splitting | You can divide the design file into arbitrary units (e.g. by design director). | Fat | Fat |
| Merge split files | Separate design files can be merged. | Fat | Fat | |
| Partial loading of model files | You can only load the model files you specified when opening the project. | – | Fat | |
| Configuration management tool integration | Exclusion control is performed on NextDesign in conjunction with configuration management tools. | Fat | Fat | |
| Model Difference Display | You can view the differences between the project files before and after the changes, and between any revisions. | Fat | Fat | |
| Extensions | Extension development | Extensions can be developed using languages such as C# and JavaScript. | Fat | Fat |
| Running an extension | Extensions can be loaded and run in NextDesign. | Fat | Fat | |
| Distribution by package | Download cloud-delivered extensions and profiles. | Fat | Fat | |
| Product line development | Defining a feature model | The relationship of features between products can be modelled in a tree-like diagram. | – | Fat |
| Registration and derivation of multiple products | You can define a product family and assign features to be used for each product. | – | Fat | |
| Assignment of variants to design data | Drag and drop to associate features with design information. | – | Fat | |
| Export of design data | You can export the design information of your fixed products. | – | Fat |
Architect only