Beginning C# 2008 Objects: From Concept to CodeAs a Java developer and instructor, Jacquie Barker wrote her first book, Beginning Java Objects, to communicate her passionate belief that learning objects thoroughly is an essential first step in mastering an object-oriented programming language (OOPL). Since Beginning Java Objects was first published in November 2000, we’ve heard from countless readers who agree wholeheartedly! We were therefore delighted when Gary Cornell, the publisher of Apress, and Dominic Shakeshaft, Apress editorial director, approached us about producing a C# version of Beg- ning Java Objects. It’s indeed true that basic object concepts are “language neutral. ” What you’ll learn conceptually about objects in Part One of this book, and about object modeling in Part Two, could apply equally well to any OOPL. But our goal for this book is twofold: not only do we want to teach you about objects and object modeling, but we also want to get you properly jump-started with the C# programming language by showing you how such concepts translate into C# syntax specifically. Hence, Beginning C# Objects was born! The first edition of Beginning C# Objects came out in the spring of 2004. Since that time, C# and the . NET platform have grown by leaps and bounds. Several new releases of the . NET Framework have come out, and many exciting new features have been added to the C# p- gramming language. This second edition of the book captures the “latest and greatest” of . |
Contents
CHAPTER | 4 |
CHAPTER | 5 |
CHAPTER | 7 |
PART THREE Translating a UML Blueprint | 13 |
CHAPTER | 14 |
CHAPTER | 15 |
CHAPTER | 16 |
Abstraction and Modeling | 45 |
Specifying Use Cases | 256 |
Modeling the StaticData Aspects of the System | 261 |
Modeling the DynamicBehavioral Aspects | 307 |
Scenarios | 313 |
Using Sequence Diagrams to Determine Methods | 322 |
Wrapping Up Our Modeling Efforts | 329 |
PART THREE Translating a UML Blueprint | 337 |
Transforming Our UML Model into C Code | 409 |
BehaviorOperationsMethods | 59 |
Object Interactions | 75 |
Method Invocation and Dot Notation | 84 |
Information HidingAccessibility | 97 |
The Power of Encapsulation | 114 |
Constructors | 122 |
Collections of Objects | 165 |
INDEX | 170 |
Collections As Method Return Types | 183 |
Summary | 189 |
PART TWO Object Modeling 101 | 239 |
Formalizing Requirements Through Use Cases | 249 |
Rounding Out Our Application Part | 467 |
CourseCatalog | 490 |
Changes to ScheduleOfClasses | 498 |
Course Modifications | 507 |
Adding a Graphical User Interface | 523 |
Creating the Look of Our GUI | 539 |
Adding Functionality Through Event Handling | 567 |
Summary | 599 |
Next Steps | 601 |
APPENDIX B Downloading and Compiling the SRS Source Code | 619 |
Other editions - View all
Beginning C# 2008 Objects: From Concept To Code Grant Palmer,Jacquie Barker No preview available - 2008 |
Common terms and phrases
abstraction accessor addition application argument array assigned association base class bool braces break Chapter client code collection compiler complex condition constructor Course Course object create declared defined derived class details omitted discussed double elements equal error example execute expression false field Figure finished given GraduateStudent hierarchy implementation inheritance initial instantiate interface invoked keyword known language later line of code logical look loop Main major method method call method header multiple notation Note operator override particular passed perform Person preceding Print private string Professor public class Student reference represent request requirements result rules shown simple single specific statement static string name Student class Student object syntax Transcript true variable void write