Get documents about "Time_log_template
Document Sample
Time Recording Log Instructions
Purpose
This form is for recording time spent on individual programming assignments.
General
Time is recorded in minutes, using a 24-hr clock. You may round to the nearest five minutes.
Keep a supply of blank forms handy so you will have one whenever you are working.
Complete the form in your neatest handwriting. Do not maintain the form electronically unless you obtain sp
Header
Enter your name and the name of the assignment or module you are working on.
LOC Start
If you are beginning work on new development, enter zero. If you are resuming work on existing developme
LOC End
When you are finished development of the module, determine the LOC and enter that number here. It’s reco
Date
Enter the date when the entry is made. (If subsequent entries are made on the same day, you may leave the fi
Start
Enter the time when you start working on a programming phase.
Example: 7:43
Stop
Enter the time when you stop working on that phase.
Example: 8:24
Interrupt
Time Record any interruption time that was not spent on the task. Write the reason for the interruption in the "Com
Example: 5+2
Delta Time
Enter the clock time you spent on the task, less the interrupt time.
Example calculation: From 7:43 to 8:24, less 7 minutes or 34 minutes, so record 34.
Comments
Enter any other pertinent comments that might later remind you of any details or specifics regarding this acti
C (Complete)
Check this colum when you complete a task
U (Unit)
The number of unit task when you complete it
cally unless you obtain special permission from the instructor.
k on existing development, modifying or enhancing existing code, determine the LOC that already exists and enter that number h
at number here. It’s recommended that you use the LOC counting tool.
day, you may leave the field blank). Example: 10/24
interruption in the "Comment" column. If you have several interruptions, record them with plus signs (to remind you to total th
ecifics regarding this activity.
dy exists and enter that number here.
signs (to remind you to total them).
Time Recording Log For: ….. Project
Name: Date:
Week Date Start Stop Interruption Delta Activity
Time Time
11-Jun 5:00 PM 6:00 PM 0 1 Kick off Team
meeting
1 12-Jun 9:00 PM 11:00 PM 0 2 Read references
13-Jun 9:00 PM 11:00 PM 0 2 Read references
14-Jun 9:00 PM 11:00 PM 0 2 Analyze
requirement
15-Jun 9:00 PM 11:00 PM 0 2 Team Review
2 16-Jun 3.5 PM 5:00 PM 0 1.5 Meeting with
mentor
17-Jun 9:00 PM 12:00 PM 0 3 Analyze
Requirement
18-Jun 9:00 PM 12:00 PM 0 3 Document
19-Jun 9:00 PM 12:00 PM 0 3 Document
20-Jun 9:00 PM 11:00 PM 0 2 Team review
21-Jun 3:00 PM 5:00 PM 0 2 Meeting with
mentor
22-Jun 11:00 PM 12:00 PM 0 1 Review
23-Jun 12:00 AM 2:00 AM 0 2 Document
9:00 PM 11:00 PM 0 2 Team Review
Assign works
24-Jun 3:00 PM 6:00 PM 0 3 Study MySQL and
Netbeans
8:00 PM 11:00 PM 0 3
25-Jun 8:00 PM 11:00 PM 0 3 Study MySQL and
Netbeans
26-Jun 6:00 AM 8:00 AM 0 2 Java course
1:00 PM 3:00 PM 0 2 Update
10:00 PM 12:00 PM 0 2 Update
27-Jun 9:00 PM 11:00 PM 0 2 Team Review
12:00 PM 13 PM 0 1 Update
28-Jun 1:00 PM 2:00 PM 0 1 Review & Update
4 9:00 PM 11:00 PM 0 2 Update
29-Jun O AM 2:00 AM 0 2 Add
6:00 AM 7:00 AM 0 1 Update
8.5 AM 10.5 AM 0 2 Add
10:00 PM 12:00 PM 0 2 Review
30-Jun 10:00 PM 12:00 PM 0 2 Coding in Java
1-Jul 10:00 PM 12:00 PM 0 2 Coding in Java
2-Jul 10:00 PM 12:00 PM 0 2 Coding in Java
3-Jul 10:00 PM 12:00 PM 0 2 Coding in Java
4-Jul 9:00 AM 11:00 AM 0 2 Coding in Java
5-Jul 9:00 PM 11:00 PM 0 2 Team review
5
6-Jul 5:00 PM 7:00 PM 0 2 Restore drive C
9:00 PM 11:00 PM 0 2 Coding in Java
AND input data in
Database Jukebox
to test
7-Jul 5:00 PM 7:00 PM 0 2 Coding
8-Jul 9:00 PM 10:00 PM 0 1 Coding
10:00 PM 11:00 PM 0 1 Document
4:00 PM 5:00 PM 0 1 Review with
mentor
9-Jul 3:00 PM 5:00 PM 0 2 Interface (GUI)
10-Jul 8:00 PM 11:00 PM 0 3 Update Document
11-Jul 7:00 AM 10:00 AM 0 3 Update Document
12:00 PM 2:00 PM 0 2 Coding
12-Jul 8:00 PM 11:00 PM 0 3 Update
13-Jul 6:00 AM 9:00 AM 0 3 Update
6
9:00 PM 11:00 PM 0 2 Team review
14-Jul 11:00 AM 12:00 AM 0 1 Review
15-Jul 2:00 PM 3:00 PM 0 1 Review
3.5PM 5:00 PM 0 1.5 Meeting with
mentor
11:00 PM 12:00 PM 0 1 Document
16-Jul 8:00 PM 11:00 PM 0 3 Document
17-Jul 8:00 AM 12:00 AM 1 3 Document
18-Jul 8:00 PM 10:00 PM 0 2 Reading
19-Jul 8:00 PM 10:00 PM 0 2 Reading
20-Jul 10:00 AM 12:00 AM 0 2 Coding Review
9:00 PM 11:00 PM 0 2 Team Review
7 21-Jul 9:00 PM 11:00 PM 0 2 Reading
22-Jul 8:00 AM 12:00 AM 1 3 Document
23-Jul 9:00 AM 10:00 AM 0 2 Document
24-Jul
25-Jul
26-Jul 9:00 PM 11:00 PM 0 2 Team Review
8 26-Jul 10:00 AM 11:00 AM 0 1 Document
28-Jul 4:00 PM 5:00 PM 0 1 Meeting with
mentor
29-Jul 2:00 PM 5:00 PM 0 3 Reading reference
30-Jul 1:00 AM 3:00 AM 0 2 Document
31-Jul 8:00 AM 12:00 AM 0 4 Testing
1-Aug
2-Jul
3-Jul
4-Jul
9 5-Jul
6-Jul
7-Jul
8-Jul COME BACK VIET NAM
Project
Artifact Comments C U
Use case diagram
Master Plan V 1.1
Use case diagram
Master Plan V 1.1 Missing Schedule
Use case diagram
Use case diagram
Architecture driver 1.0
Architecture driver 1.0
Initial Project Schedule
Architecture driver 1.0
Architecture driver 1.0
Initial Project Schedule
Architecture driver 1.0
Requirement spec 1.5
Initial Architecture 4
Design 1.0
Requirement spec 2.0
Architecture design 1.0
assigned to member
Install & configure
Connect to MySQL
Arch. Design V 1.0 1
Arch. Design V 1.0 1
Test Plan
Arch. Design V1.1 6
Arch. Design V1.1 3
Arch. Design V1.2 6
Master Plan 1.3
Arch. Design V1.2 6
Arch. Design V1.3 1
Arch. Design V1.3 1
Arch. Design V1.3 4
Arch. Design V1.3 12
Connect to Database 1
MYSQL “Jukebox”
Create form to display 1
data from Jukebox
Database
Update form to input user 1
data (Datetime style…)
Create stored procedure 1
for Jukebox database
Call and execute stored 1
procedure from Java form
Screen UI
Physical Database
Master Plan
Test Plan
Testing data in Database
and Prototype of List
Statistic (UI and control)
Prototype Configure
volume (UI and control)
Prototype Adjust volume
UI
Architecture Design 1.3
Architecture Design 1.3 Missing:
-Design rationale according with
Quality attributes
- Style of connectors in C&C view
packets
Test plan, project plan Missing: test plan, risk management,
estimate….
Should change the project Difficult to manage this kind of
type project
Architecture & Design
Document 2.0
Architecture & Design
Document 2.0
Configure clients Volume
control(UI and Control)
Adjust Clients Volume
(UI and control)
List statistic (UI and
control)
Adjust Volume
Architecture & Design
Document 2.0
Architecture & Design 4
Document 2.0
Architecture & Design
Document 2.0
Class diagram Continue to complete by Nam and
Duy
Testing Plan Continue to complete by Nhung
Master Plan Continue to complete by Viet
Class Diagram Continue to complete by Duy
Class Diagram
Test Plan, Test cases 1.0 Should improve in detail
Master Plan 3.0
Architecture & Design
Document 2.0
Requirement Traceability
Matrix 1.1
Configuration Initial draft
Management 1.0
Class diagram 1.2
Class diagram 1.3
Java course
Java course
Class diagram Duy and Name continue to complete
Java course
Architecture & Design
Document 2.3
Architecture & Design
Document 2.3
Architecture & Design
Document 2.4
Test cases
Architecture & Design
Document 2.5
Architecture & Design Require to complete rationale for
Document 2.5 Design
Architecture & Design
Document 2.6
System Test (Admin
functions)
E BACK VIET NAM
SUMMARY: TIME FOR DOING PROJECT
WORKS/ARTIFACTS HOURS
Plan and Schedule 9.0
Architecture drivers 21.5
Architecture & Design 47.0
Class diagram and Database 23.0
Coding 27.0
TOTAL 127.5
ON AVERAGE (hours/week) 15.9
