The key factors in selecting a methodology are: >Clarity of the User Requirements: Iterative systems are good, but System Prototyping, throwaway prototyping and Agile development systems work best.
>Familiarity with Technology: Iterative systems are good, but Throwaway Prototyping systems work best.
>System Complexity: Waterfall, Parallel, V-Model, Iterative, and Agile Development systems are good, but Throwaway prototyping systems work best.
>System Reliability: Waterfall, Parallel, Iterative, and agile development systems are good, but V-Model and Throwaway prototyping systems work best.
>Short Time Schedules: Parallel and Throwaway prototyping systems are good, but Iterative, System prototyping, and agile development systems work best.
>Schedule Visibility: Throwaway prototyping and Agile development systems work good, but Iterative and System prototyping systems work best.
Well, the main factor to keep in mind is that which system will be best for the company. The project manager then needs to focus of the clarity of the user requirements, familiarity, complexity, and reliability of the technology. They must also take in to account the time frame of the system and the schedule visibility, which knows whether or not the project is on schedule and hoping that there are not any setbacks to increase the time to finish the project.
The first criteria for selecting a methodology is the clarity of user requirements. System prototyping and throwaway prototyping work the best here when requirements are unclear. Second, we have familiarity with technology. When the technology is unclear throwaway prototyping usually works the best. Third we have system complexity. Throwaway once again works best when systems have a high complexity. The fourth criteria we have is system reliability. The V-model and throwaway prototyping usually works best when reliability is important. The fifth criteria we have is short time schedules. Iterative, system prototyping, and agile development usually work best for this criteria when time lines are short. The final criteria we have is schedule visibility. Iterative and system prototyping usually work the best in this situation when trying to calculate if the project is on schedule and the expectations are reasonable.
The following are key factors to consider when selecting an appropriate development methodology:
User requirements: if the users requirments are unclear then system prototyping or throwaway prototyping will be a more appropriate method to consider.
Familiarity with technology: throwaway prototyping is particularly useful when the technology that users and analysts are working with is unfamiliar, this alows them to experiment and become more familiar.
System complexity: complex systems require careful and detailed analysis and design which are also best handled by a throwaway prototype system.
System reliability: when reliability is extrememly important the V-model can be used because it emphasizes testing, throwaway prototyping is also another very appropriate model to consider when reliability is highly important.
Short time schedule: RAD methods are well suited for projects within a short time crunch because they aim at improving the speed of development. System prototyping and iterative development are also great choices because they allow adjustment of the functionality of the system depending on delivery dates.
Schedule visibility: RAD methodologies are best suited here because they move critical design decisions from the end to earlier on in the process allowing for project managers to keep the team and development on task.
The key factors in selecting a methodology are:
ReplyDelete>Clarity of the User Requirements: Iterative systems are good, but System Prototyping, throwaway prototyping and Agile development systems work best.
>Familiarity with Technology: Iterative systems are good, but Throwaway Prototyping systems work best.
>System Complexity: Waterfall, Parallel, V-Model, Iterative, and Agile Development systems are good, but Throwaway prototyping systems work best.
>System Reliability: Waterfall, Parallel, Iterative, and agile development systems are good, but V-Model and Throwaway prototyping systems work best.
>Short Time Schedules: Parallel and Throwaway prototyping systems are good, but Iterative, System prototyping, and agile development systems work best.
>Schedule Visibility: Throwaway prototyping and Agile development systems work good, but Iterative and System prototyping systems work best.
Well, the main factor to keep in mind is that which system will be best for the company. The project manager then needs to focus of the clarity of the user requirements, familiarity, complexity, and reliability of the technology. They must also take in to account the time frame of the system and the schedule visibility, which knows whether or not the project is on schedule and hoping that there are not any setbacks to increase the time to finish the project.
ReplyDeleteThe first criteria for selecting a methodology is the clarity of user requirements. System prototyping and throwaway prototyping work the best here when requirements are unclear. Second, we have familiarity with technology. When the technology is unclear throwaway prototyping usually works the best. Third we have system complexity. Throwaway once again works best when systems have a high complexity. The fourth criteria we have is system reliability. The V-model and throwaway prototyping usually works best when reliability is important. The fifth criteria we have is short time schedules. Iterative, system prototyping, and agile development usually work best for this criteria when time lines are short. The final criteria we have is schedule visibility. Iterative and system prototyping usually work the best in this situation when trying to calculate if the project is on schedule and the expectations are reasonable.
ReplyDeleteThe following are key factors to consider when selecting an appropriate development methodology:
ReplyDeleteUser requirements: if the users requirments are unclear then system prototyping or throwaway prototyping will be a more appropriate method to consider.
Familiarity with technology: throwaway prototyping is particularly useful when the technology that users and analysts are working with is unfamiliar, this alows them to experiment and become more familiar.
System complexity: complex systems require careful and detailed analysis and design which are also best handled by a throwaway prototype system.
System reliability: when reliability is extrememly important the V-model can be used because it emphasizes testing, throwaway prototyping is also another very appropriate model to consider when reliability is highly important.
Short time schedule: RAD methods are well suited for projects within a short time crunch because they aim at improving the speed of development. System prototyping and iterative development are also great choices because they allow adjustment of the functionality of the system depending on delivery dates.
Schedule visibility: RAD methodologies are best suited here because they move critical design decisions from the end to earlier on in the process allowing for project managers to keep the team and development on task.