0% found this document useful (0 votes)
15 views12 pages

Chapter 2

Uploaded by

you66823673
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
15 views12 pages

Chapter 2

Uploaded by

you66823673
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 12

1) ………………the process of defining the architecture, components, interfaces, and other

characteristics of a system or component


a) design
b) sw architecture
c) planning
2) …………………. how software is decomposed and organized into components—and the interfaces
between those components.
a) Decomposition
b) Software architecture
c) Software engineering
3) software design consists of two activities that fit between software requirements analysis and
software construction, these activities are…….. and ………:
a) sw implementation, sw testing
b) sw architectural design, sw detailed design
c) sw quality, sw detailed design
4) sw design fundamentals introduced here form an underlying basis for understanding the ….. of the
software design:
a) role and scope.
b) Concepts and notations.
c) Notations and terminology
5) design can be viewed as a form of ………………
a) data structure
b) problem solving
c) database
6) A number of other notions and concepts are also of interest in understanding design in its general
sense are ………………..
a) goals, constraints, alternatives, representations, and solutions
b) constraints, goals, solutions
c) goals, constraints, solutions
7) (T/F) it isn’t important to understand the major characteristics of software requirements analysis,
software design, software construction, software testing, and software maintenance. (correct: it is
important…)
8) Software design is generally considered a two-step process, what are they?
a) Architectural design , detailed design
b) System design, component design
c) General design, specific design
9) (T/F) The output of these two processes is a set of models and artifacts
10) ………………… is a comprehensive and fundamental law, doctrine, or assumption
a) Design
b) Concept
c) Principle
11) Some of the software principles are…………….
a) abstraction; coupling and cohesion; decomposition and modularization
b) modeling, managing the requirements, testing the req
12) ………………… is a view of an object that focuses on the information relevant to a particular purpose
and ignores the remainder of the information
a) Cohesion
b) Abstraction
c) Coupling
d) Separation
13) In the context of software design, two key abstraction mechanisms are ……….. , ………………:
a) Parameterization, specification
b) Localization, internationalization
c) Coupling, cohesion
14) (T/F) In the context of software design, there are three key abstraction mechanisms?
(correct: two)
15) Abstraction by ……………………leads to three major kinds of abstraction: procedural abstraction, data
abstraction, and control (iteration) abstraction. Abstraction by ………………….. abstracts from the
details of data representations by representing the data as named parameters.
a) Specifications, parameterization
b) Parameterization, specification
c) Localization, parameterization
16) Abstraction by specification leads to three major kinds of abstraction are …………….. ,
………………………… and …………………….
a) procedural abstraction, data abstraction, and control (iteration) abstraction.
b) Specification, procedural, data
17) (T/F) . Abstraction by specification abstracts from the details of data representations by
representing the data as named parameters. Abstraction by parameterization leads to three
major kinds of abstraction: procedural abstraction, data abstraction, and control (iteration)
abstraction.
(correct : ‫) العكس‬
18) ………………… is defined as “a measure of the interdependence among modules in a computer
program
a) Decomposition
b) Cohesion
c) Separation
d) Coupling
19) ………………… is a measure of the strength of association of the elements within a module
a) Decomposition
b) Cohesion
c) Separation
d) Coupling
20) …………………………………….. means that large software is divided into a number of smaller named
components having well-defined interfaces that describe component interactions
a) Encapsulation and information hiding
b) Decomposition and modularization
c) Separation of interface and implementation
21) ……………………………….means grouping and packaging the internal details of an abstraction and
making those details inaccessible to external entities.

a) Encapsulation and information hiding


b) Decomposition and modularization
c) Separation of interface and implementation
22) ……………………………..is defining a component by specifying a public interface (known to the clients)
that is separate from the details of how the component is realized

a) Encapsulation and information hiding


