SET A.

1. Software Architecture is the process of defining the high-level structure and

organization of a software system.
2. PROGRAMMING PHASE It involves in-depth discussions to understand the client's
vision, conduct site analyses, and develop a comprehensive program that guides the
design process.
3. Architecture is commonly defined as the process of planning, designing and
constructing building or structures.
4. Sequence diagrams depict the interactions between objects in a system over time.
5. System An array of components designed to accomplish a particular objective
according to plan.
6. DESIGN DEVELOPMENT PHASE It involves developing construction drawings,
specifications, and other necessary documents for the construction phase.
7. Object-oriented Architecture is designed paradigm based on the division of
responsibilities for an system into individual reusable and self sufficient objects.
8. PERFORMABILITY - the performance of the application is one of the key factors in
software architecture, this characteristic is achieved by how well we design.
9. System Integration Is the combination of inter-related elements to achieve a
common objective (s).
10. Data-centered Architecture refers to a physical and logical layout of the resources
and equipment within a data center facility.
11. Unified Modeling Language (UML) is most commonly used in software
engineering to create diagrams for documenting level 4 architectural elements.
12. Traceability Matrix is a document that establishes and maintains a relationship
between requirements and test cases.
13. SCHEMATIC DESIGN PHASE It involves exploring various design options,
considering site conditions, and developing preliminary drawings and sketches.
14. Use case diagrams provide a visual representation of how users interact with the
system.
15. The spiral model shows that software is developed using an iterative or spiral
approach rather than a linear approach.
16. Data flow diagrams visualize the flow of data through a system. They identify data
sources, data sinks, processes that transform data, and data stores that hold data.
17. Entity relationship diagrams (ERDs) model the relationships between entities in a
database. They show entities, which represent objects or concepts, and their
attributes, which represent properties of the entities.
18. Requirements are fundamental basis of all the system development processes.
19. The prototyping model is used for developing prototypes to clarify user
requirements.
20. Extreme Programming (XP): Developers program in pairs and must write the tests
for their own code.
21. Activity diagrams represent the workflow of a process or system. They show the
activities involved, the transitions between them, and the conditions that trigger
these transitions.
22. A project is a temporary endeavor undertaken to accomplish a unique product or
service
23. State machine diagrams illustrate the possible states that an object can be in and
the transitions between these states.
24. UNDERSTANDABILITY - architecture structure goal should be able to
communication easily and quickly understood by the development teams and
stakeholders at the same time it should meet the business requirements.
 25. Call and Return Architecture is a architectural style that is characterized by
viewing a system as a main entity which can call small sub-entities to perform an
action.

SET B

1. ARCHITECTURE DEVELOPMENT Is the intricate process of transforming a client's

vision into a tangible, functional, and aesthetically pleasing built environment.
2. Sequence diagrams depict the interactions between objects in a system over time.
3. Layered Architecture is a software architecture compromise with multiple layers of
components that are placed into logical groupings based on the type of functionality.
4. BUSINESS ARCHIECTURE the analysis and design of business processes.
5. Activity diagrams represent the workflow of a process or system. They show the
activities involved, the transitions between them, and the conditions that trigger
these transitions.
6. INFORMATION ARCHIECTURE includes logical and physical data assets and data
management resources.
7. UNDERSTANDABILITY architecture structure goal should be able to communication
easily and quickly understood by the development teams and stakeholders at the
same time it should meet the business requirements.
8. SCHEMATIC DESIGN PHASE The creative stage where the architect begins to
translate the program into initial design concepts.
9. TESTABILITY the role of software architecture is to ensure they design every
component can be testable; should clearly show all the interfaces, application
boundaries and integration between components
10. Requirement modeling is the process of translating user needs and business goals
into a clear and comprehensive set of requirements.
11. PROGRAMMING PHASE The foundational stage of architectural development where
the architect and client work together to establish the project's goals, objectives, and
requirements.
12. Call and Return Architecture is a architectural style that is characterized by
viewing a system as a main entity which can call small sub-entities to perform an
action.
13. Traceability Matrix is a document that establishes and maintains a relationship
between requirements and test cases.
14. DESIGN DEVELOPMENT PHASE The final stage where the design is refined and
detailed.
15. The Software Architecture of a program or computing system is the structure of
the system, which compromise the software component.
16. Use case diagrams provide a visual representation of how users interact with the
system.
17. Extreme Programming (XP): Developers program in pairs and must write the tests
for their own code. XP teams include developers, managers, and users.
18. Requirements are statements that identify the essential needs of a system in order
for it to have value and utility.
19. Implementation stage is a start point of project building. Code writing requires
applying various programming tools, languages to match the documented
specification.
 20. Adaptive models: Projects are mission driven and component based, using time-
based cycles to meet target dates.
21. Class diagrams model the structure of a system by representing the classes, their
attributes, and methods.
22. A project life cycle is a collection of project phases.
23. Predictive models: The scope of the project can be clearly articulated and the
schedule and cost can be predicted.
24. System integration is defined in engineering as the process of bringing together
the component sub-systems into one system
25. The spiral model shows that software is developed using an iterative or spiral
approach rather than a linear approach.

Multiple Choice

