Brief Explanation About Transaction Mapping in Software Architecture

Dec, 23 2020, 01:00 pm [IST]
Brief Explanation About Transaction Mapping in Software Architecture

Transaction mapping

In several software applications, a single data item triggers one or more information flows that affect function played by the triggering data item. The data item, call transaction.

An example

Transaction mapping Vin the Illustrator by considering the user interaction subsystem of the safe home software. A single data item, command type, causes the data flow to fan outward from a hub. Therefore, the overall data flow characteristic is transaction-oriented. It should be remarked that information flow along two of the three action paths provides additional incoming flow. Each action, path flows into a single transform, display messages, and status.

Design steps

The design steps for transaction mapping are related and in some cases same as steps for transform mapping. An important difference lies in the mapping of DFD to software structure.

Step 1: review the fundamental system model.

Step 2: Review refines data now diagrams for the software.

Step 3: Determine whether the DFD has transform or transaction flow characteristics.

  • Steps 1, 2, 3 are identical to corresponding steps in information mapping.
  • However, flow with two of the action paths originating from the invoke-command processing bubble seems to have transform flow characteristics.
  • Therefore, flow boundaries must be placed for both flow types.

Step 4: distinguish the transaction center and the flow characteristics with each of the action paths.

The place of the transaction center can be directly discerned from the DFD. The transaction center lies at the source of several action paths that flow entirely from it. The invoke command processing bubble is the transaction center. The incoming path and all action paths must also be separated. Each action path must be assessed, for its flow characteristics.

Step 5: Plan the DFD in a program structure manageable to translation processing.

Transaction flow is mapped into a structure that includes an incoming branch and a dispatch branch. The structure of the incoming branch is designed in much the identical way as to transform mapping.

Beginning at the transaction center, bubbles along the incoming path are mapped into modules. The structure of the dispatch branch includes a dispatcher module and controls all subordinate action modules. Each action flow path of the DFD is mapped to a structure the corresponds to its particular flow characteristics.

Step 6: Factor and improve the transaction structure and the structure of each working path.

All action path of the data flow diagram has its data flow characteristics. The action path correlated to the substructure is generated using the design steps. The flow shows classic - transform characteristics. A key is input and transmitted to a transform center where it is compared against stored passwords. An alarm and warning message at producer if a match is not reached.

Step 7: In the first iteration architecture using design heuristics for improved software quality.

A first iteration architecture always is defined by applying concepts of module independence. Modules are exploded or imploded to create sensible factoring, good cohesion, minimal coupling, and most importantly, a structure that can be executed without difficulty, tested with confusion, and persevered without pain.

There are times, for example, when some input processing is needed in your module that is subordinate to the transforming controller when coupling due to global data cannot be withdrawn, or when optimal structural characteristics cannot be done. Many modifications can be made to the first iteration architecture developed for the safe home monitor sensor subsystem.

Among many possibilities

  1. The incoming controller can be eliminated because it is irrelevant when a single income flow path is to be achieved.
  2. This subsection formed from that transform flow can be imploded into the module to set alarm conditions. The transform controller will not be required and this small decrease in cohesion is adequate.
  3. The modules format displays and generates display can be imploded into a new module called produce display.

The purpose of the preceding seven steps is to develop an architectural display of the software. That is, one structure is defined to evaluate and refine software architecture by viewing it as a whole. Modifications made at this time will require little additional work, yet can have a profound, importance on software quality.




Details About Software Quality Assurance

Dec, 16 2020, 12:02 pm [IST]
Details About Software Quality Assurance


Software quality assurance Software quality is described as conformance to explicitly state functional and performance requirements, explicitly documented standards and implicit features that are anticipated of all professionally developer software ... Read More

Details About Tunnelling and Encapsulation in Mobile IP

Dec, 10 2020, 02:19 pm [IST]
Details About Tunnelling and Encapsulation in Mobile IP


A tunnel establishes a virtual pipe for data packets between a tunnel entry and a tunnel endpoint. Packets entering a tunnel are forwarded inside the tunnel leave the tunnel unchanged. Tunneling, that is, sending a packet through a tunnel, is achieved by using encapsulation ... Read More

Details About Software Architecture

Dec, 06 2020, 12:17 pm [IST]
Details About Software Architecture


The overall structure of the software components and how the success provides a conceptual integrated file system. In other words, architecture is the hierarchical structure of program components, how these components interact, and the structure of data that are used by the components ... Read More

Details About Real-Time And Distributed System Design

Dec, 04 2020, 01:28 pm [IST]
Details About Real-Time And Distributed System Design


Real-time and distributed system design The real-time system is a software system the correct functioning of the system depends on the results produced by the system the time at which these results are produced ... Read More

Explanation About Software Project Lifecycle Model

Dec, 02 2020, 12:39 pm [IST]
Explanation About Software Project Lifecycle Model


Waterfall Model The waterfall model also called classic life cycle requirements is well defined and stable. It suggests a systematic, sequential approach to software development. It begins with customer specification of requirements and processes through planning, modeling, instruction, and deployment ... Read More

Software Design Concepts in Software Engineering

Dec, 13 2020, 12:01 pm [IST]
Software Design Concepts in Software Engineering


Software Design A software design is an essential engineering description of some software product that is to be established. A design can be determined to the customer's requirements and can be assessed for quality against predefined patterns ... Read More

Go to Top


About Us | Contact Us | Disclaimer | Privacy Policy | Sitemap | Terms and Conditions

Copyright © 2021 TeluguAsami. All rights reserved.