.: Dextra Technologies :.

	Home > Solutions and Services > Architecture Services

Engineering Services

IT Services

Test & Validation Practices

Supporting Complete Life Cycle

Architecture Services

Architecture Services

Based on standard methodologies Dextra provides detailed analysis and design services as preliminary step to envision whole project implementation. In Dextra we are focus on mitigating risk at early stages, for that we’ll prepare specific models that allow us to isolate the scope in and prioritize it in several phases.

The architecture is defined during the very first phases of the development as the inception phase for the RUP methodology. During this phase, the first step towards defining the architecture is the definition of a vision document where all of the client’s requirements are gathered in one common place where our project leaders and architects can refer for its future work.

Once the vision document is created, we’ll define our architecture document and our technical proposal. Both of these documents will lead us to a complete software development plan that includes the milestones, risks, compromises, deliverable of the product or service, client acceptance criteria for the product or service delivered, etc.

Phase	Deliverables
Inception	Vision Document (preliminary version) Architecture Document (preliminary version) Technical Proposal
Elaboration	Vision Document (final) Architecture Document (final) Use Cases Software Development Plan Prototype (optional) Progress Reports Change Control Documents (if applicable)

In general an architecture document is composed of the following sections:

Architecture abstraction level	Description
Logical architecture	This section shows the most significant parts of the architecture. For example: the number of logical layers in which the product is divided even in a recursively way. Additionally it’ll show the flow of information and GUIs in the system. A common pattern used here is the MVC (Model-View-Controller).
Execution architecture	In this section we mainly sketch out how the executables, etc. will interact with each other in order to accomplish the product goal. This helps us to identify possible overloads and optimize the structure of interaction.
Physical architecture	This section will identify and organize the packages/modules to be deployed and developed for the product or service.

The following is a general diagram of the people who is involved during this process pointing out some of the outcomes or deliverables:

Analysis Architecture Service

"The record of each detail leads Dextra towards the efficient accomplishment of our objectives in a timely manner"