Hierarchical Software Architecture & its Types Presentation

This is Software architecture and design presentation of topics Hierarchical Architecture, Master slave architecture, main sub routine architecture style, their advantages and disadvantages.t describes how hierarchical architectures organize systems into layers with specific responsibilities that interact with adjacent layers. Master-slave architecture involves a central master that coordinates subordinate slaves to perform tasks and report results back. Main-subroutine architecture similarly breaks programs into a main program and reusable subroutines.

1. SOFTWARE DESIGN AND ARCHITECTURE

2. HIERARCHICAL ARCHITECTURE Hierarchical architecture views the whole system as a hierarchy structure, in which the software system is decomposed into logical modules or subsystems at different levels in the hierarchy. Each level of the hierarchy serves a specific purpose and interacts with other levels in a well-defined manner. This approach is crucial for building large-scale, complex systems where clarity, organization, and scalability are paramount. Lower level modules provide services to upper level modules. Lower level modules: provide more specific functionality. For example, the data access layer might consist of classes or modules responsible for interacting with the database, executing queries, and handling data manipulation. Security modules might include functions for authentication, authorization, encryption, and input validation.

3. HIERARCHICAL ARCHITECTURE

4. HIERARCHICAL ARCHITECTURE(CONTD.) Middle level modules: provide domain-dependent functions. These modules contain the core business logic of the application. For instance, in an e-commerce platform, the middle-level modules could encompass functionalities like order processing, inventory management, payment processing, and user management. These modules abstract away the specifics of how data is stored or accessed and focus on implementing the actual business rules and processes. Upper level modules : provide abstract functionality in forms of user interfaces. These modules are responsible for user interaction and interface presentation. In a web application, the upper-level modules include components related to the user interface, such as web pages, forms, navigation menus, and other interactive elements.

5. HIERARCHICAL ARCHITECTURE(CONTD.) In terms of code organization: Lower-level modules may consist of reusable functions or classes that provide basic functionalities needed throughout the application. Middle-level modules encapsulate the core logic of the application, ensuring that business rules are implemented consistently and independently of specific user interfaces or data storage mechanisms. Upper-level modules contain code related to the presentation layer, including HTML, CSS, JavaScript for web applications, or UI components in other types of applications.

6. VIRTUAL MACHINE ARCHITECTURE HIERARCHICAL ARCHITECTURE MAIN-SUB ROUTINE ARCHITECTURE MASTER-SLAVE ARCHITECTURE

7. MAIN –SUB ROUTINE The aim of this style is to reuse the modules and freely develop individual modules or subroutine. In this style, a software system is divided into subroutines by using top-down refinement according to desired functionality of the system. These refinements lead vertically until the decomposed modules is simple enough to have its exclusive independent responsibility. Functionality may be reused and shared by multiple callers in the upper layers. There are two ways by which data is passed as parameters to subroutines, namely − Pass by Value − Subroutines only use the past data, but can’t modify it. Pass by Reference & minu ; Subroutines use as well as change the value of the data referenced by the parameter.

8. MASTER-SLAVE ARCHITECTURE In master-slave architecture, slave provides duplicate services to the master and the master chooses a particular result between slaves by a certain selection strategy. It provides replicated services to the master. Master-slave architecture is suitable for applications where reliability of software is critical issue and can be implemented to minimize semantic errors. This architecture has faster computation and easy scalability. Master-slave architecture has limitations also, it is hard to implement, not all problems can be divided and has portability issue. Slave performs the same functional task by different algorithms and methods or totally different functionality.

9. Functionality and Features The master node in this architecture is responsible for coordinating all tasks, including data processing, resource allocation, scheduling, and communication management. Slave nodes execute the tasks distributed by the master node and communicate the results back to the master. Key features of this architecture include: Centralization of control Parallel processing Improved  data consistency Data replication.

10. BENEFITS The master-slave Architecture in database replication offers several benefits. Firstly, it provides fault tolerance, as even if the master database fails, one of the slave databases can be promoted to become the new master. Secondly, it allows for load balancing, as read requests can be distributed among the slave databases, reducing the load on the master. Lastly, it improves data availability, as client applications can be read from any of

11. Challenges and Limitations Despite its benefits, the Master-Slave architecture has its set of challenges. These include: Scalability issues Potential performance bottlenecks Additionally, the system relies heavily on the master node, making  load balancing  a considerable challenge.

12. Performance Master-Slave architecture effectively bolsters data processing speed by enabling parallel processing. Nevertheless, the performance hinges on the capacity and efficiency of the master node.