GLOSSARY OF TERMS For SOFTWARE PROJECT DEVELOPMENT AND ENHANCEMENT - ISBSG
International Software BenchmarkingStandards GroupGLOSSARY OF TERMSforSOFTWARE PROJECTDEVELOPMENT AND ENHANCEMENTGlossary of Terms D&E V5.17.doc (18/11/2018)
ISBSG Glossary of Terms for Development & Enhancement (version 5.17)Table of ContentsIntroduction . 3CONTEXT . 3PURPOSE OF DOCUMENT . 3Part A: Terms . 4ACTIVITY . 4ADJUSTED FUNCTION POINTS (AFP) . 4APPLICATION GROUP . 4APPLICATION TYPE. 4ARCHITECTURE . 7BUSINESS AREA TYPE . 7CASE (COMPUTER AIDED SOFTWARE ENGINEERING) . 7CLIENT ROLES . 8CLIENT SERVER . 8CLIENT/SERVER DESCRIPTION . 8COST . 8COUNT APPROACH . 8DATA QUALITY RATING . 9DEFECT . 9DEGREE OF CONFIDENCE . 10DEGREE OF CUSTOMISATION . 10DEVELOPMENT METHODOLOGY. 10DEVELOPMENT PLATFORM . 10DEVELOPMENT TECHNIQUE . 10DEVELOPMENT TYPE . 10FUNCTIONAL SIZE . 11FUNCTIONAL SIZE MEASUREMENT (FSM) . 11FUNCTIONAL SIZE UNIT (FSU) . 11FUNCTIONAL SIZING TECHNIQUE . 11IMPLEMENTATION DATE. 11INTENDED MARKET . 12LANGUAGE TYPE. 12LIFE CYCLE ACTIVITIES. 12MAXIMUM TEAM SIZE. 12METHODOLOGY USED . 12METHODOLOGY ACQUISITION . 12 International Software Benchmarking Standards GroupPage: 1
ISBSG Glossary of Terms for Development & Enhancement (version 5.17)NORMALISED WORK EFFORT . 12ORGANISATION TYPE . 12PACKAGED SOFTWARE CUSTOMISATION . 13PRIMARY PROGRAMMING LANGUAGE . 13PRODUCTIVITY . 13PROJECT . 13PROJECT ACTIVITY SCOPE . 13PROJECT EFFORT BREAKDOWN . 13PROJECT ELAPSED TIME . 15PROJECT ID. 15PROJECT INACTIVE TIME. 15PROJECT LIFE CYCLE. 15PROJECT WORK EFFORT . 15RATING . 15REUSABLE / CUSTOM CRITERIA . 15SOFTWARE SIZE . 16SERVER ROLES . 16STAGED DEVELOPMENT . 16SUMMARY WORK EFFORT . 16TARGET PLATFORM . 16TASK . 17TIME RECORDING METHODS . 17TYPE OF SERVER . 17UNADJUSTED FIUNCTION POINT RATING . 17UNRECORDED EFFORT. 17USER BASE . 18VALUE ADJUSTMENT FACTOR (VAF) . 18WEB DEVELOPMENT . 18WORK EFFORT BREAKDOWN . 18Part B: Metrics . 20DEFECT DENSITY . 20MANPOWER DELIVERY RATE . 20PROJECT DELIVERY RATE, (PDR). . 20SPEED OF DELIVERY . 20 International Software Benchmarking Standards GroupPage: 2
ISBSG Glossary of Terms for Development & Enhancement (version 5.17)IntroductionCONTEXTWhen the International Software Benchmarking Standards Group was formed in 1994, one of theobjectives written into the original Charter was:“To develop the profession of software measurement by establishing a common vocabulary andunderstanding of terms.”Consistent with this objective, the ISBSG has defined terms and metrics for the purposes of: assisting in the collection of project data into the Repository standardising the way the collected data is analysed and reportedWhat follows is a consolidated list of ISBSG definitions and terms used. We hope this will helpus to meet our Charter. We would appreciate any comments you may have to assist us inmeeting this objective.PURPOSE OF DOCUMENTThis document provides definitions of terms used in ISBSG documents. This includes ProjectData collection forms, publications and data releases. Some of these terms refer to items nolonger collected by the ISBSG but which may be found in documents or analysis of earlier data.Where appropriate these definitions have been adjusted to align with international standards:ISO/IEC 14143-1:1998 Information technology -- Software measurement -- Functional size measurement -- Part 1: Definition of conceptsISO/IEC 20926:2003 Software engineering -- IFPUG 4.1 Unadjusted functional size measurement method -- Counting practices manualISO/IEC 20968:2002 Software engineering -- Mk II Function Point Analysis -- Counting Practices ManualISO/IEC 24765, Software and Systems Engineering VocabularyThe Glossary is divided into two parts:Part A TermsPart B Metrics International Software Benchmarking Standards GroupPage: 3
ISBSG Glossary of Terms for Development & Enhancement (version 5.17)Part A: TermsACTIVITYRefers to the 6 types of work undertaken during software development and maintenance, namely:Plan, Specify, Design, Build, Test, and ImplementIn earlier ISBSG publications these activities were frequently referred to as phases. For thecontents of these activities see PROJECT EFFORT BREAKDOWN.ADJUSTED FUNCTION POINTS (AFP)A software size based on the functional size multiplied by the technical complexity adjustment.The resultant adjusted size is reported in adjusted function points (AFP) and applies to IFPUG,FiSMA, NESMA and MARK II Functional Size Measurement methods.APPLICATION GROUPThe application group defines the purpose of the software. The four application groups are:Business ApplicationSoftware that can enable a computer to be used to perform practical business operations ordecision making. ‘Business’ may encompass activities in the public and/or private sectors.Real Time ApplicationChanges Software that may gather data and control other software or hardware devices. This isall subject to specific timing constraints for the required responses to events.Mathematically Intensive ApplicationSoftware with processing logic that is dominated by mathematical operations. Examples includemathematically intensive, scientific or engineering computations, processing of audio/videoimages.Infrastructure SoftwareSoftware that enables application software to execute on computer hardware. Infrastructuresoftware typically executes in one or more layers of a software architecture between theapplication software layer and the hardware. Examples include operating system software,middleware, device drivers, dbms, word-processing/spreadsheet software.APPLICATION TY PEHow the application is meeting the business area requirements. Classification of an applicationas a type is according to its primary intended use. Application types are grouped in the following4 categories: Business Applications, Real-Time Applications, Mathematically-IntensiveApplications, and Infrastructure Software. International Software Benchmarking Standards GroupPage: 4
ISBSG Glossary of Terms for Development & Enhancement (version 5.17)Business Applications:Catalogue or register of things or eventsCustomer billingCustomer relationship managementData warehouse systemDecision SupportThese are interactive information systems that employ database technology to support “what if”scenario testing. These applications are primarily used by middle managers to provide them withinformation, which is tailored to support semi-structured and unstructured decisions. Theseapplications provide the user with ad-hoc, interactive reporting which is based upon an analyticalmodel that is continually refined in order to solve business problems, e.g. share portfoliomanagement.Document managementElectronic Data InterchangeThe transmission of business data and documents between organisations or hardware using anOSI protocol.Executive Information SystemThese systems commonly answer a query by combining information from both internal andexternal databases. The information is required by top executives to identify problems,opportunities, planning and critical success factor information for the company.Financial transaction process & accountingJob, case, incident, project managementLogistic or supply planning & controlManagement Information SystemProvides users with predefined management reports via a reporting system where the user selectsthe criteria from a limited selection and can usually store the criteria. The report informationassists with performance management of a department or business.Management or performance reportingOffice Information SystemThese combine text processing, image processing, telecommunications and other technologies todevelop computer-based information systems that collect, process, store and transmit informationin the form of electronic office communications, e.g. Word processing, electronic mail, desktoppublishing, voice mail, teleconferencing, facsimile and image processing. International Software Benchmarking Standards GroupPage: 5
ISBSG Glossary of Terms for Development & Enhancement (version 5.17)Online analysis and reportingReservation system (e.g. airline, hotel)Stock control & order processingTradingTransaction/production systemThese systems can be batch or on-line and process business transactions in a logical sequencewithin a business area. The system consists of a set of inputs to which the transaction/productionsystem adds value and outputs customer or corporate requirements. Examples include: payroll,order entry/processing, general ledger, inventory and case management.Workflow support & managementReal-Time Applications:Automatic Data LoggingEmbedded software for simple device controlCommand & control system (e.g. military, air traffic, police)Complex process control (e.g. oil refinery, steel manufacture)Systems that make routine decisions to control operational processes by automatically adjustingphysical processes. The software is written for the purpose of controlling, monitoring ormanipulating devices such as instruments, e.g. temperature control, manufacturing processcontrol, device or instrument control.Fault ToleranceA continuously available hardware platform and operating system for critical on-lineapplications. These systems are able to continue running even when errors are occurring. Thefoundation of the continuous processing is hardware-based fault tolerance, achieved through:1. Self checking logic on each major circuit board to detect failures2. Duplicate boards to continue processing in the event of board failure3. Hardware components can be upgraded on-line without interruptionsUsed for specialised application in telecommunications and retail, travel, banking etc.Robot controlTelecom & network managementSoftware, which monitors and reports on the status of all components of telecommunicationnetworks including communication links and nodes.Transportation control (includes avionics, signalling) International Software Benchmarking Standards GroupPage: 6
ISBSG Glossary of Terms for Development & Enhancement (version 5.17)Mathematically-Intensive Applications:3D modelling or animationArtificial IntelligenceUsed to solve a particular problem by modelling the skill, judgement and expertise of humanbeings in solving problems in a particular domain. This includes knowledge based systemsartificial neural network technology and natural language systems.Geographic or spatial information systemImage, video or sound processingMathematical modellingScientific/ engineering applicationStatistical analysisInfrastructure Software:Data or database managementDevice or interface driverGraphics & publishing tools or systemOperating system or software utilityPersonal productivity (e.g. word processor, spreadsheet)Software development toolARCHITECTUREThe organisational structure of a system and its implementation guidelines. This derived attributefor the project indicates if the application is Stand alone, Multi-tier, Client server, or Multi-tierwith web public interface.BUSINESS AREA TYPEThe business area within the organisation that the application will be supporting.CASE (COMPUTER AIDED SOFTWARE ENGINEERING)The use of computer software to assist in completing tasks defined within a systems developmentlife cycle methodology.CASE may be used across the entire project life cycle or used to assist with specific parts of thecycle. The three categories are: International Software Benchmarking Standards GroupPage: 7
ISBSG Glossary of Terms for Development & Enhancement (version 5.17)Upper CASEEnvironment independent and generally used to perform analysis, e.g. logical data modelling,process modelling, data flow diagramming etc.Lower CASEEnvironment dependent and generally used to assist in physical design and construction ofsoftware, e.g. physical data base design, code generation etc.Integrated CASEFully integrating upper and lower CASE, e.g. logical models are converted to physical models,which in turn generate database tables and code.OtherAny not specified by the above definitions.CLIENT ROLESThe roles performed by the computers that provide interface to the software’s external users.CLIENT SERVERIndicator of whether the application or product requires more than one computer to operatedifferent components or parts of it.CLIENT/SERVER DESCRIPTIONA description of the architecture of the client/server software application or product.COSTThe price paid, (either through money, time or labour, etc.), to acquire, produce, accomplish ormaintain the product. The following methods of collecting COST are believed to be the mostcommon:Cost RecordedThe daily recording of all COST incurred by each person on project related tasks.Cost DerivedIt is possible to derive the COST where it has not been collected on a daily basis as in COSTRECORDED.COUNT APPROACHA description of the method used to size the project software. For most projects in the ISBSGrepository this is the Functional Size Measurement Method (FSM Method) used to measure thefunctional size (e.g. IFPUG, MARK II, NESMA, COSMIC, FiSMA etc.). For projects usingOther Size Measures (e.g. LOC etc.) this is a short name for that method, and in data releases thesize data is not included with sizes measured by an FSM Method but rather is in a section “SizeOther than FSM”. International Software Benchmarking Standards GroupPage: 8
ISBSG Glossary of Terms for Development & Enhancement (version 5.17)Where the Functional Size Measurement Method is IFPUG and the count standard is lower thanIFPUG 4 this is indicated by IFPUG ( 4), where the count standard is IFPUG 4 or higher this isindicated by IFPUG (4).DATA QUALITY RATINGThis field contains an ISBSG rating code of A, B, C or D applied to the project data by theISBSG quality reviewers to denote the following:A The data submitted was assessed as being sound with nothing being identified thatmight affect its integrityB The submission appears fundamentally sound but there are some factors which couldaffect the integrity of the submitted dataC Due to significant data not being provided, it was not possible to assess the integrityof the submitted dataD Due to one factor or a combination of factors, little credibility should be given to thesubmitted dataDEFECTA problem, which if not corrected, could cause an application to either fail or to produceincorrect results. There can be three categories:Minor DefectA minor defect does not make the application unusable in any way, (e.g. a modification isrequired to a screen field or report).Major DefectA major defect causes part of the application to become unusable.Extreme DefectA failure of some part of an application that causes the application to become totally unusable.The following information has been collected in relation to application defects both within theproject duration (defects and hours per project activity), and after implementation (defects foundwithin the first month of use of the software). Of the following only Defect Found and Repair &Rework Hours per project activity are currently collected:Defect FoundThe number of defects detected in the process in that particular Effort Breakdown orfound within the first month of use of the software after implementation.Defect OriginatingThe number of defects put into the process in that particular Effort Breakdown only.Defect Removed International Software Benchmarking Standards GroupPage: 9
ISBSG Glossary of Terms for Development & Enhancement (version 5.17)The number of defects removed from the process in that particular Effort Breakdown.Repair HoursThe effort in hours taken to correct defects detected in that particular Effort Breakdown.Rework HoursThe effort in hours taken in that particular Effort Breakdown after correction of defects,to return the project to point reached before defect detection.DEGREE OF CONFIDENCEAn expression of the confidence the organisation has in the data provided, expressed in a range 1- 4:1 not confident2 slightly confident3 confident4 very confidentDEGREE OF CUSTOMISATIONHow much customisation was involved, if the project was based on a packaged softwarecustomisation.DEVELOPMENT METHODOLOGYMethodologies used during development. For ISBSG purposes a development methodologyapplies to the whole project development process. This is distinct from development techniques,which apply to activities within the development process.DEVELOPMENT PLATFORMDefines the primary software development platform, (as determined by the operating systemused). Each project is classified as: PC, Mid Range, Main Frame or Multi platform.DEVELOPMENT TECHNIQUETechniques used during development. For ISBSG purposes a development technique applies toindividual activities within the development process. This is distinct from developmentmethodologies, which apply to the whole project development process.DEVELOPMENT TYPENew DevelopmentFull analysis of the application area is performed, followed by the complete development lifecycle, (planning or feasibility, analysis, design, construction and implementation). Examples are: International Software Benchmarking Standards GroupPage: 10
ISBSG Glossary of Terms for Development & Enhancement (version 5.17)1. A project that delivers new function to the business or client. The project addressesan area of business, (or provides a new utility), which has not been addressed before.2. Total replacement of an existing system with inclusion of new functionality.EnhancementChanges made to an existing application where new functionality has been added, or existingfunctionality has been changed or deleted. This would include adding a module to an existingapplication, irrespective of whether any of the existing functionality is changed or deleted.Re-developmentThe re-development of an existing application. The functional requirements of the applicationare known and will require minimum or no change. Re-development may involve a change toeither the hardware or software platform. Automated tools may be used to generate theapplication.This includes a project to re-structure or re-engineer an application to improve efficiency on thesame hardware or software platform. For re-development, normally only technical analysis isrequired.OtherAny other type of software development not specified above.FUNCTIONAL SIZEA size of the software derived by quantifying the Functional User Requirements (i.e., whatfunctions the software must support). This excludes Quality and Technical Requirements. Thismay be reported in different units depending on the Functional Size Measurement Method (e.g.UFP for IFPUG and NESMA, CFP for COSMIC etc.).FUNCTIONAL SIZE MEASUREMENT (FSM)The process of measuring functional size. Internationally recognised Functional Sizing Methodsinclude: IFPUG, MARK II, NESMA, COSMIC etc.FUNCTIONAL SIZE UNIT (FSU)The unit of measure of size used by a functional size measurement method. (e.g. Function Points)FUNCTIONAL SIZING TECHNIQUEThe technology used to support the functional sizing process. Certain technologies used infunction point counting can impact on the count’s potential accuracy.IMPLEMENTATION DATEThe date when the work product is delivered, (i.e. the project software is placed in production, orthe project deliverable is delivered). N.B. this is not necessarily the same as Project End Date.If the project had multiple implementations, this is the date of the first or principalimplementation. International Software Benchmarking Standards GroupPage: 11
ISBSG Glossary of Terms for Development & Enhancement (version 5.17)INTENDED MARKETThis describes the relationship between the project’s customer, end users and development team.LANGUAGE TYPEDefines the language type used for the project: e.g. 3GL, 4GL, Application Generator etc.LIFE CYCLE ACTIVITIESUsed in the context of the time at which functional sizing is carried out, (see also PROJECTEFFORT BREAKDOWN)Early life cycleUp to the completion of the system requirements definition.Mid life cycleFrom requirements definition to completion of the technical design.Late life cycleFrom technical design specification until after implementation.MAXIMUM TEAM SIZEThe maximum number of people during each component of the work breakdown who aresimultaneously assigned to work full-time on the project for at least one elapsed month.METHODOLOGY USEDWhether a development methodology was used by the development team to build the software.METHODOLOGY ACQUISITIONDescribes whether the development methodology (if used) was purchased or developed in-house,or a combination of these.NON-FUNCTIONAL SIZEA size of the non-functional aspects of the product developed or enhanced by the project.NORMALISED WORK EFFORTFor projects covering less than a full software development life-cycle, this value is an estimate ofthe full development life-cycle effort. For projects covering the full development life-cycle, andprojects where development life-cycle coverage is not known, this value is the same as SummaryWork Effort.ORGANISATION TYPEA standard classification for the business within which the organisation as a whole operates.Note: The organisation is that for which the project has been developed. International Software Benchmarking Standards GroupPage: 12
ISBSG Glossary of Terms for Development & Enhancement (version 5.17)PACKAGED SOFTWARE CUSTOMISATIONWhere a decision is made to acquire an existing product to provide the major component of therequired functionality. Note: Count only the functionality required by the client.PRIMARY PROGRAMMING LANGUAGEThe primary language used for the software development: JAVA, C , PL/1, Natural, Cobol etc.PRODUCTIVITYThe ratio of work product to work effort. In ISBSG documents and products this is given byProject Delivery Rate (see entry in Metrics section).PROJECTA collection of work tasks with a time frame and a work product to be delivered. In ISBSGdocuments and products the work product delivered is software and its documentation.Project Start (Project Start Date)A client/management decision is made formally/informally to involve Information Technologypersonnel in the development. This point is commonly known as the commencement of the'Survey', 'Feasibility Study' or 'Project Initiation' of the system development life cycle.Project End (Project End Date)The date when all work effort on the project ceased, and any remaining tasks (e.g. user support)was transferred to another organisation. In a full project life-cycle this would be the end date ofimplementation activities.PROJECT ACTIVITY SCOPESynonymous with the Project Effort Breakdown.PROJECT EFFORT BREAKDOWNProject effort is sub-divided in two ways: by project activity and by role of the groups of peopleinvolved. For the breakdown by person role see WORK EFFORT BREAKDOWN. See alsoLIFE CYCLE ACTIVITIES. Project management is assumed included in the effort of each ofthe following activities. The following table shows the major components of each activity.Project ActivityPlanPossible Activity ComponentsPreliminary InvestigationsOverall Project PlanningFeasibility StudyCost Benefit StudyProject Initiation ReportTerms of ReferenceSpecifySystems AnalysisRequirements Specification International Software Benchmarking Standards GroupPage: 13
ISBSG Glossary of Terms for Development & Enhancement (version 5.17)Review & Rework Requirements Spec.Architecture Design/SpecificationReview & Rework Architecture SpecFunctional / External DesignDesignCreate Physical / Internal Design(s)Review and Rework Design(s)Package SelectionBuildConstruct Code & Program SoftwareReview or Inspect & Rework CodePackage customisation / interfacesUnit TestIntegrate SoftwarePlan System or Performance TestingTestSystem TestingPerformance TestingCreate & Run Automated TestsAcceptance TestingImplementPrepare Releases for DeliveryInstall Software Releases for UsersPrepare User DocumentationPrepare & Deliver User TrainingProvide User SupportThe follow
Glossary of Terms D&E V5.17.doc (18/11/2018) International Software Benchmarking Standards Group GLOSSARY OF TERMS for SOFTWARE PROJECT DEVELOPMENT AND ENHANCEMENT
Bruksanvisning för bilstereo . Bruksanvisning for bilstereo . Instrukcja obsługi samochodowego odtwarzacza stereo . Operating Instructions for Car Stereo . 610-104 . SV . Bruksanvisning i original
10 tips och tricks för att lyckas med ert sap-projekt 20 SAPSANYTT 2/2015 De flesta projektledare känner säkert till Cobb’s paradox. Martin Cobb verkade som CIO för sekretariatet för Treasury Board of Canada 1995 då han ställde frågan
service i Norge och Finland drivs inom ramen för ett enskilt företag (NRK. 1 och Yleisradio), fin ns det i Sverige tre: Ett för tv (Sveriges Television , SVT ), ett för radio (Sveriges Radio , SR ) och ett för utbildnings program (Sveriges Utbildningsradio, UR, vilket till följd av sin begränsade storlek inte återfinns bland de 25 största
Hotell För hotell anges de tre klasserna A/B, C och D. Det betyder att den "normala" standarden C är acceptabel men att motiven för en högre standard är starka. Ljudklass C motsvarar de tidigare normkraven för hotell, ljudklass A/B motsvarar kraven för moderna hotell med hög standard och ljudklass D kan användas vid
LÄS NOGGRANT FÖLJANDE VILLKOR FÖR APPLE DEVELOPER PROGRAM LICENCE . Apple Developer Program License Agreement Syfte Du vill använda Apple-mjukvara (enligt definitionen nedan) för att utveckla en eller flera Applikationer (enligt definitionen nedan) för Apple-märkta produkter. . Applikationer som utvecklas för iOS-produkter, Apple .
ITIL Glossary of Terms, Definitions and Acronyms in Hungarian, V3.1.24.h2.5, 24 February 2008, prepared by itSMF Hungary 1 ITIL V3 Hungarian Glossary Notes: 1. This ITIL V3 Hungarian Glossary (internal version: 2.5) is the itSMF Hungary's official translation of ITIL V3 Glossary of Terms, Definitions and Acronyms (version 3.1.24). 2. The Hungarian ITIL Terms have a relatively long .
IEEE Std 729-1983, IEEE Standard Glossary of Software Engineering Terminology (ANSI) L3I.l It increases the number of terms from approximately 500 to 1300, and updates or refines the definitions of many terms included in the initial glossary. A few terms that were included in the initial glossary have
ASTM D 3379 ASTM D 4018 Zkouška jednosměr. laminátu ASTM D 3039 3 f f V Vlastnost Vlastnost 100 [%] 0 Matrice Tah ASTM D 638 Tlak D 695 (prizma, válce, tenké vzorky) Smyk ASTM E 143, ASTM D 5379 4 s m sy m su Fm,F,G tu m t m t m ty m tu Fm,F,E, , cu m c m c m cy m cu Fm,F,E, , Druhy zkoušek – laminy, lamináty Tah (ASTM D 3039) Tlak (ASTM D 3410, ASTM D .
