IT Project Kwa Vitendo

Sawa sawa, ofcourse lazima tuweke categorised serach ili iwe rahisi. Okey next nadhani ni REQUIREMENT DOCUMENT au?

Mkuu nawasilisha document tatu.

mbili ni template tunazoweza kutumia kuandika requirement document moja tutayokubalina members wote


na ya tatu ni ya document niliyochakachua katika hizo mbili hapo juu na kufanya wording na editing ili iendane na our project gols View attachment online Contact requirement.doc

So hapa nawasilisha.

NB. tunaweza kuendelea kuedit hiyo ya tatu na kuongeza yale yanayopungua
 

Attachments

Kuna some interesting issue project "client" kotinkarwak kaziataja hapa inabidi member tuzianglie na kukubliana issue moja wapo na ya muhimu ni ya Hii pro jct yetu je Should it be a requirement kuwa accesible kwenye mobile device?

kama kuna member yeyote member yeytie ana idea ya specific requiremnt za mobile zinahitaji nini techincaly . Anielimishe au kunipa link nijue



it's a good and challenge discussion umeleta na tunaendela kujifunza na kueleweshana issues mbali mbali.

NB
hizi ni views zangu sio maamuzi ya project members wote
 
Thanks team.
Changamoto zangu naona zinawaweka on your toes as you think about how to implement the system.
Najua wengi hapa pengine wangefaidika zaidi from building a system from scratch since in that way, more experience ingepatikana on how all aspects of an application fits together.
Pia kwa nia ya kufahamishana what solutions are out there, ningependa ku'introduce morfik into the mix. This build environment would allow various aspects of the web app to be looked at within the same IDE, database design, security, GUI/Front end design na pia kuwajumuisha wale ambao wana experience say in C#, Visual Basic, Pascal katika ku’develop a web centric application. Morfik will also allow you to develop same application to be viewable on normal web and have specific pages for the small form factors as in mobile phones (you can even go further and create for particular form factors within that mobile space)

Another application that surely would need your attention is outsystems Agile Framework. OAF may be overkill for this particular requirement but is surely an application that can be used to write true web applications that have business processes behind the scene all defined and worked into the application. There are plenty of videos on their site to see what I mean.

I know it is very involving picking up a new tool in the middle of a design process and tends not to be advisable kwani it could detract from the flow already gained lakini nimeona, pengine ni vyema nizi introduce.

They are not 100% free but have a community distro in their product line.
Again, these could just be ammunition in your learning paths and not necessarily for this project.

Comments on my earlier posts as from reply to Mtazamaji
Security is never enough, don't rely on the hosting site to implement security for your site (/home). They will implement general system security, performance tuning, backup regimes lakini your /home directory from which you will be running the site is your responsibility. You will have cgi-bin, and some providers may restrict what you drop in there while others leave you at the mercy of the wolves on the net.

Data security
I think the site disclaimers should be looked into from this point.

Feature set
The more the merrier. And if built-in at launch time will be best. I only pick up a telephone directory to look up a number/business. If however, the service offered there was more than just such lookup, I could be visiting it more often. You ask, what else could they do? Well, they have a R&D and its their job to add whistles and bells to the site for me, ontop of making it easier for the basic functions I need to be implemented. Would the companies adviced there offer me discounts? are there vouchers if I contact them through the search site? Those are the kinds of questions the R&D would work on to better their services. Remember, traffic to a site is ciritical for the sites success, and when you think about features, you will more likely be thinking of increasing the traffic and offering more than the bog standard search site. I say this because there has been a few efforts by bongo folks on creating these kinds of services, and many end up just filling in data for a handful of search categories because the assumption I guess was that the rest will be filled in as you go along. That is a dead end idea unless the initial list was big enough and the site offered more than just a standard feature to make the traffic worth while.
Looking at future developments, say in advertisement on the site. A clued up company will ask you this critical question. What is the traffic to the site?

On data input, I understand that even phone submissions will be used. I know the Mobile market offers very interesting daily/weekly tarrifs and that will mean user will be in a position to provide more info as a result when they call in. Maybe you could also have an outward call arrangement where your researchers/data specialists will contact customers from prior arangements (no cold calling please...) to have their data input into the system.

On question of data currency, I know it is difficult to have 100% clean data where user input was source of the data, but the cleaner it is, the better and efforts should be in place to at least address that. If a hospital expansion/change of venue/change of experts is not reflected in your data, then the data ceases to be of any meaningful use. Users will feel agrieved (remember even if your service is a free service, users are entitled to be) if the numbers they call are dead numbers especially for those critical services like police, hospitals and the like.
 
moja ya vitu ambavyo mobile iko limited ni flash contents na some javascript issues like pop up windows
 
View attachment 22258
here is another template

Previously i thought its a requirement definition document . So member should ignore my previous submmission of the requirement definition .

Regarding this System Requiremnet Specification lets a all member use the template you have provided astandard
 
View attachment 22258
here is another template

Prevoiusly ithought u were directing us to do a requirement definition. Now i know its a System Requirement Specification..

I advice member wote tuchangie na kuweka input zetu hatua kwa hatua kwenye hii template. mpaka tupate final version.

I submit Two section nilizojaza Introduction and Overall prduction description. for your review comment and addition
View attachment srs_template1.doc

Itakuwa vizuri tukifuta hii standard not bad tukichukua hata wiki nzima
 
Guys you need to specifically point out!
(1) What exactly are the functions of the user?
(2) How many types of administrators are you going to have?, are all the administrators going to have the same priviledges?
(3) what are the functions of The Administrators?, dont generelize, forexample when you say administer the site that is general, you need to say forexample (1) add the new bussiness (2) delete a certain bussiness (3) modify bussines info, etc

If you are able to answer the above questions then, you can proceed to model the UML such as Use case, Class diagram etc.

The other thing is: About the GUI(appearance), if you also want to develop it from scratch( I mean not using the already existing Templates) , you need to present a rough sketch of the site( home page) and the successive pages(if it is gonna be a dynamic website).
 

ni vizuri kutulia mnapo andika hizi documents, maneno kama etc sometimes si mazuri hasa inapo bidi kuwa na list ya vitu kamili. inabidi uchambuzi wa kina,kulingana na hali halisi ya hapa bongo. mfano, tunatakiwa kujui aian zote za intituion tunazo target, ili isifike wakati kikaja kitu ambacho specofication zake hazipo kwenye documents, something can cost you in the future.
 

Uko sahii mkuu.unajua sometime hii lugha ya wenyewe inakuwa kikwazo sisi wa kina kanumbas na hata hivyo ni ni just draft hope in three or for days itazidi kukizi viwango .

But no excuse hizo etc ni kweli hazitakiwi kwenye requirement specifation . Advice noted and thanks
 
Wakuuu hapa nimefanya syntax na semantic error coreections nilzolete kwenye doc yangu ya mwanzo na pia nimeongeza kipengele cha Interface Kwenye section ya product overview.

View attachment srs_template2.doc

Ila bado sijaona mebers akichangia kuhusu hii aplication kuwa accesible kwenye mobile. Should it be a requirement? is any one of us anajua tutahitaji nini. My self sina clue.
 

Im on the document, so I will be submit mine on Saturday, if thats okey with the team.
 

....i still don't get it!!!!
 
working on the project, to submit my contribution by sunday.
Thanks members for the good job.
cheers!!!!!!
 
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
 

Similar Discussions

Cookies are required to use this site. You must accept them to continue using the site. Learn more…