Search results for "requirements analysis"

showing 10 items of 20 documents

Method to Define User Interfaces in the Requirements Analysis Phase

2018

Many requirements for quality in use are elicited in the late development phase. However, if requirements are elicited in the late development phase, the development may return to the previous phase or some requirements cannot be realized due to costs and schedules. To reduce these cases, we propose a method to elicit the requirements in the requirements analysis phase. First, software developers analyze the user characteristics (UCs) of the target users and specify important quality characteristics (QCs) for quality in use and UI design items based on the relationships among UC, QC, and UI design items. Because UI design items are considerations to develop UIs, the specified UI design item…

Late developmentInformationSystems_INFORMATIONINTERFACESANDPRESENTATION(e.g.HCI)Computer sciencebusiness.industrymedia_common.quotation_subjectComputerApplications_COMPUTERSINOTHERSYSTEMS020207 software engineering02 engineering and technologyTracingPhase (combat)InformationSystems_MODELSANDPRINCIPLESSoftware020204 information systems0202 electrical engineering electronic engineering information engineeringQuality (business)User interfaceSoftware engineeringbusinessQuality characteristicsRequirements analysismedia_commonProceedings of the ACM SIGCHI Symposium on Engineering Interactive Computing Systems
researchProduct

Analysing Requirements for Content Mangement

2006

The content to be managed in organisations is in textual or multimedia formats. Major part of the content is, however, stored in documents. In order to find out the needs of the people and organisations producing and using the content a profound requirements analysis is needed. In the paper, a novel method for the requirements analysis for content management purposes is introduced. The method combines different techniques from two existing methods, which were used in various content management development projects. The paper also describes a case study where the new method is exploited.

MetadataWorld Wide WebProcess managementbusiness.industryComputer scienceOrder (business)Document management systemcomputer.software_genrebusinessContent (Freudian dream analysis)computerRequirements analysisContent management
researchProduct

A framework for intention-driven requirements engineering of innovative software products

2011

Requirements engineering is highly challenging particularly when designing innovative software products. This is so because there are no corresponding products, ultimate needs of actors are difficult to capture, the products may have unforeseeable impacts on the actors’ behavior, and it is hard to find out how value-added and competitive the product actually is. In this paper, we propose a novel framework for intention-driven requirements engineering of innovative software products, which combines technological, social and business viewpoints. We illustrate its use with a short example related to the domain of web mapping services and augmented reality. peerReviewed

RequirementBusiness requirementsSocial software engineeringProcess managementRequirements engineeringComputer sciencebusiness.industrySoftware developmentSoftware requirements specificationinnovatiivinen sovelluskehitysvaatimusmäärittelySoftware requirementsSoftware engineeringbusinessRequirements analysis
researchProduct

Composition of a New Process to Meet Agile Needs Using Method Engineering

2005

The need of developing a new software engineering process to allow the quick prototyping of some robotic applications and meet the requests by some companies for a development process that was shorter than PASSI, gave us the opportunity of applying our studies on the assembling of a new SEP by reusing parts (called method fragments) from other processes. In this paper we discuss our approach that, starting from the method engineering paradigm, adapts and extends it considering specific agent-oriented issues like the multi-agent system meta-model. The final result of our experiment (Agile PASSI) is presented together with the requirements that motivated its structure. © Springer-Verlag Berli…

RequirementRequirements engineeringUse Case Diagrambusiness.industryComputer scienceProcess (engineering)Method engineeringComputer Science (all)Theoretical Computer ScienceSoftware development processbusinessSoftware engineeringRequirements analysisAgile software development
researchProduct

Allowing End-Users to Actively Participate within the Elicitation of Pervasive System Requirements through Immediate Visualization

2009

Efficient requirements engineering activities are essential in order to develop software systems that properly satisfy end-user needs. End-users lack knowledge about requirements engineering techniques or computation in general, and it is very important that they actively participate in the requirements elicitation process because they are the "owners" of the problem. In this paper, we present a tool-supported requirements elicitation technique that is centered on end-users and that allows them to describe the main characteristics of pervasive systems. In addition, we provide end-users with an immediate natural visualization of the described requirements. Furthermore, we present a requireme…

