| Q | A |
|---|---|
| This work belongs courses | Spring 2020 Computer Software Engineering Institute (Roger Ren Jian) |
| Where the job requires | The first personal blog jobs |
| My aim in this course is | Cooperation between the learning team, how organized and efficient software development |
| This job helped me in terms of what specific goals | Strengthen my understanding of software engineering |
1. Quick Look textbooks complete lists you still do not understand the 5-10 issue
-
2.4.1 The following exercises can be used to train students in the basic skills program
1. All the command-line tools and Notepad editor, without Viusal Studio and other integrated editing environment, each person manually create and compile a command-line program of C: "Hello World"
Q1: use some basic integrated editing environment really affect you?
Now, the students around me are basically used Visual Studio or the IDEA software to write programs, but it also does is to accelerate the speed of our writing program code. And we use this to our basic skills had an impact yet? I think not, and if you want to strengthen basic skills, should be to do some real hands-on projects, combined with a variety of algorithms, knowledge to solve problems. For example, in just a freshman, I also use ordinary DEVC ++ to write programs. And when I did not feel anything when the code has improved the ability to do, is we need to submit the program's course work written by its own, but only if I successfully finished high-precision calculator that find themselves in the past and I have very big difference, and this is my relationship with the programming environment is very small.
-
4.5.4 How Pair Programming
3. continue to rotate the driver and navigator roles, do not work continuously over one hour, every hour of work rest for 15 minutes. Pilot to control time.
Q2: driver and co-driver to rotate it? Why can not one hour of continuous work?
Like real life at the real situation, racing driver and navigator are their duties, and not continue to rotate roles, because if fixed, so there is plenty more time for everyone to learn something on their own jobs. It can clear division of labor. And I believe that every computer students have felt, when writing a program into the state, really do not want to stop, so I think the time of continuous work should consider their own situation is specifically determined.
-
Unit tests should cover all code paths.
The actual project engineer did know, a lot of statements in the program is used to handle all sorts of anomalies, most of these cases will not occur. But these statements are not covered, then this module will drop coverage, amounted to less than 80% of the target, it will spend a lot of time to construct all sorts of strange test data.
Q3: This article is the concept of different places, so the unit tests to cover all code paths do?
I think not, as mentioned above, the second paragraph of text, a lot of statement is used to handle all sorts of exceptions, and some actually not a consideration. We should consider how the impact on users, whether the program should be designed. Rather than to complete the task and complete the task.
-
Myth of the three: good ideas will win
Q4: Is it a good idea not to win it?
In this paper, an example cited is the layout of a computer keyboard, the QWERTY keyboard is now, knock them out when only 10 percent of English words can not leave the keyboard listed in the fingers. But if you use Dvorak keyboard layout, you can play the keyboard listed 60% of common words, it will help reduce the burden on the fingers and associated muscles, reduce fatigue, while accelerating the typing speed. Here is an example of good ideas do not win? In fact, I think this idea is not well thought of them as he did not consider the fact that most people now have adapted to the QWERTY keyboard, should be replaced, there will be a lot of people are not suited, even before the keyboard will choose.
-
Myth five: To become an expert, to the field of innovation
Q5: Only on the field should have a detailed knowledge of innovation.
Even though I did not learn the computer, but he created the site Alibaba B2B is doing the best, but this is it innovative? The real innovation is Ma hands of those technical personnel, is the real talent of the computer. And Ma is the creation of a company, and the conditions for these people to innovation. It should be said, if not necessarily a leader in this field in order to innovate. When it is it must be an expert, if you are not an expert, you would not even understand the field, then how can it innovation, but more so-called civil division.
2. Will the "software" and "software engineering" is how these words appear - when, where, who?
- Software: In the engineering environment, the earliest known term "Software" in August 1953, Richard R.Carhart proposed in the memorandum RAND Corporation's study. In 2000, Yale Law School librarian Fred Shapiro published a letter, the first letter contains the word "software" was found in the search. JSTOR electronic records, two years earlier than the OED references. So most people believe Tukey coined the term.
- Software Engineering: In the early Apollo missions, Hamilton began to use the term "software engineering", compared with other projects at the time, software development has not taken seriously, nor be regarded as scientific. With the passage of time until the "software engineering" to get the word the same as any other technical disciplines of respect.
3. Additional [Title]: We all know the origin of software and software engineering, software engineering development process to ask what you think of interesting trivia and stories?
It should be the millennium bug problem. Due to some problem in computer programming, computer makes when dealing with date and time after January 1, 2000, incorrect operation may occur, resulting in serious consequences. This is the year due to the use of a computer program expressed as two numbers, such as 1998 is expressed as "98", so that some software will "00" misinterpreted as 1900. May cause the device to shut down, or more catastrophic consequences.
4. Internet survey about the current popular source version management software and project management software, what are, what advantages and disadvantages? (Tip: search in the Microsoft TFS , Git , Mercurial , GitHub , Bitbucket , Trac , Bugzilla , the Rational , the Apple XCode )
- Microsoft TFS: is a project management tool developed by Microsoft, is the core collaboration platform Microsoft Application Lifecycle Management (ALM) solutions.
- Pros: on demand version of the task, project progress glance, agile, msf projects such support.
- Cons: Few teams can fully utilize all the features that most only source code management this section.
- Git and GitHub: Git is a source code version control system, a manageable, traceable source tools project. GitHub is a hosted Git repository to provide services platform.
- Advantage: Git is distributed and sub-blog using the pointer. Copy Chi points easier.
- Cons: not too much command the overall design, the repeat function, too much functionality into one command. Causes the command complex.
- Mercurial: cross-platform distributed version control law
- Advantages: simple, high-performance, controllability, fully distributed development cooperation
- Cons: branch management is not flexible.
- Bitbucket: Atlassian is provided by a web-based repository hosting services, support for Mercurial and Git version control system.
- Benefits: private repository raise unlimited number of free accounts and free accounts can be used.
- Cons: good reputation but the number of people using git not high.
- Trac: is Edgewall developed and maintained open source web interface project management, bug tracking software.
- Pros: very flexible, and it can be arbitrary control and SVN integration
- Disadvantages: function is not very powerful
- Bugzilla: is a tool for network management software defect tracking program
- Pros: Free, a Chinese version support
- Cons: Quick search inaccurate results. Only manage defects.
- Apple XCode: Xcode is Apple provided developers with an integrated development environment for developing macOS, iOS, WatchOS and tvOS applications.
- Pros: fast compilation speed, each operation is very quick and easy. Automatically provides undo, redo and save functions without writing any code.
- Cons: After an updated version of a plug-in might fail.