好了，完成安装之后，我们就可以来做Windows Embedded Standard的第一个操作系统镜像了。在开始菜单中找到“Microsoft Windows Embedded Studio”，启动其中的Target Designer。然后再Target Designer的File菜单中选择New，创建一个新的Configuration。

输入名称后，点击OK，进入Target Designer的主界面。为了简单起见，我们选择Virtual PC作为我们的目标设备，这样就可以省去获取硬件设备信息的步骤。

首先，我们要在左侧的组件列表中找到我们要添加的组件。第一个自然是Silverlight组件了。Windows Embedded Standard中包括的是Silverlight 1.0，目前Silverlight 2.0还是beta阶段，也许等WES正式推出时就是Silverlight 2.0了，即使不是，也肯定会有QFE的。

由于不确定Silverlight被放到哪里了，所以只好Search了一把。结果是，在Software-System-System Services-Application Support中包括了Silverlight组件。除了Silverlight之外，我们还需要添加几个组件：

首先，是Design Templates下的Information Application；然后是，Software节点下的Test & Development下的Runtime Quick Start Helper Macro和Virtual PC 2007 Helper Macro两个组件。

添加了这些组件之后，我们就可以进行依赖检查了，按F5，或者在Configuration菜单下的Check Dependencies项，就可以执行了。如下图：

依赖检查之后，如果没有错误，我们可以直接进行编译，选择Configuration下的Build Target Image或者按F7，构建过程如下图：

在编译完成之后，我们就可以在C：\Windows Embedded Images下找到已经编译好的文件。我们将其拷贝到准备好的虚拟硬盘中就可以了。如何构建VPC的开发环境，请参考我的Webcast 《XP Embedded开发初体验》中的介绍。

在第一次启动时，系统会启动FBA(First boot agent)来完成一些设置，我们需要耐心等待一些时间：

接下来，我们关闭WES开发环境的VPC，记得一定要选择Shut down。

然后运行XPETraget的VPC，我们编译出来的Windows Embedded Standard Image其实和XP Professional非常类似，只是少了比较多的组件。不过我们仍然能够通过开始菜单来打开IE浏览器，然后再里边输入URL: http://www.silverlight.net/ 。对Silverlight比较熟悉的朋友一定会知道这个网站。而访问这个网站时，并没有提示我们需要安装Silverlight，这表明Silverlight已经被加到了Windows Embedded Standard的Image之中了。

Scrum is an iterative incremental process of Software development commonly used with Agile Software Development. Especially, Scrum will help us to manage the project more efficiently because it is an adaptive process. However, applying the Scrum Methodology should depend on the different situation during the process of project development. It’s a big issue to solve. This article gives an example to elaborate how to manage the project with Scrum.

Introduction

Software development is a complex endeavor. So the most difficult problem is how to handle the complexity through by the science of project management. Many scientists and software engineers raised a great number of methodologies for project management such as Waterfall, UP and Agile. In contrast to the heavy methodologies including Waterfall and UP, Agile is enough flexible to embrace the change, more light to be mastered by project team members, and more focuses on the communication and release of the usable software rapidly. Agile methodologies include eXtreme Programming, Scrum, Feature Driven Development and Crystal etc.

Scrum was raised by Hirotaka Takeuchi and Ikujiro Nonaka in 1986. The skeleton is shown in Figure 1.

The lower circle represents an iteration of development activities that occur one after another. In Scrum, it was called Sprint. Each Sprint is an iteration of 30 consecutive calendar days. The output of each sprint is an increment of product. The upper circle represents the daily inspection that occurs during the sprint, in which the individual team members meet to inspect each others’ activities and make appropriate adaptations.

There are three roles in Scrum including ScrumMaster, Product Owner and Team. The ScrumMaster is responsible for the Scrum process, for teaching Scrum to everyone involved in the project, for implementing Scrum and ensuring that everyone follows Scrum rules and practices. The Product Owner is responsible for representing the interest of stakeholders and creating the project’s initial overall requirement which was called the Product Backlog, for using the Product Backlog to ensure that the most valuable functionality is produces first and built upon. The team is responsible for developing functionality. Teams are self-managing, self-organizing, and cross-functional, and they are responsible for figuring out how to return Product Backlog into an increment of functionality within an iteration and managing their own work to do so.

Problem Statement

