G2

Charlie H.

Systems Engineer

Mid-Market (51-1000 emp.)

8/4/2021

"Systems Engineering done well will be seamless & transparent to the software, mech & elec guys."

4/5

What do you like best about Rhapsody?

SE tools are required to keep a sense of order, version, control, consistency & visibility of the job in hand. The subject is wide & having a tool to help which is compatible with lower level tools is critical. Depending on the complexity & number of lower level sub-systems whether hardware, firmware or straight software will depend on the success of delivery, reviewability & most other 'ilities. The power of Rhapsody for object orientated design is key & one of it's strengths is it's ability to help the decomposition of the behavioural requirements for the top down design flow to software design, code & test. Review collected by and hosted on G2.com.

What do you dislike about Rhapsody?

Rhapsody has grown from a software design tool to a CASE tool. This is ok but clear that it leans towards OOD for coding rather than for the larger subject of SE. Review collected by and hosted on G2.com.

Recommendations to others considering Rhapsody:

Look for a tool that has the ability & flexibility to remain compatible with all of the other tools required to deliver decent solutions. Rhapsody has these qualities. Review collected by and hosted on G2.com.

What problems is Rhapsody solving and how is that benefiting you?

I have not used it for SE for nearly 5 years so I am not fully up to date with its later versions. We used it extensively for an SC job in missile design where dropping out the software design was done efficiently with it. It enabled rapid prototyping for system behaviour for algorithm design whilst being very fluent at flowing to the lower level coding & testing. It was easily compatible with the trace to the originating customer reqts in DOORS & its ability to perform code generation with the necessary complilers used was impressive. Review collected by and hosted on G2.com.