Architect Consultant blog

I see it in a lot of projects but also I see that it is handled just like testing in the beginning: "oh we estimate some extra days and we also go Mobile !" Of course this is not the case, it can be a project on its own. There are a lot of choices to be made, some of them are: Which mobile platforms do we have to support? What are the performance requirements? Do we want to develop once, run anywhere? Do we want to use native functions of the mobile OS? What I also see, is that more and more BPM/Integration platforms are going to support it. But then again the Mobile experience is somewhat different than the Browser (and Desktop) experience. So depending on the requirements of the Mobile App, the platform can suffice or not. I will shortly describe some platform examples. OpenText Assure This is a BPM platform that supports Mobile. However the UIs are running within the browser app of the mobile device. The advantage is that it is developed once, and

Introduction I wanted to know more about DevOps because I agree with the fact that we need to coorporate more and remove the barriers between departments. In the end I was a little disappointed by this book. It gives some high level tools and techniques but it could be much more ... In my opinion a change would be that someone from Operations will really participate within the project team and looks at it from an operation point of view. This way also these requirements will be taken into account and the system will be more easy to operate. However there were also some interesting chapters so lets review. Chapters The book contains 7 chapters: Evolution of a Software House No pain, No gain Plan of Attack Tools and Technical Approaches Culture and Behaviors Hurdles to Look Out For Measuring Success and Remaining Successful Chapter 1 - Evolution of a Software House As the name already suggests, this chapter is about the evolution of a software house. First it