SOF 535 Chocoholics Anonymous Report Te
Chocoholics Anonymous
Team Protégé
Thomas P. Vande Zande
Padma Rilapur
Sravani Tadimeti
Tenaaz Aqthari Syed Muneer
Stratford University SOF 535
Professor Butu
December 6, 2014
Abstract *Enter abstract here*
Chocoholics Anonymous
While assessing the needs of the Chocoholics Anonymous organization our team agreed unanimously that we wanted to gain the most value out of this project. We first sat down and decided our approach for how to handle this project in the most professional and business simulating way possible. During this sit down we agreed to treat this project like a real business venture. For that we would use a hybrid approach that consisted of some project management techniques as well as agile software engineering techniques. For this project we would need a finished result that can be used by developers to accomplish the tasks with very little questions.
To accomplish the project in the manner we set forward we needed to achieve a fine-grained set of requirements and specifications during multiple sessions of business and software analysis. This means we need to have all the items needed for development figured out and all assumptions handled ahead of development as a result of these sessions. We managed to set up mock actual sessions of requirements gathering like that of a actual business analysts. During these sessions we would go back and forth with problems from the project and come up with viable solutions and answers to these problems, documenting them as we proceeded. Then came the user interface, for this we put together ideas about what we would like to see in the user interface and how customers would interact with it. Next we considered the development process and how the structure and layout of classes and other items should and could look. For this we created diagrams to assist development efforts such as the collaboration diagrams and class diagrams. We decided on collaboration diagrams versus sequence diagrams in the
Team Protégé
Thomas P. Vande Zande
Padma Rilapur
Sravani Tadimeti
Tenaaz Aqthari Syed Muneer
Stratford University SOF 535
Professor Butu
December 6, 2014
Abstract *Enter abstract here*
Chocoholics Anonymous
While assessing the needs of the Chocoholics Anonymous organization our team agreed unanimously that we wanted to gain the most value out of this project. We first sat down and decided our approach for how to handle this project in the most professional and business simulating way possible. During this sit down we agreed to treat this project like a real business venture. For that we would use a hybrid approach that consisted of some project management techniques as well as agile software engineering techniques. For this project we would need a finished result that can be used by developers to accomplish the tasks with very little questions.
To accomplish the project in the manner we set forward we needed to achieve a fine-grained set of requirements and specifications during multiple sessions of business and software analysis. This means we need to have all the items needed for development figured out and all assumptions handled ahead of development as a result of these sessions. We managed to set up mock actual sessions of requirements gathering like that of a actual business analysts. During these sessions we would go back and forth with problems from the project and come up with viable solutions and answers to these problems, documenting them as we proceeded. Then came the user interface, for this we put together ideas about what we would like to see in the user interface and how customers would interact with it. Next we considered the development process and how the structure and layout of classes and other items should and could look. For this we created diagrams to assist development efforts such as the collaboration diagrams and class diagrams. We decided on collaboration diagrams versus sequence diagrams in the
References: Flow Chart Maker / Visio Online. (n.d.). Retrieved December 7, 2014, from https://www.draw.io/#LUntitled Diagram Fadeyev, D. (2009, April 15). 8 Characteristics Of Successful User Interfaces. Retrieved December 5, 2014, from http://usabilitypost.com/2009/04/15/8-characteristics-of-successful-user-interfaces/ Schach, S. (2011). Object-oriented and classical software engineering(8th ed.)). New York: McGraw-Hill Sehlhorst, S. (2007). How to Write Good Use Case Names – 7 Tips. Retrieved December 6, 2014, from http://tynerblain.com/blog/2007/01/22/how-to-write-good-use-case-names/