Glossary FAQ
From Genunix
Contents |
ARC
Architecture Review Committee, a group of senior engineers who review the architecture of components for consistency with standards and interfaces.
Consolidation
The integration of software and/or documents specific to one area, such as kernel and networking or windows, prepared by a C-Team (or Consolidation Team) for delivery to a P-Team (or Product Team)
C-Team (or Consolidation Team)
The C-Team is responsible for integrating the components form I-Teams of a similar type (e.g., Desktop, Java, Admin...) into a consolidation and delivering it to the W-Team (or WOS Team) It is made up of representatives from the following departments: Development Engineering, Build Engineering, Test Engineering, and Technical Publications.
EOF
See also the SAC Obsolete and EOF processes. This is when a capability or component of a product is dropped, but the product continues to be delivered. Example: Drop support for a graphics feature delivered via a Solaris consolidation/component. EOF does not imply simultaneous end of service/support of that feature.
Family Vacation Model
This is a software development-and-release model in which software features, changes, and bug fixes are developed asynchronously and in parallel. The product is released when all of completion criteria for all of the compenents of the release are met. The analogy: families do not leave home without all of the children (software product deliverables) in the car.
FCS
FCS (First Customer Ship) is variously defined, depending on the functional area in question. Some common definitions are:
* Engineering: The date the product is handed off to Operations (also: RTM - Release to Manufacturing) * Operations: The date Operations releases the product as Finished Goods for shipment to customers * Customer Service: Date the first customer receives the produtc. * Availability of product for customer download via the Web
I-Team (or Implementation Team)
The I-Team designs, develops, documents, integrates, tests, and delivers software components to the C-Team or P-team. I-Teams are usually made up of people functioning as Development Engineering, Product Marketing, Technical Publications, and Test Engineering. An I-Team may consist of a single person in the case of a very small project.
Implementation Phase
The period of time in a software lifecycle during which a software product is created from design documentation and debugged. At the completion of this phase a Test Readiness Approval review is conducted to assure readiness for system test. Alpha system ready; features are complete and baseline frozen. Marketing reaffirms product viability and updates market projections.
Train Model
A software development-and-release model in which software features, changes, and bug fixes are developed asynchronously and in parallel. Those software changes that meet completion criteria (based on functionality, quality, and performance) are allowed into the release. Releases made on a regular schedule are the "trains."
P-Team (or Product Team)
The P-Team is responsible for a specific WOS release from the DEV selection and build through FCS-level production and shipment. It is made up of one or more representatives from at least the following: Engineering, Customer Service, Test, Product Marketing, Project Coordination, Release Engineering, Operations, and Technical Publications.
TCA
Technical Change Advised. Advice from the ARC to a project team that would make for a better project. As advice, it is not required that it be followed.
TCR
Technical Change Required. An ARC required change that must be made to the project's specifications in order for it to be approved.
WOS
The software and documents that comprise a complete software product (the Wad-of-Stuff). Commonly applied to the core of the Solaris Operating Environment, the OS/Net Consolidation.
