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/bkcq/p/10516756.html
Of questions to answer:
1. For software engineers, this position is not one that is not suitable, but must have a personal interest in the software engineer profession: Because only interested to make you enjoy it, you enjoy it will generate enthusiasm, passion to make you achieve outstanding; b cognition: cognitive effects attitude, attitude is everything; c.EQ (EQ): after entering the intelligence community has been retired as a secondary position, EQ aspects what is more important, including interpersonal skills, communication skills, resistance to stress, ability to manage crises; d strong willpower: both from a technical or engineering, had to have assiduously, perseverance; e. He will lead the team: after the technical standards, we must cultivate a personal leadership skills to lead a team to effectively work with others in order to achieve greater results.
2. I think the personal choice of the team's first look at whether there is a core of the team, but the core purpose of this work is primarily whether everyone on the team can firmly together toward the same goal or a most important goal . The main core of the ability to have: a strong leadership skills; b perfect personality; c ability to execute decisively....
The development prospects of the team's performance from the following factors:. A good organization and leadership: a collective enterprise, small to a functional department or a working group, to organize effectively, the team members have a higher loyalty, Well, we all preferred a recognized team leader is crucial; b 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 is the organization against all odds to make the team through thick and thin; c 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 weak character, or. is a piece of master surface, a combination of what they can bring to the team together, therefore, members of the complementary type, is the basis of "glue" the organization; d reasonable incentive assessment: people are lazy, a team organization in order to maintain lasting power and vitality, it is necessary to introduce competition mechanism, at the same time, a team from unstable Stable development process, the assessment must be incentives to survival of the fittest, to Jiangyoufalie; e learning hoisting system: man is his own worst enemy, an organization is their 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:
a two-month project team also learning not only how to work in teams from technical aspects, one good team formation has been thinking, insights! So the question for a test of the proposed Task 5 is my personal experience, the answer will come very naturally to them the.
(2) summarize their project feasibility analysis / requirement analysis / software design / implementation / testing / project acceptance / learned what "knowledge"
- 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.... - 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. - 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: This section includes two aspects, one is coded, is a test. Our language team project team using c #, so I have this language programming techniques have improved. With the understanding of the development of the project coding standards.
- 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 / pair personal experience of program / project team, talk about the experiences
from individual project / program documentation pair / team projects, systems development to the current project closure, each will spend a lot of time doing homework , energy, remember when just getting started with development of the system is ignorant, confused and do not know where to start, you can blink of an eye, again and again, bug fixes, the system checks, acceptance preparations, there is an achievement sense. A series of documentation requirements documents, system design documentation, coding standards and other documents once again modified and look for bug again and again is to achieve better inventory management system, the process is long and painful, but the result is satisfied.
(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?
For coding project, the project team are involved each time to prepare and implement written, but the exact number was not count the ways. - 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?
Experimental nine Teamwork 5: project team needs to improve the system design and operation impressed me the most, because in the research and analysis of experimental prototype-based team project needs, the needs of our group project research methods warehouse management system errors, survey law 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, it takes more time, 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 over a month in software engineering time, spend an average of three to four days 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.