Chapter 3

Methodology
3.1 User Requirements:
Based on paper (Montag et al., 2018)

 The system should allow customers to register them first by entering name and phone
number.
 After login the system will allow to add new friends.
 This system will help them to add new friends and stay connected.
 This application will also help the user to share various content for example picture,
video, contact number and can exchange money easily.
 User can also add their friends via QR code. The system can track the user by sharing
the location. Finally, the system should build in affordable budget.

3.2 Functional Requirements:

Based on paper (Montag et al., 2018):

 Signup – The system will have a signup policy for every new customer so that we
could know who is using our software.
 Login – The system will have a log in policy and his/her information will be
secure in the database.
 Display his/her profile – Redes will give him/her a profile to get connected with
others so that his/her friends could identify him uniquely.
 Share picture – The user can easily share pictures with others.
 Add new friends – The system will allow user to make new friends to get
connected no matter where he/she is.
 Share video, picture, message, contact number – The system will allow user to
share content among selected friends and stay updated.
 Remove friends – The system will allow user to remove friends.
 Transfer money – The system will allow user to transfer money.

    3.3 Non -functional Requirements:

Based on paper (Montag et al., 2018):

 Usability- The system aims to add friends and share contents among them within
the shortest possible time.
 Performance – The overall performance how smoothly our software (Redes) will
run depend on user’s action.
  Security - Our system needs to be secure because users will be providing some of
their personal information.
 Reliability - Our system will function flawlessly.
 Availability - The system tries to meet the needs of as many users as possible in
the shortest amount of time.

 3.4 Stakeholders for the system:

Main actors of this system (Montag et al., 2018)
 User
 Administrative stuff
Main use case associated (Montag et al., 2018)
1. User
 Able to log in.
 Visit the home screen.
 Able to add others as friend.
 Share any type of content (picture, text massages)
 Share any documents (doc file, pdf etc.)
 Able to make phone calls
 Exchanges money via QR code.
 Able to report any type of problems and ensure privacy.
 24/7 helpline for any kind of help.

2. Administrative stuff (Montag et al., 2018)

 View tactical details.
 Help user about any kind of information

3.5 Requirement Analysis: 

 The final product has been described with clarity (Gao & Zhang, 2013).
 The system will keep user data (name, email or phone-number, age).
 The method will also make it easier to distribute a lot of content to chosen audiences.
 This application will be quick, reliable, and secure.

3.6 Software Process Model (To Share or Not to Share? Credibility and Dissemination of
Electric Vehicle-Related Information on WeChat: A Moderated Dual-Process Model, n.d.):

For developing the system, we will use incremental methodology. We know that incremental
method works module by module. So, after delivering the first increment if user give any new
requirement, we will be able to add that requirement in the next build. 
 Figure 3.6: Incremental Methodology

     
In the first increment we will add signup and login function, profile, add/remove friends, send
message, make a phone call, transfer money and upload video. Then in the next increment
increase privacy, add some more features, ad and track their friends will be added. And finally in
the third increment we will keep developing the project according to user requirements.