GfSE
Viewpoints for framework developers
We don't have viewpoints for framework developers. Having them would make SAF development easier, especially for developers new to SAF development.
We should consider also Stakeholders planning an MBSE approach with SAF or consider using SAF. The idea somehow similar to the architecture foundation in NAF
What to do:
- define additional Stakeholders The following are new, referenced by development documentation use cases
- define concerns and rationales
- define viewpoints formally (matching already established diagram kinds)
- possibly define a separate domain for this.
From Theory to Practice: V Model, IVVQ, and MBSE in Action—Start Your Own MBSE Pilot Projects: The Key to Developing Practical Knowledge, https://www.norasi-team.com/vmodel-ivvq-and-mbse-in-action/
Architecture Contributors An Architecture Contributor provides expertise, contributes to architectural design and development efforts, collaborates with the architecture team, and ensures the delivery of high-quality architectural solutions within their assigned areas. The Responsibility, Authority, and Accountability (RAA) list for an Architecture Contributor includes: Responsibility:
- Design and Development: Contributing to the architectural design and development process.
- Expertise: Providing input and expertise on specific architectural domains or components.
- Collaboration: Collaborating with the Lead Systems Architect and other stakeholders to understand architectural requirements.
- Research: Conducting research and analysis to identify appropriate architectural solutions.
- Documentation: Developing architectural models, diagrams, and documentation.
- Reviews: Participating in architecture reviews and providing constructive feedback.
- Implementation: Implementing architectural decisions and guidelines within their assigned areas.
- Integration: Collaborating with other team members to ensure architectural alignment and integration.
- Learning: Staying updated with emerging technologies and industry trends related to their specific domain.
- Improvement: Continuously improving their architectural knowledge and skills.[ Model Based Engineering Organizational Roles Responsibility Authority and Accountability.pdf ](url)
https://www.linkedin.com/posts/gabelandrew_mbe-raa-ugcPost-7216884395218022400-9_W5?utm_source=share&utm_medium=member_ios Enhancing Model-Based Engineering Through Effective Team Structure:
As the field of systems engineering shifts from traditional methods to digital engineering, it's crucial to consider what changes are necessary for success. I've noticed that digital engineering is beginning to adopt principles akin to software engineering, which prompts us to rethink team structures for effective implementation of Model-Based Engineering (MBE).
Throughout my career in MBSE, I've identified key roles that are essential not just for MBSE teams, but for any digital engineering initiative. Digital engineering is about creating a dynamic database of interconnected information that speeds up data retrieval compared to traditional paper-based methods.
This approach to team structure is designed specifically for digital engineering teams. We're in an era where software practices have already set a precedent. Instead of starting from scratch, let's leverage the lessons learned from software engineering and integrate them proactively into these new digital engineering teams.