Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd Logo
Upload

Welcome to Scribd!

  • 297 views

    SAD Mcqs

    Uploaded by

    Genghis Khan 69
    1. The key points made in the document are: 2. Every software system has an architecture and it provides a common language for communication among stakeholders. 3. Decisions made at all levels of the software development life cycle can affect system quality. 4. When an architecture is divided, changes can occur locally, non-locally, or architecturally. 5. Changing a single component in an architecture results in a local change.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    SAD Mcqs

    Uploaded by

    Genghis Khan 69
    297 views3 pages
    1. The key points made in the document are: 2. Every software system has an architecture and it provides a common language for communication among stakeholders. 3. Decisions made at all levels of the software development life cycle can affect system quality. 4. When an architecture is divided, changes can occur locally, non-locally, or architecturally. 5. Changing a single component in an architecture results in a local change.

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    1. The key points made in the document are: 2. Every software system has an architecture and it provides a common language for communication among stakeholders. 3. Decisions made at all levels of the software development life cycle can affect system quality. 4. When an architecture is divided, changes can occur locally, non-locally, or architecturally. 5. Changing a single component in an architecture results in a local change.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    297 views3 pages

    SAD Mcqs

    Uploaded by

    Genghis Khan 69
    1. The key points made in the document are: 2. Every software system has an architecture and it provides a common language for communication among stakeholders. 3. Decisions made at all levels of the software development life cycle can affect system quality. 4. When an architecture is divided, changes can occur locally, non-locally, or architecturally. 5. Changing a single component in an architecture results in a local change.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    of 3

    1. what is the actual meaning of this statement “Every software system has an architecture”?

    a. System itself is a component


    b. Architecture an exist independently of its description or specification
    c. All the system to be stable should possess an architecture
    d. All of these

    2. We can also call a software system architecture is a vehicle for the communication among
    stake holders but why?
    a. Each stakeholder of a software system is concerned with different characteristics
    of the system affected by architecture
    b. Each stakeholder of a software system is concerned with the different aspects
    of the software system which is affected by architecture
    c. Architecture provides a common language in which different concerns can be
    expressed.
    d. Architecture provides a way for all possible communication among stake holders

    3. Which of the following is correct for decisions made at a level of software development
    life cycle?
    a. Decisions at all level of like cycle from high level design to coding, implementation
    may or may not affect system quality
    b. Decisions at all level of like cycle from high level design to coding,
    implementation affect system quality
    c. Decisions at all level of like cycle from high level design to coding, implementation
    does not affect system quality
    d. All of these

    4. In an architecture, if we divide that architecture then some changes may occur in which of
    the following categories?
    a. Local
    b. Non-local
    c. Architectural
    d. All of these

    5. If we change any single component in an architecture than which change would be


    happened?
    a. Local Change
    b. Non-local Change
    c. Architectural Change
    d. All of these

    6. Which of the following structure that describe the unit or units as a program or module is
    called?
    a. Call
    b. Uses
    c. Control Flow
    d. Data

    7. In a software system, the factors that are perceptible by run-time are


    a. Modifiability
    b. Performance
    c. Portability
    d. Integrability

    8. Don’t expect ___________ correspondence between modules and components.


    a. One to one
    b. One to Many
    c. Many to Many
    d. Many to One

    9. Unless all of your requirements are _________ your software quality attributes should be
    achieved using a specific architectural patterns and tactics specific to each attribute.
    a. Precendented
    b. Unprecedented
    c. Discernable
    d. Undiscernable

    10. The views of the software architecture should address the concerns of the most important
    stakeholders in support of the ____________.
    a. Process timeline
    b. Project timeline
    c. Quality Attributes
    d. Software Aspects

    11. The separating the concerns, the cross-cutting concerns can be localized by using which of
    the following mechanism?
    a. Structure
    b. Class
    c. Object
    d. None of these

    12. Which of the following aspect weaving approach is used where the compiler is modified
    to include an aspect weaver?
    a. Source code preprocessing weaving
    b. Link time weaving
    c. Dynamic Weaving
    d. Run time Weaving
    13. The ___________ of requirements provides a basis for identifying some system extensions
    that may be implemented as aspects.
    a. Basic Level Statement
    b. Low Level Statement
    c. High Level Statement
    d. Every Statement

    14. When designing a system every software engineer should think of a system that supports
    different stakeholders’ concerns as a
    a. Core system
    b. Central system
    c. Extended system
    d. All of these

    15. In an AspectJ event that are part of joint model does not include
    a. Data Event
    b. Call event
    c. Handling Event
    d. Execution Event

    You might also like