Doddy Christiana Saputra

The Logical Design phase During this process, we define the structure of various logical entities which will be forming the solution and the behavior of those to interact with each other. Process to create the logical design is as follows:

1 Identify Business Objects: The objects which either provide some kind of service or use some service or hold data which is useful for the business processes are the candidate business objects. Finalized business objects will be modeled as Classes.

2 Identify the services that will be offered by these business objects. These services later on will be modeled as Methods of the classes.

3Identify attributes of the business objects. Attributes will hold the data and will be modeled as Fields and Properties of the classes.

(more…)

The Component Diagram can show various classes, interfaces, pages, executables etc. packaged into deployable units called components. Components expose interfaces which are either the provider interface or the paired consumer interface. Component can have internal other multiple components which represent any deployable unit like web site, class library, page etc. and the container component can delegate the interface implementation to these internal components. In the following example the ITester interface of the Development component is consuming the ITester interface of the Testing component. Testing component has Tests and Unit Tests as further internal components. Tests component implements the ITester interface so the Testing component delegates tasks of ITester interface to Tests component. Similarly Unit Tests component implements IUnitTest interface so the Tests component further delegates the tasks of IUnitTest to Unit Tests component.

(more…)

It’s brand new stuff in vsts 2010 Sequence Diagram…This diagram models the behavior of the classes which are modeled in the class diagram. It graphically shows the method calls on various class instances from the other class instances. It may show synchronous as well as asynchronous method calls and their returns. Usually it is in the time ordered fashion.

(more…)

Guys .. it’s the need of architect one called Layer Diagram, In the process of Conceptual Design we baseline the Layer Diagram. Layers are the abstracted grouping of model elements which provide similar functionality and communicate with each other as well as elements of other layers. For example all elements which provide User Interface are grouped into Presentation Layer whereas elements which implement business logic, rules and constraints are grouped in the Business Logic Layer. They either are dependants or dependencies. Dependency relationship sometimes can be bidirectional. Team System for Architects provides packaged solutions to implement patterns related to layers. It provides solutions for Three Layers (Presentation, Business Logic, Data Access), Four Layers (Earlier three and Service) and M-V-C (Model, View, Controller) patterns. Layers can provide links to either projects in the solution or other model elements from UML Model Browser. Since all of those may not be ready, we can decide upon the pattern to use for our solution and baseline the Layer diagram. We can add links to elements as and when they become available. Example of layer diagram with three layer pattern is as shown below:

(more…)

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…)

Visual Studio Team System 2010, Microsoft’s collaborative development environment, will introduce features that both align agile methodologies with project management and help developers from a “fingers on the keyboard” perspective.

(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 Pale,

The Dependency Injection and factory design patterns are very common, and
provide great flexibility in software development and also asked by many developer
that i’ve ever meet Although, most programmers have come across these patterns,
they may not grasp the concepts completely until they
see these patterns in action in real projects.
(more…)

Hi Dudes,

The Factory design pattern is another heavily-used pattern in ASP.NET applications
to help introduce loose coupling and remove dependencies in the code. The Factory
method is a creational design pattern that is used to create objects without any prior
knowledge of the type of the object. We delegate the responsibilities of creating the
actual objects to subclasses or separate factory classes. This can be accomplished by
using interfaces or abstract classes.

(more…)

Folks,

Session object in Web Application is very important things for transferring variable or even doing some caching, as we known before in ASPNET there are a view mechanism to implement this caching object, one way approach is using the SQL server session wheter this way is eat the peformance of the retrieving the session object coz the system need to go round trips during the process, okay let’s forget it about using SQL Server session object in stead of we implement the session that we stored in Dictionary Collection which encapsulated in the class, the second things is using the cache object whether the system could save the system in web server memory by implement the cache and put it the span time to arrange the life cycle of the caching. Those action should be done coz the cache has a unlimited time life cycle in the web server memory, until  we destroy the cache by manually.

(more…)

Interviewers: Scott Swigart and Sean Campbell.

Interviewees:Blaine Wastell and Glenn Block.

In this interview with Blaine Wastell and Glenn Block of the Patterns and Practices Group at Microsoft we asked them about:

• About the Patterns and Practices Group
• What makes them different from a typical product development group
• The software development methodology they use
• Some of the things that Patterns and Practices group has produced for developers.
• The role of CodePlex for their group.

Blaine:   I’m Blaine Wastell. I’m a program manager in patterns & practices, and I’ve been in this role for a little over four years now. Most recently my focus has been in what we call the “client UX program”. It’s about providing guidance to customers on developing both smart client and web client applications.

For 12 years before Microsoft I was out in the consulting world helping business customers develop enterprise line of business applications, mainly Web applications.

(more…)