A: Experiment name: Team Project Review & course summary
II: experimental purposes and requirements
(1) master the software project will be assessed process;
(2) to reflect summarize course content.
Three: Experimental Procedure
Task one: 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.
Task two: software engineering experience to learn and practice a semester project, ask each student to complete a personal learning summary blog.
Four: Content Experiments
|
|
|
|---|---|
|
|
|
|
|
|
|
|
(1) master the software project will be assessed process; (2) to reflect summarize course content. |
Task One:
Acceptance of this team feedback form submitted in Github repository: https://github.com/maomaochongzu/tuanduizuoyeshiyanba
Task Two:
(1) For the blog link "Experimental Software Engineering to prepare a" mission five questions: https://www.cnblogs.com/wangxuegang/p/10512539.html
Of questions to answer:
the development prospects of the team's performance from the following factors:
1. common cause of vision: an organization with the ability to go farther, longer, due to the team if there is a common vision, that is, the team belief, faith organizations is to allow team members to overcome all difficulties, through thick and thin;
2. complementary member type: To ensure that the organization's strong and effective team, composed of members of the organization is critical, it is difficult to imagine that an organization is irascible, or an effeminate or are experts surface of a piece, a combination of what they can bring to the team together, therefore, complementary type of foundation members, is the "glue" the organization;
learning 3. upgrade the system: one of the greatest enemy that is, himself, an organization is its own worst enemy. When a team to rely on experience as the work of the organization is likely to fall into the vicious circle "empiricism", there is likely to be trapped in a "rigid", it is possible to "die in their own hands", an organization in order to maintain Built to Last, in order to maintain vigor, it is necessary to rely on the system to enhance learning.
3. First, determine customer requests are reasonable, if reasonable and make the appropriate solution, if unreasonable, stay calm, do not be emotional impact of the customer, calm to communicate, to find a solution acceptable to both sides.
Clarify how through learning / practice / discussion to figure out:
among this team project development process, learned a lot of knowledge, first of all let me feel the importance of teamwork project team to learn not only the technical aspects but also on how teamwork, a team of outstanding aspects of formation have to think, but to master a lot of specialized knowledge.
(2) summarize their project feasibility analysis / requirement analysis / software design / implementation / testing / project acceptance / learned what "knowledge"
- Requirements Analysis: I know several ways to get their needs using the occasion:
A site observation: pry (the site actually happened); b
Interview: nosy;
c surveys: taking;
d conference seminar: Brainstorming ; E
prototype evaluation: interface (sample) iteration (with ability prototyping);. F
scene analysis: imitation (playing with a role); G
other: Document archeology, analysis cases. - Feasibility Analysis: The first stage of the software life cycle is to study the feasibility of the project, project feasibility study is not the solution, but rather to determine to determine whether the software project worth doing, can use as much as possible price, in as much as possible within a short period of time developed.
Task feasibility study are: a determining issue is not worth solving; b if the problem is not a viable solution should be advised not to this software program, in order to avoid wasting time, resources, manpower and time; c if the problem is worth... solution, then recommend a good solution, and to develop a preliminary project plan.
The contents of the feasibility study: feasibility study to analyze the following aspects:.. A technical economic feasibility feasibility b c d legal feasibility feasibility operating system e f-effective choice of development programs.... - Software design: software design goal is to convert the software requirements specification expressed in user functionality, performance and other requirements to describe how to achieve these requirements, the results can guide the subsequent coding implementation, testing.
Software design stage and tasks: a traditional structured design method is divided into software architecture design, design data, process design and interface design of four parts; Object B Object-oriented software design method will be divided into a structural design system. class design / data design, interface design, component-level design of four parts;. c outline design (system design) to convert the software requirements for the system configuration data structures and software;. d detailed design (design process), the representation of the structure refined to obtain detailed data structure of the software and algorithms.
In this stage the software design, but also for learning UML modeling diagrams: was use case diagram, class diagram, an object diagram, a sequence diagram, a collaboration diagram, a state diagram, an activity diagram, component diagram, FIG deployment, in which FIG class the main study. - Implementation: The project development team we are using C # language, experienced access to information, write code modules to run code integration, system testing, bug fix and other aspects of project development coding standards with understanding.
- Testing: This part of the black box testing and Lily were learning, also known as structural testing white box testing, black box testing focuses on functional test software, and not a substitute for white-box testing black box, which is complementary with white box testing methods, it is likely to find other types of errors found in white-box testing is not easy.
- Project Acceptance: After the software project implementation, but also for project implementation, maintenance and management.
(3) a combination of personal items / junction personal experience of program / project team, talk about the experience
for a period of two months of the project development team is already ending, the formation of the team from the beginning to the end to complete the task, experienced project topics, prototyping , ...... needs analysis, coding, testing the system is running, bug fixes, almost every time takes a long time, sometimes not getting the expected result, but we will try to do, acceptance preparations carried out, there is a sense of accomplishment. Again and again to modify a series of documentation requirements documents, system design documentation, coding standards and other documents, making our project a perfected step by step, in short, still have the outcome.
(4) summarize the course of the practice of summary and give you a lift:
- Statistical software engineering practice, completed the code you how many rows?
From access to information to a specific code is written, after a long time, in a time of changes among specific write how many lines do not remember, but I think it does not matter how many lines to write, and through this project how much programming knowledge to develop a master class, it is meaningful. - You were to spend much time in the second practice of software engineering job?
|
|
|
|---|---|
| Experimental Software Engineering to prepare a |
|
| Software engineering experiment two individual events |
|
| Improvement of the peer review with three operations |
|
| Experiment 4 software engineering twinning projects |
|
| Experiment 5 Teamwork 1: You set up software R & D team |
|
| Experiments six team Assignment 2: Project Selection Team |
|
| Experiment 7 Team Assignment 3: prototyping and development project team |
|
| 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 |
|
| Improved system design and detailed design of the project team: 6 experiment ten teamwork |
|
| Experimental eleven Teamwork 7: Team project design & coding perfect |
|
| Experimental twelve Teamwork 8: software testing and Alpha sprint |
|
| Experimental thirteen Teamwork 9: BETA team sprint and project acceptance |
|
- Which one job to make you the most impressive? why?
Experiment 7 3 Team work: team project prototyping and development of this work is to me the most profound impact once, because in the experiment, we can be said to be ignorant of the method of prototyping, from the completion of the experiment received a mandate to , demand research method we project our team warehouse management system errors, questionnaire does not apply, so that in nine experiments necessary to complete the project needs improvement and system design but also on the demand for re-investigation and analysis, the task is relatively large, time spend more, so impressed me more profound. - The cumulative number of hours spent on the practice of software engineering? The average number of hours per week spent?
Cumulative spending nearly two months on software engineering time, spent more than four days of time per week. - You learn and master a new language, a new platform?
To learn and master a new language, a new platform: blog, GitHub, Visio2013, Mockplus, blade, SQL Server2014, Visual Studio, etc. - 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 |
| Github、sql sever2014、Visual Studio | Prototyping, structuring process, the surface of the object type development method | Modeling the object plane type |
- Other aspects of harvesting or lifting:
For some problems in the development process of the project team, encountered unexpected itself, the other members of the project team team will give advice and suggestions, which in others learned some knowledge, and making the project development speed. Each project members division of labor, co-ordination, teamwork can be a good prize.
(5) What do you think the current problems of course, do you have any better suggestions?
After a semester of software engineering subjects of this study, I can attest to: the excessive coursework. I am basically a lot of time on this subject every week experiment. I know every teacher is content to spend a lot of thought experiment, assistant assessment work is not easy. It may be too assignments, sometimes mental fatigue, resulting slack, but would be contrary to the original purpose of the experiment. So, my suggestion is: experimental tasks appropriate compromise to achieve high efficiency and high quality.