Good you are interested to pursue the ideas of conceptual systems architecture, such as software, but I would suggest only a scratching of the surface is possible without the use of architectural modelling languages.

Fundamental to any architecture is that it must clearly trace to the needs of all stakeholders.

That can be something of a challenge without the use of conceptual modelling languages, I would say.

A rule of thumb I would recommend is that if there exists a modelling language for something, then it is something worth knowing about, and therefore worth learning the language.

UML is the obvious place to start for software architecture, that is what Systems Engineers and software architects use to define software architecture, and the language most others like SysML, BPMN, DMN, WSDL, SOAML, and many others have later versions derived from that, nowadays, forming a meta-architecture of the languages themselves.

Eclipse has plugins to investigate most of those.