Recently, Microsoft Pattern and Practices released a good book about testing for continuous delivery with Visual Studio 2012. This book covers an Agile process in terms of testing and continuous improvement of your software by testing it iteratively. As mentioned in their pages
This book is aimed at test engineers, managers, developers, and folks interested in understanding the changing world of test. Over the last several years, software testing has changed a great deal. In the past, test plans were on paper, filed away and out of sight. Today they are—or can be with Visual Studio—living documents, as manual and automated tests are integrating into the test workflow supported by the test infrastructure. Today you no longer have to set up physical boxes; instead you can set up and automate virtual environments composed of virtual machines to meet your testing environment needs. With Visual Studio and Team Foundation Server, the pain of dealing with a heterogeneous test infrastructure is reduced, the cost and effectiveness of testing a product is improved, and regression testing becomes cost effective instead of a nightmare. Knowing how to test is important, but understanding how this new infrastructure is changing the business of testing and software delivery is critical. Today's businesses require nimble teams that can support continuous delivery and deal with updates and bugs in an agile fashion. It's what your customers have come to expect. In this guide, we follow a team as they move from a conventional approach to testing towards one more suited to the needs of present-day development. We see how they address the costs and the pain of their old methods by adopting the testing infrastructure of Visual Studio 2012.
You can download the book here
Having a good time to learn you can bough a good book about testing and Agile here. Buy one and you never regret it.
This article will cover a tips to adopt ALM paradigm in building Line of Business Application Through Lightswitch technology. You can download the article here.
Enjoy!. Furthermore you can learn a Lightswitch if you want to create line of business application with a rapid way. Here are several books that you can buy
Well many of you already have Windows 8, and many of you already have an application. If you want to monetize it, you can use Microsoft Ads SDK. This Indonesian article will cover how you put an ads for your Windows 8 Apps through Visual Studio 2012.
You can download the article Here
Or read online at Microsoft KB
Problem
In Visual Studio 2010, the rocket-SVN client work best. However, it’s not supported in Visual Studio 2012 and there are no plan from the developer that the Rocket SVN will be updated to support Visual Studio 2012.
Solution
The solution is to switch the SVN solution to Tortoise SVN. After you installing the tortoise you should do some upgrade or create new working copy. This video tell you how to
Adding a new local copy from your SVN server
Upgrading your current local SVN server to work with new Tortoise
Enjoy this video
This Indonesia screencast introduce you a usage point of view of a various version in visual studio 2012. After the screencast you might know the different version of visual studio and the target for each version. Enjoy
Building a software is challenging whether you build for product or for project both of them need bullet proof design to make your design “just work”. Just work concept is how we build design as efficient as possible without sacrificing the design itself. Inspired from the MSDN article that describe the approaches to design Windows Phone 7 Design. The post is created to generalize the a practice approach to design the software. But first time first you can read my previous post about Agile design. Frankly speaking, according to several situation there are three design model that should be proposed in Agile ALM. The management design, how the project is executed The technical design, how the codes is composed. The business design, how the project will be survived and used by the user The technical design is composed at least three main aspects which are data design, codes design, and UX design. In a sequential we can said that UX design is followed with data design, and codes design for the rest. You can read the document here
Deployment is an important step in an ALM. Building smooth and good experience in installation will make the user happy and the application lifecycle management will be better. In .NET development application, the software distribution can be done two ways which are click once deployment and MSI installer. For the MSI Installer you might need to set dependency such as .NET Framework, Crystal Report, and others.
Unfortunately, not the entire redistributable is ready to download in Microsoft side. You can download The SQL Compact 4 and Sync Framework here.
This is the third tutorial that focused to implement UML as a lite modeling based on Agile process. The main purposes of component diagram is to propse a solution based on the functional and the business process. Furthermore, the component diagram will help developer team to see a big picture before they build a prototype. In this Indonesian video you will learn.
What is component diagram and why we need to build it
Component dagram as the software component architecture
Building component diagram in Visual Studio
After viewing this video, you can create a component diagram and knows how to improve your design vision into higher level such as prototyping,
enjoy
This post is a sequel of the previous post “Agile modeling 101-Building Use Case Diagram”. This post assumes that you already gather the requirement and the actor of the proposed solution. This post will guide you how to explore business process that needed to develop to capture essential part of system business process. The video will tell you the rest, some of the key point for this video are:
Activity diagram captures step by step what user or system will do for a functionality described in use case.
Ideally one use case will have one or more business process that described in activity diagram
the activity diagram can be formatted to become usage scenario that lead as an ingredient for building user manual
That’s it, enjoy the video
This Indonesian video will guide you the first step to capture system and actor requirement. This tutorial uses Visual Studio Modeling project as a part of ALM features in Visual Studio started from 2010 version. Here are some conclusions from this video
Actor and Action are the main part of use case diagram
Keep the diagram simple, eliminating the technical aspect such as extend or include, except you use this use case for technical communication between technical team only
Kite level best for business use case, while sea level use case good for deep dive with the system requirement
It will be great to split up use case diagram for one actor (the video join the entire users for simplicity purpose only)
Use case will be explained further in Activity Diagram
Enjoy this video,