Thursday, November 13, 2003
Tuesday, November 11, 2003
the well defined,accepted and evolving UML 2.0 is pretty good for modeling information systems. The only problem is that it does not realistically help us get creative since there is so much diversity in how we get creative. will talk about UML later.
For now i know that i have to
-model the UI,CLI or CI (desktop, terminal, client)
-model subsystems
-model interaction
(remember a lot of what i am doing is solo so there is less collaborative structure)
naturally this is better done graphically (beware of folks that don't like pictures - they are bad people)
modeling and prototyping this pieces can be lots of fun if you have the right "things"
For now i know that i have to
-model the UI,CLI or CI (desktop, terminal, client)
-model subsystems
-model interaction
(remember a lot of what i am doing is solo so there is less collaborative structure)
naturally this is better done graphically (beware of folks that don't like pictures - they are bad people)
modeling and prototyping this pieces can be lots of fun if you have the right "things"
this week i am working on several projects. Some enterprise development with proprietary and open source frameworks, lots of desktop stuff, maybe some handheld.
I will start with what am doing today. The distributed system that i am doing currently uses JMS queues
I will start with what am doing today. The distributed system that i am doing currently uses JMS queues
---queues are FIFO---
which means that conceptually or metaphorically the whole thing is just a service and am really just writing client code. I also have to do some admin work, but its mostly client coding. The JMS client API thats available means that interacting with the server is really just like interacting with the file system. The other thing that i am working on is client-server with ADO.NET
Of course between ADO and WinForms there is enough frameworking to make the client programming almost the only thing i do.
this week i am working on several projects. Some enterprise development with proprietary and open source frameworks, lots of desktop stuff, maybe some handheld.
I will start with what am doing today. The distributed system that i am doing currently uses JMS queues which means that conceptually the whole thing is just a service. The JMS client API thats available means that interacting with the server is really just like interacting with the file system. The other thing that i am working on is client-server with ADO.NET
img
I will start with what am doing today. The distributed system that i am doing currently uses JMS queues which means that conceptually the whole thing is just a service. The JMS client API thats available means that interacting with the server is really just like interacting with the file system. The other thing that i am working on is client-server with ADO.NET
img
did i say i develop software...enterprise solutions of all types, transactional systems, internet applications, desktop software, handheld sofware and even micro devices software. Currently i mostly do enterprise and desktop stuff. The design, development and deployment of such solutions will be the focus of this blog. If you think about it, thats all the relevant information systems that exist today. Embedded stuff requires less coordination.
i write software. Small software, big software and yes sometimes magic software (vaporware). I often get analysis paralysis since its more natural to solve problems sequentially but creative work is not sequential. Information System Architecture and Development is never sequential hence gantt charts and so on. I do a lot of solo work and frankly i think most people are the same as myself, they do alot of solo individual work.I am a contractor/consultant (a bad one) and that means that the vernacular changes a few times a year. I sometimes use UML and RUP, sometimes XP and more times JSU.
JSU is probably the most popular and common information system related design and developement methodology. Its success is probably related to the fact that it is widely used in many other disciplines. Because of the ambigousness that comes with using "information" "systems", "archi.." i will get more specific here shortly. And for anybody that cares "JSU" means "just show up", a random, often frivolous way to do anything
JSU is probably the most popular and common information system related design and developement methodology. Its success is probably related to the fact that it is widely used in many other disciplines. Because of the ambigousness that comes with using "information" "systems", "archi.." i will get more specific here shortly. And for anybody that cares "JSU" means "just show up", a random, often frivolous way to do anything
Subscribe to:
Comments (Atom)