Requirements managementRequirementNon-functional requirementRequirements traceabilityRequirements engineeringComputer sciencebusiness.industrySoftware requirements specificationRequirements elicitationSoftware engineeringbusinessRequirements analysis2009 Fourth International Workshop on Requirements Engineering Visualization
researchProduct

Requirement analysis abstractions for AmI system design

2015

Current trends in the AI’s evolution are going towards enriching environments with intelligence in order to support humans in their everyday life. AmI systems are plunged in the real world and humans expect to interact with them in a way that is similar to the one they have with other humans. In this kind of systems, where eliciting requirements involves several documents and stakeholders (mainly users that will be the first consumers of the system), the requirement analysis phase can be affected by incomplete, ambiguous and imprecise information. Hence, the need to find a fruitful way for knowledge management and its representation at design time. In this paper we propose a set of abstract…

Statistics and ProbabilityAmbient intelligenceKnowledge representation and reasoningRequirement analysisComputer scienceMulti-agent systemsmart environmentGeneral EngineeringOntology (information science)software designData scienceWorld Wide WebAmI modelArtificial Intelligencemulti-agent systemAmbient intelligenceSystems designSoftware designSmart environmentontologyRequirement analysiRequirements analysisontology AmI modelJournal of Intelligent & Fuzzy Systems
researchProduct

An Information Systems Design Theory for Integrated Requirements and Release Management Systems

2009

High-tech companies need to collect and analy- ze requirements and allocate them to appropriate product releases in market-driven product development. Develop- ment activities are typically scattered across multiple sites and involve multiple partners in different countries, complicating requirements and release management. Fle- xible, scalable, and secure groupware-based support for the activities provides substantial payoffs. Yet, the extant literature provides little theoretical guidance for designing and using requirements and release management systems in multi-site, multi-partner environments. This article de- velops the meta-requirements and a meta-design of an Information Systems De…

Structure of Management InformationInformation managementCollaborative softwareRequirementProcess managementbusiness.industryComputer scienceData managementSoftware developmentcomputer.software_genreApplication lifecycle managementMarket requirements documentRelease managementRequirement prioritizationSystems development life cycleSystems managementNew product developmentInformation systemSystems designSoftware engineeringbusinessRequirements analysiscomputer2009 42nd Hawaii International Conference on System Sciences
researchProduct

Team Client Relationships and Extreme Programming

2008

This paper describes a study that examined the relationship between software engineering teams who adhered to the extreme programming (XP) methodology and their project clients. The study involved observing teams working on projects for clients who had commissioned a piece of software to be used in the real world. Interviews were conducted during and at the end of the project to get client opinion on how the project had progressed. Of interest to the researchers were opinions on frequency of feedback, how the team captured requirements, whether or not the iterative approach of XP proved to be helpful, and the level of contextual and software engineering knowledge the client had at the start…

requirements analysisXPcommunicationsoftware clientssatisfaction
researchProduct

ITKA111 Oliosuuntautunut analyysi ja suunnittelu

2009

requirements analysisinformation systems designuse casesohjelmistovaatimuksetohjelmistoarkkitehtuurioliokeskeisyyskäyttötapauksetsoftware requirementsobject orientationvaatimusanalyysitietojärjestelmien suunnittelusuunnittelumallitdesign patterns
researchProduct

Utilizing online serious games to facilitate distributed requirements elicitation

2015

Online serious games are used to facilitate distributed requirements elicitation.Interactive games enhance collaboration and communication between project members.Serious games raise individuals' confidence to engage in requirements elicitation.Using serious games can improve both quality and quantity of software requirements.Serious games specially enhance the performance of less-experienced stakeholders. Requirements elicitation is one of the most important and challenging activities in software development projects. A variety of challenges related to requirements elicitation are reported in the literature, of which the lack of proper communication and knowledge transfer between software …

ta113Requirements managementBusiness requirementsRequirementEngineeringserious gamesKnowledge managementbusiness.industryrequirements elicitationSoftware developmentRequirements elicitationpelitEmpirical researchhyötypelitHardware and Architecturesoftware developmentohjelmistokehitysbusinessRequirements analysisKnowledge transferSoftwaregamesInformation SystemsJournal of Systems and Software
researchProduct