Episode Details
Back to EpisodesForgotten, But Not Gone: How Model-Based Development Is Still Alive and Well Today
Description
00:00
Welcome to the Oracle University Podcast, the first stop on your cloud journey. During this series of informative podcasts, we'll bring you foundational training on the most popular Oracle technologies. Let's get started.
00:26 Nikita: Hello and welcome to the Oracle University Podcast! I'm Nikita Abraham, Principal Technical Editor with Oracle University, and joining me is Lois Houston, Director of Innovation Programs. Lois: Hi there! In our last episode, we looked at Oracle's Redwood design system and how it helps create world-class apps and user experiences. Today, Joe Greenwald, our Senior Principal OCI Instructor, is back on our podcast. We're going to focus on where model-based development tools came from: their start as CASE tools, how they morphed into today's model-based development tools, and how these tools are currently used in Oracle software development to make developers' lives better. 01:08
Nikita: That's right. It's funny how things that fell out of favor years ago come back and are used to support our app development efforts today. Hi Joe! Joe: Haha! Hi Niki. Hi Lois.
01:18
Lois: Joe, how did you get started with CASE tools? Joe: I was first introduced to computer-aided software engineering tools, called CASE tools, in the late 1980s when I began working with them at Arthur Young consulting and then Knowledgeware corporation in Atlanta, helping customers improve and even automate their software development efforts using structured analysis and design techniques, which were popular and in high use at that time. But it was a pain to have to draw diagrams by hand, redraw them as specifications changed, and then try to maintain them to represent the changes in understanding what we were getting from our analysis and design phase work. CASE tools were used to help us draw the pictures as well as enforce rules and provide a repository so we could share what we were creating with other developers.
I was immediately attracted to the idea of using diagrams and graphical images to represent requirements for computer systems. <