Welcome! We are Team Gappmakers and this is our second blog. Following is a brief introduction to our product requirements and user stories.
Requirement Analysis
Understanding of the user requirements is the most fundamental things for any developer. If there is any kind of difference and assumption might be due to several reasons, but this ultimately leads to undesired product and performance which later on leads to inefficient use of time and resources. Hence to understand the need of our user we had rigorous meeting and discussion among our team to understand the user desire and deliver more powerful and efficient product.
In this blog, we are going to elaborate our whole process of understanding user requirement. An in-depth explanation is given below.
We had three fruitful meetings with our customer, Every time we had prepared a long list of the question so that we can map the customer requirements. We had designed our team meetings in such a way that every time before going to customer we have a meeting to finalize the questions and second meeting after meeting with the customer, this idea helped us to ask to the point question to the customer and later on had done a lots of brainstorming to understand the specific requirement. In this whole process, we had come to a various situation where sometimes we all are having a common view and sometimes different assumptions which leads to creating some new questions for the next meeting with our customer. We had always tried to visualize this project from a user perspective, we had thought in such a way that if I would be the customer of this Mind Peace. Definitely, we had wanted an app which is safe and secure at first priority, while precise and efficient performance is the must-have.
Requirement Assembling
After all the meetings we had prepared a final list of user requirements, we had worked together in synch to prepare a fundamental requirements list. We had then prepared a use case diagram which will provide an easy way to map the project and also help us to convert the user stories into small tasks so that each team member can work independently.
With help, the UML Diagram anyone can easily understand the flow of steps to be followed In this project so that everyone will be on the same platform and we can easily track our work.
We had categorized the user requirements in mainly four categories.
-BEFO’s Requirements ( BEFO is the user that is BEing FOllowed )
-FOLLO’s Requirements ( FOLLO is the user that is FOllOwing the BEFO )
-Common Requirements
-Optional Features
-The app to be able to track my location and send automatically to my desired follower
-To have an emergency button in the app
-To delay or cancel the trip (abort reason to the followers)
-A pop-up notification in case of non movements of continuous 90 seconds
-Notifications to be in the app only
-Language should be English
-To save my privacy, Hence nobody can track my location without my permission
-To set frequency of location synch (Do not check location if the battery is less than 25%)
-Automatic suggested time and control of time of the trip should be in my hand
-Control of selecting follower
-Name list of the user I am following
-Have choice of notication type
-No Registration
-One time login only
-Contact based operation
-English language base
-In-app notifications
-Multiple language support
-Automatic suggestion for trips
-Clearing old records and save in log
-Multiple themes
-Able to see my last trips
In the whole series of time, we had in front of many wrong assumptions which was completely different from the user requirements. One of the terrifying ones was, we were thinking to provide a live location to the followers, we were not thinking in terms of privacy of the user, later on in meeting with our customer things got very much cleared. And later on, we had tried to minimize such incidents.
We are currently focusing on designing of our application, in our meeting we are mainly discussing on fixing the interface of our application. We should be also constantly touched with our customer so that we don’t get deviated from the path.
Thank you so much for your read and support.
Please stay tuned for our coming blogs.
Team G-APP MAKERS
