Navigation bar
  Start Previous page
 22 of 109 
Next page End Contents  

FYP Final Report v1.0.0
Copyright and All Rights Reserved To: Pee-Lo Team @2003/04
22
3.1 Solution Architecture Programming Model
Since we build the system using the Microsoft .NET platform, the programming model is based on
mapping the Microsoft .NET technology to our solution architecture (refer Figure 3).
Figure 3: Programming Model Diagram
ASP .NET will be used to produce dynamic web pages for all desktop, PDA devices and also tablet
PC.  ASP.NET Mobile, on the other hand, will be used by cell phones to render output it desires. 
Desktop computers running on Windows OS have an alternative access which is through
applications running on Windows OS and either VB .NET or C# will be used to program them.
Business Logic will be separated from the presentation layer and all logic dwells in a separate
container known as code behind in Microsoft .NET.  The business logic will programmatically use
ADO .NET to access the database at the backend.  All these will be contained in the second and
third layer in the diagram of Figure 3.  
The whole point of separate the logic from the client side is to enable the system being really
robust.  Developers can update the logics without going to do much alteration at the client side. 
Coding changes can be applied through just a single update in the WSDL files dwelling at the client
side.  
However, if the changes are major and it involves some GUI changes, then we still need to do
some changes on the client side.  Then again, this will be simpler since what the developers should
focus on is only on the GUI and not the business logic.
http://www.purepage.com Previous page Top Next page