Systems Engineering

Systems Engineering

Competence Center:

Systems engineering considers the entire development process and ensures seamless integration of all disciplines involved. It begins with a systematic clarification and analysis of the requirements. The functionalities, dependencies and interfaces derived from this are mapped in a logical system architecture. The system is broken down into subsystems down to electrical/electronic hardware, software components and services, specified and modelled in the physical system architecture to obtain an overall view of the system. This serves as the basis for implementation, verification and validation across all levels and is continuously monitored until handover to the customer. These activities are independent of the chosen project methodology and can be used from classic to agile or a combination thereof.

Services

CC - Team

AI (Artificial Intelligence) Konzept, Mikrochip, Geschäftsmann halten Glühbirnen und berühren AI-Infografik, Zahnräder-Icons, kreative Idee, AI-Technologie, Quantencomputer, Cloud-Computing, Automation.

How do I keep track of a complex overall system?

- Include key requirements.
- Make it clear to all stakeholders how and where the product functions will be implemented.
- Coordinate mechanics, electronics, firmware, software and even cloud.
- Define the integration steps and consider the testability of the subsystems early on.
- Be able to quickly recognise the effects of design changes
- Integrate late adjustments easily and implement them without surprises.

Die Worte Software, Hardware, Update und Upgrade sind, aus Holzklötzen gemacht, ausgelegt. Wie plane ich die Neuentwicklung meines Produkts?

How do I plan the new development of my product?

- The current status is analysed and, if necessary
described and modelled, if necessary
- The requirements for the new product are
are recorded
- The system context and the interaction with the
environment/ecosystem is described
- The system architecture is developed, the
the new functions are mapped to components
and the processes are defined or revised
- "Old vs. new" overview is developed,
Focus points identified and
Reusability analysed

Digitales Transformationskonzept mit Puzzle. Zwei Hände halten je ein Puzzelteil, welche wie Bestandteile einer Platine gestaltet sind. Komplexität. Berücksichtigen. Teillastenhefte. Zusammenfügen.

How do I take product complexity into account in partial specifications?

- Requirements, system context, functions, interfaces must be clearly defined.
- Scope of delivery, acceptance criteria, schedule and intermediate phases must be taken into account.
- The specific requirements specification must be coordinated with the overall system and the own development department.
- The component must be fully and compatibly integrable at the end.
- An experienced liaison should be able to control and check the development.

Ein Mann arbeitet an einem Laptop und daneben sind mehrere elektrische Komponenten angeschlossen (Platine). Komponenten. Angaben. Entwicklung. Anleitung.

Do I have all the necessary information to develop a component?

- Requirements, system context, functions,
interfaces are checked for completeness
checked
- The architecture of the solution is worked out and
clearly shows what is part of the system and what is not.
not
- The requirements specification will describe the solution approach,
constraints, scope of delivery, plan and
verifiability.

Konzept der Differenzierungsstrategie. Die Unternehmen entwickeln sich, indem sie Einzigartigkeit bieten, die sich von den Wettbewerbern unterscheidet und Wettbewerbsvorteile schafft. Differenzierung von Produkt, Service und Marke. Erfolg. Produktidee. Wie erfolgreich machen?

Is my product idea promising?

Market analysis and business case must be made
What functions would my product need to have in order to be successful in the market?
Product or product line should be anchored in the product portfolio
A "Go/No-Go" decision is made
Product definition and main use cases are defined
Product feature / advantage / benefit analysis should be carried out

Agile Management, die Prinzipien agiler Softwareentwicklung und schlankes Management für verschiedene Management-Prozesse, Produktentwicklung Lifecycle und Projektmanagement. Änderungsorientiertes Konzept. Entwicklungsprozesse kombinieren.

How can I combine classic and agile development processes?

The process mix between classic and agile is defined and adapted to the needs of the company.
"Backlogs", "User Stories", "Acceptance Criteria", "Definition of Done" are understood and practised.
Roles and their tasks and responsibilities are defined
"Product managers, product owners, project managers and scrum masters know exactly how to work with the rest of the organisation.
Several teams work together on the architecture and coordinate the design.
Integration of the different system parts can be planned and executed despite agile methods.

Dienstleistungen

Our Services

Business and user requirements

We help them clarify and align business and user requirements to develop a solution that meets the needs of the organisation and its users.

Market analysis

We help you to better understand the competitive environment, your target audience and potential customers.

Feature / Advantage / Benefit Analysis

We identify which functions and features are most important to provide the greatest benefit to your customers.

Business Case

We develop an objective decision-making basis for the implementation of a project.

Requirements & use cases

We elicit, consolidate, document and validate the system requirements in an iterative process with all necessary stakeholders.
In doing so, we take into account all possible use cases and the non
functional requirements.

Product definition & variability

We define the main features and functions of the solution and identify the necessary
the necessary product variability.

Requirements specification & functional specification

We develop the requirements and functional specifications and agree them with all parties involved.

Architecture definition

We define and model the system architecture (system boundaries,
components, dependencies, activities, functions, interfaces).

We use functional and structural views to ensure that the overall
architecture remains consistent.

Architecture review

We analyse the correspondence between the requirements and the
system architecture.

We align the design of the individual system components (mechanics, electronics,
firmware, software, cloud) with the higher-level architecture and look for
look for possible weaknesses in the system architecture.

System integration and testability

We define the links between requirements, architecture,
implementation and tests. We use these as a basis for the
impact analysis.

Product Line Engineering (PLE)

We define platforms, components, implementation variants and the
configuration management to support the entire product line.

Coordination of agile development

We define and maintain all necessary agile artefacts: Product Backlogs, User
Stories, Acceptance Criteria, Definition of Done. We take over for you the
Product Owner, Product Manager or Scrum Master role.

CC-Team

The Team

"Our Systems Engineering Competence Centre offers comprehensive support in the seamless integration of all disciplines in the development process of complex overall systems. We are proud to support our customers with our extensive know-how and many years of experience in the implementation of their projects."

Silviu Rata
Chief CC Systems Engineering
systems-engineering@cross-ING.ch