Pascal Eck (39 results)

Condition: Good. Good condition ex-library book with usual library markings and stickers.

Paperback. Condition: Good. 1. It's a preowned item in good condition and includes all the pages. It may have some general signs of wear and tear, such as markings, highlighting, slight damage to the cover, minimal wear to the binding, etc., but they will not affect the overall reading experience.

Condition: Good. Former library book; may include library markings. Used book that is in clean, average condition without any missing pages.

Condition: Good. Used Item. Does not include New Access Codes , Cd's or one time use items that come when New. This item is Used.

Condition: New.

Condition: New.

Paperback. Condition: New. Have you ever felt frustrated working with someone else's code? Difficult-to-maintain source code is a big problem in software development today, leading to costly delays and defects. Be part of the solution. With this practical book, you'll learn 10 easy-to-follow guidelines for delivering Java software that's easy to maintain and adapt. These guidelines have been derived from analyzing hundreds of real-world systems. Written by consultants from the Software Improvement Group (SIG), this book provides clear and concise explanations, with advice for turning the guidelines into practice. Examples for this edition are written in Java, while our companion C# book provides workable examples in that language.Write short units of code: limit the length of methods and constructors Write simple units of code: limit the number of branch points per method Write code once, rather than risk copying buggy code Keep unit interfaces small by extracting parameters into objects Separate concerns to avoid building large classes Couple architecture components loosely Balance the number and size of top-level components in your code Keep your codebase as small as possible Automate tests for your codebase Write clean code, avoiding "code smells" that indicate deeper problems.

Paperback. Condition: New. Have you ever felt frustrated working with someone else's code? Difficult-to-maintain source code is a big problem in software development today, leading to costly delays and defects. Be part of the solution. With this practical book, you'll learn 10 easy-to-follow guidelines for delivering Java software that's easy to maintain and adapt. These guidelines have been derived from analyzing hundreds of real-world systems. Written by consultants from the Software Improvement Group (SIG), this book provides clear and concise explanations, with advice for turning the guidelines into practice. Examples for this edition are written in Java, while our companion C# book provides workable examples in that language.Write short units of code: limit the length of methods and constructors Write simple units of code: limit the number of branch points per method Write code once, rather than risk copying buggy code Keep unit interfaces small by extracting parameters into objects Separate concerns to avoid building large classes Couple architecture components loosely Balance the number and size of top-level components in your code Keep your codebase as small as possible Automate tests for your codebase Write clean code, avoiding "code smells" that indicate deeper problems.

Paperback. Condition: New. Have you ever felt frustrated working with someone else's code? Difficult-to-maintain source code is a big problem in software development today, leading to costly delays and defects. Be part of the solution. With this practical book, you'll learn 10 easy-to-follow guidelines for delivering C# software that's easy to maintain and adapt. These guidelines have been derived from analyzing hundreds of real-world systems. Written by consultants from the Software Improvement Group (SIG), this book provides clear and concise explanations, with advice for turning the guidelines into practice. Examples for this edition are written in C#, while our companion Java book provides clear examples in that language.Write short units of code: limit the length of methods and constructors Write simple units of code: limit the number of branch points per method Write code once, rather than risk copying buggy code Keep unit interfaces small by extracting parameters into objects Separate concerns to avoid building large classes Couple architecture components loosely Balance the number and size of top-level components in your code Keep your codebase as small as possible Automate tests for your codebase Write clean code, avoiding "code smells" that indicate deeper problems.

Condition: New.

Paperback. Condition: New. Have you ever felt frustrated working with someone else's code? Difficult-to-maintain source code is a big problem in software development today, leading to costly delays and defects. Be part of the solution. With this practical book, you'll learn 10 easy-to-follow guidelines for delivering C# software that's easy to maintain and adapt. These guidelines have been derived from analyzing hundreds of real-world systems. Written by consultants from the Software Improvement Group (SIG), this book provides clear and concise explanations, with advice for turning the guidelines into practice. Examples for this edition are written in C#, while our companion Java book provides clear examples in that language.Write short units of code: limit the length of methods and constructors Write simple units of code: limit the number of branch points per method Write code once, rather than risk copying buggy code Keep unit interfaces small by extracting parameters into objects Separate concerns to avoid building large classes Couple architecture components loosely Balance the number and size of top-level components in your code Keep your codebase as small as possible Automate tests for your codebase Write clean code, avoiding "code smells" that indicate deeper problems.

Condition: New. SUPER FAST SHIPPING.

Condition: New. SUPER FAST SHIPPING.

Condition: New. In.

Condition: New. In.

Condition: New.

Paperback. Condition: new. Paperback. This book constitutes the refereed proceedings of the 21st International Conference on Advanced Information Systems Engineering, CAiSE 2009, held in Amsterdam, The Netherlands, on June 8-12, 2009. The 36 papers presented in this book together with 6 keynote papers were carefully reviewed and selected from 230 submissions. The topics covered are model driven engineering, conceptual modeling, quality and data integration, goal-oriented requirements engineering, requirements and architecture, service orientation, Web service orchestration, value-driven modeling, workflow, business process modeling, and requirements engineering. The topics covered are model driven engineering, conceptual modeling, quality and data integration, goal-oriented requirements engineering, requirements and architecture, service orientation, Web service orchestration, value-driven modeling, workflow, business process modeling, and requirements engineering. Shipping may be from multiple locations in the US or from the UK, depending on stock availability.

Condition: New. SUPER FAST SHIPPING.

Condition: New.

Condition: As New. Unread book in perfect condition.

Paperback. Condition: Brand New. 145 pages. 9.25x7.00x0.25 inches. In Stock.