Without doubt, Scrum is one of most popular agile methodologies now. It, however, is not easy to apply it to project management. Considering about the following situations please:
1. If the culture of your organization is contradictious with Scrum, and your leader always interrupts you during the process of project development, what should you do?
2. If your team members are not familiar with Scrum, and they don’t understand the heart and rules of Scrum, what should you do?
3. Furthermore if your team members didn’t master the basic skills of Agile developing such as pair programming, Test Driven Development etc, what should you do?
4. If your customers always change their requirement, they are not clear what they want even, what should you do?

Our Solution

In fact, we can’t find out the “Silver Bullet” to solve these problems. We know Scrum is an adaptive process. Scrum makes many rules which should be followed, but not hidebound. It’s agile and flexible. It allows us to adjust the way to achieve the goal of project.

The answer to the first question is operating within the culture of the organization. Don’t fight against the culture of your company. If you are ScrumMaster, you’d better walk a fine line between the organization’s need to make changes as quickly as possible and its limited tolerance for change. You can adopt Scrum by starting small. At the same time, you should try your best to persuade your leader to support you. Sometimes your leader will build the bridge between the agile world and non-agile for you. Of course, it needs change, but these changes must be culturally acceptable. If not, you must acquiesce. The ScrumMaster is a sheepdog of the team, and his job is to protect the team from impediments during the Sprint. Remember that the precondition of which everything is going on well is that the sheepdog cannot be dead. After all, Scrum is the art of the possible.

Right, we hope our team members are all software craftsman so that everything is Ok. Unfortunately, the real world is not as good as that we expect. In fact, the situation in which most of team members are all apprentices is more common. It is true that it is difficult to hire the experienced software engineer in this industry. So the problem we must solve is how to train them. We should draw up a training plan. Before it, we must understand the skill set of everybody. We need to assign the mentors to the fresh guys. Of course, the best way of training is practice. We should assign the task to them according to their ability. At the same time, we have to add the task duration because they are not familiar with the related skills. Besides, Pair programming is a good way to handle it.

The great character of Scrum is enough flexible to embrace the change. Scrum is an iterative and incremental process. The iteration is very short (30 days) so that we can change our plan in time. The incremental development will provide the good policy to submit the release rapidly. The increment product can give our customers confidence. And the customers can understand the difference between what they want and what we provide though by the running software. Scrum emphasis on the communication between the team and customers. Product Owner of Scrum is responsible for communicating with the customers and creating the product backlog. In case the customers changed their requirements, the Product Owner will discuss with ScrumMaster and Team. If the change is acceptable, it is added into the product backlog. If the change is within the sprint which the team is developing, the sprint has to halt, and re-open the new sprint. Beside, the daily scrum will help each team member understand the current statue of the project, and the sprint review meeting will show the result of the sprint to the customers in order to get the feedback from the customers, the sprint retrospection meeting will prompt the Scrum process framework and practices.

Evidence that the Solution Works

Now we complete the first sprint of the project on time. In a month, we went through the whole lifecycle of the software development from the requirement analysis to designing, coding and testing. Each member is familiar with the Scrum gradually. Everything is going on well such as Daily Scrum, Team Work and Sprint Development. In the end of this sprint, we submit the increment product to our customers and get the feedback from the customers. The most important achievement is that our customers approve our approach to develop the product.

Competitive Approaches

We don’t follow the rule of Agile Methodology strictly. For instance, most of team members are accustomed to the TDD (Test Driven Development), so we adopt the traditional way to design and develop the software such as Use Case Driven Development instead of TDD. But we require everybody must write the test case for classes and components. We organize the pair programming group to prompt each other.

Because our customers are off-site, so we require our Product Owner must be in-site and cooperate with them in full time. We create the communication schedule for the customers to understand the customers’ requirement. The Product Owner is empowered to handle everything with requirement.

Especially, the ScrumMaster of our project protects the team from the rest of the non-agile world. We get the enough resources and backup. For example, we have our own agile coach to direct how to apply the Scrum to our project. He can help us to solve the key problem when we are confused of Scrum Methodology.

Current Status

The project is going on well. The first sprint is very successful. Team members are all confidence. They regard the Scrum as the effective and enjoyable process. The customers are satisfied with our process. Most of risks had already solved because we emphasis on them and add them as the tasks into the sprint backlog.

Next Steps

Next month, we are going to hold the Sprint retrospective meeting to find out the existed problems in the first sprint. Then we will create the backlog for next sprint. In this sprint, we will develop the most important domain module and let it workable.

