Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.

N. A. Waldhart

dblp:22/1725 · DBLP profile ↗
← Back
1ranked-venue papers
1as first author
0since 2021 · last 1990
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Security and privacy · 1 · 1 first-author

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Software engineering, system software, and programming languages
1 paper
Operating systems · 100%
Computer architecture, parallel and distributed computing, and storage systems
1 paper
Embedded and real-time systems · 100%

Topics — the 3 heaviest of 3, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Operating systems › system security
multilevel security
0.011990
The Army Secure Operating System · S&P 1990
Operating systems › system security › operating system security
secure operating system
0.011990
The Army Secure Operating System · S&P 1990
Embedded and real-time systems
real-time operating systems
0.011990
The Army Secure Operating System · S&P 1990
YearPublicationVenuePosition
1990 The Army Secure Operating System
abstract
The Army Secure Operating System (ASOS) is a family of operating systems intended to serve the tactical needs of the US Army. It currently comprises two systems designed to be certifiable to classes C2 and A1 of the DoD Trusted Computer System Evaluation Criteria (TCSEC). Both operating systems provide a common user interface, support real-time applications written in Ada, and are configurable and easily portable to alternate hardware architectures. A brief overview of the development is presented, including a description of the hardware/software architecture, the current status of the project, and a review of lessons learned during the three year development.>
N. A. Waldhart
S&P1