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.
? Tutorial for this page

Raghubir N. Mathur

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

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

Software engineering, systems software and programming languages · 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
Requirements engineering and software design · 100%

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

TopicWeightPapersLastEvidence papers
Requirements engineering and software design
software design methodology
0.011987
Methodology for Business System Development · IEEE Trans. Software Eng. 1987
Requirements engineering and software design › design process
structured design
0.011987
Methodology for Business System Development · IEEE Trans. Software Eng. 1987

Methods — techniques the papers use, named apart from their topics

thread definition · 0.0system verification diagrams · 0.0structured design · 0.0
YearPublicationVenuePosition
1987 Methodology for Business System Development
abstract
The methodology presented here is currently being used in the design of Standard Automated Financial System (STAFS), which is a large scale business system for use by the 14 Naval Laboratories across the nation. The system will be operational in 1987-1988 time-frame. The methodology presented is suitable for all transaction oriented systems. It enforces documentation of design at all levels of system development process allowing managers and users a high visibility into the design. It highlights the human engineering aspects of system design and utilizes thread definition, data designer, and structured design techniques. The methodology requires the use of system verification diagrams which specify the user requirements. The design produces an integrated database with security mechanisms to restrict unauthorized users from accessing data they are not authorized to use. The threads also serve as a useful tool for system testing.
Raghubir N. Mathur
IEEE Trans. Software Eng.1