Software Engineering major operations summary

Software Engineering major operations summary

First, the integration of project documentation

Second, the degree of completion of the project summary

  1. President
    1. Create Event 
    2. Edit event 
    3. Event notification, community style release 
    4. Publishing tasks 
    5. Management community members 
  2. student
    1. Register for an event 
    2. Message in the community in style
    3. View all communities information 
    4. To subscribe, unsubscribe community 
    5. View community internal tasks 
  3. administrator
    1. Community management 
    2. Approval application activity 
    3. Public Site Management

Third, individual project work summary

1. The main work

  As the small number of this group, the preparatory work of the previous stage included (requirements analysis, design) are jointly done, after the code implementation, there is no specific code block presentation, a lot of work concentrated in the same class were It may not be good to show everyone's workload; but everyone has a different function realization division, personal divided as follows:

  Serial connection of + 1.1 database program
  android terminal connection to a database, using JDBC and mysql Direct Connect (cloud database before attempting ultimately failed, or will later try to use the fight can overcome difficulties); filling interface content: filling out of the database interface to show the community, staff, students and community information, etc., including the associated, and information showing the front end.
  The main difficulty lies in value between the respective transfer activities, each activity is completed corresponding to the transmission parameters based on the function, the processing related to the main thread of multiple threads cause more confusion of data, loss of information, so that each interface can not be flexibly switching activity .

  2.2 complete personnel management president and publishing push function
  to develop android terminal is learning by doing, experiencing a lot of bug, including the interface of timely refresh does not work, can not find the class and so on, are some of the details on the deal. To an increase in personnel, delete and transfer of personnel management. Realized the president upload pictures, upload your photos from an album release function in the push, the publication can be subscribed to push the society's staff to see.

  2.3 to complete the task and push function View community
  associations on the task, "I added," on display, realized by implementing community task shrink text view; a push in the community to see a "I am concerned about the" show, click on headers to push .

  2.4 complete the student community concern cancel function
  the user can take based on personal preferences community-related activities.

  2.5 The main interface implemented
  community area showing community + Introduction; optimizing personnel management interface community management; push delivery interface

2. Personal Reflection

  2.1 Requirements analysis phase
  to go in the requirements analysis phase a lot of detours, on the understanding of the needs analysis with the teacher to explain the needs of what is a slight deviation, several design requirements document was rejected by the teacher, because the real demand we set out concrete realization function, fewer restrictions required needs. Fortunately, he was not a person in combat, under the joint efforts of team members, the final completion of the project the most important preliminary work to prepare, prepare for the realization of the next project. But in fact in the process of solving the problem of late, I found the lack of demand for design.
  The stage of reflection is obtained:
  behind closed doors is not desirable, open your mind, you can learn other good programmers write code, so get some inspiration, it becomes our own things and reflect on their own projects; brainstorming equally important , you can increase the number of bright spots for their project, not just limited to some of the traditional functions.

  2.2 Design stage
  design basis requirement analysis on the basis of, for class diagrams, use case diagram, drawing and database design timing chart; at this stage, involved in the design and sketch, there is ambiguity during, not uniform in the group, At this point the teacher's answer has played a significant role in the drawing work to be completed in time.

  2.3 Code implementation phase
  1. "small but fine" not achieved:
    · not reasonable and accurate on the interactive interface;
    · rather monotonous in the use of controls, should be flexible and use the occasion calls;
    · not fully considered limited in functions to achieve conditions and rationality to achieve.

  <Teacher suggested that we will fully absorb and make amendments made on the basis of the original>

  2. Unified management code not fully reflect:
    This is a path of no return, because forgotten in the process of writing code to write the code specifications, resulting in the process of stitching behind the program, we need to modify some of the details, as a team, good writing specifications can improve the efficiency of the whole team, this is the lesson I obtained in this project practice.

Fourth, for a small promise of this teaching suggestion

First let me compliment Zhu Yong teacher:
  When Zhu Yong is an excellent teacher, in the four milestones, we girls group encountered many problems, ask questions that every teacher, answers are fine, can solve a lot of problems; in addition to teaching, the teacher will put a lot of constructive ideas that we want to be helpful, it is undeniable, on the Zhu Yong teacher's class is a piece that is hard and good times.

Then the following is my little promise recommendations:
  • Question 1:
  there may be some irrationality on the team, in terms of our girls group (personal experience speaking): fewer people, more unified style, a more balanced level, which could lead to the realization of the idea of a unified and relatively narrow in the back of the project; the team have joined forces, will say to the level of the average student, it is rather unfair?
  · Recommendation:
  Initially the idea of men and women with the teacher's actually no problem, but difficult to implement, it may be due to relatively contemporary college students shy and difficult to open. Whether we can randomness team approach, with an average allocation of resources? Or appropriate transfers in the case of group good team? Breaking the unspoken rules acquaintances team achieve teamwork, not only can reduce this irrationality, it can also increase exchanges and communication between students, do both.

  • Question 2:
  four milestone, we are all carried out in a blog form teams report shows, the relative lack of communication between the team, the lack of mutual learning process.
  · Recommendation:
  Before the end of each milestone, the group may be decimated group reported, except where the teacher can understand group, other groups can also be a certain degree of learning and communication, the problem is amplified, and then if you can improve the efficiency of unified solution ? does Additionally, some individuals believe it is necessary incentive mechanisms, such as: if the group stage to demonstrate good performance can be properly points to mobilize the enthusiasm of the students.

Guess you like

Origin www.cnblogs.com/shengxue/p/12017088.html