Program Development By Refinement Case Studies Using The B Method(1st Edition)

Authors:

Emil Sekerinski ,Kaisa Sere

Type:Hardcover/ PaperBack / Loose Leaf
Condition: Used/New

In Stock: 2 Left

Shipment time

Expected shipping within 2 - 3 Days
Access to 35 Million+ Textbooks solutions Free
Ask Unlimited Questions from expert AI-Powered Answers 30 Min Free Tutoring Session
7 days-trial

Total Price:

$0

List Price: $6.00 Savings: $6 (100%)
Access to 30 Million+ solutions
Ask 50 Questions from expert AI-Powered Answers 24/7 Tutor Help Detailed solutions for Program Development By Refinement Case Studies Using The B Method

Price:

$9.99

/month

Book details

ISBN: 1852330538, 978-1852330538

Book publisher: Springer

Offer Just for You!: Buy 2 books before the end of January and enter our lucky draw.

Book Price $0 : The Idea Of Program Refinement Programs Are Complex. They Are Typically So Complex, That They Go Beyond The Full Comprehension Even Of The Programmer Or Team Who Designed Them, With All The Consequences This Has. How Can We Cope With Such Complexity In A Satisfactory Way? An Approach, Advocated For A Long Time, Is To Separate A Concise Specification Of A Program - The "what" - From A Possibly Involved Implementation - The "how". Once A Specification Is Obtained From The Set Of Requirements On The Program, There Can Still Be A Large Gap To An Efficient Implementation. The Development From Specification To Implementation Can Then Proceed By A Succession Oflayers, Such That Each Layer Is A Refinement Of The Previous One. Design Decisions Can Be Introduced In Refinement Steps One At A Time. By This, The Refinement Steps Can Be Kept Small And Manageable. Still, The Set Of All Requirements Can Be Far Too Large To Be Taken Completely Into Account In The Initial Specification. Even If They Could, They Might Obscure Issues More Than Clarify Them. For Example: • An Information System For Stored Goods Needs To Produce An Error Message On Il­ Legal Input. Yet, The Exact Wording - And Even The Language - Of Those Messages Is Irrelevant For An Understanding Of The Essence Of The System. • A Banking Application Interacts With Customers With A Graphical Interface. Yet The Specification Of The Graphical Layout Is Secondary Compared To The Specification Of The Possible Transactions.