| Collection Title: | SIU RS | | Title : | Development high integrity software the agile way : (With particular reference to incorporating traceability into scrum) | | Material Type: | printed text | | Publisher: | Bangkok : Shinawatra University | | Publication Date: | 2014 | | Pagination: | ix, 106 p. | | Size: | 30 cm. | | Price: | Gift. | | General note: | Thesis. [M.S.[Information Technology]]. - Shinawatra University. | | Languages : | English (eng) | | Descriptors: | [LCSH]AGILE Software -- Development
[LCSH]Computer software -- Development
[LCSH]Software engineering
[LCSH]Software engineering -- Management
| | Keywords: | Software engineering.
Computer software. | | Class number: | SIU RS: SOIT-MSIT-2014-01 | | Abstract: | Much previous software engineering research is characterized by overly complex, heavyweight, solutions that are off little practical use. However researchers are increasingly focusing on solutions that are lightweight, and simple enough to be adopted in practice. Agile Methods (AM) such as Feature Driven Development, eXtreme Programming and Scrum are notable examples. Their benefits are attractive to software engineers increasingly challenged to deliver software that is both dependable (reliable, secure, available, etc.) and capable of rapid change or reconfiguration in an increasingly volatile business environment.
Until recently, the thought of applying Agile Methods to High Integrity Software Systems was unthinkable. We cannot expect industry to make large big-bang changes to processes, methods and tools, without tangible evidence of their value; and among the HIS engineering community there is little conclusive evidence of successful application of AM in this domain, while research into the possibilities is still in its infancy. One major challenge is that the AM “manifesto” emphasizes among its core values, “working software over comprehensive documentation”. Similarly another value Agile proponents hold dear is “trustworthy transparency over tiresome traceability”. Yet HISE must often be certified by the appropriate regulatory body before entering service. This normally involves submission to the appropriate regulatory authority of a dependability case (a reasoned argument that the system is acceptably secure/reliable/safe to operate), typically including claims and supporting evidence of adherence to appropriate standards. Such standards like DO178b, EN-50128 and IEC 61508 mandate production of certain documentation, and, traceability between these artifacts; all incidentally also recommend use of Formal (mathematical development) Methods, including CSP, LOTOS, Temporal Logic, VDM, Z and B, methods at best seen as orthogonal and at worst opposing to an Agile approach.
This research aims to modify Scrum to incorporate the fundamental (heavyweight) needs of engineering high integrity systems, while retaining the lightweight ‘touch’ of Agile Methods. In particular we devise a method for integrating tools supporting the varied range of development and assessment notations and techniques (including Formal Methods) used by HIS engineers, while enabling generation of cross tool traceability links between artifacts.
| | Curricular : | MSIT | | Record link: | http://libsearch.siu.ac.th/siu/opac_css/index.php?lvl=notice_display&id=24138 |
SIU RS. Development high integrity software the agile way : (With particular reference to incorporating traceability into scrum) [printed text] . - Bangkok : Shinawatra University, 2014 . - ix, 106 p. ; 30 cm. Gift. Thesis. [M.S.[Information Technology]]. - Shinawatra University. Languages : English ( eng) | Descriptors: | [LCSH]AGILE Software -- Development
[LCSH]Computer software -- Development
[LCSH]Software engineering
[LCSH]Software engineering -- Management
| | Keywords: | Software engineering.
Computer software. | | Class number: | SIU RS: SOIT-MSIT-2014-01 | | Abstract: | Much previous software engineering research is characterized by overly complex, heavyweight, solutions that are off little practical use. However researchers are increasingly focusing on solutions that are lightweight, and simple enough to be adopted in practice. Agile Methods (AM) such as Feature Driven Development, eXtreme Programming and Scrum are notable examples. Their benefits are attractive to software engineers increasingly challenged to deliver software that is both dependable (reliable, secure, available, etc.) and capable of rapid change or reconfiguration in an increasingly volatile business environment.
Until recently, the thought of applying Agile Methods to High Integrity Software Systems was unthinkable. We cannot expect industry to make large big-bang changes to processes, methods and tools, without tangible evidence of their value; and among the HIS engineering community there is little conclusive evidence of successful application of AM in this domain, while research into the possibilities is still in its infancy. One major challenge is that the AM “manifesto” emphasizes among its core values, “working software over comprehensive documentation”. Similarly another value Agile proponents hold dear is “trustworthy transparency over tiresome traceability”. Yet HISE must often be certified by the appropriate regulatory body before entering service. This normally involves submission to the appropriate regulatory authority of a dependability case (a reasoned argument that the system is acceptably secure/reliable/safe to operate), typically including claims and supporting evidence of adherence to appropriate standards. Such standards like DO178b, EN-50128 and IEC 61508 mandate production of certain documentation, and, traceability between these artifacts; all incidentally also recommend use of Formal (mathematical development) Methods, including CSP, LOTOS, Temporal Logic, VDM, Z and B, methods at best seen as orthogonal and at worst opposing to an Agile approach.
This research aims to modify Scrum to incorporate the fundamental (heavyweight) needs of engineering high integrity systems, while retaining the lightweight ‘touch’ of Agile Methods. In particular we devise a method for integrating tools supporting the varied range of development and assessment notations and techniques (including Formal Methods) used by HIS engineers, while enabling generation of cross tool traceability links between artifacts.
| | Curricular : | MSIT | | Record link: | http://libsearch.siu.ac.th/siu/opac_css/index.php?lvl=notice_display&id=24138 |
|
Add the result to your basket Refine your search Apply to external sources Make a suggestionThe unified modeling language user guide / Booch Grady / Upper Saddle River, NJ : Addison-Wesley - 2005
