IT Project Kwa Vitendo

IT Project Kwa Vitendo

Team na followers

Documentation is headache. To do something can be easy ila kuweka documentation yake in a understandable but standard way ni mtihani mkubw kwetu wengi.


Yaani unaandika kitu leo kesho unakifuta umepata wazo lingine. Sasa ukichanganya na kanumba's english. teh teh teh.

Hope tukiunganisha zote this week by the end next week tutatoka na SRS moja supa ambayo ndiyo itakuwa core reference na guidance
Maturity means ability to say no to good things that will interfere with your directions. once you choose a direction you will have to reject many good things. That is why we have BDFL in FOSS
 
Maturity means ability to say no to good things that will interfere with your directions. once you choose a direction you will have to reject many good things. That is why we have BDFL in FOSS

hapo ndo huwa unaniacha kwenye mataa na accrony unazotumia

What do u mean BDFL in FOSS.?

BTN
about this documenttion nimegundua kuwa kwa nini hata kwenye maofisi tunayofanya kazi tunajiuliza kwa nini sometime tunaongozwa na watu ambo tunahisi tunawazidi skills au elimu.

The diffeerence ni kuwa na maprogrammer, technician na engineer wengi hatupendi ku document. na hatu practise documentation
 
hapo ndo huwa unaniacha kwenye mataa na accrony unazotumia

What do u mean BDFL in FOSS.?
FOSS - Free and Open Source Software
BDFL - Benevolent Dictator(s) For Life

BTN
about this documenttion nimegundua kuwa kwa nini hata kwenye maofisi tunayofanya kazi tunajiuliza kwa nini sometime tunaongozwa na watu ambo tunahisi tunawazidi skills au elimu.

The diffeerence ni kuwa na maprogrammer, technician na engineer wengi hatupendi ku document. na hatu practise documentation
That right! Many coder thinks comments are enough....they are just lazy:coffee:
 
Passing the date...:embarrassed:
Hata mm sijamaliza but i hope k ila mtu kafanaya something tunaweza kuweka hizo pieace may be with three or foour incomplets SRS please tunaweza kuwa na SRS kamili. hata tukiextend Completeion ya hii SRS iwe by the end of next week . we dont need to rush .

But lets pput on table what we have so that tusihangaike na sections ambazo some one among members ameshafanya vizuri

How do u see that leader?
 
Hata mm sijamaliza but i hope k ila mtu kafanaya something tunaweza kuweka hizo pieace may be with three or foour incomplets SRS please tunaweza kuwa na SRS kamili. hata tukiextend Completeion ya hii SRS iwe by the end of next week . we dont need to rush .

But lets pput on table what we have so that tusihangaike na sections ambazo some one among members ameshafanya vizuri

How do u see that leader?

Makes sense. Good idea.
 
How does the project stand on numbers of contributors/developers?
Kwa wale ambao wanasubiri the meaty part of the project:- development, toeni maoni on what tools you want to play with? Document so far calls for LAMP implementation, lakini/labda developers have other ideas. In an earlier comment it was suggested kuwa developers wawe na environment ya XAMPP/WAMPP installed ndio waweze kudownload, and load the current distro of the site as each contributer makes release changes, je is this the way we are going au bado decision?
 
How does the project stand on numbers of contributors/developers?
Kwa wale ambao wanasubiri the meaty part of the project:- development, toeni maoni on what tools you want to play with? Document so far calls for LAMP implementation, lakini/labda developers have other ideas. In an earlier comment it was suggested kuwa developers wawe na environment ya XAMPP/WAMPP installed ndio waweze kudownload, and load the current distro of the site as each contributer makes release changes, je is this the way we are going au bado decision?
Plus how team is going to control concurrency, i.e modification of same file by two, three or even x developers.
 
Plus how team is going to control concurrency, i.e modification of same file by two, three or even x developers.

This is just my view not neccesarily it will be the way foward.

May be member wote tunakubaliana task ya kwanza kwenye implimentation itakuwa ni kutengeza database na business and personal info registration form(s) kwenye test enviroment . Hiyo ni task moja lakini ina visubtask viwili.

So How?

Kila member atatakiwa kuwa na test enviroment ya WAMP kwenye desktop/laptop yake ambayo attaumia kudevelop solutiion anayooona inafaaa na atatumia kutes solution walizotoa member wengine.

