`Prof.

Marianne Andres

Software Engineering IBS 5 exam questions

You can find more exam questions in the online tests in Felix, hopefully soon 😊

Introduction and project management

1. Name and explain at least 4 features that characterise software.
 Acceptability and Usability -SW must be acceptable to the user for which it is designed.
This means it must be understandable, usable and compatible with other systems they
use
 Efficiency and Performance- SW should not make wasteful use of system resources such
as memory and processor cycles. Efficiency therefore includes responsiveness,
processing time, memory utilization
 Dependability and security -Dependability includes a range of characteristics including
reliability, security and safety. Dependable SW should not cause physical or economic
damage in the event of system failure. Malicious users should not be able to access or
damage the system.
 Maintainability and Adaptability -SW should be written in such a way that it can evolve to
meet the changing needs of customers. This is a critical attribute because SW change is
an inevitable requirement of a changing business environment.
 Functionality refers to the capability of the system (safety, correctness, adequacy,
interoperability)
 Reliability refers to the maintenance of a level of performance (fault tolerance, mature,
Recoverability)
 Usability refers to the effort spent on using a system by an individual mor group of
individuals (learnability, comprehensibility, operability)

2. Explain who BITKOM is.

3. What characterises a project?
 A project is a temporary form of organisation for working on a given task. Serves to
regulate responsibilities and allocate the resources necessary for the work.
 Defined objectives: A project has a clearly defined objective or goal that it seeks to
achieve. The objective may be to develop a new product, implement a new system, or
solve a particular problem.
 Temporary: A project has a defined start and end date. It is not a continuous operation
and is designed to be completed within a specific timeframe.
 Resources: A project requires resources such as people, money, materials, and
equipment. These resources need to be managed effectively to ensure the successful
completion of the project.
 Timeline/Deadline

4. What is project management?

  Planning
 Organizing
 Controlling& monitoring
 communication

5. Explain the 4 planning phases of a web development project and name the essential
project documents of each phase.
Discovery(project initiation document- PID), definition(FRD), planning phase (PMP- project
management plan), design phase (design specification document)
6. What is the purpose of a feasibility study and which 5 questions should be answered in
any case?
The purpose is to asses the viability and potential success of a proposed project.
 Technically feasible
 Economically
 Operationally
 Legally
 Risks and benefits (sustainable)

7. Define what is meant by a process.

 A process of a project refers to the description of the steps, the persons involved, the
information required for this process and the information to be generated.

8. What is a milestone within a project?

 a point in a process / project at which there is a planned outcome.
Means for
▪ Structuring a process / project
▪ Control of the project progress
▪ Planning by defining outcome and resources
▪ Achieved when result is available
▪ Control through comparison of TARGET expenditure with ACTUAL expenditure
▪ Only effective if measurable
9. What kind of intermediate results are suitable for milestones?
 Completion of project phases: Milestones could be set for the completion of different
phases of the project, such as design, development, testing, and deployment. These
milestones should represent significant progress towards the completion of the
project.
 Completion of key deliverables: Milestones could be set for the completion of key
deliverables, such as a design document, prototype, or test plan. These deliverables
should be specific and significant in terms of the project's overall objectives.
 Meeting deadlines: Milestones could be set for meeting specific deadlines, such as
completing a deliverable by a certain date or launching the project by a specific
deadline. These milestones should be achievable and significant in terms of the
project's overall objectives.
 Project charter, requirement specification, design specification, progress report

10. What is the software life cycle? Briefly explain the stages through which it passes.
 The period of time during which a software component is edited or used is
commonly referred to as the software's lifecycle. The software lifecycle
includes all stages of the software's development, requirement
Analysis,rough design,detailed design,implementation,testing and
integration.

Process models
11. What are the phases of the Winston Royce waterfall model?
 Analysis and definitions
 Architectural concepts and designs
 Implementation
 Test
 System Introduction
 Insert (deployment) and maintenance.

12. Name four main problems for projects that strictly follow the waterfall model.
 Delayed integration and late design implementation
 ▪ late risk resolution
 Rigidity
 Late detection of issues
 Problematic relationship with stakeholders, are only involved during the requirements
specification process
 ▪ Focus on documents and review meetings
 Not keeping to the planned project duration, i.e. the end of the project falls into the
test phase
 Poorly tested products poor maintenance, poor deployment
  High risk of failure: The Waterfall model involves completing each stage of
development before moving on to the next, which can result in a high risk of
failure if any stage is not completed successfully.
 There is a danger that the documentation becomes more important than the actual
system because the Waterfall model relies heavily on upfront planning and
documentation.
 It does not always make sense to carry out all development steps sequentially because
it limits visibility. That is, it can make it difficult to identify and address issues early
in the development process, leading to delays and increased costs.

13. What measures can be taken to improve the waterfall model?

 Rapid Prototyping: Serves to improve coordination with the client. It is revised until the
requirements have been established. Usually, a prototype of the user interface is
sufficient.
 Iterative Development: One way to improve the Waterfall model is to incorporate an
iterative approach, which involves repeating certain phases of the development cycle
as needed. This can help identify and address issues early in the development process
and prevent them from becoming more significant later.
 Continuous Integration: Continuous integration involves integrating new code into the
main codebase regularly. This can help prevent issues from arising due to conflicting
changes made by different developers, reducing the risk of major issues later on.

14. Name at least two alternatives to the waterfall model. Small and linear/sequential
 Spiral Model
 Agile Model (Kanban and Scrum)
 V model (small& medium) + systematic
 V model XT
 Modern Development process (RUP) large scale+ iterative
 Xtreme small, medium+ iterative

15. For which projects is the V-Modell used? Which sub-models does it consist of?
 IT projects of the German Armed Forces and subsequently for authorities of IABG

Sub models include;

 PM= Project Management
 QA= Quality assurance
 SE= Software Development
 KM =Configuration management

16. Explain the V (subsystem software development) in the V-model.

 The "V" in the V-Model represents the verification and validation of the software
system, and it is the central concept of the model. The V-Model is based on the idea
that testing and verification should be conducted throughout the entire software
development process, starting with the initial requirements gathering and analysis
 phase, all the way through to the final testing and validation of the completed software
system.

17. Name and explain at least 6 principles or approaches that characterise Extreme
Programming.
 Mission Statement: Software Evolution
 System is not constructed but grows. (iterative)
 Processes of specification, design, and implementation are interleaved.
 Divides development into a sequence of iterations (repetitions)
 Per iteration: complete partial result with operational software
 Deliveries organised as autonomous sub-projects.
 Features:
 ▪ As simple as possible design, simple process with little administrative effort
 ▪ Evolutionary design process
 ▪ There is always a running version
 ▪ Small teams of 10-20 employees

18. How does Pair Programming work in Extreme Programming? What opportunities does it
offer and why is it also viewed sceptically?
 Pair programming is a practice in Extreme Programming (XP) where two programmers
work together at one computer, with one person typing and the other person
reviewing each line of code in real-time. The roles are switched frequently, and the two
programmers work collaboratively to write high-quality code. One person assumes
the role of the driver, actively writing the code, while the other person takes
on the role of the navigator, providing feedback.
 Importance
 15% lower error rate
 it facilitates knowledge sharing and allows developers to learn from each other's skills
and experience.
 Pair programming also helps to improve the quality of code through continuous review
and feedback, as the second person acts as a checkpoint for the code being written.
 The practice can also increase team morale, as it fosters a culture of collaboration and
support.
Disadvantages
 it can be a drain on productivity, as two people are working on one computer instead
of two.
 Additionally, some people may not be comfortable working in such a collaborative
environment, as it requires a high level of communication and can sometimes lead to
disagreements or conflicts.
 Finally, pair programming can also be difficult to implement in remote or distributed
teams, as it requires physical co-location.

19. Illustrate the steps of an iteration in Extreme Programming.

 Draft
 Test case specification
 Implementation
  Test execution
 Introduction/ maintenance
 Refactoring
 Master planning
 Iterative planning
 Requirement investigation

20. How do modern development processes work(RUP)? What happens in the individual
phases, which disciplines are important?
 Modern development processes emphasize an iterative and incremental approach. the
development is divided into smaller iterations or increments. Each iteration focuses on
delivering a working subset of the system, allowing for regular feedback, adaptation,
and continuous improvement.
 Phases of modern development processes are:
1. Inception and conception: the Inception phase is the initial phase of the
project. Its primary goal is to establish a common understanding of the
project's objectives, scope, risks, and feasibility. Key activities include defining
the business case, identifying Stakeholders.
2. Elaboration: The Elaboration phase focuses on refining the project's vision,
establishing a sound architecture, and addressing significant risks.
3. Construction: The Construction phase involves the actual development of the
software system. It includes activities such as coding, testing, integration, and
system-level verification.
4. Transition: The Transition p hase is the final phase of the project and focuses
on ensuring the successful deployment and handover of the software system
to end-users. Activities in this phase include final system testing, user
acceptance testing, training.
 The Disciplines that are important are:
1. Business modelling and requirement
2. Analysis and Design
3. Implementation
4. Test
5. Deployment
6. Configuration and change management
7. Project management Environment.

21. One can characterise the models for the development process listed in the table on the
basis of the criteria mentioned. Complete the table with the most important
characteristics:

Suitable
Procedure created for which Order of Most important
model Year (approx.) Project activities Methodologies (2-3)
sizes
1970 by Winston Small Linear Requirement Analysis,
Waterfall Architectural concept,
projects
model Royce Sequential design,implementation,t
est

Requirement
Engineering
2005 Complex
Unit Testing
and
V-Modell Government IT Systematical
extensive Deployment
XT Projects and ly
projects Quality Assurance
German armed forces and SMEs
Configuration
Management

eXtreme
Programmi small to Pair programming
ng medium-
1999 Kent Beck iterative Unit testing
sized
projects Continous Iteration

Large Scale
Iterative Development.
2000 project
Modern with Use case driven.
developme Booch,Rumboug,Jacob Iterative
extensive
nt process, sen Component based
requireme
e.g. RUP driven.
nt

Requirements management
22. What is meant by a specification? (second phase)
 In the context of software development, a specification is a document that describes
the requirements and functionality of a software system or component. It may include
information such as system architecture, design, interface specifications, data
structures, algorithms, performance characteristics, and other technical details.

23. What are software requirements? (Definition) (first phase)

 The requirement of a system or software is the description of the services that a
system should provide and the constraints of its operation. This requirement often
reflects customer needs.

24. When in the development cycle will requirements be specified? Why does this make
sense?
 Requirements are typically specified early in the software development cycle. This
makes sense because it is important to clearly define the goals, needs, and
expectations of the stakeholders before any development work begins. By specifying
 the requirements early in the development cycle, the development team can ensure
that the software system is designed and implemented to meet these requirements.

25. Why is setting requirements important? Give 5 reasons.

 Clear communication
 Scope management
 Customer satisfaction
 Qulity assurance
 Development efficiency
 Risk mitigation

26. What is a requirements specification?

A requirements document, is a formal document that captures and describes the functional
and non-functional requirements of a software system. It serves as a communication bridge
between the stakeholders, such as customers, users, and the development team, ensuring a
shared understanding of what the software system should accomplish.

27. List 10 points that must be covered in a requirements specification.

1. Introduction: Provides an overview of the software system, its purpose, and the
intended audience of the document.
2. Scope: Defines the boundaries of the software system, specifying what is
included and excluded from the project.
3. Functional Requirements: Describes the specific features, functionalities, and
behaviors the software system should exhibit. This section outlines the
system's inputs, outputs, and the interactions between different components.
4. Non-functional Requirements: Specifies the quality attributes and constraints
of the software system. This includes performance, reliability, security, usability,
and other aspects that may not directly relate to the system's functionalities
but are essential for its successful operation.
5. User Interface: Provides details about the graphical user interface (GUI) or any
other user interaction components, including design guidelines, layouts, and
navigation.
6. Use Cases/Scenarios: Presents detailed use cases or scenarios that describe
how the system will be used in real-world situations. These use cases help
identify different actors, their interactions with the system, and the expected
outcomes.
7. System Constraints: Outlines any technical, hardware, software, or
environmental constraints that need to be considered during system
development.
8. Assumptions and Dependencies: Lists any assumptions made during the
requirement gathering process and identifies any external dependencies that
may impact the system's implementation or operation.
9. Glossary: Includes a glossary of terms used throughout the document to
ensure a common understanding of terminology among stakeholders.
28. What role does the requirements process play in the development cycle? Complete the
relationship arrows in the diagram below (phases of the development cycle) and name
the relationship arrows.

29. Name the 7 main problems encountered when preparing the requirements analysis.
 Unclear objectives
 Language barrier
 Bad quality
 High complexity
 Unneeded features
 Inaccurate planning
 Changing requirements

30. Name and explain 4 basic problems that can occur when preparing the requirements
analysis.
 Redundancies
 Contracdictions
 Ambiguity
 Inaccurate information

31. Name at least 4 different types of requirements.

 Functional
 Non-functional
 User requirements
  System requirements

32. What are stakeholders?

a. Why should stakeholder interests be analysed as part of a requirements process?
 Stakeholders refer to all the persons, groups and institution that are involved
in the development of a product and the operations of its constraints.
 Affected directly or indirectly by the project’s outcome

33. Why is it necessary to identify the context of use for the product to be created?
 The future product will be part of the application context.
 The application context must contain everything that may be changed by the product
and somethings that may not be changed.
 The system involved in the application must be found.

34. A central problem in the requirements process is the identification of requirements.

a. Name 2 categories of investigative techniques and briefly describe for which
situation they are recommended.
Interviews and surveys
Document analysis
Feedback techniques
Creativity techniques: Suitable for collecting initial ideas, getting a first overview,
rough goals and vision of the system to be developed.
 Observation techniques: Powerful technique for observing work processes,
suitable for identifying detailed and unconscious demand
 Interviewing techniques: Targeted questions about stakeholders' facts,
processes and wishes, also suitable for any level of detail if the stakeholder is
aware of them and can abstract sufficiently.
b. Describe a concrete investigation technique and name advantages and
disadvantages.

Advantages of Prototyping:

 Iterative Approach: Prototyping allows for an iterative and incremental

development process, where a basic version of the system or a specific feature
is quickly built and tested. This helps in uncovering requirements and refining
them based on user feedback.
 Visualization: Prototypes provide a tangible representation of the system,
allowing stakeholders to visualize and interact with it. This helps in identifying
potential issues or gaps in requirements early on.
 User Feedback: Prototypes facilitate user involvement and feedback. Users can
interact with the prototype, providing valuable insights and suggestions for
improvements.
  Requirement Validation: Prototyping aids in validating requirements and
ensuring that they meet the intended objectives. It allows for early
identification of conflicts or inconsistencies, reducing the risk of rework later in
the development process.

Disadvantages of Prototyping:

 Time and Effort: Developing prototypes can be time-consuming and resource-

intensive, particularly for complex systems. It requires dedicated effort from
the development team.
 Scope Creep: Prototyping may lead to scope creep, where additional features
or functionalities are requested based on the prototype's initial success. This
can impact project timelines and budgets if not managed properly.
 Misinterpretation: Stakeholders might interpret prototypes as the final
solution, leading to misunderstandings or false expectations. Clear
communication is crucial to ensure that prototypes are seen as a tool for
exploration and not the end product.
 Technical Limitations: Depending on the fidelity of the prototype, technical
limitations may arise. Certain functionalities or interactions may not be
accurately represented, which can impact the validity of requirements
identified through prototyping.

UML & Use Cases

35. What does UML mean? What is UML used for?
 Unified Modelling Language and it provides for an activity diagram.

36. What is a use case? (Definition)

 A use case is a typical interaction with the system. That is, it represents an
external perceivable behaviour of the system in a work time situation
 A use case is triggered or initiated by an actor which must see perceivable
results.
 A use case may contain different process variants.
 A use case may contain a set of possible scenarios.

37. What should a use case describe, what not?

 A use case should describe WHAT a system should or must do and not HOW the system
should do.
 A use case should describe a consistent, purposeful and temporarily uninterrupted
sequence of activities of an actor with which a result of professional value visible to the
actor is produced.

38. What should a use case describe, what not? Where and how to find use cases (at least
three examples)
  A use case should describe WHAT a system should or must do and not HOW the
system should do.
 We can find use cases via
 Documentation and Manuals:
 Online Resources and Communities
 Case Studies:

39. Where does a use case start and where does it end?
 A use case starts when there is a trigger or stimulus from a client or business and its
called the business trigger. A use case start with the goal or oblective that a user or
system needs to accomplish.
 A use case ends when this objective and goal have been achieved and its called the
business value or outcome or results.

40. Draw a use case diagram for the use cases "Reserve car", "Take back car", "Accept
customer" with the corresponding actors.
41. In the lecture we had a case study "car rental". In this context, customers who want to
make use of the service offer can also be included. Describe the essential use case "Take
up customer" in the known scheme:

Name: Take a customer

Short description: An interested party (person) is to be accepted

as a customer.

Actors: Car rental company(employee, system), customer

Trigger: The car rental employee wishes to take up the njkclient

Incoming Payment details, method of payment

Confirm payment.
information:

Results: Handout car to client

Agreement Contract signed.

Procedure: Payment menthod

Payment made
Checks payment
Confirm payment
Prepare agreement contract
Sign agreement contracts
Hand over car,car keys
42. In the lecture we had a case study "car rental". In this context, there was the essential
use case "Reserving a car". Describe the concrete use case "Reserving a car on the
internet" in the known scheme:

Name: Reserve a car on the internet

Short description: A car is reserved for a customer via the Internet for a defined
period of time.

Actors: Client, system

Trigger:
A customer would like to reserve a car via the internet.

Incoming Customer number, customer pin and other customer data

Reservation Request
information:

Results: Reservation, reservation request confirmed.

Procedure: Identify customer.

Record reservation
Check possibilities of the reservation
Reserve vehicle
Confirm reservation.

43. What are the relationships between use cases?

Include: within use cases there are other use cases
Extend: a use case can be extended from a certain point
Specialisation/generalisation: sub use cases can get behaviour and meaning from
higher level use cases.
44. The processes of a use case can be modelled in an activity diagram. Create the standard
process for the use case "Reserve a car on the internet" in an activity diagram.
45. The tea online shop Teeversand Hamburg provides various online services for its customers,
among other things, the customer can order tea and accessories. To do this, the use case Order
tea online must be formulated. To do this, the customer name must first be entered. The system
checks whether the customer is already registered or whether he still has to enter his address.
The address is displayed to the customer, if it is not correct, he can change it. He can then select
different teas and the desired quantity. The system shows the total of the desired goods and the
customer can send the order. The system shows the customer the order confirmation with the
approximate delivery time.
a. Formulate the use case in the tabular representation with flow.

b. The flow of a use case can be modelled in an activity diagram. Create the activity
diagram for the use case Order tea online.
 Interfaces

46. When do you need an interface description?

 System integration
 API Development
 Interfacing with external system

47. List quality criteria for the requirements document.

 Completeness
 Consistent
 Traceability
 Clarity
 Correctness
 testable
Class diagrams + sequence diagrams
48. Model the tea online shop Teeversand Hamburg with the help of a UML class diagram. The
customers' orders are processed by the employees in the tea warehouse, i.e. they compile the
individual items into a consignment, which is then sent to the customer by TeeVersnd.
Consequently, an order includes a customer who has an address to which delivery is made and a
billing address.
From the text, there are some classes (note the nouns in bold) with attributes and methods. Each
class must contain attributes (at least 2 per class) and methods. Find a total of at least 6 sensible
methods that correspond to the text and represent all the relationships between the classes
appropriately.
49. For the Pizzeria Flitz-Piz, the following scenarios for an online pizza service are created in a first
draft:
 A customer selects his desired pizza and orders it.
 In order for the pizza to be delivered, the customer must register and provide his or her
address and other data.
 The customer can log in to view the progress of his pizza order. He can see if the order
has been received, if it has been retrieved and if it has been handed to the pizza driver.
 Employees of the Pizzeria Flitz-Piz can view the current order list and, for each order,
mark whether they want to retrieve (i.e. process) the order now or hand it over to the
pizza driver.
a. As an analyst, you are now asked to develop meaningful use cases from the rather
imprecise scenarios. Take into account the criteria of how use cases should be
constructed. First name the use cases and give a short description including actors,
possible preconditions and the achieved result.
b. Create a use case diagram with the relationships between the individual use cases and
the actors.
c. Create an activity diagram with exceptions for the Use Case Select and Order Pizza.
d. The most important subject class objects result from the use cases. Draw a subject class
diagram without attributes, but of course with the relationships and cardinalities
between the subject classes.
Consider whether it is really only possible to order pizzas or whether it makes more
sense to be able to order other products as well. Can this be modelled so generally that
other products can be added at any time? Draw a solution in the subject class diagram.

50. To which diagram type does the sequence diagram belong?

Interaction diagrams

51. A tourist Mr Karl first transmits the destination to the information desk of an information system.
In response, he receives the price of the trip and an identification number. As he agrees with the
price, he triggers a booking order with the responsible accounting department, stating the
identification number. After receipt of the booking order, the booking office obtains all necessary
travel information from the information office via the identification number. After 2 days at the
latest, the tourist Mr Karl receives a booking confirmation.
Depict the sequence of the scenario between the three relevant objects in a sequence diagram.
52. For the following class diagram, sketch the dynamic view of the objects using a sequence
diagram. The two dices are rolled one after the other and the number is read.

DiceGame Dice
Player -hat
+dice_1 : Dice -numOfPoints : : int
-name : string +dice_2 : Dice
1 * 1 2 +getNumOfPoints():int
+play() +roll()

The contents on use cases, class diagrams and sequence diagrams/interaction diagrams
may of course vary, consider in particular the assignments in the lecture. Drawings with
UML belong to the written part of the exam.

System analysis and design

53. What types of interfaces do you know? Name at least four.
 Dialogue Interface
 Output Products
 Data Interface
 Funktional Interfaces
 Components Interface
54. How should a dialogue description be structured?
 Name
 Brief Description
 Use
 Complexity
 Input Fields
 Display Fields
 Branching Possibilities
 Actions
55. Which views should be used to describe the application architecture?
 Technical Subsystem Model
 Technical Architecture (layer model, distribution model, frameworks)
56. What goals do you want to achieve with the design of a software architecture?
 Identification of the types of Software Elements
 Structure and grouping of Software elements.
 Identification of interfaces
 Definition of basic design guidelines and decisions
 Design of an application or software systems with high level of abstraction
57. What layers does the function-oriented layered architecture consist of?
 Presentation layer
  Business logic
 Data Management
58. What is client/server architecture? (Examples ? )

Client/server architecture is a distributed computing model in which tasks and

responsibilities are divided between client devices and server systems. In this
architecture, clients initiate requests for services or resources, while servers fulfill those
requests and provide the requested services. The client/server model enables efficient
resource sharing, centralized data management, and scalability.
Here are a few examples of client/server architecture:
Web Applications
Email systems
Data Base management systems
File Sharing

59. How are components of a software system characterised?

 Provided interfaces.
 Requested interfaces.

60. What are the different types of components?

Professional component model : Allocation of the classes of the analysis class model to the
planned components:

Quality management and testing

61. Why do complex systems lead to errors?

 Errors are inherent
 We need a culture of errors
 We learn from errors
 Accept and consciously make mistakes
62. What do you think is a good culture to deal with errors?
Firstly, a culture of errors actually mean that we make errors, but we also learn and use it.
A good culture of error is to accept and consciously use mistakes by facing, finding looking and
fixing mistakes, and this can be done by
Differentiating test types
And also, organisations on quality management

63. What is quality for software systems due to 9000?

Quality of a system refers to the totality of characteristics of an entity related to its ability to to
meet specific user requirement.

64. Explain the software quality comprises factors (functionality, reliability, usability, efficiency, …)
according to ISO 9126.
 Functionality refers to the capability of the system (safety, correctness, adequacy,
interoperability)
  Reliability refers to the maintenance of a level of performance (fault tolerance, mature,
Recoverability)
 Usability refers to the effort spent on using a system by an individual mor group of
individuals (learnability, comprehensibility, operability)
 Efficiency measures the results (resource consumption, Time Response)
 Transferability, means operation under different operating software (adaptability,
install -ability, conformity)
 Changeability means efficient use over a long period of time ( Modifiability, testability)

65. How can we test the validation of a product?

 How the product performs compared to how the client wanted it to
66. What is meant with the verification of a software product?
Test and assessments that demonstrate the conformance of the intermediate and final results
of a phase or iteration in the life cycle with results of the previous one
67. Describe the difference between demonstrative and destructive testing.
Demonstrative testing is a systematic execution of a system or programme to increase quality
While destructive testing is the process of running a system or program with the intention of
finding a bug.
Destructive is better bc circumstance controlled in demonstrative will limit the test.

68. Name three typical static test methods.

 Review: formally planned and structured process of analysis and evaluation in which a project
results are presented to and commented on or approved by a team of reviewers.
 Inspection
 Walkthrough

69. Describe the procedure of a formal review.

1. Review: formally planned and structured process of analysis and evaluation in which a
project results are presented to and commented on or approved by a team of reviewers.
2. Inspection
3. Walkthrough

70. How can you execute a white box test?

Software is executed with test data.
Execution in real environment
Principle of the sampling procedure
Need to select test cases and test data.

71. How do you have to design a test case? What belongs to a test case?

72. Why it is useful to build equivalence classes for test cases?

73. What is a unit test? Elucidate the advantage of a unit test.
 Unit test focuses on verifying the functionality and behaviour of individual units or
components of a software system. It aims to isolate and test each unit independently
to ensure that it meets its intended requirement.
 Advantages of Unit test
 Early bug detection
 Improved code quality
 Confidence in code refactoring
 Faster debugging
 Facilitates collaboration.
 Supports continuous integration.
 Regression testing

Notes
Can a system be fully tested for correctness?
Practically No because it needs so much time.
Theoretically its possible

What do we need to do to test our system completely?

You have to put in mind every possible case.