You have just entered room "Chat 23200920213520806925."
illinimarshke has entered the room.
illinimarshke: hey
illinimarshke: whats up?
starkiller76: not much
starkiller76: I guess we will wait a few minutes until the rest show up
starkiller76: I posted a new RUP project plan on the WIKI
illinimarshke: ok
illinimarshke: do you know wehn we get our exams back?
illinimarshke: thats why they should make everything scantron
Eceguru has entered the room.
kabev1 has entered the room.
starkiller76: I am kind of anxious to me score back too
Eceguru: hi
Eceguru: i wonder why its taken them so long to get the grades
illinimarshke: the cs dept is notoriously slow
Eceguru: yeah
illinimarshke: but these classes aren't cheap, i expect some good service
x V DoGG x has left the room.
Abhi327 has entered the room.
x V DoGG x has left the room.
Abhi327: hello everyone
starkiller76: Just wanted to let you guys know I posted a new project plan on WIKI
x V DoGG x has entered the room.
x V DoGG x: I apologize in advance if i get disconnected. I am connected over packet data while a co-worker is driving back to chicago from purdue at 120 km/hr
starkiller76: Let me know if you have any comments on it, I will change and add to it as we go
kabev1: Hey everyone, I was unable to do the CVS stuff since I was on vacation last week, I'll get it done asap
starkiller76: ok
x V DoGG x: cool.... should we throw together an adhoc agenda?
x V DoGG x: 1. Assign any remaining roles....
Eceguru: ok
Abhi327: guys i'll email you the information for our project set up on sourceforge after the meeting.
kabev1: I am finally looking at the summary, and it looks like we accomplished a lot of good things last week
starkiller76: 2. We need to assign modules, and a start prototyping
x V DoGG x: yes i agree
x V DoGG x: after looking at the criteeria
Abhi327: Also need to look at the criteria
x V DoGG x: it is heavily weighted on the implementation
Abhi327: for grading as vivek mentioned
starkiller76: has everyone looked at the criteria posted on wiki?
kabev1: no
kabev1: But I'll catch up this week
x V DoGG x: yes
illinimarshke: yeah
Eceguru: i looked at it a bit
Eceguru: not too indepth
starkiller76: According to the criteria our implemention will be a prototype developed in the elaboration phase
Abhi327: Our T.A Howard is aware that we've switched to RUP.
Abhi327: i've looked at it briefly over the weekend
x V DoGG x: i am wondering how far along other groups are....
starkiller76: OK, what roles still need to be assigned
Abhi327: For the roles part: everyone should write up a paragraph or two as we move along as to what we've contributed individually. That should help us put together a document at the end of the semester highlighting the roles performed
starkiller76: Good idea
x V DoGG x: abhi - hmmm, i am not sure i get that
Eceguru: should we have someone be focused on testing
x V DoGG x: just a little confused, should we write up things like "coordination" and such just for documentation purposes
starkiller76: Yes
Eceguru: to fulfill the Continously Verify Software Quality component
Eceguru: i can do it
starkiller76: you got it
illinimarshke: i can document, thats what i do all day at work
starkiller76: We only need to write down what artifacts we worked to create (ie. code, documents, visual diagrams, etc)
starkiller76: In our personal paragraph I mean
Eceguru: any other roles we need?
starkiller76: do we have a CM
Abhi327: did we decide on testing. ?
Abhi327: i thought kabe was our CM
Eceguru: kabe is CM
kabev1: yup I am the CM
starkiller76: Isaac said he would be tester
x V DoGG x: oh ok, so you are talking about documentation about things we will be doing in the future (coding, testing, etc...) or the past?
Abhi327: are we saying all the developers will be testers as well
illinimarshke: no i meant creating the design doc, req. doc, testing plan, etc
starkiller76: both
illinimarshke: developers should unit test
illinimarshke: but you should have a separate system tester
Eceguru: i'll come up with functional tests and ways to automate
starkiller76: cool
Eceguru: and other testing related things as i think of them
Abhi327: i agree with kevin. We shouldn't have one person assigned to testing. rather make every developer do unit testing.
Abhi327: cool.
Eceguru: everyone will do testing
starkiller76: for units
Eceguru: but i'll concentrate on the system tests
Eceguru: yeah, for unit tests everyone will do it
Abhi327: sounds good.
starkiller76: good
Abhi327: perfect.
Eceguru: i'll also come up with a short form to use for tracking bugs
illinimarshke: does sourceforge have a defect tracker?
Abhi327: yes it does
Eceguru: we can use that then
Abhi327: sure
Eceguru: but i'll monitor it i guess
illinimarshke: eceguru: you could just write the test scripts
illinimarshke: and then execute those
Abhi327: We also need to find out from our T.A what they realistically expect us to submit at the end of the semester. We only have about 5 weeks to go before the semester end.
Eceguru: that's my main plan
illinimarshke: i have templates for ever type of rup artifact
Eceguru: can you send those to everyone
Abhi327: kevin that should definitely help.
illinimarshke: yeah
Abhi327: yes please.
x V DoGG x: hey guys - i gotta take off, i can't read this screen without feeling dizzy in this car..... kabe can answer for me the rest of the meeting or call if i need to vote.... and such.... laters....
starkiller76: later
illinimarshke: later
Eceguru: bye
x V DoGG x: also - can someone please post the log on the web, since i won't have it
x V DoGG x: thanks
starkiller76: i will
illinimarshke: i'll package upsome rup stuff and send it out in the morning
starkiller76: thanx
Eceguru: k
x V DoGG x: defect tracker, keep bugzilla in mind....
x V DoGG x has left the room.
Abhi327: i believe sourceforge uses bugzilla
Eceguru: i'll investigate it and send out some info to everyone
Eceguru: prototyping...
starkiller76: Abhi, how do you want to split up the design so we can start coding this week
Eceguru: how should we proceed
illinimarshke: http://sourceforge.net/tracker/? group_id=63137&atid=50295 6
illinimarshke: here is a defect tracker in source forge
Abhi327: o
kabev1: let's use that then
starkiller76: looks good
Eceguru: yeah
Abhi327: yup
starkiller76: back to the code, we probably need to get a module working that can autodect other nodes at a minimum
Eceguru: yeah
starkiller76: for this week
Abhi327: should we just quickly list artifacts that we must start working on and keep in mind as we move along.
starkiller76: sure
Abhi327: i agree dave.
illinimarshke: how about i do the req documents
illinimarshke: cause we should have that relatively early in the process
sudigh has entered the room.
Abhi327: i'm working on developing the visual model of the s/w using use cases.
sudigh: sorry guys, I'm late today.
sudigh: Hi
illinimarshke: we can use the tracker in sourceforge to create a requirements list
Abhi327: at this point i think we should just reverse engineer our use cases back to requirements doc.
illinimarshke: and i can build a document with that info and the use cases
starkiller76: I agree
illinimarshke: well a req doc should have both
illinimarshke: use cases and supplementary specs
Eceguru: yeah
illinimarshke: you don't need to reverse the use cases
illinimarshke: but you do need to adds the URPS - usability, reliability, etc
Abhi327: yes they will be essentially part of our requirements doc.
Abhi327: non functional reqirements
Abhi327: yup agreed
illinimarshke: right
Eceguru: not sure how to best add the non functional requirements
illinimarshke: first we make a list in sourceforge
illinimarshke: i'll make a doc template
illinimarshke: then we'll add them when we have a finished list
starkiller76: why don't we all think about non-functional requirments
starkiller76: email anything you come up with to kevin
Abhi327: yes we'll only be able to identify it as we move along.
Eceguru: we can also have requirements that say that component is not a requirement
Eceguru: like saying there is no security requirement
starkiller76: good idea
Eceguru: instead of having to define something that we have no idea how to define or measure
Abhi327: yes i agree.
Abhi327: as long we do a good job identifying the core requirements and address non-functional requirements at the bare minimum, we should be ok.
starkiller76: Also we need to keep the risk assessment current
Eceguru: yeah
starkiller76: I will do it
starkiller76: when you guys come across something in coding, or think of any risks let me kno
starkiller76: know
sudigh: Did you guys all have a looks at the updated project plan ?
illinimarshke has left the room.
Abhi327: yes. looks good.
starkiller76: why thank you
sudigh: cool. We'll update it more with time.
Eceguru: looks good
starkiller76: iteration 3 pretty much specifies what we need to do in the next 4 weeks
starkiller76: Abhi, how can we split up coding for this week?
sudigh: I think we should now pick up modules and start working on them.
Eceguru: agree
Eceguru: do we have a list of modules?
sudigh: Abhishek, have you registered in sourceforge ?
Abhi327: i can get you a definite plan by wednesday. i've been working on the class diagrams using use cases essentially focussing on the autodetect use case
starkiller76: Do you need help
starkiller76: it seems like a big job
Abhi327: yes ihave. i'll email the information after the meeting.
Abhi327: actually it is.
Abhi327: i'm just breaking up the system in to modules
Abhi327: and focussing on the module we wanna implement rightaway
starkiller76: Do our diagrams help?
Abhi327: so we have something to work on
sudigh: Some of us can work with Abhi maybe.
starkiller76: If you need me to diagram something, I will
Abhi327: i just wanna ensure the dependecies b/w the modules are taken care of before we start coding.
sudigh: on coming up with a working class diagram
Abhi327: essentially the high risk modules.
Abhi327: this is what my plan is
Abhi327: i am gonna send the team a class diagram and a high level break up
Abhi327: of our system in to modules
starkiller76: sounds good
Abhi327: with the usecases prioritized
starkiller76: do you want to assign the modules to workers?
Abhi327: and how the modules work with respective to our use cases
Abhi327: can we hold off till wednesday. i'll send you guys everything at that point.
starkiller76: Do we want to meet briefly on Wed. night?
sudigh: I can try getting registered in sourceforge and try to setup the levels we would like to borrow from JXTA
Abhi327: we could meet if that works for everyone else.
Eceguru: lets meet wed.
sudigh: I can met.
starkiller76: fine with me
sudigh: met = meet
starkiller76: not meat
Abhi327: great we'll meet wednesday at 8:30 CST
starkiller76: settled
sudigh: ok
starkiller76: I just wanted to mention
starkiller76: the tutorials on the JXTA site are pretty good
sudigh: yup
sudigh: It is a plethora of info out there.
kabev1: I can be there on Wed also
starkiller76: I have been working with them, and would recommend anyone who hasn't go through some before we meet on wed
Abhi327: yes and i'll also ask Howard as to the extent to which they expect us to develop for the semester. I'll shoot off an detailed email to him. That should also give us some clarity as to how much we need to accomplish.
starkiller76: JXTA API is large
Abhi327: getting back to our list of artifacts ?
sudigh: Yes, we'll pick the ones for decentralised p2p.
starkiller76: What do we still need to cover for artifacts?
sudigh: what next ?
Abhi327: 1) kevin is working on requirements
starkiller76: 2)Dave is working on risk assessment
Abhi327: 2) i'm working on the visual model for our system (Class diagram)
starkiller76: sorry abhi
Abhi327: no probs.....:-)
Eceguru: i'm working on test plan
Abhi327: yes.
kabev1: I'm taking care of the CVS and anything else??
Abhi327: do we need the config. mgmt plan kabe
Abhi327: ?
starkiller76: yes
starkiller76: it was in the critiria
Abhi327: kave when you say CVS, you mean the config. mgmt plan right
Abhi327: kave = kabe sorry
kabev1: Yup
Abhi327: cool.
kabev1: And for Vivek?
starkiller76: The RUP book has some good imput for a CM document
sudigh: So are you gonna create accounts in sourceforge Kabe ?
starkiller76: imput = "input"
kabev1: I son't think it works like that
Abhi327: kabe, i might have a sample Config. mgmt plan for a class project if in case ur intersted. i'll send it to you.
kabev1: Please do
kabev1: I beleive with sourceforge you register yourself
Abhi327: yes
kabev1: then join the group
Abhi327: and we'll register individual
Abhi327: people with a project group
Abhi327: i guess you can checkout code for as annonymous user
Abhi327: but to checkin our CM will come in to play. it'll depend largely on our config. mgmt plan.
kabev1: You can control that I believe
Abhi327: yes absolutely
kabev1: that=who can checkout code
Eceguru: kabe, can you prepare something to summarize the whole checkout/checkin process
Eceguru: that should help with the grading as well
kabev1: I will, but I can't by wednesday
Eceguru: that's fine
Abhi327: sure.
kabev1: I will get a CM plan up by Mon
starkiller76: thanx
Abhi327: kabe, i'll send you a sample config. mgmt plan. that will help you.
kabev1: Thanks abhi
starkiller76: i am also going to be working on a more detailed iteration plan with Sudipta
sudigh: yes, sure Dave.
starkiller76: I will be able to do this after I get Abhi's stuff on Wed.
kabev1: Also, I need to know if there is anything Vivek should be working on
Abhi327: vivek is our system analyst. he'll identify use cases as we go along and specify them.
kabev1: so nothing is directly neede from him this week?
Abhi327: nope. i think he is good for the week unless something comes up on wednesday
kabev1: cool, I'll pass word
sudigh: I'll start looking more deeply into modules corresponding to use cases 1 & 2.
kabev1: alright so is there anything else we need to touch on?
sudigh: I had worked on them for hw2.
Abhi327: i think we got most of the artifacts covered.
starkiller76: Everyone start practicing JXTA/Java
starkiller76: if you need ot
kabev1: Good idea, is the meeting finished?
starkiller76: I think so, Abhi?
Abhi327: yes.
starkiller76: i will write the summary
Abhi327: we'll get together again on wednesday 8:30 CST
starkiller76: an copy the log
Eceguru: alright see everyone on wed.
kabev1: alright talk to everyine on wed
starkiller76: bye, be safe
Abhi327: goodnight everyone.
sudigh: bye.
kabev1 has left the room.
Abhi327: bye
Eceguru: bye
Eceguru has left the room.