TAILIEUCHUNG - Lecture Enterprise systems development - Lecture 18

This chapter include objectives: Define and describe the nine major e-commerce business models, identify the differences and similarities among customers and their perceived value of products and services in the B2B and B2C e-commerce business models, compare and contrast the development of a marketing mix for customers in the B2B and B2C e-commerce business models,. | Lecture 18 Enterprise Systems Development ( CSC447) COMSATS Islamabad Muhammad Usman, Assistant Professor College of Statistical and Acturial Science 1 Architecture Trade-off Analysis Method An architecture evaluation doesn’t tell you “yes” or “no” or “6,75 out of 10”. It tells you where the risks are. 2 Architecture Trade-off Analysis Method The ATAM is based upon a set of attribute-specific measures of the system Analytic (performance & availability) Qualitative (modifiability, safety, security) The ATAM workshops typically takes three days and the involvement of 10-20 people Evaluators Architects and other system stakeholders Benefits: clarified quality attribute requirements improved architecture documentation documented basis for architectural decisions identified risks early in the life-cycle increased communication among stakeholders 3 Risks, Non-risks, Sensitivity Points and Trade-off Points The latency for processing an important message might be sensitive to the priority of the lowest priority process involved in handling the message. The average number of person-days of effort it takes to maintain a system might be sensitive to the degree of encapsulation of its communication protocols and file formats. If the processing of a confidential message has a hard real-time latency requirement then the level of encryption could be a trade-off point. The rules for writing business logic modules in the second tier of your three-tier client-server style are not clearly articulated. This could result in replication of functionality, thereby compromising modifiability of the third tier (a quality attribute response and its consequences) Assuming message arrival rates of once per second, a processing time of less than 30 milliseconds, and the existence of one higher priority process, then a one-second soft deadline seems reasonable. Risks are potentially problematic architectural decisions. Nonrisks are good decisions that rely on assumptions that are frequently .

• Kỹ thuật lập trình
• Enterprise systems development
• Lecture Enterprise systems development
• Enterprise systems
• Requirements engineering
• Software Architecture
• Software quality