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

ALISON: Diploma in Project Management


Comments about System development life cycle - The design phase

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

Latest Comments

  • Zinabie Tadesse Gebremedhin Ethiopia In this phase the processes and data required by the new system are defined. In most projects, there will be a number of different ways in which the problem can be solved - and consequently, in this phase, it is important that a number of different alternatives are investigated to ensure that the most efficient and effective solution is adopted. In this phase, the steps that are followed include: preparing a detailed system design identifying and evaluating alternative system configurations selecting the best configuration preparing an implementation proposal.
    2014-11-25 10:11:35

  • ESSOTOLOME BODJO China In this phase, the steps that are followed include: •preparing a detailed system design •identifying and evaluating alternative system configurations •selecting the best configuration •preparing an implementation proposal
    2014-11-19 06:11:54

  • Md Shohel Mahmud Bangladesh in this phase the most important thing is to implement the most effective solutions, considering the different ways, and finally to plan a new plan.
    2014-11-16 05:11:00

  • Cyrus Wanjohi Kenya In this phase the processes and data required by the new system are defined. a number of different alternatives are investigated to ensure that the most efficient and effective solution is adopted
    2014-11-16 04:11:31

  • Janvier Nyandamu Rwanda Is the the implementation proposal a part of design phase?
    2014-11-07 12:11:48

  • Nothando Gumpo United Kingdom The design phase, is where the new system will be designed. In this phase the processes and data required by the new system are defined. In most projects, there will be a number of different ways in which the problem can be solved - and consequently, in this phase, it is important that a number of different alternatives are investigated to ensure that the most efficient and effective solution is adopted.In this phase, the steps that are followed include;preparing a detailed system design,identifying and evaluating alternative system configurations,selecting the best configuration and preparing an implementation proposal.
    2014-11-06 01:11:38

    • Gerald Smith Jr. Sweden Okay
      2014-11-15 10:11:46
  • Assel Satpayeva Kazakhstan It would better to change the scope at this phase, than later on. Any changes at further phases will be more complicated to apply and drastically affect the cost increase.
    2014-10-22 08:10:48

    • Kenneth M Akahoho Ghana Yea you are right
      2014-10-22 23:10:30
  • Ralph Webster South Africa The design phase, as the name suggests, is where the new system will be designed. IT S THE VALUE ADDED SECTION. In this phase the processes and data required by the new system are defined. In most projects, there will be a number of different ways in which the problem can be solved - and consequently, in this phase, it is important that a number of different alternatives are investigated to ensure that the most efficient and effective solution is adopted. In this phase, the steps that are followed include: preparing a detailed system design identifying and evaluating alternative system configurations selecting the best configuration preparing an implementation proposal.
    2014-10-19 06:10:53

  • George Ugim Nigeria this is the most critical moment of a project.
    2014-10-10 19:10:58

  • George Fragos Greece The software development life cycle (SDLC) is a framework defining tasks performed at each step in the software development process?
    2014-09-29 09:09:26

  • Segedin Dragan United Arab Emirates How deeply I should identifying and evaluating alternative system configurations? As brand new project itself? And what I have than to interviewing different delivery teams whose are not in original plan? What about budget and design changes whose should be approved from customer than?
    2014-09-28 07:09:20

  • richard geli Ghana Yai Deng Yai, why shoud 4 design sample be the most appropriate number of design samples?
    2014-09-10 17:09:56

  • ANNETTE ROBINSON United States of America Can more than one design be used for a single project? Or would theses be consider as a subset of the major design?
    2014-09-08 23:09:07

  • Samuel Kofi Odoi Ghana How many designs samples should be make for the projects especially when it comes to system design?
    2014-08-14 20:08:29

    • Kenneth M Akahoho Ghana Kofi,I suggest you use efficient design sample
      2014-10-22 23:10:21
    • Yai Deng Yai South Sudan Four designs.
      2014-08-25 11:08:13
  • Vikram Vasant Rotkar United Kingdom How to minimize the risk associated with implement phase?
    2014-07-21 16:07:01

    • Yai Deng Yai South Sudan Through project analaysis.
      2014-08-25 11:08:48
  • 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 17:07:45

    • richard geli Ghana Splendid reaction, Jones Hanungu Munang'andu. Very insightful.
      2014-09-10 17:09:52
    • Yai Deng Yai South Sudan It is too long.
      2014-08-25 11:08:14
  • 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 17:07:33

    • Yai Deng Yai South Sudan It is not fit into this topic.
      2014-08-25 11:08:48
  • 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 17:07:17

  • 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 17:07:02

  • Raymond Siwale Botswana dos the design include drawings?
    2014-07-17 10:07:19

    • Yai Deng Yai South Sudan Yes to some point.
      2014-08-25 11:08:21
Loading Menu