WGU D487 SECURE SW DESIGN TEST LATEST COMPLETE
REAL TEST QUESTIONS AND WELL ELABORATED
ANSWERS (CORRECT VERIFIED ANSWERS) A NEW
UPDATED VERSION |GUARANTEED PASS A+ (FULL
REVISED EXAM)
Software Design - ANSWER: • The process of applying various techniques and
principles for the purpose of defining a device, a process or a system in sufficient
detail to permit its physical realization
Software Design - ANSWER: • Software design is the development stage in which
solutions to a problem are explored
• More accurately, software design explores different approaches to satisfying the
requirements of the SRS
Software Design - ANSWER: • The input to the software design stage is the SW Reqs
specification
• The completeness of this specification is contingent on the life cycle model being
used
• How the design progresses is therefore contingent on the life cycle model as well
Software Design - ANSWER: • In a linear sequential development model, the entire
specification is constructed prior to the design stage
• The design stage begins with full information about the product to be constructed
• All design alternatives are available at the outset (potential solutions)
Software Design - ANSWER: • In an evolutionary life cycle, like the spiral model, the
system grows in stages
• Early design phases are limited since knowledge of the product is limited
• mock-ups
• story boards
• prototyping tools
The thin, gray line - ANSWER: • What distinguishes software specification from
software design?
• In a linear sequential model, there is a definite boundary between phases
• In an evolutionary model, this line becomes harder to detect, since the phases
iterate so often
Specification vs. Design - ANSWER: • The old adage still applies
• Specification answers the question "What are we going to build?"
• Design addresses the issue "How are we going to build it?"
Specification vs. Design - ANSWER: • Prototypes and mock-ups in a specification
address
, • user interaction with the system
• business processes and constraints
• requirements of process interaction
• other product environment issues and interfaces
• "What the system will do"
Specification vs. Design - ANSWER: • Prototypes and mock-ups in a design address
• How data will be represented
• How data will be transformed
• How control will flow through the system
• How the system will react to stimuli
• other implementation specific details
• "How will it be done"
Software Design - ANSWER: • Data/Class design - transforms analysis classes into
implementation classes and data structures
• Architectural design - defines relationships among the major software structural
elements
• Interface design - defines how software elements, hardware elements, and end-
users communicate
• Component-level design - transforms structural elements into procedural
descriptions of software components
????? - ANSWER:
Design and Quality - ANSWER: • the design must implement all of the explicit
requirements contained in the analysis model, and it must accommodate all of the
implicit requirements desired by the customer.
• the design must be a readable, understandable guide for those who generate code
and for those who test and subsequently support the software.
• the design should provide a complete picture of the software, addressing the data,
functional, and behavioral domains from an implementation perspective.
Quality Guidelines - ANSWER: • A design should exhibit an architecture that (1) has
been created using recognizable architectural styles or patterns, (2) is composed of
components that exhibit good design characteristics and (3) can be implemented in
an evolutionary fashion
• A design should be modular; that is, the software should be logically partitioned
into elements or subsystems
• A design should contain distinct representations of data, architecture, interfaces,
and components.
Quality Guidelines - ANSWER: • A design should lead to data structures that are
appropriate for the classes to be implemented and are drawn from recognizable
data patterns.
• A design should lead to components that exhibit independent functional
characteristics.
REAL TEST QUESTIONS AND WELL ELABORATED
ANSWERS (CORRECT VERIFIED ANSWERS) A NEW
UPDATED VERSION |GUARANTEED PASS A+ (FULL
REVISED EXAM)
Software Design - ANSWER: • The process of applying various techniques and
principles for the purpose of defining a device, a process or a system in sufficient
detail to permit its physical realization
Software Design - ANSWER: • Software design is the development stage in which
solutions to a problem are explored
• More accurately, software design explores different approaches to satisfying the
requirements of the SRS
Software Design - ANSWER: • The input to the software design stage is the SW Reqs
specification
• The completeness of this specification is contingent on the life cycle model being
used
• How the design progresses is therefore contingent on the life cycle model as well
Software Design - ANSWER: • In a linear sequential development model, the entire
specification is constructed prior to the design stage
• The design stage begins with full information about the product to be constructed
• All design alternatives are available at the outset (potential solutions)
Software Design - ANSWER: • In an evolutionary life cycle, like the spiral model, the
system grows in stages
• Early design phases are limited since knowledge of the product is limited
• mock-ups
• story boards
• prototyping tools
The thin, gray line - ANSWER: • What distinguishes software specification from
software design?
• In a linear sequential model, there is a definite boundary between phases
• In an evolutionary model, this line becomes harder to detect, since the phases
iterate so often
Specification vs. Design - ANSWER: • The old adage still applies
• Specification answers the question "What are we going to build?"
• Design addresses the issue "How are we going to build it?"
Specification vs. Design - ANSWER: • Prototypes and mock-ups in a specification
address
, • user interaction with the system
• business processes and constraints
• requirements of process interaction
• other product environment issues and interfaces
• "What the system will do"
Specification vs. Design - ANSWER: • Prototypes and mock-ups in a design address
• How data will be represented
• How data will be transformed
• How control will flow through the system
• How the system will react to stimuli
• other implementation specific details
• "How will it be done"
Software Design - ANSWER: • Data/Class design - transforms analysis classes into
implementation classes and data structures
• Architectural design - defines relationships among the major software structural
elements
• Interface design - defines how software elements, hardware elements, and end-
users communicate
• Component-level design - transforms structural elements into procedural
descriptions of software components
????? - ANSWER:
Design and Quality - ANSWER: • the design must implement all of the explicit
requirements contained in the analysis model, and it must accommodate all of the
implicit requirements desired by the customer.
• the design must be a readable, understandable guide for those who generate code
and for those who test and subsequently support the software.
• the design should provide a complete picture of the software, addressing the data,
functional, and behavioral domains from an implementation perspective.
Quality Guidelines - ANSWER: • A design should exhibit an architecture that (1) has
been created using recognizable architectural styles or patterns, (2) is composed of
components that exhibit good design characteristics and (3) can be implemented in
an evolutionary fashion
• A design should be modular; that is, the software should be logically partitioned
into elements or subsystems
• A design should contain distinct representations of data, architecture, interfaces,
and components.
Quality Guidelines - ANSWER: • A design should lead to data structures that are
appropriate for the classes to be implemented and are drawn from recognizable
data patterns.
• A design should lead to components that exhibit independent functional
characteristics.
