Learn More About the Interface-Driven Architecture Method
-
Phase 1 - Architecture
-
Analysis
We don't write a line of code until we know your business as well as the people who keep it running every day. During our initial Analysis stage, we'll interview your key stakeholders to get a thorough sense of all the business requirements your application will need to address. The way your company works will be reflected in the solution we create.
Objectives
- Review existing business process
- Identify organization/brand position
- Identify user profiles
- Create use cases
- Research supporting technologies
-
Interface Design
Once we know exactly how the software should fit into the business process, we design an interactive prototype that allows all the project's stake-holders to engage with the system in real-time. This step is a key principle of Interface-Driven Architecture and a critical part of the process. Because we do it early in the development stage, it allows us to ensure your software is intuitive, easy to use, and really does what you need it to do—well before moving into development.
Objectives
- Define site/application structure
- Create site/application design
- Design user interaction
-
Usability Testing
Once we've designed the prototype, you and your stakeholders take it for a test drive. We assemble focus groups of target users to test the system and provide feedback until we get the function and usability just right. This methodical user testing process lets us ensure the software is both effective and easy to use.
Objectives
- Assemble virtual focus groups
- Test use cases
-
-
Phase 2 - Fabrication
-
Software Engineering
You can't build a house without a blueprint. And you can't build software without a "domain model". This is the foundation on which your software will be built, including all software components and databases.
Objectives
- Create domain model
- Create data schema
- Create API (Application Programming Interface)
- Create user documentation/help system
-
Coding
Our method makes the actual "programming" process easier for us—and less expensive for you. Unlike a traditional development process, ours establishes all the system's requirements before a line of code is written. And because our programmers are skilled in a wide range of languages, we have the expertise to select the technologies that will work best for your project.
Objectives
- Develop system component
- Perform unit testing
- Perform coverage testing
- Perform load testing
-
BETA Testing
During the coding phase, we build the code. In the beta testing phase, we try to break it. Many software developers will leave the beta testing up to the user—so that as you use the "finished" product, you find the errors and request the fixes. We prefer not to deliver the software until it's perfect—so we test in-house. Our dedicated testers work in partnership with coding specialists to find and eliminate problems before the software is launched.
Objectives
- Test all use cases
- Conduct acceptance testing
-
Deployment
We've built an interactive prototype and run it by the users. Then we've written our code and done our best to break it. After this, the launch is the easy part. Our process results in flawless software that works the way you expect it to in a live environment—with no surprises.
Objectives
- Prepare server environment
- Deploy code to production server
-
Obsessively Thorough The Book
Obsessively Thorough Software Design examines the fundamental flaws that often bedevil development projects, and demystifies the software design experience to pave the way for systems capable of transforming business from the ground up.
“An intelligent exploration of a next-generation methodology for achieving software excellence. Helms and Valberg provide a proven framework for the kind of design experience companies need to keep innovation happening.”
Purchase Your Own Copy
All major credit cards and Paypal accepted
via our 100% Safe Shopping Cart.
- Visa
- MasterCard
- American Express
- Discover
- Paypal