| project | content |
|---|---|
| Software Engineering | https://www.cnblogs.com/nwnu-daizh/ |
| Work requirements | https://www.cnblogs.com/sunmiaokun/p/11095027.html |
| Course learning objectives | (1) master the software project will be assessed process; (2) summarizes the course content to reflect |
1. The course content of the semester, Contrasts "Experimental Software Engineering to prepare a" task 5 you mentioned (given questions blog link), to try to answer questions and clarify how the discussion by learning / practice / make clear; whether learning creates new problems? If so, please ask.
1. The software development process, if a combination of many features of the software, it will not cause uncontrollable situation generated?
Software complexity, invisibility, unpredictability, volatility, combined with the non-continuity features, the program will become like a virus program like covert, infectious, triggering again, even go into an infinite loop can not be dead control. So in the software development process, we need to try to avoid such problems.
2. growing up in junior engineers, which side is more important? There are many problems in the field, what is the most popular current problem areas most in need of software engineering? What is good software design? What is the good software engineering ideas?
The growth of the primary software engineers are the following:
(1) the accumulation of knowledge related to software development, enhance technical skills.
(2) knowledge and experience in the field of problem.
(3) general understanding of software design and software engineering ideas
(4) enhance the professional skills (as distinct from technical skills).
Vocational skills include: ability, ability to communicate and express self-management, the ability to cooperate with others, according to the quality and quantity to complete the task execution and so on.
(5) the actual results. (User evaluation, market share, etc.)
2. summed up his analysis of the feasibility of the project / needs analysis / software design / implementation / testing / project acceptance / learned what "knowledge."
Feasibility Analysis:
Feasibility analysis is conducted in terms of technical, economic, engineering and other projects by the main content and related conditions, such as market demand, supply of resources, the scale of construction, process routes, equipment selection and environmental impact, financing, profitability, etc. research and comparative analysis, financial, economic and social and environmental impact after completion of the project may be made to predict, which made the project worth the investment and advice on how to build and provide a comprehensive basis for decision-making project systems analysis. Feasibility analysis should have predictability, fairness, reliability, scientific characteristics.
demand analysis:
Requirements analysis, also known as software requirements analysis, system analysis needs analysis or requirements engineering, is a developer of an intensive research and analysis, an accurate understanding of the specific requirements of the user and project features, performance, reliability, etc., in the form of non-users demand expressed into a complete requirements definition, to determine what the system must do the process.
software design:
Software design is the SRS from the description, the overall structure of the software system function design requirements identified during the analysis, the division of functional modules, and algorithm determines to write specific code for each module, the specific form of software design.
achieve:
Implementation is specific coding stage.
test:
Under the conditions specified in the program to operate, to discover bugs, measure software quality, and evaluate whether it can meet the requirements of the design process.
Project Acceptance:
Project Acceptance is whether the work or activities within the scope of the provisions of the verification project has been completed, the deliverables are satisfactory, and the results of the verification record a series of activities in the acceptance document.
3. The combination of individual project / twinning individual program / project team experience, to talk about the experience.
In the individual event, because there is no basis for programming, it is a loss, but to keep a check online or ask for help from others. Although the results unsatisfactory, but I learned a lot in the process, which can be considered a very good experience. In the team project, we work for everyone division of labor, the whole process encountered many problems, but can discuss, complementary short board, making the entire project development process more efficient than a person, made me realize the importance of collaboration.
4. Summary of Practice on the course and upgrade to bring you, including the following.
- Statistical software engineering practice, completed the code you how many rows;
2500 lines of code
- You were to spend much time in the second practice of software engineering job? (Make a list)
| experiment | time |
|---|---|
| Experiment 1: Preparation Software Engineering | 2h |
| Experiment two: Software Engineering Individual Project | 8h |
| Experiment III: Improvement mutual evaluation operations | 2h |
| Experiment 4: Software engineering twinning projects | 5h |
| Experiment 5: Software R & D team set up | 1h |
| Experiment Six: Team Project Selection | 3h |
| Experiment 7: prototyping and development project team | 4h |
| It Experiments Eight: prototype-based research and analysis needs of the project team | 4h |
| Experimental nine: the project team needs improvement and system design | 4h |
| Experiment X: designed to improve the system and detailed design of the project team | 6h |
| Experiment XI: Team project design & coding perfect | 25h |
| Experiment 12: Software Testing and Alpha sprint | 6h |
| Experimental thirteen: Beta team sprint and project acceptance | 4h |
- Which one job to make you the most impressive? why?
I was most impressed by is the experimental XII since early for a period of long encoding process, in which encountered many problems, had weak programming skills I appears to be more difficult, so but the course has been to test link, but I the programming phase is not complete, but it seemed more the more strenuous.
- The cumulative number of hours spent on the practice of software engineering? The average number of hours per week spent?
80 hours, 10 hours
- You learn and master a new language, a new platform;
java language; GitHub
- Complete the 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 |
| Eclipse，MySQL | Object-oriented development methodology | Object-Oriented Modeling |
- Other aspects of harvesting or lifting.
In the project development process, the project development process with a new awareness.
5. What problems do you think the current curriculum, do you have any better suggestions.
This semester, in the course behalf of the teacher, the teacher of our best, whether in the classroom or in the experiment, we can learn a lot. Is the project development process, the workload is a little big, because the foundation is weak, it will become more difficult.