1. How would you evaluate the effectiveness of a software architecture in meeting user
needs and organizational goals?
A) By assessing the number of components used in the architecture
B) By analyzing user feedback and system performance metrics
C) By comparing it to the architecture of a competitor's system
D) By ensuring it follows the latest programming trends
2. In a scenario where a software system is experiencing frequent downtime, which
architectural characteristic should be prioritized for improvement?
A) Understandability
B) Usability & Learnability
C) Reliability & Availability
D) Secularity
3. If tasked with designing a new software system, which architectural style would you
choose to ensure modularity and reusability of components?
A) Data-Centered Architecture
B) Call and Return Architecture
C) Object-Oriented Architecture
D) Layered Architecture
4. When considering architectural alternatives during the design phase, what is the
primary benefit of doing so?
A) It allows for a more complex system design
B) It reduces the risks associated with construction and implementation
C) It ensures that the latest technologies are used
D) It simplifies the communication among team members
5. In the context of software architecture, how would you analyze the implications of
choosing a data flow architecture over a layered architecture?
A) Data flow architecture is always more secure than layered architecture
B) Layered architecture is easier to implement than data flow architecture
C) Data flow architecture may lead to more complex data management
challenges
D) Layered architecture requires less initial planning than data flow architecture
6. If you were to create a new architectural model for a software system, which of the
following factors would be most critical to consider?
A) The latest programming languages available
B) The historical performance of similar systems
C) The specific needs and behaviors of the target users
D) The number of developers available for the project
7. In evaluating the security of a software architecture, which characteristic is most
essential to ensure user data protection?
A) Understandability
B) Usability & Learnability
C) Secularity
D) Reliability & Availability
8. If a software architecture is designed with a focus on usability and learnability, what
outcome can be expected?
A) Users will require extensive training to use the software
B) Users will find the software intuitive and easy to navigate
C) The software will have a complex interface
D) Users will prefer alternative software solutions
9. When analyzing the effectiveness of a layered architecture, which aspect should be
prioritized?
A) The number of layers implemented
B) The interaction and communication between layers
C) The aesthetic design of each layer
D) The historical success of layered architectures in other projects
10. If tasked with creating a new software architecture for a business process, which type
of architecture would be most appropriate to analyze and design?
A) Information Technology (IT) Architecture
B) Application (Software) Architecture
C) Business Architecture
D) Information Architecture
11. If a company is considering implementing a remote work policy, which of the
following potential outcomes should be prioritized for analysis to ensure employee
productivity?
A) The geographical location of employees
B) The technological tools available for remote work
C) The historical performance of employees in the office
D) The number of hours employees spend online
12. If a software application is experiencing performance issues, which characteristic of
software architecture should be analyzed first to identify potential causes?
A) Interoperability
B) Performability
C) Testability
D) Scalability
13. How can the C4 model's context diagram be utilized to improve stakeholder
understanding of a software system?
A) By detailing the code structure of the application.
B) By providing a high-level overview of the system's purpose and
interactions with external systems.
C) By focusing on the internal components of the system.
D) By illustrating the performance metrics of the application.
14. In a scenario where a legacy system needs to integrate with a new application, which
characteristic of software architecture would be most critical to evaluate?
A) Testability
B) Interoperability
C) Performability
D) Observability
 15. When designing a system that must handle fluctuating loads, which characteristic
should be prioritized to ensure optimal performance?
A) Testability
B) Scalability
C) Observability
D) Interoperability
16. How would you evaluate the effectiveness of using a high-level software architecture
diagram in the early stages of software development?
A) It provides detailed code-level insights that are unnecessary at this stage.
B) It helps stakeholders understand the overall design and relationships
between components.
C) It focuses solely on the deployment environment, which is irrelevant initially.
D) It is only useful for documenting existing systems rather than planning new ones.
17. Consider a scenario where a team is struggling with deployment issues. Which
architectural diagram would be most useful for diagnosing the problem?
A) High-level software architecture diagram.
B) Deployment architecture diagram.
C) Website architecture diagram.
D) Behavioral diagram.

True or False

1. System integration is defined as the process of separating component sub-systems

into individual systems. False
2. A project is defined as a temporary endeavor undertaken to accomplish a
unique product or service. True
3. The course requires students to complete a software project as part of their
assignments. True
4. Opportunities for new information systems projects can arise only from
existing problems within the organization. False
5. The architecture of a system includes elements such as components,
connectors, systems, properties, and styles. True
6. Identifying integration issues upfront is not considered a best practice in
system integration. False
7. New or changed information systems development projects can originate
from directives imposed by management or external influences. True
8. The prototyping model is primarily used for projects with vague user
requirements. False
9. Extreme Programming (XP) requires developers to work in pairs and write
tests for their own code. True
10.Scrum methodology is best suited for projects that do not require strong
leadership. False
11.Requirements are considered the fundamental basis of all system
development processes. True
12.A good requirement should describe how a system should be built rather than
what it needs to achieve. False
13.Daily meetings in the Scrum model are intended to help teams measure their
outcomes. True
14.The prototyping approach is a cost-effective method suitable for small-scale
projects. False
15.Requirements must be documented, accessible, and approved by their owner
to be considered good. True
16.The effectiveness of Extreme Programming (XP) is independent of the project
staffing profile. False
17.A project life cycle consists of a series of phases that can vary by project or
industry. True
18.The analysis phase of the Software Development Life Cycle involves
identifying goals and diagnosing issues related to the current project. True
19.The waterfall model allows for client feedback to be incorporated during the
development process. False
20.The maintenance phase of a project involves systematically testing
functionalities for bugs that were previously identified. False
21.The spiral model is characterized by a linear approach to software
development. False
22.The implementation stage of a project is when the code is written and the
project begins to take shape. True
23.The waterfall model allows for client feedback to be incorporated during the
development process. False