Conclusions

Scrum is an excellent agile methodology to release the software product rapidly and correctly. It gives all team members the new management responsibilities. The process of the project management is visible and controllable. The ScrumMaster and Product Owner don’t need to write the redundant documents and draw up the unrealistic project plan. The team members become more active due to self-organizing and self-managing.

References
1. Agile Project Management with Scrum, Ken Schwaber
2. Software Craftsmanship, Pete McBreen
3. Applying UML And Patterns, Craig Larman

捷道·敏捷堂发布：http://www.agiledon.com/post/2008/07/Scrum-Practice-In-PM.aspx

好了，无论Windows Embedded Standard叫什么，我们只要记得，它就是一个组件化的XP Professional SP2就好了。为了适应嵌入式产品的定制化需求，微软将XP Professional拆成了两万多个组件，允许用户根据自己的需求进行二次开发，定制尺寸更小的操作系统。而且可以完成一些特殊的要求，比如换一个桌面程序，启动时执行自定义操作，还可以更换启动的XP界面等。还有一些EWF之类的高级功能。

但是被乱刀切块的XP Embedded也是XP，所以Windows Embedded Standard也只能运行在x86架构的CPU上，而不能支持其他的CPU，比如ARM。

当然Windows Embedded Standard比起之前版本的XP Embedded还是有很多进步的，最大的一个特点就是将Silverlight引入到了WES中，后边我们还会详细说到。

说到这里，相信大家会对Windows Embedded Standard有一个感性的理解。接下来，我们就要通过实践，让大家看到Windows Embedded Standard开发的流程。

安装Windows Embedded Standard

目前Windows Embedded Standard还没有正式发布，现在的CTP（社区预览版）相当于征求意见稿，可以免费从微软网站上下载的到。只需要在下列地址中，使用Live ID做一个简单的注册，下载项目中选择Windows Embedded Standard的ISO文件即可。下载地址：

https://connect.microsoft.com/windowsembedded

下载过程会安装微软的File Transfer Manager，文件有4G左右，下载过程会根据网速有所不同，请大家耐心等待。

下载完成后，我们可以刻盘或者使用Daemon虚拟ISO文件，然后自动运行。运行会为我们启动一个Windows Embedded Standard的安装向导。

首先在Prepare中需要首先安装SQL Server 2005 Express版本，可以从Web或者DVD安装。我选择从Web安装，30多M，不算太大。SQL Server Express主要是为了存储WES的组件数据库。

接下来直接进入WES的安装向导：

省略欢迎界面和License界面，反正所有软件都有这两个界面。下面是选择快速安装还是高级安装的界面。我选择了“Advanced”:

在高级安装模式中，果然有我们需要的东西。在“Windows Embedded Standard”-“Database”中选择“Chinese(PRC) Language Pack”和“Chinese(Taiwan) Language Pack”，简体中文和繁体中文不是默认安装，所以我们要选：

下面这一步非常重要：我在这里被困扰了两个小时……。安装过程需要输入SQL Server Express的名称。我在这里犯了错误（之前一直在用SQL Server），我们要填写计算机名+实例名称，而SQL Server Express安装时，我没有填写实例名称，然后就想当然的认为没有实例名称。不过经过试验，我知道SQL Server Express的数据库名是：计算机名+SQLEXPRESS。

然后点击旁边的Test按钮，如果数据库连接成功，则显示下图的对话框。需要说明的是，如果数据库连接不成功，也可以完成安装过程，不过在打开Target Designer时，会告诉你数据库初始化失败。（知道我为什么被困扰两个小时了吧？）

如果显示下面的界面则说明数据库连接没有问题，放心安装就好了。

后边的安装过程没有需要介绍的了，安装完成即可。

Microsoft Windows Sharepoint service技术从SPS2003发展到Moss2007，不只是名称有了巨大的变化，产品本身已经从SPS2003的注重与协作的知识门户，演变成了一个具有六大块功能的整个office产品线的服务器端，门户已经只是其中的一个模块。包含门户、协作、搜索、ECM、BI、工作流的Moss2007已经成为企业信息化应用的集成的平台，而其中的BI功能更是通过报表呈现，快捷反映企业经营状况提升管理效率的有效途径。

