
Functional Software Size Measurement Methodology with Effort Estimation and Performance Indication
Description
Alles über E-Books | Antworten auf Fragen rund um E-Books, Kopierschutz und Dateiformate finden Sie in unserem Info- & Hilfebereich.
More details
Other editions
Additional editions


Person
Content
Preface xi
Acknowledgments xv
About the Author xvii
List of Acronyms xix
About the Companion Websites xxv
Part One FSSM: Introduction
1 Introduction to Functional Software Size Measurement 3
1.1 Introduction 3
1.2 Functional Size Measurement and Effort Estimation 3
1.3 Important Considerations for the Software Size Measurement and Effort Estimation 4
1.4 Introduction to the Functional Software Size Measurement Methodology with Effort Estimation and Performance Indication (FSSM) 10
1.5 Chapter Summary 12
Exercises 13
2 Synopsis of the Functional Software Size Measurement Methodology with Effort Estimation and Performance Indication (FSSM) 15
2.1 Salient Characteristics of the FSSM 15
2.2 Distinguishing Unique Key Features of the FSSM 20
2.3 Synoptic Description of the FSSM 22
2.4 Lists and Brief Descriptions of the FSSM Constituents 36
2.5 Source of Information for the FSSM Constituents 46
2.6 Examples 47
2.7 Chapter Summary 49
Exercises 49
Part Two FSSM: Software View
3 Software's Measurable Components in the FSSM 53
3.1 Software's Measurable Component (SMC) Description 53
3.2 Software's Measurable Components (SMCs) Characteristics 56
3.3 Software's Measurable Components (SMCs) Presence and Size 56
3.4 Examples 57
3.5 Chapter Summary 57
Exercises 58
4 Software Component's Measurable Features in the FSSM 59
4.1 Software Component's Measurable Feature (SCMF) Description 59
4.2 Usage of the Software Component's Measurable Features (SCMFs) 71
4.3 Software Component's Measurable Features (SCMFs) Presence and Quantity 72
4.4 Examples 72
4.5 Chapter Summary 74
Exercises 75
Part Three FSSM: Measurements
5 Software Component's Feature Points in the FSSM 79
5.1 Software Component's Feature Point (SCFP) Description 79
5.2 Usage of the Software Component's Feature Points (SCFPs) 92
5.3 Software Component's Feature Points (SCFPs) Presence and Quantity 92
5.4 Examples 93
5.5 Chapter Summary 95
Exercises 96
6 Software Component's Feature Point Counts in the FSSM 97
6.1 Software Component's Feature Point Count (SCFPC) Description 97
6.2 Counting Guidelines Flowchart for the Software Component's Measurable Features (SCMFs) of the Software's Measurable Component 'Functionality Execution' (CFE) 105
6.3 Some Specific Guidelines for the Software Component's Feature Point (SCFP) Counting 105
6.4 Software Component's Feature Point Counts (SCFPCs) Formation 110
6.5 Usage of the Software Component's Feature Point Counts (SCFPCs) 110
6.6 Software Component's Feature Point Counts (SCFPCs) Value 112
6.7 Examples 112
6.8 Chapter Summary 113
Exercises 114
7 Software Component's Measurements through Software Component's Feature Measurements in the FSSM 116
7.1 Software Component's Measurement (SCM) and Software Component's Feature Measurement (SCFM) Description 116
7.2 Software Component's Measurement (SCM) and Software Component's Feature Measurement (SCFM) Formulae 123
7.3 Examples 130
7.4 Chapter Summary 131
Exercises 133
Part Four FSSM: Estimations and Indications
8 Software Size Determination and Effort Estimations in the FSSM 137
8.1 Software Analysis - Size Determination and Effort Estimation, Static Structure, and Dynamic Characteristics in the FSSM 137
8.2 Software Size and Effort Estimation (SSEE) Description 138
8.3 Software Size and Effort Estimation (SSEE) Formulae 143
8.4 Chapter Summary 150
Exercises 152
9 Software Performance Quality Indicators for Static Structure and Dynamic Characteristics in the FSSM 153
9.1 Software Performance Quality Indicator (SPQI) Description 153
9.2 Software Performance Quality Indicator (SPQI) Construction Information Source 164
9.3 Software Performance Quality Indicator (SPQI) Formulae 165
9.4 Examples 183
9.5 Chapter Summary 183
Exercises 187
Part Five FSSM: Summary Charts
10 Summary Charts of the FSSM 191
10.1 Summary Charts of the FSSM Constituents 191
10.2 Chapter Summary 206
Part Six FSSM: Strengths
11 Software Diagnostics Based on the Software Component's Feature Measurements and Software Performance Quality Indicators in the FSSM 209
11.1 Basic Diagnostics About the Functional Requirements Specifications (FRS) and Software, Based on the Software Component's Feature Measurements (SCFMs) 209
11.2 Advanced Diagnostics About the System Architecture, Functional Requirements Specifications (FRS), and Software, Based on the Software Performance Quality Indicators (SPQIs) 214
11.3 Chapter Summary 216
12 Convertibility and ISO/IEC Standards Compliance of the FSSM 217
12.1 Convertibility of the FSSM to Other Functional Size Measurement (FSM) Methodology COSMIC 217
12.2 ISO/IEC Standards Compliance of the FSSM 218
12.3 Chapter Summary 225
13 Significant Strengths of the FSSM 226
13.1 Coverage Capabilities of the FSSM in Comparison with Some Existing Software Size Measurement Methodologies 226
13.2 Advantages of the FSSM Over the Currently Available Methodologies 231
13.3 Examples 239
13.4 Chapter Summary 241
Part Seven FSSM: Usage - Example
14 Example for Using the FSSM 247
14.1 Mini-FSSM Application Software Development (ASD) Introduction 247
14.2 Functional Requirements Specifications (FRS) of the Example - 'Mini-FSSM Application Software Development' 248
14.3 Software Component's Feature Point (SCFP) Counting Explanation for the Example Mini-FSSM ASD 260
14.4 Software Component's Feature Point (SCFP) Counting and Software Component's Feature Point Count (SCFPC) Formation Table for the Example Mini-FSSM ASD 289
14.5 FSSM Results Tables for the Software Example Mini-FSSM Application Software Development 289
14.6 Graphical Representation of the Final Output Results for the Example Mini-FSSM 305
14.7 Chapter Summary 306
Part Eight Concluding Information
15 Effort Estimate for the Usage of the FSSM 313
15.1 Software Component's Feature Point (SCFP) Counting, Analysis, and Report Preparation Effort Estimate for the Usage of the FSSM 313
15.2 Chapter Summary 315
16 Known Limitations, Improvement Scope, and Conclusion 316
16.1 Known Limitations of the FSSM 316
16.2 Improvement Possibilities in the FSSM 316
16.3 Conclusion 317
16.4 Chapter Summary 318
Part Nine Glossary
17 Glossary 321
17.1 Terms and Their Significance 321
Part Ten List of Figures and Answers to Exercises
18 List of Figures 393
19 Answers to Exercises 395
19.1 Chapter 1 Exercises 395
19.2 Chapter 2 Exercises 395
19.3 Chapter 3 Exercises 395
19.4 Chapter 4 Exercises 396
19.5 Chapter 5 Exercises 396
19.6 Chapter 6 Exercises 396
19.7 Chapter 7 Exercises 396
19.8 Chapter 8 Exercises 396
19.9 Chapter 9 Exercises 396
References 397
Index 399
Preface
Prelude
Software Size Measurement is an extremely important and highly specialized part of the software life cycle. It is needed for determining the effort and cost estimations for project planning purposes of the software projects' execution, and/or for other costing/charging/productivity analysis purposes of the software projects. The software size measurement part has not received proper attention and has been neglected till now as it is well known that many software projects exceed their allocated budget limits because the currently available methodologies for software size measurement present many areas for improvements whereby better and more accurate estimations for effort can be obtained. These methodologies measure only a very limited part of the software to determine the complete software's size which is an inaccurate way for the measurement of most of the software applications because of the reasons explained later in the book.
The available standards in this area, for example, ISO/IEC 14143-1[1], ISO/IEC 14143-2[2], do not specify what the constituents of the software are, which need to be measured. So it is left to the methodologies what to measure.
Project leaders and project managers depend on the size measurement specialists for measuring the software size. Specialists measure the size based on the current techniques. Then, various multiplier factors depending on the environmental factors such as the area of application software and assumptions about the complexity of the software are used to expand the size of the remaining unmeasured parts to get the complete software size in order to include the size of the parts missing in the measurements. Using non-specific multipliers would result in an assumed measurement size for the project. Project leaders, project managers, and specialists are aware of these facts but are obliged to continue using these measurements because no other thorough technique is available.
The new software size measurement methodology presented in this book, "Functional Software Size Measurement Methodology with Effort Estimation and Performance Indication (FSSM)", overcomes these deficiencies, and is a comprehensive, elaborate, and complete software Functional Size Measurement[1] methodology, which can help enterprises to estimate the size and required effort for all their software projects developed in High Level Languages, quite accurately. Hence, these projects can be completed within the defined budget limits because of accurate estimations obtained by using the detailed and complete approach of the FSSM.
Software Size Measurement
"Functional Size Measurement (FSM)"[1] is a very effective method to measure the software "size in terms of the functions required by the user"[1] in which the functional "size of the software derived by quantifying the Functional User Requirements (FUR)"[1] is measured. Extra care should be taken to select a specific FSM[1] method. A method which measures only very few of the various types of functions available in the software should not be selected but one which measures all the important types of functions should be selected, for the reasons explained later in the book. Many currently available, popular FSM[1] methodologies can be improved in this respect. The most desired improvement would be to increase the coverage of the measurement regarding the number of the measured type of functions. The very small number of the type of functions measured - a small subset of the complete set of various available types of measurable functions - should be increased to a more extensive functional range.
Software consists of several constituent parts or components which can be named as "Base Functional Components (BFCs)"[1]. These components have no fixed proportional relationships amongst themselves or with respect to the complete software concerning their size in different applications or in the sub-programs (modules) of the same application. Moreover, the BFCs[1] have sub-types which are called "BFC Type"[1]. Most of these sub-types have no fixed proportional relationships amongst themselves for a particular BFC[1] or with the sub-types of other BFCs[1] regarding their size. Therefore, if only one or a few BFC types[1] of one or a few BFCs[1] are measured - so only a partial measurement - the size of the other remaining sub-types and components cannot be determined correctly based on this aforementioned measured part and some multiplication factors. However, this is how the current software sizing methodologies approach the estimation.
About the Book
Software has become so ubiquitous that the importance of the software projects and their timely completion cannot be overlooked. Timely completion is dependent on correct planning which requires realistic effort estimates. Effort estimates can be realistic only if accurate and complete software size measurements are available.
Many medium- and big-sized software projects are unable to be completed within the planned limits of time, money, and resources. This book pinpoints one of the major, originating, basic root causes of the erroneous planning by disclosing the hidden errors that are made in the software size measurement, and consequently in the effort estimates and project planning. It then reveals the simple and correct manner of accurate software size measurement whereby realistic effort estimates can be obtained based on which precise project planning can be done, and successful execution of the projects can be achieved within the planned limits.
The "Functional Software Size Measurement Methodology with Effort Estimation and Performance Indication (FSSM)" presented in this book provides comprehensive and precise measurements of the complete software whereby factual software size determination, development effort estimation, and performance indications are obtained. The methodology is elaborate, effective, and accurate for software size measurement and development effort estimation. Consequently, misconstrued project planning of the software projects can be avoided.
All the major, relevant, and important aspects of the software size measurement are taken into consideration in the FSSM and are presented to the reader. They are the software's measurable components, software component's measurable features, software component's feature points, software component's feature point counts, software component's feature measurements, software component's measurements, software size and effort estimations, and software performance quality indicators. Also included are a worked-out example with counting table, explanation, and results; software diagnostics based on the software component's feature measurements and software performance quality indicators; comparison with and advantages over some of the currently available methodologies; convertibility to another FSM[1] methodology; effort estimation for applying the FSSM methodology; and details of the full compliance with the ISO/IEC 14143-1[1] standards.
The book is destined and recommended for all the management/software professionals/students, and those interested in the field of software size measurement. It is intended to be used as a text book for the full or part of the advanced, specialized course of "Software Size Measurement" at the level of Master of Technology/Engineering/Science in the curriculum of the Computer Science/Engineering/Technology courses.
It is recommended that the reader already has some exposure to the software concepts/architecture from the point of view of applications, requirements, analysis, design, coding, and testing; DBMS, object-oriented technology; and acquaintance with the existing software size measurement/estimation techniques such as COSMIC[3] and IFPUG[4].
The book comprises:
- Introduction to Functional Software Size Measurement;
- Synopsis of the Functional Software Size Measurement Methodology with Effort Estimation and Performance Indication;
- Software's Measurable Components;
- Software Component's Measurable Features;
- Software Component's Feature Points;
- Software Component's Feature Point Counts;
- Software Component's Measurements through Software Component's Feature Measurements;
- Software Size Determination and Effort Estimations;
- Software Performance Quality Indicators for Static Structure and Dynamic Characteristics;
- Summary Charts;
- Software Diagnostics;
- Convertibility and ISO/IEC Standards Compliance;
- Strengths and Comparison: Methodology Coverage and Advantages;
- A Worked-Out Example with Functional Requirements Specifications, Counting Table and Explanations, and Results;
- Methodology Usage Effort;
- Examples, Exercises, and Glossary.
The presentation of the contents of FSSM is organized in the chapters in the following manner:
- Distinct parts of group of chapters:
- The book is divided into distinct parts of groups of chapters. The chapters in a group are related and linked amongst themselves. The parts follow a pattern of flow of information convenient for understanding.
- Flow of information in the chapter contents:
- The sequence of chapters with respect to their contents follows an orderly flow according to the flow scheme of proceedings...
System requirements
File format: ePUB
Copy protection: Adobe-DRM (Digital Rights Management)
System requirements:
- Computer (Windows; MacOS X; Linux): Install the free reader Adobe Digital Editions prior to download (see eBook Help).
- Tablet/smartphone (Android; iOS): Install the free app Adobe Digital Editions or the app PocketBook before downloading (see eBook Help).
- E-reader: Bookeen, Kobo, Pocketbook, Sony, Tolino and many more (not Kindle).
The file format ePub works well for novels and non-fiction books – i.e., „flowing” text without complex layout. On an e-reader or smartphone, line and page breaks automatically adjust to fit the small displays.
This eBook uses Adobe-DRM, a „hard” copy protection. If the necessary requirements are not met, unfortunately you will not be able to open the eBook. You will therefore need to prepare your reading hardware before downloading.
Please note: We strongly recommend that you authorise using your personal Adobe ID after installation of any reading software.
For more information, see our ebook Help page.