2015
DOI: 10.14257/ijseia.2015.9.7.02
|View full text |Cite
|
Sign up to set email alerts
|

Towards a Development of an Operational Process for Software Requirements: Case study application for Renewable Energy Software's

Abstract: Abstract

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2

Citation Types

0
2
0

Year Published

2017
2017
2021
2021

Publication Types

Select...
2
1

Relationship

2
1

Authors

Journals

citations
Cited by 3 publications
(2 citation statements)
references
References 5 publications
0
2
0
Order By: Relevance
“…During this phase, the detailed plan should provide a systematic and step at a time process. The design process in engineering projects has the maturity of the work efforts, time and cost of the product Indonesian J Elec Eng & Comp Sci ISSN: 2502-4752  A sustainable procedural method of software design process improvements (Khalid T. Al-Sarayreh) 441 [3][4][5], even though the engineering and scientific design life cycle is not the same as the software life cycle. However, the scientific design process [6] is a set of the design steps used to explore and predict solutions for most of the time for innovative software, engineering products or a combination of both.…”
Section: Introductionmentioning
confidence: 99%
“…During this phase, the detailed plan should provide a systematic and step at a time process. The design process in engineering projects has the maturity of the work efforts, time and cost of the product Indonesian J Elec Eng & Comp Sci ISSN: 2502-4752  A sustainable procedural method of software design process improvements (Khalid T. Al-Sarayreh) 441 [3][4][5], even though the engineering and scientific design life cycle is not the same as the software life cycle. However, the scientific design process [6] is a set of the design steps used to explore and predict solutions for most of the time for innovative software, engineering products or a combination of both.…”
Section: Introductionmentioning
confidence: 99%
“…Many software products failed to deliver because of poorly identified and measured requirements, including security requirements. Software engineers have no consensual reference model [3][4][5][6] that is built based on consolidated different industrial views and on different types of international standards to justify the need for such software requirements [4][5][6][7][8]. Accordingly, the identification of security requirements, for example, is delayed in the software process, hence they are specified vaguely.…”
Section: Introductionmentioning
confidence: 99%