Valdez, Kaycee M.

BSIT 3-1

TEST I. ESSAY. Elaborate and briefly discuss the following. (5 points Each)
10/23/23 / 3:pm

1. What is the role of system architecture in the development of complex software systems?
System architecture plays a crucial role in the development of complex software systems
by providing a blueprint for the system's structure and organization. It involves making high-level
design decisions that define how various components of the system will interact, communicate,
and function. The key roles of system architecture include defining the system's components and
their relationships, determining the system's behavior and functionality, managing trade-offs and
constraints, such as performance, scalability, and security, ensuring that the system meets the
requirements of stakeholders, and guiding the development team throughout the project's
lifecycle. A well-defined system architecture also enables easier maintenance, expansion, and
adaptation of the system over time.

2. Explain the concept of modularity in system architecture. How does it benefit software
development?
Modularity, in system architecture involves breaking down a software system into self-
contained modules or components. Each module has interfaces and specific functionalities. This
approach brings benefits to software development. It improves reusability as modules can be
used in parts of the system or other projects. Modularity also simplifies maintenance by isolating
issues or updates to modules making them easier to handle. It supports scalability by allowing
the addition or replacement of modules based on changing requirements. Collaboration among
development teams is streamlined as they can work on modules simultaneously. Furthermore,
testing becomes more manageable, with modules.

3. How does system architecture impact the performance and scalability of a software application?
The impact of system architecture on the performance and scalability of a software
application is significant. Architectural choices can dictate how efficiently workloads are
distributed, affecting both performance and scalability. Key considerations include selecting
appropriate hardware, optimizing algorithms, and designing for horizontal scalability, which
allows the system to grow by adding more instances. Factors such as data storage mechanisms
and caching strategies can also have a profound impact on performance. An architecture that is
well-tailored to the specific needs of the application can result in better performance and
scalability.

4. What are the key considerations when choosing a technology stack for a system architecture?
When choosing a technology stack for system architecture, it's essential to consider
various factors, including the project's requirements, team expertise, available resources, and
the specific problem the system aims to solve. The technology stack encompasses programming
languages, databases, web frameworks, and cloud services, among other components. It's
critical to evaluate how well the chosen technologies align with the architectural goals and the
 long-term vision for the project. For example, if a system requires real-time processing, the
choice of programming language and data storage solutions becomes crucial, and cloud services
may be necessary for scalability and reliability.

5. Can you describe the principles of abstraction and how they are applied in system architecture?
Abstraction in system architecture simplifies complex systems by hiding unnecessary
details and exposing only essential information. It is applied by creating layers or interfaces that
shield higher-level components from the complexities of lower-level components. By doing so,
abstraction simplifies the design, maintenance, and understanding of the system. For instance, a
user interface layer abstracts the underlying data storage and processing, making it easier for
developers to work on the user interface without worrying about the intricacies of data retrieval
and manipulation. Abstraction promotes encapsulation and reduces the dependencies between
components, enhancing the system's flexibility and maintainability.

6. Discuss the importance of robustness in system architecture. How can robustness be achieved?
Robustness in system architecture is of paramount importance as it ensures a system's
ability to continue functioning even in the presence of unexpected or erroneous inputs or
conditions. Achieving robustness involves the implementation of features such as error handling,
redundancy, failover mechanisms, and data validation. Error handling mechanisms can intercept
and gracefully manage exceptions, preventing crashes or data corruption. Redundancy and
failover strategies provide backup systems or components that can take over in case of failure.
Data validation ensures that only valid data is processed, reducing the risk of errors. Achieving
robustness requires a proactive approach to identify potential failure points and mitigate them
during the system's design phase.

7. How does system architecture contribute to the security of a software system?

System architecture is a critical factor in the security of a software system. It involves the
design of security layers, access controls, encryption, and secure data transmission. Security
considerations should be integrated into the architecture from the project's outset, and threat
modeling can help identify potential vulnerabilities and mitigate them effectively. For instance, a
multi-layered architecture can segregate sensitive data from the public-facing components,
reducing the attack surface. Access controls and encryption ensure that only authorized users
can access data, and data transmission between components or over networks is secure.
Security should be an integral part of system architecture to protect against various threats, such
as unauthorized access, data breaches, and malicious attacks.

8. Explain the trade-offs between a monolithic architecture and a microservices architecture.

The choice between a monolithic architecture and a microservices architecture involves
trade-offs. A monolithic architecture entails building a single, tightly integrated application
where all components are interconnected. While it's easier to develop and deploy initially, it
becomes more challenging to maintain and scale as the system grows. In contrast, a
microservices architecture decomposes the system into smaller, loosely coupled services, each
responsible for a specific function. This approach offers more flexibility, scalability, and ease of
maintenance, but it introduces complexity and operational challenges, including service
 discovery, communication, and orchestration. The choice between these architectures should
consider the specific needs, team expertise, and long-term goals of the project.

9. What are some common design patterns used in system architecture, and when should they be
applied?
Common design patterns in system architecture include the Model-View-Controller
(MVC), Layered Architecture, Event-Driven Architecture, and Microservices Architecture, among
others. The choice of design pattern depends on the project's requirements and constraints. For
example, MVC is suitable for web applications, as it separates data, presentation, and user
interaction, simplifying development and maintenance. Layered Architecture divides the system
into tiers (e.g., presentation, business logic, data), promoting modularity and scalability. Event-
Driven Architecture is ideal for systems with asynchronous communication and real-time
updates. Microservices Architecture is well-suited for complex, scalable systems that can be
divided into independent services, but it requires careful management due to its distributed
nature.

10. How does system architecture support high availability and disaster recovery in mission-critical
applications?
System architecture plays a vital role in ensuring high availability and disaster recovery in
mission-critical applications. High availability is achieved by designing architectures with
redundancy, load balancing, and failover mechanisms. For example, having multiple instances of
a component or service and load balancing incoming traffic across them ensures that the system
remains available even if one instance fails. Disaster recovery involves strategies like data
backup, replication, and off-site storage to safeguard against data loss. Geographic distribution,
which includes data centers in different regions, can further enhance availability and recovery
capabilities. Automated recovery processes, such as restoring from backups or transitioning to
redundant systems, are essential components of high availability and disaster recovery planning.