Typically engaged at the early stages of a project, ArchitecturePLUS is a one calendar-month service that at its end will put the customer in a position where product development can commence.

In a multi-core software development environment, performing this upfront work completely and accurately can be the difference between successful development projects and those who fail to achieve objectives. The following bundle of tasks are performed by Cavium architects as components of an ArchitecturePLUS effort:

• Requirements capture
• Detailed software architecture
• Performance analysis
• Memory analysis
• Risk analysis
• Testing strategy
• Project plan

• Time-to-Market
• Reduced development costs
• Risk mitigation

Cavium typically assigns one to two architects for the duration of the calendar month to perform the work. The larger CSS team further refines and reviews the developed architecture. As CSS performs numerous ArchitecturePLUS tasks per year, the resultant work is typically of optimum quality and accuracy. A 40 page document is developed and delivered capturing the result of the work performed.

Requirement Capture
Although customers have a clear idea as to their system requirements, they are often not clear how their requirements map to the OCTEON device. CSS architects meet for two full days at the customer’s site to fully understand their requirements. Doing so, enables them to quickly determine how each and every requirement can be satisfied. The OCTEON software level requirements will be captured in the delivered document.

Detailed Software Architecture
Over a two-week period, Cavium experts will develop and document a detailed software architecture that satisfies achievable customer requirements. As applicable, this work includes:

• Partitioning application across control and data plane divide.
• Identify control plane / data plane APIs
• Identification of system level interfaces
• Identification of the various software blocks
• Detail software block internals and APIs
• High level software diagram and packet flow description

Performance Analysis
Performance tends to the be the primary reason behind customer’s initiatives to adopt multi-core technology. Therefore, achieving desired performance may be as important as functional operation. For specific applications, Cavium readily offers performance numbers but those numbers may not correspond to customer specific performance metrics. Especially as you take into account …

• Customer specific applications and functions
• Combining multiple features into a single device
• Traffic mix and behavior of end customer deployment
• Clock speed and memory speed of a particular design
• Scalability of application while varying number of dedicated cores.

As part of architecture analysis, CSS will develop a model for the end application in order to estimate performance for customer identified performance metrics. Based on years of experience, proven methodology and numerous data points, CSS architectures can predict performance of a given application with remarkable accuracy. In addition, architects will map software modules into specific number of cores/core combinations in accordance with the developed architecture.

Customers can rest assured as to the accuracy of these performance predications as CSS would sign up to achieve those numbers in case it is selected for the implementation phase.

Memory Analysis
Achieving desired performance and scalable products depends on correct memory sizing. CSS architecture have developed a precise method of estimating correct memory sizing based on performance requirements and number of supported users in a given system. Having an accurate prediction of required memory, allows hardware designers and products managers the ability to plan the device capability early on in the project.

Risk Analysis
No project or technology development initiative is without risk. Clarifying items of higher risk from those of minimal risks early in the project can empower engineering managers and product managers to mitigate those risks as the product is developed and marketed.

CSS architecture will identify and document project and technology risks, assigns them importance and suggest mitigations strategies

Testing Strategy
CSS has learned that a well thought out testing strategy early in the project can ensure one time completion and enhance code reuse. CSS architecture will suggest a sound testing methodology appropriate for a customer’s particular initiative.

Project Plans
Complete project plans are developed as part of ArchitecturePLUS service. Project plans include:

• High level schedule with milestones
• Project flow and phase by phase description
• Required engineering resources
• Required equipment for development and acceptance testing
• Acceptance testing overview