The workshop on software development methodology was conducted as part of our curriculum at SCIT.The aim of the workshop was to get the hands on experience of latest software development methodology with small small teams working on small projects.We as MBA SDM students, will be working as Project Managers or Business Analysts or Software Architects in the industry, so understanding of latest development methodologies, the dos and don'ts of these methodologies etc is very important for us to understand . Though all the work carried out during the workshop was far from real scenario in the industry( I m not sure about this) but still it initiated a thought process in us about the development methodologies.
In the beginning of the workshop all teams had to select a product or project as their start up plan. After selecting the "start up", teams needed to work on their project/product using either Agile or RUP development methodology. My team(Dhurva, Rachna, Kshitiz, Roshan, Sandeep) selected Visitor Management System as our start up product and decided to develop it using RUP methodology. We christened our start up as VMS Solutions.
We conceived this start up by sensing the growing need of security systems. The increasing terrorism has made companies to look for more robust and powerful security systems which can keep a close eye on the visitors at their premises.Therefore, we at VMS Solutions proposed to provide a Visitor Management System which can help the companies to store and track the details of visitors at their premises.
On the day I of workshop we executed inception and elaboration phases of RUP methodology. The outcome of these two phases were design artifacts like sequene diagrams, use cases, class diagrams, test plan for unit and functional testing, project plan with time and cost estimates. These things make strong foundation for next phase of RUP i.e. Construction phase.
During the elaboration phase, we also did extensive risk planning. One best thing I like(& found) about RUP is that it calls for early risk planning and solves them early so that they don't become nightmares for the project team in future as the system grows. In our case, there were so many risks which were unidentified.The risk planning involved extensive brainstorming and during this, several times we went "off tangent" from our project scope; but eventually we were able to come back to our main goal after rigourous debates and talks within the group.With our Mentor cum customer - Mr. Parag Shah's guidance(he provided us feedback on our project by wearing customer shoes) we were able to properly identify the risks involved. The risks that were identified were business as well as technical risks hence the system became more robust from technology as well as business perspective. The system is now able to sustain any future requirement from technical as well as business perspective.
During my internship, my project was also exectued using RUP methodology but during that I was not involved in any business risk planning, as a trainee software developer all I could do was look for any technical risks involved. Here in this workshop I was able to see business risks also(though they were very few but were very important!!!).
The design of the Visitor Management System underwent a drastic change after risk planning phase. Thank God we didn't do any coding by this time :-). Now I think that we have done proper thinking and planning to take our the system to next phase of development that is construction phase. This phase will be carried out on the second day of workshop i.e.on 2nd Jaunary 2009 till then Happy New Year :)!!!!
In the beginning of the workshop all teams had to select a product or project as their start up plan. After selecting the "start up", teams needed to work on their project/product using either Agile or RUP development methodology. My team(Dhurva, Rachna, Kshitiz, Roshan, Sandeep) selected Visitor Management System as our start up product and decided to develop it using RUP methodology. We christened our start up as VMS Solutions.
We conceived this start up by sensing the growing need of security systems. The increasing terrorism has made companies to look for more robust and powerful security systems which can keep a close eye on the visitors at their premises.Therefore, we at VMS Solutions proposed to provide a Visitor Management System which can help the companies to store and track the details of visitors at their premises.
On the day I of workshop we executed inception and elaboration phases of RUP methodology. The outcome of these two phases were design artifacts like sequene diagrams, use cases, class diagrams, test plan for unit and functional testing, project plan with time and cost estimates. These things make strong foundation for next phase of RUP i.e. Construction phase.
During the elaboration phase, we also did extensive risk planning. One best thing I like(& found) about RUP is that it calls for early risk planning and solves them early so that they don't become nightmares for the project team in future as the system grows. In our case, there were so many risks which were unidentified.The risk planning involved extensive brainstorming and during this, several times we went "off tangent" from our project scope; but eventually we were able to come back to our main goal after rigourous debates and talks within the group.With our Mentor cum customer - Mr. Parag Shah's guidance(he provided us feedback on our project by wearing customer shoes) we were able to properly identify the risks involved. The risks that were identified were business as well as technical risks hence the system became more robust from technology as well as business perspective. The system is now able to sustain any future requirement from technical as well as business perspective.
During my internship, my project was also exectued using RUP methodology but during that I was not involved in any business risk planning, as a trainee software developer all I could do was look for any technical risks involved. Here in this workshop I was able to see business risks also(though they were very few but were very important!!!).
The design of the Visitor Management System underwent a drastic change after risk planning phase. Thank God we didn't do any coding by this time :-). Now I think that we have done proper thinking and planning to take our the system to next phase of development that is construction phase. This phase will be carried out on the second day of workshop i.e.on 2nd Jaunary 2009 till then Happy New Year :)!!!!
4 comments:
I do agree with dhruva as i was also a part of this team.I have one more point to make that RUP allows you to accommodate new requirements at later stage as before construction phase you can review the design in the previous two stages.This kind of practical exercise improved our thought process and thus enabled us to think about the system with different perspectives..
Nice explanation of the whole lecture and our project.
Though VMS, we had a hands on that what happens with the development team when customer requirements change but thanks to RUP methodology which enable us to tackle the change easily by making our class diagram more robust.
Let see what happen next with our VMS in next class :).
Excellemt dhruva...that was a good blog..you have really mixed the experience from your workshop with other experiences very well. Also the idea of VMS as a idea or product is excellent. I am sure parag sir would have given you exact idea for a product like VMS. I liked the flow of the blog..and i will congratulate you for not making it boring. so i will wait for next blog
Hmm, Good post even though it is out of my area, I could understand what you must have done in the workshop.Good attempt to make it understand a layman of computer language like me.......he...he.... good gandumal :)
Post a Comment