Extreme Programming for Service-BasedApplication Development Architecture 1025255018 何庠逵

Outline

Abstract SBA Architecture Service-Based Application Life-Cycle Conclusion

Abstract

The process of developing of new software product versions has speed up rapidly.

The necessity of flexible and particularly prompt responses to the changes triggered off genesis of new technologies, software architectures and methodologies.

The Service Oriented Architecture (SBA) allows defining services operation environment, web services then form one of the available technologies for SBA realization.

The software development limits the possibilities of adapting the development process to the changes and up-to-date requests.

This problem might be solved by adoption of Extreme Programming (XP).

SBA Architecture-IBM’s definition of SBA

lnteroperability The application has to get real-time financial data to perform local currency

conversion as well as interface with a database server to retrieve product information. As the two systems are probably different, the developer has to take care of interfacing.

Redundancies The interfacing component required might have already been developed by

other divisions of the company, probably even in other country.

However, chances are that it will be unknown to the current developer and the same work is duplicated.

Another hurdle in sharing components is that different departments across the organization might not be using similar technology in developing their application and hence increased the difficulty in component reuse.

lsolating Business Logic In the example of accessing the database, the developer needs to know the database

schema, what table to query, how to construct the SQL query etc., the usual chore that distracts the developer from the real work of implementing the application and business logic.

Consequently, when the database schema changed, the application breaks and the data access component need to be updated accordingly.

The updated component will have to go through unit testing, integration testing etc. before it is deployed.

Again these chores are duplicated across the Service Oriented Architecture (SBA) is a business-centric IT architectural approach that supports integrating your business as linked, repeatable business tasks, or services.

It is important to note that SBA is not a product but is an architectural style organization.

In general, the typical architecture of a non-SBA system.

Types of services Business services Entity services Functional services Utility services

Service-Based Application Life-Cycle

Control & Governance

Analysis and design

Realization

Phase

Deployment

Operation and maintenance

Control & Governance Organizational aspects - planning and deliverables schedule, project

team and roles establishing, defmition of both decision processes and guidelines to respond to special and specific situations, setting up a policy against which all future changes must confirm.

Analysis and design 2. Analysis of legacy system interfaces and functionality. 3. Identification and hierarchical categorization of services. 4. Partitioning service port1. Analysis of either requirement or

process operations to be realized by services, folio. 5. Specification of integration needs and patterns. 6. Detailed specification of services and individual components. 7. Model of service interactions within realized process.

Realization 1. Implementation of new serVices including description and semantics.

2. Localization of proper existing serVices.

Phase 1. Assignment of services and components into appropriate places within SBA.

2. Service and components functional testing.

Deployment 1. Deployment into a secured and integrated environment,

relevant data migration.

2. Availability and performance testing.

Operation and maintenance 1. Monitoring performance of service requests and timelines

of service responses.

2. Mainlining problem logs to detect failures.

3. Detecting and localizing failures, routing work, recovering work affected by failures.

4.Routine maintenance, administering and securing of applications and users.

Conclusion

現今的企業系統越來越複雜，系統設計必須確保可擴展性和怎麼跟別人溝通。而 XP這個方法可以讓系統更靈活，減少傳統設計上的缺陷，並確保系統的重用性和擴展性。

THE END