10.46243/jstj.2017.v2.i1.135 registered
Significance of Software Layered Technology on Size of Projects
Resolves to https://www.jst.org.in/index.php/pub/article/view/135
Held by Longman Publishers (India) · prefix 10.46243 live · DOI address https://doi.org/10.46243/jstj.2017.v2.i1.135
Registered 29 Sep 2026 via crossref · record version 2 · last change 29 Sep 2026, 11:59 PM · record sha256 8ddd0f33bb9b0a49…
Resolve ⬇ Record (JSON) ⬇ Kernel Metadata Declaration (XML) Compare with Crossref Cite (APA · BibTeX · RIS · CSL)
What the DOI identifies
JournalArticle — an article in a journal · Digital · Visual · en
Significance of Software Layered Technology on Size of Projects (PrincipalTitle)
Published 2017-01-12
Part of Journal of Science & Technology · ISSN 2456-5660 · volume 02 · issue 01 · pages 46–58
Agents
- Jogannagari Malla Reddy (author)
- S.V.A.V. Prasad (author)
- B.V. Ramana Murthy (author)
- Longman Publishers (publisher)
Identifiers DOI 10.46243/jstj.2017.v2.i1.135
Abstract
The objective of the software engineering is committed to build software projects within the budget, time and required quality. Software engineering is a layered paradigm comprised of process, methods, tools and quality focus as bedrock to develop the product. Software firms build software projects of varying sizes constrained on resources, time and functional requirement. Impact of software engineering layered technology may vary according to the size of the projects during their development. Quantitative evaluation of layer significance on size of the software project could be categorized as a complex task because it involves a collective decision on multiple criteria. Analytic Hierarchy Process(AHP) provides an effective quantitative approach for finding the significance of software layered technology on size of the projects. This paper presents the estimations through quantitative approach on real time data collected from several software firms. These findings help for a better project management with respect to the cost, time and resources during building a softwareproject.
System metadata — ISO 26324:2025, Annex B · DOI Handbook 10.1
Each element by the standard's name (Annex B: reference elements, then administrative) and the Handbook's (in grey), read off the record above.
| Element | Value | In the record |
|---|---|---|
| DOI Name DOI name | 10.46243/jstj.2017.v2.i1.135 | doi |
| Referent Type referentType | Creation | referent |
| Referent Sub-Type referentSubType | JournalArticle — an article in a journal | type |
| Referent Name(s) referentName(s) | Significance of Software Layered Technology on Size of Projects (PrincipalTitle, en) | titles |
| Basic Metadata basicMetadata | author: Jogannagari Malla Reddy author: S.V.A.V. Prasad author: B.V. Ramana Murthy publisher: Longman Publishers published: 2017-01-12 part of: Journal of Science & Technology · ISSN 2456-5660 · vol. 02 · no. 01 · pp. 46–58 language: en form: Digital · Visual · Language | agents, dates, container, language, structural_type, modes, characters |
| Referent Identifier(s) alternateIdentifier(s) | none besides the DOI | identifiers, relations (IsSameAs) |
| Registration Authority registrationAuthorityCode | Crossref — issued by Crossref (member 25296); held here as a copy | record.source_agency (our code, ra_doi_name, for names issued here once appointed) |
| Created Date issueDate | 2026-09-07 | record.registered (when the DOI name was first registered) |
| relatedIdentifiers | none needed — the descriptive metadata is in this record | container, relations (only where the descriptive metadata lives at another identifier) |
complete Every System Metadata element is here, with the basic metadata a journal article needs.
The System Metadata Declaration (JSON) · the Kernel Metadata Declaration (XML) · what each sub-type needs
History — the ledger
Every change to this DOI, in order, as it was recorded. Entries are only ever added, never changed or removed.
| # | When | What | By | Changes |
|---|---|---|---|---|
| 1 | 29 Sep 2026, 10:00 PM | register registered at Crossref; record read from api.crossref.org | Administrator (admin) | 109 fields set · sha256 41a698852cbd… |
| 2 | 29 Sep 2026, 11:59 PM | update record re-read from api.crossref.org | Administrator (admin) | container.titles.0.value: |
Machine-readable: the history as JSON, with the full record after each change.
