1.
Introduction
The purpose of this application we are to build is to help users collect notes and organize the notes.
This SRS document outlines our plans and what we will achieve at the end of the process.
2. Functional Requirements
2.1 User Authentication and Authorization
The app will allow users to register and log in using their email and password. The app will also allow
users to reset the password any time they want, especially when they forget it.
2.2 Note Creation and Editing
Users will be able to create notes, add titles and descriptions, and categorize them. The app will also
provide the ability to edit and delete the notes.
2.3 Note Organization and Management
The app will allow users to organize their notes by categorizing them. The app will also provide the
ability to search for notes by title or date of creation.
2.4 User Profile Management
The app will allow users to manage their information, such as name and email address. The app will
also provide the ability to change the password and delete the account.
3. Non-Functional Requirements
3.1 Performance
The app has to be optimized, ensuring that it loads quickly and a large number of users can use it
smoothly. The app will also be responsive, so as to be used by a wide range of devices.
3.2 Security
The app will provide security just at the level of password authentication and encryption. The app will
use encryption to secure user’s data on our database.
3.3 Compatibility
The app will be compatible with the latest versions of web browsers. The app will also be responsive
and adaptable to different screen sizes.
3.4 Accessibility
The app will be accessible to users in many languages. Also, the SEO ranking will be elevated so as to
be easily found by search engines.
4. Constraints
4.1 Technology Used
The app will be constructed using Angular for the front-end and Django for the back-end. The app
will use Angular for the user interface and styling.
4.2 User Interface/ User Experience
The backend provides two interfaces for manipulating notes and sticky notes, the api/note/ endpoint is
for manipulating notes while the api/sticky note/ endpoint is used for manipulating the sticky note. On
this endpoint you can perform GET, PUT, DELETE, PATCH and POST methods on the notes and
sticky notes. It is worth noting that all these methods are hidden behind two api/ endpoints. This is to
ensure that the authentication and authorisation endpoints are not accessed directly by anyone.
It is quite easy to manipulate the front-end we have created for the system. To register into the
system, we start from accessing the URL and clicking the sign up button and providing a user name,
password, and e-mail address. It is the same procedure to login and register.
After logging in, the app takes us to the dashboard which displays all sticky notes. On the right side of
the page, the user is provided a form to create sticky notes with. The user only provides the tag and
content of the sticky notes.
5. Criteria for Acceptance
5.1 User Acceptance
The app has to be tested by several users to ensure that it meets these requirements and is effective.
The app should be able to handle a large number of notes without disturbing or freezing.
5.2 Testing Performance
The app has to be tested with different network conditions to ensure that it performs well under
manageable circumstances and is efficient too. The app should be able to load and save notes quickly
too at any time.
5.3 Security Testing
We make use of the Django authentication to create access tokens upon creation of accounts.
This tokens are managed by managed by the front-end to perform login and login out
operations. This provides a layer of security as the access tokens are not easy to obtain.
All our methods including the authentication endpoint are hidden behind two api/ endpoints. This is to
limit others from navigating through our endpoints and obtaining access to unauthorised data. This
way no other frontend can be used for the system and every users access token is safe.
The app has to be tested for vulnerabilities and security issues.
6. Conclusion
This SRS contains the functional and non-functional requirements of our note collection app which is
being constructed with Angular and Django.
7. Diagrams
a. Use case Diagram
b. Entity Relationship Diagram
c. Sequence Diagram
d. Class Diagram
