In this post, we are going to have a look at UI commands. UI commands are responsible for reacting to user input, for example the send button click in the sample I use throughout this series of agile user interface development in .NET series. For other posts in this series look here: table of contents.
We have seen in the last post that the view binds a command to the send button that it gets from the view-model:
Last time we started looking at sample code with the view-model class for the UI to send messages on channels (table of contents). In this post, we continue with the next responsibility, the visualization. The View The view is responsible for visualizing the domain model to the user. We have seen in the last post that the view-model provides a simplified mini-model to the view. That means that the view does not have to care about the domain model as a whole with all its interactions and...
After the posts (table of contents) in which I covered why we need an agile UI design pattern, it’s big picture and the needed tools, I start digging into sample code. I’ll show in each post a small part of the whole picture. If you want to get all at once then you find the source of all samples at . ProCollEE is my playground to experiment with WPF and UI design. Lets start Yes, let’s start. But where? There is one UI design pattern – presenter first (link) – that...
In the last post, I showed you the big picture of my UI design pattern. Before I can start showing you sample code for the different parts, I need to introduce some tools, which are used to glue all the tiny parts together:
Dependency Injection
Design By Contract
Synchronous and Asynchronous Communication
Test Driven Development
In the last two posts of this series (table of contents) I explained the need for a new UI design pattern: changeability and extensibility.
In this post, I’ll throw a big diagram in your face without much explanation. The reason for this is that I want to give you the big picture before I start digging into details in the following posts of this series. You can always come back here to see where we are.
The Big Picture
In the first post in this series (table of contents) I explained why agile software development influences the choice of the UI design pattern. For short, changeability and extensibility are must have characteristics. In this post, I’ll show you the corner stones of a UI design pattern that fulfills these needs. Principles of Object Oriented Software Design – SOLID One of the best known set of principles to achieve my goal of a UI design pattern that is changeable and extensible is...
There are a lot of patterns available for UI architecture: Model-View-Presenter (MVP), Model-View-Controller (MVC), Passive View, Model View View-Model (MVVM) and some more. However, none does really fit my needs in an agile project. In this series, I’ll show you first why they don’t work for me and then I’ll try to evolve a pattern that matches the special needs in agile software development. Why is Agile Software Development different? In agile development, we start little...
Recently, I was asked by a colleague why I like Scrum. I didn’t have a good answer at hand immediately, and since then the question bugged me. Therefore it’s time to give you my top ten now:
Team Spirit
Continuum Of Work Pressure
Don’t Assume, Show
Team Knowledge Over Experts
Control Is Good, Presentation Is Better
Continuous Improvement
True Incremental Development
No One-Man Shows
ROI Is The King
Fun
I found the blog Agile: In A Flash some time ago and I really like it.
The blog discusses agile software development based on flash cards. The authors put together cards that each express a single idea, practice or methodology in agile software development.
Go and have a look!
Some people share the opinion that scrum and other agile development methods are easily maintainable with pencil and post-it only. Nonetheless there is a growing list of software solutions which support scrum methodology. Boris Gloger from Scrum 4 You publishes regularly reviews of scrum tools on his blog. I strongly recommend to take a look at his website and the scrum tools list!