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

12

13
Use Case Description
Department Head Use case description:
Actor: Department Head
Precondition:
1. He/she must the part of the University of that Department.
2. He/she knew the login id and password
3. He/she has the internet connection
Post condition:
1. Logout to system
Flow1:
1. Login to online web portal
2. View staff list
3. Select project coordinator
4. Logout
Flow2:
1. Login to web portal
2. View staff details
3. Set quota for each professor
4. Logout

14
Flow3:
5. Login to web portal
6. View staff quota details
7. Increase staff quota
8. Logout
Project Coordinator Use Case diagram:
Precondition:
1. He/she must the part of the University of that Department.
2. He/she knew the login id and password
3. He/she has the internet connection
Post condition:
2. Logout to system
Flow1:
1. Login to web portal
2. Add new student details
3. Logout
Flow2:

15
1. Login to web portal
2. View student list who has no supervisor
3. View available list of professors
4. Assign supervisor and second marker to students
5. logout

16
Flow3:
1. Login to web portal
2. View the students reports and finalize marks
3. Print student’s marks to send registry office.
4. logout

17
Student Use Case Description
Actor: Student
Precondition:
1. Student of that university
2. He/she enrolled to that university
3. He/she must the last year or last semester student of university
Post condition:
1. Details are saved to database
2. Logout
Flow1:
1. Register to web portal
Flow2:
1. Login to web portal
2. View available Supervisor list and the project topics
3. Request for supervisor with a project topic
4. Wait for approval
5. Logout
Flow3:
1. Login to system
2. View supervisor time availability for appointment
3. Select time slot and request for appointment
4. Logout

18
Flow4:
1. Login to system
2. View the appointment approval status
3. Logout
Flow5:
1. Login to portal
2. Submit the report
3. Logout
Supervisor user case description:
Actor: Supervisor
Precondition:
1. Supervisor knew the login details
2. He/she has the internet connection
Post condition:
1. Logout
Flow1:
1. Login to system
2. Add or delete project topics
3. Logout

19
Flow2:
4. Login to system
5. View the student project topic request and approve them
6. Send this detail to Project coordinator
7. Logout
Flow3:
1. Login to system
2. View the student project topic request and disapprove them
3. Logout
Flow4:
1. Login to system
2. View the student appointment request and approve request
3. Logout
Flow5:
1. Login to system
2. View the student appointment request and disapprove request
3. Logout
Flow6:
1. Login to system
2. Add free time slots for appointment
3. Logout

20
Flow7:
1. Login to portal
2. View student report details and mark them
3. Logout
Flow8:
1. Login to portal
2. Edit the student mark details
3. Logout

21
Task 6: Report
1. Order of tasks:
 A list of user requirements (Task 2)
 Design use case diagram (Task 4)
 Design class diagram (Task 3)
 Design sequence diagram (Task 5(a))
 Describe the use case diagram (Task 5 (b))
2. Why I choose this order? , did it work?
 Make the list of requirements:
Description of task and how I do this?
To do this task, first I have analyzed the task and have gone through the task description.
Then I have finalize the list of all requirements like functional and non-functional
requirements. The functional requirements are the technical requirements. The non-
functional requirements are included in system proficiency, response, nice user interface,
robustness of the system. There are two more additional requirements these are software
and the hardware requirements.
Why I choose this as first step?
When we analyze the system then we come to know the complete role of the system and
the actor who are going to use this system. After doing this task first we come to know
about the various actors relations.
 Secondly I have designed the use case diagram by finalizing the all actors and their roles
from the given case study. Then I have write the use case descriptions for all the actors
separately.

22
Why I choose this as second step?
After first step we knew the actors and their actions so it is easy to draw the use case
diagram.
 After reading the case study and designing the use case diagram it becomes easy to
design the class diagram. To design the class diagram, first I have think about the
database design and the user interface through which every actor will go to connect with
the online web portal. I finalized the some forms and then thought to be with only one
GUI class.
Why I choose this as third step?
This become easy to design the class diagram after analyzing the requirements and the
actors and their roles in this system.
 In last step I have designed the sequence diagrams for each student and supervisor who
are included in this portal. The every step sequence is clearly defined in the sequence
diagram.
Why I choose this at last?
After defining the class entities it become easy to explain the exact flow of every action
for actors by using the entities names. This diagram is a pictorial description of every
actor action with system. This diagram also explains the system flow between various
system entities.
3. How would I do it? , Had this been a real life project?
Ans: This project is inspired from many real life projects that are University web portals.
I have search through many web portals like this and took some ideas to design this
project plan. The some project requirements are imaginary and some are taken by some
web portal ideas. So according to this given case study I have designed the whole idea
and come out with the number of users for this web portal. This will be completely online
system. I have plan to design this project using some scripting languages and MySQL
database to design this fully functional. The whole database is designed in MySQL. I will
use of java language to do this project. Scripting languages are used for validation and
designing the web portal in better look. As in earlier steps I have done all project
blueprint, now this time is easy to design and develop the code for this project. I will add

23
user’s registration part in this and the administration. There will be one more user that is
admin who will add, update or delete any user information or any other information in
under authorization. This system will be robust. This will be try to keep whole data
consistent.