Welcome to Enterprise Architect Dotnet Angular Generator Add-in👋

An Add-in for Enteprise Architect that generates a test-driven development-ready .NET Angular CRUD application from a UML model. Its generate itegration tests for api development and storybook cases for angular development, both with autogenetate fake data using autobogus. Inspired by the JHipster and Yellicode bookstore tutorial, it is minimalistic and intended to be modified for your own model-driven generator technology.

🏠 Homepage

Screenshots

Enteprise architect model

Api development environment ( integration tests )

Angular development environment ( Storybook cases )

Motivation

Model-Driven Development (MDD) generators enhance productivity, improve code quality, and foster better collaboration and communication. By leveraging MDD generators, development speed can be accelerated by 2 to 5 times or more compared to traditional software development approaches.

Benefits of Custom Code Generator

• Tailored Solutions: Custom code generators can be tailored specifically to the needs of a particular project or organization, providing greater flexibility and customization options.
• Optimized Code: With custom code generators, developers have more control over the generated code, allowing for optimization of performance, scalability, and maintainability based on project requirements.
• Integration with Existing Systems: Custom code generators can be seamlessly integrated with existing systems, ensuring smoother transitions and better compatibility with legacy infrastructure.

Features

• Generate integration tests.
• Generate Storybook cases.
• Generate seed and mock data using AutoBogus
• Simple and modifiable.
• Fast t4 template development in unit test.

Primitive types

• Integer
• Text
• Decimal
• DateTime
• Bool

Prerequisites

• EA 16 (x64)
• net8.0
• Imported data\Mdg\MdgDotnetWebapi.xml techonolgy file for new project ( The sample already has an imported MDG technology )

Install

• Download installer from last github Actions Artifacts (https://github.com/david-skalka/EA-dotnet-webapi/actions)
• Confirm that Add-in is enabled in EA Ribbon menu Specialize > Manage Add-ins

Example

1. Open data\Sample\SampleModel.qea
2. Open (Specialize > Preference > Dotnet Webapi > Settings) and fill output-dir and project-name
3. Click on the menu (Specialize > Dotnet Webapi) and perform all the steps to generate the entire application
4. Run generated solution in Visual studio

Usage

Define the Domain Model Using a Class Diagram

Identify Main Data Entities: Extract key entities (e.g., users, products, orders) from the business specifications. Understand Attributes and Relationships: Analyze their attributes, relationships, and necessary operations. Add stereotypes to @UMLModel ( ReactCoreGen ), @UmlClass ( Entity ), Attributes ( Field ). Fill in their tags accordingly.

Initialize the Project

Generate the Application: Navigate to the menu (Specialize > Dotnet Webapi) and follow the steps to generate the entire application.

Customization

Create Prototype: Focus on entity relationships and validate them. Specify Action Behavior: Customize the specified actions, then make minor UI changes. Code Merging: Be cautious with full customizations before modifying the UML model.

Continuous Application Updates

Version Control: Utilize version control systems to merge new UML model changes into the customized application.

Test-Driven Development (TDD)

Utilize execution tests to customize API actions instead of using Swagger UI or the React client. For insights into the TDD application, refer to the test coverage report, which provides valuable information about the application's architecture and its test cases. Benefits: TDD facilitates faster development and enhances code quality by making refactoring easier. It ensures that bugs are detected and resolved early, resulting in a more robust and maintainable codebase.

Deploying the Application Using Continuous Deployment (CD)

Test Execution: It is critical to execute tests using a continuous integration server (e.g., GitHub Actions) to ensure all tests in the repository pass. Disable application deployment unless all tests succeed.

Roadmap

• Many to many relation

How to modify for your owen MDG technology

1. Export your xmi diagram to Data directory
2. Execute t4 template by EADotnetWebapiCliTest\TemplatesTest.cs using test runner and check output in console ( faster development time )
3. Integrate your t4 template to EADotnetWebapiCli as command

Author

👤 David Skalka

Show your support

Give a ⭐️ if this project helped you!

---

This README was generated with ❤️ by readme-md-generator