Sign inSubmit
Tips: “quotes” for a phrase · author:Lee · a DOI goes straight to its article

33 results for “software requirements engineering”

Set a search alert
Research ArticleOpen accessIn the abstractStakeholders Selection Model for Software Requirements ElicitationFares Anwar, Rozilawati RazaliRequirements elicitation is the most critical phase in software requirements engineering. The process is resource intensive, as it concerns with a lot of dedicated stakeholders gathering purposefully to present and stipulate software requirements. The extent of effectiveness of the process is greatly influenced by the suitability of the stakeholders in the process of gathering the requirements. Previous studies indicate that … …American Journal of Applied Sciences, Vol. 13, Issue 6 · 7 Jun 2016 · 8,017 accessesView PDFCite
Research ArticleOpen accessIn the abstractA GQM Based Approach towards the Development of Metrics for Software SafetyKotti Jayasri, Panchumarthy SeetharamaiahSoftware sometimes safety-critical if it resides in a safety-critical computer systems and it causes or contributes to hazards. Therefore, Safety-critical software intensive systems require verification and validation to confirm that they function as per the safety requirements. Software Safety is a combination of many factors. Metrics are commonly used in engineering as measures for the performance of a system on … …Journal of Computer Science, Vol. 11, Issue 6 · 30 Sep 2015 · 6,411 accessesView PDFCite
Research ArticleOpen accessIn the abstractHOW PUBLIC ORGANISATIONAL STRUCTURES INFLUENCE SOFTWARE DEVELOPMENT PROCESSESMohammed A. Bindrees, Robert J. Pooley, Idris S. Ibrahim, Diana S. BentalSoftware applications are developed differently based on each organisation's needs and requirements. Software projects are fundamentally based on three considerations (time, cost and quality) each of which is affected by organisational factors. Both Project Management and Software Engineering have emphasised the role of organisation structure on the quality of the deliverable software applications, recognising that organisation structure influences flexibility, reporting … …Journal of Computer Science, Vol. 10, Issue 12 · 29 Dec 2014 · 7,985 accessesView PDFCite
Research ArticleOpen accessIn the abstractNon Functional Requirement Traceability Automation-an Mobile Multimedia ApproachM. Rajaram, J. SelvakumarRequirements Engineering (RE) is the area of software engineering that deals with the discovery and specification of the objectives for the system under development and the environment in which it is used including the human activities it supports. Requirement Elicitation is process of gathering requirements from stakeholders. Incorporating RE to identify non Functional Requirements (NFR) in early stages of design … …Journal of Computer Science, Vol. 8, Issue 11 · 7 Sep 2012 · 6,923 accessesView PDFCite
Research ArticleOpen accessIn the abstractApplying Software Engineering Methodology for Designing Biomedical Software Devoted To Electronic InstrumentationGilsa Aparecida de Lima Machado, Patricia Mara Danella Zacaro, Alderico Rodrigues de Paula Junior, Marcelo Lopes de Oliveira e SouzaProblem statement: Significant effort goes into the development of biomedical software, which is integrated with computers/processors, sensors and electronic instrumentation devoted to a specific application. However, the scientific work on electronic instrumentation controlled by biomedical software has not emphasized software development, instead focusing mainly on electronics engineering. The development team is rarely composed of Software Engineering (SE) experts. Usually, a … …Journal of Computer Science, Vol. 8, Issue 10 · 23 Aug 2012 · 6,971 accessesView PDFCite
Research ArticleOpen accessIn the abstractA Methodological Framework for Software Safety in Safety Critical Computer SystemsP. V. Srinivas Acharyulu, P. SeetharamaiahSoftware safety must deal with the principles of safety management, safety engineering and software engineering for developing safety-critical computer systems, with the target of making the system safe, risk-free and fail-safe in addition to provide a clarified differentaition for assessing and evaluating the risk, with the principles of software risk management. Problem statement: Prevailing software quality models, standards were not … …Journal of Computer Science, Vol. 8, Issue 9 · 16 Aug 2012 · 7,655 accessesView PDFCite
Research ArticleOpen accessIn the abstractSecured Requirement Specification Framework (SRSF)R.A. Khan, K. MustafaGenerally, software engineers are poorly trained to elicit, analyze and specify security requirements, often confusing them with the architectural security mechanisms that are traditionally used to fulfill them. One of the most ignored parts of a security-enhanced software development lifecycle is the security requirements engineering process. Security should begin at the requirements level and must cover both overt functional security … …American Journal of Applied Sciences, Vol. 5, Issue 12 · 31 Dec 2008 · 6,872 accessesView PDFCite
Research ArticleOpen accessIn the abstractSecurity Policy Development: Towards a Life-Cycle and Logic-Based Verification ModelLuay A. Wahsheh, Jim Alves-FossAlthough security plays a major role in the design of software systems, security requirements and policies are usually added to an already existing system, not created in conjunction with the product. As a result, there are often numerous problems with the overall design. In this paper, we discuss the relationship between software engineering, security engineering, and policy engineering and present … …American Journal of Applied Sciences, Vol. 5, Issue 9 · 30 Sep 2008 · 7,338 accessesView PDFCite
Research ArticleOpen accessIn the abstractSynthesizing Behavioral Model of Event-Based RequirementsSeyyed M. BabamirProblem Statement: in the software engineering field, satisfaction of user's requirements by software has been a matter of concern. Therefore, monitoring software behavior against user's high-level requirements has already received a considerable and significant attention. However, the gap between low-level software behavior and high-level requirements has put an obstacle in the way of monitoring. Approach: to overcome the obstacle, we … …Journal of Computer Science, Vol. 4, Issue 7 · 31 Jul 2008 · 6,667 accessesView PDFCite