当然，严格说来，MOSS2007中的BI功能，仅仅是指BI的展现部分，比如使用Excel Service实现的简单的报表以及PivotTable实现的数据透视，这里的局限性取决于Excel本身的功能，就MOSS2007来说，它只是提供了一个BI展现的场所，如果要作真正的BI，还需要别的系统的集成，比如水晶报表等等，这不是本文讨论的范围，在这里我们仅仅讨论，如何通过Excel Service，来实现简单的（但其实是非常具有普遍意义的）BI的应用。具体来说，就是使用Excel 2007，通过外部数据源连接到数据库，读取数据库中的数据，并根据需要制作成相关的报表以及分析用的数据透视图表，发布到MOSS2007上，并通过Excel Service展现为Web页面。

实现MOSS2007中的BI功能，大致需要以下的三个步骤：
一、在管理中心中配置Excel Service

1. 前提条件：

   要使用Excel Service，需要MOSS2007的企业版，并且需要在网站集中激活企业版的功能，在网站操作> 网站设置 > 网站功能的页面，我们可以激活这个企业版的功能：

2.编辑 Excel Services 设置

在Excel Services的设置中，最基础的设置就是编辑 Excel Services 设置

本页面中有两个地方我们需要注意：在安全性的文件访问方式我们要选择模拟，这是Excel Calculation Services 从所有非 Windows SharePoint Services 受信任文件位置检索工作簿文件时使用的身份验证方式。还有就是在外部数据部分，我们需要设置一个无人参与服务的帐号和密码，这是连接到需要用户名和密码字符串进行身份验证的数据源时，Excel Calculation Services 使用的默认 Windows 帐户的凭据。如果不设置，则无法连接到数据源。

3.受信任文件位置

在SSP的Excel Service的设置中，还有一个关键的设置，就是受信任文件位置，这时Excel Service内部实现的一个安全性的机制，如果一个报表没有被存放到指定的受信任文件位置中列表设定的文档库的中，则这个Excel文件不能使用Excel Servcie的功能，使用Excel Access Webpart以浏览器的方式呈现。

操作方法：在网站集中创建要存放报表的文档库，病把这个文档库的地址添加到受信任文件位置，例如文档库：http://moss.bonainfo.com/Reports/ReportsLibrary

在受信任文件位置添加的页面，我们在位置中填入创建的文档库的地址，要注意选择受信任的子级，以信任这个文档库中文件夹及目录中的内容；在计算行为 的工作薄计算模式中选择文件。

要特别注意的是外部数据这个部分的设置：允许外部数据要选择允许处理来自以下位置的数据连接：受信任的数据连接库和嵌入连接；刷新时警告处不选择启用刷新警告，因为我们一般不喜欢在打开或刷新报表时弹出那个警告的页面；在 "打开时刷新"失败时停止打开处，我们启用停止打开，以便在以下情况下停止打开此位置的文件：文件包含"打开时刷新"数据连接，但打开文件时无法刷新，且用户对文件没有"打开"用户权限。在外部数据缓存生存期处我们可以设定系统可以使用外部数据查询结果的最长时间(秒)；在每个会话允许的最大并发查询数处，可以指定单个会话中可并发执行的外部数据查询的最大数目，这里都是用默认的设置。

在用户定义函数，我们启用允许的用户定义函数。

4、受信任数据连接库

在SSP的Excel Service的设置中，受信任数据连接库是另外的一个非常重要的设置。所有在报表中使用到的到数据库的连接，必须以文件的方式储存在这里指定的数据连接库中，才能被Excel Service正确使用。通常，我们需要首先在网站集中创建一个用于保存数据链接的文档库（数据连接库），然后把此文档库的地址填写到受信任数据连接库的列表中（当然允许不止一个这样的数据连接库）。

至此，我们完成了管理中心的SSP中，关于Excel Service的部分配置，之所以说部分，是因为受信任数据提供程序以及用户定义的函数我们并没有涉及。受信任数据提供程序实际上是能被MOSS2007使用的到数据库连接的驱动程序，如果有数据库没有在列出的列表中出现，你需要手工添加到数据库的驱动，至于用户定义的函数属于开发的范畴，我们不加讨论。

其实项目需求千奇百怪，剑招是不够用的，也不必生搬硬套，否则硬用也只能是伤到自身而不能破敌。

记得金庸小说里风清扬教令狐冲的时候，说过独孤九剑的总纲，无招胜有招，其实设计模式中也有这种总纲，那便是 •Identify the aspects of your application that vary and separate them from what stays the same.(找到系统中变化的部分，将变化的部分同其它稳定的部分隔开。)

