Doddy Christiana Saputra

With Activity Diagram ,If anyone has used flow charts, they know almost all details of activity chart. The following image shows all the elements which can be used to create activity diagram. Although both Use Case and Activity diagram can model the requirements, while Use Case provides the scope in the nutshell, activity diagram provides the flow of activities in a serial and specific order. It shows the business processes which are executing.

(more…)

Till VSTS 2008 there was no support for various architectural diagrams which form the UML. Team Edition for Software Architects supported some non-UML but very practical diagrams. Those diagrams provided us ability to do High Level Design of solution architecture and infrastructure architecture. Except in case of WebService the Application Diagram did not support the Low Level Design and on the infrastructure side, except for deployment diagram no other design elements were supported. Team System 2010 for Architects has quite a number of enhanced capabilities compared to Team Edition of Software Architects 2008. Distributed Diagrams model which was present in the Team Edition for Software Architects 2008 is no longer available with Team System 2010 for Architects.
First two phases of traditional Microsoft Solution Framework (MSF) are Envisioning and Planning. Although some of the architectural diagrams are started to be created in envisioning, the completion of those happen during the planning phase. Planning phase is further divided in three processes which run to an extent parallel but are started with a little bit of phase difference. Those processes are:

· Conceptual Design
· Logical Design
· Physical Design

In this article we will look at the details of various diagrams which are required during each of the design process and check if it is supported by Team System 2010 for Architects. Architectural diagrams can be created using Team System 2010 for Architect in which there is a project template for ‘Modeling Project’ which allows us to create various diagrams. We will take an overview of those in the article.
Conceptual Design: This is a process in which from a hazy cloud of needs, crystallization of requirements happens. Requirements are gathered, analyzed and prioritized. Requirements are modeled using ‘Requirement Document’ and ‘Use Case’ diagrams. We also document the processes that are followed by the business. These processes are workflows within the business system. We can use ‘Activity Diagram’ to model those processes and workflows. During the conceptual design the architect will also list all the user roles that will be interacting with the system and the general architecture of the system. General architecture definition will contain the list of logical layers and physical tiers which will be present in the future state of the system. To model it, we can use the ‘Layer diagram’ which is available in the Team System 2010 for Architects.

(more…)

Microsoft’s upcoming Visual Studio Team System 2010 release is anchored in efficiency and code quality, incorporating new ALM, architecture and testing tools. As the release draws nearer, the company is continuing to flesh out those features, and developers are learning how to adapt their workflows to its new capabilities.

(more…)

Hi Developers,

Version control is the core of agile collaboration development for these days, why ? because when we talked about collaboration development project, our first head is we involve so many developers and it’s element with in, and we need the mechanism to manage that, not possible closed to development in ERP Microsoft Dynamics Axapta 2009 the daily development happen and often is develop the AOT ( Application Object Tree ) structure and architecture ,because this is the layer of what we called the ERP Customization in Axapta, so let’s take a look this picture below :

(more…)

The Essential Of Agile Extreme Programming 

As We known before  that from Fowler,Gamma,Cunningham had defined the definition of Exteme programming which has the meaning is “..a lightweight methodology for small to medium-size teams developing software in the face of vague or rapidly changing requirements…” and furthermore XP has a view characteristics which are :

• A team of 5-10 programmers work at one location with costumer representation on site.
• Development occurs in frequent builds or iterations, each of which is releasable and delivers incremental functionality.
• Requirements are specified as stories, each a chunk of new functionality the user requires.
•  Programmers work in pairs, follow strict coding standards, and do their own unit testing.
• Requirements, architecture, and design emerge over the course of the project.

             So , let’s take a look the model of extreme programming process :

From that point view above we could follow the process of XP like this point :

1. From the left side of the graphic model ,we can see two things that drive release planning and development .
2. User stories represent functionality that is to be implemented in the course of the release.
3. Architectural spikes are any work that the team needs to execute in order to lay in some architectural foundation, to explore a potential refactoring, or to look at new technology that may need to be included in the release. These inputs drive the release planning session.
4. The outcome of the release session is an iteration plan defining a set of iterations intended to accomplish the release.
5. To the right , and integral to the iteration, are the ever-present acceptance tests, which are typically written by the customer  and serve to the test the functionality implemented against the user stories.
6. Finally, the result of all the process is a series of small releases that rapidly evolve to address the customer problem.

Okay , from the simple thought of Extreme programming above we have already get a paradigm of XP collaboration team development .

cheers,

Doddy Ch Saputra,MCPD,MCITP,MCTS