Applying the SCR method in software requirements specifications

2002 ◽  
Author(s):  
T.G. Kirner
Keyword(s):  
Software Requirements ◽  
Requirements Specifications

scholarly journals Software Requirement Specification Sistem Informasi Manajemen Rumah Makan Berdasarkan ISO/IEC/IEEE 29148-2018

2020 ◽  
Vol 9 (2) ◽  
pp. 215
Author(s):  
Dwi Januarita AK
Keyword(s):  
Information System ◽  
Rapid Development ◽  
Software Requirements ◽  
Business World ◽  
Requirements Specifications ◽  
Standard Information ◽  
Software Requirements Specification ◽  
Specification Document ◽  
Software Requirement Specification ◽  
Reference Document

The rapid development of technology makes this technology have an impact on many fields, one of which is the business world. The number of businesses that have emerged both small and large businesses that have an impact on competition between these businesses. Today, business in the culinary field is getting tougher. The culinary business sector of restaurants is increasingly popping up in this age. We need to overcome the competition in the emerging restaurant business. By using the stages of making software requirements specifications based on ISO / IEC / IEEE 29148-2018, this restaurant business will have an international standard information system. The result of this method is a software requirements specification document (SKPL) as a reference document for all activities carried out during the development of this information system.

Software Requirements Risk and Maintainability

2005 ◽  
pp. 2562-2566
Author(s):  
Norman F. Schneidewind
Keyword(s):  
Risk Factors ◽  
Life Cycle ◽  
Software Metrics ◽  
Space Shuttle ◽  
Software Requirements ◽  
Requirements Specifications ◽  
Requirements Change ◽  
Code Metrics ◽  
Change Requests

In order to continue to make progress in software measurement, as it pertains to reliability and maintainability, there must be a shift in emphasis from design and code metrics to metrics that characterize the risk of making requirements changes. By doing so, the quality of delivered software can be improved because defects related to problems in requirements specifications will be identified early in the life cycle. An approach is described for identifying requirements change risk factors as predictors of reliability and maintainability problems. This approach can be generalized to other applications with numerical results that would vary according to application. An example is provided that consists of 24 space shuttle change requests, 19 risk factors, and the associated failures and software metrics.

A Fuzzy Case-Based Reasoning Model for Software Requirements Specifications Quality Assessment

2019 ◽  
Vol 9 (6) ◽  
pp. 2134
Author(s):  
Salama A. Mostafa ◽  
Saraswathy Shamini Gunasekaran ◽  
Shihab Hamad Khaleefah ◽  
Aida Mustapha ◽  
Mohammed Ahmed Jubair ◽  
...  
Keyword(s):  
Quality Assessment ◽  
Software Requirements ◽  
Case Based Reasoning ◽  
Requirements Specifications ◽  
Case Based
Sign in / Sign up

Export Citation Format

Share Document