Development Diary.docx

looneyvillestaticSoftware and s/w Development

Aug 15, 2012 (5 years and 2 months ago)

280 views

Development Diary

Author:
Joseph Kearney

Team
:
20


Week

1

Work:




Set up facebook page Added other group members
.



W
e set up our groups github account/aceproject account/gmail account
.
I then familiarised
myself with th
e different sites and software.



Using

the user requirements w
e each went off and gathered,
w
e then refined them and
added them to

make a user requirements list.



Group has changed bug tracking to fogbugz

so I

f
amiliarised myself with website.


Problems:



Not being familiar with the different
sites was challenging at first as I wasn’t aware of the full
functionality of the sites.



Not knowing everyone on the team made it hard

to criticize their work.

Solutions:



Constantly

using the websites made it easier
to understand their functionality.



I go
t used to voicing my ideas

by voicing them
.




Week

2

Work:



Started using netbeans IDE.



Set up my laptop to connect to github repository to share code with my group.



Looked at database design ideas.



Prepared my speech and slides for the group
presentation.

Problems:



Had to merge all our files together, left it a bit late we we're rushing a small bit.



Not sure as to how to approach the designing

of the database

and what it entails.

Solutions:



We provisioned more time for activities where we
would have to join our work together.



We got a relational database making lecture which helped.



Week 3

Work:



Dataflow diagram

sketched out and then made in G
liffy
(Online drawing software)
.



Showed to group so the coders had a visual representation of
som
e of the user
requirements.



Completed database schema and implem
ented database with Victor and D
onnchadh.

Problems:

None

Solutions:


None



Week 4

Work:



Made a use case diagram and show

to team so we know a bit more
what the users expect
form their
system.



Looked up different types of tests and testing that can be done on the system.



Found a good website with all different types of tests.


Problems:



Not sure what types of tests to do or how long the tests will take.

Solutions:



Researched the differen
t tests and their specifics.



Week 5

Work:



Made help page with different FAQs and answers
.



Coded it into a jsp page. Merged it with the system.



Started creating test bible.



Checked cross browser co
mpatibility for project so far.

Working on chrome v17
.0/Firefox
v10.0/safari v5.1.2/
Not working in IE 6
.


Problems:



Just some problems getting the .jsp page working and remembering what syntax to use.

Solutions:



Looking up the error codes online for solutions. And asking my team mates for help.





Week 6

Wo
rk:



Started commenting

the

code

making sure everything is javadoc’d


Problems:



Its hard to get used to looking at other peoples code and understanding straight away what
they’re trying to do.

Solutions:



More looking at other people’s code will improve my
understanding.