UML Father Peeks Into Development Future.Software will become pervasive during the next 30 years, and development of applications will evolve accordingly, according to according toprep. 1. As stated or indicated by; on the authority of: according to historians. 2. In keeping with: according to instructions. 3. one leading industry thinker. IBM fellow An IBM Fellow is an appointed position at IBM made by IBM’s CEO. Typically only 4 or 5 IBM Fellows are appointed each year, at the annual Corporate Technical Recognition Event (CTRE) event in May or June. Grady Booch yesterday predicted that IT systems will grow bigger as people come to rely on software in their day daily lives, through new forms such as wearable computers. This evolution in the computing landscape will mean hot- technology trends, such as XML XML in full Extensible Markup Language. Markup language developed to be a simplified and more structural version of SGML. It incorporates features of HTML (e.g., hypertext linking), but is designed to overcome some of HTML's limitations. and Service Oriented Architectures are left behind. Looking ahead to 2031 during Rational's user conference in Dallas, Texas, Booch said: "Software will be larger than it is today." Newer computing devices and runtimes means software will become increasingly distributed, and software development will evolve to tackle problems inherent in organizing development teams, designing systems and integrating distributed software. New devices will produce new computer languages designed specifically for their systems, or domains. "Java is not the last language," Booch told conference delegates during a keynote speech. "We will see continuation of languages... domain specific languages and frameworks will emerge built on UML (Unified Modeling Language) An object-oriented analysis and design language from the Object Management Group (OMG). Many design methodologies for describing object-oriented systems were developed in the late 1980s. semantics." Modeling through UML, will become important as developers attempt to encapsulate en·cap·su·late v. 1. To form a capsule or sheath around. 2. To become encapsulated. en·cap system design using repeatable, scalable architectures. "We will see tremendous emergence of architectural patterns - assets - to codify codify to arrange and label a system of laws. the variety of patterns for understanding those distributed systems," Booch said. Integrating these distributed systems will be tackled using new practices and architectures, which mean today's generation of work becomes dated and left behind. "In the future, the hard things are weaving those systems together - SOA (1) (Start Of Authority) The first record in a DNS zone file. See DNS records. (2) (Service Oriented Architecture) The modularization of business functions for greater flexibility and reusability. and XML are step on the way, but we will see other kinds of connection mechanism over time," Booch said. He noted 2031 would also see a growing legacy of XML, Java and C++ code living in computer systems. |
|
||||||||||||||||||||

Printer friendly
Cite/link
Email
Feedback
Reader Opinion