Research in Software Engineering Paradigms and Methods

Research in Software Engineering Paradigms and Methods - Key Points

Software engineering is new to the research field due to its different:

Research methods.
Validation methods.

The main focus of this papers is in the identification of research problems in software engineering. Research problems in software engineering can be classified into 2 categories:

Scientific Nature	Engineering Nature
Consist of different objects of study	Problem of building new software from existing artifacts
Focus is on the theoretical aspects of Software engineering	Its focus is on the artificial aspects
It is not just the actual but also the knowledge	It is not just the application but also the knowledge
Example: What things are like?	Example: What things should be like to create new?

Software engineering and computer science had been considered as a single field till the early 1980's which led to the immaturity of the software engineering research field. This immaturity had been verified as a result of the detected deficiencies in its research i.e. :

Systematic rigorous methods.
Lack of evident methods of research result validations.

Software engineering is a combination of two types of studies:

Software engineering designs can be created from an old one or the existing software designs can be studied to analyze their use in the industry but the same cannot be applied to software engineering tools as even after the creation of new tools, it is the old ones that are still tested. In this case, the development of the software engineering design is an empirical or a socio-cultural problem where as the later is the engineering problem. The justification of software engineering research had been conducted via:

The use of the research methods and paradigms depends on the nature of the research being conducted. The method required to solve engineering problems itself is becoming a research field.

Comments

Quality Practices in Agile Approaches

Agile Approaches Agile is an umbrella consisting of different methods adopted by the practitioners depending upon the circumstances. In the recent years Agile has been gaining popularity among software practitioners due to its ability in assisting the development team to deliver the software product in a short amount of time. Original Agile Approaches Based on the circumstances under which the agile methodologies have been used can be classified into the following 3 categories: Classification of Agile Approaches Agile Methodologies consist of the original agile methods Hybrid Agile Methodologies consist of a combination of several original agile methodologies e.g. Industrial Extreme Programming merged with practices of Rational Unified Process Miscellaneous category consists of methodologies adopting only certain aspects of the original agile methodologies Extreme Programming, Test Driven/Test First Development, and SCRUM are among the most popular agile met

How traceability of non-functional requirements is managed throughout the software development process?

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

Software Architecture Views and Structures

Description of Views: In the year 1995 Kruchten presented his 4+1 architectural view model consisting of the following five types of views: Logical Development Process Physical Scenario Later with further development and research in the domain of architectural view following new views were developed to represent their respective structures: Views Sub-View of Description Logical None Highlights the functionalities provided by the system to the end-users. Unified Modeling Language (UML) diagrams such as the Class diagram, Domain diagram, Use Case diagram, State diagrams and Activity diagrams can be used to represent the logical view of the architecture. Development None It is also known as an implementation view. It is mainly concerned with the software project management. It represents the system with the programmer’s perspective. Process None It deals with the representation of

Domains of Software Engineering

Search This Blog