Architectural Naming, a Secret of Agile Thinking

Abstract

The confrontation between the software professionals and legacy system is one of the major issues in the software engineering field. Efforts made in this regard for the formation of the Re-engineering process. The modern software industry is producing quality oriented software rather they go only for producing mere software. The reengineering process is developed for the evolution of legacy software products in the current cutting edge global scenario; besides other this specific area lacks some compact review and inspection precautions. The authors of the research paper focused their efforts on the missing corners of inspection and review the robustness is obtained through incorporating each state of the art method in the process while taking care for the project variation under the harmonious flexibility .Initially the idea is planted in the student's project's soil. The result may be helpful in the desire for efficient review and inspections contribution in software reengineering process for modern technological and corporate needs.Agile processes improve the relations between stakeholders, decrease documents and other non-coding artifacts, so they speed up development greatly. In other words, agility doesn't build stronger bridges, it destroy the need of bridges. I think consistent and comprehensive naming is the secret of better relationships. If the parameters which affect the names are known, a naming convention is better developed. The element position in architecture is one of the most important parameters. For example if the element is a class in UI Layers of Ordering Component, the name of it can be OrderForm. Form is a suffix which is added to all UI classes and Order in an entity which is located in ordering subsystem.Architecture is a pattern which is recurring through the system, when each name is related to architecture, they repeat consistently too. In this poster we present this idea by describing various examples using the method. We show how structural view(class diagrams) and behavioral view(sequence diagrams) can lead naming.14th Asia-Pacific Software Engineering Conference