Domains of Software Engineering

1. Requirements Traceability: Requirements traceability is the process of describing and keeping track of a set of requirements throughout the system’s lifecycle. The process assists in managing changing requirements of a particular software product. Requirements traceability of is two types, forward traceability where a particular requirement involved during the design and implementation phases of the software system, and backward requirement traceability where a particular requirement is being traced back to its source. 2. Proposed Solutions for the Traceability of Non - Functional Requirements : The author J. Merilinna [8], proposed a framework supported by a tool to trace the non-functional requirements in both forward and backward direction. The proposed method is based on the context of DSM (Domain Specific Modeling).  The NFR+1 framework involved are used for the elicitation, definition and redefinition of the system’s non-functional requirements. The proposed

1.     Software Architectural Styles Description: Sr. # Style Name Component Types Connectors Configuration / Topology Quality Attributes 1.                   Process Control Architecture Processes Message Protocol Arbitrary ·          Performance ·          Reusability 2.                   Message Bus Architecture ·          Schemas ·          Shared Data Infrastructure Buses Network ·          Extensibility ·          Scalability ·          Flexibility ·          Performance 3.                   Component based Architecture ·          Software package ·          Service ·          Resource containing related functions Interface Components are put together on a single platform thus creating a new system ·          Maintainability ·          Performance ·          Reusability ·