1. Develop user stories. These create time estimates for the release planning meeting and are used instead of a large requirements document. They are written by the customers as things that the system needs to do for them.
2. Hold a release planning meeting. A release plan, which lays out the overall project, is created at this meeting. The release plan is then used to create iteration plans for each software version.
3. Create the release plan. This specifies exactly which user stories are going to be implemented for each system release and specifies dates for those releases.
4. Release small pieces of the system to the customers often. This is critical to getting valuable feedback in time to have an impact on the sys…
Summary: Using new Microsoft Office Outlook 2003 add-in support in Microsoft Visual Studio 2005 Tools for the Microsoft Office System, create Microsoft Office Word 2003 task reports using WordProcessingML and XML expansion packs, and create a context menu for tasks in Outlook. (24 printed pages)
Note This article is pre-release documentation and is subject to change in future releases. Visual Studio 2005 Tools for Office Beta 2 is included with Microsoft Visual Studio 2005 Beta 2.The beta release of Outlook add-in support for Visual Studio 2005 Tools for Office Beta 2 is available separately, by downloading Microsoft Visual Studio 2005 Tools for the Microsoft Office System – Outlook (Beta).
TargetProcess:Suite 1.3.5 is a web-based integrated agile project management and bug tracking software. It is designed to solve distributed teams problems and support agile development processes like Extreme Programming. Integrated Bug Tracking makes project management more effective, improves overall project traceability and provides consistent snapshot of project state. In general, TargetProcess will help you keep project on track in an agile way.
It seems probable that eventually most software capabilities will be delivered and consumed as services. Of course they may be implemented as tightly coupled systems, but the point of usage—to the portal, to the device, to another endpoint, and so on, will use a service-based interface. We have seen the comment that architects and designers need to be cautious to avoid everything becoming a service. We think this is incorrect and muddled thinking. It might be valid right now given the maturity of Web Service protocols and technology to question whether everything is implemented using Web services, but that doesn't detract from the need to design everything from a service perspective. The service is the major construct for publishing and should be used at the point of each significant interface. service-oriented architecture allows us to manage the usage (delivery, acquisition, consumption, and so on) in terms of, and in sets of, related services. This will have big im…
Description: A powerful, cheap and easy to use POP3 .NET component, which allows you to download/parse emails from POP3 server, save attachments, retrieve custom headers etc. Great help with examples (C#), free updates and support.
// get all types of the dynamic assembly
Type types = ws.ProxyAssembly.GetTypes();
// get a certain type by name - watch out for fully qualified name
Type t = ws.ProxyAssembly.GetType(ns + 'Order');
Then create an instance of the type by using reflection.
object result = Activator.CreateInstance(t);
result = ws.InvokeCall();
While developing clients for web services, we typically add a web reference to the web service by specifying URL of the .asmx file. Adding a web service in VS.NET generates required proxy object. However, it may happen that after adding the web reference the web service is moved to some other location. In such cases the most easy way is to recreate the proxy object. But what if the same thing happens after you deploy your web service client. It would be nice to allow configurable URL so that even if original web service is moved your clients need not be recompiled. In this article we will see how to do just that.
Orthogonal Arrays: "Orthogonal arrays are beautiful and useful. They are essential in statistics and they are used in computer science and cryptography. In statistics they are primarily used in designing experiments, which simply means that they are immensely important in all areas of human investigation: for example in medicine, agriculture and manufacturing.
Your automobile lasts longer today because of orthogonal arrays ['The new mantra: MVT', Forbes, Mar. 11, 1996, pp. 114-118.]
The mathematical theory is extremely beautiful: orthogonal arrays are related to combinatorics, finite fields, geometry and error-correcting codes. The definition of an orthogonal array is simple and natural, and we know many elegant constructions - yet there are at least as many unsolved problems.
Here is an example of an orthogonal array of strength 2:
Each of us who migrate to VS.NET encounters a few bumps in the road. One bump that caught me off guard was that my macros no longer worked.
My existing build number incrementing macro was a combination of bits and pieces of code scavenged from countless authors over the years. Although my build numbering system is not complicated, and does not require features found in similar macros, it will provide a solid foundation to start from.
These are my requirements for automating build numbers:
On each release build, automatically increment a build number contained in a separate file that will be included into my project.
Automatically track build date and number in a log file.
The Microsoft.VisualStudio.TestTools.WebTesting namespace supplies classes that enable Web testing. This namespace includes the WebTest class which is the base class for all Web tests. The WebTestRequest and WebTestResponse classes simulate the HTTP requests and responses of the Web pages under test. These classes use the FormPostHttpBody class to simulate the use of form post parameters. Microsoft.VisualStudio.TestTools.WebTesting also includes classes for data binding, test rules, representing Web pages, query strings, HTTP context, and plug-ins that provide a test extensibility function.
Here you will find information on the various ways to customize, extend, and integrate with the Visual Studio environment, including macros, add-ins and the Visual Studio Industry Partner (VSIP) Program SDK. Whether you are building large scale commercial tools or just personalizing your Visual Studio experience, the Visual Studio Extensibility Center is Microsoft’s primary source for information and guidance.
Bugzilla.NET is my Visual Studio.NET <-> Bugzilla integration project. So far it has the ability to query Bugzilla from within Visual Studio and synchronize a set of tasks with a given set of server-side queries.
Windows XP PowerPacker 1.0 RC6.1 beta
PowerPacker will help a user create a Multiboot Windows XP disk with or without DriverPacks. It will do almost everything for you, even hex edit the files needed to be hexed, create the boot directory, boot menu, etc. It makes creating multiboot XP disks a breeze.
* New File Menu that you can find at the top left of the main window
* Got rid of the ugly picture that was on the right side that made you have to tilt your head and squint your eyes to read it
* Added an UnDocumented option that you can add to your ini file
Privoxy is a web proxy with advanced filtering capabilities for protecting privacy, modifying web page content, managing cookies, controlling access, and removing ads, banners, pop-ups and other obnoxious Internet junk. Privoxy has a very flexible configuration and can be customized to suit individual needs and tastes. Privoxy has application for both stand-alone systems and multi-user networks.
* Proxy Classes and Web References
o Creating a Web Reference
o Renaming the Web Reference
o Viewing the Web Reference Files and Properties
o Using a Proxy Class
* XML Web Service Clients
o Creating the Windows Forms Client
o Creating the Web Forms Client
o Creating the Console Client
o Chapter 4 Quick Reference
TTN On-Line Edition for September 2002: "Load Testing Terminology by Scott Stirling (firstname.lastname@example.org) Introduction What is the difference between load, stress and performance testing? Why do these three types of testing seem to belong together, perhaps with others such as scalability testing and benchmarking? Questions such as these, which I have encountered in my own career as sometimes load tester, on Web forums and in discussions in the workplace, are what this article purposes to answer. It would be nice to point to some seminal piece of QA literature that settles these questions definitively, but surprisingly, this is not possible. The use of these terms in the QA literature varies to the point that sometimes load testing is defined as a type of performance test, or performance test is a type of load test, or (somewhat common, actually) load testing is not worth mentioning explicitly. To what degree definitions proposed in the literature have been arrived at ind…
Running an application on more than one machine introduces potential challenges into the design and layout of the application. If you're Web app is not 100% stateless you will run into potential problems with resources required on specific machines. You'll want to think about this as you design your Web applications rather than retrofitting at the last minute.
For example, if you're using a Visual FoxPro backend and you're accessing local FoxPro data in any way, that data must be shared on a central network drive in order for all of the cluster servers to be able to access those files. This includes 'system' files of the applications itself – in Web Connection this would mean things like the log file and the session management table, which would have to be shared on a network drive somewhere. It can also involve things like registry and INI file settings that may be used for configuration of servers. When you build these…
Summary: "The subject of software estimating is definitely a black art," says Lew Ireland, former president of the Project Management Institute. As you know, estimating is more of an art than a science, and inherently more prone to the negative aspects of human biases. So bare with me, if am awry in my estimation exercise. These are the lessons learnt out of my experiences which describes in detail the following key areas for effort calculation:
Candidates for test automation.
Factors that affects test automation estimation.
Grouping steps to determine complexity.
Framework design and estimation.
Scripting effort estimation.