After the overwhelming response for Groove Search V1.0 and after carefully analyzing our user feedbacks, we present you the much improved version of Groove search.
Groove search V1.1 is the new version search tool for Groove 2007 ans 3.1 users. It is designed to search forms/files/contacts/messages/discussions in Groove accounts. It gives you results which are directly linked to the tools in Groove.The results are displayed in the form of tree which can then be opened up for details. Other significant features are: 1. Multiple search.
2. Categorized results.
3. Snapshot of all the search results, accross workspaces.
9. Link back search results to Groove by double clicking on the search results.
10. Directly open files from search results, edit and save. Get to know where file is saved in workspace.
11. Export data to excel or print results.
12. User friendly UI.
13. Auto login to account, if user has not logged in.
14. Its free. Limitations for Groove 3.1 users:
1. Auto - login not supported
Groove 2007 users, if not logged will be automatically logged in but Groove 3.1 users cannot be logged in automatically. 2. Link back to discussion and calendar tools
Although Groove Seach 1.1 supports complete link back to discussions/forms/calendar entry in respective tool, it doesn't support the same for 3.1. However it will open the correct discussion/forms/calendar.
To download the tool:http://groovesearch.codeplex.com Please note we have no partners or associations as of yet. It will be our greatest pleasure if we can work in association.
Welcome to the new comprehensive Groove search tool. It is a search tool, specially designed for searching anything in Groove accounts. It gives you results which are directly linked to the tools in Groove. Which means that when you search the files in Groove Search you can directly open it.
The results are displayed in the form of tree which can then be opened up for details. It also contains advanced search options so that results can be filtered on selection. The grid in which the results are displayed further helps for basic analysis like grouping the data, cutom filtering. The data can also be exported to excel and other documents.
It is a free tool. Pre-requisites: 1. Windows Xp SP3 or higher 2. .net framework 3.5 SP1. 3. microsoft Office Groove 2007
MDA is a way to organize and manage enterprise architectures supported by automated tools and services for both defining the models and facilitating transformations between different model types.
Why model driven architecture?
Evolution
Evolution of computers started with hardware programming where in circuits was switched between various points of connection. This procedure was made somewhat easy using the punch cards. As the computers were used only mathematics and science, the usage of computers was restricted to scientists.Scientist found a way to command the computers using the silicon chips and then binary programming came to picture where the commands were stored in memory location and physically moving the circuit points stopped. Binary programming was tedious but it abstracted the physical movement.
Scientists again found out that the binary commands can be abstracted to English like language so that they can programme the chip faster and is easy to remember. It was known as Assembly programming. This opened up new avenue for applications of computers and was used to automate business.
To simplify the process of programming and to reuse the existing written code, procedural programming came to picture. Also there was a need to abstract the database management process due to massive data.Languages like C, FORTRAN and FoxPro evolved with time and procedural programming came to picture.
The problem with procedural programming was that it used to work perfectly for executing a series of steps, but couldn’t depict the real world entities in business, like customers. So to bring them closer to real world entities and to depict the real world business scenario, Object Oriented Programming was evolved. To increase code reusability and implement code standardization, architectures and frameworks were implemented.
As the time passing by, the technology is changing very fast and by Moore’s Law, the speed will keep on increasing. In the process of evolution, the business fundamentals for remained the same. The complete code was re written as the implementation of business in software changed. This resulted in multiple iterations and huge amount of rework. With the ongoing trends, making changes in software will become extremely difficult.
To cope with those problems, Model Driven Architecture is being introduced. MDA defines the way business can be implemented irrespective of the way the technical architecture can be implemented.
Example
Consider a simple example of implementing the simple registration process for school. Applicant comes to registration counter and submits the documents to receptionist. The receptionist checks for the valid documents and if found valid, accepts the form.
Business process:
Procedural Programming:
Object Oriented Programming:
Architectural Implementation: (only for Application class.)
The diagram shows the clear distinction in the methodologies of implementing the code for same business process but different technology. This amounted huge amount of rework and code implementation.
MDA answers this problem by separating the business from its implementation and the complete business can be modeled, independent of implementation.
Implementing Model Driven Architecture:
Implementing MDA is a 3 step process:
Step 1: Creating the Business Domain Model: (PIM)
The first step is to understand the domain and understand the core processes in business. It usually contains 2 diagrams: Business process model and domain model. These core processes are depicted in UML symbols as mentioned by OMG. Domain model is the diagrammatic representation of static relation between various entities in business. Business process model contains the diagrammatic representation of the various processes followed by business for executing day to day activities. These models are also referred to as Platform Independent Model.
Step 2: Finalizing the technical architecture: (PSM)
The second step is to create the technical architecture for the project for the system. Technical architecture is usually defined by the Non Functional Requirements. So architecture can be reused from previous projects.
The critical part is writing the transformation scripts to convert the business model to implementation model, which can be used cases, class diagrams. The transformation scripts actually convert the business model in to implementation model, or the way the system will be implemented.
These models are also referred to as Platform Specific Model.
Step 2: Code Generation:
Final step is to generate the code from the PSM. We need to write the new set of transformation script for generating the code. These scripts are called the code generation scripts. These scripts convert the class diagrams into code, as defined in technical architecture.
How MDA helps?
As shown in above diagram, the code for framework, architecture usually doesn’t change. The core process of the business also remains the same. Thus rather than manually making the changes in the code, the changes in business scenario’s can be modeled, and then using transformation scripts, source code and other artifactscan be generated.
MDA Projects implementation Process
The document above shows the difference in the project implementation process with and without MDA. The clear difference is the process of business analyst creating the Requirement Specification Document to Technical specification document and then to development is completely vanished. With MDA, business analyst, according to requirements creates or makes the changes in the business model.The business model undergoes transformation and then the code generation. With minor changes, the changes can then undergo integration testing.
Benefits
vLogic remains in design
vCan generate specs, documentation and source code using templates
vA change in logic and flow of system is clear and apparent due to designs.
vTakes implementation nearer to business and services it is catering to.
vTime required to implement the changes to code is minimal.
vReduce development time and errors as major part of
vCode can be auto generated.
vReuse existing expertise in domain model.
Prerequisites
vClear and crisp understanding of domain
vClear understanding of implementation.
vDifferentiation between what should be automated and what not.
vExpertise to implement MDA.
vPredefined process to apply MDA to a project / product development
Founded in year 2004, Vedaantees, in its journey of years achieved mastery not only in doing different things, but also doing it differently. We are no innovators, but challenge ourselves to be. We are no solution providers, but we have a sense that is common in all of us. We are what the world knows as "geeks" striving, engineering, re-engineering, manifesting thoughts, and ideas so as to provide top-notch and innovative solutions to our clients, for a better and happy life. We don't believe in requirements, but in understanding and addressing real needs. Our purpose is to bring together the best of IT, systems, knowledge so that we all can spend our time with the one we love and what we love the most.
