Intro to our Semester Software Engineering Project

One thing that you will often hear me say is that Software Engineers are often not good at things outside their field. Most people aren’t. But because we will often work with other fields, we need to be able to utilize a Subject Matter Expert (SME). That is someone who is an expert in the…

ERDs, or Entity Relationship Diagrams, are an important part of developing many software projects. They let us see how our data is related to itself, and other entities, so we know how to construct our data sources, such as a database. They are also good, because they can be shared among the development team, so…

No matter what type of system you build, it is important that we learn what the end user will actually need. Otherwise we risk building something that isn’t necessary and won’t be used by anyone. As we go through this process, we must identify who needs what, and does it really matter to the success…

In this video, I show how I picked what will go into version 1, or as we refer to it as our MVP, or Minimally Viable Product. Now, a version 1 of a software product is not necessarily an MVP. An MVP, or minimally viable product, is a simple product that is still usable. We…

Today’s users expect a well defined, and easy-to-use application. The days of a screen with a thousand items on it being standard are long gone. Now we’re trying to simplify, only showing what is necessary, and keeping things as clean as possible. Now that we know what will be in our application (by defining our…

Based upon the information gather from both requirements gathering and subject matter experts, we have start to identify what the software must do, who does what, and how it must do it. The formal process is to build a Use Case. This is a technical document that says who is doing what, how is it…