Jowles Object Model: Difference between revisions
From HBMobile
Jump to navigationJump to search
No edit summary |
No edit summary |
||
Line 6: | Line 6: | ||
=Jowles, What Does It Do?= | =Jowles, What Does It Do?= | ||
''Jowles is a web application that controls a mobile phone. Consisting of a Javascript enabled web client, a GSM module control daemon and a PHP-based testing and mocking Interface; each component is capable of being independently upgraded. The goal of the system is to provide a toolkit for experimentation.'' | |||
=Classes | =Instances, Interfaces and Classes= | ||
: Application : The '''Application''' represents the top level... uh... application that the UI interacts with. It understands concepts like communication modules, data networking interfaces | |||
Revision as of 00:25, 24 April 2007
Introduction
- Why would we care about an Object Model?
- Most of the work in any software development project is in trying to figure out the true requirements. Slinging code is (or can be) easy, interviewing end users to figure out what they want in a mobile phone and then deciphering their responses... well, that's a lot harder. What makes it even harder is that if you're doing any large project, you have to get all your developers thinking about the project in the same way. This is why I like Model Driven Architectures (User:Msh). MDA as it is described in the literature may be overkill for the Jowles project, but the theory sounds nice. I'm also a fan of Object-Orientation 'cause in my experience, encapsulation and inheritance are powerful tools for representing application models.
- Okay... one more time... in English...
- In short, the Jowles Object Model describes the behavior of system components in a language-neutral manner. Used correctly, Objects and Classes can make it easy to add new features to the system. We're all about giving people the ability to extend the stuff we've done here, so OO Models it is.
Jowles, What Does It Do?
Jowles is a web application that controls a mobile phone. Consisting of a Javascript enabled web client, a GSM module control daemon and a PHP-based testing and mocking Interface; each component is capable of being independently upgraded. The goal of the system is to provide a toolkit for experimentation.
Instances, Interfaces and Classes
- Application : The Application represents the top level... uh... application that the UI interacts with. It understands concepts like communication modules, data networking interfaces