Software Requirements Blog

This month I had an interview with this company called Accenture and basically is a consultant company. So everything I learn from this class can be applied to that company. why? When you need talk to a customer who wants to create an application, you need to do software requirements and by that you need to do all what I learn here from: - listing stakeholders - domain research - domain questionnaires - domain prescription units - domain concepts - domain theories But how did I benefit from that, in that company Accenture they do a case interview where you need to talk with a hypothetical customer who want to do an application, and you are a consultant. The interview problem is to see how you resolve and come with a plan to resolve the customer need and the best way of doing that, or thinking about a solution is by software requirements.

It is really important to do distinction between Verification and Validation. Verification is mostly verifying that your implementation is following the requirements that the software team made by doing domain acquisition and talking to the domain experts. Validation in the other hand, is when you go to the Domain Expert and show them the product and they approve that is right or wrong. Obviously that is a really general description, but it is essentially that. The funny story is, that most people would think that something as simple as that is not useful in real life. But for me, and many other, in some interviews with some companies, they ask about that and it is really useful.