Architecture design is a difficult process so it is fairly easy for novice analysts to make mistakes. One common mistake that is made is not considering the future of the system. It is important to create a sustainable system that not only meets current needs but future needs as well.
Another common mistake of novice analyst's is not considering all aspects of system security that need to be factored into the architecture design. It’s important to include the system value, access control, encryption/authentication, and virus control.
Mistakes are common and can be very costly. One mistake that can end up costing than the hardware, software, and equipment alone is infrastructure planning mistakes. Infrastructure planning is key in ensuring that your system can perform all the functions necessary to the business.
Mistakes can happen at anytime, especially unexpected mistakes. One of whioh is security. This mistake can detrimental to a company and potentially scar the business if the right implemntations are taken to include in the infrastructure
A common mistake that novice analyst’s make is the testability of the performance requirements. According to our book “each requirement must be measurable so that a benchmark comparison can be made”. With such attention to detail when creating performance requirements it lessens the chance of a poor performance requirement. When all the performance requirements work the way they should there should be little errors when they are implemented.
I cant find in chapter 8 where the text specifically lays out the Three Common Mistakes of novice analysts. What page did you all find this on? Or are we basing this off of the requirements?
One problem that I can think of is not properly calculating the hardware and software needs of a new system while planning its architechure. Both hardware and software can be extremely expensive, so having either too much or too little resources can be extremely costly and detrimental to the system. I think the most common thing that happens on this end is aquiring more resources than necessary. While you want to leave enough room for future expansion, you also don't want a costly resource to go unused.
Architecture design is a difficult process so it is fairly easy for novice analysts to make mistakes. One common mistake that is made is not considering the future of the system. It is important to create a sustainable system that not only meets current needs but future needs as well.
ReplyDeleteAnother common mistake of novice analyst's is not considering all aspects of system security that need to be factored into the architecture design. It’s important to include the system value, access control, encryption/authentication, and virus control.
ReplyDeleteMistakes are common and can be very costly. One mistake that can end up costing than the hardware, software, and equipment alone is infrastructure planning mistakes. Infrastructure planning is key in ensuring that your system can perform all the functions necessary to the business.
ReplyDeleteMistakes can happen at anytime, especially unexpected mistakes. One of whioh is security. This mistake can detrimental to a company and potentially scar the business if the right implemntations are taken to include in the infrastructure
ReplyDeleteA common mistake that novice analyst’s make is the testability of the performance requirements. According to our book “each requirement must be measurable so that a benchmark comparison can be made”. With such attention to detail when creating performance requirements it lessens the chance of a poor performance requirement. When all the performance requirements work the way they should there should be little errors when they are implemented.
ReplyDeleteI cant find in chapter 8 where the text specifically lays out the Three Common Mistakes of novice analysts. What page did you all find this on? Or are we basing this off of the requirements?
ReplyDeleteOne problem that I can think of is not properly calculating the hardware and software needs of a new system while planning its architechure. Both hardware and software can be extremely expensive, so having either too much or too little resources can be extremely costly and detrimental to the system. I think the most common thing that happens on this end is aquiring more resources than necessary. While you want to leave enough room for future expansion, you also don't want a costly resource to go unused.
ReplyDelete