scholarly journals Specification of Non-Functional Requirements (NFRs) in Request for Proposal (RFP)

2016 ◽  
Vol 1 (3) ◽  
pp. 197
Author(s):  
Harsimran Kaur ◽  
Ashish Sharma
Keyword(s):  
Development Process ◽  
Reference Model ◽  
Planning System ◽  
Requirement Analysis ◽  
Use Case ◽  
Functional Requirements ◽  
Development Cost ◽  
Request For Proposal ◽  
Complete Procedure ◽  
Critical Activity

Software Requirement Analysis is one of the most important and critical activity of software development, that affects the development cost and success of end product. This paper proposes to add both formal and informal specifications of NFR to Request for Proposal document. It ought the developers to focus on each NFR right from the beginning of development process. In this paper NFRs are specified informally by extended use case and formally by proposed extension to Formal Reference Model. The paper claims that the proposed add-ons related to NFRs are qualitative one and can be considered as standard add-ons in RFP documents to deal with NFRs. It shall act as important step during early planning system for designing and implementing proposed software. The complete procedure is illustrated using a general case of cafeteria ordering framework.

Modeling of Automobile Stamping Parts Management System Driven by Use Case

2013 ◽  
Vol 756-759 ◽  
pp. 1517-1521
Author(s):  
Cheng Shuang Han ◽  
Zai Ling Cheng
Keyword(s):  
Information System ◽  
Management Information System ◽  
Flow Diagram ◽  
Requirement Analysis ◽  
Use Case ◽  
Functional Requirements ◽  
Management Information ◽  
System Activity ◽  
Requirement Model ◽  
Business Flow

Requirement analyses based on use case apply to the requirement description of information system. This paper discusses the requirement analysis and modeling of automobile stamping parts management information system based on use case. Starting from analyzing its business flow diagram, the system activity (actor) and its candidate requirements reflecting from its feature checklist are recognized. The system functional requirements and non functional requirements are captured in the form of the use case, then the requirement model of automobile stamping parts management information system is established..

scholarly journals Requirement analysis for autograder system using use case model

2021 ◽  
Vol 1098 (3) ◽  
pp. 032084
Author(s):  
R Elsen ◽  
D Kurniadi ◽  
S Rahayu ◽  
M R Nashrulloh
Keyword(s):  
Requirement Analysis ◽  
Use Case ◽  
Use Case Model

scholarly journals Designing and manufacturing of a soybean harvest residue picker

2015 ◽  
Vol 35 (6) ◽  
pp. 1053-1064 ◽  
Author(s):  
Rubem Schöffel ◽  
Walter Boller ◽  
Márcio Walber
Keyword(s):  
Architectural Design ◽  
Development Process ◽  
Crop Residues ◽  
Reference Model ◽  
Screw Conveyor ◽  
Centrifugal Fan ◽  
Agricultural Machinery ◽  
Plant Parts ◽  
Design Build ◽  
Market Perception

ABSTRACT Soy harvest matches seasons with shortage of dry matter supply for ruminant feeding in most Brazilian soy-growing areas. Agricultural machinery-producing companies must have market perception, observing new opportunities and developing equipment to meet costumers’ needs. This paper aims to design, build, and test a device to collect soybean crop residues from the combine cleaning mechanism, consisting mainly of vegetable straw (chaff), and the other plant parts (stems) remain being deposited onto the ground. For equipment designing, we made use of the architectural design methodology proposed in the reference model for the agricultural machinery development process. The equipment was designed and built following the proposed methodology, then installed and put into operation in a John Deere 1165 combine. After initial testing and few adjustments, the device showed satisfactory chaff-collecting performance. The equipment consists of a screw conveyor assembled transversely to the combine and a centrifugal fan assembled on the side. The collected chaff is dumped into a trailer towed by tractor.

scholarly journals Supporting Non-functional Requirements in Services Software Development Process: An MDD Approach

2014 ◽  
pp. 199-210
Author(s):  
Valeria de Castro ◽  
Martin A. Musicante ◽  
Umberto Souza da Costa ◽  
Plácido A. de Souza Neto ◽  
Genoveva Vargas-Solar
Keyword(s):  
Software Development ◽  
Development Process ◽  
Software Development Process ◽  
Functional Requirements

