The Infona portal uses cookies, i.e. strings of text saved by a browser on the user's device. The portal can access those files and use them to remember the user's data, such as their chosen settings (screen view, interface language, etc.), or their login data. By using the Infona portal the user accepts automatic saving and using this information for portal operation purposes. More information on the subject can be found in the Privacy Policy and Terms of Service. By closing this window the user confirms that they have read the information on cookie usage, and they accept the privacy policy and the way cookies are used by the portal. You can change the cookie settings in your browser.
Requirements engineering (RE) for complex industrial systems can defy traditional processes and tooling. Some topics, such as managing requirements for contract based and regulated systems are rarely mentioned in the literature. Market forces such as increased staff turnover and reduced development times are changing the way products and services are defined. Other issues, such as eliciting, analyzing,...
A research has studied different views of suppliers and customers have of solution projects that include both provided goods and rendered services. The goal of the research is to help the suppliers and customers to understand each other better, and therefore make solution projects more profitable for the suppliers and be more effective for the customers. We are involved in an infrastructure improvement...
The authors identify, categorize, and name nine specific ethical and professional dilemmas in software engineering, placing them in the context of the IEEE code of conduct, with the hope that giving such behavior a name will increase awareness and decrease the frequency with which these dilemmas occur.
Industrial training imposes some unique restrictions on pedagogical methods, both in terms of ascertaining retention, fostering class participation, and reinforcement. The reinforcement pedagogical pattern has now been used successfully in training courses and workshops at Siemens AG with positive results. This brief paper describing the reinforcement pattern explains the rationale for the pattern...
In 2003, the Software & Engineering department (S&E) at Siemens Corporate Research (SCR) initiated the training of Siemens employees worldwide in requirements engineering (RE). The first courses taught were customized for the target audience and taught onsite. In 2005, a standardized foundation course was created; the first course in a suite of offerings. To date, the course has been taught...
Successful software development involves the elicitation, implementation, and management of critical systemic requirements related to qualities such as security, usability, and performance. Unfortunately, even when such qualities are carefully incorporated into the initial design and implemented code, there are no guarantees that they will be consistently maintained throughout the lifetime of the...
Empirical studies have shown that the use of a product line approach to software development can result in shorter time to market and improved productivity. Outsourcing and distributed development has added a new dimension to product management, exacerbating problems associated with transitioning from marketing studies to product definition to analysis and design. Communication problems can arise...
In global development projects, different modeling techniques are used to create and manage the requirements, analyze the problem domain, identify potential hazards and develop the system design. For each modeling technique, separate tools (e.g. UML case tool, requirements database, Word) are used. Each tool comes with its own meta-model, which hinders the interchange of models across tools and makes...
Models are frequently used for illustrations in software design documents. Commonly they are used to show static structure and less often, external dynamic behavior. However, in software engineering, the lack of conceptual models often inhibits creativity and understanding, which may in turn lead to incomplete or poor design. This paper describes our experience using models for the architectural,...
Automated traceability applies information-retrieval techniques to generate candidate links, sharply reducing the effort of manual approaches to build and maintain a requirements trace matrix as well as providing after-the-fact traceability in legacy documents.The authors describe nine best practices for implementing effective automated traceability.
Summary form only given. This talk describes experiences and lessons learned while defining product requirements for small and large companies over a thirty-year period. From 1969 to the present the author has assisted or led teams in the definition of requirements for a wide variety of products and systems, including music information, produce delivery, power and process control, baggage handling,...
Poirot is a Web-based tool supporting traceability of distributed heterogeneous software artifacts. A probabilistic network model is used to generate traces between requirements, design elements, code and other artifacts stored in distributed 3rd party case tools such as DOORS, rational rose, and source code repositories. The tool is designed with extensibility in mind, so that additional artifact...
Set the date range to filter the displayed results. You can set a starting date, ending date or both. You can enter the dates manually or choose them from the calendar.