Skip to content

Current System and proposed system:

Preeti Sharma edited this page Apr 20, 2015 · 7 revisions

##Current System and Proposed System:

  1. Current System
  2. Limitations of Current System
  3. Proposed System
  4. Objective of Proposed System

##Current System Current System is developed in ASP.net ,this prototype was created keeping in mind that developer should not need to make it complex,but debugging of code is hard plus asp.net is dying technology due to which there is shortage of asp.net developers.This site is made with the idea of centralization of updation i.e any changes were made by the developers only .Since updation of information can not be done properly, this is the main failure of the present site.

##Limitations of Current System

  • Current site is fully static.
  • In the current version of site updating the information as well as uploading new information is a difficult task.
  • Documentation of old site is not available.
  • It’s not easy to include new member in development team because project didn't properly planned and didn't modulated.
  • In the earlier version of site Code is not intended and don't mention comments in code.

##Proposed System The IIPS website being created will be a decentralized system, where authorized users(maintainer) will be responsible for its updating so that students can get updates of the recent activities.The students can view their result,forth coming events and any recent information in real time.

##Objective of Proposed System: To create a simple,easy to navigate, effective website with mobile responsive design which automates the result procedure,request issuing system (bonafide, marksheets) inside IIPS.The main objective of the project is decentralization so that website can be updated in real time .The intended users of the system are students, staff, faculties and visitors.

Clone this wiki locally