EE ePortfolio

1
EE ePortfolio

• Presented by Team 3
• David Schue
• Fred Pabon
• Stuart Ford
• Aydrian Howard
• Zach Bertram
• Zack Miller

2
Outline

• Purpose
• Clients requirements
• Our scope of project
• Process/Progress
• Milestones/Tasks
• Artifacts completed
• Lessons Learned
• What went wrong
• How to improve

3
Project Description

• Proposal
• Make new version of E-portfolio
• Organization
• RHIT Electrical and Computer Engineering
  Department
• Clients
• Dan Moore
• Dave Voltmer
• Sonny Kirtley

4
Problem

• Dissatisfaction of current ePortfolio
• Needed more functionality
• Grading system
• Managed by students and graders

5
Clients Requirements

• ECE Department
• User friendly
• Web-based application
• Turn-in directory for students
• Capability for graders to grade submitted
  homework
• Kerberos username/password system
• IAIT
• Oracle database
• Perl or PHP language

6
Previous Groups Progress

• Last years group progress
• Graduate students thesis document

7
Scope

• Student/Grader web-based interaction
• Students
• Turn in files
• Manage folders
• Graders
• View and grade homework
• Submit grades

8
Grader UML
9
Student UML
10
Process

• Meet with client and gather project description
  and requirements.
• Obtain materials needed (development platform)
• Develop requirements document, feasibility
  report, and UML descriptions
• Planning Project plan, configuration management
  plan, and test plan.

11
Project Plan

• Project plan needed to contain all milestones as
  well as estimated times.
• Used Microsoft Project to generate the project
  plan
• Project plan updated dynamically if certain tasks
  took longer than expected
• Project Plan website

12
Project Milestones

• Project webpage creation
• Project plan, initial version
• Feasibility report
• Configuration management plan
• Requirements document
• Use cases document
• Program prototype
• Test plan
• User interface prototype
• Presentation

13
Project Plan
14
Progress

• Feasibility Report
• Config Mgmt Plan
• Requirements Doc
• UML Description
• Project Plan

• Website
• Database Layout
• Login control prototype
• Test Plan

Team 3 - Project Website
15
Progress

• Development Environment
• Delays with IAIT
• Delays with CS department
• Timeline of setbacks

16
(No Transcript)
17
Lessons Learned

• Well organized client simplifies design process
• Importance of IAIT support

18
Lessons Not Learned

• Much of process was completed prior to our
  assignment to our project
• Use Case Models
• Process ideas

19
Risk ManagementLack of IT Support

• Impact high

• Probability low

• Despite our initial estimate of low
  probability, this event still occurred

20
Risk Management Mitigation

• Decline project

• Have alternate software solution

• Have alternate project(s) to work on

21
Summary

• Purpose
• Progress
• Process
• Lessons learned