Search Results: 1 - 10 of 100 matches for " "
All listed articles are free for downloading (OA Articles)
Page 1 /100
Display every page Item
A Noble Methodology for Users Work Process Driven Software Requirements for Smart Handheld Devices  [PDF]
Tamjid Rahman,M. Rokonuzzaman
Computer Science , 2014, DOI: 10.5121/ijsea.2014.5402
Abstract: Requirement engineering is a key ingredient for software development to be effective. Apart from the traditional software requirement which is not much appropriate for new emerging software such as smart handheld device based software. In many perspectives of requirement engineering, traditional and new emerging software are not similar. Whereas requirement engineering of traditional software needs more research, it is obvious that new emerging software needs methodically and in-depth research for improved productivity, quality, risk management and validity. In particular, the result of this paper shows that how effective requirement engineering can improve in project negotiation, project planning, managing feature creep, testing, defect, rework and product quality. This paper also shows a new methodology which is focused on users work process applicable for eliciting the requirement of traditional software and any new type software of smart handheld device such as iPad. As an example, the paper shows how the methodology will be applied as a software requirement of iPad-based software for play-group students.
Qualitative Reasoning and Articulate Software  [PDF]
Y.C. Alicia Tang
Information Technology Journal , 2005,
Abstract: Qualitative Reasoning (QR) about physical system is one of the most active research areas in Artificial Intelligence (AI) in recent years. We believe that the part taking of qualitative reasoning will help to expand artificial intelligence application in new domains such as those that are highly qualitative in nature and the development of articulate software. Educational software using qualitative model can offer high interactivity rather than merely a static content-driven tool. With this, educational software can be made more engaging and interesting. As a result, the practical value of qualitative reasoning is significantly increased in the development of Intelligent Tutoring Systems. This study reviews three prominent ontologies for QR. The suitability of applying qualitative reasoning for building intelligent educational software was also discussed.
Reconciling software requirements and architectures within MDA
Uldis Donins , Janis Osis
Scientific Journal of Riga Technical University. Computer Sciences , 2009, DOI: 10.2478/v10143-009-0007-9
Abstract: In the software development world little guidance and few methods are available for reconciling software requirements and architecture which satisfies those requirements. In fact none of these methods use formal basis for the reconciling process. The main goal of this paper is to define an approach by which it is possible to reconcile software requirements and architectures within model driven architecture. Model driven architecture considers system from three viewpoints. Each viewpoint has its own model by which the viewpoint is modelled. It is possible to use topological functioning model of system to reconcile software requirements and architectures and to make formal transformation from computation independent model into platform independent model. The use of topological functioning model provides possibility for traceability between software artefacts, e.g. between requirements and architecture elements. By using case study we have proven that it is possible to reconcile requirements and architectures by using topological functioning model. The software architecture in this case is modelled by using topological class diagrams. At the end of the case study we have shown how we can introduce more formalism into UML diagrams by transforming topology from topological functioning model to class diagrams.
The Illusion of Requirements in Software Development  [PDF]
Paul Ralph
Computer Science , 2013, DOI: 10.1007/s00766-012-0161-4
Abstract: It is widely accepted that understanding system requirements is important for software development project success. However, this paper presents two novel challenges to the requirements concept. First, where many plausible approaches to achieving a goal are evident, there may be insufficient overlap between approaches to form requirements. Second, while all plausible approaches may have sufficient overlap to state requirements, we cannot know that unless all approaches are identified and we are sure that none have been missed. This suggest that many, if not most, software projects may have too few requirements drive the design process, and that analysts may misrepresent design decisions as requirements to compensate.
The NLC Software Requirements Methodology  [PDF]
G. R. White,H. Shoaee
Physics , 2001,
Abstract: We describe the software requirements and development methodology developed for the NLC control system. Given the longevity of that project, and the likely geographical distribution of the collaborating engineers, the planned requirements management process is somewhat more formal than the norm in high energy physics projects. The short term goals of the requirements process are to accurately estimate costs, to decompose the problem, and to determine likely technologies. The long term goal is to enable a smooth transition from high level functional requirements to specific subsystem and component requirements for individual programmers, and to support distributed development. The methodology covers both ends of that life cycle. It covers both the analytical and documentary tools for software engineering, and project management support.
On the Requirements of New Software Development  [PDF]
Vincenzo De Florio,Chris Blondia
Computer Science , 2015,
Abstract: Changes, they use to say, are the only constant in life. Everything changes rapidly around us, and more and more key to survival is the ability to rapidly adapt to changes. This consideration applies to many aspects of our lives. Strangely enough, this nearly self-evident truth is not always considered by software engineers with the seriousness that it calls for: The assumptions we draw for our systems often do not take into due account that e.g., the run-time environments, the operational conditions, or the available resources will vary. Software is especially vulnerable to this threat, and with today's software-dominated systems controlling crucial services in nuclear plants, airborne equipments, health care systems and so forth, it becomes clear how this situation may potentially lead to catastrophes. This paper discusses this problem and defines some of the requirements towards its effective solution, which we call "New Software Development" as a software equivalent of the well-known concept of New Product Development. The paper also introduces and discusses a practical example of a software tool designed taking those requirements into account --- an adaptive data integrity provision in which the degree of redundancy is not fixed once and for all at design time, but rather it changes dynamically with respect to the disturbances experienced during the run time.
Software Security Requirements Gathering Instrument  [PDF]
Smriti Jain,Maya Ingle
International Journal of Advanced Computer Sciences and Applications , 2011,
Abstract: Security breaches are largely caused by the vulnerable software. Since individuals and organizations mostly depend on softwares, it is important to produce in secured manner. The first step towards producing secured software is through gathering security requirements. This paper describes Software Security Requirements Gathering Instrument (SSRGI) that helps gather security requirements from the various stakeholders. This will guide the developers to gather security requirements along with the functional requirements and further incorporate security during other phases of software development. We subsequently present case studies that describe the integration of the SSRGI instrument with Software Requirements Specification (SRS) document as specified in standard IEEE 830-1998. Proposed SSRGI will support the software developers in gathering security requirements in detail during requirements gathering phase.
Software Security Requirements Checklist  [PDF]
Mahtab Alam
International Journal of Software Engineering , 2010,
Abstract: The increasing use of information systems led to dramatically improve the functionalitywith respect to safety, cost and reliability. However, with this growthof information systems the likelihood of vulnerabilities also increases. Securityproblems involving computers and software are frequent, widespread, and serious.The number and variety of attacks from outside organizations, particularlyvia the Internet, and the amount and consequences of insider attacks are increasingrapidly. We routinely hear customers claim that their system is insecure.However, without knowing what assumptions they make, it is hard to justifysuch a claim, and it is important to identify security requirements of the system.Enumerating the security to a system helps system architects develop realisticand meaningful secure software. In this paper, we propose a checklist for securityrequirements and assess the security with the help of a metrics based onchecklist threshold value.
Requirements Engineering in Agile Software Development  [cached]
Andrea De Lucia,Abdallah Qusef
Journal of Emerging Technologies in Web Intelligence , 2010, DOI: 10.4304/jetwi.2.3.212-220
Abstract: Finding out, analyzing, documenting, and checking requirements are important activities in all development approaches, including agile development. This paper discusses problems concerned with the conduction of requirements engineering activities in agile software development processes and suggests some improvements to solve some challenges caused by agile requirements engineering practices in large projects, like properly handling and identifying sensitive (including nonfunctional) requirements, documenting and managing requirements documentation, keeping agile teams in contact with outside customers. The paper also discusses the requirements traceability problem in agile software development and the relationships between the traceability and refactoring processes and their impact on each other.
Writing Software Requirements Specification Quality Requirements:An Approach to Manage Requirements Volatility  [PDF]
International Journal of Computer Technology and Applications , 2011,
Abstract: Quality requirements, that form a major sub-category of requirements, define a broad set system-wide attributes such as security, performance, usability and scalability. Unfortunately, many organizations pay less attention to quality requirements & assume that the necessary qualities are implicitly understood & will naturally emerge as the product is developed. In this paper, we would try to address important questions related to role of quality requirements in the software development lifecycle, and techniques for managing them effectively. Also, we would find out as to what happens when requirements are not managed? and suggest some practices to write quality requirements. The purpose is to make the community specifying the requirements understand requirements defects that have been made in the past. Hopefully, it also helps to avoid similar mistakes in the future.
Page 1 /100
Display every page Item

Copyright © 2008-2017 Open Access Library. All rights reserved.