Scribd
Upload
10 views4 pages

Essay and All Match

Uploaded by

Aya Adel
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
10 views4 pages

Essay and All Match

Uploaded by

Aya Adel
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

1. Explain the ISO 9126 Software Quality Model?

a software quality model which categorizes software quality into


six:
 Functionality: Characteristics relating to achievement of the basic purpose for
which the software is being engineered
 Reliability: Characteristics relating to capability of software to maintain its level of
performance under stated conditions for a stated period of time
 Usability: Characteristics relating to the effort needed for use, and on the individual
assessment of such use, by a stated implied set of users.
 Efficiency: Characteristic related to the relationship between the level of performance of
the software and the amount of resources used, under stated conditions
 Maintainability: Characteristics related to the effort needed to make modifications
 Portability: Characteristics related to the ability to transfer the software from one
organization or hardware or software environment to another
2. Why are the software changes inevitable?
 New requirements emerge when the software is used;
 The business environment changes;
 Errors must be repaired;
 New computers and equipment is added to the system;
 The performance or reliability of the system may have to be
improved.

3. What are the software configuration management activities?


 Change management
 Version management
 System building
 Release management

4. Draw the model of software testing process?


5. What are the benefits of test-driven development?
Code coverage
 Every code segment that you write has at least one associated test so all code written has at least
one test

Regression testing
 A regression test suite is developed incrementally as a program is developed.

Simplified debugging
 When a test fails, it should be obvious where the problem lies. The newly written code needs to
be checked and modified.

System documentation
 The tests themselves are a form of documentation that describe what the code should be doing.

6. Compare between software verification and software


validation?
Verification: "Are we building the product right”.
The software should conform to its specification.

Validation: "Are we building the right product”.


The software should do what the user really requires..

7. What are the differences between Release testing and System testing?
Important differences:
 A separate team that has not been involved in the system
development, should be responsible for release testing
 System testing by the development team should focus on discovering
bugs in the system
 objective of release testing is to check that the system meets its
requirements and is good enough for external us
8. What are the advantages of Inspections?
 During testing, errors can mask (hide) other errors, inspection is a
static process
 Incomplete versions of a system can be inspected without additional
costs
 inspection can also consider broader quality attributes of a program,
such as compliance with standards, portability and maintainability
9. Explain the Change Management Process?
The CM process is concerned with analyzing the costs and benefits of
proposed changes, approving those changes that are worthwhile and tracking
which components in the system have been changed

10. Explain software quality reviews and its application on Agile


Methods?
 The review process in agile software development is usually informal
 In Scrum, there is a review meeting after each iteration of the software
has been completed
 In extreme programming, pair programming ensures that code is
constantly being examined and reviewed by another team member.

11. What is software measurements? Explain what is meant by Predictor


and Control measurements? Explain Product Metrics?

Software measurement is concerned with deriving a numeric value for an


attribute of a software product or process

A quality metric should be a predictor of product quality


Classes of product metric
 Dynamic metrics which are collected by measurements made of a program
in execution;
 Static metrics which are collected by measurements made of the system
representations;

12. Explain McCall Software Quality Model


13. What are the components of software release?
 configuration files
 data files
 an installation program
 electronic and paper documentation
 packaging

<<Question Choices>>
Change management :- Keeping track of requests for changes, working out the costs and impact of changes, and deciding
the changes.
Configuration item or software configuration :- Anything associated with a software project (design, code, test data,
document, etc.) that has been placed under configuration control.
Configuration Control :-The process of ensuring that versions of systems and components are recorded and maintained.
Baseline :- collection of component versions that make up a system.
Codeline :- set of versions of a software component and other configuration items on which that component depends.
Mainline :- A sequence of baselines representing different versions of a system.
Branching :- The ((creation of a new codeline)) from a version in an existing codeline
Merging :- The ((creation of a new version)) of a software component by merging separate versions in different codelines
System building :- The ((creation of an executable system version)) by compiling and linking the appropriate versions of
the components and libraries making up the system.
Fog index :- This is a measure of the ((average length of words)) and sentences in documents.
Validation :- The software should do what the user really requires.
Verification :- The software should conform to its specification.
Test case :- A program with input and expect output to test the real program.
Relability :- the extent to which a software performs its intended function ((without failure)).
Software metric :- Any type of measurement which relates to a software system ,process or related documentation.
Robustness :- the extent to which a sofware tolerates the unexpected problem .
Configuration management :- the policies, processes and tools for managing changing software systems.
Regression test :- testing the system to check that changes have not ‘broken’ previously working code.
Fan-in :- a measure of the number of functions or methods that call another function or method (sayX).
Fan-out :- a measure of the number of functions that are called by function X.

You might also like