| Home : Testing : Analysis Modeling |
| Click "Subscribe" if you want to be notified of new or updated links in this category. | Subscribe |
|
|
Analysis Modeling Listings
|
|
Total:
53 | Displaying: 1 - 10 | Pages: 1 2 3 4 5 6 >> |
|
|
|
Software development includes gathering information about tasks, work practices and design options from users. This project investigates a method of gathering requirements whereby users, working independent of software engineers, construct rough interfaces augmented with textual argumentation. Our initial study has compared the use of GRC with questionnaire-based requirements gathering. Author(s) : J. Michael Moore and Frank M. Shipman III
Updated: 10/08/2005
|
|
|
This article reviews some Web sites in the spirit of "mammals designed for fighting mastodons on the savanna have been reduced to fighting bugs in Windows 98". Author(s) : Robert Filman
Updated: 10/08/2005
|
|
|
This article provides suggested conditions for performing requirements gathering and recommended requirements gathering practices. The author has conducted an extensive review of industry literature and combined this with the practical experiences of a set of requirements analysts who have supported dozens of projects. Involving customers and users throughout the development effort results in a better understanding of the real needs. Author(s) : Dr. Ralph R. Young
Updated: 10/08/2005
|
|
|
This paper describes in detail the interaction that took place between an analyst and a client in a public sector agency in Tasmania, Australia. This paper shows how theory concepts were used in this case. The author also includes a general discussion of themes of other cases she has studied. Author(s) : *
Cathy Urquhart
Updated: 10/08/2005
|
|
|
On the basis that earlier analysis is better, a performance modeling capability has been installed in a scenario modeling tool for Use Case Maps that is part of a proposed standard for User Requirements Notation. Using examples, the paper shows how this kind of early analysis can address high-level performance questions, at a comparable level of abstraction to the specification. The imprecision of early knowledge, and the risk of ignoring some performance limitations, are key factors whose impact is addressed. Author(s) : Dorin Petriu and Murray Woodside
Updated: 10/08/2005
|
|
|
This slide presentation outlines the following topics: the purpose of analysis, sources of information, the goals of OO analysis, finding candidate classes, CRC analysis, modeling classes and attributes and operations. Author(s) : Author Unknown
Updated: 10/08/2005
|
|
|
A multiple viewed requirements technique deals with requirements analysis based on having available diverse multiple descriptions of software requirements. Because these multiple descriptions are often expressed in differing notation schemes based on differing underlying paradigms and methodologies, the problem of consistency and completeness is a significant impediment to obtaining a reliable set of requirements. This paper outlines part of an approach to these multiple-viewed requirements that provides some structure for integrating and validating multiple views. Author(s) : Harry S. Delugach
Updated: 10/08/2005
|
|
|
Quality attributes can be assumptions, constraints or goals of stakeholders. This paper presents a process to identify and specify quality attributes and to integrate them with functional requirements. The crosscutting nature of some of the quality attributes influences negatively, for example, reusability and traceability in the later stages of the software engineering process. To minimize that influence the paper begins by proposing a template to specify quality attributes at the requirements stage. Then, the use cases and sequence diagrams are extended to specify the integration of those attributes with functional requirements. Author(s) : Isabel Brito, Ana Moreira and Joao Araújo
Updated: 10/08/2005
|
|
|
This paper discusses three case studies in the lightweight application of formal methods to requirements modeling for spacecraft fault protection systems. Methods that were applied and findings are also addressed for each case study. Author(s) : Steve Easterbrook, Robyn Lutz, Richard Covington, John Kelly, Yoko Ampo and David Hamilton
Updated: 10/08/2005
|
|
|
This paper suggests an approach to software development that integrated elaboration of security requirements at an early stage of the software life cycle. Reasoning about security in goal-oriented requirements engineering allows one to anticipate malicious behaviors of agents in the environment of the software-to-be and thereby systematically build more robust systems. This paper elaborates attack patterns whose instantiation on a specific system will generate resolution strategies to avoid them, either by design strengthening or by some alternative design. Author(s) : Pierre-Jean Fontaine, Axel van Lamsweerde, Emmanuel Letier and Robert Darimont
Updated: 10/08/2005
|
|
|
Analysis Modeling Listings
|
|
Total:
53 | Displaying: 1 - 10 | Pages: 1 2 3 4 5 6 >> |
|
|
