Sign-up today to join over 5 million learners already on ALISON:

Diploma in Project Management


Comments about The use/evaluation phase - The System Development Life Cycle Use/Evaluation Phase Revision

The comment must be about:
- Module: The use/evaluation phase
- Topic: The System Development Life Cycle Use/Evaluation Phase Revision
Please note: Comments are not reviewed by ALISON Support staff. For technical support, please contact [email protected]

Latest Comments

  • aaa
    Abosi Bill [[]] To review the SDLC
    2015-05-26 12:05:37

  • aaa
    NKOTANYI Francis Rwanda Revision has been coming more and more, meaning that it is very crucial.
    2015-05-17 11:05:35

  • aaa
    Barnabas Halimani Zimbabwe GOOD QUESTIONS
    2015-05-14 10:05:40

  • aaa
    John Day United Kingdom What are and were the risks, a SWOT analysis.
    2015-05-11 16:05:07

  • aaa
    ZAFRUL HASSAN MUJIB India Revision Use this question and answer activity to review the phases of the SDLC
    2015-05-07 15:05:51

  • aaa
    Faith Thompson Nigeria one phase over
    2015-05-06 13:05:40

  • aaa
    jooj hywrd Iraq The use of evaluation phase depends on informative process
    2015-05-06 10:05:06

    • aaa
      maha mustafa eltahir Sudan Yes that means evaluation of the system output
      2015-05-26 19:05:48
  • aaa
    Hilary Madzvimbo Zimbabwe impact based revision of measure.
    2015-05-05 14:05:18

  • aaa
    Narayanan Cg United States of America useful
    2015-04-24 09:04:22

    • aaa
      maha mustafa eltahir Sudan Important
      2015-05-26 19:05:19
  • aaa
    sunday mbiam Nigeria Typical evaluation methods include: timing how long an operation takes counting errors recorded in an error log visually inspecting output for quality, listening to sound reproduction counting and assessing incidents of failure or downtime observing users to see how quickly they learn to use the new system, how often they need help or make errors stress-testing the system or abusing it in ways that would be expected in real-life operation using the system to its stated capacity, or beyond (e.g. filling a database or hard disk drive) using the system in conjunction with another system to see if data and hardware are compatible carrying out functions to see if they exist and work as expected attempting to break into the system or get access to secured data attempt to configure the system to different users, or add modules, or change the way it works to suit new needs weigh it, measure it, carry it around to see if it's comfortable. After implementation, but how long after? o If you wait too long, users remember less about the development process and how it might be improved o If too soon, users have insufficient time to assess system strengths and weaknesses Six months of operation is desirable, but pressure to finish sooner often exists. Wait until the system is 'bedded down' and users are familiar with it, then evaluate whether it has solved the original problem
    2015-04-22 13:04:33

  • aaa
    Jahidul Islam Bangladesh Explain the Disadvantage of SDLC ?
    2015-04-07 23:04:55

    • aaa
      maha mustafa eltahir Sudan Disadvantage dependent on experience of the team design
      2015-05-26 19:05:07
  • aaa
    Jahidul Islam Bangladesh t's not testing! You are not finding faults to fix - they should have been found and fixed well before the system was implemented. Evaluation measures how well the original ambitions of the new system (i.e. the logical design laid down during the analysis phase) have been achieved. Evaluation doesn't really serve to improve the system that is being evaluated; it serves to improve the next system you will work on. You learn lessons for next time when you evaluate. Different systems will have different criteria that demonstrate their effectiveness or efficiency. Just make sure that the criteria you evaluate are relevant to the goals the system was supposed to have when it was originally analysed. For example, if you buy a cow, you don't evaluate its speed, and if you buy a greyhound, you don't evaluate its milk output. Typical evaluation criteria include: speed accuracy quality of output reliability cost of operation attractiveness ease of use robustness capacity compatibility with other systems functionality (does it have the features it needs?) security flexibility (can it be upgraded, modified, adapted, tweaked, configured?) size, portability. valuation criteria describe what features will be measured. Evaluation methods describe how they will be measured. Don't get them confused! Whenever the word "efficiency" pops up, you should automatically be thinking: "time, money, effort/labour". So let's use them as a structure for an answer. To evaluate time efficiency, you could look at the time taken to: start the system enter data process data produce output communicate information maintain the hardware and software. To evaluate economic efficiency, you could look at the costs of: initial purchase costs of hardware, software, installation, consultancy training and documentation wages consumables repairs, upgrades, maintenance, service contracts interest rates, leasing costs To evaluate labour efficiency, you could look at: the number of staff required to operate the new system (e.g. the old system may have required 2 people, whereas the new system only requires 1 person) the number of man-hours spent operating the system (e.g. the new payroll system may take half the time to process weekly pay runs than did the original system. Typical evaluation methods include: timing how long an operation takes counting errors recorded in an error log visually inspecting output for quality, listening to sound reproduction counting and assessing incidents of failure or downtime observing users to see how quickly they learn to use the new system, how often they need help or make errors stress-testing the system or abusing it in ways that would be expected in real-life operation using the system to its stated capacity, or beyond (e.g. filling a database or hard disk drive) using the system in conjunction with another system to see if data and hardware are compatible carrying out functions to see if they exist and work as expected attempting to break into the system or get access to secured data attempt to configure the system to different users, or add modules, or change the way it works to suit new needs weigh it, measure it, carry it around to see if it's comfortable. After implementation, but how long after? o If you wait too long, users remember less about the development process and how it might be improved o If too soon, users have insufficient time to assess system strengths and weaknesses Six months of operation is desirable, but pressure to finish sooner often exists. Wait until the system is 'bedded down' and users are familiar with it, then evaluate whether it has solved the original problem. Has it achieved the goal specified in the Problem Analysis? If not, fix the thing! Don't sit around with a new system that is as bad, maybe worse, than the old system. Ideally, post-implementation evaluation should be performed by people who were not involved in the development process. External auditors often are involved, since they are impartial and don't have a stake in the success or failure of the system.
    2015-04-07 23:04:51

  • aaa
    Bandar Alalwi United States of America what are five phases of the SDLC ?
    2015-04-06 17:04:48

  • aaa
    Bandar Alalwi United States of America five phases of the SDLC
    2015-04-06 17:04:36

  • aaa
    Bander Alalwi United States of America How we can know The System Development Life Cycle Use/Evaluation Phase Revision?
    2015-04-04 22:04:17

    • aaa
      maha mustafa eltahir Sudan Proper output
      2015-05-26 19:05:33
  • aaa
    Bander Alalwi United States of America Information Technology -> The System Development Life Cycle Use/Evaluation Phase Revision
    2015-04-04 22:04:04

  • aaa
    Genaro Ceballos Panama good, compact documentation ..
    2015-03-27 19:03:20

    • aaa
      maha mustafa eltahir Sudan Sharing the revisions points enhance the best knowledge
      2015-05-26 19:05:05
  • aaa
    CONFIDENCE Ekeh Nigeria interesting module
    2015-03-24 10:03:23

    • aaa
      maha mustafa eltahir Sudan Yes give you conclusion
      2015-05-26 19:05:38
  • aaa
    Mabrat Abdulai Sierra Leone good exercise
    2015-03-20 16:03:42

    • aaa
      maha mustafa eltahir Sudan Thanks
      2015-05-26 19:05:00
  • aaa
    Oyetope Oyewunmi Nigeria Ok.
    2015-03-20 16:03:09

Loading Menu