1 / 7

The Unified Approach

The Unified Approach. The UA approach establishes a unifying and unitary framework around their works by utilizing the UML to describe, model & document the s/w development process. It revolves around the following processes & concepts . The processes are: Use-case driven development

btownsend
Download Presentation

The Unified Approach

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The Unified Approach The UA approach establishes a unifying and unitary framework around their works by utilizing the UML to describe, model & document the s/w development process. It revolves around the following processes & concepts. The processes are: • Use-case driven development • OO analysis • OO design • Incremental development & prototyping • Continuous testing. The methods & technology employed include: • UML used for modeling. • Layered approach. • Repository for OO s/m dvlpmt. Patterns & frameworks. • CBD.

  2. The Unified Approach OO Analysis consists of the following steps: • Identify the actors. • Develop a simple business process model using UML activity diagram. • Develop the use case. • Develop interaction diagrams. • Identify classes.

  3. The Unified Approach OO design process consists of : • Designing classes, their attributes, methods, associations, structures & protocols, apply design axioms. • Design the access layer. • Design & prototype user interface. • User satisfaction & usability tests based on the use cases. • Iterate & refine the design.

  4. The Layered Approach • In a 2-layered s/m, user interface screens are tied to the data through routines that sit directly behind the screens. Ex: a routine that executes when we click on a button. • With every interface we create, we must re-create the business logic needed to run the screen. • A better approach to s/ms architecture is one that isolates the interface from the functions of the business. • This approach also isolates the business from the details of the data access.

  5. The Three-Layered Approach Consists of : • A view or user interface layer, • A business layer & • An access layer. The Business Layer: contains all the objects that represent the business. The responsibilities of the business layer are : Model the objects of the business & how they interact to accomplish the business processes. Business objects should not be responsible for the following: • Displaying details. • Data access details. The business objects are identified during the OOA. Use cases can provide a wonderful tool to capture business objects.

  6. The Three-Layered Approach The user interface (view) layer:consists of objects with which the user interacts as well as the objects needed to manage or control the interface. This layer is responsible for two major aspects : • Responding to user interaction: the user interface objects must be designed to translate actions by the user into an appropriate response. • Displaying business objects: this layer must paint the best possible picture of the business objects for the user.

  7. The Three-Layered Approach The Access layer:Contains objects that know how to communicate with the place where the data actually reside. It has the two major responsibilities: • Translate request: it must be able to translate any data-related request from the business layer into the appropriate protocol far data access. • Translate results: it also must be able to translate the data retrieved back into the appropriate business objects & pass those objects back up into the business layer. Access objects are identified during OO design.

More Related