Enterprise inlines the solution within business. It means any action that create a solution should provide values. Values mean productivity, revenue gain, or cost effeciency. Simply said that values related directly with the business. Last month, we should create a software engineering framework based on tight project management and approval model, as fine as minimalist approach. The proposed solution is called ALM minimalist. So how we create an ALM minimalist, here are the steps: We select the starting template. In this step we are using MSF for Agile. MSF for Agile is choosen because the mature is in the middle between Scrum and CMMI We breakdown and make an effor to understand their project management habits. It is including their approval models and validation model We compose the artifact that minimalist enough As a result we get the templates as a follow: Vision and Scope document Functional Specification Document Master Plan Document Project Execution Reporting document Project Delivery Acceptance form Project Closure document That’s it, hope it will help you to compose a minimalist document for ALM purpose
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 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
Building codes is a complex activity. Therefore, we need to build a software in a rapid way without sacrificing a basic documentation for the software. In this article, it will share an approach to build a software through UML modeling but eliminating several verbose step.
This article point several activities that, we must do to build a software in a top-down model through UML modeling. These three steps which are
Gathering the requirement using Use Case
Understanding the business process using Activity Diagram
Building the software architecture using component diagram
You can read the article in Indonesian language at here
or you read it online at Microsoft KB here
Simple thing should be simple, complex thing should be possible. Many of the system start from small and increasing its complexity and become big and bigger. This Indonesia article will tell you two facts which are:
Visual Studio is your foundation to build any kind of system either small or big system.
Team Pulse and TFS will support you when you need a set integration many of Visual Studio
You can download the article here
Having problem to manage your source code? or feeling inconfidence because you don’t have enough source code management. This Indonesian articlwe will share several usual tips for you and your developer team to manage your source codes bettr. You can download here
or you can read here
@ridife
Noewaday, information system is not about how cool the technology, how cool the solution,or how cool the featutes. It’s about how the IS can sustain the changes. Everyday people works, innovates, and creates a new way of works. The want there is also adaptives. But IS is created from a bunch of related codes. Yesterday they said enough, but today they say nothing. Beside the others software type, IS is the most demanding software and the most adapotive in a changes. so how we fight the changes..? ALM is one of the answer…
In 07/01/2011, I will be invited to speak about IS in ALM Persectives. You can reach me at AMIKOM Building university from 09.00 AM till 12.00 PM. Special Thanks to Mr. Khusnawi and Mrs. Armadyah..
You can download the material below.
or you can read the article online here http://support.microsoft.com/kb/2661914/id-id
Want to explore more? I recommend you to read these books
Ciao
@ridife