Augmented Reality im Bauwesen: Teil 1 – Anwendungs- und Anforderungsanalyse/Augmented Reality in civil engineering: Part 1 – Use-case and requirement analysis

Bauingenieur ◽  
2020 ◽  
Vol 95 (10) ◽  
pp. 379-388
Author(s):  
Christian Schranz ◽  
Alexander Gerger ◽  
Harald Urban
Keyword(s):  
Expert System ◽  
Augmented Reality ◽  
Building Information Modeling ◽  
Civil Engineering ◽  
Information Modeling ◽  
Requirement Analysis ◽  
Use Case ◽  
Building Information

Zusammenfassung Die Bauwirtschaft gehört bis dato zu den am wenigsten von der Digitalisierung erfassten Wirtschaftszweigen. Der vermehrte Einsatz von Building Information Modeling (BIM) in Planungsbüros beschleunigt nun die Digitalisierung des Bauwesens. Dies ermöglicht den vermehrten Einsatz weiterer digitaler Tools im Bauprozess, zum Beispiel Augmented Reality (AR). Neue Tools bieten die Chance, die vorhandenen Prozesse neu zu überdenken und auf Innovations- und Effizienzpotenzial zu untersuchen. Die Autoren sehen für die Technologie AR großes Potenzial im Bauprozess. Im Forschungsprojekt AR-AQ-Bau führten sie daher eine Anwendungs- und Anforderungsanalyse für AR durch. In diesem Artikel werden einige derzeitige und mögliche Anwendungen von AR im Bauwesen sowie deren Anforderungen an AR-Hard- und Software (z. B. durch die Besonderheiten der Baustelle) dargestellt und ein Ausblick in die Zukunft gegeben. Der Anwendungsbereich von AR ist äußerst vielfältig. Einerseits kann BIM dadurch leichter auf die Baustelle übertragen und können Abnahmen und Qualitätskontrollen durchgeführt werden. Andererseits stellen ein Remote-Expert-System, Schulungen und die Unterstützung im Behördenverfahren weitere Einsatzmöglichkeiten dar.

Skyline

2017 ◽  
Vol 9 (3) ◽  
pp. 34-53 ◽  
Author(s):  
Ignacio Alvarez ◽  
Laura Rumbel
Keyword(s):  
Research And Development ◽  
Rapid Prototyping ◽  
User Experience ◽  
Development Process ◽  
User Feedback ◽  
High Fidelity ◽  
Use Case ◽  
Software Components ◽  
User Assessment

This paper describes the research and development process of an in-vehicle user experience using Skyline, an automotive prototyping platform created in Intel Labs to empower interaction designers and user experience researches to rapidly and iteratively develop and test in-vehicle user experience concepts. The paper describes the hardware and software components of Skyline in depth and how to configure them to suit individual researcher needs. The paper also presents a case study to exemplify the design making process that Skyline enables. From ideation to use-case creation, prototyping and validation through user assessment, the paper showcases the benefits of capturing early qualitative user feedback as support for rapid prototyping walking through a study titled Agency vs. Control and the associated interactions inside the cockpit. Ten defined use-cases are developed and integrated into a hero scenario in Skyline. High fidelity HMI concepts are tested and validated over the course of six months with feedback from a total of fifty users.

Making Real Progress with the Requirements Defects Problem

2011 ◽  
pp. 90-111
Author(s):  
R. Geoff Dromey
Keyword(s):  
Information Systems ◽  
Model Checking ◽  
Development Process ◽  
Fundamental Problem ◽  
Integrated Design ◽  
Significant Problem ◽  
Functional Requirements ◽  
Formal Representation ◽  
Behavior Tree ◽  
Behavior Trees

Requirements defects remain a significant problem in the development of all software intensive systems including information systems. Progress with this fundamental problem is possible once we recognize that individual functional requirements represent fragments of behavior, while a design that satisfies a set of functional requirements represents integrated behavior. This perspective admits the prospect of constructing a design out of its requirements. A formal representation for individual functional requirements, called behavior trees makes this possible. Behavior trees of individual functional requirements may be composed, one at a time, to create an integrated design behavior tree (DBT). Different classes of defects are detected at each stage of the development process. Defects may be found at the translation to behavior trees, and then at the integration of behavior trees and when individual component behavior trees are projected from the DBT. Other defects may be found by inspection and model-checking of the DBT.

Sign in / Sign up

Export Citation Format

Share Document