Design and Implementation of Interactive Multimedia Book Platform
1. Requirements sorting
There are three roles in the system, author, reader, and system administrator, with a variety of terminal forms: mobile phones, browsers, and desktop software. The following analyzes system requirements from several perspectives
1.1, functional requirements
Author side:
Red is your own perfect demand, mainly related to data feedback and indicator monitoring
From a functional point of view, the author needs to be able to meet
- Editing functions for books and exercises, including article directories, article content, etc., third-party software can be embedded in articles
- The preview function of the editing result can preview the effect of each end during the editing process
- Specify the appropriate end-side type of the article, and can specify the end-side type of the article to display
- Statistical preview of the reading situation after the article is published
Reader side:
Red is for your own perfect needs, and needs to meet the reader's feedback functions, such as comment annotations, and various retrieval logic implementations
From a functional perspective, the main needs of the reader are:
- Reading needs, reading needs in various ways
- Retrieval needs, able to search books by title, author, etc.
- Practical requirements, able to call up third-party plug-in practice, and be able to make simple judgments on the correctness of practice
- Feedback requirements, ability to annotate article content, and grade textbooks
1.2, quality requirements
1.3, design constraints
- Reader apps, web, and desktop applications use unified code
- Call out third-party software to call through a unified plug-in model, transparent to readers
- Prioritize front and back end js + nodejs + mongodb
- Author-side independent deployment
1.4, process constraints
- Only when the author publishes the book can the data be imported into the end-side system
2. Conceptual prototype design
2.1 Reader / author use case diagram
2.2 System data model
3. In-depth analysis and design of key use cases (eg reader timing diagrams)
4. Design
4.1 Design class diagram
1. Requirements sorting
There are three roles in the system, author, reader, and system administrator, with a variety of terminal forms: mobile phones, browsers, and desktop software. The following analyzes system requirements from several perspectives
1.1, functional requirements
Author side:
Red is your own perfect demand, mainly related to data feedback and indicator monitoring
From a functional point of view, the author needs to be able to meet
- Editing functions for books and exercises, including article directories, article content, etc., third-party software can be embedded in articles
- The preview function of the editing result can preview the effect of each end during the editing process
- Specify the appropriate end-side type of the article, and can specify the end-side type of the article to display
- Statistical preview of the reading situation after the article is published
Reader side:
Red is for your own perfect needs, and needs to meet the reader's feedback functions, such as comment annotations, and various retrieval logic implementations
From a functional perspective, the main needs of the reader are:
- Reading needs, reading needs in various ways
- Retrieval needs, able to search books by title, author, etc.
- Practical requirements, able to call up third-party plug-in practice, and be able to make simple judgments on the correctness of practice
- Feedback requirements, ability to annotate article content, and grade textbooks
1.2, quality requirements
1.3, design constraints
- Reader apps, web, and desktop applications use unified code
- Call out third-party software to call through a unified plug-in model, transparent to readers
- Prioritize front and back end js + nodejs + mongodb
- Author-side independent deployment
1.4, process constraints
- Only when the author publishes the book can the data be imported into the end-side system
2. Conceptual prototype design
2.1 Reader / author use case diagram
2.2 System data model
3. In-depth analysis and design of key use cases (eg reader timing diagrams)
4. Design
4.1 Design class diagram