Application Development Procedure

1. Application Code that shows the working application with source code available
2. Specification Document which explains the purpose of the application and collects all its requirements
3. Application Coding Standard which consists of a collection of Architectural Patterns and underlying Coding Conventions in the code
3.1. Architectural Patterns: "Model-View-Controller" (MVC),
3.2. Coding Conventions on the basis of ASP.NET MVC

We have created a Visual Studio solution that contains three projects:
.Domain - C#Class Library - holds bisness logic
.WebUI - ASP.NET MVC 3 Web Application - controllers and views
.UnitTests - Test Project - holds the unit tests for the other two projects

source used: Pro ASP.NET MVC 3 Framwork , Freeman/Sanderson, Apress

Source control

Subversion
(http://svnbook.red-bean.com/)

Tortoise SVN
http://tortoisesvn.net/docs/nightly/TortoiseSVN_en/index.html
(suomeksi: http://tortoisesvn.net/docs/nightly/TortoiseSVN_fi/index.html)

Here starts specification document of the application

We are creating an application which will run on multiple mobile platforms using ASP.Net with MVC structure.

Currently we are preparing first prototype of the application using Flickr example application as a starting point of the development.

Abstract here is to demonstrate how MVC application which slower to build compared to e.g ASP.NETWeb Forms, will eventually be good investment for mobile applicatin infrastructure
*maintainable
*extensible
*well-structured code
*support for unit testing

Sample application will be Flickr feed reader that simply demonstrates how the same webcontent /-service can be scaled at different platforms. There is The Flickr.Net API Library for accessing the Flickr API. Current CodePlex Flickr.NET API is written in C# and it can be accessed from the following framework:
*.Net Framework 2.0 and above.
*.Net Compact Framework 2.0 SP1 and above.
*Silverlight 3.0 and above.
*Windows 7 Phone
*Mono
*Monotouch for iPhone

Requirements for Flickr application

*easy to create different UI Views based on the multiple web clients
*mobile connectivity and bandwidth issues

Scenario Flickr application

Scenario where user can view and search Flickr pictures with the device.
1. Users should be able to view list of Flickr Categories with the device
2. The category list should be searchable
3. User should be able to choose one picture from the Category list
3. Using device input method user should be able retrieve picture to View

test case

Feature: device detection
In order to provide optimal user experience both for mobile and Desktop
first need to detect device plaform

@mytag
Scenario: Mobile or Desktop
Given User access Flickr application
And mobile user agent
When request of service
Then mobile View/mobile_libraries will be served

Scenarios
features