FTC ACCA tips for June 2007 exam 2.1详解之evaluating冲刺版

zhongya8558 · 发表于 2007-5-21 23:30:59

1 Changeover techniques (data conversion)
【meanings & merits of changeover techniques】<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com<img src=" /><o:p></o:p>
Parallel running,<?xml:namespace prefix = st1 ns = "urn:schemas-microsoft-com<img src=" /><st1:chsdate w:st="on" IsROCDate="False" IsLunarDate="False" Day="30" Month="12" Year="1899">06.6.6</st1:chsdate>
The old & new systems are run in parallel, both processing current data and the results are compared (need to planned how long, what if problems)
Two typical advantages of parallel running are:
1.The existence of a ‘fail-safe’ proven current system which can be returned to if the proposed replacement turns to be inaccurate or unreliable. The existence of this system effectively reduces the risks associated with implementing a new system.
2.The prolonged period of parallel running allows staff to gradually become familiar with the new system and its associated procedures. It effectively provides a relatively long period of time where training (and testing) can be done to gain the user’s understanding and acceptance
Direct changeover <st1:chsdate w:st="on" IsROCDate="False" IsLunarDate="False" Day="30" Month="12" Year="1899">06.6.6</st1:chsdate><o:p></o:p>
The current system is replaced immediately by the replacement system. Transactions are passed solely through the new system.
Two typical advantages of direct changeover are:
1.If the proposed replacement system is effectively tested, then the direct changeover approach provides a much cheaper implementation method than the normal alternative (parallel running) where transactions have to be entered through both the current and proposed system. This is costly and time consuming and may impinge on the effectiveness of the overall business process.
2.Direct changeover is a much more widely applicable approach to implementation than the other alternatives. It can be used in circumstances where there is no current system or where the current system is so different that meaningful comparison of transactions is not possible.
【meaning and what problems data conversion could cause】06.6.6  <st1:chsdate w:st="on" IsROCDate="False" IsLunarDate="False" Day="30" Month="12" Year="1899">05.6.2</st1:chsdate>
The data items may be of a different length. For example, the address may be 50 characters wide in one of the current systems and 30 characters wide in the proposed system. This could lead to certain addresses becoming truncated and hence unusable.
The data items may be of a different type. For example, the patient code may be numeric in the proposed system and alphanumeric in one of the current systems. There may be validation rules on the numeric field that specifically disallow alphanumeric entries. This would lead to these values being rejected unless the validation rules were overridden in some way.
The data items may have a different structure. For example, the address may be three fields in the proposed system－street town and county. However, one of the current systems may hold address as one large field. There has to be some strategy for splitting up the fields in the current system so that they populate the three appropriate fields of the required system.
【issues need to be addressed when populating the new file structure】<st1:chsdate w:st="on" IsROCDate="False" IsLunarDate="False" Day="30" Month="12" Year="1899">04.6.6</st1:chsdate>
Issues include:
—How to split up the examiner address in the current system to populate the three address lines in the proposed system.
—How to organise the entry of examiner codes into the new EXAMINER file and populate this field in the EXAMINATION file.
—Whether Examiner names have been abbreviated in the current ASSESSMENT file and now need to be expanded for the larger Examiner name field in the EXAMINER file.
—How to enter syllabus summary information into the new system. This data does not exist on the old system.
2 Documentation<o:p></o:p>
【documentation expect from sw supplier and what constitutes high quality documentation】<st1:chsdate w:st="on" IsROCDate="False" IsLunarDate="False" Day="30" Month="12" Year="1899">03.6.3</st1:chsdate>
—user manual (①focus on business functions the users will have, eg 'raise a payment against insurance claim',②up-to-date, well designed layout, clear print③written in a language that the business user understands)<o:p></o:p>
—technical doc. (①concerning installing software, ②a description of the procedures that are necessary to keep it operational③technical accuracy & completeness)<o:p></o:p>
3Training<o:p></o:p>
【Meaning & merits】<st1:chsdate w:st="on" IsROCDate="False" IsLunarDate="False" Day="30" Month="12" Year="1899">04.12.2</st1:chsdate>
Attendance public course: In classroom, intensive course<o:p></o:p>
Adv
— Few staff members away from the office at any one time, means that remaining employees should be able to cope with the additional workload.
— Employees have the opportunity to meet users who work for other companies and to learn from their ideas and experience.
Disadv
—Long elapsed time to get everybody trained. 
—There may be little chance to discuss the problems of using the software in the context of the company.
Computer-based training (CBT): Using CD, Internet<o:p></o:p>
Adv
—Much the cheapest option. 
—Employees can learn at their own rate. <o:p></o:p>
Disadv
—no motive to use the package 
—no clear method of resolving problems 
Onsite course<o:p></o:p>
Adv
—Short elapsed time to get everybody trained. 
—The course can be tailored to local requirements..
Disadv
—Too many people away from their desk at any one time. It is unlikely that the remaining employees will be able to cope with the additional workload.
—the costliest option.
【how to deliver effective training】<st1:chsdate w:st="on" IsROCDate="False" IsLunarDate="False" Day="30" Month="12" Year="1899">03.6.3</st1:chsdate>
For training to be effective, one must establish what she wants the training to achieve and identify the ‘skills gap’ (what employee know now and what they must know in the future to use the sw effectively)
To address this gap training must be delivered at an appropriate time and use an appropriate method. Training approaches might include conventional lecturer-based training courses and computer-based tuition. The latter allow the employees to learn at their own rate. It must be assessed that whether the training objectives have been achieved or not. Furthermore, computer-based tuition may also be available, developed at a cost that would be prohibitive to a bespoke solution.
4 Maintenance <o:p></o:p>
【Types of maintenance】<st1:chsdate w:st="on" IsROCDate="False" IsLunarDate="False" Day="30" Month="12" Year="1899">04.12.3</st1:chsdate>    <st1:chsdate w:st="on" IsROCDate="False" IsLunarDate="False" Day="30" Month="12" Year="1899">03.12.6</st1:chsdate>   <st1:chsdate w:st="on" IsROCDate="False" IsLunarDate="False" Day="30" Month="12" Year="1899">01.12.6</st1:chsdate>
Maintenance: the redoing of certain aspects of the systems development process.<o:p></o:p>
1. Corrective – to fix a problem or failure<o:p></o:p>
- although most faults should be eliminated during testing process, problems may be revealed during the operation of the system<o:p></o:p>
- urgent as the system cannot be fully operation<o:p></o:p>
2. Perfective – to improve the performance, usability, efficiency or effectiveness<o:p></o:p>
prompted by   -the availability of new technology, e.g. adopt GUI (graphical user interface)<o:p></o:p>
               -a request for system enhancement from users<o:p></o:p>
