如何根据业务规范为应用编写“系统规范”。

本文介绍了如何根据业务规范为应用编写“系统规范”。的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

我认为我实际上要求的最多只是一个模板，然后是我必须指定哪些方面的一些建议。 我有一个商业规格每个故事的用户故事条款以及其他验证规则等。 我认为我的规范，应该分为前端和后端两个开发团队，在应用程序的基本构成上会相当大 - 应该如何实现（ASP.NET MVC是一个要求，因为这是我们的标准），以及对水平服务的详尽描述。然后它将为每个用例提供细节的小附件。我在这里是正确的轨道吗？ 我尝试过： 我正在拼凑一个非常非常粗糙的原型来获得应用程序的形状和轮廓，所以我可以处理从哪个角度来记录需求。

I suppose what I'm actually asking for is at best a template, then some suggestions of what areas I must specify. I have a business spec in terms of user stories together with additional validation rules etc. per story. I think my spec, which should be divided into front and back-end, for two teams of developers, will be quite large on the basic makeup of the app - how it should be implemented (ASP.NET MVC is a requirement, as that is our standard), and thorough descriptions of the horizontal services. It will then have small appendages of detail for each use case. Am I on the correct track here? What I have tried: I'm slapping together a very, very rough prototype to get the shape and outline of the application, so I can get a handle on what angles to document the requirements from.

推荐答案

不是真的可以在快速答案论坛中回答的问题！ 你提到了用户故事所以我猜它是敏捷环境 - 看看这个敏捷功能规范 - its-all-design [ ^ ] 这个网站上有一些更正式的东西...或者这个特定的页面：重新关于敏捷项目的要求>商业分析师社区&资源|现代分析师 [ ^ ] Not really something that can be answered in a "quick" answers forum! You've mentioned "user stories" so I'm guessing it's an Agile environment - have a look at this An Agile Functional Specification - its-all-design[^] There's some more formal stuff on this site ... or this specific page: Requirements Specifications on Agile Projects > Business Analyst Community & Resources | Modern Analyst[^]