1. An Evaluation Of Requirements Engineering Process Performance Measures POONAM SHARMA PARUL MATHUR ANIL BHALLA

2. INTRODUCTION POONAM SHARMA

4. Problem Stmt SRS Requirements Elicitation Requirements Analysis Requirements Documentation Requirements Review Reqt Engg

9. Admin Reservation Clerk Passenger Update Train Info Login View Reservation Status Reserve Seat Cancellations

10. Draw the context diagram Develop prototypes (optional) Model the requirements Finalize the requirements Requirement Analysis Steps

11. Requirements Documentation 1 Introduction 1.1 Purpose 1.2 Scope 1.3 Definitions, Acronyms & Abbreviations 1.4 References 1.5 Overview 2 The Overall Description 2.1 Product Perspective 2.2 Product Functions 2.3 User Characteristics 2.4 Assumptions & Dependencies 2.5 Constraints

12. Cont.. 3. Specific Requirements 3.1 External Interfaces 3.2 Performance Requirements 3.3 Logical Database Requirements 3.4 Design Constraints 3.5 Functions 3.6 Additional Comments 4. Change Management Process 5. Document Approvals 6. Supporting Information

13. Measure & Metrics Measure : A measure provides a quantitative indication of the extent, amount, dimension, capacity, or size of some attributes of a product or process Metrics : A quantitative measure of the degree to which a system, component, or process possesses a given attribute

14. METHODS OF REQUIREMENTS ENGINEERING PARUL MATHUR

19. This is not a line count, but a statement count. It is possible to put several statements on one line by using the colon ":" or writing single-line If..Then statements. Statements Two or more lines joined with the line continuation character "_" are counted as one logical line. Logical lines of code Counts lines but excludes empty lines and comments. Also referred as the source lines of code (sLOC) metric. Physical lines of code Counts physical lines, but excludes classic VB form definitions and attributes. Physical lines Counts all lines in source files. Simple line count Description Metric

20. } 18 return 0; 17 } 16 } 15 x[j]=save; 14 x[i]=x[j]; 13 save=x[i]; 12 { 11 if(x[i]<x[j]) 10 for(j=1;j<=im1;j++) 9 im1=i-1; 8 { 7 for(i=2;i<=n;i++) 6 if (n<2) return 1; 5 /*this function sort array x in ascending order*/ 4 int i, j, save, im1; 3 { 2 int sort(int x[],int n) 1

24. Weighting Factor 9 8 4 Interfaces 14 12 10 Files 9 7 3 Enquires 7 6 5 External Outputs 4 3 2 External Inputs Complex Average Simple Function Specifications

29. Evaluation Emphasis is more on quantity than quality Quality Depend on time & LOC Cost More time is required; depending upon functionality & complexity Time Dependent on system capabilities Functionality Effect Measure

30. METHODS OF REQUIREMENTS ENGINEERING ANIL BHALLA

31. Software Science Measures & Cyclomatic Complexity

33. Four scalar numbers derived directly from a program's source code Total number of operands N2 Total number of operators N1 Number of distinct operands n2 Number of distinct operators n1 Description Symbol

34. Five measures are derived E= D * V E Effort D= (n1/2) * (N2/n2) D Difficulty V= N * (LOG2 n) V Volume n= n1 + n2 n Program vocabulary N= N1 + N2 N Program length Formula Symbol Measure

38. Evaluation Cost will fluctuate Cost Depends on computational complexity Functionality Quality decreases upon increase in conditions Quality Time increases according to difficulty of program Time Effect Measures

42. Flow Chart 1 3 6 4 5 7 8 2 9 10 11

43. Flow Graph 1 2,3 6 7 8 9 10 4,5 11 Edges Nodes R1 R2 R3 R4 Regions

45. Evaluation Depends on time, quality & functionality of program Cost Provide basis for planning tests for program Functionality Gives logical complexity Quality Time required is more than size estimation Time Effect Measures

46. THANK YOU !!!

47. ANY QUERIES ??