Monday, March 30, 2009

Irritated Hair Follicle

I

conventional portal concept is a platform which offers content, functionality (search, advertising ,...), entries ...

A Collaborative Portal is influenced by the Web 2.0 philosophy:
- Users know where to find information (centralized). Depending on the profile information will be shown or another.
- brings together the business processes of organizations.
- job sharing is encouraged Online.
- In Ultimately, the users are the most important.

Soltel walk in engaged in the design and development of a Collaborative Portal, allowing us to accelerate certain processes and of course, we are working to "not stay" in the company. To do this, we emphasize the abstraction, modularization and general services should have to convert it into a product.


What should be a collaborative portal?

- A centralized repository for all kinds of documents. Single point of access to information.
- Agendas shared.
- Incident Management System.
- Tools communication.
- ...


Keys to Success

- Custom (user can see, for example, holidays that are left).
- communication (instant messaging, video ,...).
- Transactions (tasks, access to services).
- Integration with internal applications (ERPs, CRMs ,...). Advantages




- Optimize resources.
- Reduces redundant tasks.
- Improves communication integrated approach and monitoring tasks.
- Reduce IT costs.
- Improved security.
- connectivity information.



Difficulties


- It represents a paradigm shift in the way of working and thinking of the employee.
- You have to restructure the information systems of the company.


Value Generation

The main value is the user. There is no point having the best technological infrastructure and more innovative, if not used heavily by users.
Metcalfe's Law: the value of a communications network increases proportionally to the square of the number of users of the system (n ²).



Factors to consider

- The installation must simple.
- The system should be modular to facilitate scalability.
- Easy to use.
- Use of open standards.
- Service-oriented architecture (SOA), which promote interoperability among different technologies coexisting in the company.
- Security. This is a critical system in the company, so it should be safe.
- should offer a multitude of collaborative services, without reinventing the wheel. There are many who are already implemented in Free Software.
- Ability to adapt to the business.
- Must have good support and communities that support it.


The following article on Collaborative Portals, talk about real solutions and applications that may be interesting in setting up a Collaborative Portal "Integral." Metrics

Tuesday, March 24, 2009

2010 Hobie Adventure Island For Sale

v3 vs Agile Metrics Visit

v3: Methodology of Planning, Development and Maintenance of information systems proposed by the Ministry of Public Administration.

Any defender of the techniques, methodologies and metrics tool v3 agile argue that a system is too heavy, both in its implementation, and in its maintenance processes. I would corroborate, but not demonized.

I'm used to being in this world of computers are believed true "tenets of faith," which carry their own "religious wars." Examples might be: Proprietary vs. Open Source Software, Windows vs Linux, Web Services vs Rest, Oracle vs MySQL, Explorer vs Firefox, Apache vs IIS, Eclipse vs. Netbeans, and we could go with a long list. Instead of finding the best solution, or universal solutions, I propose to make an intensive analysis, and answer certain questions. Generally, there is a solution worth "for everything." The question that finally we can throw more light is: "what is going to use?". That is, try to find the solution that best suits our specific problem or scenario. Metrics

v3 vs Agile methodologies are not an exception. I after having used both, I have an opinion. I would use Metrica v3 in the circumstances which I shall report:
- extremely large projects where it is important enough to have a specified functional analysis.
- Projects involving multiple teams, where communication is not always easy.
- Projects with potential to have a high staff turnover.
- Projects commissioned by clients who are not quite clear what they want, not what they expect.
- Projects with unstable initial conditions, with changes potentially high-impact, and large deviations in the timing of a project.
- Projects implemented by programmers very "junior."
- Projects that v3 metric is non-functional requirement of the client (usually government).

Many of these circumstances are reflected in the Chaos Report as causes of most failures in software development projects, and can be alleviated significantly by Metric.

is true that every change in the Functional Requirements (FRQ), for example, may mean you have to make changes in one or more, information requirements (IRQ), Constraints and Business Rules (CRC), in Case use, and even in the Data Model, and keep this often tedious and time consuming, but also provides:

- Some requirements are stable.
- A detailed project specification, which can reach the separation on many simple tasks.
- An analysis of the client must validate, and that is the "contract" for both developers and the customer.
- Traceability to tell us the impact and costs involved in a change request.

Instead, it is true that for projects that are not under the circumstances I have outlined above, the agile techniques, or an adaptation of these (depending on the project, expertise and equipment, client) can give us better results.

Monday, March 16, 2009

How Much Does Stacey London Make A Year

Accenture - Málaga

On March 4th I traveled to Manchester, along with the manager Soltel , Julio Perez. More specifically, we were in the Technological Park of Andalusia. We were in Sequel ... There will be time to talk about it. In this post I talk about my meeting with Pedro García Navarro, responsible for implementing processes and CMMI certification of Accenture. Pedro

received us very kindly, and showed us the facilities of Delivery Center, home to about six hundred workers. I was especially struck by the CPD, where they had all kinds of servers to emulate any environment (IBM, Sun ...).

After we were talking about the CMMI certification. They are level 5, which is not easy to achieve. Carlos had combined some agile tools, techniques heavier. There will be an upcoming article that front heavy with agile techniques.

Pedro Garcia knew that he had designed the indicators of maturity of all Accenture centers in the world, and since I was developing the plan of maturation Development Team Soltel for Enterprise Strategic Plan, I asked him to converse about it, and drew some conclusions:

