Every Aspiring Developer Should Pay Attention

 The maintenance of applications is a crucial activity in the software industry. The high cost of this process is due to the effort invested on software comprehension since, in most of cases, there is no up-to-date abstraction or documentation to ease this task but the source code. The goal of many commercial and academic tools is to build software architectural views from the code. The main disadvantages of such tools are: i) they are dependent on the language/technology on top of which the application is built; and ii) they offer pre-defined views that are too difficult to adapt to meet particular software comprehension needs. In this paper, we present a Technology-independent approach which is flexible enough to allow developers to define metric-centered architectural views by using annotations. These views display in a single canvas architectural elements whose look and feel maps software metrics.

The Covid-19 pandemic has led many worldwide businesses to reconsider their business strategy, owing to the challenges they faced during the tough time. The biggest challenge remains to manage remote employees and keeping their productivity levels intact. While many employees have the resources, such as laptops and computers to operate remotely without any hassle, it became a costly business for organizations to arrange for infrastructure, software, etc. for each of their employees. The time, money, and resources spent on IT maintenance impact their overall growth our software companies.

The newly embraced remote work situation generated quite a few concerns for the IT departments or organizations.

Tracking the exact location of their employee to know if they're working or not.

Tracking the time they logged in and the total hours they have been active on their desktop.

Managing devices to track employees

Managing IT software remotely and providing software updates and troubleshooting.

Is the private and confidential data being sent over the internet safely?

To cater to all of these concerns, you might want to consider choosing VDI (Virtual Desktop Infrastructure) to streamline management and workflow in your organization.

Scope

In this section, we present an evaluation that focuses on showing the flexibility of our solution. By ‘flexibility’ we mean the ease with which our approach can be modified for use in various source technologies. We chose the technologies of the industrial cases (see Section 3) which are quite different from one another: Oracle Forms is a four-generation programming language, Java and Ruby are Object Oriented Programming languages that range from statically to dynamically typed. We present the results obtained in the three aforementioned industrial cases and finally a discussion is presented.

In the case of Oracle Forms, 3 out of 3 expected views were generated. For the Forms and Tables view of Oracle forms, an additional EgdeDescription for ‘Mas- terDetailRelationship’ was included because this one, as opposed to the other ones, has a source and two targets; this is, a form and the master and detail tables. Our approximation is limited to relations with a unique source and target. A workaround would be to annotate a same class from the metamodel with @Relationship several times, indicating for each annotation a different pair source-target.

In the JEE case, 2 of the 4 expected views were produced. The view about depen- dencies among EJBs had to be done by hand, because in the architecture metamodel there is not a class that represents in a synthetic way the relationships between the EJBs; what is described is that the dependency relationships have an invoking method and one invoked. As a consequence, we had to write a query that navigates dependencies between methods to, from there, derive the calls between EJBs. Simi- larly, the specification for the Microservices and Tables view was made by hand since the instances of ‘Table’ are contained within ‘Architecture’ instead of being inside ‘Microservice’. The proposed decomposition views assume that in the architecture model the container and content elements share a direct composition reference.