Project summary of software engineering team

Project summary of software engineering team

A semester of software engineering is over, and this semester we have done three projects for individual projects, pair projects, and team projects. The first two are mainly to take practiced hand, experience a simple software engineering methodology, and the pair project before and after two months, can be said to be a systematic software engineering exercise, the following two iterations of the process to do a summary.

M1:

What we have done: a community platform, to provide students with a browse community activities of the plaza, to the community to provide a management member registration and send notification Integration services.

How we do it: demand analysis, imagine the user scene of our products, establish basic ER diagram model, learn the basic knowledge of web development, do some demos, learn how to use AJAX-based technology to carry out the network data interaction, writing API development documents, front-end engineers to implement separately, Front-end docking test, release.

What software engineering methodologies do we use: the Agile Development Process (TFS Release task, weekly session, scrum meeting of the sprint stage, full communication of team members), demand-driven development (the original design has something imperfect or impersonal, and in the process of development there are new ideas, Software Testing (unit testing, stress testing, compatibility testing, etc.).

Our Harvest: First contact with such a large team project, learn to communicate, learn to cooperate, learn to plan, learn time management, learn to use Project management software to promote software development process.

Our weaknesses: Emphasis on code building and neglect of document writing; TFS task-making is too inflexible to play a guiding role in project development; There is no Code management tool, code is scattered, the version is different, some people change the old version of the code is not aware of.

M2:

What we have done: build more user scenarios on the basis of M1, facilitate the users to join the community, provide the functions of the Community management, provide a more diverse way of notification, basically, completed a community platform of the most basic and core functions.

How we do it: summarize the M1 development process, clear M2 new requirements, try to refactor M1 's scattered code, learn a concise layout, try to use the framework, abandon the use of the framework (in order to improve page loading speed, improve the user experience), focus on the implementation of the function and the beautification of the interface, Extended front-End interactive API, backend implementation API, front-end writing interaction code, docking, testing, publishing.

What new software engineering methodologies do we use: The design method of graphic modeling (using graphs to express the user's needs, drawing the call relationship between the pages), User experience evaluation (not only considering the aesthetics of the interface, but also considering the corresponding time, the robustness of the software, the user's usage habits, can provide a good experience for every type of user).

We are better than M1: TFS has played a role in reflecting the progress of the team project in a more realistic way; GitHub's use provides a good platform for the team to publish, document, discuss, and communicate; Try using the page layout framework despite the failure, But this is a good exploration.

We have no progress or backward than M1: Time is tense, the pressure is too big, the document problem is not enough attention, due to the development of the work time, mutual communication obstacles, development efficiency is not as good as M1, late testing is not sufficient, the quality of software is not too big guarantee.

Project summary of software engineering team