Architecture for Qt Mobile App and Azure mobile services
-
We are in the process of Architecting a mobile app to be developed using Qt and Azure Mobile Services. Coming from C#.Net background and worked on WPF applications, it's something new for us. We have used MVVM, MVP in past along with Layered architecture. Which architecture pattern will be the best fit for this kind of application? Read about Layered and Onion architectures. Onion architecture provides loose coupling in a better way and adhere to DDD somewhat. Please suggest if something else will be a good fit. Also, like to know which development methodology(DDD/BDD/TDD) shall be used considering the duration to be 4 months.
-
We are in the process of Architecting a mobile app to be developed using Qt and Azure Mobile Services. Coming from C#.Net background and worked on WPF applications, it's something new for us. We have used MVVM, MVP in past along with Layered architecture. Which architecture pattern will be the best fit for this kind of application? Read about Layered and Onion architectures. Onion architecture provides loose coupling in a better way and adhere to DDD somewhat. Please suggest if something else will be a good fit. Also, like to know which development methodology(DDD/BDD/TDD) shall be used considering the duration to be 4 months.
-
Why are you looking at it from the wrong end? The first thing you need to do is to get the overall design of the application worked out. Only then can you really see which patterns, methodologies etc will fit with what you are trying to create.
Thanks Richard. Can you suggest what should be covered in overall design? Is it going to UML diagrams(Component, Class, Use case). In Agile world, how much design would be enough for such an application.
-
Thanks Richard. Can you suggest what should be covered in overall design? Is it going to UML diagrams(Component, Class, Use case). In Agile world, how much design would be enough for such an application.
Well you know what you want this application to do, so you should be able to identify all its requirements and get them documented. Like I said above, you need to get your design complete first, then you can start looking at what processes and patterns would be most useful to turn that design into a working product.
-
Well you know what you want this application to do, so you should be able to identify all its requirements and get them documented. Like I said above, you need to get your design complete first, then you can start looking at what processes and patterns would be most useful to turn that design into a working product.
I am planning to follow the C4 technique for Software architecture by Simon Brown as it seems to be agile and incremental. C4 model poster - Coding the Architecture[^] Thanks again for your inputs on this.
-
I am planning to follow the C4 technique for Software architecture by Simon Brown as it seems to be agile and incremental. C4 model poster - Coding the Architecture[^] Thanks again for your inputs on this.
The question looks quite blunt. MVVM, AFAIK it's like a MS trademarked one. (Though there are a pile of frameworks for Web-client). It's tightly bound with WPF/SL & similar MS frameworks. MVP/ MVC, unless it's with frameworks like Cocoa (mac) & Asp.net MVC, which gives you some guidelines with implementations, it's just a pattern you can implement anywhere by yourself. All these what we are talking about is UI design patterns. And the link you've shared talks about Software Architecture in general. First decide what UI pattern framework is available right out of the box in Qt. This is just for the UI to Data binding design. The rest is the whole story. It all depends on what you need in your App. You can create you own "patterns" as per your need!
Starting to think people post kid pics in their profiles because that was the last time they were cute - Jeremy.
-
The question looks quite blunt. MVVM, AFAIK it's like a MS trademarked one. (Though there are a pile of frameworks for Web-client). It's tightly bound with WPF/SL & similar MS frameworks. MVP/ MVC, unless it's with frameworks like Cocoa (mac) & Asp.net MVC, which gives you some guidelines with implementations, it's just a pattern you can implement anywhere by yourself. All these what we are talking about is UI design patterns. And the link you've shared talks about Software Architecture in general. First decide what UI pattern framework is available right out of the box in Qt. This is just for the UI to Data binding design. The rest is the whole story. It all depends on what you need in your App. You can create you own "patterns" as per your need!
Starting to think people post kid pics in their profiles because that was the last time they were cute - Jeremy.
Thanks Vunic!