| project | content |
|---|---|
| Course Title | 2016 Computer Science and Engineering Software Engineering (Northwest Normal University) |
| Work requirements | Experimental fourteen project review team & course summary |
| Course learning objectives | (1) master the software project will be assessed processes, (2) to reflect summarize course content. |
Task One: Team Project github repository address link: GitHub repository
Task two: course summary
Summed up his analysis of the feasibility of the project / needs analysis / software design / implementation / testing / project acceptance / learned what "knowledge."
Feasibility analysis: is produced by the project 's main content and related conditions, such as market demand , supply of resources, the scale of construction, process routes, equipment selection, environmental impact, financing, profitability, etc., from the technical , economic, engineering, etc. conduct 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 how the construction of advice for project decisions provide a comprehensive basis of systems analysis methods . Feasibility analysis should have predictability, fairness, reliability, scientific characteristics.
Requirements 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, user non-expressed in the form of demand into a complete requirements definition, to determine what the system must do the process.
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. The problem is many things and abstract them, and their different abstraction levels and angles. The problem or something decomposition and modularity make the problem easier to solve, the more the number of small modular decomposition of the more, the side effects that enable designers to consider more modules between the coupling of the situation.
Program code: This phase is the result of software design into a computer program code can be run. In a program to develop a unified coding must meet standards in writing. In order to ensure the program's readability, ease of maintenance. Improve the efficiency of the program.
Software Testing: After the completion of the design software to conduct rigorous testing, found a software problem in the entire software design process and correct the problem. Throughout the test phase is divided into unit testing, assembly and testing, the test system in three stages.
Task three: a combination of personal items / junction personal experience of program / project team, talk about the experience.
Learning this course, as well as the diversification of teacher taught me not only from the theoretical grasp of software engineering, as well as from different instances, so that theory and practice to get a good combination. A whole semester, in general, or learned a lot of things, there are many places worthy of recognition, in fact, in my opinion, is not so much a software engineering curriculum, as it is an idea. Is a process of how to analyze and deal with the problem, it should be said that the scope has been limited to far more than the course, the idea of becoming a comprehensive solution to the problem can be a collection of a lot.
Task four: Summary
- 1. Statistical software engineering practice, you completed the code number of rows.
About four thousand lines of code. -
2. You were how much time each homework software engineering practices?
experiment When using (min) Experimental Software Engineering to prepare a 60 Software engineering experiment two individual events 120 Improvement of the peer review with three operations 60 Experiment 4 software engineering twinning projects 200 Experiment 5 software R & D team building 70 Experiments six team project topics 70 Experiment 7 team prototyping and development project 90 Experimental research and analysis needs eight prototype-based team projects 90 Experimental nine team project needs improvement and system design 110 Experimental ten project team to improve the system and detailed design 200 Well-designed experimental eleven project team and coding 120 If a software testing and test Alpha sprint 500 Beta test thirteen team sprint and project acceptance 550