Abstract
We are seeking to find measures of risk that can be used by management and the developers. We will show which characteristics and constraints could be assessed directly from the requirements specification document in the form of numeric values. These numeric must be normalised and used in a comparative manner with other events in the software development process. The required characteristics — the specific risks — will be expressed by the proposed metrics. The construction of a database with requirements analysis process data is emphasised as a testbed for metrics evaluation. In summary our approach is as follows: First decide what the important areas of risk are, then identify attributes available in a CASE (Computer Aided Software engineering) repository that may give an insight into these risks and then combine these attributes to provide risk measures.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
