Organizer: A new Start up Project

Software Development Methodologies Workshop as a part of our curriculum is being conducted and it surely began a chain of thought process since the start of the session. Be it regarding RUP Vs Agile or RUP with Agile, which one fits the best and where etc... Now, in the last session we (my team: Prerna, Manpreet, Rahul, Pawan and Harkul) took up a new start up project of developing an for an organization to define roles, responsibilities, expertise, current projects etc. of each employee within a hierarchy. Organizer helps in allocating tasks to employees according to their expertise or skill set. We decided to follow RUP methodology, in which Inception and Elaboration phases are complete. Thinking process initiates when I started thinking of what can be taken up as a project start up. Then head on to deciding it with my team and the work begins. We started with developing a business case and based on that we completed with the inception phase. While the critical high risks use cases and sequence diagrams were reviewed by Mr. Parag Shah, a concern stuck in our way, whether or not to show failure cases in sequence diagrams or not. Because there can be so many failure cases that our one sequence diagram can be swamped with and whole motive of drawing the diagrams is all in vain. So, we decided to make it more clear, hence our next exercise will be to show diagrams with and without failure cases and see how much time can be saved or how to identify which failure situations if not considered can turn into a high risk later on. So, stay tuned for the results..