System Design Project

This document presents a comprehensive system design for a faculty and student web portal. It begins by outlining both functional and non-functional requirements, including details on hardware and software specifications (MySQL, JSP, HTML, CSS, AJAX, Java). The core of the document consists of detailed UML diagrams: a class diagram illustrating the system's entities and their relationships, a use case diagram depicting the interactions between actors (students, faculty, supervisors, department heads) and the system, and sequence diagrams illustrating the flow of actions for specific use cases (student and supervisor). Each use case is thoroughly described, outlining preconditions, postconditions, and various flow scenarios. Finally, a report section discusses the chosen order of tasks (requirements, use case diagram, class diagram, sequence diagrams, use case descriptions) and justifies the rationale behind this approach. The report also reflects on how the project would be approached in a real-world setting, emphasizing the use of scripting languages for validation and a robust, secure system with administrative capabilities.

[ FACULTY AND STUDENT WEB PORTAL]
SYSTEM DESIGN
Student Name:
Student ID:
Course Name:
Course ID:
Faculty Name:
University Name:

1

2
Contents
New System Requirements List.......................................................................................................3
Class Diagram..................................................................................................................................6
Use Case Diagram...........................................................................................................................7
Sequence Diagram...........................................................................................................................9
Use Case Description.....................................................................................................................13
Task 6: Report................................................................................................................................21

3
New System Requirements List
Functional 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 student
also 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.

4
9. Response time: The response time of system is lesser as much as possible for user
convenience.

5
Hardware Requirements:
Hard Disk: 100 GB
RAM: 2 GB
Software Requirements:
Operating System: Windows 7
Front End: JSP, HTML, CSS, AJAX
Back End: MySql
IDE: Netbeans 8.0
JDK: Jdk 8

6
Class Diagram

7
Use Case Diagram

8

9
Sequence Diagram
Sequence diagram for Student

10

11
Supervisor Sequence Diagram