b) Decomposition and modularization
c) Separation of interface and implementation
23) …………………………….. means ensuring that a software component captures all the important
characteristics of an abstraction and nothing more.
a) Encapsulation and information hiding
b) Decomposition and modularization
c) Sufficiency, completeness, and primitiveness
24) (T / F ) Primitiveness means the design should be based on patterns that are difficult to
implement.
(correct: easy to implement)
25) …………………… is area of interest with respect to a software design
a) Principle
b) Concern
c) Design
26) A number of key issues must be dealt with when designing software. Some are ……….. concerns
a) Designing
b) Quality
c) Requirement
27) other issues in software design is “deal with some aspect of software’s ……………….
a) Structure
b) Design
c) Behavior
28) ………………. is which “tend not to be units of software’s functional decomposition, but rather to be
properties that affect the performance or semantics of the components in systemic ways
a) Concerns
b) Aspects
c) Components
29) Some of the key issues in the sw design are: …………….. , …………… and ………………
a) Concurrency, data persistence, and control and handling of events
b) Completeness, consistency, and prototyping
30) ………………… is concerned with decomposing software into processes, tasks, and threads and
dealing with related issues of efficiency, atomicity, synchronization, and scheduling.
a) Data persistence
b) Security
c) Concurrency
31) ……………………. is concerned with how to organize data and control flow as well as how to handle
reactive and temporal events
a) Data persistence
b) Security
c) Concurrency
d) Control and handling of events
32) ………………. is concerned with how to handle long-lived data.
a) Data persistence
b) Security
c) Concurrency
d) Control and handling of events
33) ……………………………… is concerned with how to distribute the software across the hardware ,how
the components communicate
a) Data persistence
b) Security
c) Distribution of components
d) Control and handling of events
34) …………………………………is concerned with how to prevent, tolerate, and process errors and deal
with exceptional conditions.

a) Data persistence
b) Error and Exception Handling and Fault Tolerance
c) Distribution of components
d) Control and handling of events
35) ……………………………… is concerned with how to structure and organize interactions with users as
well as the presentation of information.
a) Data persistence
b) Error and Exception Handling and Fault Tolerance
c) Distribution of components
d) Interaction and Presentation
36) ……………………………. is concerned with how to prevent unauthorized disclosure, creation, change,
deletion, or denial of access to information and other resources.
a) Security
b) Error and Exception Handling and Fault Tolerance
c) Distribution of components
d) Control and handling of events
37) ………………………………….. is “the set of structures needed to reason about the system, which
comprise software elements, relations among them, and properties of both.
a) Software architecture
b) Sw design
c) Error and Exception Handling and Fault Tolerance
d) Distribution of components
38) (T / F ) Some of these concepts can be useful during the architectural design (for example,
architectural styles) as well as during the detailed design (for example, design patterns).
39) A …………………. represents a partial aspect of a software architecture that shows specific
properties of a software system
a) Principle
b) Snapshot
c) View
d) Database
40) What are different views in the sw development level ?
a) Logical view, process view, physical view, development view
b) Design view, logical view, behavioral view, physical view
41) An …………………………… is a specialization of element and relation types, together with a set of
constraints on how they can be used
a) Architectural design
b) Architectural style
c) Design patterns
42) number of major architectural styles are :
a) general structure , creational structure, behavioral structure
b) General structures , Distributed systems , Interactive systems , Adaptable systems , Other
43) An example of general structure in architectural style is:
a) Model-View Controller, Presentation-Abstraction-Control
b) Client server
c) Pipes and Filters
d) microkernel, reflection
44) An example of distributed systems in architectural style is:
a) Model-View Controller, Presentation-Abstraction-Control
b) Client server
c) Pipes and Filters
d) microkernel, reflection
45) An example of interactive systems in architectural style is:
a) Model-View Controller, Presentation-Abstraction-Control
b) Client server
c) Pipes and Filters
d) microkernel, reflection
46) An example of adaptable systems in architectural style is:
a) Model-View Controller, Presentation-Abstraction-Control
b) Client server
c) Pipes and Filters
d) microkernel, reflection
47) ………………………… is a common solution to a common problem in a given context
a) Pattern
b) Architectural design
c) Architectural style
48) Design patterns can be used to describe details at a lower level. These lower level design patterns
include ??
a) Creational patterns, structural patterns and behavioral patterns
b) General structures , Distributed systems , Interactive systems , Adaptable systems , Other
49) (T / F ) It is useless to think of the architectural design process from a decision-making perspective
rather than from an activity perspective. (correct: it is useful…)
50) ( T / F ) One approach to providing for reuse of software designs and components is to design
families of programs, also known as software product lines
51) ( T / F ) In object-oriented (OO) programming, a key related notion is that of a framework
52) …………………………. should ensure that interaction between the human and the machine provides
for effective operation and control of the machine.
a) User interface design
b) Prototyping
c) Reviews
53) ( T / F ) the user interface should be designed to match the skills, experience, and expectations of
its anticipated users.
54) Some of the General User Interface Design Principles are :
a) Learnability, user familiarity and consistency
b) Coupling, cohesion
c) Decomposition and modularization
55) ……………………. Is The software should be easy to learn
a) Learnability
b) User familiarity
c) Recoverability
d) User guidance
56) ………………. Is The interface should use terms and concepts drawn from the experiences
a) Learnability
b) User familiarity
c) Recoverability
d) User guidance
57) …………………….. is The interface should be consistent so that comparable operations are activated
in the same way.
a) Learnability
b) Consistency
c) Recoverability
d) User guidance
58) ………………… is The behavior of software should not surprise users.
a) Learnability
b) Consistency
c) Minimal surprise
d) User guidance
59) …………………….. is The interface should provide mechanisms allowing users to recover from errors.
a) Learnability
b) Recoverability
c) Minimal surprise
d) User guidance
60) ………………………… is The interface should give meaningful feedback when errors occur and provide
context-related help to users.
a) Learnability
b) Recoverability
c) Minimal surprise
d) User guidance
61) ………………………….. is The interface should provide appropriate interaction mechanisms for diverse
types of users and for users with different capabilities
a) Learnability
b) Recoverability
c) Minimal surprise
d) User diversity

