| project | content |
|---|---|
| This work belongs courses | <Classroom teachers blog Home Links> |
| course | 2016 Computer Science and Engineering Software Engineering (Northwest Normal University) |
| Work requirements | Experimental fourteen project review team & course summary |
| Job learning objectives | Team Project Review & course summary |
1, experimental purposes and requirements
(1) master the software project will be assessed processes;
(3) summarizes the course content to reflect.
Second, the experimental environmental requirements
Experimental thirteen prepare a team project acceptance documents and configure the system.
Third, the experimental content and steps
Tasks (a): to review the list, to play according to team projects knot by the project group B, knot-playing party to the project team, each for their own software products Acceptance Review (Meeting Process see experimental thirteen software project acceptance knowledge), and the formation of acceptance opinion.
Acceptance will be assessed in two stages: the first stage, served as moderator by A project leader, will organize acceptance A project acceptance, project team members play twinning project of Party A; B by the second phase of the project leader, served as moderator , will organize acceptance B project acceptance, project team members play twinning project B Party.
After the lesson, each project team shall submit to Party in Github repository project team fill in the acceptance of the views of acceptance feedback form.
Team project github repository address link: https://github.com/struggle17/projecttable
Task (2): The experienced software engineering study and practice of a semester project, ask each student to complete a personal study concluded blog, content requirements are as follows:
Course content of the semester, compared to issue "a test preparation software engineering," the task 5 you mentioned (given questions blog links), try to answer the questions raised,
Question blog link: https://www.cnblogs.com/XL1105/p/10487669.html
Questions 1. Why do we need software engineering?
Professional point of speaking, software engineering goal is to realize "software manufacturing" social, industrial production, increase their labor productivity. Only in this way, the software industry to achieve socialization, industrial production, in order to "bigger and stronger." No management of the design is a failure and confusing design, programming guide is not designed disorderly busy. Depending on the size of the development of the software, application software engineering should be thinking of an appropriate degree of flexibility required, after all, we developed software mostly small and medium, large and rare (I think so). But as long as the exchange and communication between the people involved, more or less have the need for software engineering in order to be more efficient, more stable results of the work.
Question 2. How to learn software engineering?
Content of software engineering involved is very large, and learning theory mostly abstract thing, there is no specific experience in the future there will be more difficult to deal with specific issues, perhaps this is the reason why many people feel very empty, but clearly not the case.
(1) First, you must master a programming language, with programming capabilities.
(2) Secondly, more reading, not to follow blindly, but to form their own opinions in the future.
(3) in practice need specific issues and problems, very sensitive mechanically.
"Theory" and "experience" is important, as many people are now talking about the "Road" (theory), it must not be confused, "art" is also very important to know the "Road" may not be able to help you solve the problem, but know that "Road" will make people be sublimated and wide, including ideas, "art" is the basis for truly understand the "Road", otherwise all talk, like martial arts often say "What is clear to understand" and the like a pack of lies.
3. How the problem developed software to meet user needs?
Actual work collection, derivation, refining demand, and indeed after the software is released to meet the actual demand data validation. Demand from the actual, rather than trying to imagine the "demand" or parrot needs (such as: virtual, nobody uses, there is no "library management system" data).
(1) summarize their project feasibility analysis / requirement analysis / software design / implementation / testing / project acceptance / learned what "knowledge."
| Feasibility Analysis | Step purpose and feasibility analysis of the feasibility analysis |
| demand analysis | By prototyping tools (according to the needs of users for the user as the requirements for a software developer blade , mockplus take more specific and accurate information). Also learn a task needs analysis to understand the conversion standardization and state diagram of the data. |
| software design | Learning the UML model development, control of both the modeling tool ( processon and Visio) |
| achieve | When coding must pay attention to the logic clear and concise and easy to read and easy to understand, there will be a lot of BUG in the process of writing code, you need patience to solve. |
| test | Testing is to find errors in the program, any project needs to test white-box (structural testing) and black box testing (functional testing), to understand the black box more emphasis on third-party testing. Also learn the step test. |
| Project Acceptance | I know the entire agenda of work and the need to prepare for acceptance of projects, but also learned the need to check the terms of acceptance of the project. |
(2) a combination of personal items / pair personal experience of program / project team, talk about the experience.
I just started programming ability is particularly weak, for the completion of individual projects are very far-fetched, but as a junior we have no longer been a programming language teacher, learning to fend for themselves in the class. After learning this course, so I have an understanding of the system to create an implementation of the project, it is undergoing a project from project to project acceptance process, in which I mastered the prototyping tool, modeling tool also learned deployment task team WBS and division of labor. After group work let me know a person's strength is very weak, each member of the team has their own strengths, the so-called Three Stooges top of a Zhuge Liang. Interaction among team members communicate and ultimately in the process, found a way to ending the problem in the communication; in addition, the importance of design documents slowly come to understand, if there is no record of the document, the task done no later so convenient. Each stage of the workload of each person different tasks, a complete team must be close cooperation between the various team members results.
(3) statistical software engineering practice, completed the code you how many rows;
In software engineering practice, I completed the 2500 lines of code.
(4) how much time you are in the practice of software engineering homework? (Make a list)
| Soft-tasking | Spend time (h) | Cumulative spending time (h) | The average time spent per week (h) |
|---|---|---|---|
| Experimental Software Engineering to prepare a |
|
|
|
| Software engineering experiment two individual events |
|
||
| Third experiment software engineering twinning project |
|
||
| Experiment 4 prototype based software needs access to |
|
||
| Experiment 5 software R & D team building |
|
||
| Experiments six teams and project review team project topics report |
|
||
| Experiment 7 prototyping and development project team teamwork 3- |
|
||
| Experiments eight Teamwork 4- demand research and analysis based on the prototype of the project team |
|
||
| Experimental nine Teamwork 5- team project needs improvement and system design |
|
||
| Experiments ten team improved design and detailed design work 6- Team Project System |
|
||
| Experimental eleven Teamwork 7- team project designed to improve coding & testing |
|
||
| Experimental twelve Teamwork 8- team project User Acceptance Review |
|
(5) Which one job to make you the most impressive? why?
Affect me the most profound is the third team work: the prototype design team project, this is the first time I met prototyping tool (blade), I feel this software is very powerful, very simple operation can be achieved interactively, by drag the control interface can be achieved, it can be a team work together, you can also use the phone in real-time preview. A good prototype for a very important project, prototype design allows designers and developers to visualize the presentation of the basic concepts and ideas, so that everyone involved can view, use and give feedback, it is the biggest prototyping the advantage is that you can effectively avoid the important element is ignored, it can prevent you from making inaccurate unreasonable to assume that the job is completed makes sense.
(6) you learn and master a new language, a new platform;
I have to master a new language: Java; a new platform: Myeclipe
(7) form below, summarizes a semester of study, software engineering development tools, development methods and modeling methods you learn or use;
| Software Development Tools | Project Management Tools | Software development methods | Modeling software |
| MyEclipse、MySQL、tomcat | Github | Prototyping, survey | Object-oriented modeling, structural modeling |
(8) Do you think what are the problems existing curriculum, do you have any better suggestions.
1. theory and practical operation to be carried out simultaneously, lack of time, the need to increase class time.