Detailed Description about Our Project

Introduction

In this section, the main focus and target is to answer the questions about our project in terms of assumptions, goals and plans. Moreover, some descriptions and explanations of this software about the design, implementation and test will be displayed in this blog.

Assumptions, Goals and Plans

Assumptions:

In the beta sprint, we hope to further improve and enhance our software through further improvements in functionality, implementation of various tests, and feedback from user tests, in order to obtain the final version of the software that can be released to the public. In terms of functionality, we expect the friend system and chat system to be perfectly implemented, providing users with a good user experience during use. In terms of usage effectiveness, we hope that this software can effectively bring convenience to users in campus communication and exchange.

Plans:

In Beta sprint, the plans our team come up with are to finish all the functions of the software, including Friend System and Chat system. Above all are the basic functions we need to implement. To be honest, there are still some functions that are not completed in the Alpha Sprint, so in the beta sprint, we need to finish these, and at the same time, the test of each function should be conducted. Besides, error management and regression test should also be performed during this period, as well as the interface test and the integration test.

After the programming and testing, in the Beta Sprint, the software should be approximately perfect and be available for the users (such as our schoolmates and our friends, etc.) to test through their personal devices. After that, a survey of the user experience and improvement suggestions should be obtained. After this step, some improvement measures should be taken in order to acquire the final version of the software for releasing the software.

Goals:

For the functions:

Friend and Chat system:
Users can easily find friends on friend list as well as having normal chat with friend when the network is connecting. Also, the capacity of the friend list should be as large as possible to meet different social needs.

The chat interface should be clear, and users can easily distinguish which side is their own and which side is what the other person is saying. In addition, the communication of the two users should be consistent and the chat history should be stored in the database.

User Interface Design:
The interface of our software reflects our core ideas of conveying a warm feeling to the users, as well as setting up a user-friendly and easy-to-start-with software interface.

Design, Implementations and Test

Design:

In this part, design issues about Interface, functions and test are going to be explained in detail.

Interface Design: In this part, we have designed a user-friendly UI interface in an attempt to provide users with a warm atmosphere conveyed by the software while using it. A typical representative is that we have added some cute and warm illustrations in the user interface, so that users can have a good and warm user experience.

Function Design: In this part, our aim is to provide users with a good user experience. The functions are designed and arranged, namely the friend system and chat-with-friend system to showcase their relationships through class diagrams. When designing software features, we mainly focus on the practicality of these features to prevent major functional issues.

Test Design: In this part, our goal is to create test cases that fit the requirements based on requirement analysis. Through various combinations of testing methods (programmers conduct unit testing during the programming process, testers conduct functional testing, provide feedback on defects, regression testing, etc.), to eliminate defects in the software as much as possible and obtain the best final software version that can be released.

After the basic testing phase is completed, we need to plan to hand over the initial test version of our software to some internal testing users for use and testing, in order to obtain their feedback and improvement suggestions on the user experience, and further optimize it, which will further improve the quality of our software.

Implementations:

Function Implementations: In this section, the basic functions of the software, including login, registration, friend chat, etc., will be implemented. At the same time, we focus on the implementation effect of these functions and the frequency of errors or crashes, in order to improve these functions and ultimately obtain the best software version within our capabilities.

Below are some demo video about our software:

Registration and Log in.

Adding Friends

Chat With Friends

Test:

Function Test: The function test of the software has been basically completed in the alpha test, while in the beta test, we focused on identifying and filling in the gaps of previously tested functions, hoping that our software functions will not have significant/intolerable errors in subsequent user testing.

The link to acquire user cases: Click Here to GitHub to Find Them.

Integration Test: The idea of how we implement the integration test is Function-Based test. In the integration test, we integrated our various functions together for testing. We have identified a path with the highest priority and integrated all the functions on that path together, gradually integrating two and three functions until all the functions that need to be tested (such as registration, login, opening the friend interface, adding friends, selecting friends, chatting) are integrated onto our path, and our integration testing is considered complete.

User Test: In user test, we package the software and send it to be qualified users for a one-week software usage test. After completion, we provide feedback on their usage experience through questionnaires and provide targeted improvement suggestions as the basis for our final improvement and adjustment, so that the version we can ultimately release is as perfect as possible.
Below are some defects that are tested during the test procedure.

Defects Management:
Also, the same as previous test, we use Zen Taoism to manage our defects.

Below is the entire demonstration of our project.

The Entire Demonstration

Summary

In this article, our software has provided detailed answers to some specific questions according to the modules. We believe that with our efforts, this software can ultimately be used by the public.