bla bla bla

1. Meeting Management System
Course Code: CSE 400
School of Engineering
Department of Computer Science And Engineering
Sylhet International University

2. Team Name: Good For Nothing
Supervised By
 Dewan Yourid Ahmed Chowdhury (21028)
 Shahidul Islam (21029)
 Jannatul Fardus Taj (21030)
 Ahsan Ul Kabir (21041)
Khaled Hussain
Assistant Professor
Department of Computer Science And Engineering
Sylhet International University
Team Members:

3. Introduction
We developed a Meeting Management System that can be used as a tool to
manage the meetings, specially which are held in our department.
It is a web application specifically designed to manage meeting activities
and get more out of them

4. Background ( To Call A Meeting)
 In paper based system, first all the stakeholders
have to be invited via some written letters
informing them about the Time, Date and the
Place of the meeting.
 During a meeting, if any information needed
from any previous meetings, then one has to go
through a lot of papers to find that specific
information.

5. Background(During A Meeting)
 Everyone present in a meeting has to sign a form to
ensure that he/she was presented in that meeting
 If there is any change needed to make in a meeting
resolution, it has to wait for the next meeting to come.
 The processes takes a lot of time and the cost is also
very high.

6. Proposed System In Brief
There are two interfaces of the system
1: One for the User
2: One for the admin
 All of the members will login with his/her user name and password.
 They will view the contents about the members and meetings.
 Search option to find the specific contents by any keyword.
 A form to make communication with the admin
User Interface

7. Admin Interface
 Admin login
 Admin privilege.
 Sub admin privilege.
 When admin calls a meeting, an Email will be sent to the
users as an invitation with the title of that meeting,
description with time and place, date of that meeting.
 Every user will get an email when the admin will save
information for every meeting

8. Requirement Analysis
 Interviewing the stakeholders
 Researched on the paper based system to.
 Research over the Internet
 We got Positive result in all four sectors of the feasibility study.
Feasibility Study

9. Prototyping
 For this project, we used Evolutionary approach
 First of all we designed our interfaces then gradually
added new feature. We tested it to ensure that it is
working as it should. Then we repeated this process
again and again until we are accomplished our goal .

10. ER Diagram

11. Data Flow Diagram (User)

12. Data Flow Diagram (Admin)

13. User login

14. User login

15. User login

16. Feedback

17. Admin login

18. Admin Home

19. Call a Meeting

20. Call a Meeting(Continued)

21. Call a Meeting(Continued)

22. Call a Meeting(Continued)

23. Member list

24. Add Sub admin

25. Add member

26. Edit member

27. Edit member(Continued)

28. Delete member

29. Delete member (Continued)

30. Meeting Database

31. Start a meeting

32. Start a meeting(Continued)

33. Edit a meeting

34. Edit a meeting(Continued)

35. Delete a meeting

36. Sub admin interface

37. Sub admin interface

38. Feedback

39. Testing
We tested our system via some common testing methods.
They are :-
White Box Testing
Black box Testing
Alpha Testing
Beta Testing
Usability Testing

40. Future plan
we would like to take this system into a whole new level by including
features like :
Video conference
Mobile application
Ordering food and refreshment online

41. Conclusion
This project is created for our university and we hope that it will be used in the future
meeting held in out university. Some of the merits of this project are mentioned below:
The application is web based.
It provides a simple and user friendly interface.
The whole system is automated.