210 likes | 220 Views
EE ePortfolio. Presented by Team 3: David Schue Fred Pabon Stuart Ford Aydrian Howard Zach Bertram Zack Miller. Outline. Purpose Client’s requirements Our scope of project Process/Progress Milestones/Tasks Artifacts completed Lessons Learned What went wrong How to improve.
E N D
EE ePortfolio Presented by Team 3: David Schue Fred Pabon Stuart Ford Aydrian Howard Zach Bertram Zack Miller
Outline • Purpose • Client’s requirements • Our scope of project • Process/Progress • Milestones/Tasks • Artifacts completed • Lessons Learned • What went wrong • How to improve
Project Description • Proposal • Make new version of E-portfolio • Organization • RHIT Electrical and Computer Engineering Department • Clients • Dan Moore • Dave Voltmer • Sonny Kirtley
Problem • Dissatisfaction of current ePortfolio • Needed more functionality • Grading system • Managed by students and graders
Client’s 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
Previous Groups’ Progress • Last year’s group progress • Graduate student’s thesis document
Scope • Student/Grader web-based interaction • Students • Turn in files • Manage folders • Graders • View and grade homework • Submit grades
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.
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
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
Feasibility Report Config Mgmt Plan Requirements Doc UML Description Project Plan Website Database Layout Login control prototype Test Plan Progress Team 3 - Project Website
Progress • Development Environment • Delays with IAIT • Delays with CS department • Timeline of setbacks
Lessons Learned • Well organized client simplifies design process • Importance of IAIT support
Lessons Not Learned • Much of process was completed prior to our assignment to our project • Use Case Models • Process ideas
Risk ManagementLack of IT Support • Impact ~ high • Probability ~ low • Despite our initial estimate of low probability, this event still occurred
Risk Management & Mitigation • Decline project • Have alternate software solution • Have alternate project(s) to work on
Summary • Purpose • Progress • Process • Lessons learned