具有服务器端交互的 Flash 应用程序的估算报价
我正在构建一个 Flash AS3 应用程序，允许用户修改图像（拖放、选择、缩放、改变饱和度等），然后将它们提交保存到服务器。
然后，用户将能够通过缩略图库中的单独管理工具登录并访问这些保存的图像。 他们可以删除图像或单击缩略图以原始尺寸查看图像。
我仅设计和构建前端，并将提供设计就绪的资产。
由于我之前一直致力于固定报价，因此非常感谢任何有关引用该项目的反馈建议！
提前致谢！
I am building a Flash AS3 application that allows users to modify images, (drag and drop, select, scale, alter saturation, etc) and then submit-save them to a server.
The user will then have the ability to log in and access these saved images via a separate admin tool in a thumbnail gallery. They can either delete an image or click a thumbnail to view it at original size.
I am architecting and building the front end only and will have design ready assets supplied.
Since I have been burned in working to fixed quote before, would appreciate ANY feedback advice on quoting this project!
Thanks in advance!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我已经做了很多估计，我发现获得可靠估计的唯一方法是将所有任务和子任务分解到尽可能细化的级别，估计所有这些元素，然后然后把它加起来。 这通常需要我经过几次，并且有几次在半夜醒来。
这是很耗时的，但至少在三个方面效果很好。
显然，第一种方法是您最终得到一个非常可靠的估计。
您还会想到各种如果您没有坐下来写下所有内容就不会想到的事情（这首先是估计结果错误的一个重要原因） 。 真正思考整体方法，最终在使用哪个框架等问题上做出更好的决定。
将所有内容写得非常详细，有助于对您正在做的工作与其他队友的工作进行排序。 可以很容易地看出，在给定点上，如果您没有来自服务器团队的 API 等，您将受到阻碍。还可以帮助您了解如何潜在地阻碍您的队友，并让您能够处理
希望这有帮助。 让自己在项目估算结束时努力工作确实帮助我在实际开发方面取得成功。
I've done a lot of estimating, and I've found that the only way I can get a reliable estimate is to break down all of the tasks and subtasks to as granular a level as I can, estimate all of those elements, and then add it up. This usually takes me several passes, and a couple of times waking up in the middle of the night.
It's time-intensive, but works out really well in at least three ways.
Obviously, the first way is that you end up with a pretty reliable estimate.
You also think of all kinds of things that you wouldn't have thought of if you hadn't sat down and wrote everything out (which is a big part of why estimates turn out to be wrong, in the first place). You also give yourself the chance to really think through your overall approach, and you end up making better decisions on things like which framework to use.
Writing everything out to the detail level helps a lot in sequencing the work you're doing with the work of other teammates. Makes it easy to see that at a given point you'll be roadblocked if you don't have an API from the server team, etc. Also helps you realize how you will potentially roadblock your teammates, and gives you the ability to deal with that.
Hope that's helpful. Making myself work hard at the estimation end of a project has really helped me be successful in the actual development aspect.