Hi,
In fact I'm exactly at the same point as you.
The company started the development 2 years ago, and as every start-up time to market is quite more important as guidelines and standards.
Now, we need to put a frame around all that is analyzed, designed and developped.
So I am in teh process of writing this Design guideline.
One question I want to ask you : Have you defined the scope in a very precise way, i.e. at what granularity level do you stop ? And what flexibility do you let to designers ?
Anyway, I'm quite surprised nobody answered you.
It seemed to me that some quite good professionnals were active on this list.
Unless, in practice nobody makes that guideline ?
Romuald Restout
Senior Analyst
Recruitsoft
-----Original Message-----
From: Williamson, Rusty
To: '[EMAIL PROTECTED]'
Sent: 11/27/00 2:02 AM
Subject: RE: (ROSE) Design Guidelines
Col,
I'm 3 weeks into the development of the Use Case Modeling Guidelines and
Design Guidelines, plus a model demonstrating the guidelines and the use
of
the RUP framework (anyone notice its missing the 'test model'?). I have
perhaps another couple of weeks of work left. Its not been the OOA&D
part
or the UML or modeling parts thats taken the time (been there, done
that) as
much as learning how RUP wants it done and how Rose works as well as how
the
RUP framework organizes it.
Its funny, I didn't get any feedback from the forum on this issue
(original
message at bottom) -- not a word. Oh well, I was asking a lot. Now,
however, to just publish that much work causes a slight pain in my
chest.
If I thought I'd get some constructive feed back that would be another
story. Oh, I'll do it... maybe. I will need to get approval from my
manager. My justification to him will be 'valuable feedback from the
design
community' and indeed that is the purpose -- I'd love someone to tear it
to
pieces (in a nice way). If I get approval I'll post both the artifacts
and
the model. Its just the 'first go at it' anyway, its going to change as
we
use it.
[side note: analysis has become a dirty word]
Management is so preoccupied with 'analysis paralysis', sometimes, I
think,
also known as 'we want it now, just do it!'. Try sending a construction
worker with a rivet and an torch into an empty field and see how long it
takes to build that skyscraper. 'Analysis paralysis', what a catchy
phrase... tell you, I'll take a dozen designers doing months of
'analysis
paralysis' any day to the other side of the coin -- 5 to 10 years paying
100s of support and development personnel to support a bloated ad hoc
product. Rational, in tune with 'market forces', has wisely bent with
the
wind by down playing and all but eliminating the analysis model. And,
LOL,
moved it to 'use-case realization'! Even then, we quickly move through
it
and 'seamlessly' into design. Trade-offs... I guess.
Rusty
------------------------------------------------------------
Rusty Williamson
Sr. Systems Architect
GERS Retail Systems
http://www.gers.com/
The Object Workshop
http://home.san.rr.com/williamson/
Home Page
http://www.znet.com/~rusty/
------------------------------------------------------------
-----Original Message-----
From: Colin Gourlay [mailto:[EMAIL PROTECTED]]
Sent: Saturday, November 25, 2000 3:16 PM
To: '[EMAIL PROTECTED]'
Subject: RE: (ROSE) Design Guidelines
>... I will post the final product, minus any proprietary material, and
will
furnish the URL when it is completed.
Rusty,
This would be fantastic.
I am a novice at UML having just recently studied it at OU so I am
afraid I
cant help you out with your requests - I do however look forward to your
final posting - as I am sure do many others on the list - where I can
hopefully learn from a real example as opposed to the many 'academic'
examples I have been provided with recently
Regards
Col
-----Original Message-----
From: Williamson, Rusty [mailto:[EMAIL PROTECTED]]
Sent: 04 November 2000 17:18
To: 'Rose Forum'
Subject: (ROSE) Design Guidelines
Hello,
I've been changed with developing the Design Guidelines for our pilot
RUP/UML/Rose project. This is a RUP 'activity' that results in an
'artifact': Design Guidelines. Areas ('almost' directly from the RUP
template) are listed below. I say 'almost' because I added "4. User
Interface Guidelines" and "8. Modeling Conventions" to the topics listed
in
the template -- more then likely both these areas are documented in
another
RUP artifact but at this point I don't know what it is (if anyone knows,
please let me know).
Any input, experience, best practices you've discovered or 'words' of
wisdom
concerning any of the following areas would be greatly appreciated and
I'm
sure would help all member of this mailing list. Ideally 'most'
material
should be language and domain independent. References to any on-line
resources should be included. I am researching this from a broad range
of
resources (too many really). The outcome will also be, for better or
worse,
influenced by my own experience with UML, modeling, OOA&D, RUP and two
decades of development experience. I will post the final product, minus
any
proprietary material, and will furnish the URL when it is completed.
3. General Design and Implementation Guidelines
3.1 Mapping from Design to Implementation
3.2 Specifying Interfaces on Subsystems
3.3 Documenting Operations
3.4 Documenting Messages
3.5 Detecting, Handling and Reporting Faults
3.6 Memory Management
3.7 Software Distribution
3.8 How to Represent Reusable Components
3.9 Designing Persistent Classes
3.10 Fault Management
3.11 Transaction Management
3.12 Special Use of Language Features
3.13 Program Structure
3.14 Algorithm Guidelines
3.15 Hardware Interfacing
3.16 System Modification and Build Guidelines
3.17 System Diagnostic Guidelines
4. User Interface Guidelines
5. Database Design Guidelines
6. Architectural Design Guidelines
7. Mechanism Guidelines
8. Modeling Conventions
Thanks!
------------------------------------------------------------
Rusty Williamson
> Sr. Systems Architect
GERS Retail Systems
http://www.gers.com/
The Object Workshop
http://home.san.rr.com/williamson/
Home Page
http://www.znet.com/~rusty/
------------------------------------------------------------
************************************************************************
* Rose Forum is a public venue for ideas and discussions.
* For technical support, visit http://www.rational.com/support
*
* Admin.Subscription Requests: [EMAIL PROTECTED]
* Archive of messages:
http://www.rational.com/products/rose/usergroups/rose_forum.jtmpl
* Other Requests: [EMAIL PROTECTED]
*
* To unsubscribe from the list, please send email
*
* To: [EMAIL PROTECTED]
* Subject:<BLANK>
* Body: unsubscribe rose_forum
*
************************************************************************
*
************************************************************************
* Rose Forum is a public venue for ideas and discussions.
* For technical support, visit http://www.rational.com/support
*
* Admin.Subscription Requests: [EMAIL PROTECTED]
* Archive of messages:
http://www.rational.com/products/rose/usergroups/rose_forum.jtmpl
* Other Requests: [EMAIL PROTECTED]
*
* To unsubscribe from the list, please send email
*
* To: [EMAIL PROTECTED]
* Subject:<BLANK>
* Body: unsubscribe rose_forum
*
************************************************************************
*
************************************************************************
* Rose Forum is a public venue for ideas and discussions.
* For technical support, visit http://www.rational.com/support
*
* Admin.Subscription Requests: [EMAIL PROTECTED]
* Archive of messages:
http://www.rational.com/products/rose/usergroups/rose_forum.jtmpl
* Other Requests: [EMAIL PROTECTED]
*
* To unsubscribe from the list, please send email
*
* To: [EMAIL PROTECTED]
* Subject:<BLANK>
* Body: unsubscribe rose_forum
*
************************************************************************
*