1. What matters are the processes, tools above. If you can use some automated tool, icing on the cake. For example, and simplifying, it is important to test the software. You can make programming unit tests with JUnit or TestNG, but it is essential to do, even manually.
2. It is good to sort the indicators and measures to improve these indicators, levels, both individually and in terms "team" community "and they are known to developers, so they know what level they are and should make it better.
3. During 2009 will change the process of ISO-9001 Quality Aenor Soltel to adapt to our new way of working. Our new way of working we should lead to producing quality and with little deviation in the projects. The processes should be the vehicle to the quality of software, not towards the "stamp in" Aenor only.
4. We are on track, and soon we will get great results. This was the same feeling I got when I spoke to Manuel Pray (as well as receive other good tips to put into practice).

Tuesday, March 10, 2009

Shower Magnet Strip Australia



concept that dominates Internet Portal, is associated with Content Management. A portal is much as it can offer a flexible way, "pieces of programs, Java Portlets in the world, adapted to the needs and preferences of the administrator, or each user. In fact, not all users have to access (or have chosen in your preferences) to all portlets in a Portal.

That is, if we are modularity, flexibility, and even interoperability between platforms Portlets based solution is optimal.

As a picture is worth a thousand words, I invite you to try (which you have not already done so), iGoogle .


From iGoogle is not difficult to imagine an enterprise software, ERP, CRM, or an intranet-based portals.

Well, these "snippets" have Java specification: JSR-168, JSR-286 (Portlets version 2.0) and the site containing the portlets is a portal.

Before developing any portlet, the logical process is to analyze why there are portals in the market and see what benefits are. I understand that we have studied some engineering, this process of analyzing the right solution for every problem, we have internalized. We continually consulting on technology (this does not mean that people who have not studied engineering unable to make a consultancy). Back then, I did consulting portals, the portals appreciated: Liferay, JBoss Portal and JetSpeed \u200b\u200b(previously had ruled out other solutions, not to suit our requirements.) I will not go into the details of the consultancy, as it would for various posts. Just let me tell you that the performance of Liferay are dramatically higher than those of its competitors.

In my company we have a firm commitment to this technology and we have faced some Liferay-based portals. We have integrated Liferay with Alfresco (Document Management). Our goal: to become a reference for Liferay in Spain, not only for private enterprise, but for the government. And I hope there will soon be news about it ...

Tuesday, March 3, 2009

Viral Infection Arm Numbness

Liferay Portlets with J2EE Architecture - MVC Pattern

The concept of reusing software is not limited only to use the same functions, classes, or methods to solve similar problems, but extends to other phases of software development as can be, as is the case at hand in this post, architecture.

reuse in internal architecture level are particularly important design patterns. Specifically, today I speak of the Standard Model-View-Controller. The MVC pattern is widely used in various types of applications.

I heard comments from developers, in which J2EE associate this pattern, since there are several frameworks that implement it, such as Spring MVC, but MVC, like other employers, is not unique the technology. In fact in the first iteration of design, architecture abstract programming technology. In Soltel have adopted this pattern in many developments of a different nature: J2ME mobility, mobility. NET, C #, and of course in J2EE applications.

In our day to day, do not develop critical applications, where it would be prohibited from using this type of pattern. In fact I doubt that for a critical application is chosen Java as a technological solution.

For J2EE applications, most of the time, the MVC architecture meets the needs of the application. In fact, I think it has become as standard de facto, and if you work on projects for public administration in Andalusia, almost a de jure standard, as in hanks (Framework for the Development of Andalusia), is recommended.

broadly, the pattern indicates that they should establish three components or layers in the architecture, each of these, only communicates with the adjacent.


- Layer View: Responsible for the presentation logic and data capture our system to the outside and vice versa.
- Control Layer: Responsible for the operational logic of business. Forwards requests Layer View of the Model Layer, and according to the response, redirect or Layer not Vista. Load objects and works with them.
- Layer Model: basically contains the actual business logic, the application domain (VO, Value Object) to get and set classes, and data access objects (DAO) to implement CRUD (Create, Read , Update, Delete). This broadly, because depending on the application, as well as VO and DAO patterns, you can enter a Façade. This layer interacts either directly (for example, jdbc) or through the persistence layer with database servers, LDAP ...

Many of the J2EE frameworks and implement communication mechanisms between layers following MVC.



Using JSF or Struts layer for Vista, for Layer Controller Spring and Hibernate JPA for Layer model would be one solution to the J2EE application architecture. Advantages


MVC pattern gives us a very maintainable software construction, which can be located in a flexible errors. Is a modular design, and little trailer, promoting reuse.
For example, we can make a desktop GUI and a web, which share the controller and model layers, and only treated as separate developments in the two layers Vista.

Swallowing 6 Goldfishes Hd

Starts: Master in New



Perfeccionate: Master in Alternative Therapies


Our goal as therapists is to convey our learning over the years so that each reader can find in this blog a place where you can learn, experience and taste the best advice and scientific material that we will write a daily basis to achieve a better quality of life: physical, mental, emotional and spiritual.
Techniques to develop throughout this journey we will walk together will be:

* Foot Reflexology Massage Metamorphic

* * * Theory
Pranoterapia and practice of Chakra Meditation

* * *
Bioenergetics Healing Visualization Relaxation and breathing techniques

* * * EFT-
Cromoterapia "Emotional Freedom Techniques." Dowsing

* * * Magnet

Gem * Bach Flowers - Herbal Remedies, and much more ...

An imbalance in the human energy field creates a disturbance in the physical, emotional and mental. Alternative therapies work reorganizing the energy imbalance to achieve comprehensive health care.
In this context, characterized by Biopsicoenergética collect these ancient knowledge and give a scientific foundation and practical for everyone to get a better quality of life.

The Saturday 21 March at 16.30 pm is performed briefing and open on the Master in Alternative Therapies.

'll see you at the LIBRARY OF OLIVES.

Av Maipú 2901 - Olivos.
Reports: 4794-7655

Teachers in charge:

Marpez
Alberto Miguel Angel Cancino Mario Callegari