FUNDAMENTALS OF SOFTWARE
ENGINEERING FINAL PAPER 2026 TEST
PAPER QUESTIONS AND SOLUTIONS
GRADED A+
● Plan-driven processes. Answer: processes where all of the process
activities are planned in advance and progress is measured against the
plan
● Agile processes. Answer: incremental and it is easier to change the
process to reflect changing customer requirements- 'Light-weight'
process models. Everyone can work at any part of the stages at a time.
● Is there a right or wrong type of software process to use?. Answer: In
practice, most practical processes include elements of both plan-driven
and agile approaches. There are no right or wrong processes.
● Software process model. Answer: An abstract representation of a
software process
● Software Process Models:. Answer: -Waterfall model: Start at stand-
alone phases step by step
-Incremental development
-Evolutionary development
,-Formal systems development
-Reuse-based development
● Hybrid software process models:. Answer: -Incremental development
-Spiral Development
-SCRUM
● Waterfall Model:. Answer: -Conducted in stand-alone phases; a plan-
driven software process model.
-In principle, the next phase does not start until previous phase
completes (in practice, the phases overlap and there is feedback)
Basically each step is stand-alone, so we start at a step at a time.
-First created in 1970 by Royce
-Presents the software development process by number of stages
-The stages of the waterfall model directly reflect the fundamental
software development activities:
1. Requirements analysis and definition: The system's services,
constraints, and goals are established by consultation with system users.
They are then defined in detail and serve as a system specification.
2. System and software design: The systems design process allocates the
requirements to either hardware or software systems. It establishes an
overall system architecture. Software design involves identifying and
,describing the fundamental software system abstractions and their
relationships.
3. Implementation and unit testing: During this stage, the software
design is realized as a set of programs or program
4. Integration and system testing: The individual program units or
programs are integrated and tested as a complete system to ensure that
the software requirements have been met. After testing, the software
system is delivered to the customer.
5. Operation and maintenance: Normally, this is the longest life-cycle
phase. The system is installed and put into practical use. Maintenance
involves correcting errors that were not discovered in earlier stages of
the life cycle, improving the implementation of system units, and
enhancing the system's services as new requirements are discovered.
-The waterfall model is an example of a plan-driven process. In principle
at least, you should plan and schedule all of the activities before starting
software dev
● Advantages of Waterfall Model. Answer: Advantages:
-Simple to follow (sequential, linear)
-Relatively simple to track progress (project management, "predictable
development")
-Good structural design
Challenges:
-In practice, phases overlap and iterate
, -Hard to modify and implement changes (requirements, designs)
-Need nearly a complete set of requirements from customers at the
project start (the biggest challenge)
Waterfall appropriate for:
-Embedded systems
-Critical systems (safely, security, reliability, etc.)
-Large systems with several partners, vendors, suppliers
● Incremental Development. Answer: Develop an initial
implementation, expose to users receive comments/feedback, & refine
until satisfied
-One of the most common approaches nowadays for application systems
and software products
*Can be plan-driven or agile approach
-One of the fundamental components of agile development
-Plan-driven, system increments defined in advance
-Agile development, early increments are defined but later increments
depend on the progress, reviews, and customer priorities
-Incremental development is better than waterfall when requirements are
changing during the development process. This would be the case for
business systems and software products
*Common for business systems, software products
*Each increment delivers new functionality to evaluate and feedback to
the development team
ENGINEERING FINAL PAPER 2026 TEST
PAPER QUESTIONS AND SOLUTIONS
GRADED A+
● Plan-driven processes. Answer: processes where all of the process
activities are planned in advance and progress is measured against the
plan
● Agile processes. Answer: incremental and it is easier to change the
process to reflect changing customer requirements- 'Light-weight'
process models. Everyone can work at any part of the stages at a time.
● Is there a right or wrong type of software process to use?. Answer: In
practice, most practical processes include elements of both plan-driven
and agile approaches. There are no right or wrong processes.
● Software process model. Answer: An abstract representation of a
software process
● Software Process Models:. Answer: -Waterfall model: Start at stand-
alone phases step by step
-Incremental development
-Evolutionary development
,-Formal systems development
-Reuse-based development
● Hybrid software process models:. Answer: -Incremental development
-Spiral Development
-SCRUM
● Waterfall Model:. Answer: -Conducted in stand-alone phases; a plan-
driven software process model.
-In principle, the next phase does not start until previous phase
completes (in practice, the phases overlap and there is feedback)
Basically each step is stand-alone, so we start at a step at a time.
-First created in 1970 by Royce
-Presents the software development process by number of stages
-The stages of the waterfall model directly reflect the fundamental
software development activities:
1. Requirements analysis and definition: The system's services,
constraints, and goals are established by consultation with system users.
They are then defined in detail and serve as a system specification.
2. System and software design: The systems design process allocates the
requirements to either hardware or software systems. It establishes an
overall system architecture. Software design involves identifying and
,describing the fundamental software system abstractions and their
relationships.
3. Implementation and unit testing: During this stage, the software
design is realized as a set of programs or program
4. Integration and system testing: The individual program units or
programs are integrated and tested as a complete system to ensure that
the software requirements have been met. After testing, the software
system is delivered to the customer.
5. Operation and maintenance: Normally, this is the longest life-cycle
phase. The system is installed and put into practical use. Maintenance
involves correcting errors that were not discovered in earlier stages of
the life cycle, improving the implementation of system units, and
enhancing the system's services as new requirements are discovered.
-The waterfall model is an example of a plan-driven process. In principle
at least, you should plan and schedule all of the activities before starting
software dev
● Advantages of Waterfall Model. Answer: Advantages:
-Simple to follow (sequential, linear)
-Relatively simple to track progress (project management, "predictable
development")
-Good structural design
Challenges:
-In practice, phases overlap and iterate
, -Hard to modify and implement changes (requirements, designs)
-Need nearly a complete set of requirements from customers at the
project start (the biggest challenge)
Waterfall appropriate for:
-Embedded systems
-Critical systems (safely, security, reliability, etc.)
-Large systems with several partners, vendors, suppliers
● Incremental Development. Answer: Develop an initial
implementation, expose to users receive comments/feedback, & refine
until satisfied
-One of the most common approaches nowadays for application systems
and software products
*Can be plan-driven or agile approach
-One of the fundamental components of agile development
-Plan-driven, system increments defined in advance
-Agile development, early increments are defined but later increments
depend on the progress, reviews, and customer priorities
-Incremental development is better than waterfall when requirements are
changing during the development process. This would be the case for
business systems and software products
*Common for business systems, software products
*Each increment delivers new functionality to evaluate and feedback to
the development team
