【文章內(nèi)容簡(jiǎn)介】 ing accounts is to be carried over to the new application. （ 1． 2） Obviously details about existing customers will need to be set up before the new application can bee operational. It would be helpful to release the functionality to set up customer details well in advance of the changeover. （ 2） Details of invoices that have already been sent out but have not yet been paid would also need to be recorded for the new application. If the invoices have a lot of plex detail it might be worth releasing that functionality earlier, even if the users would have to transfer the invoice number and amount due to their existing accounting system. It might at least save them typing if the old system is a purely clerical one. 五、 成績(jī)僅根據(jù)第 2 和 6 題批改，第 3 題不需要看 2. If you were asked as an expert to provide an estimate of the effort needed to make certain changes to an existing piece of software, what information would you like to have to hand to assist you in making that estimate? The estimation of the effort to change a software ponent requires a different approach to the development of pletely new software as a major factor is the structure of the existing software. The estimator might need to know: ? The nature of the changes required ? Ideally they should be told about the reasons for the change, as they may be able to suggest alternatives and more economic ways of meeting the requirement ? The structure of the software to be changed ? Some idea of which parts of the software need changing ? Who will be carrying out the changes – will it be someone who is already familiar with the software to be changed, or will additional time have to be allocated for familiarization? ? Evaluation, Tools, Risk, Personnel, Delay, Cost 3. （此題不需要改） A small application maintains a telephone directory. The database for the application contains the following data types: Staff reference Surname Forenames Title 8 Department code Room number Telephone extension Email address Fax number Transactions are needed which: ii. set up new entries。 iii. amend existing entries iv. delete entries v. allow enquirers to list on line the details for a particular member of staff vi. produce a plete listing of the telephone directory entries in alphabetical order a) Use this scenario to produce an estimated Mark II FP count. List all the assumptions you will need to make. b) Another requirement could be to produce the listing in (v) in departmental order. In your view should this increase FP count and if so by how much? a) 涉及的 input/output 數(shù)據(jù)類型 transaction inputs outputs entities accessed set up new entry ( staff reference to fax number 9 error message 1 directory entry 1 amend (display) staff reference 1 surname to fax number or error message 10 directory entry 1 amend (update) surname to fax number 9 error message 1 directory entry 1 delete entry staff reference 1 surname, forenames (as check) error message 3 directory entry 1 enquiry staff reference (or surname, forenames) 3 (1) full details + error message 10 directory entry 1 listing trigger 1 full details 9 directory entry 1 totals 24 x = 35 x = 7x = grand total Discussion： 關(guān)于相同功能，工作量是否應(yīng)當(dāng)重復(fù)計(jì)算？ （不同原因） b) It can argued that the data presented in the two reports are the same, so that they are logically the same and so should be counted only once. Most development environment have easy to use features for sorting data and so the actual amount of work needed to produce the second report would probably be negligible. However, if you have every tried to look up details in an unsorted list, the fact that it is sorted can provide considerable value. There is therefore a debate among FP practitioners about whether FPs should reflect the value of the system to the user or the amount of work that is needed to develop it. This is particularly an issue in relation to the question of reusable ponents. 9 6. Given the project data below: project inputs outputs entity accesses system users programming language developer days 1 210 420 40 10 x 30 2 469 1406 125 20 x 85 3 513 1283 76 18 y 108 4 660 2310 88 200 y 161 5 183 367 35 10 z 22 6 244 975 65 25 z 42 7 1600 3200 237 25 y 308 8 582 874 111 5 z 62 X 180 350 40 20 y Y 484 1190 69 35 y a) What items are size drivers? inputs, outputs, entity accesses (system users for certain aspects) b) What items are productivity drivers? Programming language c) What are the productivity rates for programming languages x, y and z? x 10 FPs a day [*（ 210+469） +*（ 40+125） +*（ 420+1406） ]/(30+85)= y 7 FPs a day z 12 FPs a day d) What would be the estimated effort for projects X and Y using a Mark II function point count? project inputs outputs entity accesses system users programming language developer days FPs 1 210 420 40 10 x 30 2 469 1406 125 20 x 85 3 513 1283 76 18 y 108 4 660 2310 88 200 y 161 7 1600 3200 237 25 y 308 5 183 367 35 10 z 22 6 244 975 65 25 z 42 8 582 874 111 5 z 62 X 180 350 40 20 y Y 484 1190 69 35 y Project X : 262/7 . 37 days 10 Project Y 705/7 . 101 days e) What would be the estimated effort for X and Y using an approximate analogy approach? Project X Project 5 22 days, (language is not considered) Project Y Project 3 108 days. f) What would have been the best estimating method if the actual effort for X turns out to be 30 days and for Y turns out to be 120 days? Can you suggest why the results are as they are and how they might be improved. If we use a measurement based on the percentage error, calculated as absolute (actualestimate)/actual we get the following: Project X