Ikifika deadline ya tasks member wanaleta solution zao then every member test and look each other mebers solutions . Hapa kutakuwa na kuunaulizana maswali kuelimishana juu tools mbali mbali tulizotumia , ugumu wake urahisi wake. etc

At the end of the task one solution amabayo labda inaweza kufanyiwa marekebisho fulani na imekubalika inawekwa Online kwenye free hosting website.

So kutakuwa kuna concurency kwenye online site. For experince and learnig purpose responsbility ya ku update online site inaweza kuwa rotated btn members
 
How does the project stand on numbers of contributors/developers?
Kwa wale ambao wanasubiri the meaty part of the project:- development, toeni maoni on what tools you want to play with? ?

Tuko developers wanne ila nahisi kuna mmoja naye atachomoka siku si nyingi.

Nadhani contributors watakuwa wengi ikifikia stage hii lakini again itakuwa maamuzi ya team leader na members kuchagua what will be best according to the situation
 
I think one thing you have not discusse or I just missed it!
Are you going to use Procedural, OOP or hybrid?
 
I would prefer OOP, easy to manage and maintain. Then to develop it is easier to go procedural with PHP.
 
Pia kwasababu sijawahi kutmia OOP kwenye PHP, nitajifunza. Ila, I go with the group.
 
I would prefer OOP, easy to manage and maintain. Then to develop it is easier to go procedural with PHP.

Any one who has an Idea of MVC partten. I think it can help us to structure our software.
 
naomba mtazamaji, member or anyone akileta mchango wake, uweke kwenye original post pale juu. maana sometimes inakuwa ngumu kutafuta, au tunaweza kuruka doc ya mtu.
 
I have some knowledge o MVC pattern. Here is what I propose as the way to go for whole thing
1. Overall design pattern -MVC
2. Database accessing class pattern - singleton

I concur with TL that OOP focuses on solution than programming issue. Eg. Auth class will deal with authentication issue while Session class will manage sessions. Also you can easily extend stuffs with classes than procedural

let say your project have 100 classes and you wanna change one method occured in each of them. You just change base class method...voila, presumably that all these have single base class somewhere....just my un organized thoughts!
 
naomba mtazamaji, member or anyone akileta mchango wake, uweke kwenye original post pale juu. maana sometimes inakuwa ngumu kutafuta, au tunaweza kuruka doc ya mtu.
tabutupu hukupata nafasi ya kuandika SRS au sijaiona doc yako?
 
Members na wachangiaji kuhusu developmemt approach kuna umuhimu wowote wa kuchagua specific aproach? . As to my knowlegde hapa tunacho develop sio software ni just some simple programs. na hizi approch nyingine zipo kwa ajili ya big programs (Software )

Approach Niliyokuwa nafikiria mimi wich can be productive katika mazingiraya precthii ni

Mfano ikifika stage task ya kusema members wa submit log in , authentication and confimration script kila member ata submit scripts ambazo ziko properly commented. itayayoonekana iko bora zaidi ndo hiyoitatumika . Sijui mnaonaje?

Kwa manufaa ya kujifunza kila task inaweza kuchukua zaidi hata ya wiki mbili kumpa kila member nafasi

Mi nona tutumie hii wiki kupolish , kuboresha na kukamilisha SRS while wakati huohuo member na wachangaji tuwe tuna brain storm mlolongo na mpangilio wa tasks execution ulio bora katike development

Mfano mlolongo wa unaweza kuwa hivi

  1. Propose web server/hOTS for testing -2 days
  2. Install WAMP on local machine- 3 days
  3. Database.- Member wataleta SQL script za ku create databaase na table wanazoendekeza - 7 days
  4. HOME PAGE- hapa member wataendelekza HTML scipt za homepageitakavyo kuwa - 7 dyas
  5. FORM- Hapa memberswatapendekeza script za form

  • Form ya user kusajili mawasiliano
  • Form ya user ku login
  • etc
6. OTHER PAGES AND LINKS
7. TESTING.- task hii inawezakuwa ya kutest user input, error na kurekebisha
8. etc

So katika kila task the best solution inachukuliwa. kwenye local machine zao member watatumia aproach wanayojua. but in presentation wawe tayari kufafanua na kuelimisha

Thats my views
 

Similar Discussions

Back
Top Bottom