System Analysis and design of A social Network -

is possible perform system analysis , design website ( particularly social network ) ?

what expected contents , in document ?

can u provide example , please ?

{ made social network (www.sy-stu.com) graduation project , want add full analysis study graduation document , have experience in uml , usecases idea of analysis of website not clear , never perform 1 before }

thanx in advance

this sounds ambitious, i'm sure it's possible. unfortunately, i've forgotten bit of system analysis, adhere many of guiding principles own projects. in fact, data-driven web sites excellent candidates systems analysis , should used during web planning project plan on putting production.

straight wiki:

1. the development of feasibility study, involving determining whether project economically, socially, technologically , organizationally feasible.
2. conducting fact-finding measures, designed ascertain requirements of system's end-users. these typically span interviews, questionnaires, or visual observations of work on existing system.
3. gauging how end-users operate system (in terms of general experience in using computer hardware or software), system used etc.

for first point, analyze different technologies such asp.net, ruby on rails , php. each technology has strengths , weaknesses. 1 key thing keep in mind if plan on making social network free, may consider open source technologies on proprietary - many servers , application frameworks proprietary projects costly. consider web startup , hosting fees. if plan on getting reseller account host gator, need factor in monthly billing costs. if plan host own servers, may amazed @ cost of doing so. stable system, need put lot of work , cash managing own web servers.

for second point, locate plenty of information on user requirements similar sites - check out forums diy social networks , see people having issues in technical support section. obviously, looking technology based articles , magazines place search on end user expectations - or joining facebook , twitter - see doing since people seem content.

for third point, again can consult competition , see how user interface works out. easy use? difficult in aspects? if had use system 8 hours day @ least 5 days week, drive mad , how better? , keep in mind logical work flow well. knowing user base important too. in systems, may developing other programmers. using strong jargon may fine, social network must remember aren't familiar web site data flow , terminology. controls should still make sense computer novice , still work securely (don't forget system security too!) , in organized fashion.

finally, remember things happen. created back-end site client of mine. though system worked - , pleased, got email today want way order items stored work differently. why there's maintenance aspect system development life cycle - things change after finish deploying. said if had communicated client's needs more closely, have been resolved. fortunately, change relatively minor, , live in real world things don't work expect. our best :)

as said earlier, systems analysis lot of work , should be. point of determine trying accomplish feasible , practical without committing long term project span years. , remember no plan perfect. if there perfect plans, wouldn't need new systems :).