Student Profiling System. Group 2.

Views:
 
Category: Entertainment
     
 

Presentation Description

Technology used is XML and XSLT

Comments

Presentation Transcript

Student Profiling System: 

Student Profiling System XML and XSLT

Introduction: 

Introduction Technology evaluated is XML and XSLT There is a need to computerise student profiles because: Two tier architecture used Less security Time consuming Difficult to manage

Scenario and Cross-platform compatibility: 

Scenario and Cross-platform compatibility Will use 3-tier architecture Variety of languages New system will be viewable across various browsers Help for the visually impaired

Possible solutions: 

Possible solutions HTML & CSS Better display Widely acknowledged Outdated JavaScript Increased interactivity Message alerts Used for malicious purposes Ajax Simultaneous updates Easy search Classic web pages need reloading Cannot cope with large requests

3-tier architecture: 

3-tier architecture Three separate tiers exist each with its own responsibility: client tier, middle tier and data tier. More secure and easier to maintain Updates can be made faster Increased user capacity Middle tier Data tier Client tier

Solution - XML/XSLT: 

Solution - XML/XSLT XSL stands for EXtensible Stylesheet Language and is a style sheet language for XML documents . (Source: http://www.w3schools.com/ xsl / tryxslt.asp?xmlfile = cdcatalog&xsltfile = cdcatalog ) A chunk of XML tagged data can be organised using XSLT templates

Pros and cons of XML and XSLT: 

Pros and cons of XML and XSLT Pros: Fast organisation of data Saves money and paper Cons: XSLT professionals required Costly XML files

Technology in 3 Tier Architecture : 

Technology in 3 Tier Architecture XML is in the middle tier as it contains tagged and can be sent over the internet XSLT is in between the client and middle tier because users can view it in different formats XSLT Middle tier Data tier XML Client tier

Conclusions: 

Conclusions XML and XSLT is a good solution to the student profiling system. However, a better solution could be Ajax, because: Webpages do not need to refreshed manually It has a feature known XMLHttpRequest which allows pages not compatible with Ajax to be used. Uses HTML, JavaScript and XML hence making it more user friendly and accessible Uses up less bandwidth, making it faster