tag:blogger.com,1999:blog-12948038.post379013329602140947..comments2023-07-29T09:15:17.416+01:00Comments on allan's blog - Agile & Digital Business: Requirements and Specificationsallan kellyhttp://www.blogger.com/profile/06262139490250478379noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-12948038.post-48527810100787973182013-04-16T14:36:40.188+01:002013-04-16T14:36:40.188+01:00Good point Jeff, I need to think that through a li...Good point Jeff, I need to think that through a little more.<br /><br />Right off my first thought is:<br />- the program is the ultimate specification of what happens (provable via formal methods if you want) therefore any specification step prior to implementation could be seen as just the first action of implementation<br />- this would also explain why specification steps are often completely missing, because if you don't have one you flush it out by coding and testing<br /><br />So specification would not equate to implementation but it is part of implementation.<br /><br />Business logic is more tricky, partly because it is such a loose phrase.<br />Certainly the specification could contain business constraints, even elements of business processes but would it be the entire thing? I'm nor sure.allan kellyhttps://www.blogger.com/profile/06262139490250478379noreply@blogger.comtag:blogger.com,1999:blog-12948038.post-66915548781578187222013-04-16T13:05:02.534+01:002013-04-16T13:05:02.534+01:00Allan - This makes a lot of sense. In a colloquial...Allan - This makes a lot of sense. In a colloquial sense, would "specification" equate to "business logic" or "implementation"? That would seem to fit with the definition that specifications are developed by the team after the requirements are given; also that requirements should not include implementation details. If I am wrong on that point, I would appreciate some clarification. Thanks for the post!Jeff Lucashttps://www.blogger.com/profile/12503533139694410842noreply@blogger.com