有了总纲接下来的事变就好做了，分析一下总纲，找到系统中变化的部分。这句话的含义是什么？我们怎么才能找到

“系统中变化的部分”？我想这个是总纲中深层的含义，其实这是在提示我们从需求中分析，发现需求方可能会改动

的地方，而在此基础上做的事情，通常我会认为我们要与需求人员达成一致的目的，而基于这个目的是有不同的变化

的，而另一半话 将变化的部分同其它稳定的部分隔开，又有这样的疑问了，如何寻找稳定的部分呢？其实不说大家

应该也能猜到 稳定的部分一样也是从需求目的中寻找。

貌似这样显得有点虚，来点儿实际的项目例子好了

在一个项目中，我遇到的问题是有一个搜索框类似于google，输入后需要有联想提示，并且要有一个层与之关联显

示不同的数据。这么一项目，变化点在于，显示不同数据的层，和联想提示的显示是可能变化的，而稳定的点是联想

提示本身与显示数据的层是分开的，而且都需要关联文本框的变化。这么经过分析这些变化与不变的点后，发现很适

合观察者模式，提示数据类和显示数据层类都需要观察文本框有没有变化，而有变化时就触发变化事件，而引起两个

类去做触发后的事情。

变化与不变是我们需要分析的最重要的部分，这个便是设计模式中独孤九剑的总纲。当然熟悉金庸书的人也知道要有破剑式，破掌式等等，等有时间了我再把这个类别也写出来。

http://www.cnblogs.com/aawolf/archive/2008/06/23/1228203.html

下载Image

下载Image的过程与Digi开发板类似，在Image编译成功后，我们打开Platform Builder的Target菜单，选择Connectivity Options。

我们可以使用CE Device作为下载的Target Device，为了之后的部署方便，我们还是创建一个革新的Device，作为下载目标设备。在Target Device Connectivity Options对话框中，我们选择Add Device，在New target device name中填写“Gexin2410D”：

然后选择Kernel Service Map，Download和Transport都选择以太网：“Ethernet”。点击Download后的Settings按钮。

点击Settings按钮后，Ethernet Download Settings对话框会弹出。等待Eboot发送BOOTME的消息后，我们会在Active target devices中看到新的开发板名称出现。如果Eboot已经开始发送BOOTME的消息，而这边接收不到时，我们应该首先查看PC机和开发板的IP地址设置，看是否处于同一个网段内，子网掩码是否正确。

在设置完成后，我们点击OK返回Target Device Connectivity Options对话框。点击Apply，然后Close该对话框，大家记得一定要Apply，我第一次因为忘记了所以造成Download不成功。

返回到IDE环境后，选择Target菜单中的Attach Device项，启动下载Image的操作。

如果网络连接正常，我们会看到Download下载对话框的出现。下载的速度与Eboot和网卡驱动相关。因为我们编译的是Debug版本，Windows CE 6.0的Debug版大概在50M左右，所以下载需要4分钟左右的时间。

下载完成后，等待一段时间，如果正常运行，我们会看到LCD屏显示我们OS Design的界面:

我们能在OS Design的桌面上看到Windows Embedded CE 6.0 R2的版本号。这样的话，我们的Windows CE 6.0 R2平台在革新2410D的开发板上了。（完）

预告：稍后我们还将有如何在CE 6.0 R2上开发.NET CF 3.5程序的文章，不过前提条件是我把程序调通……如果想看的兄弟，就替我祈祷一下吧，我RP值一直不高……

上篇文章：

http://www.cnblogs.com/aawolf/archive/2008/06/05/1214281.html

编译成功后，我们就要将NK.bin文件下载到开发板上了。下载镜像文件需要boot-loader和EBoot的支持，与Digi开发板相同，革新开发板也将boot-loader和Eboot烧写到了NAND Flash中，我们只需要通过超级终端来完成boot-loader的设置和Eboot的启动即可。

首先，需要将我们的开发板和PC机通过串口线连接起来，确定你连接的是哪个串口。然后打开超级终端（Vista下是没有超级终端的，我们的解决方法是从XP底下拷一个过来），创建新的连接，选择COM口，然后设置波特率为：115200，剩下的按下图设置即可：

设置完成后，我们就可以打开开发板的电源，超级终端上应该有相应的输出，如下图：

如果我们不理它，开发板会启动NAND Flash<