62) ( T / F ) User interface design should solve three key issues? (correct: two)
63) ( T / F ) User interface design must integrate user interaction and information presentation.
64) ( T / F ) interface design should not consider a compromise between the most appropriate styles
of interaction and presentation for the software, the background and experience of the software
users, and the available devices. (correct: interface design should …)
65) User interaction styles can be classified into?
a) Question-answer, direct manipulation, menu selection, form fill-in
b) Consistency, recoverability, minimal surprise
c) Minimal surprise
d) User diversity
66) …………………………. to a single question-answer exchange between the user and the software. The
user issues a question to the software, and the software returns the answer to the question.
a) Direct manipulation
b) Menu selection
c) Question-answer
d) Natural language
67) ……………………… Users interact with objects on the computer screen.
a) Direct manipulation
b) Menu selection
c) Question-answer
d) Natural language
68) …………………………… The user selects a command from a menu list of commands.
a) Direct manipulation
b) Menu selection
c) Question-answer
d) Natural language
69) ……………………… The user fills in the fields of a form
a) Direct manipulation
b) Menu selection
c) Form fill-in
d) Natural language
70) ………………………….. The user issues a command and provides related parameters to direct the
software what to do.
a) Direct manipulation
b) Menu selection
c) Command languages
d) Natural language
71) …………………………….. The user issues a command in natural language.
a) Direct manipulation
b) Menu selection
c) Command languages
d) Natural language
72) Information presentation may be …………………. in nature
a) textual or graphical
b) textual
c) graphical
d) none
73) (T / F ) A good design keeps the information presentation separate from the information itself.
74) …………………….. is an effective way to keep information presentation separating from the
information being presented.
a) ASP
b) SAP
c) MVC
d) MVVC
75) Software engineers also consider software ………………… and …………………. in the design of
information presentation.
a) Performance , security
b) Response time, feedback
c) Correctness, availability
76) ……………………… is generally measured from the point at which a user executes a certain control
action until the software responds with a response. An indication of progress is desirable while
the software is preparing the response.
a) Feedback
b) Performance
c) Response time
77) ………………………. can be provided by restating the user’s input while processing is being completed
a) Feedback
b) Performance
c) Response time
d) Abstract visualization
78) ………………………… can be used when large amounts of information are to be presented.
a) Feedback
b) Performance
c) Response time
d) Abstract visualization
79) (T / F ) User interface design is an iterative process;
80) ………………………………are often used to determine the features, organization, and look of the
software user interface.
a) interface prototypes
b) interface design
c) user interface
81) user interface process includes three core activities:
a) user analysis, software prototyping, interface evaluation
b) user analysis, implementation, testing
82) …………………………….. is the process of designing a software application so that it can be adapted to
various languages and regions without major engineering changes.
a) Prototyping
b) Internationalization
c) Localization
d) Both b & c
83) …………………………………..is the process of adapting internationalized software for a specific region
or language by adding locale-specific components and translating the text.
a) Prototyping
b) Internationalization
c) Localization
d) Both b & c
84) ………………………. should consider factors such as symbols, numbers, currency, time, and
measurement units.
a) Prototyping
b) Internationalization
c) Localization
d) Both b & c

