java_roshan

This might be a new term among novice developers but not among Professionals in the software Industry!

While developing projects in school/college, how many consider the facts about user acceptance?

We, here in india, mumbai city, are usually confined to the acceptance of the professors/guides who would guide us in the development of projects and generally not the end user. If the user-acceptance fails for the guide, it has to be assumed that it fails for the end user?

We would provide with a user manual for the application, which would help the user understand how he has to use the system. Should this be considered as well in the project or just the acceptance of the guide?

Just wanted to know your opinions.

__________________
Visit: http://www.somaiya.edu

Arevos

During most CompSci degree work, the real users of the system are those examining it. Unless you are planning to publically distribute your software, I wouldn't worry about what a hypothetical end user thinks. So long as those grading your system are satisfied with it, then not much else matters.

java_roshan

So, while I am developing this software, I should consider them and not the actual end users?

Initially, when we started design on this, we thought of end users and not our guides

__________________
Visit: http://www.somaiya.edu

Arevos

Well, it depends what the professors want from you. At the end of the day, you should design software for the needs of your customers. In the workplace these will be paying consumers and businesses. At college these will be the people assessing your work.

It's not all that simple, however. It could be that your "guides" want you to design your system with an end-user in mind. Given this, the fact that you're thinking about hypothetical end-users will doubtless impress those who set you the task. But you also have to take into account that your idea of what end-users require may differ from what your guide thinks an end-user will require. In such a case, it helps to think up ways to justify your point of view.

java_roshan

Thanks, this helped me a bit. Ah!...I forgot to say something..

I am actually developing a web application. And, after some thinking, I have understood some specific points.
Some would like to use yahoo! because of what it has to offer , while some would use it because the way it has to offer -> functionality and user interface
while others might use the email client ...

Any more suggestions/replies/comments welcomed. A complete thought process....

__________________
Visit: http://www.somaiya.edu

zorin

With all the programs I develop in college we have to produce a user guide, test data and a trouble shooting guide. It helps to think that the person using your software has no previous computer experience so your guide deals with the problems they might have, stuff like not being to close the program, finding the program etc:-

Its actually good working practice and will help you out later out later in life if you start early. Might seem tedious now but its worth it

java_roshan

We do have user guide, but not test data and trouble shooting guide. I will work on that.
For the web application, are you commented on the visual designs which might be pretty good for you/client you may be virtually developing for, which might not be accepted by your professor / guide?
Just wanted to know what would happen elsewhere!

__________________
Visit: http://www.somaiya.edu