Welcome! You'll be glad you are finally here to check out software architecture materials & resources!
The software architecture related documents & templates below are close to professional standards and can be customized easily to use.
|
|
Software Architecture Quick Links from DocStoc.com
- Models05 ServiceAspects - Current software systems increasingly consist of distributed interacting components. The use of web services and similar middleware technologies strongly fosters such architectures. The complexity resulting from a high degree of interaction between distributed components – that we face with webservice orchestration for example – poses severe problems. A promising approachto handle this intricacy is service-oriented development; in particular with a domain-unspecific service notion based on interaction patterns. A service is defined by the interplay of distributed system entities, which can bemodeled using UML Sequence Diagrams. However, we often face functionality that affects or is spanned across the behavior of other services; a similar concept to aspects in Aspect-Oriented Programming. In the service-oriented world,such aspects form crosscutting services. In this paper we show how to modelthose; we introduce aspect-oriented modeling techniques for UML SequenceDiagrams and show their usefulness by means of a running example.
- Service Oriented Modeling - Service-oriented modeling, a discipline of modeling business and systems, for the purpose of designing and specifying service-oriented business systems within a service-oriented architecture. You will find - approaches, issues, assets, notations, conceptualization (SOMA, SOMF). - A few examples and further readings.
- Unified Modeling Language - The Unified Modeling Language(UML) is used to specify, visualize,modify, construct and document theartifacts of an object-oriented softwareintensive system under development.[1]UML offers a standard way to visualize a system's architectural blueprints, including elements such as:• actors• business processes• (logical) components• activities• programming language statements• database schemas, and• reusable software components.[2]UML combines best techniques from data modeling (entity relationship diagrams), business modeling (work flows),object modeling, and component modeling. It can be used with all processes, throughout the software developmentlife cycle, and across different implementation technologies.[3] UML has synthesized the notations of the Boochmethod, the Object-modeling technique (OMT) and Object-oriented software engineering (OOSE) by fusing theminto a single, common and widely usable modeling language. UML aims to be a standard modeling language whichcan model concurrent and distributed systems. UML is a de facto industry standard, and is evolving under theauspices of the Object Management Group (OMG). OMG initially called for information on object-orientedmethodologies, that might create a rigorous software modeling language. Many industry leaders have responded inearnest to help create the UML standard.[1]UML models may be automatically transformed to other representations (e.g. Java) by means of QVT-liketransformation languages, supported by the OMG. UML is extensible, offering the following mechanisms forcustomization: profiles and stereotype. The semantics of extension by profiles have been improved with the UML 2.0major revision.
- Trainer's Material for OOAD using UML - This is an excellent UML training material for novices to advanced. It is a compilation from various UML resources. Read and become a UML trainer with authority in the subject.
- UseCase Estimation Template.xls - A Use Case Estimation template that is detailed readily usable!
Get more documents
