Friday June 03, 2005 Sometimes a picture is worth more than a page of blog text. This diagram illustrates my prior posting about basic architectural definitions and their relationships.
| |
| Legend (Click on image to see a larger version) | |
|---|---|
| Workspaces | Sun uses Teamware to manage much of its source code. The Teamware term Workspace is used to describe a copy of a source tree that contains its version control history; Teamware can manage the relationships and content flow between workspaces. |
| I-Teams | Implementation Teams (aka developers) |
| RE | Release Engineering |
| Realizations | Instances of a product in specific forms |
| PLC Phase 3 | The first three phases of Sun's Product Life Cycle are "Propose a Concept", "Commit to a Plan" and "Develop a Product". The reference indicates that (duh!) product development happens in the development phase. Yes, there are some people that need to be told the obvious .
|
| « November 2009 | ||||||
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
|---|---|---|---|---|---|---|
1 | 2 | 3 | 4 | 5 | 6 | 7 |
8 | 9 | 10 | 11 | 12 | 13 | 14 |
15 | 16 | 17 | 18 | 19 | 20 | 21 |
22 | 23 | 24 | 25 | 26 | 27 | 28 |
29 | 30 | |||||
| Today | ||||||
I've been at Sun since 1989, and have been involved in many different projects - from porting SYSV to x386 systems and involvement with the early BSD/Libux efforts, bringup of Solaris 2.0 and porting the X/NeWS Window System and the OpenLook Desktop, to database clusters, systems management, yadda yadda yadda :-)
For the last 5 years or so, I've been the keeper of Sun's proactive architectural processes and the tools used by its various review committees.
Today's Page Hits: 10