Page 259 - DCAP305_PRINCIPLES_OF_SOFTWARE_ENGINEERING
P. 259

Unit 12: Refactoring



               8.  The process of optimizing the reliability of ................. through a program.  Notes
                 (a)  matrices                   (b)  software
                 (c)  refactoring                (d)  All of these.
               9.  Refactoring is an activity crucial for evolutionary .....................
                 (a)  Document process           (b)  right key process
                 (c)  Verification process       (d)  All of these.
              10.  Refactoring can be thought of as an alternative to:
                 (a)  Document upfront design    (b)  simple design
                 (c)  Careful upfront design     (d)  All of these.
              11.  Software Matrices Activates is:
                 (a)  Error prevention           (b)  complex prevention
                 (c)  Simple prevention          (d)  All of these.
              12.  Software metrics have been proved:
                 (a)  Bad quality                (b)  Right quality
                 (c)  To reflect software quality   (d)  All of these.
              13.  Refactoring is the process of converting existing
                 (a)  “Bad” code into “good” code   (b)  bugs code
                 (c)  Simple Code                (d)  All of these.

              14.  Matrices Complex city is the right process of .......................
                 (a)  verification refactoring   (b)  factoring
                 (c)  bugs factoring             (d)  All of these.
              15.  Confirmation by examination and provision of objective evidence that specified
                 requirements have been fulfilled.
                 (a)  True                       (b)  False

            12.6 Summary

               •  Refactoring is the process of converting existing “bad” code into “good” code. It is done
                 via the parser, the relational model, and the language module.
               •  Refactoring is an activity crucial for evolutionary development processes.
               •  A change made to the internal structure of software to make it easier to understand and
                 cheaper to modify without changing its observable behaviour is called Refactoring.
               •  Metrics to measure software reliability do exist and can be used starting in the requirements
                 phase.
               •  Refactoring helps the code to retain its shape. Without refactoring the design of the program
                 will decay. As people change code.
               •  The power of refactoring as a method lies in systematically organized documents, which
                 describe proven techniques for enhancing software.

            12.7 Keywords


            Documenting Refactoring: The power of refactoring as a method lies in systematically organized
            documents, which describe proven techniques for enhancing software safely.




                                             LOVELY PROFESSIONAL UNIVERSITY                                   253
   254   255   256   257   258   259   260   261   262   263   264