Mendix POC project sharing-system requirements specification

Project Overview

1. Project Introduction

This project is based on Siemens Mendix's POC, including privatized environment deployment, Mendix product feature experience, and business POC verification based on the customer's IT&DT department.

Deployed in the customer's privatized environment, using Mendix Studio Pro 8.5 development tools.

The main contents are:

1. Demo verification based on Mendix
2. Mendix scalability verification
3. POC scenario 1: Marketing system-online order management
4. POC Scenario 2: Supply Chain System-Contract Management
5. POC scenario 3: SUC integration, abnormal parts approval workflow and data warehouse API call

2. User needs

• Target users:

The target users of this project are all internal developers of the company, including back-end (Java, PHP), front-end (React, VUE), and mobile (Android, IOS) developers. The project is based on the Mendix platform for rapid development, using a unified component library and implementation the way.

• Description of Requirement:

At present, the company's internal development methods are characterized by long development cycles, complex technology selection, repeated development of components, and inconsistent component standards, which to a certain extent caused a waste of human and material resources. The Siemens Mendix platform provides a low-code development method, so that business personnel and developers can participate in the construction of products together. In terms of products, they can quickly build web and mobile applications; in terms of components, it provides a general component library APP Store, development Personnel can choose suitable components to quickly reference to the project.

Function description

1. Demo verification based on Mendix

Deployment environment construction

The customer's Mendix POC environment adopts a privatized deployment method, two Linux servers are set up, Server(2) deploys Mendix APP, WEB Server, Server(3) deploys Database, Server(1) and Server(4) are proxy servers and file servers , According to the basic team resources, no additional allocation will be made.

Server unless otherwise specified, use the baseline version provided by the foundation team. For privatized deployment, refer to the Mendix App On-premises Deployment deployment manual.

Deployment content	Features	Description
M2ee tools	Command line tool for managing Mendix installation
JDK	JDK11
Mendix Runtime	Mendix runtime environment	Admin Port：8080 Runtime port：8090
Web server	Install Mendix software
database	Oracle database
Nginx reverse proxy	Mapping Server(2)

Mendix product feature experience

01. Download Mendix Studio Pro IDE, and log in with the company's registered email account;

02, Microflow feature experience;

03. Domain Model feature experience;

04. Team collaboration and function verification of Story and task;

05. Simple page CRUD verification;

06. CRUD association verification for complex pages;

07. Exception handling function verification;

08. CI/CD function verification;

09. Multithreading;

10. Filters, listeners, timers;

11. Transaction processing;

12. Separation of reading and writing of database tables, sub-database and sub-table;

Invoke the REST service

Use Mendix platform to call externally provided REST API.

Provide REST service

Use Mendix platform to provide REST API in REST mode.

 

2. MENDIX Scalability Verification

Mendix Java Extension verification 

1. Use the third-party library Guava, which includes APIs such as collections, caching, and string processing;

2. Verify the function of the guava library

1. Verify that Guava's toolkit implements String non-empty, length verification and other verification:

• Non-empty verification: verify whether the input strings "abcdefg" and "abcd efg" are non-empty.
• Length verification: Verify whether the input string "wang", "wangd", "wangding" is a string of length 5-7.

2. Verify that guava implements the intersection, difference, and union of sets:

• Verify that the intersection, difference, and union of hashset "1,2,3,4,5,6" and "3,4,5,6,7,8,9" are correct.

Mendix Javascript Extension verification

Provide chart services based on Echarts; provide data for graphical display.

 

3. POC scenario 1: Marketing system-online order management

Figure one

         

Figure II

      

Figure three

     

Statement of needs

1. Develop APP applications.

As Figure I, Figure II  , the pages TAB two pages, are "online order", "offline order", the data acquired from the data table tm_poc_order The order_source fields case. Please refer to Figure 1 and Figure 2 for the page layout .

Authorization isolation: People from different distributors can only view the data under their own distributors after entering the APP.

2, top right, click "funnel" ICON, enter Figure III screening page, filter criteria refer to Figure III .

3. Compatibility verification: a) Please provide APP and IPAD two display forms after configuration at one end; b) Perform compatibility verification of multiple operating systems and multiple models based on the customer's existing test machine.

4. Add an "order function", which requires an appointment time. After 4 pm, you can only make an appointment the day after tomorrow, and you can make an appointment for tomorrow before 4 o'clock. Before placing an order, judge whether there is a "completed or canceled" order. If there is a reminder, it is not allowed to place another order.

 

Database table structure

 

4. POC Scenario 2 : Supply Chain System - Contract Management

Requirement description: As it involves customer business secrets, no detailed explanation is given here, please understand.

Picture 1:

Figure II:

Picture three:

Picture four:

1. Tooling contract management page; click a piece of data, as shown in the figure above, the status bar changes with the value of the "task status" field.

2. Double-click on a data into the details page, as Figure II , to enter the contract summary sheet page, click on the different sheet page can switch between tabs, contract summary sheet provided "Add", "Edit", "Delete", "Import" , "Export", "Paging query" function.

3. Click the "Edit" button, and the pop - up box shown in Figure 4 will pop up, providing the editing function for a piece of data.

4, contract quotations sheet page as Figure III shown to provide "import", "paging query" feature.

Database table structure

 

5. POC scenario 3: SUC integration, workflow and data warehouse API call

Authentication

The POC work of the SUC integration module involves customer business secrets. The SUC access part will not be explained in detail, please understand.

Abnormal parts handling workflow

(1) Business logic

1. The initiator selects the part whose part status is abnormal, and clicks to initiate approval. The part information and application content input box are displayed on the initiation approval interface.
2. The business flow goes to the manager's approval, and the manager's approval interface has two buttons, "Agree" and "Return".
3. If the manager's approval is passed, the business flow will be transferred to the senior manager for approval; if the manager's approval is not passed, the business flow will be transferred back to the initiator. The initiator interface sees that the process is returned and returned to the operator, and you can choose "Resubmit for approval".
4. If the senior manager's approval is passed, the approval process ends; if the senior manager's approval is not passed, the business flow is transferred back to the initiator, and the initiator interface sees that the process is returned and returned to the operator, and you can choose "Resubmit for Approval".

(2) Database table structure

Data warehouse API report data display

1. For details of the request and response format, please refer to the attached data warehouse API interface call description: because it involves customer business secrets, we will not explain it in detail here, please understand.

2. Requirements description:

Through manual maintenance, create a new table in the data warehouse test environment: tm_poc_mendix, and maintain the tooling contract master data in the table. Develop a new page through Mendix: Provide a "call data warehouse" button, and display data warehouse data in a table by calling the REST API.

3. Table structure: According to 4. POC Scenario 2: Supply Chain System-Contract Management .

 

Thanks for reading!