>... 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
*
*************************************************************************
