X-PASTER
JF-Expert Member
- Feb 12, 2007
- 11,610
- 1,810
Mkuu kazi ianze tu...!
Mkuu kazi ianze tu...!So we done with planning? Should we start on requirement analysis?
Hallo mkuu, Nimeongeza project objetives (Kipengere 1.4). Halafu hiyo documents nimeiweka kwenye mode ya kutrack all changes. Kwa hiyo kitu chochote ukibadili will be tracked with red colour. Lengo ni kutaka ni to have someone who can verify and validate these changes in the same document. Nam[pongeza mtazamaji kwa kuweka version ya hii document . Thanks.
Can everybody come with a use case diagram so that we all clear on how the system gon work.
Thank you!
Use-Case Description
From the project objective the design and implemented online contact directory is required to one major function
- Display contact and location information of Government institutions businesses, Organisation and individuals.
The above core function in this online directory system can be further broken down into smaller processes or sub functions which are performed by web visitors, Registered user and Data entry operator.
User / Web visitor
- Web visitor view all available contact
- Web visitor input search criteria to search particular info
- Web visitor register his. Contact/location information
Registered user (Individual, business, companies, Services)
- Confirm her/his Registration ( Important for individual private contact info)
- Change or edit his/her contact information
Data entry operator
NB: Confirmation of registration is through email user provided when registering their information. In future it can also be done though sms alert for user who requested their information to register through telephone.
- Key in contact information which is already available in public domain( Government institution businesses and services organisation like hospital ,schools)
- Register request of non web user who wants their information to be keyed in the directory ( trough telephone)
For simplicity I have just used word description of use case in stead of drawing a diagram
Why not one draw UC diagram and others keep posting the cases and the same person keep modifying to accommodate the needs. I submit to you ArgoUML, excellent tool and free!Can everybody come with a use case diagram so that we all clear on how the system gon work.
Thank you!
Mi pia najifunza mambo mengi...I'll keep visiting!kotinkarwak Yeshuamalech aksante nisana though project haijafika hata robo but naona faida zake. kuna tools na nyenzo tunajulishana hapa sikuwai kuzijua na sijui kama ningezijua..
Project Leader Vipi unaonaje. mambo yanavyokwenda?
I am sure it misses a lot. please tell..
View attachment 21907
Dear team.
Here is my contribution for use case diagram.
Download the document below.
First of ol, niseme: This is gud, from both of you.
RedSilver: Huna admin, (you have service proviser, user and registered user), sa hawa ma service providers tutawaaminije? what if I come up with "fake" contacts, 100 of them najaza tu db, is there any need ya kurestrict watu kama hawa? Then tofauti ya user na registered user an how are we going to model both in the db?
Tabutupu: Mi naona umemnyima rights nying sana user na member, jamani hadi hadi profile yake aneditiwa??? Authentication should happen to all actors...
My take:
Use case ya redsilver ichukuliwe, with just a few changes. Then description za tabutupu na redsilver zichanganywe (maana zote ni nzuri) to make up the whole usecase document/diagram
I am sure it misses a lot. please tell..
View attachment 21907
First of ol, niseme: This is gud, from both of you.
RedSilver: Huna admin, (you have service proviser, user and registered user), sa hawa ma service providers tutawaaminije? what if I come up with "fake" contacts, 100 of them najaza tu db, is there any need ya kurestrict watu kama hawa? Then tofauti ya user na registered user an how are we going to model both in the db?
Tabutupu: Mi naona umemnyima rights nying sana user na member, jamani hadi hadi profile yake aneditiwa??? Authentication should happen to all actors...
My take:
Use case ya redsilver ichukuliwe, with just a few changes. Then description za tabutupu na redsilver zichanganywe (maana zote ni nzuri) to make up the whole usecase document/diagram
:clap2:Ahsante, because I do not think we need to be adding info as it is a dynamic application let users do. but I think we need a way where can report any scam and spams. We shall have a simple component during registration that will restrict bots from registering.
Good!
Scenario
In viewing all available contacts,official , services , business , private information web user can have a sort or filtering interface . Which s(he) will use to filtercontact(people or organisation, service, ) by location ( Region/ district s.) or by industry, career or name or type of business.
User will enter hisher name or Enter Just his her Profession, Location . And contact
Web user enter his/her businesses/service company, name , location and type of product /service provided
User request his/her information removed from the system( database)
User request his or Her information( Businesses, private, Profession, etc) to be added
some scenario example
- mtazamaji does not like to register by his name but rather he would like to register by his prefession ( computer Techinician),his location Kinondoni and hi emaill
- Mr patel would like just to register his business name, location and type of product he sell without providingng his real name
I am sure it misses a lot. please tell..
View attachment 21907
First of ol, niseme: This is gud, from both of you.
RedSilver: Huna admin, (you have service proviser, user and registered user), sa hawa ma service providers tutawaaminije? what if I come up with "fake" contacts, 100 of them najaza tu db, is there any need ya kurestrict watu kama hawa? Then tofauti ya user na registered user an how are we going to model both in the db?
Tabutupu: Mi naona umemnyima rights nying sana user na member, jamani hadi hadi profile yake aneditiwa??? Authentication should happen to all actors...
My take:
Use case ya redsilver ichukuliwe, with just a few changes. Then description za tabutupu na redsilver zichanganywe (maana zote ni nzuri) to make up the whole usecase document/diagram