# data[].attributes.body
=D

# data[].attributes.body
-masuk soalan
-baca buku
goodluck

# data[].attributes.body
wait wait. tips tips

# data[].attributes.body
tip please

# data[].attributes.body
do the best guys

# data[].attributes.body
1. determine the satisfications of users to perform better user-friendly system.
2. determine the findings, reports and recommendations for improvements
3. Identify further development
areas

# data[].attributes.body
Because it ability to provide project sponsors and funding organizations with evidence of costs and benefits

# data[].attributes.body
to get users feedback and make improvement

# data[].attributes.headline
Improved understanding of Karisma business needs

# data[].attributes.subject
Improved understanding of Karisma business needs

# data[].attributes.body
1) be sure that the new system to be reliable for the best user experience with less faulty and error.
2) ensure database functionality and its accuracy.

# data[].attributes.headline
1) to test effectiveness of system output

# data[].attributes.subject
1) to test effectiveness of system output

# data[].attributes.body
2)can generate a feedback from user

# data[].attributes.body
1. Test the accuracy of the information.
2. Gain feedback for further improvement.

# data[].attributes.body
Post implementation .. important... why

# data[].attributes.headline
importance of post implementation evaluation

# data[].attributes.subject
importance of post implementation evaluation

# data[].attributes.body
1) to test accuracy, completeness, and timeliness of information system output.
2) it will determine the level of users satisfaction

# data[].attributes.headline
No. It is very difficult to detect minor errors  as due to absence of parallel system. Errors may be there because testing data is not as big as there may be live data.

# data[].attributes.subject
No. It is very difficult to detect minor errors  as due to absence of parallel system. Errors may be there because testing data is not as big as there may be live data.

# data[].attributes.headline
no. because it is a risky  approach to replace the old system completely by a new one.

# data[].attributes.subject
no. because it is a risky  approach to replace the old system completely by a new one.

# data[].attributes.body
because it is an immediate system changeover that can cause error to the system

# data[].attributes.body
1 It costs a less amount of money as everything has to just set up for once.

2 It is very easy to make change over .

# data[].attributes.headline
He should be able to implement way better changeover technique. It is the parallel changeover where the new system will be running simultaneously with the old system.. Direct cut is costly

# data[].attributes.subject
He should be able to implement way better changeover technique. It is the parallel changeover where the new system will be running simultaneously with the old system.. Direct cut is costly

# data[].attributes.body
once the system develop the problem, this will effect the entire company

# data[].attributes.body
because potential for an error to occur is high due to immediate changeover of the system

# data[].attributes.body
because it requires the management to replace the entire system with the new one. It could less the cost but if something goes wrong it will risk the company because to revert back to the old system is usually impossible.

# data[].attributes.body
instead of direct cutover, parallel implementation might be the best option since this kind of implementation have the lowest risk although it is costly. the old system can be used if there is any errors or problem for the new system.

# data[].attributes.headline
direct cutover is the best method because karisma berhad can stop using the old system and started using the new system immediately. besides, its only use a fewer resources such as low cost and it is easy and simple to implement.

# data[].attributes.subject
direct cutover is the best method because karisma berhad can stop using the old system and started using the new system immediately. besides, its only use a fewer resources such as low cost and it is easy and simple to implement.

# data[].attributes.body
testing on individual software components or module.

# data[].attributes.body
2 integration testing

# data[].attributes.headline
System TestsA complete and integrated testing to make sure all the different parts of the system work together as expected.

# data[].attributes.subject
System TestsA complete and integrated testing to make sure all the different parts of the system work together as expected.

# data[].attributes.body
The method can be performed to expose defects in the inventory system and the interaction between purchase system and sales system.

# data[].attributes.body
while using the coding, en. hakimi can test the unit of program to know whether the system is error free

# data[].attributes.body
-isolate each unit in the system and to describe its erroneous by testing it.
-Mr. Hakimi should be able to evaluate the faulty existed system and eliminate every one of it.

# data[].attributes.body
this system require two or more program that depend on each other to make sure it works properly