2. Coupling
Interaction: It occurs due to methods of a class invoking methods of other classes.
Component Coupling: refers to interaction between two classes where a class has variables of the other class. Obj
Inheritance coupling: if one class is directly or indirectly sub class of other.

3. Cohesion
Method: It focuses on why the different code elements of a method are together within the method. same as functional cohesion, X and Y are a part of single functional task. Related to performing single function.
Class: Focuses on why different attributes and methods are together in this class.
Inheritance: why classes are together in hierarchy.

4. Software Metrics It is a unit of measurement of software product.
The continuous application of measurement based techniques to the software development process and its products to supply meaningful and timely management information , together with the use of those techniques to improve that process and its products.

5. What and Why How to measure the size of a s/w
How much will it cost to develop a s/w?
How many bugs can we expect?
When can we stop testing?
When can we release the s/w?
What is the complexity of a module?
What is the module strength and coupling?

6. User Interface Responsible for all the interaction with users
Characteristics
Speed of learning – should be easy to learn
A- component based- similar to interface of other application
B- Use of metaphors and intuitive command names- speed of learning increases if the command names are based on day 2 day real life eg.

7. Speed of use- it is determined by the time and user effort necessary to initiate and execute different commands.
Speed of recall –
Error prevention- good interface should minimize the scope of committing errors while initiating different commands.
Attractiveness- A to use
Feed back- provide feedback to various user actions.
Support for multiple skills level- procedure for different categories of users.

8. Error recovery- allow user to undo a mistake
User guidelines and Online help

9. Types of user Interfaces
Command language Based- difficult to learn
Require user to memorize the set of commands
Menu Based-
(a) scrolling menu:
(b) Walking Menu:
(c) Hierarchical Menu:
Direct manipulation Interface

10. Software Configuration Management
Change Management more commonly called S/w configuration mgt. It is applied throughout the s/w process.
SCM activities are developed to (1 ) identify change, (2) control change, (3) Ensure that change is being properly implemented (4) report changes .

11. A SCM Scenario Project Manager: In charge of a s/w group
A configuration Manager: In charge of SCM Procedures and policies.
SE: Responsible for developing and maintaining the s/w product.
Customer: Who uses the product

12. Elements of a configuration Management System
Component elements- a set of tools coupled with file mgt (a Database) that enable access to s/w config item.
Process elements- a collection of procedures and tasks that define an effective approach to change management.
Construction elements- A set of tools that automate the construction of s/w by ensuring that the proper set of validated components.
Human elements- s/w team

13. Baselines
s/w configuration items- suite of test cases, or a named program component( function, java applet)
Before a s/w configuration items becomes a baselines, change may be made quickly and informally. However once the baseline is established , changes can be made but a specific formal procedure must be applied.

14. Once base line is established, it is copied from Database into engineers private work.

16. S/w configuration items

17. The SCM Repository

18. The SCM Process

19. What is reliability at the time of release?
Which test technique is more effective?
Do we have strong program or weak test suite?

20. Token count It is classified as either operators or operands.
Variable, constants- operands
+,-,/,*, while ,for, printf, eof
n=n1+n2
n= vocabulary of a program
n1= no of unique operators
n2= no of unique operands

21. Length of the program in terms of the total no of tokens
N=N1+N2
N1- Total occurrences of operator
N2- Total occurrences of operands
Volume- actual size of programs (bits)
V= N*log2n