Blue Flke's first assignment: Team debut

1. Team Name: Blue Flke

2. Composition of team members:

   201571030126/ To Zhifu (Team Leader)  
   201571030122 / Ma Zhonglin 
   201571030129/ Wang Shenghai
     201571030123/ Niu Ruixin
   201571030103/ Deng Yingrong  
   201571030105/ Dong Runyuan

3. Member style:

    201571030126/ To Zhifu

           Style: like to be active

      Specialties: Web Front-End Design

      Hopeful Soft Worker Role: Writing Programs

      One-Sentence Statement: Do Your Best

 

  201571030122 / Ma Zhonglin 

     Style: objective and rational

     Good at technology: Baidu search information

     Wanted Soft Worker Role: Programming

     One sentence declaration: You are not brave, no one is strong for you

 

     201571030129/ Wang Shenghai

     Style: Be careful and responsible

          Expertise: web programming

          Hopeful Soft Worker Role: Debugging

          A one-sentence declaration: The path you choose must stick to

 

     201571030123/ Niu Ruixin

      Style: Be assertive and accept others' opinions humbly

      Skills: C, java

      The Soft Worker Role of Hope: Gathering Information

      One-sentence declaration: Once you set a goal, you will never give up until the goal is reached, and you will succeed.

 

      201571030103/ Deng Yingrong  

      Style: strong sense of time, able to communicate with team members in a timely manner

      Good technology: familiar with java, understand front-end framework

      The Soft Worker Role of Hope: Testing

      One sentence declaration: If a worker wants to do a good job, he must first sharpen his tools

 

      201571030105/ Dong Runyuan

      Style: Able to learn with an open mind, accept suggestions, and communicate with team members in a timely manner

      Good technology: familiar with java, understand front-end framework

      The Soft Worker Role of Hope: Testing

      A one-sentence declaration: If you don't take a small step, you can't go a thousand miles.

4. The first group photo of the team:

  

 

5. Description of team features:

        There are six small partners in our team, all of whom like to discuss, express their opinions, and seek common ground while reserving differences. In general, the team has unity, mutual help, clear division of labor, and mutual trust.
 
6. Project name: Android-based web version address book management system

7. Brief description of the feasibility of the team R&D project:

  Project purpose: To develop a web version address book management system based on Android system, which aims to save the memory space of the mobile phone and maximize the use of the memory space of the mobile phone.

  User requirements: There are a large number of smartphone users, a large number of mobile phone contacts, and the contact information is easy to change.

team interview

  1. Give the team name and team project name of the interview

  Team Name: IoT Innovation Application Team

  Team project name: energy storage system based on RFID and energy conversion

  2. How much value does the project developed by the team give users? Does anyone still use it?

  The project developed by this team is an embedded project. Because it is a small project, it does not bring practical value to users at present. The team's project is an energy storage system based on RFID and energy conversion. The kinetic energy generated by the radio frequency identification module and the energy conversion device is converted into electrical energy and stored in the battery. The radio frequency identification module is mainly used to identify a person after punching in the energy. Statistics of conversion efficiency, in which the administrator login interface is written in C#, and statistics of these information can be performed in the background; as long as the energy conversion device uses physical knowledge, it will not be described in detail here.

  3. Can this project continue to be developed by our team, is there any source code/documentation?

  Since this project is related to hardware, our team cannot continue development; the source code is not available for some reason.

  4. What are the experiences and lessons learned from project development?

  Start small, then expand: When adding a function, start with simplicity, and then improve the function after the simple function is implemented, and do not add a complex function at one time;

  Advanced modular testing before overall testing: modular testing saves time, and errors are found quickly after they occur, making integration much easier;

  Taking longer than expected: While writing the code, we couldn't anticipate all kinds of unexpected problems we encountered while developing.

  5. What advice do you have for learning software engineering well?

  Software engineering is generally more inclined to the "engineering" nature. Personally, I don't think it will learn much, but it is more practice. In practice, read more materials, think more, and focus all your energy on software programming.

Guess you like

Origin http://43.154.161.224:23101/article/api/json?id=324803844&siteId=291194637