Virtual Integration Process (VIP) facilitation of cross-domain collaboration
VIP development provides flexibility to link with multiple types of collaboration tools including software tools, architectural languages, domain analysis tools and open source tools. It emphasizes cross-domain collaboration improvements over a traditional document-based approach to system development.
The VIP provides protection of intellectual property at all levels of system hierarchy. It promotes configuration management throughout the integration process and provides industry-wide solutions with regulatory organization inputs from the earliest development stages.
Start integrated — Stay integrated
The VIP affords distributed inter-domain/inter-model consistency checks throughout development. Dependencies are defined early in the process. Verifications checks are run early and often. Inter-model inconsistencies are caught early when they are less costly to fix.
Dependency example
A design team, by simply increasing the system security confidentially requirement, spawns a cascade of changes:
- Encryption policy changes
- Bandwidth increases
- Power consumption increases
- Worst case execution time increases
- CPU utilization increases which again increases power consumption
The SAVI process recognizes these dependencies and prevents the myriad of resulting possible inconsistencies even though they may exist across multiple models and development environments.
Unique characteristics
Strong semantics make model sets analyzable.
Reliance upon models to link requirements and to build interface controls rather than impose them from documents.
Semantic sophistication simplifies quantitative and formal analysis and the architectural models generate specifications and interface control documents.