SOFTWARE ENGINEERING FINAL EXAM | 2026 UPDATE
| QUESTIONS AND ANSWERS WITH COMPLETE
SOLUTION
structured analysis Answer - considers data and the process that transforms
data as separate entities
object oriented analysis Answer - considers the class and how it collaborates
with other classes
requirements of modeling for webapps Answer - - content analysis
- interaction analysis
- functional analysis
- configuration analysis
interaction model Answer - - use cases
- sequence diagrams
- state diagrams
- user interface prototype
functional model Answer - - user observable functionality
- operations contained within analysis classes
configuration model Answer - server side:
,- server hardware and operating system environment must be specified
- interoperability considerations on the server side must be considered
- appropriate interfaces, communication protocols, and related collaborative
information must be specified
client side:
- browser configuration issued must be identified
- testing requirements should be defined
design principles Answer - - design process should not suffer from tunnel
vision
- design should be traceable to the analysis model
- design should not reinvent the wheel
- design should minimize the intellectual distance between the software and
the problem as it exists in the real world
- design should exhibit uniformity and integration
- design should be structured to accommodate change
- design should be structured to degrade gently
- design is not coding, coding is not design
- design should be assessed for quality as it is being created
- design should be reviewed to minimize conceptual errors
architecture Answer - the overall structure of the software and the ways that
structure provides conceptual integrity for a system
cohesion Answer - the degree to which a module performs one and only one
function
, coupling Answer - the degree to which a module is connected to other
modules in the system
refactoring Answer - process of changing a software system in such a way that
it does not alter the external behavior of the code yet improves its internal
structure
why architecture? Answer - - enables communication between all parties
interested in the development of the system
- highlights early design decision
- provides a relatively small, intellectually graspable model of how the system is
structured and how its components will work together
data design Answer - - create a model of data at a high level of abstraction
- iteratively refine into more implementation specific representations
- data structures at the component level
- database architecture at the application level
- data warehouse at the business level
data warehouse Answer - a large independent data store that contains some
but not all data that are stored in a business' database
data mining Answer - navigating through a business' databases for the purpose
of knowledge discovery
architectural styles encompass Answer - - set of components that perform a
function required by a system
- set of connectors that enable 'communication, coordination, and cooperation'
among components
| QUESTIONS AND ANSWERS WITH COMPLETE
SOLUTION
structured analysis Answer - considers data and the process that transforms
data as separate entities
object oriented analysis Answer - considers the class and how it collaborates
with other classes
requirements of modeling for webapps Answer - - content analysis
- interaction analysis
- functional analysis
- configuration analysis
interaction model Answer - - use cases
- sequence diagrams
- state diagrams
- user interface prototype
functional model Answer - - user observable functionality
- operations contained within analysis classes
configuration model Answer - server side:
,- server hardware and operating system environment must be specified
- interoperability considerations on the server side must be considered
- appropriate interfaces, communication protocols, and related collaborative
information must be specified
client side:
- browser configuration issued must be identified
- testing requirements should be defined
design principles Answer - - design process should not suffer from tunnel
vision
- design should be traceable to the analysis model
- design should not reinvent the wheel
- design should minimize the intellectual distance between the software and
the problem as it exists in the real world
- design should exhibit uniformity and integration
- design should be structured to accommodate change
- design should be structured to degrade gently
- design is not coding, coding is not design
- design should be assessed for quality as it is being created
- design should be reviewed to minimize conceptual errors
architecture Answer - the overall structure of the software and the ways that
structure provides conceptual integrity for a system
cohesion Answer - the degree to which a module performs one and only one
function
, coupling Answer - the degree to which a module is connected to other
modules in the system
refactoring Answer - process of changing a software system in such a way that
it does not alter the external behavior of the code yet improves its internal
structure
why architecture? Answer - - enables communication between all parties
interested in the development of the system
- highlights early design decision
- provides a relatively small, intellectually graspable model of how the system is
structured and how its components will work together
data design Answer - - create a model of data at a high level of abstraction
- iteratively refine into more implementation specific representations
- data structures at the component level
- database architecture at the application level
- data warehouse at the business level
data warehouse Answer - a large independent data store that contains some
but not all data that are stored in a business' database
data mining Answer - navigating through a business' databases for the purpose
of knowledge discovery
architectural styles encompass Answer - - set of components that perform a
function required by a system
- set of connectors that enable 'communication, coordination, and cooperation'
among components
