Is my use case UML diagram too complicated?

The user of my app has access to two tools within my app. Each tool is comprised of multiple tables that the user has to fill with information.
The app is more complex but that’s roughly what’s it’s about.
This is the UML Diagram that I have designed based on the app:
enter image description here I am wondering whether the use case diagram should be designed otherwise. Maybe, I should design the use case diagram for each tool independently. That way, it will be less cumbersome.
But, this will mean that each tool represents its own system. And I don’t know if from a UML viewpoint, that is the right thing to do.

Sequence diagram, main scenario of use case “Register Company”

enter image description here

About the Sequence Diagram above, judge the following items:

I.The internal actor is the “Company”, which is responsible for informing the data to perform the business registration.

II.As initial interface, the class “Register Company” is used. To register the companies, it is understood that the objects “Branch of Activity” and “Zip Code” are already registered.

For each object represented, it can be seen that a “lifeline” has begun, and when the object begins to interact, the focus of control is used, which has its messages in a numbered and orderly manner.

IV.After the execution of the operations, the receiving object “Company” sends a return message to the sender interface “Form_Cadastrar Empresa”, represented in the dashed line.

The correct items are:

Sequence Diagram Assistance with external database

I have 5 Java/android classes which are in sequential order. The user inputs data into the text box and clicks next. Two things happen, 1 the data the user inputs is passed to the next activity and it is also inserted into an external database.

The same things happens on each of the 5 activities. I’m struggling to represent this in a sequence diagram form. All the sequence diagram examples I see dont have an external database involved in every class/activity and my diagram only moves forward, most diagrams have methods moving back and forth.

How do I represent a schema diagram of my MongoDB database?

I have a MongoDB database that I want to properly document its schema design. I know that MongoDB is a NoSQL database and is schemaless by nature, but I do enforce a schema through my application and I want to represent it in a better way than a print of a findOne() result.

I see many people using ER or UML, but I don’t feel that’s conceptually right to represent my NoSQL database as a relational DB or, at least, it looks weird.

Example using UML: MongoDB: How to represent a schema diagram in a thesis?

I thought that people would be using different models. I’ve searched and the far that I’ve saw was MongoVUE that offers a nice Tree view to understand the schema, but its not printer-friendly.

Is there something else that I’m missing for the NoSQL world? Or should I rest and stick with traditional UML?

Three variables bifurcation diagram

I’m trying to reproduce a paper. The point is that I have three variables and I will like to do the bifurcation diagram.The paper is this one:”A chaotic model of migraine headache considering the dynamical transitions of this cyclic disease” by Atiyeh Bayani, Sajad Jafari,Boshra Hatef and Julien Clinton.If you want to check it all. I’ll show you the model in wich all the parameters are fixed except (e01) which is going to be my bifurcation parameter.Any idea? enter image description here