Microsoft Bing

After a long wait Microsoft ready to launch Search Engine -'Bing'. It makes people for better decisions at Bing.com.

Decision Engine goes beyond search to help customers deal with information overload.

The result of this new approach is an important beginning for a new and more powerful kind of search service, which Microsoft is calling a Decision Engine, designed to empower people to gain insight and knowledge from the Web, moving more quickly to important decisions. The new service, located at http://www.Bing.com, will begin to roll out over the coming days and will be fully deployed worldwide on Wednesday, June 3.

"Today, search engines do a decent job of helping people navigate the Web and find information, but they don't do a very good job of enabling people to use the information they find," said Steve Ballmer, Microsoft CEO. "When we set out to build Bing, we grounded ourselves in a deep understanding of how people really want to use the Web. Bing is an important first step forward in our long-term effort to deliver innovations in search that enable people to find information quickly and use the information they've found to accomplish tasks and make smart decisions."

Microsoft's popular cashback program, now dubbed Bing cashback, with more than 850 merchants and more than 17 million products available, will be fully integrated into the Bing Shopping experience.

Microsoft is committed to building better tools to help people find the shortest distance from their initial search query to the point of making an informed decision. Bing is an important first step toward this long-term vision and a strong indicator of Microsoft's commitment to move search technology forward for customers.

Bug is simply (not) a bug

Severity Wise:

• Major: A defect, which will cause an observable product failure or departure from requirements.
• Minor: A defect that will not cause a failure in execution of the product.
• Fatal: A defect that will cause the system to crash or close abruptly or effect other applications.

Work product wise:

• SSD: A defect from System Study document
• FSD: A defect from Functional Specification document
• ADS: A defect from Architectural Design Document
• DDS: A defect from Detailed Design document
• Source code: A defect from Source code
• Test Plan/ Test Cases: A defect from Test Plan/ Test Cases
• User Documentation: A defect from User manuals, Operating manuals

Type of Errors Wise:

• Comments: Inadequate/ incorrect/ misleading or missing comments in the source code
• Computational Error: Improper computation of the formulae / improper business validations in code.
• Data error: Incorrect data population / update in database
• Database Error: Error in the database schema/Design
• Missing Design: Design features/approach missed/not documented in the design document and hence does not correspond to requirements
• Inadequate or sub optimal Design: Design features/approach needs additional inputs for it to be completeDesign features described does not provide the best approach (optimal approach) towards the solution required
• In correct Design: Wrong or inaccurate Design
• Ambiguous Design: Design feature/approach is not clear to the reviewer. Also includes ambiguous use of words or unclear design features.
• Boundary Conditions Neglected: Boundary conditions not addressed/incorrect
• Interface Error: Internal or external to application interfacing error, Incorrect handling of passing parameters, Incorrect alignment, incorrect/misplaced fields/objects, un friendly window/screen positions
• Logic Error: Missing or Inadequate or irrelevant or ambiguous functionality in source code
• Message Error: Inadequate/ incorrect/ misleading or missing error messages in source code
• Navigation Error: Navigation not coded correctly in source code
• Performance Error: An error related to performance/optimality of the code
• Missing Requirements: Implicit/Explicit requirements are missed/not documented during requirement phase
• Inadequate Requirements: Requirement needs additional inputs for to be complete
• Incorrect Requirements: Wrong or inaccurate requirements
• Ambiguous Requirements: Requirement is not clear to the reviewer. Also includes ambiguous use of words – e.g. Like, such as, may be, could be, might etc.
• Sequencing / Timing Error: Error due to incorrect/missing consideration to timeouts and improper/missing sequencing in source code.
• Standards: Standards not followed like improper exception handling, use of E & D Formats and project related design/requirements/coding standards
• System Error: Hardware and Operating System related error, Memory leak
• Test Plan / Cases Error: Inadequate/ incorrect/ ambiguous or duplicate or missing - Test Plan/ Test Cases & Test Scripts, Incorrect/Incomplete test setup
• Typographical Error: Spelling / Grammar mistake in documents/source code
• Variable Declaration Error: Improper declaration / usage of variables, Type mismatch error in source code

Google squared

-->

The search engine is a bit different animal. According to Google, "Google Squared is an experimental search tool that collects facts from the web and presents them in an organized collection, similar to a spreadsheet. If you search for [roller coasters], Google Squared builds a square with rows for each of several specific roller coasters and columns for corresponding facts, such as image, height and maximum speed."

This one is easier to see than explain. Here are the results from search supreme court justices.

Next generation data warehousing is here. Google Squared is an amazing technology with which you can build squares of data. I am very interested to see whether we can achieve a "data schema" with which we are able to build "people square" based on our product data. That would be taking people data warehousing to next level.