中平籤詩一首

事端百出慮雖長
莫聽人言自主張
一著先機君記取
紛紛鬧裡更思量

What kinds of testing should be considered?

Type of Testing	Description
Black box testing	Not based on any knowledge of internal design or code. Tests are based on requirements and functionality.
White box testing	Based on knowledge of the internal logic of an application's code. Tests are based on coverage of code statements, branches, paths, conditions.
Unit testing	The most 'micro' scale of testing; to test particular functions or code modules. Typically done by the programmer and not by testers, as it requires detailed knowledge of the internal program design and code. Not always easily done unless the application has a well-designed architecture with tight code; may require developing test driver modules or test harnesses.
Incremental integration testing	Continuous testing of an application as new functionality is added; requires that various aspects of an application's functionality be independent enough to work separately before all parts of the program are completed, or that test drivers be developed as needed; done by programmers or by testers.
Integration testing	Testing of combined parts of an application to determine if they function together correctly. The 'parts' can be code modules, individual applications, client and server applications on a network, etc. This type of testing is especially relevant to client/server and distributed systems.
Functional testing	Black-box type testing geared to functional requirements of an application; this type of testing should be done by testers. This doesn't mean that the programmers shouldn't check that their code works before releasing it (which of course applies to any stage of testing.)
System testing	Black-box type testing that is based on overall requirements specifications; covers all combined parts of a system.
End-to-end testing	similar to system testing; the 'macro' end of the test scale; involves testing of a complete application environment in a situation that mimics real-world use, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems if appropriate.
Sanity testing or smoke testing	Typically an initial testing effort to determine if a new software version is performing well enough to accept it for a major testing effort. For example, if the new software is crashing systems every 5 minutes, bogging down systems to a crawl, or corrupting databases, the software may not be in a 'sane' enough condition to warrant further testing in its current state. Smoke tests get their name from the electronics industry. The circuits are laid out on a bread board and power is applied. If anything starts smoking, there is a problem. In the software industry, smoke testing is a shallow and wide approach to the application. You test all areas of the application without getting too deep. This is also known as a Build Verification test or BVT.
Regression testing	Re-testing after fixes or modifications of the software or its environment. It can be difficult to determine how much re-testing is needed, especially near the end of the development cycle. Automated testing tools can be especially useful for this type of testing.
Acceptance testing	Final testing based on specifications of the end-user or customer, or based on use by end-users/customers over some limited period of time.
Load testing	Testing an application under heavy loads, such as testing of a web site under a range of loads to determine at what point the system's response time degrades or fails.
Stress testing	Term often used interchangeably with 'load' and 'performance' testing. Also used to describe such tests as system functional testing while under unusually heavy loads, heavy repetition of certain actions or inputs, input of large numerical values, large complex queries to a database system, etc.
Performance testing	Term often used interchangeably with 'stress' and 'load' testing. Ideally 'performance' testing (and any other 'type' of testing) is defined in requirements documentation or QA or Test Plans.
Usability testing	Testing for 'user-friendliness'. Clearly this is subjective, and will depend on the targeted end-user or customer. User interviews, surveys, video recording of user sessions, and other techniques can be used. Programmers and testers are usually not appropriate as usability testers.
Install/uninstall testing	Testing of full, partial, or upgrade install/uninstall processes.
Recovery testing	Testing how well a system recovers from crashes, hardware failures, or other catastrophic problems.
Failover testing	typically used interchangeably with 'recovery testing'
Security testing	Testing how well the system protects against unauthorized internal or external access, willful damage, etc; may require sophisticated testing techniques.
Compatibility testing	Testing how well software performs in a particular hardware/software/operating system/network/etc. environment.
Exploratory testing	Often taken to mean a creative, informal software test that is not based on formal test plans or test cases; testers may be learning the software as they test it.
Ad-hoc testing	Similar to exploratory testing, but often taken to mean that the testers have significant understanding of the software before testing it.
Context-driven testing	Testing driven by an understanding of the environment, culture, and intended use of software. For example, the testing approach for life-critical medical equipment software would be completely different than that for a low-cost computer game.
User acceptance testing	Determining if software is satisfactory to an end-user or customer.
Comparison testing	Comparing software weaknesses and strengths to competing products.
Alpha testing	Testing of an application when development is nearing completion; minor design changes may still be made as a result of such testing. Typically done by end-users or others, not by programmers or testers.
Beta testing	Testing when development and testing are essentially completed and final bugs and problems need to be found before final release. Typically done by end-users or others, not by programmers or testers.
Mutation testing	a method for determining if a set of test data or test cases is useful, by deliberately introducing various code changes ('bugs') and retesting with the original test data/cases to determine if the 'bugs' are detected. Proper implementation requires large computational resources.

Triangle of project QCD

When a project is running, what will you do to balance the triangle of QCD?
Q=Quality, C=Cost, and D=Delivery

We all know we wanna make more money from a project. But if the quality is too bad, you probably won't get any money.

When the project is phasing into another stage, you probably find out you'd better to add some more human resources or hardware resources. But it will bring more cost.

If you can not add more resource, but also need to remain the higher quality, then it might bring some impacts on the delivery date.


For a project management, there are many phases and tasks need to be take care. But the most simple way is to balance the QCD triangle.

What do you think about that?

再談選購NB

再談談選購NB吧

拿最近NB市場的實例，或許會比較有趣

* 大尺寸，還是小尺寸
買NB，你要買大尺寸，還是小尺寸？
12吋NB，長時間使用，螢幕大小真的太小，眼睛肯定會很酸。回想以往使用15吋CRT，然後把解析度設定成1024*768的時代吧～～
14～15吋的NB，對眼睛來講，輕鬆多了，可是，2~3公斤的重量，帶來帶去，可真不方便。次數多了，乾脆不帶了，那又失去NB容易攜帶的利基了！

* 高階還是中階？
你要買 Pentium M 還是 Celeron M？要最新的 Sonama 、Dothan 還是要普通的 Pentium？

* 內建顯卡還是獨立顯卡
其實我不太玩遊戲，所以獨立顯卡對我來講不需要

實例：
Acer TravelMate 2303Lci: CM1.4, 40G HD, Combo, 15": $28,000
Acer TravelMate 382Tci: PM1.6, 40G HD, Combo, 12": $40,000
Acer TravelMate 4102Lci: PM1.73(Sonama), 60G HD, Combo, 15" 64M ATi: $40,000
Acer TravelMate 3002WTci: PM1.73(Soname), 60G HD, 512M, Combo, 12": $50,000

你會買哪一台？

從小處著眼看大局面

很多事情都可以從小處著眼，來看整個大局面
一個人、一件事、一個物品、一個局面，都是由很多小的元素所組成，懂得從這些小元素來拼湊整個大局面，你就比較容易了解為何事情會是那樣的發展，會是那樣的呈現，會是那樣的結果