物件導向軟體之架構(Object-Oriented Software Construction)探討

This paper presents an overview of the field of software systems requirements engineering (RE). It describes the main areas of RE practice, and highlights some key open research issues for the future.

/pdf/requirements-engineering-a-roadmap-3lcu5ikya8.pdf

Requirements engineering: a roadmap

The Object Management Group's (OMG) Model Driven Architecture (MDA) strategy envisages a world where models play a more direct role in software production, being amenable to manipulation and transformation by machine. Model Driven Engineering (MDE) is wider in scope than MDA. MDE combines process and analysis with architecture. This article sets out a framework for model driven engineering, which can be used as a point of reference for activity in this area. It proposes an organisation of the modelling 'space' and how to locate models in that space. It discusses different kinds of mappings between models. It explains why process and architecture are tightly connected. It discusses the importance and nature of tools. It identifies the need for defining families of languages and transformations, and for developing techniques for generating/configuring tools from such definitions. It concludes with a call to align metamodelling with formal language engineering techniques.

Model Driven Engineering

A method is demonstrated to prepare graphene dispersions at high concentrations, up to 1.2 mg mL(-1), with yields of up to 4 wt% monolayers. This process relies on low-power sonication for long times, up to 460 h. Transmission electron microscopy shows the sonication to reduce the flake size, with flake dimensions scaling as t(-1/2). However, the mean flake length remains above 1 microm for all sonication times studied. Raman spectroscopy shows defects are introduced by the sonication process. However, detailed analysis suggests that predominantly edge, rather than basal-plane, defects are introduced. These dispersions are used to prepare high-quality free-standing graphene films. The dispersions can be heavily diluted by water without sedimentation or aggregation. This method facilitates graphene processing for a range of applications.

/pdf/high-concentration-solvent-exfoliation-of-graphene-4bof0xqooc.pdf

High-concentration solvent exfoliation of graphene.

data types Sorting and searching parallel and distributed algorithms 3. [AR] Computer Architecture

/pdf/guide-to-the-software-engineering-body-of-knowledge-4x9ajlpq2m.pdf

Guide to the Software Engineering Body of Knowledge

Developing software systems that meet stakeholders' needs and expectations is the ultimate goal of any software provider seeking a competitive edge. To achieve this, you must effectively and accurately manage your stakeholders' system requirements: the features, functions, and attributes they need in their software system. Once you agree on these requirements, you can use them as a focal point for the development process and produce a software system that meets the expectations of both customers and users. However, in real world software development, there are usually more requirements than you can implement given stakeholders' time and resource constraints. Thus, project managers face a dilemma: how do you select a subset of the customers' requirements and still produce a system that meets their needs? The authors developed a cost-value approach for prioritizing requirements and applied it to two commercial projects.

A cost-value approach for prioritizing requirements

The potential role of natural language processing in the requirements engineering process has been overstated in the past, possibly due to fundamental misunderstandings of the requirements engineering process itself. Since more realistic ambitions are likely to lead to less disappointment in the future, an effort is made to identify some phases and tasks where natural language processing may usefully be applied. It is suggested that the validation of requirements must remain an informal, social process. >

/pdf/the-role-of-natural-language-in-requirements-engineering-22m3t8ur7p.pdf

The role of natural language in requirements engineering

An efficient, accurate and practical process for prioritising requirements is of great importance in commercial software developments This article improves an existing cost-value approach in which stakeholders compare all unique pairs of candidate requirements according to their value and their cost of implementation Techniques for reducing the required number of comparisons are suggested, thus making the process more efficient An initial approach for managing requirements interdependencies is proposed A support tool for the improved process has been developed to make the process more practical in commercial developments The improved process and its support tool have been applied and evaluated in an industrial project at Ericsson Radio Systems AB The results indicate a pressing need for mature processes for prioritising requirements, and the work presented here is an important step in that direction

Improved practical support for large-scale requirements prioritising

The effect of solvent choice on the mechanical properties of carbon nanotube–polymer composites

The choice of candidate requirements for implementation is a primary determinant of customer satisfaction. It is argued that a set of requirements should be chosen which reflects both the importance and the estimated cost of each candidate requirements. A contribution-based method is proposed which determines importance and estimates cost and industrial experience in applying this method is reported. The results indicate that the contribution of candidate requirements can vary by orders of magnitude. By applying the method, software managers are in a position to select requirements for implementation based on each candidate requirement's contribution.

Kevin Ryan

Papers

A cost-value approach for prioritizing requirements

The role of natural language in requirements engineering

Improved practical support for large-scale requirements prioritising

The effect of solvent choice on the mechanical properties of carbon nanotube–polymer composites

Supporting the selection of software requirements