Tech Papers
I thought I would share some of my papers I wrote for school with the world. Plus it helps people find my site on Google. Keep in mind there were requirements to which I had to adhere, which makes some of the papers flow a little weird.
In February of 2002, Microsoft unveiled to the world its new development platform named Microsoft .NET. The technology was preceded by years of speculation and rumor. .NET was developed from the ground up as a World Wide Web friendly framework and direct competitor of the well established Java platform. With almost three years and one revision under its belt, .NET has emerged as a major player in the world of programming.
In the information driven culture of today, programmers have two mainstream methods of data storage: relational database management system (RDBMS) and object-oriented database management system (OODBMS). Though both management systems focus on data storage, the underlying concepts behind the technologies are very different.
When dealing with a relation database management system, there are several ways in which to relate data. Depending on the required business rules, data may be related using a one-to-one, one-to-many, or many-to-many relationship.
Implementing a network/telecommunication system without a design would be like trying to build a house without a blueprint. It can be done, but it will be a maintenance nightmare. Even if the architect was capable of committing all the details of the construction to memory, what good does it do if the architect leaves or gets hit by the proverbial bus. The design is crucial to ensuring the network survives, even if the architect does not.
The design process is extremely important to any enterprise-level business systems. In the most successful systems, the design process encompasses over half the time of the development cycle; not counting maintenance. As with analyzing requirements, the methodologies and tools available for enterprise-level design vary.
It is a well known fact that a large majority of projects fail, regardless of the countless books, classes, and videos on the subject. Where does the fault lay? What truly indicates the success or failure of a system? With proper assessment of the business system, it is possible to not only know the requirements before hand but also what will indicate success or failure of the project.
Industry is changing, and as such so must the way in which applications are written to support industry. Enterprise-level business systems can no longer operate under the weight of multiple stand-alone applications, as was the method used for decades. With the advent of the Internet, businesses found that they were no longer separated by physical boundaries. The technology had finally arrived, but would industry be able to follow?