Optimization and practice of requirement analysis based on prototype portrait in software development process

2021 ◽  
pp. 1-9
Author(s):  
Mingyu Yue ◽  
Haiyan Feng
Keyword(s):  
Software Development ◽  
Requirements Analysis ◽  
Prototype System ◽  
Requirement Analysis ◽  
Software Development Process ◽  
Functional Requirements ◽  
Analysis Method ◽  
Development Cycle ◽  
Requirement Document ◽  
Software Requirement Specification

Aiming at the problems of incomplete description, ambiguity and inconsistency in the traditional requirements analysis method based on prototype system in software development, this paper proposes a requirement analysis method based on prototype portrait, introduces the process of obtaining the software requirement specification and designing the software by using the prototype portrait method according to the user’s requirements, and formalizes the process of the method, and develops the software with the prototype portrait requirement document approved by the customer, so as to ensure the correctness of the designed functional requirements. The practical results show that the requirement analysis method based on prototype portrait overcomes the problems of long development cycle and high failure rate existing in the traditional requirements analysis method of prototype system, and improves the quality and cycle of software development.

scholarly journals Tailoring effective requirement's specification for ingenuity in Software Development Life Cycle.

2021 ◽  
Vol 12 (3) ◽  
pp. 3338-3344
Author(s):  
Naveen N Kulkarni Et.al
Keyword(s):  
Best Practices ◽  
Software Development ◽  
Natural Language ◽  
Development Process ◽  
Object Oriented ◽  
Software Development Process ◽  
Software Documentation ◽  
Development Life Cycle ◽  
Software Development Life Cycle ◽  
Software Requirement Specification

Software Requirements Engineering (SRE) process define software manuscripts with sustaining Software Requirement Specification (SRS) and its activities. SRE comprises many tasks requirement analysis, elicitation, documentation, conciliation and validation. Natural language is most popular and commonly used to form the SRS document. However, natural language has its own limitations wrt quality approach for SRS. The constraints include  incomplete, incorrect, ambiguous, and inconsistency. In software engineering, most applications are object-oriented. So requirements are unlike problem domain need to be developed. So software  documentation is completed in such a way that, all authorized users like clients, analysts, managers, and developers can understand it. These are the basis for success of any planned project. Most of the work is still dependent on intensive human (domain expert) work. consequences of the project success still depend on timeliness with tending errors. The fundamental quality intended for each activity is specified during the software development process. This paper concludes critically with best practices in writing SRS. This approach helps to mitigate SRS limitation up to some extent. An initial review highlights capable results for the proposed practices

SyBeL: A SYSTEM MODELLING LANGUAGE ENHANCING AUTOMATIC SUPPORT IN THE SOFTWARE DEVELOPMENT PROCESS

2013 ◽  
Vol 23 (02) ◽  
pp. 223-257
Author(s):  
GIUSEPPE DELLA PENNA ◽  
SERGIO OREFICE ◽  
BENEDETTO INTRIGILA ◽  
DANIELE MAGAZZENI ◽  
ROBERTO DEL SORDO ◽  
...  
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Development Process ◽  
System Modelling ◽  
Test Cases ◽  
Practical Case ◽  
Software Development Process ◽  
Functional Requirements ◽  
Modelling Language ◽  
System Behaviour

In this paper we present SyBeL (System Behaviour modelling Language), an XML based formalism for software system modelling. In particular, SyBeL focuses on the description of the system behaviour in order to capture its functional requirements and has been designed to fulfill some of the most trendy software engineering issues. The use of the underlying XML language makes the artifacts generated by SyBeL immediately available to further automatic manipulation (e. g., to automatically generate test cases) without the need of intermediate models, as usually done in semi-formal approaches. Moreover, we are experimenting SyBeL on a variety of practical case studies.

scholarly journals Implementing Item-Based Collaborative Filtering System in Requirement Elicitation

2019 ◽  
Vol 8 (2S2) ◽  
pp. 230-233 ◽  
Keyword(s):  
Software Development ◽  
Collaborative Filtering ◽  
Development Process ◽  
Requirement Engineering ◽  
Vital Role ◽  
Software Development Process ◽  
Requirement Elicitation ◽  
Requirement Specification ◽  
Human Effort ◽  
Software Requirement Specification

In Requirement Engineering, Gathering Requirements plays a vital role in the Software Development Process. There are lot of processes available to gather requirements i.e. Brainstorming, Interview, Observation. This process takes lot of time and effort for the developer to gather and continue the development, and if the requirements which are analyzed are not up to the satisfaction of the user, it will cause issues in end product resulting in loss of human effort, time and cost. To overcome this issue faced by the developers we have developed a tool using item-based collaborative algorithm for users which will recommend users the required set of functional and nonfunctional requirements based upon the questionnaire given tothe user and produce a software requirement specification (SRS).

scholarly journals A Multi-Objective Dragongfly Optimization for Requirement Traceability Establishment

2021 ◽  
Vol 12 (2) ◽  
pp. 2523-2532
Author(s):  
Swathine.K , Et. al.
Keyword(s):  
Software Development ◽  
Development Process ◽  
Ad Hoc ◽  
Tool Support ◽  
Software Systems ◽  
Development Effort ◽  
Software Development Process ◽  
Functional Requirements ◽  
Faster Development ◽  
Requirement Traceability

