There is no substitute in developing a software system for a user or client without involving the user or
client as much as possible. Requirements, prototypes, feedback changes, and delivery should all revolve
around the user. However, since that is not a
Great discussion. You made really great points regarding meeting the users and seeing how they work
and also that some users do not like change. I notice that a lot of older users are more resistant to
change, whereas younger users are welcome to new tech
You made some great points! I definitely agree that it can be extremely frustrating to have to participate
in requirements analysis and software testing with IT, when you are also trying to get your own job done.
Coincidentally, I currently manage the bil
INFO 638 Project Proposal
Company: Campus Books, Inc.
This document defines the business scope of impact and project goals. It explains the
scope of operational/business problems and business processes that the proposed system
solution will impact and sum
Microsoft SharePoint is a content management system that offers a collaboration service for
intranet configuration management capabilities. First released in 2001, SharePoint h