In partial fulfillment of the requirements for the Bachelor of Science in Computer Engineering (CSE) degree. Shirajul Islam, ID No., Department of Computer Science and Engineering, Daffodil International University has been accepted as satisfactory in partial fulfillment of the requirements for the Diploma in Computer Science and Engineering and approved for style and content. Department of Computer Science and Engineering Faculty of Science and Information Technology Daffodil International University.
We declare that the project report titled "CLASS TO DO" was made by us under the supervision of Nadira Anjum Nipa, Lecturer, Department of Computer Science. We also declare that neither this project nor any part of this project has been submitted elsewhere for the award of any degree or diploma. We are grateful and convey our best wishes to our Supervisor Nadira Anjum Nipa, Lecturer, Department of Computer Science and Engineering wishes Daffodil International University, Uttara, Dhaka.
To complete the project, the author asked all the faculty members and professors of Uttara campus, Head of Department of Computer Science and Engineering Dr. Syed Akhter Hossain and other faculty members would like to express their sincere gratitude to the staff of CSE Department of Daffodil International University.
Introduction
- Motivation
- Objectives
- Methodology
- Organization of the Report
- Expected Justification
To use our application on your mobile phone, you must have an internet connection. Google's security is very high, so we don't need additional security in our applications. In the search function of our application, a user can quickly find a list of other users based on their profile information.
For the user attraction, we will develop the user interface and increase the security of our app. By using this app students can do their class, class work and attend their exam on time. We just want to share our idea and we are building our app in the initial stage.
Background
- System Development Life Cycle
- Phase of Software Development Life Cycle
- Initial Idea
- Feasibility Study
The software development life cycle describes the various phases and related activities of the system development life cycle in details. After completing the initial idea, the systems analyst (who studies the system) drafts a proposal and presents it to the user. Once the system proposal is acceptable to management, the next stage is to investigate the feasibility of the system.
At that stage we know how long a project should take and how the results should be presented. The feasibility study must be completed if the development of the project is economically and organizationally supported. The central role of the analyst in the feasibility study is to analyze the actual system at a high level.
Data flow diagrams (DFDs) are used to describe how the actual system works and to illustrate known problems.
Requirement Specification 3.1 Introduction
- Permission Requirement
- Security of Database
- Threats to System Security
- Conclusion
- Design Specification
- User Interface Prototyping
- ER Diagram
- DFD Diagram
- Technology Used
User must also first login with a valid email address and provide their email password to open an account. If any students don't want to miss his class attendance and take the exam on time, we think he/she will get a good reward if he/she uses this application. An important part of designing and prototyping in every application is the concept of phase.
Design can be more effective and reliable for users important as the most user-friendly interface. In these apps we have used Android Studio, Android virtual device and worked on Flatter platform using dart language. It was developed by Google and used to create mobile, desktop, server and web applications.
Post Database
Comments Database
Timeline Database
Routine Database
User Profile
Final Output
This page is for user authentication and from here each user can choose their used email address or add a new account. Here the logged in user can see the follower's post on the timeline page and post a comment if they wish. Here users can set their day-by-day routines. Users can add or remove routines here if they wish, so they reach all users and are seen by everyone.
On the activity page, the user can see other users' activities, comment, like, play their posts, and if someone follows him, he can see them. Our apps here automatically suggest usernames as soon as you enter a username to search for users on the search page. On the profile page, the user can see the number of his posts, the number of his followers and the number of people he follows and his posts. Here you will see your name and username and your details.
If you wish, you can delete your message here and you will be presented with this option via a pop-up page. On this profile editing page, you can change your display name and change your biography and upload it to your profile by clicking the Update Profile button. Here you will also find the Logout button that you can click to close apps.
Implementation and Testing 5.1 Introduction
- How it works
- Goals of “Class-To-Do”
- Testing
- Automate user interface test
- Test UI Performance
- Security Testing
- System Testing
The main reason behind creating these apps is that we want students to get good results. Today most of the students can't remember these during exams during their classes due to which they can't attend their classes on time, can't do their exam preparation , cannot join their classes properly due to which their exam results are at maximum times bad. But if a student uses our apps then he will be able to complete his classes on time and he will be able to prepare his exam on time and give his exams on time. properly, so that its result is much better. than before. Also by using our applications they will be able to share any information with each other in these applications and anyone will be able to collect that information and accordingly they will be able to prepare for work in class. So after the completion of our project we are sure that it can fulfill our goals. Testing is a very important part of any Android application. Before release any Android application should be tested. First we should have checked that all the function works or not, all the data is checked so that the user does not provide any unnecessary data. Next we need to check whether our expected result is coming or not. If the expected result has come than ok, but otherwise we have to detect the error and start testing again. Another important part of Android application is verification and validation. Each user who logs into our applications will be provided with their valid email and valid password.
The user interface ensures that our Android application meets functional requirements and achieves a high quality standard. Then the user can use our application in a very friendly way. We know that many people in the world use different versions of Android and there are many people who use iOS. That's why we develop our apps in Flutter so that iOS users and Android users can use our apps. The user interface of any application is more important than any other part. The user interface is more important than the backend. The first time a user notices the UI when viewing an application, they check the backend of the app to see if they like the user.
Security is one of the biggest issues with any Android application. Due to the lack of security, people lose their own data and personal information by using many Android applications and get harassed. Before we create an Android application, we must keep the security issue in mind. In "Class-To-Do" we used the Firebase database. Google is responsible if data from Firebase is lost or stolen. We now know that Firebase is more secure than other databases, so we haven't done anything for extra security. Our app may not install on every device and a bug may have been found. So testing methods can solve all these problems. The system testing of our project went through 3 steps: UI testing, integration testing and unit testing.
Conclusion and Future Work 6.1 Conclusion
Future Implementation and Limitation
APPENDIX
