Diagrams

Something that is really good to express how requirements are applied into designing a project is by creating diagrams. Here are some of the diagrams I learn from the software requirements class, that I think are really useful for any software project:

• Problem diagram: Better for expressing interaction between system scope like context and problems.

• Entity relationship diagram: Better for modeling a database but basically for conceptual structures.

• SADT diagrams with actigram and datagram: When it comes to activities like input and output, and how the environment can affect those values.

• Event Trace diagram: Interaction between all the scenarios that can be in your program.

• State Machine diagram: For system behavior such as how the program operates and all the possible outcomes.