Introducing
Your new presentation assistant.
Refine, enhance, and tailor your content, source relevant images, and edit visuals quicker than ever before.
Trending searches
GROUP MEMBER
Name : Afsana Akter
ID : 19202103295
Name : Abu Bakar Siddiq Mim
ID : 19202103288
Name : MD. Hadisur Rahman
ID : 19202103307
Name : Nasir Uddin
ID : 19202103316
Name : Khadija Akter
ID : 19202103297
Supervisor:
Sadah Anjum Shanto
Lecturer
Department Of CSE
Designing the Recommended System
For designing our system we use those diagram.
DFD:
A data flow diagram (DFD) maps out the flow of information for any process or system. It uses defined symbols like rectangles, circles and arrows, plus short text labels,
to show data inputs, outputs, storage points and the routes between each destination.
Use Case Diagram:
A key concept of use case diagram is that it helps us design a system from the end
user’s perspective.
Activity Diagram:
Activity diagram is another important behavioral diagram. Activity diagram is essentially an advanced version of flow chart that modeling the flow from one activity to another activity.
Class Case Diagram:
A class diagram is a structure diagram that describes the structure of a system by showing the system’s
classes, their attributes, operations (or methods), and the relationships among ob-
jects.
Sequence Diagram:
A sequence diagram shows the
sequence of messages passed between objects. Sequence diagrams can also show the
control structures between objects
Identifying Problems:
We didn’t yet complete our project and our project is not well developed.
• Fist of all we have to finding the problems which we need to improve
• We have to improve our design
• Have to improve the Features
• Overcome the old procedures
• To make more interesting online Quiz.
The seven phases of the SDLC:
1. Identifying Problems.
2. Determining Human Information Requirements.
3. Analyzing System Needs.
4. Designing the recommended system.
5. Developing and documenting system.
6. Testing and maintaining the system.
7. Implementing and evaluating the system.
Analyzing System Needs
*System must store information about users (Student and Teachers), tests, questions and result
* System should able the teacher to punch tests
* Each teacher should be able to punch many tests
*System should do not allow unauthorized user to enter the system
*Each student should be able to attempt many tests
* System should keep and display the results of Students
*System should support test which one or more question dependent on it
*System should allow the administrator to delete and update tests and questions dependent on it.
Developing and Documenting Software
Determine Human Information Requirements:
* Creating new quizzes
* Check whether the answer to the quiz is correct or incorrect.
* Points are given if the answer to the quiz is correct .
* Creating a leaderboard based on the mark of the user's quiz.
* They want to make it more easier.
* They want more faster service.
* Show the negative marks.
* They want to know which of their answers are wrong.
* Showing the correct ans of wrong questions.
* More secure.
Testing and Maintaining the System
System Testing is basically performed by a testing team that is independent of the development team that helps to test the quality of the system impartial.
There are many types of testing in a System, such as:
*Performance Testing
*Load Testing
*Stress Testing
*Scalability Testing
Maintaining the system:
1-The administrator will be able to add new questions in the quiz.
2-The administrator will be able to select the start and end date for quiz.
3-The system will maintain different subjects for quizzes.
4-The administrator will be able to select maximum number of questions to be included in the quiz.
5-The administrator will be able to edit or delete a question.
6-The application will enable the quiz for users once the start date is active.
Implementing and Evaluating the System: