in black and white
Main menu
Share a book About us Home
Biology Business Chemistry Computers Culture Economics Fiction Games Guide History Management Mathematical Medicine Mental Fitnes Physics Psychology Scince Sport Technics

convergent architecture Building model driven J2EE Systems with UML - Hubert R.

Hubert R. convergent architecture Building model driven J2EE Systems with UML - Wiley publishing , 2002. - 289 p.
ISBN: 0-471-10560-0
Download (direct link): convergentarchitecturebu2002.pdf
Previous << 1 .. 78 79 80 81 82 83 < 84 > 85 86 87 88 89 90 .. 142 >> Next

Many assembly components may exist in various stages of development or deployment at any time in the system development organization. The lead developer of each assembly component remains its resource owner throughout its entire life cycle and accompanies its evolution through generations of development and deployment.
Worker Roles and Responsibilities
Worker-specialized roles and responsibilities in the assembly development team include the following:
■ Assembly developer. This is the lead developer of the assembly
development team who normally has extensive experience as a component developer. This worker has the following additional responsibilities as owner of the assembly component: o Begins with the inception phase of a development project to
delimit and define the project and help the system project manager produce the longterm development strategy. o Develops the BUCS, AUCS, and the convergent business
object model for the entire assembly together with the domain experts involved in the assembly. o Works in the project planning stages to define the
component development teams required by the assembly, partitions development among the teams, and works closely with the lead developers of these teams. o Develops the assembly-specific configuration management
reference together with the lead developers and configuration manager.
o Produces the assembly architecture reference, which
describes the overall design of the assembly in the context of the Convergent Architecture style reference. The assembly architecture reference consolidates the component design references produced by its component development teams. o Defines, implements, and carries out integration tests,
business-case tests, and installation and deployment tests for the entire assembly. Assembly tests are carried out in the test center organization assisted by its respective workers. o Defines and carries out the deployment plan for the
assembly with the deployment manager. The deployment plan covers both tests and operational releases.
Convergent Architecture
Chapter 5: The IT-Organization Model
o Develops the assembly installation kit, which drives the
intelligent installation and deployment of the assembly. o Coordinates the development of design and end-user
documentation with the technical writer and the component development teams.
o Coordinates and tracks the reuse of any of its enclosed
convergent components by other assemblies. This tracking information is recorded in the assembly models. By the same token, he or she communicates the reuse of external convergent components with the respective assembly developer. o Remains resource owner of the assembly across all
generations until it is retired from use. o Convergent Architecture-specific consolidation of the
following RUP worker roles: same as component developer (discussed later) plus RUP system analyst and RUP integrator.
Owned resources: o Change sets (artifacts): Assembly component
(assembly architecture reference, assembly glossary, assembly configuration management reference, architectural IDE artifacts [convergent business object model, assembly UML model, project configuration files, generation cartridges, build and test environment,
Java-IDE environment], assembly installation kit, user documentation, developer documentation, application server configuration). The following specifications apply: o The convergent business object
model is comprised of the structural CRC model and dynamic state-transition-flow models (visual and recorded run-throughs) of BUCS and AUCS. o The assembly UML model is
comprised of the cumulative accessor component models and business component models (optional UML representations as required for explanatory or documentation detail: use-case representations of BUCS and AUCS, sequence diagrams, and activity diagrams for convergent components).
o The assembly installation kit normally
deploys an enterprise archive (EAR) in the J2EE technology projection and is comprised of all convergent component installation sets (discussed later), J2EE Web archives containing accessors, EJB archives, client Java archives, uninstaller, consolidated user documentation, assembly installation guide and release notes, and the consolidated installation verification test. o Specialized technologies: Same as Lead
Developer plus Zero-G Install Anywhere.
The Component Development Team
Component development teams specialize in the reusable parts of assemblies. Although the convergent components will be managed exclusively by their owning assembly, they often will be reused by other assemblies.[5] Thus, the component development team plays an important role in producing effectively reusable convergent components.
Convergent Architecture
Chapter 5: The IT-Organization Model
Worker Roles and Responsibilities
Worker-specialized roles and responsibilities in the component development team include the following:
■ Component developer. This worker is a developer in the context of
Previous << 1 .. 78 79 80 81 82 83 < 84 > 85 86 87 88 89 90 .. 142 >> Next