MSE Presentation 1 By Padmaja Havaldar- Graduate Student Under the guidance of Dr. Daniel Andresen – Major Advisor Dr. Scott Deloach-Committee Member Dr. William Hankley- Committee Member

Introduction Vision Document Project Overview Project Requirements Specification Project Plan Cost Estimation Gantt Chart of Project Plan Architecture Elaboration Plan Software Quality Assurance Plan Demonstration

Overview Objective: To develop a web-based Statistical Analysis tool based on the statistics alumni information. Four Types of analysis will be performed, namely, Regression analysis, correlation analysis, hypothesis test, Chi- Square test. Stake Holders: Department of Statistics, Kansas State University Padmaja Havaldar, Department of computing and information Science, Kansas state university Use: The department will use the analysis as research to help make decisions for future Statistics students

Overview Features: 1. The members will be able to register online with the help of a form provided for this purpose. They will be able to add, delete or modify the data provided. 2. The website will perform analysis based on the research question selected 3. Each research question will perform the appropriate analysis 4. The results will be displayed in the form of Graphs/Tables 5. A list of all alumni will be made available 6. A search for a particular alumni will be made available

Project Requirements Login Provides member authentication Input is verified by checking the existence of the member in the database Registration Registration of a non-member. Input is validated using client side as well as server side validation. The client side validation will include checks for missing information in the required fields. The server side validation will involve checking if the username entered is already used by a member in the database.

Requirements- contd Statistical Analysis A research question is selected to perform analysis like regression. Depending on the research question, the appropriate statistical analysis is performed with the help of the EJB which provides the middle layer in this three tier application. The analysis can be regression analysis, correlation, hypothesis test or the chi square test. The output will be a graph or table of the analysis results displayed on the web browser page

Requirements- contd Performance Requirements Since the application will be displaying graphs for the analysis, the response time for a particular analysis should not be greater than 3-4 seconds for a respectable internet connection speed. The database should be scalable; it must have the capacity to hold large number of users in future. Assuming that the department uses this website for the next 20 years, the number of users will probably not exceed Oracle is scalable enough to meet these requirements for the next 20 years.

Use Case

Requirements- contd The data for the analysis will be obtained from the database of users, so the response time for a query from the client side to the database side should not be more than 1 second. Error handling should be implemented and the application should be able to handle all run time errors. The application should be flexible for future enhancements, for example, the addition of a few more research analysis questions

Cost Estimation The Cost and size of the project is estimated using Function point analysis Cocomo model

Cost Estimation Function point analysis Total UFP = 110 Product Complexity Adjustment (PC) = (0.01 *46) = 1.11 Total Adjusted Function Points (FP) = UFP * PC = 122 Language Factor (LF) for Java assumed as = 38 Source Lines of Code (SLOC) = FP * LF = 4636

Cost Estimation COCOMO TDEVProgrammer Productivity Development Time (Month) Application Programs PM = 2.4 * (KDSI) 1.05 PM = 2.5 * (PM) 0.38 Utility ProgramsPM = 3.0 * (KDSI) 1.12 PM = 2.5 * (PM) 0.35 System ProgramsPM = 3.6 * (KDSI) 1.20 PM = 2.5 * (PM) 0.32

Project Plan Phase 1 – Requirements Deliverables : Overview, Requirement Specification, Cost Estimation, Software Quality Assurance Plan (SQAP) and a Project Plan First Presentation – June Phase 2 – Design Deliverables : Overall Design, Formal Specifications, Test Plan and a Formal Technical Inspection Second Presentation - July Phase 3 – Final Deliverables: Source Code, Tests, User Manual Final Presentation – August An Engineering notebook will be maintained at all times.

Project Plan Phase I Develop Overall RequirementsFri 3/14/03Thu 5/15/03 Learning project technologiesWed 4/30/03Tue 5/20/03 Develop Executable prototypeFri 5/9/03Mon 6/9/03 Develop software requirementsTue 6/3/03Tue 6/10/03 Develop Cost EstimateFri 6/6/03Mon 6/9/03 Develop software quality assurance planMon 6/9/03Thu 6/19/03 Develop Architecture Elaboration PlanMon 6/23/03Thu 6/26/03

Project Plan - contd Phase II Architecture DesignTue 7/1/03Fri 7/4/03 Formal SpecificationsSat 7/5/03Thu 7/10/03 Formal Specification InspectionWed 7/16/03Fri 7/18/03 Refine Vision documentFri 7/18/03Tue 7/22/03 Develop prototypeFri 7/25/03Mon 7/28/03 Prepare Presentation 2Tue 7/29/03Wed 7/30/03 Presentation 2Thu 7/31/03Thu 7/31/03

Project Plan-contd Phase III Implementing projectSat 8/9/03Thu 8/21/03 TestingSat 8/9/03Thu 8/28/03 Write User ManualFri 8/22/03Mon 8/25/03 Refine vision documentMon 8/25/03Tue 8/26/03 Refine project planTue 8/26/03Tue 8/26/03 Write project ReportThu 8/28/03Sat 8/30/03 Prepare Presentation 3Sat 8/30/03Sun 8/31/03 Presentation 3Mon 9/1/03Mon 9/1/03

Architecture Elaboration Plan Activities The documents presented during the phase I, which are the Software Requirement specification, Software Quality Assurance plan along with the changes will be documented. An updated time log will be documented. The vision document will be updated to ensure that the requirements specification have captured the driving requirements of the project. The updated version will be approved by the major advisor. Cost Estimation: The updated cost estimation will present the evaluated cost, size and effort for the statistical analysis tool. The revised version will be approved by the major advisor.

Architecture Elaboration Plan - contd The project plan will be updated taking into consideration any new milestones, corrected phases or iterations and deliverables along with the estimated completion date. The Implementation plan will define the activities and actions that must be accomplished during implementation. The plan will include a Work Breakdown Structure, with time and cost estimates and the completion criteria. The complete design of the project will be documented This will include class diagrams and object models along with any sequence or interaction diagrams. A section of the product’s design will be formally specified using OCL. A test Plan and Executable Architecture Prototype will be delivered A formal inspection by two MSE students will be conducted.

Software Quality Assurance Plan Resources Reference documents IEEE guide for software quality assurance planning Lecture notes, CIS 748 Software Management, Dr. Scott Deloach, Spring 2002 Software Development Environment Oracle Database is used as the database server Sun ONE Application Server 7 is used as a J2EE container which consists of EJB server and Web Server JDeveloper version serves as an IDE tool for EJB2.0 and web application Rational Rose tool is used for the UML model design USE is used for the formal OCL specification

Software Quality Assurance Plan Deliverables Vision document Project Plan Software quality Assurance (SQA Plan) Design artifacts User Manual Installation guide Test Report Java Source Code

Constraints Obtaining data from the alumni center Requirements from the Statistics department Learning curve to understand the methodologies and the Statistical tests

Demonstration