Goal Management – Goal partitioning for Elaboration phase

This is the second part in continuation to my earlier post Goal Management – Goal partitioning for Inception phase While the team identifies requirements in the inception phase and also find out the business risk of the project during the same, the elaboration phase is the time when the technical risks are supposed to be unearthed and mitigated. So definitely the goal in this phase is to elaborate the system technically. This includes:     *  To elaborate the system's technical requirements     *  To establish the architecture (establish different views of the system).     *  To establish the QOS and

Continue reading

Goal Management – Goal partitioning for Inception phase

Goal Management in iterative development process is a multi step process. Starting from partitioning the goals into phases and then from phases to iterations is a critical process. Goal partitioning into phases: The phases are Inception, Elaboration, Construction and Transition. Now how to partition the goals of the project into these phases? Let discuss it from phase to phase: 1. Goal partitioning for Inception phase Inception is a phase in which the team basically identifies the requirement for the system. This is the phase in which the feasibility of the project comes up. It gives insight to the complexity of

Continue reading

Enabling mobility for enterprise application

Almost all enterprises have a physical boundary and some tangible shape for its service boundary. The enterprise do all the talkings with the market/consumers/customers staying within its peripheri. Only few enterprises like mobile or wireless phone has been able to assume the shape of an amoeba – known well for being able to take almost any shape. All this is possible because of the capability of this wireless technology. So the mobile or wireless technology is now has started giving food for thought to the enterprise technology pundits to evolve different techniques to give dynamism (or so called amoebeic boundary)

Continue reading

A-Z Guide to Being an Architect

Eh! There is something interesting to read and learn. We here also are in the way of architecting in a big way already. I am reproducing this post from MSDN.   A-Z Guide to Being an Architect A Is for Advocate “I think you’ll find that you really don’t want to do it like that.” Architects have to explain and advise on technical issues to business stakeholders. They also have to be able to advise delivery teams on how to build. This advice is the currency of an architect; invested wisely, it will return goodwill and trust. The architect is

Continue reading

State Management Best Practices

  The following table highlights the main state management issues:   State Management Issues Implications Stateful components Holds server resources and can cause server affinity, which reduces scalability options. Use of an in-memory state store Limits scalability due to server affinity. Storing state in the database or server when the client is a better choice Increased server resource utilization; limited server scalability. Storing state on the server when a database is a better choice In-process and local state stored on the Web server limits the ability of the Web application to run in a Web farm. Large amounts of state

Continue reading

Architectural patterns

Architectural patterns are meant for providing solutions to architectural problems in software engineering. It fundamentally provides a readymade structure of a solution that is targeted at a particular established proble. It describes a structural organization schema for a solution consisting of subsystems and underlines their responsibilities and interrelations. However there is significant difference between the architectural pattern and the architecture itself. An architectural pattern is a concept that captures essential elements of a software architecture. The pattern is a guideline to implement a particular architecture. So following a particular architectural pattern, the architects may come out with several different and

Continue reading

MVC : Model View Controller

Model View Controller is an Architectural pattern. View: The user interface (GUI) or the software which produces User Interface (ASP.Net Web forms ) which enables display of  information about the model to the user. Any object that needs information about the model needs to be a registered view with the model. Example – Boundary Class   Controller: The user interface presented to the user to manipulate the application. User Driven Events in GUI. Example – Control Class   Model: The core of the application. This maintains the state and data that the application represents. When significant changes occur in the

Continue reading

The Architecture Journal Reader

Wow! See what I got!! The Architecture Journal Reader from Microsoft. Thanks a Zillion to MS team. First, the Architecture Journal has been one of the best things MS is doing. I am a regular CONSUMER of the journal. It carries so much of good things that it keeps you on the toe always. Now coupled with the journal reader, it is going to touch the zenith of perfection. It presents the content of the journal in a very very comprehensive and readable format. MS is always pioneering the art of UX (User eXperience). I will request all of you

Continue reading

Software Architecture!

It was at the end of two hectic days of organisation level review of our software development process (in line with CMMi). I had a good sleep through the night only to start the day with my most hated activity, catch the morning flight! I was carrying the book "Analyzing Requirements And Defining Microsoft .net Solution Architectures – Microsoft Press (ISBN:978-81-203-2322-3)" to kill the boredom of the cramped journey in the airplane. I tried to consume every word of the book to make the maximum use of the flying time. The breakfast was being served. I closed the book, kept

Continue reading