|
I was between two minds about writing this post. After all, everyone knows that change control is important, don’t they? Then I remembered a couple of interesting cases where people did not seem to know that. In one case, a junior programmer had developed a very good rapport with one of […] In Step 4 we modelled the exception path when a leave request is rejected, but to complete our diagram, we need to take into account any SLAs. SLAs can be documented textually as part of your business rules catalogue, but how they impact your flow should appear on the diagram.
In Step 3 we continued our workflow by exploring the path where the leave request also requires the approval of the HR Department. Now we shall investigate the exception paths when the leave request is rejected. In this case, when the Requestor reviews the rejected leave request, he can choose to […] Have you heard the term “helicopter parent“? Well, I try not to be a “helicopter leader” (although I am sure I don’t always succeed). When mentoring a team of people, it can be tempting to do things for them if they aren’t getting things perfectly right, but that can distract you […] In Step 2 we continued our workflow by using connector shapes to show the flow between the different stages of the work. In this step we are going to model any alternate flows that still lead to an approved leave request (in this case, just one alternate flow). The business rule […] I'd like to personally say… I have just joined Slideshare and I received an automated welcome e-mail from “donotreply@slideshare.net”. The message said: Your SlideShare account is verified. And I’d like to personally welcome you to the World’s largest community for sharing presentations. It was “signed” by the CEO of Slideshare. Why do people […] I believe that when you hire a hound with a good pedigree and training, you ought to follow where it is going and not stop it so you can insist it explain why it uses one sniffing technique and not another. It seems to me that this is generally the case […] In Step 1 we started drawing our workflow based on what we knew from the high level statements of requirement in the project scope. The next step is to start connecting the dots, the dots being the functionality available to the users. As I said in another post, we […] In the world of systems development, “assumption” is kind of a dirty word, but sometimes it can be a good thing. Assumptions are only bad when they are not confirmed with the customer. However, as a business analyst, your job is to put your thinking cap on between interviews/workshops and you […] In the foreword, I suggested a definition of “workflow” and provided some high level statements of requirement which provided the scope of our leave request workflow. I also said that four of those statements could be investigated in the form of sub-processes, use cases or user stories. I have tried to comply to […] |