Coupling Interaction: It occurs due to methods of a class invoking methods of other classes. Component Coupling: refers to interaction between two classes.

Slides:



Advertisements
Similar presentations
Configuration Management
Advertisements

System Integration Verification and Validation
Configuration Management Managing Change. Points to Ponder Which is more important?  stability  progress Why is change potentially dangerous?
Object-Oriented Analysis and Design
Object-Oriented Metrics. Characteristics of OO ● Localization ● Encapsulation ● Information hiding ● Inheritence ● Object abstraction.
Software Configuration Management
Software Metrics II Speaker: Jerry Gao Ph.D. San Jose State University URL: Sept., 2001.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Software Configuration Management (SCM)
Implementation. We we came from… Planning Analysis Design Implementation Identify Problem/Value. Feasibility Analysis. Project Management. Understand.
Software Process and Product Metrics
Introduction to Software Testing
Software Configuration Management
Design, goal of design, design process in SE context, Process of design – Quality guidelines and attributes Evolution of software design process – Procedural,
Effective Methods for Software and Systems Integration
Configuration Management Managing Change. Points to Ponder Which is more important?  stability  progress Why is change potentially dangerous?
Chapter 2 The process Process, Methods, and Tools
Component-level testing – Equivalence partitioning, boundary value analysis, path testing Navigation testing – Testing navigation syntax and semantics.
Software Configuration Management (SCM)
Software System Engineering: A tutorial
1 Software Quality CIS 375 Bruce R. Maxim UM-Dearborn.
Chapter 6 : Software Metrics
 To explain the importance of software configuration management (CM)  To describe key CM activities namely CM planning, change management, version management.
Configuration Management (managing change). Starter Questions... Which is more important?  stability  progress Why is change potentially dangerous?
Software Measurement & Metrics
This chapter is extracted from Sommerville’s slides. Text book chapter
Product Metrics An overview. What are metrics? “ A quantitative measure of the degree to which a system, component, or process possesses a given attribute.”
Moving into Implementation SYSTEMS ANALYSIS AND DESIGN, 6 TH EDITION DENNIS, WIXOM, AND ROTH © 2015 JOHN WILEY & SONS. ALL RIGHTS RESERVED.Roberta M. Roth.
SOFTWARE CONFIGURATION MANAGEMENT. Change is inevitable when computer software is built. And change increases the level of confusion among software engineers.
TESTING LEVELS Unit Testing Integration Testing System Testing Acceptance Testing.
Software Project Management
Configuration Management and Change Control Change is inevitable! So it has to be planned for and managed.
Chapter 5:User Interface Design Concepts Of UI Interface Model Internal an External Design Evaluation Interaction Information Display Software.
Configuration Management
Software Configuration Management
Software Configuration Management
Software Configuration Management
Software Project Configuration Management
Software Metrics 1.
Chapter 11: Software Configuration Management
Software Verification and Validation
Software Engineering (CSI 321)
Coupling and Cohesion 1.
System Design Ashima Wadhwa.
Software Life Cycle “What happens in the ‘life’ of software”
Configuration Management
Basic Concepts in Software Design
Unit 2 User Interface Design.
Maintaining software solutions
Chapter 27 Change Management
Lecture 3 Change Management
User Interface Design PPT By :Dr. R. Mall.
Software Engineering: A Practitioner’s Approach, 6/e Chapter 23 Estimation for Software Projects copyright © 1996, 2001, 2005 R.S. Pressman & Associates,
Configuration Management (managing change)
Software Configuration Management
Chapter 27 Change Management
Software engineering USER INTERFACE DESIGN.
Coupling and Cohesion By Bonnie Ngu.
Introduction to Software Testing
Chapter 27 Change Management
Software Architecture
Chapter 13 Quality Management
Chapter 11: Software Configuration Management
Software Engineering: A Practitioner’s Approach, 6/e Chapter 23 Estimation for Software Projects copyright © 1996, 2001, 2005 R.S. Pressman & Associates,
Chapter 27 Change Management
Proper functionality Good human computer interface Easy to maintain
Chapter 27 Change Management
Configuration management
Chapter 26 Estimation for Software Projects.
Software Configuration Management
Presentation transcript:

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.

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.

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.

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?

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.

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.

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

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

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 .

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

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

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.

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

S/w configuration items

The SCM Repository

The SCM Process

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

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

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