SECME Project

1
SECME Project

• Vamsiravali Kaza
• Naveen K. Pinnama Reddy
• Harish Ramakrishnan
• Yu "Andy" Wu

2
SECME

• The SECME (Science Engineering Communications
  Mathematics Enrichment) program was established
  in 1975 by the Deans of Engineering from six
  Southeastern Universities.
• SECME is a pre-college program that focuses on
  the preparation and motivation of students who
  will follow an engineering or technical career

3
Project Overview

• The purpose of this project is to create a
  database designed to track a student through the
  Central Florida SECME Program.
• It will also catalogue teachers, school systems,
  and school performance. It will also provide a
  facility for MECSP to input and edit information.

4
Current System, If Any

• SECME does not have a computer-based system to
  keep track of students in the program. Everything
  for this purpose is paper-based.
• The schools usually fax demographic data on
  students, progress, and schools to SECME. Most of
  the faxes are handwritten, although some of them
  are printed Excel spreadsheets.
• The SECME staff maintains these faxed copies in
  file folders.

5
Proposed System

• Windows-based
• Access backend
• Control of Access
• Administrator
• Regular User
• Restricted user

6
Requirements

• User-friendly GUI Very Important
• Users lack technical knowledge
• Users want familiar Windows GUI
• System login
• Password protected
• Flexibility of queries
• Users shall run queries based on tasks
• All queries relatively straightforward and simple
  ?

7
Queries

• Students
• Demographic, longitudinal (courses, SAT )
• Teachers
• Contact info
• Involvement (Courses taught and year)
• Schools
• Contact info
• Counties
• Listing of participating schools

8
Use Case Diagram

9
Standards

• Coding Standards
• Visual Basic.NET
• Access XP
• OS Windows 2000

10
Standards

• Software Life Cycle Model
• Waterfall
• Team Organization
• Democratic Approach

11
Testing

• Testing is done through out the project
• The functionality of the system is as per the
  clients requirements.
• The software produced is robust and is of good
  quality.
• The software runs as expected in the clients
  business environment
• Test cases are drawn as per the specifications

12
Problems Risks

• Problems Faced
• Meeting
• Scope creep
• Desktop versus Web-based
• Risks Involved
• Time limitation
• Lot of documentation