Teaching Management System-Requirement Analysis

1. System Description
The Teaching Management System (TMS) is an auxiliary teaching management system used by colleges within the university. Its main functions include the management of students' homework and teaching courseware.
2. Scenario Description
2.1 Teaching Management
2.1.1 instructor publishing Courseware
Teacher Li Si is a teacher in Java programming. He uses the Powerpoint Courseware in class and explains the code in eclipse. After class, many students asked him for the courseware and code. He felt that it was too troublesome to distribute the files one by one. He opened the TMS client, logged on to the system, and compressed the courseware and Code for publishing. In this way, all the students in the class he taught can see the courseware.
2.1.2 students complete homework
After logging on to the system, the student Zhang San can see the assignment and completion of each course. He opened An unsubmitted job and saw the question Requirements for the job. According to the job requirements, John completed the required job code in the external editor and compressed it into a file. He entered the job answer in the job editor and submitted the compressed file as an attachment. After submitting the assignment, the instructor can view the student's homework. After the instructor corrects the assignment, James can view the assignment's score and comments.
2.1.3 view courseware for students
Student Zhang San needs to preview the course Java programming before class, but there are many contents in the textbook. Where is the focus? He opened the TMS client. After logging in, he could see the courseware of the course. After opening the courseware, he prepared the course according to the courseware.
3. Functional Requirements
3.1 System Management
3.1.1 user management
3.1.1.1 system user management
3.1.1.2 School Department management
3.1.1.3 basic instructor Information
3.1.1.4 basic student information
3.1.1.5 import user data
3.1.2 Teaching Management
3.1.2.1 Basic course information
3.1.2.2 course class Maintenance
3.1.2.3 import course data
3.1.3 System Maintenance
3.1.3.1 permission settings
3.1.3.2 Data Backup
3.2 Teaching Management
Teaching management is the core module of the system and is used to assist classroom teaching.
3.2.1 courseware Management
3.2.1.1 publish Courseware
The instructor publishes the courseware, which can be viewed by all students in the specified course class. Required
Courseware title
Courseware description
Courseware type: Course/Experiment
Courseware attachment: files (1)
Course class: course class that can view courseware (*)
3.2.1.2 view Courseware
Students can view all the courseware published in their course classes.
Courseware is organized by course/type.
3.2.2 Job Management
3.2.2.1 assignment
Teachers and TAS can assign assignments for their course classes.
The job content includes:
Job title: title, used to display
Job description: job description
Job Attachment: job attachment (1)
Submission time: The deadline for students to submit their homework
Assignment type: group assignment/personal assignment
Course class :(*)
3.2.2.2 submit a job
Students can submit unsubmitted and returned assignments. After submitting a job, you cannot modify it.
If the assignment type is personal assignment, each student can submit the assignment. If the assignment type is group assignment, only the group leader can submit the assignment, and other students can only view the assignment.
The content of the submitted job includes:
Answer: text description
Assignment attachment: (1)
3.2.2.3 correction operations
The instructor scores the assignments submitted by the students, and the unqualified assignments can be returned.
Personal homework, score directly.
For group assignments, if the group type is "average assignment", the score is the same for all team members. If the group type is "group leader assignment", only the total score is set. The score of the team members is allocated by the team leader.
When correcting assignments, enter:
Homework score: integer, which is defined by the instructor. For example, it can be a five-digit or a percentage system.
Job comment: Quick input is provided to extract the input content of the same job for quick input.
3.2.2.4 view a job
Students can view their homework. You can reply to the assignment and discuss it with the instructor.
3.2.2.5 job reply
The instructor can view the reply to the assignment.
Students can view their homework replies.
Special prompts for unread replies.
3.2.2.6 job query
Instructors can only view assignments in their course classes. You can query assignments by student ID, Student name, and assignment title. You can double-click the query result to open the job and view the job. You can return the job or rescore the job.
3.2.2.7 job statistics
Statistics can be made by class, homework, and students.
3.2.3 student group
3.2.3.1 group application
For the new semester, students can apply for a study group, which is approved by the course teacher. The content can be modified before approval, but cannot be modified after approval.
Required
Group Name
Team lead: (1)
Member :(*)
Assignment score assignment type: average assignment/team lead assignment
3.2.3.2 score assignment
Lists all assignments that need to be assigned. Only the team lead can assign scores.
3.2.4 Course Resources
3.2.4.1 FAQs
FAQs related to the course.
3.2.4.2 download resources
Students can download resource-related documents and installation programs.
3.2.4.3 course Forum
Each course provides a forum where you can discuss it.
3.3 instant messaging
3.3.1 address book
3.3.2 network hard drive
3.3.3 download center
School Management 3.4
3.4.1 Document Management
3.4.2 book management
3.4.3 Teaching Plan
3.4.4 instructor Profile
3.4.5 instructor Assessment
3.4.6 graduation internship
3.4.7 Employment distribution
3.5 e-commerce
3.5.1 online stores
3.5.2 advertising management
4. Non-functional requirements
4.1 friendly user interface
The program interface should be intuitive and easy to understand. Users can use it without special training. The program provides the following common functions on the interface:
Shortcut
Tooltip
Right-click menu
User help
4.2 Performance
The client loading time is less than 2 seconds.
The user login time is less than 2 seconds.
The response speed of key queries is less than 1 second.
Capacity 4.3
The number of users is about 30000, and more than 1000 concurrent users are supported.
4.4 Security
Only login users can use this system. The system provides different functions based on user roles. Illegal users cannot access the system's restricted functions.
The logon interface has the anti-attack function. When the password is incorrect for multiple times, the interface will be stopped for a period of time.
The user password is MD5 encrypted to prevent password leakage on the server.
5. Development and Target Platform
The system uses the CS architecture and communicates through the TCP/IP protocol.

Client: Use eclipse RCP for development.
Application Server: jboss4.0.4, which is fully implemented in ejb3.
Database Server: MySQL 5.0.
Development tools: Use eclipse 3.2 + WTP

All the system code is completed in Java, because the system is platform independent. Some program codes can be installed in most systems without modification. The system is designed and tested on Windows XP.
6. Risk Analysis
6.1 Technical Risks
Ejb3 specifaction has not been completed yet. JBoss's hibernate provides compatibility implementation, and there may be changes to specifications during the project period.
Eclipse RCP has certain technical difficulties and is difficult to get started.
6.2 personnel risks
There is a lack of jee and eclipse RCP developers. The project manager needs to study related technologies and develop basic class libraries and development guidance to lower the technical barriers for later personnel.
The exit of key personnel may result in project failure because there are few project personnel. Therefore, necessary documents must be completed during the development process.