PROJECT SECME1 Carthik A. Sharma Juan Carlos Vivanco Majid Ali Khan Santhosh Kumar Grandai Software Engineering Fall 2002 Dr. Damla Turgut’s Students UCF

PROJECT SECME2 Definition: The M.E.C.S.P. at UCF is responsible for conducting the following on behalf of SECME Inc. : A) Annual Competitions B) Saturday Workshops Aims 1.Inculcate interest in engineering among minority students 2.Attract high school students to colleges, including UCF. M.E.C.S.P – Minority Engineering and Computer Science Program SECME – Previously an acronym for South Eastern Consortium for Minorities in Engineering

PROJECT SECME3 Annual Competitions Multiple competitive events for students Annual event lasting 1-2 days ~60 schools ~1000 students 2 main organizers at MECSP

PROJECT SECME4 Saturday Workshops 3-5 workshops a year Aims 1.Familiarize students with events in annual competition 2.Talks on various aspects of technology

PROJECT SECME5 Users & Needs: System for Minority Program Coordinators to register their students for the events. System for the MECSP organizers to keep track of registration.

PROJECT SECME6 Present System Developed by Web Services, UCF Website hosted by CECS, UCF Database handled by WebCT team Uses ColdFusion Hastily Developed Insufficient

PROJECT SECME7 Problems with the System. Responses from the Client… 1.Not user friendly 2.No provision to edit entries 3.Poor data formatting 4.Lack of flexibility 5.Difficult to adapt & maintain 6.Poor support 7.Having to manually re-enter data in spreadsheets 8.Not secure

PROJECT SECME8 Proposed System - Users MECSP Organizers School Coordinators: 1.Minority program coordinators at Central Florida Schools 2.2 coordinators per school

PROJECT SECME9 Proposed System - Needs Secure password protected log-in log-out Users can View/Add/Modify relevant information Data available in required format to the MECSP user Notification

PROJECT SECME10 Operational Features MECSP user should be able to 1.Define school coordinators 2.Define workshops & competition 3.Retrieve data in a useful, friendly format 4.Receive notification/queries

PROJECT SECME11 Operational Features School coordinators should be able to : 1.Review information before submitting to MECSP 2.Modify or Delete school registration records 3.Post queries from the website 4.View information about events on the website

PROJECT SECME12 Expected Improvements Ease of entry and retrieval of data Ease of management of events Security of data Increased efficiency

PROJECT SECME13 Analysis Disadvantages - Completely Web – Based Limitations - Future maintenance not available - Dynamic manipulation of data formats not envisaged Risks - UCF public server system may crash at a critical time Alternatives - Existing system - Manual system

PROJECT SECME14 Operations Log-in and log-out Registration Modification Data retrieval Information updating messaging

PROJECT SECME15 Product Requirements Web server that can 1.Run Tomcat Support Java, JSP, Java Beans 3.Support MS Access The users should use IE 5.0 or higher Remarkably low financial requirements!!

PROJECT SECME16 Use Cases

PROJECT SECME17 Technology Used MS Access Java 2 Java Server Pages Java Beans, Servlets Tomcat 4.0 server Desktops, servers at UCF

PROJECT SECME18 Project Management Overview of Team organization Process Project steps Project metrics

PROJECT SECME19 Team Organization Small democratic team with a figurehead leader 1) All members have a say. 2) Each member has equal responsibility in creating, reviewing all artifacts. 3)Active and frequent ( 2-3 times a week) discussions Team Leader/Representative Carthik – 1. Coordinate efforts 2. Interface with Dr.Turgut 3. Maintain website, documentation

PROJECT SECME20 Development Process Fountain Software Development Model 1.Requirements Phase (completed) 2.Object Oriented Analysis Phase (completed) 3.Object Oriented Design Phase (in progress) 4.Implementation Phase 5.Implementation and Integration Phase 6.Maintenance

PROJECT SECME21 Development Process Contd.. Why Fountain Model? 1.Supports incremental development 2.Allows limited overlap between stages 3.Best suited for development in object oriented paradigm

PROJECT SECME22 Schedule SRS 10/01/02 * Analysis of Use-Cases 10/15/02 * High-Level Design10/22/02 Detailed Design 10/22/02 Test Plan 10/22/02 User’s Manual 11/19/02 Final Test Results 11/19/02 Source Code, Executables, and Build Instructions 11/19/02 Project Legacy 11/19/02

PROJECT SECME23 PROJECT SECME Carthik A. Sharma Juan Carlos Vivanco Majid Ali Khan Santhosh Kumar Grandai Software Engineering Fall 2002 Dr. Damla Turgut’s Students UCF Thank You! Questions?