Safe and secure: re-engineering a software process set for the challenges of the 21st century

Wallace, Ken

doi:10.1049/cp.2014.0987

Cited by 2 publications

(2 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…When we increase requirements integrity, it leaves effects on security. By software elicitation tried to overcome these risks of software integrity [12].…”

Section: Software Re-engineeringmentioning

confidence: 99%

See 1 more Smart Citation

An empirical approach for software reengineering process with relation to quality assurance mechanism

Muzammul

Awais²

2018

ADCAIJ

View full text Add to dashboard Cite

Muhammad Muzammul and Dr. M. AwaisAn empirical approach for software reengineering process with relation to quality assurance mechanism ADCAIJSoftware development advances focus on productivity of existing software systems and quality is basic demand of every engineering product. In this paper we will discuss complete reengineering process with aspects of forward, reverse and quality assurance mechanism. As we know the software development life cycle (SDLC) follows a complete mechanism of engineering process. In forward engineering we tried to follow selective main phases of software engineering (data,requirements,design,development,implementation). Inreverse engineering we move backward from the last phase of developing product as it gather requirements from implemented product (implementation, coding, design,requirements,data).During reengineering we add up more quality features on customer demands, but the actual demand is to fulfill quality needs that can be assured by external as well as internal quality attributes such as reliability, efficiency, flexibility, reusability and robustness in any software system. We discussed a methodological approach to move from reengineering to the journey of quality assurance. More than 50 studies come into discussion and throughput results proposed by graph and tabular form. We can say if the reengineering process produce quality attributes, then it can be said by old software system refactoring as code refactoring, data refactoring and architectural refactoring we obtained a quality products at lower cost instead of new software system development, which causes decrease in quality attributes as cost, time etc. In future work testing methodology can be proposed for quality assurance.Muhammad Muzammul and Dr. M. Awais An empirical approach for software reengineering process with relation to quality assurance mechanism ADCAIJAn empirical approach for software reengineering process with relation to quality assurance mechanism ADCAIJ

show abstract

“…When we increase requirements integrity, it leaves effects on security. By software elicitation tried to overcome these risks of software integrity [12].…”

Section: Software Re-engineeringmentioning

confidence: 99%

“…However, the main problem comes into existence when we try to understand current system. Usually, the documentation with architectural design and source code is not present or expired due to large time passage so we cannot get its view clearly [12]. What we have to do here?…”

Section: Introductionmentioning

confidence: 99%

An empirical approach for software reengineering process with relation to quality assurance mechanism

Muzammul

Awais²

2018

ADCAIJ

View full text Add to dashboard Cite

show abstract

Security Requirement Engineering Using Structured Object-Oriented Formal Language for M-Banking Applications

Emeka¹,

Liu²

2017

2017 IEEE International Conference on Software Quality, Reliability and Security (QRS)

View full text Add to dashboard Cite

Safe and secure: re-engineering a software process set for the challenges of the 21st century

Cited by 2 publications

References 0 publications

An empirical approach for software reengineering process with relation to quality assurance mechanism

An empirical approach for software reengineering process with relation to quality assurance mechanism

Security Requirement Engineering Using Structured Object-Oriented Formal Language for M-Banking Applications

Contact Info

Product

Resources

About