Are business requirements the only source for deriving product attributes? No. There are
many other sources that can provide clues to the kinds of products the business organization
is planning to construct. These artifacts can be problem domain documents; business process
modeling documents and diagrams, which depict and characterize business activities; business
and technology strategy documents; technical requirements and specifications; and others. Thus,
the attribute derivation process should not be confined to business requirements, because they
may not provide all the product descriptions that are being sought.
What major goals should be achieved during the attribution phase? There are three chief
objectives to aim for:
1. Study and understand the organization??™s business requirements and become acquainted
with business objectives, business strategies, and the general business direction of the
enterprise. New business ideas and proposed concepts should be analyzed.
2. Business requirements or product specifications may be delivered in a raw format that
is not always understood by business and information technology (IT) organizations; the
requirements may be too generic or underspecified. Thus, this is the time to break down
the proposed business specifications and separate organizational concerns. This conceptual
decomposition of enterprise ideas must be pursued to simplify the complex manner in
which they were originally presented for implementation.
Pages:
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152