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

ALISON: Diploma in Project Management

Comments about System development life cycle - The implementation phase

The comment must be about:
- Module: System development life cycle
- Topic: The implementation phase

Latest Comments

  • Ralph Webster South Africa The implementation phase is where physical and conceptual resources that are required for the project are obtained and integrated into the existing system to produce the final working system. There are a number of steps that are followed in this phase, including: planning and announcing the implementation acquiring the hardware resources acquiring the software resources preparing the physical facilities educating the participants and users preparing an implementation schedule (or changeover) changing over to the new system.
    2014-10-19 07:10:45

  • George Ugim Nigeria why is educating the participants and users not the first in the list?
    2014-10-10 20:10:09

    • Kenneth M Akahoho Ghana You will need to plan and acquire you hard and soft resources ,physical facilities on the participants will be educated
      2014-10-23 00:10:35
  • George Fragos Greece Does a project take shape during the implementation phase?
    2014-09-29 10:09:35

  • Davy Armel ASSEKO MENGOMO Gabon Shouldn't the testing phase come before the implementation phase?
    2014-09-27 13:09:52

    • Assel Satpayeva Kazakhstan What you will test, if nothing is implemented yet? Usually, there is a commissioning phase that discloses all the Pros and Cons of the project.
      2014-10-22 09:10:35
  • ANNETTE ROBINSON United States of America Why isn't Piloting the design not indicted before implementing?
    2014-09-09 00:09:01

  • ARIHO SIMPLISIO Uganda Planing and implementing what should be the first?
    2014-08-20 13:08:03

    • Tendani Matumba South Africa Planning should be the first. If you did not plan there will be nothing to implement.
      2014-09-13 02:09:25
    • Patrick Obeng Ghana planning
      2014-09-02 14:09:53
    • Yai Deng Yai South Sudan Planning should be the first.
      2014-08-25 12:08:29
  • Saw Minyau Germany Which kinds of training activities when educating the participants and users?
    2014-08-15 20:08:41

    • Manasseh Taloafiri Solomon Islands Some training activities would be community buy-in for them to support the project. As good as projects are, if communities or beneficiaries do not support and take ownership, projects will surely fail. Thanks
      2014-10-13 04:10:47
    • Yai Deng Yai South Sudan About the project activities and procedures required to do the work.
      2014-08-25 12:08:28
  • Samuel Kofi Odoi Ghana Who is supposed to control the implementation phase?
    2014-08-14 21:08:16

    • Yai Deng Yai South Sudan Project manager.
      2014-08-25 12:08:55
  • Vikram Vasant Rotkar United Kingdom Who plays a major role in the implementation phase?
    2014-07-21 17:07:26

    • Assel Satpayeva Kazakhstan Project Manager and his team.
      2014-10-22 09:10:53
    • Yai Deng Yai South Sudan Project team and stakeholders and beneficiaries.
      2014-08-25 12:08:58
  • Jones Hanungu Munang'andu Zambia he principal objective of a feasibility study is to determine whether the system is desirable on the basis of long-term plans, strategic initiatives, and a cost-benefit analysis. System analysis provides a detailed answer to the question, What will the new system do? The next stage, system design, results in an extensive blueprint for how the new system will be organized. During the programming and testing stage, the individual software modules of the system are developed, tested, and integrated into a coherent operational system. Further levels of testing ensure continuing quality control. Installation includes final testing of the system in the work environment and conversion of organizational operations to the new system. The later stages of development include such implementation activities as training users and modifying the organizational processes in which the system will be used. Life-cycle development is frequently faulted for its long development times and voluminous documentation requirements—and, in some instances, for its failure to fulfill the user's requirements at the end of the long development road. Increasingly, life-cycle development has been replaced by a process known as rapid application development. With RAD a preliminary working version of an application, or prototype, is built quickly and inexpensively, albeit imperfectly. This prototype is turned over to the users, their reactions are collected, suggested modifications are incorporated, and successive prototype versions eventually evolve into the complete system. Sometimes RAD and life-cycle development are combined: a prototype is produced to determine user requirements during the initial system analysis stage, after which life-cycle development takes over. After an installed system is handed over to its users and operations personnel, it will almost invariably be modified extensively over its useful life in a process known as system maintenance. For instance, if a large system takes 2 years to develop, it will typically be used and maintained for some 5 to 10 years or even longer. Most maintenance is to adjust the system to the organization's changing needs and to new equipment and system software, but inevitably some maintenance involves correcting design errors and exterminating software “bugs” as they are discovered.
    2014-07-20 18:07:38

  • Jones Hanungu Munang'andu Zambia he principal objective of a feasibility study is to determine whether the system is desirable on the basis of long-term plans, strategic initiatives, and a cost-benefit analysis. System analysis provides a detailed answer to the question, What will the new system do? The next stage, system design, results in an extensive blueprint for how the new system will be organized. During the programming and testing stage, the individual software modules of the system are developed, tested, and integrated into a coherent operational system. Further levels of testing ensure continuing quality control. Installation includes final testing of the system in the work environment and conversion of organizational operations to the new system. The later stages of development include such implementation activities as training users and modifying the organizational processes in which the system will be used. Life-cycle development is frequently faulted for its long development times and voluminous documentation requirements—and, in some instances, for its failure to fulfill the user's requirements at the end of the long development road. Increasingly, life-cycle development has been replaced by a process known as rapid application development. With RAD a preliminary working version of an application, or prototype, is built quickly and inexpensively, albeit imperfectly. This prototype is turned over to the users, their reactions are collected, suggested modifications are incorporated, and successive prototype versions eventually evolve into the complete system. Sometimes RAD and life-cycle development are combined: a prototype is produced to determine user requirements during the initial system analysis stage, after which life-cycle development takes over. After an installed system is handed over to its users and operations personnel, it will almost invariably be modified extensively over its useful life in a process known as system maintenance. For instance, if a large system takes 2 years to develop, it will typically be used and maintained for some 5 to 10 years or even longer. Most maintenance is to adjust the system to the organization's changing needs and to new equipment and system software, but inevitably some maintenance involves correcting design errors and exterminating software “bugs” as they are discovered.
    2014-07-20 18:07:23

  • Jones Hanungu Munang'andu Zambia he principal objective of a feasibility study is to determine whether the system is desirable on the basis of long-term plans, strategic initiatives, and a cost-benefit analysis. System analysis provides a detailed answer to the question, What will the new system do? The next stage, system design, results in an extensive blueprint for how the new system will be organized. During the programming and testing stage, the individual software modules of the system are developed, tested, and integrated into a coherent operational system. Further levels of testing ensure continuing quality control. Installation includes final testing of the system in the work environment and conversion of organizational operations to the new system. The later stages of development include such implementation activities as training users and modifying the organizational processes in which the system will be used. Life-cycle development is frequently faulted for its long development times and voluminous documentation requirements—and, in some instances, for its failure to fulfill the user's requirements at the end of the long development road. Increasingly, life-cycle development has been replaced by a process known as rapid application development. With RAD a preliminary working version of an application, or prototype, is built quickly and inexpensively, albeit imperfectly. This prototype is turned over to the users, their reactions are collected, suggested modifications are incorporated, and successive prototype versions eventually evolve into the complete system. Sometimes RAD and life-cycle development are combined: a prototype is produced to determine user requirements during the initial system analysis stage, after which life-cycle development takes over. After an installed system is handed over to its users and operations personnel, it will almost invariably be modified extensively over its useful life in a process known as system maintenance. For instance, if a large system takes 2 years to develop, it will typically be used and maintained for some 5 to 10 years or even longer. Most maintenance is to adjust the system to the organization's changing needs and to new equipment and system software, but inevitably some maintenance involves correcting design errors and exterminating software “bugs” as they are discovered.
    2014-07-20 18:07:19

  • Jones Hanungu Munang'andu Zambia he principal objective of a feasibility study is to determine whether the system is desirable on the basis of long-term plans, strategic initiatives, and a cost-benefit analysis. System analysis provides a detailed answer to the question, What will the new system do? The next stage, system design, results in an extensive blueprint for how the new system will be organized. During the programming and testing stage, the individual software modules of the system are developed, tested, and integrated into a coherent operational system. Further levels of testing ensure continuing quality control. Installation includes final testing of the system in the work environment and conversion of organizational operations to the new system. The later stages of development include such implementation activities as training users and modifying the organizational processes in which the system will be used. Life-cycle development is frequently faulted for its long development times and voluminous documentation requirements—and, in some instances, for its failure to fulfill the user's requirements at the end of the long development road. Increasingly, life-cycle development has been replaced by a process known as rapid application development. With RAD a preliminary working version of an application, or prototype, is built quickly and inexpensively, albeit imperfectly. This prototype is turned over to the users, their reactions are collected, suggested modifications are incorporated, and successive prototype versions eventually evolve into the complete system. Sometimes RAD and life-cycle development are combined: a prototype is produced to determine user requirements during the initial system analysis stage, after which life-cycle development takes over. After an installed system is handed over to its users and operations personnel, it will almost invariably be modified extensively over its useful life in a process known as system maintenance. For instance, if a large system takes 2 years to develop, it will typically be used and maintained for some 5 to 10 years or even longer. Most maintenance is to adjust the system to the organization's changing needs and to new equipment and system software, but inevitably some maintenance involves correcting design errors and exterminating software “bugs” as they are discovered.
    2014-07-20 18:07:53

  • Jones Hanungu Munang'andu Zambia he principal objective of a feasibility study is to determine whether the system is desirable on the basis of long-term plans, strategic initiatives, and a cost-benefit analysis. System analysis provides a detailed answer to the question, What will the new system do? The next stage, system design, results in an extensive blueprint for how the new system will be organized. During the programming and testing stage, the individual software modules of the system are developed, tested, and integrated into a coherent operational system. Further levels of testing ensure continuing quality control. Installation includes final testing of the system in the work environment and conversion of organizational operations to the new system. The later stages of development include such implementation activities as training users and modifying the organizational processes in which the system will be used. Life-cycle development is frequently faulted for its long development times and voluminous documentation requirements—and, in some instances, for its failure to fulfill the user's requirements at the end of the long development road. Increasingly, life-cycle development has been replaced by a process known as rapid application development. With RAD a preliminary working version of an application, or prototype, is built quickly and inexpensively, albeit imperfectly. This prototype is turned over to the users, their reactions are collected, suggested modifications are incorporated, and successive prototype versions eventually evolve into the complete system. Sometimes RAD and life-cycle development are combined: a prototype is produced to determine user requirements during the initial system analysis stage, after which life-cycle development takes over. After an installed system is handed over to its users and operations personnel, it will almost invariably be modified extensively over its useful life in a process known as system maintenance. For instance, if a large system takes 2 years to develop, it will typically be used and maintained for some 5 to 10 years or even longer. Most maintenance is to adjust the system to the organization's changing needs and to new equipment and system software, but inevitably some maintenance involves correcting design errors and exterminating software “bugs” as they are discovered.
    2014-07-20 18:07:38

  • Jones Hanungu Munang'andu Zambia he principal objective of a feasibility study is to determine whether the system is desirable on the basis of long-term plans, strategic initiatives, and a cost-benefit analysis. System analysis provides a detailed answer to the question, What will the new system do? The next stage, system design, results in an extensive blueprint for how the new system will be organized. During the programming and testing stage, the individual software modules of the system are developed, tested, and integrated into a coherent operational system. Further levels of testing ensure continuing quality control. Installation includes final testing of the system in the work environment and conversion of organizational operations to the new system. The later stages of development include such implementation activities as training users and modifying the organizational processes in which the system will be used. Life-cycle development is frequently faulted for its long development times and voluminous documentation requirements—and, in some instances, for its failure to fulfill the user's requirements at the end of the long development road. Increasingly, life-cycle development has been replaced by a process known as rapid application development. With RAD a preliminary working version of an application, or prototype, is built quickly and inexpensively, albeit imperfectly. This prototype is turned over to the users, their reactions are collected, suggested modifications are incorporated, and successive prototype versions eventually evolve into the complete system. Sometimes RAD and life-cycle development are combined: a prototype is produced to determine user requirements during the initial system analysis stage, after which life-cycle development takes over. After an installed system is handed over to its users and operations personnel, it will almost invariably be modified extensively over its useful life in a process known as system maintenance. For instance, if a large system takes 2 years to develop, it will typically be used and maintained for some 5 to 10 years or even longer. Most maintenance is to adjust the system to the organization's changing needs and to new equipment and system software, but inevitably some maintenance involves correcting design errors and exterminating software “bugs” as they are discovered.
    2014-07-20 18:07:20

  • Raymond Siwale Botswana give example of software resources?
    2014-07-11 23:07:42

    • Yai Deng Yai South Sudan Electronic document.
      2014-08-25 12:08:02
  • Reza Abbasi Iran What procedures are followed in the implementation phase?
    2014-06-22 15:06:12

    • Yai Deng Yai South Sudan Planning and announcing the implementation,acquiringthe hardware and software resources, preparing the physical facilities. Educating the participants and users, preparing an implementation schedule, changing over to new system.
      2014-08-25 12:08:44
    • Raymond Siwale Botswana one of them is educating participants and users
      2014-07-18 09:07:18
    • Satu Korhonen Finland f.ex. acquiring the resources, preparing the facilities and educating the users, changing over to the new system etc.
      2014-06-24 20:06:52
  • ToeToe Aung Singapore We should effectively use the data during data analysis while we are implementation the project.
    2014-06-21 08:06:22

  • Reza Abbasi Iran What procedures are followed in the implementation phase?
    2014-06-19 23:06:40

    • Yai Deng Yai South Sudan Answered.
      2014-08-25 12:08:31
  • Annette Weizbauer Germany Which resources are integrated into the existing system during the implementation phase?
    2014-06-15 12:06:47

    • Yai Deng Yai South Sudan Those ones I mention above.
      2014-08-25 12:08:03
    • Glyn Chapman United Kingdom Both the physical and the conceptual for instance say a MS windows programme Physical: updates Conceptual: The aim of the update. That's how I perceive it
      2014-07-21 18:07:27
    • ojo taiwo Nigeria PHYSICAL AND CONCEPTUAL
      2014-06-20 12:06:45
    • Reza Abbasi Iran The implementation phase is where physical and conceptual resources that are required for the project are obtained and integrated into the existing system to produce the final working system.
      2014-06-19 23:06:30
    • Parhalad Saini India Physical and conceptual resources are integrated into the existing system during the implementation phase.
      2014-06-17 11:06:30
Loading Menu