Develop training material for a class about debugging crashes (blue and red screen) and hangs in Windows Vista. Target audience are engineers with only C programming knowledge and nothing else. To reemphasize, the audience do not know Windows programming, device driver programming, or internal kernel architecture.
The class material consist of two major components, lecture and labs. Duration of the class is 8 hours, with 2 hours for lecture and 6 hours for labs.
**_The lecture part covers these areas:
**Vista internal architecture**. Example of some of the key areas are: kernel, HAL, memory management, scheduling, executive functions, hardware error reporting, boot-up sequence, shut down sequence, etc.
**Debugging tools**: tools overview, tools set-up, debugging techniques for analyzing blue and red crashes, Debugging techniques for hang, kernel mode debugging, user mode debugging, remote debugging, data structures and functions of interest for debugging
Obviously there is not enough time to go over any concept in detail. The idea is to present ONLY the major points of each section. Using Power Point, each topic (such as scheduling) should take no more than 1-2 power point slides, with each slide has a maximum of 7 bullets. Each bullet is one short sentence or phrase. In a corresponding Word document, each bullet of each slide is explained further by a couple of paragraphs. A link or pointer to reference sources (documentation, books, web sites, etc) must be provided for each bullet so that the audience can explore the detail further.
Continue in "Deliverables section"
Develop 10 labs, each about half an hour long to do. The object of each lab is to create a problem and demonstrate the usage of a tool (example WinDbg) to solve it. Each of the lab simulates/causes a problem (kernel crash, user crash, hang in user mode, hang in kernel mode, etc). Each of the labs must have detail step-by-step instructions to run and resolve the problem. Keep in mind that each of the lab should take half an hour to do, so the problem should be simple to debug.
Bidders must prove/demonstrate that you have the knowledge to do this.
1) Development schedule:
- The class outline is due 2 days after the project got started
- The lecture portion is due 1 week after the outline is accepted by us
- The labs are due 2 week after the outline is accepted
- Final version of all work are due 3 weeks after the outline is accepted
- Total project time is 3-4 weeks.
2) Deliverables include the following items:
- A Microsoft Power Point document containing presentation slides
- A Word document supporting the PPT slides
- A Word document containing labs procedures
- All software needed to do the labs except for any Microsoft tools. All source code must be delivered, including any installation code, as well as any build scripts. The code and any scripts must be well documented.
3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement).
Windows XP and Vista.
Microsoft Power Point and Word are to be used for documenation. C language and Microsoft Visual Development environment are to be used for code development.