3. Adaptive – to fit the new environment <o:p></o:p>
       enables the system to adjust to changes in its environment e.g. new taxation legislation require to change the payroll software <o:p></o:p>
【meaning & benefits &purpose of User Group】<st1:chsdate w:st="on" IsROCDate="False" IsLunarDate="False" Day="30" Month="12" Year="1899">04.12.2</st1:chsdate>    <st1:chsdate w:st="on" IsROCDate="False" IsLunarDate="False" Day="30" Month="12" Year="1899">01.12.6</st1:chsdate>
1.individual users band together to exchange info. and experience of using a particular package
2.form a focus for lobbying the developer to develop new features & correct current problems
3.encouraged & financed by the developer
4.User Groups can encourage and assist new users of the software.
5. Most User Groups issue newsletters and hold conferences and workshops
【meaning and conduct of user workshop】<st1:chsdate w:st="on" IsROCDate="False" IsLunarDate="False" Day="30" Month="12" Year="1899">03.6.5</st1:chsdate>
（访谈：每次的限于1-2人；专家引导）→导致用户论坛的产生（不限人数；用户建议）
1. the workshop is an open forum can explore requirements, issues & problems in a more reflective environment
2. led by a facilitator, need not significant IT skills
3.IT staff provide technical input and explore design solution using RAD (Rapid Application Development) tools
4.the proceedings of the workshop documented
5 Post implementation issues<o:p></o:p>
【purpose and objectives】<st1:chsdate w:st="on" IsROCDate="False" IsLunarDate="False" Day="30" Month="12" Year="1899">05.12.6</st1:chsdate><o:p></o:p>
A post-implementation review is normally carried out a few months after the new system has gone live. Its main purpose is to review whether the system has met its defined business objectives and to consider whether the delivered functionality matches the business need. The review will also focus on any difficulties encountered in using the system (for example, problems of usability, requirements not quite met, requirements that have changed since implementation) and actions will be agreed to tackle these difficulties. The review is normally a joint exercise between the users and suppliers of the system.
An end-project review is where the project formed to deliver a system, service or product is brought to an orderly close. The review often confirms the closure of the project by formally signing acceptance letters or undertaking an equivalent sign-off procedure. The end-project review examines how the project has been run with the prime aim of identifying good and bad practice that can be fed back into the project management standards. For example, continual failure to meet deadlines may be diagnosed as due to optimistic estimating. Hence, the end-project review panel may recommend changes to the model that produced those estimates.
【why it is important to conduct a post-implementation review】<st1:chsdate w:st="on" IsROCDate="False" IsLunarDate="False" Day="30" Month="12" Year="1899">04.12.1</st1:chsdate><o:p></o:p>
As in the scenario, a post-implementation review is held a few months after the system has gone live. Participants include representatives of the users of the software, the people who wrote or supplied it and appropriate senior management who can action any requests and resolve any issues. The review identifies perfective or corrective action required to improve the system, including technical modifications and further staff training. Such reviews may prevent similar problems occurring in future projects. The post-implementation review is an opportunity to ensure that the system is on course to meet the business case requirements (benefits outweighing costs) as well as the technical requirements of the system.
【structure & content of report】<o:p></o:p>
post-implementation review<o:p></o:p>
<OL style="MARGIN-TOP: 0cm" type=1>
<LI class=MsoNormal style="MARGIN: 0cm 0cm 0pt; mso-list: l2 level1 lfo1; tab-stops: list 36.0pt">Executive summary of findings <o:p></o:p></LI></OL>
       highlight problems e.g. Dec2004 case study: poorly designed report, absence of audit trail & archiving facility…<o:p></o:p>
