1 |
Nonlinear design, modeling and simulation of magneto rheological suspension: a control system and systems engineering approachZambare, Hrishikesh B. 12 1900 (has links)
Indiana University-Purdue University Indianapolis (IUPUI) / Suspension has been the most important subsystem of the vehicle viewed as a system. The ride comfort and vehicle handling performance are affected by the suspension design. Automotive technology has been continuously incorporating developments over the past few decades to provide the end users with a better comfort of driving. Multi-objective optimization of MR damper with objective function of maximizing damping force generated by MR damper with the geometrical parametric constraint function is achieved in this research using pattern search optimization technique.
Research focuses on design, modeling, and simulation of active suspension using non-linear theory of the Magneto-Rheological (MR) damper with consideration of the hysteresis behavior for a quarter car model. The research is based on the assumption that each wheel experiences same disturbance excitation. Hysteresis is analyzed using Bingham, Dahl’s, and Bouc-Wen models. Research includes simulation of passive, Bingham, Dahl, and Bouc-wen models. Modeled systems are analyzed for the six road profiles, including road type C according to international standards ISO/TC108/SC2N67. Furthermore, the comparative study of the models for the highest comfort with less overshoot and settling time of vehicle sprung mass are executed. The Bouc-Wen model is 36.91 percent more comfortable than passive suspension in terms of damping force requirements and has a 26.16 percent less overshoot, and 88.31 percent less settling time. The simulation of the Bouc-Wen model yields a damping force requirement of 2003 N which is 97.63 percent in agreement with analytically calculated damping force generated by MR damper. PID controller implementation has improved the overshoot response of Bouc-Wen model in the range of 17.89 percent-81.96 percent for the different road profiles considered in this research without compromising on the settling time of system. PID controller implementation further improves the passenger comfort and vehicle ride handling capabilities.
The interdisciplinary approach of systems engineering principles for the suspension design provides unique edge to this research. Classical systems engineering tools and MBSE approach are applied in the design of the MR damper. Requirement traceability successfully validates the optimized MR damper.
|
2 |
Effective Requirements ManagementWanganga, George January 2004 (has links)
In many smaller companies, requirements management is a daunting challenge. Smaller groups mean fewer resources, and many organizations focus their efforts on design, development and testing not on managing requirements. Some small organizations may perceive requirements management as an activity only for large organizations that have complex products and large staffs to support the effort. Poor and uncontrolled requirement engineering processes yield low quality, highly expensive software products. Obviously, customers are highly dissatisfied with such systems. One of the most critical requirement engineering processes that grossly contribute to this misnomer is lack of “effective requirements management” Information Technology Associates (ITA) has had many challenges resulting from some poor and uncontrolled requirements engineering processes. Lack of effective requirements traceability has also had its share in plaguing ITA in software development activities. ITA started small and so it handled its requirements documentation manually as it only dealt with few customer requirements. Time has seen the company expand, and manual handling of customer requirement became difficult. This master thesis therefore aims to investigate: ♦ The state-of-practice, regarding requirements engineering and requirements management within a medium-sized software development company. ♦ How to successfully implement effective requirement management process within the ITA Company. ♦ How to successfully migrate ITA Company into this RE process while ensuring minimum hassles.
|
3 |
Predicting vulnerability for requirements: A data-driven approachImtiaz, Sayem Mohammad 09 August 2019 (has links)
Being software security one of the primary concerns in the software engineering community, researchers are coming up with many preemptive approaches which are primarily designed to detect vulnerabilities in the post-implementation stage of the software development life-cycle (SDLC). While they have been shown to be effective in detecting vulnerabilities, the consequences are often expensive. Accommodating changes after detecting a bug or vulnerability in late stages of the SDLC is costly. On that account, in this thesis, we propose a novel framework to provide an additional measure of predicting vulnerabilities at earlier stages of the SDLC. To that end, we leverage state-of-the-art machine learning classification algorithms to predict vulnerabilities for new requirements. We also present a case study on a large open-source-software (OSS) system, Firefox, evaluating the effectiveness of the extended prediction module. The results demonstrate that the framework could be a viable augmentation to the traditional vulnerabilityighting tools.
|
4 |
InnoTrace : rastreamento de requisitos de inovação na concepção de produtos de softwareARAÚJO, Breno Leonardo Gomes de Menezes 08 July 2015 (has links)
Submitted by Mario BC (mario@bc.ufrpe.br) on 2017-02-08T14:12:20Z
No. of bitstreams: 1
Breno Leonardo Gomes de Menezes Araujo.pdf: 3596044 bytes, checksum: ba04fae7f1924573f14255f9d5e2c44a (MD5) / Made available in DSpace on 2017-02-08T14:12:20Z (GMT). No. of bitstreams: 1
Breno Leonardo Gomes de Menezes Araujo.pdf: 3596044 bytes, checksum: ba04fae7f1924573f14255f9d5e2c44a (MD5)
Previous issue date: 2015-07-08 / Innovation driven approaches prescribe principles, practices and tools that are used to develop innovative products or services. Introducing elements of these innovation-driven approaches in the context of software processes allow that aspects related to the business, market and creativity being considered in design an innovative software product. However, there are gaps between innovation processes and software processes. This work seeks to address the relationship between elements of innovation processes and elements of software processes through traceability. Therefore, this work proposed an approach called InnoTrace that aims to enable tracking of innovation requirements toward system requirements and tracking of system requirements backward innovation requirements. The InnoTrace approach consists of: specifying signs to represent innovation requirements and system requirements; specifying a track to represent the relationship between signs through the notation provided by the SysML language; and traces that consist of following the track in the context of cases that demonstrate the application of software processes that incorporate innovation practices and techniques. The main contribution of this work is to provide a method appropriate for documenting traceability relations (cause and effect) between innovation and system requirements and thus mitigate the gaps commonly observed between innovation and software processes. / As abordagens dirigidas à inovação prescrevem princípios, práticas e ferramentas que são utilizados no desenvolvimento de produtos ou serviços inovadores. A introdução de elementos dessas abordagens dirigidas à inovação no contexto de processos de software permite que sejam tratados aspectos relacionados ao negócio, ao mercado, e à criatividade na concepção de um produto de software inovador. Porém, é comum existir lacunas entre os processos de inovação e os processos de software. Este trabalho procura tratar as relações entre elementos dos processos de inovação e de software, através de rastreabilidade. Para tanto, é proposta uma abordagem denominada InnoTrace que visa possibilitar o rastreamento de requisitos de inovação em direção a requisitos de sistema e vice-versa. A abordagem InnoTrace consiste: na especificação de sinais que representam os requisitos de inovação e de sistemas; na especificação de trilha que representa os relacionamentos entre sinais, através de notação fornecida pela linguagem SysML; e em rastros que consistem em seguir a trilha no contexto de casos que demonstram a aplicação de processos de software que incorporam práticas e técnicas de inovação. A principal contribuição deste trabalho é prover um método que permita documentar as relações de rastreabilidade (causa e efeito) entre requisitos de inovação e de sistema e assim mitigar as lacunas comumente observadas entre processos de inovação e de software.
|
5 |
Software Testing : A Comparative Study Model Based Testing VS Test Case Based Testing / Software Testing : A Comparative Study Model Based Testing VS Test Case Based TestingPolamreddy, Rakesh Reddy, Irtaza, Syed Ail January 2012 (has links)
Software testing is considered as one of the key phases in the software-development life cycle (SDLC). The main objective of software testing is to detect the faults either through manual testing or with automated testing approach. The most commonly adopted software testing approach in industries is test case based testing (TCBT) which is usually done manually. TCBT is mainly used by the software testers to formalize and guide their testing activities and set theoretical principals for testing. On the other hand, model based testing (MBT) is widely used automation software testing technique to generate and execute the tests. Both techniques are showing their prominence in real time with some pros and cons. However, there is no formal comparison available between these two techniques. The main objective of this thesis work is to find out the difference in test cases in TCBT and MBT in terms of providing better test coverage ( Statement, Branch and Path), requirement traceability, cost and time. To fulfill the aims of the research we have conducted interviews for static validation, and later we did an experiment for validating those results dynamically. The analysis of experiment results showed that the requirement traceability in MBT generated test cases are very hard to make the test cases traceable to the requirements, particularly with the open-source tool Model J-Unit. However, this can be done by using other commercial tools like Microsoft Spec Explorer or Conformiq Qtronic. Furthermore, we found by conducting experiment, that MBT consumes less time thus it is cost-effective as compared to TCBT and also MBT show better test coverage than TCBT. Moreover, we found that, in our case, requirement traceability is better in traditional TCBT approach as compared to MBT. / +4746851975
|
Page generated in 0.0976 seconds