Ask a question from expert

Ask now

Faculty and Student Web Portal: System Design

12 Pages629 Words1131 Views
   

Added on  2019-09-13

Faculty and Student Web Portal: System Design

   Added on 2019-09-13

BookmarkShareRelated Documents
[ FACULTY AND STUDENTWEB PORTAL]SYSTEM DESIGNStudent Name: Student ID: Course Name: Course ID:Faculty Name: University Name:
Faculty and Student Web Portal: System Design_1
1
Faculty and Student Web Portal: System Design_2
2ContentsNew System Requirements List.......................................................................................................3Class Diagram..................................................................................................................................3Use Case Diagram...........................................................................................................................3Sequence Diagram...........................................................................................................................5Use Case Description.......................................................................................................................5
Faculty and Student Web Portal: System Design_3
3New System Requirements ListFunctional Requirement:1.It is assumed that the large number of students or faculty records could be saved into database.2.It is assumed the web portal must be secured by login id and password.3.This is supposed that user interface is easy to understand and use.4.The student can easily login and select project topic from the given topic list. The studentalso able to request for supervisor easily.5.The all frequently updated data is saved into database successfully.Non-functional Requirements:1.The user who operates the web portal can easily interact with the system and the 2.Accessibility: The student and the faculty staff can access the portal from anywhere and at any time.3.Capacity, current and forecast: It is assumed that the new system will handle the large number of student’s data.4.Compliance: No error or bug occur at the user end while using this.5.Efficiency: This is assumed that the new system will be efficient by keeping updated data.6.Maintainability: If in future any functionality need to be added to this system then it can be done easily without affecting he old code functioning. 7.Privacy: Every user has their own login id and password.8.Reliability: When user access the database and made any changes in the required details then these details equally updated to all relevant tables.9.Response time: The response time of system is lesser as much as possible for user convenience.
Faculty and Student Web Portal: System Design_4

End of preview

Want to access all the pages? Upload your documents or become a member.