Reference Library Analysis Modeling
	This page provides access to a variety of downloadable papers that address analysis modeling issues. The following topics are considered: Requirements Gathering General Modeling Object-Oriented Analysis (OOA) Modeling Patterns Unified Modeling Language (UML) Related Issues Use-case Methods Gathering A Comparison of Questionnaire-Based and GUI-Based Requirements Gathering [PDF] J. Michael Moore and Frank M. Shipman III 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. Defining Stakeholder Relationships [PDF] *FEE* Harold W. Lawson This article discusses two case studies that demonstrate the importance and versatility of the ISO/IEC 12207 standard Software Life Cycle Processes. Gathering Requirements from Remote Users [PDF] *FEE* T. Leonard, V. Berzins and M.J. Holden This paper describes a distributed requirements engineering environment the authors created using Microsoft's Personal Web Server (PWS), Microsoft's Open Database Connectivity (ODBC) technology, Netscape Communicator, Microsoft's Internet Explorer, Microsoft's Access97 database and PERL scripts. The authors then show how they added basic security to the Internet accessible database. Hunting and Gathering [PDF] Robert Filman 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". Recommended Requirements Gathering Practices [PDF] Dr. Ralph R. Young 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. Themes in Early Requirements Gathering The Case of the Analyst, the Client and the Student Assistance Scheme [PDF] *FEE* Cathy Urquhart 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. Back to the top General Analyzing Software Requirements Specifications for Performance [PDF] Dorin Petriu and Murray Woodside 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. Analysis (part 1) [PDF] Author Unknown 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. An Approach to Conceptual Feedback in Multiple Viewed Software Requirements Modeling [PDF] Harry S. Delugach 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. A Requirements Model for Quality Attributes [PDF] Isabel Brito, Ana Moreira and Joao Araújo 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. Computer-Assisted Analysis and Refinement of Informal Software Requirements Documents [PDF] *FEE* Jacob L. Cybulski and Karl Reed This paper describes RARE (Reuse-Assisted Requirements Elicitation), a method enabling software requirements engineers to process informal software requirements effectively. RARE's object is to assist analysts in transforming requirements expressed in natural language into a comprehensive collection of rigorous specifications that can be used as a starting point in software development. Experiences Using Lightweight Formal Methods for Requirements Modeling [PDF] Steve Easterbrook, Robyn Lutz, Richard Covington, John Kelly, Yoko Ampo and David Hamilton 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. Goal-Oriented Elaboration of Security Requirements [PDF] Pierre-Jean Fontaine, Axel van Lamsweerde, Emmanuel Letier and Robert Darimont 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. Knowledge Structuring and Representation in Requirement Specification [PDF] Egidio Astesiano and Gianna Reggio This paper proposes a way of structuring and representing the Requirements Specification artifacts that presents a number of novelties w.r.t. the best-known current methods. A more refined and stringent structuring of the Requirements Specification may help the specification process and make consistency checks easier. 2. Requirements Analysis [PDF] J. Denzinger This slide presentation outlines the requirements specification, customer requirements document, the software requirements analysis process, the analysis steps, communication basics, analysis principles, guidelines, modeling, requirements notations, and the software requirements document. Lecture 14: Requirements Analysis [PDF] Steve Easterbrook This slide presentation outlines the basic requirements process (requirements in the software lifecycle, the essential requirements process), what a requirement is (what vs. how, machine domain vs. application domain, implementation bias), non-functional requirements, notations, techniques and methods and notations, techniques and methods (elicitation techniques, modeling methods). Requirements Analysis and the Unified Process [PPT] Author Unknown This PowerPoint presentation's topics include: what is requirements analysis, the Unified Process, and OO analysis and design including the basics, UML, actors and use cases. Requirements Development in Scenario-Based Design [PDF] *FEE* John M. Carroll, Mary Beth Rosson, George Chin Jr. and Jürgen Koenemann This paper discusses a case study involving a group of teachers and system developers who set out to create a virtual physics laboratory. This process of requirements development in this case study is analyzed. Scenario-Based Requirements Analysis [PDF] Alistair Sutcliffe A method for scenario based requirements engineering is described. The method uses two types of scenarios, structure models of the system context and scripts of system usage. A modeling language is reported for describing scenarios, and heuristics are given to cross check dependencies between scenario models and the requirements specification. Scenario - Based Techniques for Supporting the Elaboration and the Validation of Formal Requirements [PDF] Patrick Heymans and Eric Dubois This paper focuses on the language Albert II, a formal language designed for the purpose of expressing requirements for distributed real-time systems. It presents two contributions supporting its use. The first contribution aims at improving the elaboration process by providing a method for constructing an Albert II description from scenarios expressing the stakeholders' requirements. The second contribution takes the form of a requirements validation tool (a so-called animator) that the stakeholders can use interactively and cooperatively in order to explore different possible behaviors (or instance-level scenarios) of the future system. The Missing Piece of Software Development [DOC] *FEE* Alan M. Davis and Ann S. Zweig This paper is about the missing piece of software development: software product planning. The wrong systems are being built. Software product planning is the activity of selecting the product to be built. The Requirements Iceberg and Various Icepicks Chipping at it [PDF] Daniel M. Berry This slide presentation covers requirements engineering in the following topics: lifecycle models, conceptual problems, cost, myths and realities, E-type systems, where requirements come form, formal methods, software and mathematical theories, requirement errors, requirements and other engineering, requirements engineering lifecycle, an overview of research, and the future. Back to the top Modeling Chapter 3 Developing Object Oriented Software (Requirements Modeling) [PDF] D.E Abel and J. Orr Class lecture slides on requirements modeling, functional use cases and operation scenarios, list actors and external systems, developing use case diagrams and reviewing against the architectural model. Introduction to CRC Cards [PDF] David M. Rubin This paper begins with an introduction to CRC (Class-Responsibility-Collaborator) Card Modeling which is a tool used in the collaborative design of a system. Other topics include: the CRC team, the CRC environment, the CRC session and miscellaneous techniques. Object Modeling with OMG UML Tutorial Series Behavioral Modeling [PDF] Gunnar Övergaard , Bran Selic, Conrad Bock and Morgan Björkander This slide presentation gives an UML quick tour, outlines behavioral modeling including interactions and collaboration, statecharts and activity graphs. Requirements Modeling [PDF] Author Unknown This slide presentation outlines the architecture, system interface prototypes and a use case model for requirements modeling. Requirements Modeling Technology A Vision for Better, Faster and Cheaper Systems [PDF] Darrell Barker This paper discusses a vision, motivation, and objectives for a new engineering technology based on the Rosetta System Level Design Language (SLDL) that is called "requirements modeling". Requirements modeling is what systems engineers and systems analysts do with Rosetta SLDL. Rosetta SLDL is information technology that supports the specification of multi-technology, multi-faceted, multi-discipline systems. SM2SMV - A Tool for Facilitating Dependable Software Requirements Analysis Using Model Checking [PDF] Huigang Li, Andrew J. Kornecki and David P Gluch This paper discusses experiments applying SMV (Symbolic Model Verifier), a tool used in model checking, to verify system requirements. The results are that since the second phase of the SMV involves a translation from a state machine diagram to SMV input code, this could be done with a software tool. State-Machine-Based User-Interface Specification [PDF] L.M.F. Carneiro-Coffin, M.H. Coffin, D.D. Cowan and C.J.P. Lucena JASMINUM (Joining ADVs and State Machines in a Notation for User-Interface Modeling) is a new visual formalism for designing interactive systems. JASMINUM is state-machine and event-oriented and is based on earlier research on visual formalisms (statecharts and objectcharts). JASMINUM has a number of advantages over other visual formalisms for specifying interactive systems since it handles aspects of design specific to those types of systems, including focus of control, the specification of concurrent operation of the components of a user interface, and the relationship of the various user-interface components. Back to the top Object-Oriented Analysis (OOA) Modeling A Process for Combining Object Oriented and Structured Analysis and Design [PDF] Dale M. Richman By using both OO models and structured models (e.g., data flow diagrams, control flow diagrams, state transition tables) during systems analysis, a more complete understanding of the system requirements can be developed. During the design process, the software architecture components can be designed and built either as OO modules or structured modules depending upon the requirements of the module. Since both views of the system (OO and structured) have been built during the analysis phase, there is no "translation/conversion" from one methodology to the other. By combining models and approaches from both OO and structured methods in one process we can take advantage of the strengths of both methodologies. Lecture 8: Introduction to OO Analysis (By Example) [PDF] Kenneth M. Anderson This slide presentation outlines an overview of OO analysis, use cases, activity diagrams, interaction diagrams (sequence and collaboration), and statechart diagrams. The KEY System: Integrating Object-Oriented Design and Formal Methods [PDF] Wolfgang Ahrendt, Thomas Baar, Bernhard Beckert, Martin Giese, Reiner Hähnle, Wolfgang Menzel, Wojciech Mostowski and Peter H. Schmitt This paper gives a brief description of the KeY system, a tool written as part of the ongoing KeY project1, which is aimed at bridging the gap between (a) OO software engineering methods and tools and (b) deductive verification. The KeY system consists of a commercial CASE tool enhanced with functionality for formal specification and deductive verification. The Knight Project: Supporting Collaboration in Object-Oriented Analysis and Design [PDF] Klaus Marius Hansen Object-oriented analysis and design benefits from active collaboration between developers and users. Based on user studies of collaborative modeling practice, the department of computer science of the university of Aarhus are developing a tool, called Knight, for supporting this active collaboration. By combining a large shared screen with gesture recognition and zoom-able interfaces, Knight allows the collaborative construction of UML based models mixed with informal drawings. This position paper thus presents a novel approach to narrowing the gap between developers and users. Chapter 2 Underpinnings of Requirements Analysis [PDF] L.A. Maciaszek This slide presentation outlines the following topics: fundamentals of object technology (instance object, class, association, aggregation and composition, generalization, and class object), and problem statements for case studies. Back to the top Patterns AI Analysis Patterns as UML Meta-Model Constructs [PDF] Angeles Manjarrés, Gerson Sunyé, Damien Pollet, Simon Pickin and Jean Marc Jézéquel This article investigates the use of the OO computational paradigm for the formulation of knowledge model patterns as OO analysis patterns. The authors seek to take advantage of research on design pattern specification, aimed at modeling patterns by means of structural and behavioral "meta-level" constraints, introducing appropriate modifications into the UML. They illustrate their argument with the formulation of an OO "assessment pattern" in analogy to the well known "assessment task template". Analysis Patterns [PDF] Martin Fowler This slide presentation begins with an introduction to using analysis patterns. Other topics include observation patterns, accounting patterns and how to use patterns. A Pattern Language for Building Stable Analysis Patterns [PDF] Haitham Hamza and Mohamed E. Fayad One of the common problems with today's analysis patterns is the lack of stability. In many cases, analysis pattern that model specific problems fail to model the same problem when it appears in different context, forcing software developers to analyze the problem from scratch. As a result, the reusability of the pattern will diminish. This paper presents a pattern language for building stable analysis patterns. The objective of this language is to propose a way of achieving stability while constructing analysis patterns. Building Systems Using Analysis Patterns [PDF] Eduardo B. Fernandez This paper considers the use of analysis patterns in the definition of initial object-oriented models. In particular, large patterns are considered, as opposed to the small analysis patterns shown in most of the current literature, and analogy is used in carrying over the patterns between applications. The author believes that this approach produces a software architecture that is more flexible and reusable than approaches applying patterns at a later stage. Interaction Patterns that Support Intellectual Creative Tasks [PDF] Kumiyo Nakakoji This slide presentation's topics include: a spectra of computation support, integration of the support, interaction patterns, and cognitive modes. Model-based Software Reuse Using Stable Analysis Patterns [PDF] Haitham Hamza and Mohamed E. Fayad Software analysis patterns are recurring and reusable models. However, there are several deficiencies with analysis patterns. These deficiencies make it difficult to use analysis patterns as efficient reusable artifacts. This paper proposes eight essential properties to evaluate pattern reusability. In addition, the concept of Stability Analysis Patterns is introduced. This paper contrasts stable analysis patterns with some analysis patterns using the proposed properties. Semantic Analysis Patterns [PDF] Eduardo B. Fernandez and Xiaohong Yuan Analysis patterns can contribute more to reusability and software quality than the other varieties. Also, their use contributes to simplifying the development of the analysis model. In particular, a new type of analysis pattern is proposed, called a Semantic Analysis Pattern (SAP), which is in essence a miniapplication, realizing a few Use Cases or a small set of requirements. Using SAPs, a methodology is developed to build the conceptual model in a systematic way. Back to the top Unified Modeling Language (UML) Related Issues A Framework of Requirements Tracing using UML [PDF] *FEE* Toshihiko Tsumaki and Yoshitomi Morisawa This paper discusses requirements tracing and the two functions of requirement tracing: change tracking and influence analysis. These were examined using class diagrams, use-case diagrams and sequence diagrams. Formalizing the Use of UML in Requirements Analysis [PDF] Zhiming Liu, Jifeng He and Xiaoshan Li This paper attempts to develop a method to support the formal use of UML in software development for object-oriented software. The method contains formal definitions of modeling units in UML used to relate different models in different stages. This paper discussed UML models used in a requirements analysis: use case and conceptual. Problems and Deficiencies of UML as a Requirements Specification Language [PDF] Martin Glinz In recent years, UML has become a standard language for modeling software requirements and design. This paper investigates the suitability of UML as a semiformal requirements specification language. Using the Teleservices and Remote Medical Care (TRMCS) case study as an example, this paper identifies and demonstrates various problems and deficiencies of UML, particularly concerning use case models and system decomposition. The paper also investigates whether and how the deficiencies can be overcome and how potential alternatives could look. Rational Rose [PDF] Rational Software Corporation This article about rational rose covers the following topics: visual modeling for the entire team, harness the power of rational rose, accelerate development through architecture excellence and why rational rose is the world's leading modeling tool. UML - Based Analysis [PDF] Alfred Strohmeier This slide presentation on UML-based analysis covers the following topics: purpose and process of analysis, domain class model, system context model, analysis class model, analysis behavior model = system operation model + system interface protocol, system operation model, system interface protocol, and detailed process of analysis. Back to the top Use-case Methods A Pragmatic Approach to Use Cases [PDF] Jurgen Börstler, Thomas Boman and Katarina Sigerud This paper describes a pragmatic approach to use cases and how this approach is embodied in the prototype tool RECORD (REquirements COllection, Reuse, and Documentation). RECORD provides a form-based user interface for stakeholders to input their requirements. These forms are analyzed to generate initial object models, which can be used to query a repository for matching object models. In addition a set of hypertext documents documenting the use cases are produced, their interrelationships, as well as their relationships to the generated and/or reused object models. A Use-Case Driven Method of Architecture Recovery for Program Understanding and Reuse Reengineering [PDF] *FEE* Dragan Bojic and Dusan Velasevic This paper proposes a method for architectural recovery for program understanding and reuse reengineering of legacy object-oriented systems. The method uses dynamic analysis on test cases covering relevant use cases. A Use Case Template: Draft for Discussion [PDF] Derek Coleman In the author's experience, most users find it convenient to follow Jacobson's original style of natural language descriptions embedded in a table. The problem is that the original proposal was incomplete. The absence of a UML standard means that users are likely to continue to invent their own format and thus continue the proliferation of use case variants. This document outlines a syntax and informal semantics for use case templates and for the uses and extends relationships between use cases. Be Careful with "Use Cases" [PDF] Edward V. Berard This paper discusses the confusion that may result from using use cases. This paper presents a history of use cases. Use cases are then defined and potential problems are presented. Design Patterns with Use Case Maps: A Case Study in Reengineering an Object-Oriented Framework [PDF] R.J.A. Buhr, R.S. Casselman and T.W. Pearce This paper shows how a new technique called use case maps helps humans to understand, capture, analyze, reuse, and change high-level behavior patterns in complex software. This is done through the example of reengineering an object-oriented framework, a type of software that is well known to be difficult to understand. Essential Use Cases and Responsibility in Object-Oriented Development [PDF] Robert Biddle, James Noble and Ewan Tempero Typically using essential use cases requires a translation to conventional use cases. This paper describes how essential use cases can be used directly without a translation. This paper also presents some benefits of using essential use cases. Functional Requirements and Use Cases [PDF] Ruth Malan and Dana Bredemeyer This paper gives an overview of functional requirements and use-cases. Use case guidelines and the role of use cases in the architecting process are also discussed. Requirements Use Case Tool [PDF] James R. McCoy This slide presentation on Requirements Use case Tool (RUT) topics include: an overview of UML, the use case model, use case diagrams, validating use cases, RUT features, and RUT screen shots. The Art of Use Cases [HTM] Laura Drabik This article presents recommendations of the use case process. Topics include: preparation, conduct the sessions, use case document, communication and acceptance. UML Use Case Diagrams [PDF] Author Unknown This paper discusses in detail the UML use case diagrams using an example: sales clerk checks out an item. Use and Abuse Cases [PDF] Martin Fowler This article focuses on use cases and problems of use cases that are not well understood. The author shares some cases of abuse and how he thinks they can be avoided. 3.1 Use Cases [PDF] J.W. Schmidt and F. Matthes This slide presentation's topics include: an introduction to use cases, user goals and system interactions, human and system actors, the extends relationship between use cases, the uses relationship between use cases, and usage of use cases in objectory. Use Case Authoring: Replicating the CREWS Guidelines Experiment [PDF] Karl Cox and Keith Thomas Phalp As part of a welcome and important research project into the use of scenarios in requirements engineering, the CREWS team has proposed a set of guidelines for writing use-case descriptions. This paper describes the replication of a CREWS project experiment that suggests CREWS use-case authoring guidelines improve the completeness of use-case descriptions. The results show that the CREWS guidelines do not necessarily improve the use-case descriptions, only that the subjects implemented varying numbers of guidelines in their use-case descriptions. Use Case Maps as a Feature Description Notation [PDF] Daniel Amyot This paper proposes Use Case Maps (UCMs) as a notation for describing features. UCMs capture functional requirements in terms of causal scenarios bound to underlying abstract components. This particular view proved very useful in the description of a wide range of reactive and telecommunications systems. This paper presents some of the most interesting constructs and benefits of the notation in relation to a question on a User Requirements Notation recently approved by ITU-T Study Group 10, which will lead to a new Recommendation by 2003. Back to the top