DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Partner Zones AWS Cloud
by AWS Developer Relations
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Partner Zones
AWS Cloud
by AWS Developer Relations

The Secret Focus of Successful Software

With all the talk over various Agile processes, the true focus of software, providing quality code to people, can get pushed aside.

Michael Dowden user avatar by
Michael Dowden
·
Jul. 04, 17 · Opinion
Like (2)
Save
Tweet
Share
3.83K Views

Join the DZone community and get the full member experience.

Join For Free
Quality software is hard work, but the results will be worth it, for you, your company, and your customer.

There is a constant influx of hype these days around X-first and X-driven software. Some examples:

  • Mobile-first design.

  • Content-first design.

  • Test-driven development.

  • Fear-driven development.

  • Complaint-driven development.

  • Model-driven development.

What each of these approaches has in common is that they elevate one specific factor of software design and development as more significant (either good or bad) than the others.

Modern software should not be built this way. There are exactly three factors that all modern software should consider as equally important, and are the only design criteria you will ever need:

Mission + Audience + Integrity

Mission

This is the purpose for your software. The objective or goal. Its very reason for existence. It is hard to sell software that doesn't have a clear purpose because it is hard for people to visualize the problem it solves.

It is easy to get distracted by new technology and industry trends. However focusing too much on the technology means losing focus on the real value your software should provide.

Audience

Your audience is those people that will use your software. This embodies their needs and desires along with their experience using your software. Nobody will use software that is difficult to use or fails to address a problem.

Carefully looking at your audience will help you make the right design decisions. You might discover you only need a mobile app, don't need one at all, or even that your software should simply be a plugin to an existing product.

Integrity

The overall integrity of the system includes such fundamental concerns as availability, reliability, security, and performance. This includes protections for information held by the system. People will not trust software of low integrity and will not use it.

Nearly every week there are examples of private data being leaked and consumers losing confidence in companies and products.

Getting It Right

It is critical that we stop assembling teams of only programmers and start assembling diverse teams across disciplines such as user experience, design, security, quality assurance, and infrastructure.

Collaborating across diverse teams is a lot harder than just a development team slinging code. It will require everyone on the team to set aside their ego and accept input and critique from others.

Software design

Published at DZone with permission of Michael Dowden, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • How To Build a Spring Boot GraalVM Image
  • Use Golang for Data Processing With Amazon Kinesis and AWS Lambda
  • Apache Kafka Is NOT Real Real-Time Data Streaming!
  • Best CI/CD Tools for DevOps: A Review of the Top 10

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends: