|
RE: Re: Development: A Structured Problem Area?: msg#00052programming.language-of-the-year
Why is the expression of requirements separate from the code? Are you viewing these as separate entities because the design of most languages is lower level than the language you express requirements in? It seems to me that if you write a solid abstraction layer for your business's systems, then the code should more closely resemble the language of your business requirements. Take a look at something like AppleScript, where the code is written more like natural English. Certainly, structure is still required for the interpreter to understand it, but my wife can look at it and tell you what it is doing. Now, if you have your core processes abstracted (using Java, or whatever you like), and you can write code in something that is more readable (even more so than AppleScript), do you still need to have separate business requirements documents from your code? I don't think it is that unreasonable to close the gap between the language of requirements and the language we use to code our applications. There is still going to be a need for plumbing, but closer to the user interface, things really should be much simpler than they are now. -----Original Message----- From: Gregg Irwin [mailto:greggirwin-mn4gwa5WIIQysxA8WJXlww@xxxxxxxxxxxxxxxx] Sent: Saturday, June 19, 2004 7:27 PM To: Greg Jorgensen Subject: Re: [pragprog] Re: Development: A Structured Problem Area? Hi Greg, GJ> Perhaps the key is finding the right language for expressing GJ> requirements. Yes, and the "right language" is different for every problem space; we need a lot of languages, domain-specific languages. --Gregg Yahoo! Groups Links ------------------------ Yahoo! Groups Sponsor --------------------~--> Yahoo! Domains - Claim yours for only $14.70 http://us.click.yahoo.com/Z1wmxD/DREIAA/yQLSAA/nhFolB/TM --------------------------------------------------------------------~-> Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/pragprog/ <*> To unsubscribe from this group, send an email to: pragprog-unsubscribe-hHKSG33TihhbjbujkaE4pw@xxxxxxxxxxxxxxxx <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/ |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: Re: Development: A Structured Problem Area?: 00052, Chris Morris |
|---|---|
| Next by Date: | Re: Re: Development: A Structured Problem Area?: 00052, Robert Watson |
| Previous by Thread: | Re: Pragmatic Project Automation [was ...]i: 00052, Dave Thomas |
| Next by Thread: | Fwd: Re: Re: Development: A Structured Problem Area?: 00052, Bryan Ewbank |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |