Results 1 - 10
of
63
Use of A Taxonomy of Security Faults
, 1996
"... Security in computer systems is important so as to ensure reliable operation and to protect the integrity of stored information. Faults in the implementation of critical components can be exploited to breach security and penetrate a system. These faults must be identified, detected, and corrected to ..."
Abstract
-
Cited by 66 (3 self)
- Add to MetaCart
Security in computer systems is important so as to ensure reliable operation and to protect the integrity of stored information. Faults in the implementation of critical components can be exploited to breach security and penetrate a system. These faults must be identified, detected, and corrected to ensure reliability and safeguard against denial of service, unauthorized modification of data, or disclosure of information. We define a classification of security faults in the Unix operating system. We state the criteria used to categorize the faults and present examples of the different fault types. We present the design and implementation details of a prototype database to store vulnerability information collected from different sources. The data is organized according to our fault categories. The information in the database can be applied in static audit analysis of systems, intrusion detection, and fault detection. We also identify and describe software testing methods that should be effective in detecting different faults in our classification scheme.
The Authoring Process of the UML-based Web Engineering Approach
, 2001
"... We propose a precise UML-based authoring method for Web applications. This authoring method is part of the UML-based Web Engineering (UWE) approach. Starting with a requirement analysis done by use cases technique, it focuses on the design phase. The conceptual model of the application is used as gu ..."
Abstract
-
Cited by 41 (5 self)
- Add to MetaCart
We propose a precise UML-based authoring method for Web applications. This authoring method is part of the UML-based Web Engineering (UWE) approach. Starting with a requirement analysis done by use cases technique, it focuses on the design phase. The conceptual model of the application is used as guideline for modeling the navigation space. From the navigation space model we derive, in a next step, a navigation structure model which shows how to navigate through the navigation space using access elements like indexes, guided tours, queries and menus. Finally, a presentation model is constructed based on the navigation structure model. It provides an appropriate UML notation to support sketching and storyboarding. In addition, we suggest to use UML interaction diagrams to represent the presentation flow. During the whole development process we identify steps that can be performed in an automatic way thus providing the basis for a generation mechanism for Web application design. The different models of the design process are represented by using a UML conform extension of UML for Web applications (UML profile). The authoring process is illustrated with an example: a Web--based conference review system. The strength of the presented Web engineering approach is given by the fact that we use exclusively the UML notation and techniques. Moreover, our specification of constraints with OCL (part of UML) allows augmenting the exactitude of the models. In the same way our methodology has a high degree of precision in the description of guidelines of the authoring process of Web application, which can even partially be automated. Keywords: Web Engineering, Unified Modeling Language, Web applications, Authoring Process, Design Method, Systematic Development, UML Extension 1
A Taxonomy of Security Faults in the Unix Operating System
, 1995
"... ix 0.1 An Overview of Software Testing Methods # # # # # # # # # # # # # # # 2 0.2 Provable Security and Formal Methods # # # # # # # # # # # # # # # # # 9 0.3 Security Testing # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # 10 0.4 Applications of Fault Categories # # # # # # # # # # # # ..."
Abstract
-
Cited by 31 (1 self)
- Add to MetaCart
ix 0.1 An Overview of Software Testing Methods # # # # # # # # # # # # # # # 2 0.2 Provable Security and Formal Methods # # # # # # # # # # # # # # # # # 9 0.3 Security Testing # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # 10 0.4 Applications of Fault Categories # # # # # # # # # # # # # # # # # # # # # 11 0.5 Organization of the Thesis # # # # # # # # # # # # # # # # # # # # # # # # 12 1. RELATED WORK # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # 14 1.1 Protection Analysis Project # # # # # # # # # # # # # # # # # # # # # # # 14 1.2 RISOS Project # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # 19 1.3 Flaw Hypothesis Methodology # # # # # # # # # # # # # # # # # # # # # # 21 1.4 Case Study# Penetration Analysis of the Michigan Terminal System # 23 1.5 Software Fault Studies # # # # # # # # # # # # # # # # # # # # # # # # # # 25 1.5.1 Fault Categories # # # # # # # # # # # # # # # # # # # # # # # # # # 27 1.6 Errors of T E X # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # 31 1.7 A Taxonomy of Computer Program Security Flaws # # # # # # # # # # 32 1.8 Comparison of Security Fault Classi#cation Schemes # # # # # # # # # # 33 2. A TAXONOMY OF SECURITY FAULTS IN THE UNIX OPERATING SYSTEM # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # 35 2.1 A Taxonomy of Security Faults # # # # # # # # # # # # # # # # # # # # # 36 2.2 Con#guration Errors # # # # # # # # # # # # # # # # # # # # # # # # # # # 40 2.2.1 Examples # # # # # # # # # # # # # # # # # # # # # # # # # # # # # 40 2.3 Synchronization Errors # # # # # # # # # # # # # # # # # # # # # # # # # # 41 2.3.1 Example # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # 41...
Towards Automatic Debugging of Computer Programs
, 1991
"... Programmers spend considerable time debugging code. Symbolic debuggers provide some help but the task still remains complex and difficult. Other than breakpoints and tracing, these tools provide little high level help. Programmers must perform many tasks manually that the tools could perform automat ..."
Abstract
-
Cited by 27 (3 self)
- Add to MetaCart
Programmers spend considerable time debugging code. Symbolic debuggers provide some help but the task still remains complex and difficult. Other than breakpoints and tracing, these tools provide little high level help. Programmers must perform many tasks manually that the tools could perform automatically, such as finding which statements in the program affect the value of an output variable under a given testcase, what was the value of a given variable when the control last reached a given program location, and what does the program do differently under one testcase it does not do under another. If the debugging tools provided explicit support for such tasks, the whole debugging process would be automated to a large extent.
Extending the Test Template Framework for specification-based testing of interactive systems
- Proceedings of the 1993 International Symposium on Software Testing and Analysis (ISSTA
, 1999
"... s and compressed postscript les are available via http://svrc.it.uq.edu.au Extending the Test Template Framework for specication-based testing of interactive systems Ian MacColl David Carrington Abstract In this paper we introduce a framework for specication-based testing of interactive system ..."
Abstract
-
Cited by 26 (4 self)
- Add to MetaCart
s and compressed postscript les are available via http://svrc.it.uq.edu.au Extending the Test Template Framework for specication-based testing of interactive systems Ian MacColl David Carrington Abstract In this paper we introduce a framework for specication-based testing of interactive systems. Interactive systems can be analysed and developed in terms of functionality, presentation and behaviour. Testing information for interactive systems can be derived from formal specications of these aspects. The paper uses the Multi-modal Airline Travel Information System (MATIS) specication of Duke and Harrison which provides a partial specication for each aspect. We derive testing information from the specications of functionality and behaviour, and we extend the Test Template Framework to encompass behavioural testing information. 1 Introduction An interactive system is one in which \each user entry causes a response from or action by the system" [IEEE, 1990]. Interaction...
A Survey of Formal Concept Analysis Support for Software Engineering Activities
- In Gerd Stumme, editor, Proceedings of the First International Conference on Formal Concept Analysis - ICFCA’03
, 2003
"... Abstract. Formal Concept Analysis (FCA) has typically been applied in the field of software engineering to support software maintenance and object-oriented class identification tasks. This paper presents a broader overview by describing and classifying academic papers that report the application of ..."
Abstract
-
Cited by 26 (5 self)
- Add to MetaCart
Abstract. Formal Concept Analysis (FCA) has typically been applied in the field of software engineering to support software maintenance and object-oriented class identification tasks. This paper presents a broader overview by describing and classifying academic papers that report the application of FCA to software engineering. The papers are classified using a framework based on the activities defined in the ISO12207 Software Engineering standard. Two alternate classification schemes based on the programming language under analysis and target application size are also discussed. In addition, the authors work to support agile methods and formal specification via FCA is introduced. 1
An Integrated Toolset for Engineering Software Configurations
- Proceedings of the ACM SIGSOFT/SIGPLAN Software Engineering Symposium on Practical Software Development Environments, ACM
, 1989
"... Configuration management in toolkit oriented software development environments (SDE), such as the UNIX+ system, is a long standing nuisance. Mostly,one has to face the choice between poorly or not at all integrated, independent tools, or highly integrated, most specialized, and often language depen ..."
Abstract
-
Cited by 19 (0 self)
- Add to MetaCart
Configuration management in toolkit oriented software development environments (SDE), such as the UNIX+ system, is a long standing nuisance. Mostly,one has to face the choice between poorly or not at all integrated, independent tools, or highly integrated, most specialized, and often language dependent environments. The first choice offers very limited support for a complex task that needs a broad informational basis. The second choice often takes away the programmers' most cherished tools, forces him to adopt some different work discipline, and thereby eventually restricts his creativity.The toolset described in this paper integrates a dedicated version control system and shape,a significantly enhanced Make [Feld79a] program, on the basis of a common object model. This object model comprises multiple versions of software objects as well as conventional file system objects. Taking this approach made it possible to have a sufficiently integrated toolsystem for engineering software con...
Using Dependency Charts to Improve Scenario-Based Testing -Management of Inter-Scenario Relationships: Depicting and Managing Dependencies . . .
- Proceedings of the 17th International Conference on Testing Computer Software (TCS2000), Washington D.C
, 2000
"... Scenarios (use cases) are used in many modern software engineering methods for capturing requirements and specifying a system. Yet prominent and renowned approaches like the UML (Unified Modeling Language [1]) are missing a concept for modeling dependencies and relations between scenarios and offer ..."
Abstract
-
Cited by 17 (0 self)
- Add to MetaCart
Scenarios (use cases) are used in many modern software engineering methods for capturing requirements and specifying a system. Yet prominent and renowned approaches like the UML (Unified Modeling Language [1]) are missing a concept for modeling dependencies and relations between scenarios and offer only little support for the management and description of scenarios and inter-scenario relationships. Furthermore, analysis scenarios are hardly ever used in testing, even though scenarios form a kind of abstract test cases. In this paper we introduce a new kind of chart and a notation to model dependencies between scenarios. We call it dependency chart. We introduce a method to use scenarios and dependency charts in testing to support testers to systematically develop test cases for system test. Keywords Scenario, use case, scenario-based testing, dependencies between scenarios, scenario management 1 INTRODUCTION Validation and verification (V&V) are important activities in developing ...
Software Maintenance from a Service Perspective
, 2000
"... In this paper we investigate the differences between software maintenance and software development from a service point of view, and the consequences thereof for the maturity of software maintenance organizations. We argue that software maintenance can be seen as providing a service, whereas softwar ..."
Abstract
-
Cited by 17 (2 self)
- Add to MetaCart
In this paper we investigate the differences between software maintenance and software development from a service point of view, and the consequences thereof for the maturity of software maintenance organizations. We argue that software maintenance can be seen as providing a service, whereas software development is concerned with the development of products. Differences between products and services affect the way in which customers assess their respective quality. Consequently, customers will judge the quality of software maintenance differently from that of software development. This in turn implies a need for different processes than those used by the average software development organization. We discuss two overall approaches to achieve a high-quality IT service organization which include these service-specific processes: ITIL and the IT Service Capability Maturity Model. ITIL is a set of best practices widely used within the IT service industry. The IT Service CMM is a maturity growth model akin to the Software CMM.

