Classical Analysis
Introduction
ü The Specification Document
ü Informal Specifications
ü Structured Systems Analysis
ü Structured Systems Analysis:
The Art Dealer
ü Other Semiformal Techniques
ü Entity-Relationship Modeling
ü Finite State Machines
ü Petri Nets
ü Z
ü Other Formal Techniques
Specification document — Contract between client and developer Specifying what product must do and Constraints on product
Almost always has a specified deadline for delivering product Incorporates constraints that product has to satisfy
Portability (e.g., hardware or operating system) Reliability (e.g., needed to be operational 24 hours a day)
A set of acceptance criteria A series of tests
The Specification Document
Solution strategies — General approach to building theproduct Once
development team fully understands the problem
Development
team suggests solution strategies Determined if a solution satisfies client’s
constraints
Record
keeping of discarded solution for future justifications
One or
more possible solution strategies are determined Client has to make a two-stage decision
(1)Whether client should computerize: Cost-benefit
analysis
(2)If so, which of viable solution strategies to
adopt: Client’s optimization criterion
E.g.,
minimizing total cost to client
E.g., maximizing return on
investment
Developers advise client as
to which of the viable solution strategies best satisfies the optimization
Informal Specifications
Specification
document could consist of many pages of text
English
or other natural language
Client’s
wishes may be ignored
There
can be ambiguity
Style
may not be good
Related Topics
Privacy Policy, Terms and Conditions, DMCA Policy and Compliant
Copyright © 2018-2023 BrainKart.com; All Rights Reserved. Developed by Therithal info, Chennai.