Top Banner
Project Report Software Engineering Courses Teaching Aided Website PRD-13
23

Project Report

Jan 21, 2016

Download

Documents

elani

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 - PowerPoint PPT Presentation
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Project Report

Project ReportSoftware Engineering Courses Teaching Aided Website

PRD-13

Page 2: Project Report

Page 2

Content

Team Introduction

Project Performance

Project Achievement

Workspace Configuration

Experiences

Page 3: Project Report

Page 3

TEAM INTRODUCTION

Page 4: Project Report

Page 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

Page 5: Project Report

Page 5

Team Introduction--- Special Skills of Each mamber

Name Special Skills

Xin TAN High-level programming skillStrong sense of leadership

Azhu LIU Good at writingStrong sense of responsibility

Shan WU Highly motivatedGood at writing

Shengpeng LIU Strict implementation capacityGood at understanding

Sizhao SHANG HardworkingGood at writing

Ting ZHANG Good at designingDo anything carefully

Xinxin HUANG High efficiencyStrong sense of responsibility

Yifan ZHAO Like programmingStrict implementation capacity

Page 6: Project Report

Page 6

PROJECT PERFORMANCE

Page 7: Project Report

Page 7

Content

1. Team Introduction

2. Project Performance

3. Project Achievement

4. Workspace Configuration

5. Experiences

Page 8: Project Report

Page 8

Project Performance

Weekly Meeting

Version Control

WBS & Milestones

Evaluation of Members

Page 9: Project Report

Page 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

Page 10: Project Report

Page 10

Project Performance---Version Control

iStudy BBS Not work!

Page 11: Project Report

Page 11

Project Performance---Version Control

SVN Our Choice!

Page 12: Project Report

Page 12

Project Performance---WBS & Milestones

Using the software Microsoft Project 2010

Page 13: Project Report

Page 13

Project Performance---Evaluation of Members

Page 14: Project Report

Page 14

PROJECT ACHIEVEMENT

Page 15: Project Report

Page 15

Project Achievement --- Milestone

Requirement Engineering Plan2.25 ~ 3.11

M 1

Project Feasibility Analysis3.10 ~3.18

M 2

Project Chapter & Project Plan3.18 ~ 4.1

M 3

Modified Requirement Engineering Plan3.11 ~4.7

M 4

SRS

4.11 ~ 5.12

M 5

M 7

Software Requirement Change Control & Outline Design Specification5.30 ~ 6.2

M 9

Test Plan &Project Deployment & Training Plan &System Maintenance Plan5.27 ~ 6.16

Project Summary Report & Presentation6.3 ~6.9

M 8

Modified SRS & System Design and Implementation5.12 ~5.27

M 6

Page 16: Project Report

Page 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

Page 17: Project Report

Page 17

Project Achievement---Website Prototype

Page 18: Project Report

Page 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.

Page 19: Project Report

Page 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

Page 20: Project Report

Page 20

Project Crisis---Solutions

Send an e-mail to the teachers to illustrate the situation

Task-responsible system

More communication

Page 21: Project Report

Page 21

EXPERIENCES

Page 22: Project Report

Page 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.

Page 23: Project Report

Page 23

END

THANK YOU!!!