1 / 20

Esprit Project Number 29512

Esprit Project Number 29512. Case Study. Emergency Scenario 1. Application oriented 2. Well defined ‘conversion’ task - with legal deadlines 3. Assess to verify budgets an time scales. The e mergency Scenario. Case Study Overview. The two phases of the evaluation task

michel
Download Presentation

Esprit Project Number 29512

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Esprit Project Number 29512 Case Study

  2. Emergency Scenario 1. Application oriented 2. Well defined ‘conversion’ task - with legal deadlines 3. Assess to verify budgets an time scales The emergency Scenario

  3. Case Study Overview • The two phases of the evaluation task • Selection of sample • Method evaluation • The three sections to this document • Application selection • Rationale • Character of selected application • Estimate • Showing how forms were completed • Conclusion • Concerning both qualitative and quantitative value of the method • Comparison with other methods

  4. Application SelectionSelection criteria • Two major selection criteria • Must be representative of a wide family • Classical legacy monolithic applications • Must reflect the business priorities of the user • Siceas had already stated the need to set priorities for those applications involving external customers • Selected application • Ferry Company Accounts Management

  5. FRANZA GROUP GENERAL ACCOUNTING SYSTEM PURCHASE FERRIES MAINTENANCE ACCOUNTING TICKETING SALARIES MANAGEMENT Application SelectionApplication Logical Structure Developed in house Jan 1984 Deployed Dec 1984 Last revised Dec 1997 Not scheduled for replacement

  6. Euro EstimateForms Used Customer Questionnaire Application Catalogue Assessor Questionnaire Modification/ Solution Table Direct Effort Weights IT Characteristics Euro Solution Characteristics Referenceonly Estimate Not used Cost Item / Modification Parameters Other Cost Parameters Effort Parameters

  7. Euro EstimateEmergency Method Steps Step 1 1 Id & record applications 2 Calibrate parameters (Corporate Assessment) Identify Applications Step 2 Partially done 1 Collect Application Information 2 Determine quality of application information 3 Document application information Gather Application Information Step 5 1 Re-Calibrate parameters In-Use Evaluation Step 3 Not done Gather Solution Information 1 Determine solution 2 Determine modifications 3 Document solution modifications Step 4 Prepare Estimate 1 Do calculations

  8. Euro EstimateCustomer Questionnaire Summary Size Documentation Coverage and Quality TP - 115 prgs, 240000 stmts Batch - 5 prgs, 10000 stmts Maps 78 Archives - 8 Prints - 20 IO Flows - 4 I, 2 O Source code User Manual High functional coverage Impacts on general accounting application Medium functional quality Medium technical quality Maintenance last year - .5p/m Maintenance forecast - .5p/m e Compliance Has currency code Amounts contain decimals Not multi currency Not e compliant e adaptation has high impact Usage 1 Department 75 Users Used internally for internal and client support purposes 5 year historical data Deployed for all users at once Environment Not C/S IBM/VSE/CICS/VSAM/COBOL No other hardware These values were supplied by Siceas personnel and were recorded on the Customer Questionnaire form.

  9. User Reliability is 7 This makes a User Reliability Weighting of LOW Euro EstimateAssessor Questionnaire Summary • Level of responsibility for application • Direct (weight = 0) • Technical Competence • High (weight = 0) • Seniority in role • More than 5 years (weight = 0) • User availability • Medium (weight = 7) • Personal impression of assessor • Positive (weight = 0) These values were deduced by Engineering using a combination of assessor judgement and the parameters pre recorded on the Assessor Questionnaire form.

  10. Euro EstimateDirect Effort Weights Summary These values were deduced by the Engineering assessor using information on the Customer Questionnaire and the parameters pre recorded on the Direct Effort Weights form.

  11. Euro EstimateIT Characteristics Summary CharacteristicValue/Code Development Policy 1 Application Type 2 No. TP Programs 115 No. Batch Programs 5 Total Programs 120 Maps 78 Total Archives 8 CharacteristicValue/Code No. Prints 20 Tech/Funct Adequecy Medium Organisational Impact Medium Structural Criticality Low Maintenance Complexity Medium Documentation Low No. Interface Flows 7 These values were obtained from information recorded in the Customer Questionnaire, the Assessor Questionnaire and the Direct Effort Weights

  12. e & NC Rounding Anomalies ? C o n e & NC v e r e & NC t e & NC e r e & NC Euro EstimateSelection of Solutions C o n Application v e Converter e & NC e & NC r t e r ? ? Not required Required

  13. Euro EstimateEuro Solution Characteristics Summary Modifications Required Solution CharacteristicValue/Code Decimaliz 2 Dual amount 1 Curr Code 0 Algorit 2 Constants & represent. 1 New Funct 0 Dual amount output 126 Interface Converter 6 Arch Convert 1 TP input convert 0 Other modifications 0 Dual Amount e Compliance CharacteristicValue/Code Curr Code yes Decimals yes Multi currency yes Appl Euro compl no Impact high These values were obtained from information recorded in the Customer Questionnaireand the Modification/Solution Table

  14. Total Effort is defined as - Implementation Effort  Other Effort Where - Implementation Effort is - The Basic Effort ( due to size ) The Extra Effort ( due to complexity ) Other Effort is - Contingency Effort ( due to uncertainty in info ) Euro EstimateCalculation of Effort Effort was calculated, according to the formulas documented in the deliverable D321, using the figures recorded on theIT Characteristicsand theEuro Solution Characteristicsforms and the parameters documented in theCost Item / Modification Parameters, Effort ParametersandOther Cost Parameters

  15. Euro EstimateEstimate Summary Effort was documented on theEstimate Formand a summary of the figures for each system within the application is given here

  16. Conclusions Quantitative Evaluation

  17. ConclusionsQualitative Evaluation • Learning Complexity • Well documented • Easy to learn • Wide spectrum of problems covered • Good instrument for consultancy services • Usability • Covers concrete needs • Well defined forms • Step by step guidance through the forms • Can be ‘programmed’ • Excel formulae, DB facility, programs

  18. ConclusionsQualitative Evaluation - Cont’d • Scope and Applicability • Difficult to assess - narrow case study • Approach appears to be wide • Customisable parameters increase scope • Strengths and Weaknesses • Problem oriented approach - Strength • Computational complexity - Weakness • Programmable - Strength

  19. ConclusionsQualitative Evaluation - Cont’d • Compatibility • Related approaches generally compatible • Helpfulness • Assists quantification of necessary resources • Assists project planning • Alternatives • Many alternatives due to each ‘player’ involved in Euro conversion

  20. Conclusion The emergency method caters for concrete requirements arising from the need to make IT systems e compliant. It addresses the issues of e conversion practically and realistically. The results of the emergency project are published in English and Italian on web pages which can be found at: www.comp.lancs.ac.uk/computing/research/cseg/projects/emergency/emergencyHome.html

More Related