TEACHER FEEDBACK WEBSITE
-
Upload
sharon-snyder -
Category
Documents
-
view
16 -
download
1
description
Transcript of TEACHER FEEDBACK WEBSITE
TEACHER FEEDBACK WEBSITE
HTVN TEAM
DUY TAN UNIVERSITYINTERNATIONAL SCHOOL
AGENDA
1. TEAM INTRDUCTION
2. PROJECT OVERVIEW
3. PLAN
4. PRODUCT ARCHITECTURE
5. DATABASE DESIGN
6. TEST PLAN & TEST REPORT
7. REFLECTION
8. DEMO
9. QUESTIONS AND ANSWERS
HTVN TEAM
TEAM MEMBER
HTVN TEAM
Roles of team members
HTVN TEAM
Role Participant(s)Mentor Tam Thanh Thi Nguyen
Project Manager Hung Phi Cao
Programmer Nam Nhat NguyenThanh Thuy Thi Le
Tester Nam Nhat NguyenThanh Thuy Thi LeVu Xuan Nguyen
Reviewer Hung Phi Cao
Designer Hung Phi CaoNam Nhat NguyenThanh Thuy Thi LeVu Xuan Nguyen
Analyst Hung Phi CaoNam Nhat NguyenThanh Thuy Thi LeVu Xuan Nguyen
TEAM GOALS
• Learn XP process and follow XP.
• Learn how to write document.
• Learn what and how to communicate between
members.
HTVN TEAM
AGENDA
1. TEAM INTRDUCTION
2. PROJECT OVERVIEW
3. PLAN
4. PRODUCT ARCHITECTURE
5. DATABASE DESIGN
6. TEST PLAN & TEST REPORT
7. REFLECTION
8. DEMO
9. QUESTIONS AND ANSWERS
HTVN TEAM
PROJECT IDEAS
• Student do teacher feedback more easily.
• Teacher will change teaching method to suitable
for students.
• Students will benefit from the evaluation of
teachers.
HTVN TEAM
XP Process
HTVN TEAM
XP - The 12 Principles
1. Planning project.
2. Small releases.
3. Metaphor.
4. Simple design.
5. Testing.
6. Refactoring.
7. Pair programming.
8. Continuous integration.
9. Collective ownership.
10. On-site customer.
11. 40-hour weeks.
12. Coding standardsHTVN TEAM
AGENDA
1. TEAM INTRDUCTION
2. PROJECT OVERVIEW
3. PLAN
4. PRODUCT ARCHITECTURE
5. DATABASE DESIGN
6. TEST PLAN & TEST REPORT
7. REFLECTION
8. DEMO
9. QUESTIONS AND ANSWERS
HTVN TEAM
MILESTONES
HTVN TEAM
BURNDOWN CHART OF DEVELOPING RELEASE
Estimate Initiation Release 1 Release 2 Implemention0
20
40
60
80
100
120
ActualPerfect
HTVN TEAM
EFFORT EVALUATION
HTVN TEAM
25%
24%26%
24%
Effort evaluation of HTVN team
Hung Nam
Thanh Vu
AGENDA
1. TEAM INTRDUCTION
2. PROJECT OVERVIEW
3. PLAN
4. PRODUCT ARCHITECTURE
5. DATABASE DESIGN
6. TEST PLAN & TEST REPORT
7. REFLECTION
8. DEMO
9. QUESTIONS AND ANSWERS
HTVN TEAM
Architectural Drivers
HTVN TEAM
Architectural Drivers
Business constraints:
• Project begins from August 31th, 2012 to December
12th, 2012.
• The HTVN team has no budget for commercial software.
• Resource availability is defined below: 31/8 – 12/12, 4
members x 8 hours x 16 weeks.
HTVN TEAM
Architectural Drivers
Technical constraints:
• Technology: Microsoft Visual Studio 2012, Microsoft SQL
Server 2008.
• Network : Internet.
• OS: Windows XP/ Vista/ 7 / 8.
• Framework Tool: .NET framework 4.0+, ASP.NET, C#.
• Server hardware: Ram: Min 512M, HDD: Min 40GB, CPU:
Intel or AMD. HTVN TEAM
Architectural Drivers
Functional requirements:• Log in
• Log out
• Student do feedback
• Teacher view feedback
• Feedback management
• User management
• Class management HTVN TEAM
Architectural Drivers
Quality Attribute:
• Usability
• Performance
• Modifiability
• Scalability
• Security
• Availability
HTVN TEAM
System Context Diagram
HTVN TEAM
C&C VIEW
HTVN TEAM
MODULE VIEW
HTVN TEAM
ALLOCATION VIEW
HTVN TEAM
AGENDA
1. TEAM INTRDUCTION
2. PROJECT OVERVIEW
3. PLAN
4. PRODUCT ARCHITECTURE
5. DATABASE DESIGN
6. TEST PLAN & TEST REPORT
7. REFLECTION
8. DEMO
9. QUESTIONS AND ANSWERS
HTVN TEAM
Figure : Entity relationship diagram of TFWFigure : Entity relationship diagram of TFW
DATABASE DESIGN
HTVN TEAM
AGENDA
1. TEAM INTRDUCTION
2. PROJECT OVERVIEW
3. PLAN
4. PRODUCT ARCHITECTURE
5. DATABASE DESIGN
6. TEST PLAN & TEST REPORT
7. REFLECTION
8. DEMO
9. QUESTIONS AND ANSWERS
HTVN TEAM
TEST TYPES
• Unit testing
• Function testing
• Integration testing
• Regression testing
• Acceptance testing
HTVN TEAM
TEST LIST
HTVN TEAM
TEST REPORT
HTVN TEAM
AGENDA
1. TEAM INTRDUCTION
2. PROJECT OVERVIEW
3. PLAN
4. PRODUCT ARCHITECTURE
5. DATABASE DESIGN
6. TEST PLAN & TEST REPORT
7. REFLECTION
8. DEMO
9. QUESTIONS AND ANSWERS
HTVN TEAM
Reflection 1
What we did well?• Identifying task was helpful for focusing the followed XP process.• Analyzing, designing and coding are made simultaneously.• Writing technical documents.• Understanding how to workgroup together.
HTVN TEAM
Reflection 2
What we did well?• Meeting with mentor to figure out problems and how to solve
the problems.• Initially, effort for unplanned tasks was not tracked. Now,
planning is more accurate.• Complete the project on schedule.
HTVN TEAM
Reflection 3
What we didn’t well?• Spent more time than plan.• Need rule for process assessments.• Lacked of an on-site customer (as desired by XP) because
customer was busy.• Initially, got trouble in XP process, sometimes mistake with other
processes.
HTVN TEAM
Reflection 4
What we didn’t well?• We have not analyzed the relevancy of performed tasks at the end
of sprints.• Need to make more metrics visible.• Project was behind schedule but was then recovery.
HTVN TEAM
Reflection 5
Positives• Adequate understanding of business drivers and System
Architecture. • Better understanding what is XP and how to apply XP in a real
environment.• Understanding the role of a mentor who has an influence on
guiding & coaching students.
HTVN TEAM
Reflection 6
Positives• Independent work help us to promote the full potential of each
member.• Change thinking, and know how an actual software engineer
must do, what actual skills?
HTVN TEAM
Reflection 7
Negatives• Workload balance among teams were not even.• Get trouble in write technical documents.• During do Capstone, we work and study simultaneously so time
is not ensure.• Spend a lot of time learning XP process.• Sometimes conflict between members.
HTVN TEAM
AGENDA
1. TEAM INTRDUCTION
2. PROJECT OVERVIEW
3. PLAN
4. PRODUCT ARCHITECTURE
5. DATABASE DESIGN
6. TEST PLAN & TEST REPORT
7. REFLECTION
8. DEMO
9. QUESTIONS AND ANSWERS
HTVN TEAM
DEMO
THANK YOU!
HTVN TEAM
QUESTION &
ANSWER