Not Signed-In
Which clippings match 'Use Case' keyword pg.1 of 1
11 MARCH 2013

Mobile Apps: the trouble with using 'Responsive Design'

"Amid an overwhelming amount of mobile options and solutions, it's easy to see why responsive design's singular code seems like an alluring universal panacea for mobile optimization. However, while responsive design aims to scale web content fluidly across multiple devices with different screen sizes, it may not represent the best option for organizations aiming to deliver unique and innovative experiences to customers. ...

The future of digital business depends primarily on mastering the mobile channel. Mobile's mushrooming numbers are due to the convenience of remote access and a new reliance upon the delivery of information when and where little to none was previously available. When developing your approach to engaging customers via mobile, it is key to ensure your strategy accounts for the rising expectations your customers have for this important channel.

Once you understand the kind of mobile experience you want to create, you can decide whether adopting a responsive design philosophy can deliver upon these expectations and goals. While responsive design can help you achieve a certain measure of consistency across channels, the real prize lies with the ability to create unique experiences. A broader multi–screen approach designed dynamically by channel will enable the sort of customer experiences that yield higher engagement and contribute to overall success."

(Carin van Vuuren, 18 November 2012, Forbes)

TAGS

appconveniencecustomer experiencedesign principles • device-specific content display • differencedigital business • engaging customers via mobile • Forbes • Forrester • information delivery • interactive experienceLinkedInmagazinesmobile apps • mobile channel • mobile development • mobile experience • mobile optimisation • mobile site • mobile solutions • mobile strategy • multi-screenmultiple devicesnewspapers • one-web • People magazine • remote access • responsive design • responsive site • responsive web design • scale web content • screen size and orientation • screen sizes • singular code • smartphonetechnology solutionuse case • varying screen sizes • web development • web experience

CONTRIBUTOR

Simon Perkins
06 NOVEMBER 2008

The Waterfall Versus Whirlpool Project Management Methods

"'Whirlpool' projects embrace the fact that requirements are volatile. Instead of trying to deliver a system that satisfies 100% of the requirements in one go, the focus is on delivering an agreed subset of the requirements at intervals. Use cases are the building blocks of requirements and provide a convenient basis for risk assessment and prioritising. The riskiest and most significant use cases are tackled first, within the context of a clearly understood architectural vision. Tackling risk early identifies problems before they become too expensive or threatening, and helps lead to more stable architectures. The system evolves as a sequence of increments, each one an enhancement to the already–delivered functionality.

The development process for each increment is founded on the idea of a workflow, consisting of activities. For example. instead of having an analysis stage followed by a design stage, a worker might be engaged in analysis activities and design activities, depending on the job in hand. It is important to recognise that analysis activities focus on the problem space, while design activities focus on the solution space. A good understanding of one part of the problem may well lead to faster progress to design in that area. It is also possible that design activities highlight shortcoming in the analysis or even the requirements, in which case these are amended to reflect the newer (and hopefully better) understanding.

Successive iterations converge on a more complete, correct and consistent model, leading ultimately to implementation and delivery."
(Tecademy)

1

TAGS

agile developmentconcurrent engineering (CE)developmentdevelopment life cycleincremental • iterative • objectives • PRINCE2 • projectproject managementproject management methodrequirementsrisksoftware development lifecycle • stable • Unified Process • use case • volatile • waterfall modelwhirlpool modelworkflow

CONTRIBUTOR

Simon Perkins
Sign-In

Sign-In to Folksonomy

Can't access your account?

New to Folksonomy?

Sign-Up or learn more.