Software Requirements Blog

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.

I learn that one way of creating a solution for a potential project or client is: Do Domain Acquisition by doing domain research, talking with domain experts, doing questionnaires. Then after having all that information you need to create a project definition. One of the ways I learn to do a project definition is by doing an Informative Documents that contains: Name of the project, place of execution and date, the need of the application, the idea of what the project going to do, the concepts and assumption you are making in order to complete the project, decencies and some goals. You can go and do some listening of requirements stakeholders: the people involve in these requirements that you going to do next. After having the stakeholders is good to group them by groups. Then you create the Requirements prescription units: that involves creating the requirement statement, the group of stakeholder involve in the requirement, and the concepts type and facet involve in it. Then a