Product Requirements Document
Product Requirements Document
1. Purpose
The purpose is to create an Android Application to ease the communication between the employees
in and across departments.
2. Scope
The scope of this document includes all the major features that have high priority and all the extra
features that have to be included on completion of version 0.1
3. Stakeholders
A) Super Admin
i. Creates the structure of departments and its classification into location.
ii. [v0.2] Add / delete departments.
iii. [v0.2] Authorized the admin of each department.
B) Admin (one for each department)
i. Authorizes employees and their details.
ii. [v0.2] Updates employee details.
iii. [v0.2] Transfers employee from one department to another.
iv. [v0.2] Removes employees.
C) Employee
i. Send / receive messages.
ii. [v0.2] Send / receive documents (.pdf, .jpeg, .png, .odt, .doc, .dox, .ppt, .pptx).
iii. [v0.2] Broadcast messages.
iv. [v0.3] Create and confirm availability for events.
4. Product Requirements
A) Sessions
i. [v0.2] Documents / images can be shared in a session.
ii. [v0.2] Search a message.
iii. [v0.2] Clicking on someone’s name will take you to their profile.
iv. [v0.3] Sessions have a pinning feature that helps to pin important messages.
v. [v0.4] Send images from the viewfinder.
vi. [v0.4] Video calling.
b) Temporary Sessions
i. Employees can be added / removed by the session admin.
ii. Individual and group sessions will be together.
iii. A name is needed to be inserted for each session. For a one-to-one sessions it is the name of
the other person.
iv. Sessions have 2 options – Lock and Delete.
v. Lock makes the session messages read-only.
vi. Delete permanently deletes the session.
vii. An invitation is needed to join a session.
viii. A filtering option to select employees from other departments.
ix. [v0.2] Sessions can be shared. This enables a session to be converted into a .pdf and then to
be sent to anyone.
B) [v0.2] Broadcast
i. Anyone can broadcast. The broadcast will be sent to everyone in that department.
ii. [v0.3] Admins can broadcast across departments.
C) [v0.2] Events
i. Chronological order with date of event.
ii. Consists of:
• Event Name
• Venue
• Time
• Employee in-charge
iii. [v0.3] Option to opt-in or opt-out.
D) Registration
i. Once an employee registers, it has to be confirmed the the department admin.
ii. The registration field consists of:
• Name
• Employee ID
• Aadhar Number
• Phone Number
• Email ID
• Department
• Location
• Designation
iii. [v0.2] OTP feature while registering.
E) Login
i. The employee should be logged in at all times to get real-time messages.
ii. The employee will have to login when they change their phone or re-install the app.
iii. The login field consists of:
• Employee ID
• Phone Number
F) Profile
i. User can make changes to his profile but the changes need to be authorized by the
Department Admin.
ii. Profile consists of:
• Name
• Designation
• Department
• Location
• Status
6. Glossary
[v0.2] – To be implemented in version 0.2
[v0.3] – To be implemented in version 0.3
[v0.4] – To be implemented in version 0.4