February 18, 2008
Obsolete Web Server
- The web server is quite old. The .NET platform that it is using is 5 years old (ASP.NET 1.1), which in IT terms is an eternity. What this means is that if we use the professor’s web server, we will not be able to leverage the productivity enhancements of ASP.NET 3.5, which could throw off our project timeline.
Shared Hosting
- Since our site is hosted on a shared web host and database, there is a high risk that other websites will impact our site’s performance and security.
Cross-Domain Communication
- Our web server is hosted by AspSpider.net and our database is hosted by IXWebHosting.com. The cross-domain communication adds risk since there could be a breakdown in communication with neither host taking responsibility.
Virtual Technical Team
- Having a virtual team adds risk that doesn’t exist in a team that is physically located in the same office. If a web developer needs the DBA to create a Stored Procedure in the database, it can be done in the matter of minutes in a traditional team. In a virtual team, however, the turnaround time could be in hours or even days.
Lack of Source Control
- The web application code is being maintained in Mohammad’s machine, the DDL script for the database is being maintained in Leong’s machine, and the web graphics is being maintained in Ed’s machine. If any one of these machines go down, we risk losing many person-hours of work.
RSS feed for comments on this post. TrackBack URL
You must be logged in to post a comment.
All good stuff, thanks for putting these together!
I have thought of some additional technical risks that might be appropriate to our project:
* Diversity of targeted software platforms:
Our test plan is limited to Windows base environment, some bugs might remain unknown.
* Lack of system availability control
These include the vulnerabilities cause by hackers, malicious code (such as viruses, worms, Trojan horses), system component failures, software flaws, and human errors.
Please advice.
Thanks,
Leong.
Comment by Leong — February 18, 2008 @ 3:37 pm
How is the authetication done? Server of database or both?
Comment by oge — February 19, 2008 @ 12:57 am
How about DoS (denial of service). Is it possible for the site be unavailable or slow as a result of too many users logged on @ the same time?
Thanks
Comment by oge — February 19, 2008 @ 12:59 am
Very good! The only thing I might add are ways to mitigate these risks, if any.
Comment by admin — February 20, 2008 @ 12:44 am