Resource
Article [7216]
General
[1038]
Acceptance
[63]
Ad Hoc
[28]
Agile, Scrum
[233]
Black Box
[117]
Bug, Defect
[258]
DB, Test Data
[275]
Environment
[43]
Functional
[115]
Glossary, Term
[74]
GUI, Usability
[98]
Integrate test
[47]
Interview, FAQ
[288]
Manual Testing
[117]
Methodology
[232]
Metrics
[332]
Mobile, Embed
[154]
Performance
[327]
Process
[194]
Requirement
[124]
Review, Static
[102]
Risk
[99]
Security Test
[215]
Standard, ISO
[179]
Test Automate
[349]
Test Case
[342]
Test Design
[70]
Test Plan
[314]
Test Manage
[229]
Test Script
[56]
Test Technique
[265]
Tool
[176]
Tool- Jmeter
[41]
Tool- Selenium
[127]
Unit Test
[167]
Web Test
[258]
White Box
[70]
Ebook [1168]
General
[281]
Acceptance
[3]
Agile, Scrum
[24]
DB Test
[76]
Development
[137]
GUI, Usability
[17]
Interview, FAQ
[9]
Java Test
[68]
Metrics
[17]
Mobile, Embed
[14]
Performance
[49]
Process
[11]
Requirement
[55]
Review, Analysis
[8]
Risk
[7]
Security Test
[71]
Standard
[20]
Test Manage
[86]
Test Automate
[84]
Tool
[8]
Unit Test
[67]
Web Test
[60]
Testing Tool [2277]
Acceptance
[25]
Agile, Scrum
[42]
Bug Tracking
[127]
Build, Release
[27]
Environment
[58]
DB, Test Data
[83]
Functional
[240]
GUI, Usability
[79]
Java Test
[71]
Metrics
[57]
Mobile, Embed
[79]
Network Test
[67]
Performance
[222]
Requirement
[62]
Review, Static
[105]
Security Test
[111]
Test Design
[52]
Test Manage
[208]
Unit, Debug
[224]
Utility, Capture
[97]
Web Testing
[235]
Video [622]
News [2773]
Webinar [914]
Certification Resource
CTAL [271]
CTEL [35]
CSTE, CSQA [198]
CSQE [41]
CMMI, TMMI [135]
PMP [115]
ITIL [67]
Six Sigma [41]
Other [83]
Forum
Forum [1943]
Book
[56]
Certification
[48]
Conference
[64]
ISTQB
[159]
QTP
[93]
Software Test
[1066]
Standard, ISO
[89]
Testing Tool
[289]
2010.01.29 03:25:48
3319
Preface
Object-oriented design is common in computing systems development. There is a plethora of techniques and an abundance of texts on the subject. Why, then, a book on validated designs for object-oriented systems? Our experience with specification, modelling and analysis techniques over the last decade tells us that object-oriented design is much more than mere “boxes and arrows.” Systems developers should be able to combine techniques and tools to achieve designs that are not merely the subject
of heated argument but can be improved by careful, rigorous and machine-supported analysis. This book describes an approach to the design of object-oriented systems which combines the benefits of abstract modelling with the analytic power of formal
methods to give designs that can be rigorously validated and assured with automated support.
System modelling has a valuable contribution to make in the development of computing systems. It encourages abstract, systematic and comprehensive consideration of system aspects, including the description of functionality, interactions with the environment and temporal behaviour. The rising level of interest in modelling is evidenced by the central role being taken by model-driven development approaches within the software engineering communities, such as the model-driven architecture work by the Object Management Group. Formal methods can bring further tangible benefits to systems and software development, including objectivity and rigour of analysis, without compromising abstraction. However, these benefits can only be realised in practice if formal techniques are carefully targeted. In particular, formal techniques cannot be applied in isolation but must work alongside other analysis and design tools. The successful application of these techniques is regularly reported. This book stands in the tradition of “Lightweight” formal methods. Its aim is to equip readers with the ability to take advantage of formal modelling techniques without necessarily having to deploy the whole panoply of formal methods. We show how a formal notation (VDM++) can be used to complement and enhance object-oriented class models, with the engineer free to move between the class structure view and the functional view in VDM++. The approach shows how formal techniques can be used to take practitioners on from where they are, rather than requiring a radical shake-up of existing practice.
Object-oriented design is common in computing systems development. There is a plethora of techniques and an abundance of texts on the subject. Why, then, a book on validated designs for object-oriented systems? Our experience with specification, modelling and analysis techniques over the last decade tells us that object-oriented design is much more than mere “boxes and arrows.” Systems developers should be able to combine techniques and tools to achieve designs that are not merely the subject
of heated argument but can be improved by careful, rigorous and machine-supported analysis. This book describes an approach to the design of object-oriented systems which combines the benefits of abstract modelling with the analytic power of formal
methods to give designs that can be rigorously validated and assured with automated support.
System modelling has a valuable contribution to make in the development of computing systems. It encourages abstract, systematic and comprehensive consideration of system aspects, including the description of functionality, interactions with the environment and temporal behaviour. The rising level of interest in modelling is evidenced by the central role being taken by model-driven development approaches within the software engineering communities, such as the model-driven architecture work by the Object Management Group. Formal methods can bring further tangible benefits to systems and software development, including objectivity and rigour of analysis, without compromising abstraction. However, these benefits can only be realised in practice if formal techniques are carefully targeted. In particular, formal techniques cannot be applied in isolation but must work alongside other analysis and design tools. The successful application of these techniques is regularly reported. This book stands in the tradition of “Lightweight” formal methods. Its aim is to equip readers with the ability to take advantage of formal modelling techniques without necessarily having to deploy the whole panoply of formal methods. We show how a formal notation (VDM++) can be used to complement and enhance object-oriented class models, with the engineer free to move between the class structure view and the functional view in VDM++. The approach shows how formal techniques can be used to take practitioners on from where they are, rather than requiring a radical shake-up of existing practice.
Service
New
Popular Documents
Monthly
Yearly
Popular Download
Weekly
Monthly
Twitter
Tag List
Plan
security
mobile application testing
process
tester
checklist
QTP
Exam
mobile testing
Development
Certification
agile testing
mobile
Quality
testing
Metrics
software qa service
software testing company
performance
Sample Exam
HP
web
test plan
Guide
Unit Testing
Questions
Sql
Software Testing
Performance Testing
Test Automation
web testing
Automation
Manual
Interview
conference
outsourcing software testing
Test
QA
framework
agile
Test Case
Selenium
ISTQB
Bug
security testing
PM
Template
Software
QC
Management
tool
Visitor
Member Login (IP)
180975
51749
210028655
Yesterday
Today
Total

 
 
rua_0611