WHAT ARE REASONS AND IMPACTS OF WEAKNESSES IN BUSINESS REACTIVITY WITH UML?
Factors that impact negatively the reactivity of systems to changes are mainly due to the lacks that concern evolution of specifications, to their absence of traceability from requirement analysis toward software implementation and also to the gap that persists between the business and the application system layers. A brief insight for each one of these development issues is given below : • Lacks of Evolutivity in Specifications: Specifications are not rendered identifiable in the UML diagrams. Indeed, in general, a given requirement references operations implemented in more classes. As a consequence of this orthogonality between requirements and classes, it is not easy for analysts to specify evolution of requirements in face of changes and for designers to implement required “corrections”. In order to specify evolution of requirements within their kind of nominal and alternate realization scenarios, specifications need to be designed as identifiable classes and components like object
Related Questions
- For competitive reasons, we have very different benefits for different lines of business. Can we choose to "play" for some and "pay" for others?
- What are some of the other broader economic impacts if an automaker goes out of business?
- What are the reasons for accrediting business schools outside North America?
