This paper outlines the modeling process in SysML (Systems Modeling Language) in context of MBSE (Model Based Software Engineering) as well as the MBD (Model-Based Design) in Simulink and we compare the models to get useful information into software. For this goal, we propose the use of an RM/SM tool (Requirements Management and Systems Modeling) (3SL Cradle) and Matlab/Simulink to model the system, do the system validations, and finally embed the generated code.For automotive systems, the development process is visualized through the V-Model, which leads to the right choice of components, the integration of the system and the project realization. The first step in V-Model handles the requirements management for the development, i.e., the requirements for a project will be collected in respect to the stakeholder’s needs and system limitations. Then, the next steps consist of modeling the system based on its requirements, going through simulation, system validation through Model-In-the-Loop (MIL), Software-In-the-Loop (SIL), Processor-In-the-Loop (PIL), and Hardware-In-the-Loop (HIL) tests. For this paper, the chosen modeling language was SysML for the MBSE point of view because it aims to standardize Modeling Design, by unifying diverse modeling languages used by engineers. This language also supports specification, analysis, design, verification, and validation of systems. To get executable models, we use Matlab/Simulink models that are largely used by the Original Equipment Manufacturers (OEMs) to develop new products.Our approach addresses the V-Model through SysML and MBD in Matlab/Simulink towards software validation. To achieve that, we use the commercial RM/SM tool that is used to collect stakeholder’s and system requirements. It provides a SysML design section as well where SysML models can be developed according to project requirements. One of the objectives in using the commercial tool is that it will be possible to analyze the transition from models in RM/SM tools to models for simulation, such as Simulink and offer a new possibility for OEM’s and suppliers to abstract system models into executable models. The main contribution of this paper is that the automotive software development process is showed from its concept to its realization in real systems.