| project | content |
|---|---|
| This work belongs to Northwest Normal University Software Engineering courses | <Classroom teachers blog Home Links> |
| Please click on the link to see the job requirements | <Operational requirements> |
| My goal in this course | There could be some practical experience in the computer staff |
Task One: View
Task Two:
First, the question first job blog
by clicking here => link
two, answers to blog in question
1. Software development process how rational and efficient allocation to all members of the task?
After experienced a real project, I feel the need to distinguish between the terms of reference for everyone (this can be a rough definition, such as certain matters in charge of a particular area), then clearly define the responsibilities of these will be publicly disclosed in the project and ask them to take the initiative to assume their responsibilities within the scope of things. Of course, things outside duties should be encouraged to do, but everyone should be encouraged to do 110% of the work, namely to complete their own work at the same time, also we need to be completed within 10% of team affairs. People responsible for things within the same range of responsibilities, you can use this head of claim assignment or project members to take the initiative in two ways, or a combination of these two ways. Arranged for each person's work, everyone did a number of things, if we can very clearly presented in a system, and try to create a project in a benign competitive environment, coupled with hard work and a clear performance management measures to follow up, then we will reduce complaints. Managed well, maybe your members will complain that you give him a task too little of it. In the process, our team did was quite good, very positive cooperation. In this process, I also really understand the importance of cooperation.
2. Analysis software needs to be done before the full software development, but in the actual development can not be avoided sometimes and finished work with different or conflict, then this is not the time should be changed in accordance with the requirements or continue to follow the completion of works?
When software development carried out, when necessary analysis, it can not avoid conflict and subsequent works. This time we are faced with is not it should be changed in accordance with the demand or changes in accordance with the completion of work to do full software requirements. I think this time you should carefully analyzing the needs of the prior needs analysis, and comparison functions to complete the work, to see whether demand before really applies, really benefit users, much in the writing process difficulties and this demand may cause vulnerabilities. after careful and thorough analysis, and then determine whether to continue.
What is the goal 2. software engineering in the end is?
I think that the development of user satisfaction with the system can be modified as of a given cost, under the premise of progress, developed, validity, reliability, understandability, maintainability, reusability, adaptability, portability, traceability and interoperability and meet the needs of users of software products.
Third, by learning how to figure out
the course of the semester, we experience the whole process of software development, from design to implementation, through a very long time, in the process, we also experience the genuineness these problems. really going to know the importance of learning in the course, ask the teacher, the students and discuss their own access to the Internet to find the open book, my personal experience is to clarify these issues before, solved my doubts. I really appreciate the teachers as well as students.
Fourth, whether before or do not understand the problem created new problems?
now before the problem is not not understand is also not a problem of particular concern.
V. various stages of learned knowledge
1. needs analysis phase
serious consideration to each requirement, aware of its importance and unimportance, in the user's point of view, not how you want to write on how to write.
2. design phase
mainly reception design and database design, is very important, only complete database design and layout of the background of the front desk, to make you write code and there is not a clue. to reduce the workload of late.
3. Stage
one after another down to earth functional design of the system.
4. The test phase
must be tested many times multiple angles.
The project acceptance stage
as long as is practical to do, acceptance is equivalent to a test.
Six, brought me upgrade
1. statistical software engineering practice, completed the code you how many rows?
Completed about 3000 lines of code
2. how much time you are in the practice of software engineering homework?
| task | Spend time (h) |
|---|---|
| Software R & D team building | 2h |
| Determine team project and team name | 3h |
| Prototyping team projects | 6h |
| Project needs research and analysis | 8h |
| The project team needs to improve and detailed design | 7h |
| Project design team and perfect coding | 48h |
| Alpha sprint five days | 26h |
| Beta sprint three days | 15h |
3. Which one job to make you the most impressive? Why?
In Beta testing impressed, at this stage, although the preparation of the system has been basically completed, but in the process, due to the carelessness of some preliminary cause of the current system error on some features, we also spent a lot of time of intense changes. I never felt so helpless before, when the problem difficult to solve, but think of work to do before now lead to imperfect results really should not have happened. We also learned a lesson this time, so every step of the software development process is not that a little slack, otherwise it will lead to more problems at a later stage.
4. The cumulative number of hours spent on the practice of software engineering? The average number of hours per week spent?
From the beginning of the project to acceptance, it spent about 120h, the average weekly cost about 13h.
? 5. You learn and master a new language, a new platform
for JSP from the strange to the familiar; Java from a low level to a better level; more familiar with MySQL database; configure the project environment more skilled; learned to use blog garden to learn , published on the blog writing have more knowledge and experience; first contact on the GitHub; for leangoo awareness and use of billboards and so on.
6. 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、GitHub | Prototype method, an object-oriented approach, structured approach | Object-oriented modeling, structural modeling |
7. Other aspects of harvesting or lifting?
Ability to solve problems has increased; and friendship classmates sublimated; greater awareness of unity and cooperation; treat things more rigorous carefully.
Seven experience
in this semester software engineering courses, for me is a challenge. From the requirements analysis phase to the final acceptance of the initial phase of the project, not a stage for the first time are so closely engaged in also We encountered a series of problems, starting with the language selection, to ensure completion of the project selection. many technologies are first heard, a little novel, while looking for information on the internet learning, while writing his projects at the interface, total was made with the plans vary considerably, they convince themselves, will improve learning at a time. to know the interface is beautiful and smooth. just interface it takes quite a long time. then to improve the function of the database, interface features button dislocation, overlapping and so on. no way, change. in the process of change continues to change, the change to the scalp. during development, the programmer must clear thinking, able to articulate, organized, it will diverge, but can be properly controlled. stronger ability to learn, help solve the problem. care must be taken, so as not to cause too much of the system vulnerability is also very important in the code specifications, do comment, as this will ensure the follow-up can be seen in know will not forget. But also I will summarize the knowledge of their own to do the procedure used in the summary. Form their own knowledge. During development, a person can not independently, which requires each member has a unity of heart. Our group the girl is very lively and very united, in the course of the entire project completed in 2005 with a high degree, very hard, to make himself would make a satisfying project.
Here I have some experience of it related documentation must be complete, and that all personnel involved in the development of both know the meaning of the document where you want to express; must pay attention to do more experiments, a demo can not spend more than time, but do not do demo, the core of the program did not do the experiment, the other things are around the core of the program to write, in case of an error, the delay is more time; pay attention to the user experience; test plan many times, in batches, not all developed it is also likely to rework doing the test. persist more than two months, the end of the acceptance of the project, when the fruits of their efforts to get the teacher's praise, before that no matter how tough is worth it, and he is very happy. we hope be able to maintain this attitude of learning, seriously everything later. Thank you, teacher assistant for us not to give up.
Eight, what problems do you think the current curriculum, do you have any better suggestions
this course is very good, very serious and responsible teacher, teaching assistant, too.