<OL style="MARGIN-TOP: 0cm" type=1 start=2>
<LI class=MsoNormal style="MARGIN: 0cm 0cm 0pt; mso-list: l0 level1 lfo2; tab-stops: list 36.0pt">A review of system performance and user satisfaction<o:p></o:p></LI></OL>
       by recording response time, down time, errors, questionnaires<o:p></o:p>
<OL style="MARGIN-TOP: 0cm" type=1 start=3>
<LI class=MsoNormal style="MARGIN: 0cm 0cm 0pt; mso-list: l6 level1 lfo3; tab-stops: list 36.0pt">A cost-benefit analysis <o:p></o:p></LI></OL>
       comparing actual costs with actual benefits<o:p></o:p>
<OL style="MARGIN-TOP: 0cm" type=1 start=4>
<LI class=MsoNormal style="MARGIN: 0cm 0cm 0pt; mso-list: l8 level1 lfo4; tab-stops: list 36.0pt">Recommendations for system modifications <o:p></o:p></LI></OL>
end-project review<o:p></o:p>
<OL style="MARGIN-TOP: 0cm" type=1>
<LI class=MsoNormal style="MARGIN: 0cm 0cm 0pt; mso-list: l5 level1 lfo7; tab-stops: list 36.0pt">Review of project initiation document <o:p></o:p></LI></OL>
       especially note the objectives from the project and check whether the objectives have been met…<o:p></o:p>
<OL style="MARGIN-TOP: 0cm" type=1 start=2>
<LI class=MsoNormal style="MARGIN: 0cm 0cm 0pt; mso-list: l9 level1 lfo8; tab-stops: list 36.0pt">Performance<o:p></o:p></LI></OL>
       a review of achievements vs. original objectives, provides a comment on the way that the objectives were achieved, e.g. lack of clarity in objectives<o:p></o:p>
