SRS ONLINE MEETING MANGEMENT SYSTEM M3
Introduction
1.1Purpose:
The greatest time waster in most organizations
is ineffective meetings. Yet meetings are important. To be a successful
organization, information flow is critical. Additionally “face time” is
important to support and perpetuate good relationships and teamwork.
The problem is, most companies have meetings
just because they’ve always had certain meetings or because “it seems like a
good idea to have a meeting.” Some managers let the calendar dictate the need
for a meeting – the first of the month, every Monday, etc. But little thought
is given to the purpose and outcome of the meeting or even who needs to be
there. This makes for apathetic inefficiency at best.
1.2 Scope:
The proposed software is online meeting management system the system will use to create a agenda and
minutes of meeting and send it to the
organization meeting participants and then storing this agenda and minutes of
meeting for further usage the current system is paper based system it is too
slow and cannot create and send immediately the intensions of the system are to
reduce overtime pay and time. Requirement statement of this document are both
functional and non functional.
1.3 Abbreviations & Definitions :
M3 - Online meeting management system
Login id - User and Administrator identification to enter the system
Password - A word that enables one to gain admission into the system
1.4 Over
view
Currently manual record keeping is
done for the meetings. This a criteria of great concern on FUUAST campus so
there is a great need for a fully automated meetings minutes system to resolve
this problem.
The FUUAST meetings minutes manager
primarily based on the oracle 10 g and reduces the time.
·
Meeting data is gathered ,this is
produced in format of an agenda
·
The agenda is later on transformed
for meeting date and points
·
The meetings are conducted and
resulting minutes are maintained
·
The overall results are given
via e-mail alerts
2 General descriptions:
2.1 product perspective
Online meeting management system M3 is to
simplify the overall process of minutes processing and data distribution on
campus and to help the authorities proceed with their meeting related tasks and
guide them in giving this data to the other stakeholders in the final
distribution of the meeting decisions.it manages the minutes of meeting which
sends to meeting management system
2.2 Product Functions
Meeting
management system can perform following functions
Participant’s
details:
It
will store the information of all employees of organization
Minutes
of meeting:
It
will store the minutes of meeting and information about that meeting
Over
all meetings details:
Organization kept the detail of all meetings
held by organization
2.3 User Characteristics:
The
system will be used in different organizations the administrator and the
employers of the organizations will be the main users user with basic computer skill user can use this
Employees:
Those
employees who are recognized from organization to create agenda and minutes of
meeting and send it to participants used this software
Administrator:
Administrator
has responsible for giving a responsibility to employees who create agenda and
minutes of meeting also administrator can revoke employees creation rights.
2.4
General Constraints
·
The
system must be delivered in 5 days after organizations agreement
·
The
system must be user friendly
2.5
Assumptions and Dependencies
·
It
is assume that the organization have enough trained staff to care of the system.
·
This
software package is developed Oracle Developer as front end which is supported by Sun Micro
System.
·
Oracle
Database is the back end which is supported by Microsoft windows .
3
Specific Requirements:
It
describes all the details that the software developer need to know for
designing and developing the system.
3.1
Functional requirements:
3.1.1
Administrator login:
Administrator login include the
Administrator login id and administrator login password. Administrator have
full access to the software it changes all the things in the software
3.1.2
Employee login:
Employee login have two things first
is employee login id and second is employee login password employee read information and reply for feed back
3.1.3 Sign up module:
The
user signs up in this particular system via the sign up module and the data is
used for validation upon login in to the system.
3.1.4 Agenda module:
The agenda is
created through the points the authorities enter in order to create a rough
draft for the next coming meeting.
SRS001 Prepare Notice
Notice
which has Send to all the entities related to this meeting containing information about time date and place of
meeting.
SRS002 Format
In which format people want to make
their agenda like doc,docx,pdf.
SRS003 Approvals
According to this module feature
Authority gives the final approval to the agenda.
SRS004 Publish
Finally this Feature publish the
Agenda on the official website of Organizations.
SRS005 Agenda
Directory
All Agendas detail of
Organization.
3.1.5 Minutes
Of Meeting Module:
Minutes of meeting contain Records
Related to previous meetings Conditions Suggestions and Recommendations related
to that topic.
SRS006 Build
Organizations
make their Minutes of Meeting for future .
SRS007
Format
In which format
people want to make their Minutes like doc,docx,pdf.
SRS008
Approvals
According to this
module feature Authority gives the final approval to the Minutes.
SRS009
Publish
Finally this
Feature publish the Minutes on the official website of Organizations.
SRS010
Minutes
Directory
All Minutes
detail of Organization.
3.1.6
Notification
module:
Share your
information with all your internal stakeholders from our notifications center.
3.1.7 E-mail
alerts module:
Through this module your System sent
the Agenda or Minutes of Meeting to the
specific person or group of person.
SRS011 Email Addresses
SRS012 First Name
SRS013 Last Name
SRS014 CC
SRS015 BC
3.2
Design Constraints
SRS016 Database
Oracle
database is use
SRS017 Operating System
Window
7,8 And Vista ,Xp
SRS018 Web-Based
Smtp
is used in this system
3.3 Non Functional
Requirements
3.3.1
Security
SRS019 User Identification:
System requires the user to identify him/herself
in m3
SRS020 Modification:
Adding modification in minutes of meeting ,
agenda and meeting invitation in m3 is only done by
administrator rights only (Administrator
)
SRS021 Administrator Rights:
Administrator shall be able to view and modify
all data in m3 management system
3.3.2 Performance
Requirements:
SRS022 Response time:
The system shall give response in 15 sec after
sending the invitaitions to the
participants .
SRS023 Capacity:
System must store 5000 employees data (email
id,name,designation etc) At a time
SRS024 User Interface:
User interface screen should show within three
seconds.
SRS025 Conformity:
System must confirm do the Microsoft
accessibility guide lines.
3.3.3 Maintainability:
SRS026 Backup :
System shall provide the capability of backup
the data
SRS027 Errors:
System shall keep the log of all errors
SRS028 Availability:
System shall be Available all time
Conclusion:
This SRS document is used to give details regarding meeting management
system . In this all the functional and non functional are specified in order
to get a clear cut idea to develop a project
