1 / 23

Project Report

PRD-13. Project Report. Software Engineering Courses Teaching Aided Website. Content. Team Introduction Project Performance Project Achievement Workspace Configuration Experiences. Team Introduction. Team Introduction--- Team Organization. Team Leader: Xin TAN Team Members: Azhu LIU

elani
Download Presentation

Project Report

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. PRD-13 Project Report Software Engineering Courses Teaching Aided Website

  2. Content • Team Introduction • Project Performance • Project Achievement • Workspace Configuration • Experiences

  3. Team Introduction

  4. Team Introduction--- Team Organization • Team Leader: Xin TAN • Team Members: Azhu LIU Shan WU Shengpeng LIU Sizhao SHANG Ting ZHANG Xinxin HUANG Yifan ZHAO

  5. Team Introduction--- Special Skills of Each mamber

  6. Project Performance

  7. Content • 1. Team Introduction • 2. Project Performance • 3. Project Achievement • 4. Workspace Configuration • 5. Experiences

  8. Project Performance • Weekly Meeting • Version Control • WBS & Milestones • Evaluation of Members

  9. Project Performance---Weekly Meeting Time: 2:00 pm every Saturday Place: Dormitory No. 30, Yuquan Campus Duration: 1-2 hours Participants: All team members Targets: 1. Conclude previous work 2. Solve untackled problem 3. Assign tasks in the following stage Other Methods for communication: QQ Discussion Group

  10. Project Performance---Version Control Not work! • iStudy BBS

  11. Project Performance---Version Control Our Choice! • SVN

  12. Project Performance---WBS & Milestones Using the software Microsoft Project 2010

  13. Project Performance---Evaluation of Members

  14. Project Achievement

  15. Project Achievement --- Milestone M 2 M5 M1 M3 M 4 Project Chapter & Project Plan 3.18 ~ 4.1 Requirement Engineering Plan 2.25 ~ 3.11 Project Feasibility Analysis 3.10 ~3.18 Modified Requirement Engineering Plan 3.11 ~4.7 SRS 4.11 ~ 5.12 M 6 M 8 M7 Modified SRS & System Design and Implementation 5.12 ~5.27 Software Requirement Change Control & Outline Design Specification 5.30 ~ 6.2 Project Summary Report & Presentation 6.3 ~6.9 M9 Test Plan & Project Deployment & Training Plan & System Maintenance Plan 5.27 ~ 6.16

  16. Project Achievement---Documents • Project Feasibility Analysis Report V0.1 • Project Charter V1.0 • Project Plan V0.5 • Project Vision and Scope V1.0 • Software Quality Assurance Plan • Change and Configuration Management Plan • Change Control Document V1.0 • Risk Management Plan • Requirement Engineering Plan V1.0 • M5.SRS V0.8, V1.0, V1.1 • System Design and Implementation Plan V1.0 • Software Outline Design Specification V1.0 • Training Plan V1.0 • Project Deploymeng Plan V1.0 • Test Plan V1.0

  17. Project Achievement---Website Prototype

  18. Project Crisis---Problems • Some of the documents were submitted after deadline. • Some of the documents were submitted with unfinished state. • The documents were of low quality. • Every member didn’t know what he should do and what others were doing. • Some of the members were always busy while others were unoccupied. • All the members didn’t know that our project was out of schedule.

  19. Project Crisis---Reasons • Misunderstanding of the two courses. • The work assignments are not clear and efficient. • “What to do” and “When to do” are not defined clearly. • Lack of communication. • Lack of consulting the teachers about the problems

  20. Project Crisis---Solutions • Send an e-mail to the teachers to illustrate the situation • Task-responsible system • More communication

  21. Experiences

  22. Experiences • Communication among the project team is important!!! • Get every body farily busy!!! • Make reasonable plan and update the plan periodically. • Set up a uniform format of the documents. • Pay attention to requirements of the users. • Choose proper software tools. (Rational Rose, AXURE RP, Project2007，SVN…) • There should be a reviewer of each document.

  23. END Thank you!!!

More Related