哪些质量属性对于电子商务 Web 应用程序至关重要?

发布于 2024-08-14 22:49:54 字数 344 浏览 7 评论 0原文

这个问题只是出于兴趣,也许对我的论文有用。

Web 应用程序,尤其是当您的企业在经济上依赖它时,需要满足某些要求才能生存。我想听听您认为对于 Web 应用程序最重要的(软件)质量属性(仅举几例)。

我给出我的分享: 性能(当访问者必须等待超过 2 秒时,50% 或更多的人会离开您的网站,这意味着可能的销售量会减少)。

安全性,至少要注意 OWASP

可靠性,您的 Web 应用程序必须能够处理错误的输入,而且还要处理大量错误的输入。

可维护性,在这个世界上,能够快速变化并适应用户增加销量的需求对于生存至关重要。

This question is just out of interest, and perhaps could be useful for my thesis.

A web application, especially when your business is relying on it financially, needs to meet certain requirements in order to survive. I'd like to hear what kind of (software) quality attributes you find most important (name a few) regarding to web applications.

I give my share:
performance (when visitors have to wait more than 2 seconds, 50% or more will leave your site, meaning less possible sales).

security , atleast be aware of OWASP

reliability, your web app must be able to handle faulty input, but also loads of them.

maintainability, in this world being able to change fast and adapt to your users need to increase sales is vital for survival.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(3

佼人 2024-08-21 22:49:54

这个问题很有趣,您已经提到了有趣的非功能性需求(又称质量)。

但我认为,就电子商务网站而言,最关键的品质是影响最终用户的品质。我的排名如下:

  1. 安全性(和可靠性)。作为用户,我希望系统是安全的,以便我有信心使用它。但安全性并不是可见的,需要体现在可用性中。如果发生中断,在我看来,恢复客户信心的最佳方法是对所发生的事情保持透明。
  2. 可用性。作为用户,我希望系统感到轻松。我不需要一些花哨的东西,而是一些有用的东西,它提供的功能让我感觉很舒服。可用性还与安全性的整体印象有关,例如,我收到的确认注册的电子邮件可能会给我带来更好或更差的系统印象,或者我的信用卡显示方式(通常只有最后一位数字)等所有这些可用性细节都可以增加我对系统的信任。
  3. 可用性。作为用户,如果网站出现故障或不稳定,我会得到非常糟糕的印象。确保您可以降低服务质量,并且至少有一个漂亮的页面指示定期维护或服务饱和度。
  4. 性能(和响应时间)。只有到那时,性能才会出现。我不想等待太久,但只要我得到有关正在发生的事情的反馈,我就可以稍等一下。

其他品质对于为电子商务网站提供支持的公司也很重要。但即使没有它们,您最终也能取得成功。我的排名如下:

  1. 可扩展性。之后的可扩展性改造是很困难的。如果业务进展顺利,拥有一个可以扩展的架构就很重要。因为糟糕的架构而错过商机就太糟糕了。
  2. 稳健性。如果您不希望您的热线电话被愤怒的客户电话淹没,您的系统就必须强大。 24/7 支持可能会产生大量成本。
  3. 可操作性(和可管理性)。如果需要大量的管理维护,那么保持系统正常运行的成本可能会很高。降低管理成本很有趣。
  4. 可维护性。当然,面对不断变化的需求,必须保持开发成本的下降是件好事。

编辑:我刚刚碰到了另一个答案显示了低响应时间的重要性。所以这确实是一个非常重要的因素。我不知道它是否比安全性、可用性和可用性更重要。关键是我们可以轻松地衡量性能,而这对于可用性和安全性来说则更困难。我很想知道每次流行网站停机时有多少客户流失。

This question is interesting and you have already mentioned interesting non-functional requirements (aka qualtities).

I think however that in the case of e-commerce website, the most critical qualities are the ones that impact the end user. My ranking would be the following:

  1. Security (and reliability). As a user, I want the system to be secure so that I am confident using it. But security is not visible as-is, and need to be reflected in the usability. If there is an outage, the best to regain confidence of the customer is IMO to be transparent with what happened.
  2. Usability. As a user, I want the feel at ease with the system. I don't need something fancy, but something usable, which provide the feature that make me feel comfortable with it. Usability also relate to the overall impression of security, e.g. the email that I receive to confirm a registration can give me a better or worse impression of the system, or the the way my credit card is shown (usually only the last digit), etc. all these usability details can increase my trust in the system.
  3. Availability. As a user, if the site is down or there are instability I get a really bad impression. Make sure you can degrade the quality of service and at least have a nice page indicating scheduled maintenance or service saturation.
  4. Performance (and response time). Performance would come only then. I don't want to have to wait excessively, but as long as I get a feedback about what's going on, I can wait a bit.

The other qualities are important for the company powering the e-commerce website. But you could ultimately be successful even without them. My ranking would be the following:

  1. Scalability. Retro-fitting scalability afterward is hard. It's then important to have an architecture that can scale if the business is going well. Would be too bad to miss a business opportunity because of a poor architecture.
  2. Robustness. Your system need to be robust if you don't want that your hotline gets overwhelmed by angry customer calls. 24/7 support can generate important costs.
  3. Operability (and manageability). It can be expensive to keep a system up and running if it requires lots of administrative maintenance. It's then interesting to keep the administration costs down.
  4. Maintainability. Of course nice to have to keep the development cost downs in face of changing requirements.

EDIT: I just bumped on this other answer which showed the importance of low response time. So it's indeed a very important factor. Whether it's more important than security, usability and availability I don't know. The point is that we can measure performance easily, which is harder for usability and security. I would be interested to know how many customers are lost each time a popular website suffer a downtime though.

倒带 2024-08-21 22:49:54

想在上述答案中添加一件事

共享选项:众所周知,如今每个网站都有一个特定社交网站(如 Twitter、Facebook)的共享选项。提供商添加此类内容将是一件好事网站的一个选项可以帮助用户分享,这对某些人来说会有帮助

。 积极因素——人们很快就会在网站上跟进,这也是一个很好的营销策略。

Would like to add one more thing to above answers

SHARING OPTIONS : As everyone knows nowadays every site has a sharing option to particular social networking sites like Twitter,Facebook.It would be good for the provider to add such an option to the site which would help the user to share which would be helpful for some people

Postives- People follow up soon on networking sites,would be good marketing strategy too.

风尘浪孓 2024-08-21 22:49:54

可用性
与产品相关的信息应该很容易找到。用户导航应该非常友好,即用户不需要去一系列页面来查找信息。

性能要求:
在当前的竞争世界中,您的网上商店必须快速响应用户请求。理想情况下,没有用户愿意等待超过 04 到 05 秒来加载页面并获取信息。您的网站应在此期间提供可用的内容。
另外,请记住移动购物,必须考虑到您的网站为移动用户提供了完全访问权限,并且他们能够完成购物。这里的页面加载时间非常重要,您必须使移动页面加载速度更快。

可维护性要求
随着快速变化的技术的出现,您的站点应该能够提供良好的应用程序功能和可扩展性。该架构应该足够灵活,能够处理大多数未来的需求,而无需在根级别进行太多更改。

安全要求:
凡是涉及金钱的地方,安全都是最重要的。为货币交易实施安全套接字层(SSL)就是其中之一。您还可以在您的网站上发布安全相关数据、隐私政策等。

可靠性要求
您的应用程序应该能够有效地处理有意或无意输入的大量错误数据。还要确保网站的停机时间非常短。

合规/法定要求:
如果您的网站满足某些合规标准(例如 PCI 合规性等),这总是有利的。它将增强网站用户对网站上交易的信心。

Usability
The information related to products should be easily found. The user navigation should be very friendly i.e. user need not go to series of pages for finding information.

Performance requirements:
In the current world of competition, it is a mandatory that your web store responds quickly to user requests. Ideally no user would be interested to wait for more than 04 to 05 seconds for pages to load and get the information. Your site should serve the usable content within this period.
Also Keeping in mind about the mobile shopping, it has to be considered that your site gives the full access to the mobile users and they be able to complete the shopping. Page load time here is very crucial and you have to make the mobile pages load faster.

Maintainability Requirements:
With the advent of fast changing technology, your site should be able to provide good features and scalability of the application. The architecture should be flexible enough to handle most of the future needs without much of changes at root level.

Safety Requirements:
Where there is money involved, safety is of prime importance. Implementing secure socket layer (SSL) for the monetary transactions is one of such step.You can also publish safety related data on your website, the privacy policy etc.

Reliability Requirements:
Your application should be able to effectively handle lots of faulty data coming either purposefully or accidently entered. Also ensure that the web site has very low downtime.

Compliance/Statutory Requirements:
It is always to advantage if your website has met some compliance standards e.g. PCI compliant etc.. It will imbibe confidence in the website user about the transactions on website.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文