Wiki code for Architecture Review Process

Hide Line numbers
1: ==  Note: CLARC wiki with agenda and conference call details can be found [[here>>http://wiki.genunix.org/wiki/index.php/CLARC]]
2: 
3: = Solaris Cluster Architecture Review Process
4: 
5:  Sun uses the following process internally for projects going into the Solaris cluster product. The HA Clusters community will develop a process for projects going into Open HA Cluster, but until that process is in place we will use the Sun-internal process.
6: 
7: Most projects need only a CLARC review, but some projects require PSARC/LSARC reviews as well. The details follow.
8: 
9: == Cluster Architecture Review Committee (CLARC)
10: 
11: The Cluster Architecture Review Committee (CLARC) is responsible for overseeing the architecture of the Solaris Cluster product line. CLARC serves a role similar to the Architecture Review Committees (ARCs); however CLARC is chartered by the Solaris Cluster (SC) PAC, whereas the other ARCs are chartered by the System Architecture Council (SAC).
12: 
13: ===  What does CLARC review?
14: 
15: ** New software components added to the product. 
16: ** Changes to the functionality provided by a component that are visible to the clients of that component. Usually this is in the form of changed semantics or interfaces. 
17: ** Changes to multiple components. 
18: ** Significant design changes within a component, even if these are not visible outside the component. 
19: ** Changes to the interfaces imported by a component from other products. 
20: ** Deciding what projects get done. However, CLARC may reject projects that it feels do not fit into the architecture of the project. 
21: ** Management aspects of projects (e.g. resource requirements and allocation). 
22: 
23: ===  The CLARC review process
24: 
25:  Most of the CLARC processes have been borrowed from the SAC ARCs.  The purpose of an CLARC review is: 
26: 
27: * to ensure that a description of each engineering project exists, so that others in the group can understand what the project is. 
28: * to provide a consultation service with a group of senior engineers whose expertise is in the area of their project. 
29: * to identify any duplication of effort, over-engineering, quality problems, or dangerous effects on the strategic direction of the system architecture. 
30: 
31:  Review scope 
32: 
33: ===  I need a review - what do I do?
34: 
35: Don’t panic
36: 
37: OK, so someone told you that you can’t continue until your project has had a "CLARC Review".
38:  This section is designed to help you determine what this requirement really means to you and your project. 
39: 
40: This section explains the approach we use.  
41: 
42: The first question is usually "What kind of review do I need?" 
43: 
44: ==== FastTrack 
45: 
46: A FastTrack is a lightweight process for simple cases whose architectural impact is obvious and that are not likely to be controversial. A FastTrack is not intended for urgent cases: If a case needs urgent CLARC review, which should be rare, please send mail to ha-clusters-discuss@opensolaris.org .
47: 
48: =====  What you need to do:
49: 
50: Email ha-clusters-discuss@opensolaris.org to find a sponsor. The sponser will guide you through the process.
51: 
52: ==== Inception Review 
53: 
54: If you don’t qualify for FastTrack review, you will need to follow the full CLARC review process. The full CLARC review process involves a combination of email, detailed project specifications, and formal meetings. The time required varies considerably, but teams should schedule reviews early - an inception review by mid-prototype stage or earlier, with Commitment Reviews between alpha and beta in order to allow the iteam time to incorporate any CLARC-required changes before FCS. At the completion of the Commitment Review the project is approved by the committee. The approval of the project may be contingent on implementing some "Technical Changes Required" TCRs. 
55: 
56: Sometimes enough information is available at the time of the Inception Review for the project to be approved immediately without an additional round of commitment review. 
57: 
58: Changes are made to the project after approval may require additional review by CLARC. Depending on the magnitude of the change, this can be done as an addendum to the approved case, or as a separate case. 
59: 
60: What you need to do:
61: 
62: * Email ha-clusters-discuss@opensolaris.org to find a sponsor who will guide you through the process.
63: * Write a Requirements Specifications (ask your sponsor for the template) and ask your sponsor to submit it
64: * Attend the meeting. Your sponsor will give you details.
65: 
66: ==== Commitment Review 
67: 
68:  After the Inception Review comes the Commitment Review 
69: 
70: What you need to do:
71: 
72: * Write Design Document (ask your sponsor for a template) and ask your sponsor to submit it
73: * Attend the meeting. Your sponsor will give you details.
74: 
75: PSARC/LSARC
76: 
77:  Any project that changes the product’s interfaces to its customers should also go through PSARC or LSARC as appropriate. Minor interface changes can opt for a "self-review."
OpenSolaris

Top Menu

Wiki code for Architecture Review Process

Search

Collectives

Community Group

Project

User Group

Subsites

Community Group ha-clusters Pages