85) User interface designers can use ………………………..and ……………………… to set up mappings between
the software and some reference system known to the users in the real world, which can help the
users to more readily learn and use the interface.
a) Metaphors, conceptual models
b) Metaphors, user interface
c) Conceptual models, user interface
d) none
86) (T / F ) software engineers should be careful to not use more than one metaphor for each
concept.
87) (T / F ) not all metaphors are meaningful or are applied in the same way within all cultures
88) quality attributes discernible at runtime like :
a) performance
b) modifiability
c) correctness
89) quality attributes NOT discernible at runtime like :
a) performance
b) modifiability
c) correctness
90) those related to the architecture’s intrinsic qualities:
a) performance
b) modifiability
c) correctness
91) Various tools and techniques can help in analyzing and evaluating software design quality, they
are :
a) Quality attributes, metaphors
b) Sw design reviews, static analysis, simulation and prototyping
92) ……………………….. informal and formalized techniques to determine the quality of design artifacts
a) Static analysis
b) Sw design reviews
c) Simulation and prototyping
93) ……………………………. formal or semiformal static (nonexecutable) analysis that can be used to
evaluate a design
a) Static analysis
b) Sw design reviews
c) Simulation and prototyping
94) ………………………………. dynamic techniques to evaluate a design (for example, performance
simulation or feasibility prototypes
a) Static analysis
b) Sw design reviews
c) Simulation and prototyping
95) …………………can be used to assess or to quantitatively estimate various aspects of a software
design
a) Static analysis
b) Measures
c) Sw design reviews
d) Simulation and prototyping
96) (T / F ) These measures are classified in two broad categories: Function-based (structured) design
measures , Object-oriented design measures.
97) (T / F ) . Some notations are used to describe the structural organization of a design, others to
represent software behavior.
98) ( T / F ) Certain notations are used mostly during architectural design and others mainly during
detailed design, although some notations can be used for both purpose
99) (T / F ) they are categorized into notations for describing the structural (static) view vs. the
behavioral (dynamic) view.
100) …………………………. mostly but not always graphical, describe and represent the structural
aspects of a software design
a) Behavioral ( dynamic ) view
b) Structural (static) view
c) None
101) they are used to describe the major components and how they are interconnected (static
view):
a) Architecture description languages, Class and object diagrams, Component diagrams, Class
responsibility collaborator cards (CRCs):, Deployment diagrams, Entity-relationship diagrams
(ERDs), Interface description languages (IDLs), Structure charts
b) Flowchart
c) Pseudo code
102) …………………………………some graphical and some textual, are used to describe the dynamic
behavior of software systems and components

a) Behavioral ( dynamic ) view


b) Structural (static) view
c) None
103) behavioral descriptions can include a rationale for design decision such as how a design will
meet security requirements.
a) Activity diagrams:, Communication diagrams, Data flow diagrams (DFDs), Decision tables and
diagrams, Flowcharts, Sequence diagrams, State transition and state chart diagrams, Formal
specification languages, Pseudo code and program design languages (PDLs)
b) Component diagram
c) ERD
104) examples of general strategies useful in the design process include:
a) Function-Oriented (Structured) Design
b) Object-Oriented Design
c) divide and-conquer and stepwise refinement strategies, top-down vs. bottom-up strategies
105) ……………………. starts from the data structures a program manipulates rather than from the
function it performs. The software engineer first describes the input and output data structures
and then develops the program’s control structure based on these data structure diagrams.
a) Function-Oriented (Structured) Design
b) Object-Oriented Design
c) Data structure-centered design
106) ………………………….. is an independent unit, having well-defined interfaces and dependencies
that can be composed and deployed independently.
a) Function-Oriented (Structured) Design
b) Object-Oriented Design
c) Data structure-centered design
d) Component-Based Design (CBD)
107) Other interesting approaches also exist in the Software Design Strategies and Methods
a) Function-Oriented (Structured) Design
b) Iterative, Aspect-oriented design, and Service-oriented architecture
c) Data structure-centered design
d) Component-Based Design (CBD)
108) ……………………………….can be used to support the creation of the software design artifacts
during the software development process.
a) Software design tools
b) Software design interface
c) Structural view

You might also like