TASK ONE: Work Breakdown Structure NEW ACTIVITIES
Prepared by: Tony Prince Date: 1/11/2015 1.0 Project background Research 2.0 Project Scoping 3.0 Project Proposal Presentation 4.0 Test Past Algorithms 5.1 Test Function word Analysis 5.2 Test WRI 5.3 Test Trigram Markov 5.0 Developing Proposed Algorithms 6.4 Common N-Gram 6.5 Maximal Frequent ward sequence 6.0 Text Classifier 7.6 Dissimilarity Calculation 7.7 Support Vector Machine 7.8 Naïve Bayes 7.0 Testing and Evaluation 8.9 Entering Bugs to the System 8.10 Fault Injection 8.11 Results Analysis 8.0 Comparing Algorithms 9.12 Generating Differentiation Report 9.13 Generating Improvement Report 9.0 Apply to controversies 10.0 Beta In House Launch 11.14 In House User Testing 11.0 Alpha Launch

First of all, as we know that the main idea of a WBS (Work Breakdown Structure) is to maintain a proper hierarchy of events that are to be performed throughout the SDLC (Software Development Life Cycle). We have already created a WBS, and added the following Events that will further be assigned Durations and other details, First of all under the Testing and Evaluation four more activities are added, that includes, Entering Bugs to the System, Fault Injection, Results Analysis. Entering Bugs in the system is a way to analyze that our functionality is working fine, not only fine; it does not has any loose ends. The thing that I am referring to is that we will provide false inputs and check if the security checks applied are working or not. Similarly we will input right commands and check them as well. On purpose bugs are a way to ensure the system is working fine and does not has any false inputs. Furthermore, I have added Generating Differentiation