Software traceability is a crucial component of various exact software development process and it is needed for various component certification and approval process in security system. With the tremendous growth of system, traceability is considered as a recent research topic. The traceability is a software development process that is indefinable. Various manufacturers struggle in predicting the appropriate traceability degree for their needs and produce the appropriate set of traceability links. The effort, cost, and discipline have to be maintained with tracking links with the faster development of software systems that are extremely higher. Also, it produces various advantages in practical realization; as it can be either ad-hoc or not properly defined traceability process, produces poor training or lack of effectual tool support. Moreover, the traceability process has to be determined as it can diminish the development effort and to enhance the development process. Generally, traceability research is based on empirical investigations for exploring newer investigational queries or to compute newer tracing methods. Here, this work concentrates on traceability, functional requirements, link establishment. It shows a better trade-off among the prevailing approaches.

scholarly journals Safety Requirements Analysis using Misuse Cases Method

2021 ◽  
Vol 7 (1) ◽  
pp. 1-9
Author(s):  
Ryo Alif Ramadhan ◽  
Dana Sulistyo Kusumo ◽  
Jati Hiliamsyah Husen
Keyword(s):  
Software Development ◽  
Requirements Engineering ◽  
Security Analysis ◽  
Safety Analysis ◽  
Requirements Analysis ◽  
Software Requirements ◽  
Analysis Approach ◽  
Analysis Method ◽  
Safety Requirements ◽  
Software Product

Safety requirements analysis is an activity inside software requirements engineering that focuses on finding and solving safety gaps inside a software product. One method to do safety requirements analysis is misuse cases, a technique adopted from the security analysis method. Misuse cases provide a safety analysis approach which allows detailed steps from different stakeholders' perspective. In this research, we evaluate the misuse cases method's understandability by implementing it to analyze safety requirements for an electric car's autopilot system. We assessed the developed models using the walkthrough method. We found differences between how the model understood from someone with experience in software development and those who don't.

scholarly journals The MINERVA Software Development Process

10.29007/5jlw ◽  
2018 ◽  
Author(s):  
Anthony Narkawicz ◽  
Cesar Munoz ◽  
Aaron Dutle
Keyword(s):  
Software Development ◽  
Development Process ◽  
Unmanned Aircraft ◽  
Unmanned Aircraft Systems ◽  
Theorem Prover ◽  
Test Cases ◽  
Software Development Process ◽  
Functional Requirements ◽  
Physical Systems ◽  
Formal Specification Language

This paper presents a software development process for safety-critical software components of cyber-physical systems. The process is called MINERVA, which stands for Mirrored Implementation Numerically Evaluated against Rigorously Verified Algorithms. The process relies on formal methods for rigorously validating code against its requirements. The software development process uses: (1) a formal specification language for describing the algorithms and their functional requirements, (2) an interactive theorem prover for formally verifying the correctness of the algorithms, (3) test cases that stress the code, and (4) numerical evaluation on these test cases of both the algorithm specifications and their implementations in code. The MINERVA process is illustrated in this paper with an application to geo-containment algorithms for unmanned aircraft systems. These algorithms ensure that the position of an aircraft never leaves a predetermined polygon region and provide recovery maneuvers when the region is inadvertently exited.

scholarly journals Automating Software Develpoment using Artificial Intelligence.doc

2020 ◽  
Author(s):  
Sai Lohith Vasireddi ◽  
Mahesh Dhaka ◽  
Jinan Fiaidhi
Keyword(s):  
Software Development ◽  
Development Process ◽  
Research Paper ◽  
Team Formation ◽  
Software Development Process ◽  
Requirement Specification ◽  
Software Requirement ◽  
Software Requirement Specification

The research paper focuses on automating software development process by automating the team formation by extracting information from the software requirement specification (SRS) document of the project.

scholarly journals Automating Software Develpoment using Artificial Intelligence.doc

2020 ◽  
Author(s):  
Sai Lohith Vasireddi ◽  
Mahesh Dhaka ◽  
Jinan Fiaidhi
Keyword(s):  
Software Development ◽  
Development Process ◽  
Research Paper ◽  
Team Formation ◽  
Software Development Process ◽  
Requirement Specification ◽  
Software Requirement ◽  
Software Requirement Specification

The research paper focuses on automating software development process by automating the team formation by extracting information from the software requirement specification (SRS) document of the project.

scholarly journals ELICITATION, REPRESENTATION AND MANAGEMENT OF SOFTWARE DESIGN KNOWLEDGE

2011 ◽  
Author(s):  
Behrouz H. Far ◽  
Mohsen Afsharchi
Keyword(s):  
Software Development ◽  
Project Manager ◽  
Prototype System ◽  
Software Development Process ◽  
Multiple Stakeholders ◽  
Types Of Knowledge ◽  
Decision Making Processes ◽  
Context Specific ◽  
Descriptive Knowledge ◽  
Coding Rules

In this research we focus on understanding the nature of the knowledge used during the various phases of the software development process. We have found that there are two types of knowledge involved in software development: (1) descriptive knowledge represented by conversion and coding rules, e.g., a rule for splitting a class into two; and (2) prescriptive knowledge required for deployment of global or local strategies at a micro design level; e.g., knowledge required to answer the question “why should a class should be split into two?” Most of the already existing knowledge management solutions address descriptive knowledge. Elicitation and management of the prescriptive knowledge is difficult in the sense that it is probabilistic, personalized, distributed and context specific. Also we have found that prescriptive knowledge tends to be used in decision making processes involving multiple stakeholders with different perspectives (e.g., designer, tester, software architect and project manager). We also report on a prototype system called ISS-OKM to extract and reuse both the descriptive and prescriptive knowledge.

Sign in / Sign up

Export Citation Format

Share Document