the application will be supporting in Software

Creation QR in Software the application will be supporting

CASE (Computer Aided Software Engineering) The use of computer software to assist in completing tasks defined within a system s development life cycle methodology CASE may be used across the entire project life cycle or used to assist with specific parts of the cycle The three categories are

Upper CASE Environment independent and generally used to perform analysis tasks, for example, logical data modeling, process modeling, data flow diagramming, and so on Lower CASE Environment dependent and generally used to assist in physical design and construction tasks, for example, physical data base design, code generation, and so on Integrated CASE Fully integrating Upper and Lower CASE, for example, logical models are converted to physical models, which in turn generate database tables and code

Client roles The roles performed by the computers that provide the interface to the software s external users Client-server Client-server computing or networking is a distributed application architecture that partitions tasks or workloads between service providers (servers) and service requesters, called clients Client-server description A description of the architecture of the client/server software application or product Cost The price paid (either through money, time, labor, and so on) to acquire, produce, accomplish, or maintain the product The following methods of collecting COST are believed to be the most common:

Cost recorded The daily recording of all cost incurred by each person on project-related tasks Cost derived It is possible to derive the cost where it has not been collected on a daily basis as in cost recorded

Count approach A description of the method used to size the project software For most projects in the ISBSG Repository, this is the functional size measurement method (FSM method) used to measure the functional size (for example, IFPUG, MARK II, NESMA, COSMIC, and so on) For projects using other size measures (for example, LOC, and so on) this is a short name for that method, and in data releases the size data is not included with sizes measured by an FSM method but rather is in a section Size Other than FSM Data quality rating This field contains an ISBSG rating code of A, B,

C, or D applied to the project data by the ISBSG quality reviewers to denote the following:

A = The data submitted was assessed as being sound with nothing being identified that might affect its integrity B = The submission appears fundamentally sound, but there are some factors that could affect the integrity of the submitted data C = Due to significant data not being provided, it was not possible to assess the integrity of the submitted data D = Due to one factor or a combination of factors, little credibility should be given to the submitted data

to either fail or to produce incorrect results There can be three categories:

Minor defect A minor defect does not make the application unusable in any way (for example, a modification is required to a screen field or report) Major defect A major defect causes part of the application to become unusable Extreme defect A 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 the project duration (defects and hours per project phase) and after implementation (defects found within the first month of use of the software) Of the following, only defect found, repair hours, and rework hours per project phase are currently collected: Defect found The number of defects detected in the process in that particular effort breakdown or found within the first month of use of the software after implementation