Carthik%20A.%20Sharma

1
PROJECT SECME
UCF
Software Engineering Fall 2002 Dr. Damla
Turguts Students

• Carthik A. Sharma
• Juan Carlos Vivanco
• Majid Ali Khan
• Santhosh Kumar Grandai
• http//www.geocities.com/secmep/

2
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
• Inculcate interest in engineering among minority
  students
• 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

3
Annual Competitions

• Multiple competitive events for students
• Annual event lasting 1-2 days
• 60 schools
• 1000 students
• 2 main organizers at MECSP

4
Saturday Workshops

• 3-5 workshops a year
• Aims
• Familiarize students with events in annual
  competition
• Talks on various aspects of technology

5
Users Needs

• System for Minority Program Coordinators to
  register their students for the events.
• System for the MECSP organizers to keep track of
  registration.

6
Present System

• Developed by Web Services , UCF
• Website hosted by CECS, UCF
• Database handled by WebCT team
• Uses ColdFusion
• Hastily Developed
• Insufficient

7
Problems with the System.

• Responses from the Client
• Not user friendly
• No provision to edit entries
• Poor data formatting
• Lack of flexibility
• Difficult to adapt maintain
• Poor support
• Having to manually re-enter data in spreadsheets
• Not secure

8
Proposed System - Users

• MECSP Organizers
• School Coordinators
• Minority program coordinators at Central Florida
  Schools
• 2 coordinators per school

9
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
• Email Notification

10
Operational Features

• MECSP user should be able to
• Define school coordinators
• Define workshops competition
• Retrieve data in a useful, friendly format
• Receive email notification/queries

11
Operational Features

• School coordinators should be able to
• Review information before submitting to MECSP
• Modify or Delete school registration records
• Post queries from the website
• View information about events on the website

12
Expected Improvements

• Ease of entry and retrieval of data
• Ease of management of events
• Security of data
• Increased efficiency

13
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

14
Operations

• Log-in and log-out
• Registration
• Modification
• Data retrieval
• Information updating
• Email messaging

15
Product Requirements

• Web server that can
• Run Tomcat 4.0
• Support Java, JSP , Java Beans
• Support MS Access
• The users should use IE 5.0 or higher
• Remarkably low financial requirements!!

16
Use Cases
17
Technology Used

• MS Access
• Java 2
• Java Server Pages
• Java Beans, Servlets
• Tomcat 4.0 server
• Desktops, servers at UCF

18
Project Management

• Overview of
• Team organization
• Process
• Project steps
• Project metrics

19
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

20
Development Process

• Fountain Software Development Model
• Requirements Phase (completed)
• Object Oriented Analysis Phase (completed)
• Object Oriented Design Phase (in progress)
• Implementation Phase
• Implementation and Integration Phase
• Maintenance
•  

21
Development Process Contd..

• Why Fountain Model?
• Supports incremental development
• Allows limited overlap between stages
• Best suited for development in object oriented
  paradigm

22
Schedule

• SRS 10/01/02
• Analysis of Use-Cases 10/15/02
• High-Level Design 10/22/02
• Detailed Design 10/22/02
• Test Plan 10/22/02
• Users Manual 11/19/02
• Final Test Results 11/19/02
• Source Code, Executables,
• and Build Instructions 11/19/02
• Project Legacy 11/19/02

23
PROJECT SECME
UCF
Software Engineering Fall 2002 Dr. Damla
Turguts Students
Thank You! ? Questions? ?

• Carthik A. Sharma
• Juan Carlos Vivanco
• Majid Ali Khan
• Santhosh Kumar Grandai
• http//www.geocities.com/secmep/