Paperback. Condition: Brand New. 1st edition. 149 pages. 9.00x7.00x0.50 inches. In Stock.

Paperback. Condition: New. Have you ever felt frustrated working with someone else's code? Difficult-to-maintain source code is a big problem in software development today, leading to costly delays and defects. Be part of the solution. With this practical book, you'll learn 10 easy-to-follow guidelines for delivering Java software that's easy to maintain and adapt. These guidelines have been derived from analyzing hundreds of real-world systems. Written by consultants from the Software Improvement Group (SIG), this book provides clear and concise explanations, with advice for turning the guidelines into practice. Examples for this edition are written in Java, while our companion C# book provides workable examples in that language.Write short units of code: limit the length of methods and constructors Write simple units of code: limit the number of branch points per method Write code once, rather than risk copying buggy code Keep unit interfaces small by extracting parameters into objects Separate concerns to avoid building large classes Couple architecture components loosely Balance the number and size of top-level components in your code Keep your codebase as small as possible Automate tests for your codebase Write clean code, avoiding "code smells" that indicate deeper problems.

Paperback. Condition: New. Have you ever felt frustrated working with someone else's code? Difficult-to-maintain source code is a big problem in software development today, leading to costly delays and defects. Be part of the solution. With this practical book, you'll learn 10 easy-to-follow guidelines for delivering C# software that's easy to maintain and adapt. These guidelines have been derived from analyzing hundreds of real-world systems. Written by consultants from the Software Improvement Group (SIG), this book provides clear and concise explanations, with advice for turning the guidelines into practice. Examples for this edition are written in C#, while our companion Java book provides clear examples in that language.Write short units of code: limit the length of methods and constructors Write simple units of code: limit the number of branch points per method Write code once, rather than risk copying buggy code Keep unit interfaces small by extracting parameters into objects Separate concerns to avoid building large classes Couple architecture components loosely Balance the number and size of top-level components in your code Keep your codebase as small as possible Automate tests for your codebase Write clean code, avoiding "code smells" that indicate deeper problems.

Condition: New. In.

Condition: New. Constitutes the refereed proceedings of the 21st International Conference on Advanced Information Systems Engineering, CAiSE 2009, held in Amsterdam, The Netherlands, on June 8-12, 2009. This book covers topics such as model driven engineering, conceptual modeling, quality and data integration, and goal-oriented requirements engineering. Editor(s): Eck, Pascal van; Gordijn, Jaap; Wieringa, Roel J. Series: Lecture Notes in Computer Science / Information Systems and Applications, Incl. Internet/Web, and HCI. Num Pages: 580 pages, biography. BIC Classification: KJQ; UBJ; UKR; UNF; UYZ. Category: (P) Professional & Vocational. Dimension: 235 x 155 x 30. Weight in Grams: 884. . 2009. Paperback. . . . .

Condition: New. With this practical book, you ll learn 10 easy-to-follow guidelines for delivering C# software that s easy to maintain and adapt. These guidelines have been derived from analyzing hundreds of real-world systems.&Uumlber den Autorrnrn.

Condition: New. Constitutes the refereed proceedings of the 21st International Conference on Advanced Information Systems Engineering, CAiSE 2009, held in Amsterdam, The Netherlands, on June 8-12, 2009. This book covers topics such as model driven engineering, conceptual modeling, quality and data integration, and goal-oriented requirements engineering. Editor(s): Eck, Pascal van; Gordijn, Jaap; Wieringa, Roel J. Series: Lecture Notes in Computer Science / Information Systems and Applications, Incl. Internet/Web, and HCI. Num Pages: 580 pages, biography. BIC Classification: KJQ; UBJ; UKR; UNF; UYZ. Category: (P) Professional & Vocational. Dimension: 235 x 155 x 30. Weight in Grams: 884. . 2009. Paperback. . . . . Books ship from the US and Ireland.

Paperback. Condition: New. Have you ever felt frustrated working with someone else's code? Difficult-to-maintain source code is a big problem in software development today, leading to costly delays and defects. Be part of the solution. With this practical book, you'll learn 10 easy-to-follow guidelines for delivering Java software that's easy to maintain and adapt. These guidelines have been derived from analyzing hundreds of real-world systems. Written by consultants from the Software Improvement Group (SIG), this book provides clear and concise explanations, with advice for turning the guidelines into practice. Examples for this edition are written in Java, while our companion C# book provides workable examples in that language.Write short units of code: limit the length of methods and constructors Write simple units of code: limit the number of branch points per method Write code once, rather than risk copying buggy code Keep unit interfaces small by extracting parameters into objects Separate concerns to avoid building large classes Couple architecture components loosely Balance the number and size of top-level components in your code Keep your codebase as small as possible Automate tests for your codebase Write clean code, avoiding "code smells" that indicate deeper problems.

Paperback. Condition: New. Have you ever felt frustrated working with someone else's code? Difficult-to-maintain source code is a big problem in software development today, leading to costly delays and defects. Be part of the solution. With this practical book, you'll learn 10 easy-to-follow guidelines for delivering C# software that's easy to maintain and adapt. These guidelines have been derived from analyzing hundreds of real-world systems. Written by consultants from the Software Improvement Group (SIG), this book provides clear and concise explanations, with advice for turning the guidelines into practice. Examples for this edition are written in C#, while our companion Java book provides clear examples in that language.Write short units of code: limit the length of methods and constructors Write simple units of code: limit the number of branch points per method Write code once, rather than risk copying buggy code Keep unit interfaces small by extracting parameters into objects Separate concerns to avoid building large classes Couple architecture components loosely Balance the number and size of top-level components in your code Keep your codebase as small as possible Automate tests for your codebase Write clean code, avoiding "code smells" that indicate deeper problems.