Home About us Contact
|
Home About us Contact | ||
|
|
||
Requirements Analysis (requirement + analysis)
Selected AbstractsLazyBrush: Flexible Painting Tool for Hand-drawn CartoonsCOMPUTER GRAPHICS FORUM, Issue 2 2009Daniel Sýkora Abstract In this paper we present LazyBrush, a novel interactive tool for painting hand-made cartoon drawings and animations. Its key advantage is simplicity and flexibility. As opposed to previous custom tailored approaches [SBv05, QWH06] LazyBrush does not rely on style specific features such as homogenous regions or pattern continuity yet still offers comparable or even less manual effort for a broad class of drawing styles. In addition to this, it is not sensitive to imprecise placement of color strokes which makes painting less tedious and brings significant time savings in the context cartoon animation. LazyBrush originally stems from requirements analysis carried out with professional ink-and-paint illustrators who established a list of useful features for an ideal painting tool. We incorporate this list into an optimization framework leading to a variant of Potts energy with several interesting theoretical properties. We show how to minimize it efficiently and demonstrate its usefulness in various practical scenarios including the ink-and-paint production pipeline. [source] A goal-driven approach for service request modelingINTERNATIONAL JOURNAL OF INTELLIGENT SYSTEMS, Issue 8 2010Chiung-Hon Leon Lee We propose a goal-driven approach to model the service request intention in service-oriented systems. The service request intention can be extracted from the user input and modeled by predefined goal models. We identify this problem as the service request intention extraction. If a service-oriented system has the abilities of user's intention extraction and can make some activities to satisfy the extracted intention, the system can provide a more convenient and efficient service for the user. We start the system construction from the view of goal-driven requirements engineering. The requirements specification is generated by the goal-based requirements analysis in which the functional and nonfunctional requirements will be extended with goal models. A set of computable goal models that represent the user requirements is selected and refined as the basis of system services. The designer can also design related system services based on the requirements specification. Based on the proposed intention extraction approach, the user's vague and imprecise intention will be extracted and mapped to computer understandable and computable goal models for representing the intention. A case-based method is developed to implement the intention extraction process. The intention interpretation knowledge is stored in a case base, and the intention interpretation is based on the process of case retrieval and adaptation. A general architecture for an intention-aware service-oriented system is proposed for demonstrating how to apply the proposed approach. © 2010 Wiley Periodicals, Inc. [source] Consistent database sampling as a database prototyping approachJOURNAL OF SOFTWARE MAINTENANCE AND EVOLUTION: RESEARCH AND PRACTICE, Issue 6 2002Jesús Bisbal Abstract Requirements elicitation has been reported to be the stage of software development when errors have the most expensive consequences. Users usually find it difficult to articulate a consistent and complete set of requirements at the beginning of a development project. Prototyping is considered a powerful technique to ease this problem by exposing a partial implementation of the software system to the user, who can then identify required modifications. When prototyping data-intensive applications a so-called prototype database is needed. This paper investigates how a prototype database can be built. Two different approaches are analysed, namely test databases and sample databases; the former populates the resulting database with synthetic values, while the latter uses data values from an existing database. The application areas that require prototype databases, in addition to requirements analysis, are also identified. The paper reports on existing research into the construction of both types of prototype databases, and indicates to which type of application area each is best suited. This paper advocates for the use of sample databases when an operational database is available, as is commonly the case in software maintenance and evolution. Domain-relevant data values and integrity constraints will produce a prototype database which will support the information system development process better than synthetic data. The process of extracting a sample database is also investigated. Copyright © 2002 John Wiley & Sons, Ltd. [source] Building secure products and solutionsBELL LABS TECHNICAL JOURNAL, Issue 3 2007Ashok K. Gupta Many security vulnerabilities in current information technology (IT) solutions and products are the result of a piecemeal "strap-on" security approach. The inclusion of many security add-ons, such as firewalls, antivirus software, intrusion detection systems (IDSs), and intrusion prevention systems (IPSs), may imply that the security objectives were an afterthought, not adequately defined initially, or that the required security objectives were never met by the individual system components. In fact, a "grounds-up" approach to security, where each component is individually secure, in a defined network deployment scenario helps meet the need of minimal risk exposure. Security should not be bolted on; rather, it should be the prime consideration from the beginning and throughout the entire lifecycle,from concept to deployment and ongoing operation for each product in the solution. Given the ever-increasing sophistication of attacks, developing and monitoring secure products have become increasingly difficult. Despite the wide-scale awareness of common security flaws in software products, e.g., buffer overflows, resource exhaustion, and structured query language (SQL) injection, the same flaws continue to exist in some of the current products. The objective of this paper is to introduce a technology-agnostic approach to integrating security into the product development lifecycle. The approach leverages the Bell Labs Security Framework, the foundation of the International Telecommunication Union, Telecommunication Standardization Sector (ITU-T) X.805 global standard. Building this framework into the product lifecycle supports the goal of realizing secure products. The security framework can be applied to any product domain to facilitate security requirements analysis and the development of usable tools such as checklists, guidelines, and security policies. The application of Bell Labs Security Framework concepts and its use in the development of secure products are illustrated using the example of a centrally managed firewall product. © 2007 Alcatel-Lucent. [source] | ||||||||||