<OL style="MARGIN-TOP: 0cm" type=1 start=3>
<LI class=MsoNormal style="MARGIN: 0cm 0cm 0pt; mso-list: l7 level1 lfo9; tab-stops: list 36.0pt">Productivity <o:p></o:p></LI></OL>
       how efficient the project was in terms of budgets for resources and the actual resources used. Budget comparisons for cost of the project, no.of hours spent…<o:p></o:p>
<OL style="MARGIN-TOP: 0cm" type=1 start=4>
<LI class=MsoNormal style="MARGIN: 0cm 0cm 0pt; mso-list: l1 level1 lfo10; tab-stops: list 36.0pt">Quality of the product and the process of the product itself<o:p></o:p></LI></OL>
       e.g. whether the testing design effective<o:p></o:p>
【Procedure to effectively collect the metrics】
<OL style="MARGIN-TOP: 0cm" type=1>
<LI class=MsoNormal style="MARGIN: 0cm 0cm 0pt; mso-list: l3 level1 lfo5; tab-stops: list 36.0pt">carefully select the metrics that can measure significant aspects of the system (time, costs or quality focus)<o:p></o:p></LI></OL>
<OL style="MARGIN-TOP: 0cm" type=1 start=2>
<LI class=MsoNormal style="MARGIN: 0cm 0cm 0pt; mso-list: l4 level1 lfo6; tab-stops: list 36.0pt">agree the data collection methods with users<o:p></o:p>
<LI class=MsoNormal style="MARGIN: 0cm 0cm 0pt; mso-list: l4 level1 lfo6; tab-stops: list 36.0pt">test the metrics in advance <o:p></o:p>
<LI class=MsoNormal style="MARGIN: 0cm 0cm 0pt; mso-list: l4 level1 lfo6; tab-stops: list 36.0pt">use the metrics consistently to ensure comparability</LI></OL>
【metrics to measure the success of the system】<o:p></o:p>
Metrics: quantified measurements used to measure system performance e.g. response time, down times per week<o:p></o:p>
the most appropriate measures for IS system<o:p></o:p>
1、agreement to original specification  (compare specification and the outcome, e.g. 80% agree)<o:p></o:p>
2、time (compare estimated & actual time )<o:p></o:p>
3、financial objectives (egg. costs, NPV, IRR)<o:p></o:p>
4、less quantifiable measures (egg. user-friendliness, customer satisfaction, questionnaires, no. of complaints)<o:p></o:p>
【IS automation system will lead to greater efficiency by】<o:p></o:p>
1.Costs of computer system lower than manual system      <o:p></o:p>
(e.g. e-marking system, costs of courier from & to the markers saved)<o:p></o:p>
2.Accuracy of data processing improved as avoid human errors<o:p></o:p>
       (e.g. e-marking system, the markers can mark scripts directly on the screen & the results sent to exam centre’s database directly, no need to key in manually, which may lead to type error)<o:p></o:p>
3.Speed of processing increased<o:p></o:p>
       (e.g. e-marking system, the markers can mark directly on the screen & the result send to exam centre’s database directly, which reduce the lead time on the way)          <o:p></o:p>
【Software monitors】<o:p></o:p>
a computer program that records data about the application in use. Might be used to identify excessive delays during execution of the program. (the application being monitored is interrupted and slowed down)<o:p></o:p>
<o:p> </o:p>

[ 本帖最后由 zhongya8558 于 2007-5-21 23:32 编辑 ]

mort12 · 发表于 2007-5-29 22:10:14

大救星啊

alice_944 · 发表于 2007-6-3 20:12:06

THANKS A LOT

账号		自动登录	找回密码
密码			立即注册

FTC ACCA tips for June 2007 exam 2.1详解之evaluating冲刺版

评分

回复 #1 zhongya8558 的帖子

thank you

好人卡