Chapter 5 of modern software engineering discussion-Chapter 8

Chapter 5

1. What is the relationship between the team model and the team's development model?

The team mode refers to the way a team member works together, and the team's development mode is used by the software development team in the software development process. That is to say, the team development mode is a special team mode for applications in the software development field.

 

2. If you lead a new project, how do you choose a "suitable" team model?

If I take the lead in creating a brand new project, I will select people with different characteristics and give full play to their respective specialties. Similar to the functional team model, we will discuss their affairs and work together equally. For example, I am good at code writing, database design, Requirement Analysis among members, Document Sorting and summarization, and testing.

 

3. there are many ways and reasons to quarrel. Some quarrel is actually a discussion. Such quarrel is actually conducive to the progress of products and a positive factor for improving efficiency, which can be encouraged as appropriate; but some are caused by personal factors (such as personality and shirking responsibility). This situation should be avoided and curbed. I think there are several ways to avoid quarrel:

And Pm, design, testing phase:

1) Everyone is clear about their tasks and responsibilities. When prompted, they should correct their problems and have a good attitude of admitting mistakes. They should be rational reminders of others' problems.

2) Case-based, rational

And user stage:

1) put users first, and products are made for users to use. They are expected to get their certification and affirmation, and listen carefully to their suggestions.

2) There is an academic specialization. In many cases, users and product developers have imperfect discussions on product requirements. They need to know how to stand in the perspective of others (professional knowledge and expressions) let's look at the problem and understand what the user wants.

3) using users as co-developers is an indisputable way to quickly improve code and efficient debugging.

Everyone is trying to make better products. It is better to treat this quarrel as patience and training for their own technologies, and the team is constantly becoming closer and better.

 

4. What is the difference between team spirit and collectivism? Let's look back at the learning process in primary and secondary schools. In a group, how much work is done in the form of "team work, how much work is done in the form of a "workgroup? Perhaps most of the work is done in the form of "non-team. What is the difference between "Team Spirit" and "collectivism?

The Team Spirit emphasizes the initiative of individuals. The team may not necessarily have clear leaders, and members may have decision-making powers. Each team member must also work together to share responsibilities. Each person has different skills,.

While collectivism emphasizes more clear leaders. Each person has the same goal, the same skill, and the same passive slack of members.

 

3. In the cellular mode, a group of people start to write code without a specific division of labor. The team's production capacity is low and there is no direct communication between teams, thus affecting the evaluation of team performance.

Physician-attending mode: This mode is often represented by only one person who is working hard. Other team members are only visible, resulting in a decline in the overall production capacity of the team.

Star mode: stars often overwrite the sum of other team members, and cannot maximize the performance. Often, the performance of star members affects the performance of the entire team.

Community mode: In this mode, if everyone contributes, the overall performance of the Team will certainly be improved, but not everyone is willing to contribute to the team, therefore, the performance of the team will be affected by the voluntary degree and contribution of the team members.

Amateur troupe mode: the alternate roles change, so that the performance of the team in different projects also changes, if a team member can assume the correct role, it will bring the greatest benefit to the performance of the entire team.

Secret team: In this mode, the team's performance cannot be estimated, so the team members must make their own efforts. Team members can work together in harmony to bring good performance to the team.

The secret Team and the Special Agent team are very important to their own abilities ,.

As the name suggests, the conductor's command quality directly affects the team's performance.

Jazz mode, with impromptu play among team members and status Affecting Performance

The functional model affects the team performance mainly by the combination of members and achieving good performance.

The bureaucratic model, as its name implies, is only capable of good communication, mainly affecting its performance.

5. The form and process of the Chandler team are too idealistic. Many things are drills that are not practical. But the Chandler team has the qualities of a good team. They are persistent and never give up on their dreams. We can get some experiences and lessons from them, which will play a significant role in our future career.

 

Chapter 6

After reading so many methodologies, some people may be confused. Which development method is better? This is not a problem in practice. Some scholars have also listed some simple problems to help people make decisions:

Table 6-3 problem Introduction

Problem	Yes-process that is biased towards the traditional waterfall + document	No- Agile Process
1. Do projects require a clear spec?
2. There are no clear users in the project, and users cannot be contacted.
3. Is the software system large?
4. Is the software system complex? For example, Real-Time System
5. Does the software have a long life cycle?
6. Are you using poor software tools?
7. Are software project members distributed in different regions?
8. Does the team have a "document first" tradition?
9. Is the team's programming technology poor?
10. Is the software system to be delivered approved by certain industry regulations or administrative regulations?
11. Do users see the results after the development is complete?
12. Is the project delivered at one time?

 

6.3.2 how teams build software

1. Boss and others seize the market dynamics and obtain requirements

2. Developers propose design solutions as needed

3. Discuss the feasibility of the solution and make improvements

4. Start writing (not agile development, socode and fix)

5. coding is tested at the same time, and a balance point is found based on user needs and development.

6. After the development is completed, the product is put on the market, receive feedback, and modify the product to enter the next iteration.

Chapter 7

Question 1: The software engineering principles and MSF and agile summarized by Barry Boehm:

1. This principle focuses on phased planning, while MSF and agile focus more on flexible development.

2. This principle requires continuous inspection and authentication to detect problems in the early stage. MSF and agile also require early detection of problems, but they are achieved by making products as early as possible.

3. This principle adheres to the standard product control, while MSF and agile care more about communication between members.

4. This principle and MSF and agile both use modern programming methods and tools, but the methods and tools used are slightly different.

5. The development process of this principle ensures that team members can be divided into stages and modules, while each team member in MSF and agile is responsible for the project.

6. These two principles use fewer and more refined personnel to reduce communication costs.

7. This principle improves the software process and quality through summarization, while MSF and agile will improve the team members' abilities by summarizing more.

 

 

Question 2: What is the difference between the MSF principle and the principle proposed by Barry Boehm:

MSF is agile development, while the principles proposed by Barry Boehm tend to be traditional software development types and emphasize clear requirements.

MSF is expected to change, while the principle proposed by Barry Boehm is to detect errors and problems in the early stage,

MSF emphasizes business value, while Barry Boehm adheres to the standard process,

 

Programmers have different levels of self-cultivation and work quality. The concepts and working principles in software engineering are just a criterion to help programmers constantly judge and improve themselves, however, you cannot simply follow these rules. They vary from person to person.

Chapter 8Requirement Analysis

Question 2: You want to write an enterprise management software. Who are you looking for to do user research? List the user types that you consider important and the methods that you consider appropriate user surveys.

Employees-most users who use the System

Boss-learn about the company's development from the system

System Administrator-the person responsible for managing the system

Grass-roots leadership-used together with employees in daily work

Employees and grass-roots leaders should be the most important user types, because they are the people who primarily use this system.

 

3. It is impossible to restore to the average daily workload of 30 hours, because the scheduled time has been used up.

 

4. I feel that such a project manager is better because it takes too long to mobilize the conference. After the project starts, everyone should be clear about the project's objectives. The main problem is to focus on solving the specific problems encountered in the project, such a one-day mobilization conference is completely unnecessary. The project manager is more focused on projects and project members.

 

Chapter 5 of modern software engineering discussion-Chapter 8