Results 1 -
7 of
7
FORM: A feature-oriented reuse method with domain-specific reference architectures
- Annals of Software Engineering
, 1998
"... Systematic discovery and exploitation of commonality across related software systems is a fundamental technical requirement for achieving successful software reuse. By examining a class/family of related systems and the commonality underlying those systems, it is possible to obtain a set of referenc ..."
Abstract
-
Cited by 132 (7 self)
- Add to MetaCart
Systematic discovery and exploitation of commonality across related software systems is a fundamental technical requirement for achieving successful software reuse. By examining a class/family of related systems and the commonality underlying those systems, it is possible to obtain a set of reference models, i.e., software architectures and components needed for implementing applications in the class. FORM (Feature-Oriented Reuse Method) supports development of such reusable architectures and components (through a process called the “domain engineering”) and development of applications using the domain artifacts produced from the domain engineering. FORM starts with an analysis of commonality among applications in a particular domain in terms of services, operating environments, domain technologies, and implementation techniques. The model constructed during the analysis is called a "feature " model, and it captures commonality as an AND/OR graph, where AND nodes indicate mandatory features and OR nodes indicate alternative features selectable for different applications. Then, this model is used to define parameterized reference architectures and appropriate reusable components instantiatable during actual application development. Architectures are defined from three different viewpoints (subsystem, process, and module) and have
A Conceptual Basis for Feature Engineering
, 1999
"... The gulf between the user and the developer perspectives lead to diculties in producing successful software systems. Users are focused on the problem domain, where the system's features are the primary concern. Developers are focused on the solution domain, where the system's life-cycle artifacts ar ..."
Abstract
-
Cited by 32 (1 self)
- Add to MetaCart
The gulf between the user and the developer perspectives lead to diculties in producing successful software systems. Users are focused on the problem domain, where the system's features are the primary concern. Developers are focused on the solution domain, where the system's life-cycle artifacts are key. Presently, there is little understanding of how to narrow this gulf.
Feature Engineering
- In Proceedings of the 9th International Workshop on Software Specification and Design
, 1998
"... ..."
Security Engineering for VANETs
"... (SEVECOM) has the aim to develop a future proof security solution for vehicular communication (VC). As there are no clear scenarios and standardized protocols for VC yet, traditional approaches for security engineering fail, as they usually consider a specific scenario and system. At the same time, ..."
Abstract
-
Cited by 5 (3 self)
- Add to MetaCart
(SEVECOM) has the aim to develop a future proof security solution for vehicular communication (VC). As there are no clear scenarios and standardized protocols for VC yet, traditional approaches for security engineering fail, as they usually consider a specific scenario and system. At the same time, VC encompasses dozens of potential applications with very diverse properties. At this point, it is hardly possible to discuss security and privacy issues of all these scenarios in detail. On the other hand, it might be problematic to leave out an important application with distinguished properties when creating the basis of security mechanisms. Therefore, we suggest a new approach that allows to analyze a large set of applications, select typical representatives that will cover the requirements of a whole cluster of applications and develop a security solution for this subset. Additionally, we also present the results of this process that give new insight into security requirements of VANETs. I.
Informal Requirements Analysis Supporting System for Human Engineer
- In Proceedings of Conference on IEEE-SMC99.Vol
, 1999
"... As software becomes more complicated and large-scaled, user's demands become various and the expectation level about a software product becomes higher. Therefore, it is very important that a software engineer analyzes user's requirements precisely and applies them effectively in the development step ..."
Abstract
-
Cited by 1 (1 self)
- Add to MetaCart
As software becomes more complicated and large-scaled, user's demands become various and the expectation level about a software product becomes higher. Therefore, it is very important that a software engineer analyzes user's requirements precisely and applies them effectively in the development step. This paper proposes a requirement analysis supporting system that effectively reduces and revises errors of requirements analysis. The proposed system measures the similarity between requirements specifications or sentences. It extracts the sentences that contain ambiguous words. An indexing method for the similarity measurement combines a sliding window model and a parser model. This method can complement each model's weak points. Using these methods in information retrieval, the proposed system supports a function to trace dependency between documents, improve completeness in a document, reduce inconsistency between sentences, and improve document quality. This paper verifies the efficie...
Implementation of an Efficient Requirements Analysis Supporting System Using Similarity Measure Techniques
, 2000
"... As software becomes more complicated and larger, software engineer's requirements analysis become important and uneasy activity. This paper proposes a requirements analysis supporting system that supports informal requirements analysis. The proposed system measures the similarity between requirement ..."
Abstract
- Add to MetaCart
As software becomes more complicated and larger, software engineer's requirements analysis become important and uneasy activity. This paper proposes a requirements analysis supporting system that supports informal requirements analysis. The proposed system measures the similarity between requirement sentences to identify possible redundancies and inconsistencies, and extracts the possible ambiguous requirements. The similarity measurement method combines a sliding window model and a parser model. Using these methods, the proposed system supports to trace dependency between documents and improve quality of requirement sentences. Efficiency of the proposed system and a process for requirement specification analysis using the system are presented. Key words Requirements engineering, natural language processing, software analysis, similarity measurements 1 Introduction Requirements analysis plays an increasingly important role in software development because most problems are caused by...

