Software final examinational questions and answers, Exams of Software
Engineering
structured analysis - ANSWERconsiders data and the process that transforms
data as separate entities
object oriented analysis - ANSWERconsiders 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 - ANSWERserver 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 - ANSWERthe overall structure of the software and the ways that
structure provides conceptual integrity for a system
cohesion - ANSWERthe degree to which a module performs one and only one
function
coupling - ANSWERthe degree to which a module is connected to other
modules in the system
refactoring - ANSWERprocess 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
Engineering
structured analysis - ANSWERconsiders data and the process that transforms
data as separate entities
object oriented analysis - ANSWERconsiders 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 - ANSWERserver 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 - ANSWERthe overall structure of the software and the ways that
structure provides conceptual integrity for a system
cohesion - ANSWERthe degree to which a module performs one and only one
function
coupling - ANSWERthe degree to which a module is connected to other
modules in the system
refactoring - ANSWERprocess 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
