Knowledge Check 6 Reviewer

An educational design featuring abstract representations of software architecture layers: Presentation, Application, and Data Layer, overlaid with UML diagrams, colorful and engaging style.

Knowledge Check 6: A Comprehensive Architecture Quiz

Test your understanding of architectural concepts and layers in application development with this engaging quiz! Covering critical areas such as the Presentation, Application, and Data layers, as well as essential UML diagrams, this quiz is perfect for aspiring developers and architects.

Key Features:

  • 51 challenging questions
  • Multiple choice format
  • Immediate feedback on your answers
51 Questions13 MinutesCreated by DesigningTree789
It is a comprehensive framework that describes its form and structure – its components and how they fit together.
Execution Environment
Architecture
Presentation Layer
Application Layer
Which among the following is TRUE about an architecture?
Provides a representation of the system that enables consistent communication: structure, usage, behavior, process and functions.
Highlights early design decisions that define limitations, points of flexibility and provides a basis for later decisions.
Supports non-functional requirements management: performance, capacity, reliability, security, adaptability, etc.
All of the above.
None of the above.
Which of the following are part of the HRS Application 3-Tier Client/Server System?
Presentation Layer
Data Layer
Application Layer
All of the above
None of the above
The client in this layer is a console based UI. The console client will do the following: user input and output, output rendering, basic validations.
Presentation Layer
Data Layer
Application Layer
All of the above
None of the above
This layer contains the Business Logic and Business Model components. The Business Logic and Model components handle the following: business logic, data manipulation.
Presentation Layer
Data Layer
Application Layer
All of the above
None of the above
This layer contains the Data Access component to the ODBMS. It connects to an Oracle 9i ODBMS. The Data Access Objects (DAOs) handle the following: object-to-relational mapping (persistence).
Presentation Layer
Data Layer
Application Layer
All of the above
None of the above
In the Application Layer, these provide the mediation between the Model, which defines the session state and the Presentation Layer.
Action Classes
Model
Value Objects (VOs) & ResultSet
None of the above.
In the Application Layer, this is contained in Business Components, which contain the necessary logic to reflect the state of the Business Objects (the model).
Action Classes
Model
Value Objects (VOs) & ResultSet
None of the above.
In the Application Layer, these provide the necessary mapping of the Business Objects to the physical storage or the database.
Action Classes
Model
Value Objects (VOs) & ResultSet
None of the above.
In the Data Layer, Data Access Objects (DAOs) are the components that utilize the VOs and ResultSets to provide the necessary persistence services to the Business Objects to a Relational Database.
True
False
In the Data Layer, the DataSource objects handle the connection to the database using connection pooling.
True
False
It is the target deployment environment when the application is placed in production (operation).
Execution Environment
Architecture
Server Network
Development Environment
It contains the Application and Authentication Server with Fedora Core 4 Linux and the Database Server. Users will have direct access to the Database Server.
Execution Environment
Architecture
Server Network
Development Environment
It provides the developers in the Developer Network with access to resources on the public Internet and the corporate Sharepoint server (in this case, Accenture’s Sharepoint Servers).
Execution Environment
Architecture
Server Network
Development Environment
In the Development Enviornment, the Server Network will house the Systems Test Application & Authentication Server and the Database server. The CVS server houses the source code for the software and pertinent documentation regarding the software design.
True
False
These are typically used to communicate the high-level functions of the system and the system's scope.
Use case diagrams
Sequence diagrams
Class diagrams
Component diagrams
These are used to show how objects interact with one another and emphasize the order of the messages over time.
Use case diagrams
Sequence diagrams
Class diagrams
Component diagrams
These show the different entities, how they relate to each other, and their attributes and operations.
Use case diagrams
Sequence diagrams
Class diagrams
Component diagrams
These are used to model the relationships between software components in a system, I.e., a physical view of the system.
Use case diagrams
Sequence diagrams
Class diagrams
Component diagrams
In a use case diagram, this illustrates a system functionality.
Actor
Relationships
Use case
In a use case diagram, this represents the people or other systems that interact with the system.
Actor
Relationships
Use case
In a use case diagram, these show the interaction between actors and between use cases via solid lines.
Action
Relationships
Use case
Inheritance between actors and between use cases are shown by a close-headed arrow to the parent.
True
False
<> and <> between use cases are shown via open-headed arrows.
True
False
What is the first step to drawing a sequence diagram?
Indicate the return value by a dotted arrow pointing back to the originating object; label the return value above the dotted line.
Identify the objects needed in the model and draw them across the top.
If an object sends a message to another object, draw a solid arrow pointing to the receiving object; place the name of the message above the line.
What is the second step to drawing a sequence diagram?
Indicate the return value by a dotted arrow pointing back to the originating object; label the return value above the dotted line.
Identify the objects needed in the model and draw them across the top.
If an object sends a message to another object, draw a solid arrow pointing to the receiving object; place the name of the message above the line.
What is the third step to drawing a sequence diagram?
Indicate the return value by a dotted arrow pointing back to the originating object; label the return value above the dotted line.
Identify the objects needed in the model and draw them across the top.
If an object sends a message to another object, draw a solid arrow pointing to the receiving object; place the name of the message above the line.
The Class Definitions document completely defines all aspects of a class that will be used within the system. This is another document that is created during the BUILD phase.
True
False
The class definitions document describes all the details of a particular class, including its name, a description of what it does, what classes it relates to, what it is responsible for doing, its attributes, and what operations it will conduct.
True
False
In class diagrams, this is a rectangle with compartments showing the name, attributes, and operations of the class.
Composition
Inheritance
Association
Class
In class diagrams, this is a line showing interaction and multiplicity between classes.
Composition
Inheritance
Association
Class
In class diagrams, models “is a” and “is like” relationships and shown by a close-headed arrow to the parent.
Composition
Inheritance
Association
Class
In class diagrams, models “is part of” relationships and shown by an arrow with a blocked diamond to the whole.
Composition
Inheritance
Association
Class
In a component diagram, this represents a modular, deployable and replaceable part of a system.
Dependency
Component
Interface
In a component diagram, this is shown as a dashed arrow from the dependent component.
Dependency
Component
Interface
In a component diagram, a component may implement this, and these can be shown as a lollipop joined to the component by a dashed arrow; required instances of this are shown via the socket symbol.
Dependency
Component
Interface
The component definition document is another DESIGN phase document. This document, much like the class definition, outlines the details of each specific component.
True
False
These are recurring solutions to software design problems within a particular context.
Design Document
Design Pattern
Business Logic
Business Model
Which of the following is NOT a benefit of design patterns?
Design patterns enable large-scale reuse of software architectures
Patterns explicitly capture expert knowledge and design tradeoffs, and make this expertise more widely available
Patterns help improve developer communication
All of the above
None of the above
Which of the following is a drawback of design patters?
Patterns do not lead to direct code reuse
Patterns are deceptively simple
Teams may suffer from pattern overload
Patterns are validated by experience and discussion rather than by automated testing
All of the above
None of the above
This kind of pattern is used for modeling requirements.
Analysis
Architectural
Design
Programming
This kind of pattern is used for major components of a software system.
Analysis
Architectural
Design
Programming
This kind of pattern is used for smaller software components.
Analysis
Architectural
Design
Programming
This kind of pattern is used for specific languages.
Analysis
Architectural
Design
Programming
It defines an interface for creating an object, but lets subclasses decide which class to instantiate. This method lets a class defer instantiation to subclasses.
Prototype
Abstract Factory
Singleton
Factory Method
Builder
This provides an interface for creating families of related or dependent objects without specifying their concrete classes.
Prototype
Abstract Factory
Singleton
Factory Method
Builder
This separates the construction of a complex object from its representation so that the same construction process can create different representations.
Prototype
Abstract Factory
Singleton
Factory Method
Builder
Specifies the kind of objects to create using a prototypical instance and creates new objects by copying this prototype.
Prototype
Abstract Factory
Singleton
Factory Method
Builder
Ensures a class has only one instance and provides a global point of access to it.
Prototype
Abstract Factory
Singleton
Factory Method
Builder
In the design pattern catalog, Factory Method, Abstract Factory, Builder, Protoype and Singleton are?
Structural Patterns
Behavioral Patterns
Creational Patterns
(LOL) In 1994, Design Patterns: Elements of Reusable Object-Oriented Software by Erich Gamma, Richard Helm, Ralph Johnson and John Vlissides explained the usefulness of patterns and resulted in the widespread popularity of design patterns. These four authors together are referred to as?
Dabarkads
Tito, Vic & Joey
The Four Horsemen
The Gang of Four
{"name":"Knowledge Check 6 Reviewer", "url":"https://www.quiz-maker.com/QPREVIEW","txt":"Test your understanding of architectural concepts and layers in application development with this engaging quiz! Covering critical areas such as the Presentation, Application, and Data layers, as well as essential UML diagrams, this quiz is perfect for aspiring developers and architects.Key Features:51 challenging questionsMultiple choice formatImmediate feedback on your answers","img":"https:/images/course4.png"}
Powered by: Quiz Maker