Go to main section
Require­ments Engin­eer­ing for the Auto­mot­ive Industry

Require­ments Engin­eer­ing for the Auto­mot­ive Industry

Ewa Kawińska Ewa Kawińska

Require­ments engin­eer­ing can be defined as a stage of soft­ware devel­op­ment life­cycle and as an area of soft­ware engin­eer­ing. The main under­stand­ing of “require­ments” is spe­cified as the descrip­tion of the func­tion­al­ity of soft­ware and its prop­er­ties (known as func­tion­al and non-func­tion­al requirements).

In last dec­ades the com­plex­ity of elec­tron­ic com­pon­ents in the auto­mot­ive industry increased rap­idly. This led to quick devel­op­ment of require­ments engin­eer­ing in elec­tric and elec­tron­ic sys­tem design, espe­cially in the high-end auto­mot­ive market.

In Codelab we under­stand that we need to con­sider more than our cus­tom­er­’s expect­a­tions. The soft­ware must meet stand­ards, norms, and oth­er reg­u­la­tions that increase the num­ber of require­ments. For doc­u­ment­a­tion pur­poses, our require­ments engin­eers map the stake­hold­er require­ments to ana­lysed sys­tem require­ments which reflect cus­tom­ers intern­al view of the sys­tem. Our res­ults of sys­tem require­ments ana­lys­is form the basis for the sys­tem qual­i­fic­a­tion tests and all down­stream processes.

Thank­fully to many years of exper­i­ence in cer­tain auto­mot­ive pro­jects, Codelab meets the chal­lenge to provide com­pet­ences to sup­port the man­age­ment of sys­tem require­ments for its cus­tom­ers. Our require­ments engin­eers are famil­i­ar with whole soft­ware devel­op­ment life­cycle, require­ments ana­lys­is pro­cess and domain know­ledge. The men­tioned com­pet­ences are proved by cer­ti­fic­ates gained by our employ­ees which makes Codelab a con­firmed sup­pli­er of sup­port for require­ments engin­eer­ing domain of soft­ware development.

To provide the best qual­ity and to meet stand­ards of deliv­ery for auto­mot­ive industry, Codelab ful­fils Auto­mot­ive SPICE® SYS.2 Pro­cess rel­ev­ant to Sys­tem Require­ments Ana­lys­is. We sys­tem­at­ic­ally improve exist­ing work­flows and meth­ods, we eval­u­ate the status of our pro­cess improve­ments through form­al assess­ments and gap analyses.

Sticky news

| Jan Tecker Siegel

Auto­mot­ive SPICE — a lux­ury or necessity?

Auto­mot­ive SPICE — a lux­ury or necessity?

The auto­mot­ive industry is get­ting more and more com­plex every day. All com­pan­ies, nev­er­the­less if OEMs or Tier­’s, are oper­at­ing in VUCA (Volat­ile, Uncer­tain, Com­plex and Ambigu­ous) world. The sys­tems that we build...

| Robert Rychcicki, Sebastian Wieczorek and Bartosz Hajdaś

Design Think­ing in R&D

Design Think­ing in R&D

When cre­at­ing new products or ser­vices, it is worth doing it based on a deep under­stand­ing of the prob­lems and needs of users. That’s the time where “Design Think­ing” should be used. In Codelab, we have used this approach while work­ing...