دسترسی نامحدود
برای کاربرانی که ثبت نام کرده اند
برای ارتباط با ما می توانید از طریق شماره موبایل زیر از طریق تماس و پیامک با ما در ارتباط باشید
در صورت عدم پاسخ گویی از طریق پیامک با پشتیبان در ارتباط باشید
برای کاربرانی که ثبت نام کرده اند
درصورت عدم همخوانی توضیحات با کتاب
از ساعت 7 صبح تا 10 شب
ویرایش: 1
نویسندگان: Randall Hyde
سری:
ISBN (شابک) : 9781593279790, 2003017502
ناشر: No Starch Press
سال نشر: 2020
تعداد صفحات: 378
زبان: English
فرمت فایل : PDF (درصورت درخواست کاربر به PDF، EPUB یا AZW3 تبدیل می شود)
حجم فایل: 10 مگابایت
در صورت تبدیل فایل کتاب Write Great Code به فرمت های PDF، EPUB، AZW3، MOBI و یا DJVU می توانید به پشتیبان اطلاع دهید تا فایل مورد نظر را تبدیل نمایند.
توجه داشته باشید کتاب نوشتن کد عالی: نرم افزار مهندسی نسخه زبان اصلی می باشد و کتاب ترجمه شده به فارسی نمی باشد. وبسایت اینترنشنال لایبرری ارائه دهنده کتاب های زبان اصلی می باشد و هیچ گونه کتاب ترجمه شده یا نوشته شده به فارسی را ارائه نمی دهد.
نرمافزار مهندسی، جلد سوم از مجموعههای شاخص Write Great Code توسط Randall Hyde، به شما کمک میکند کدی خوانا و قابل نگهداری بسازید که باعث شگفتی برنامهنویسان دیگر شود. حوزه مهندسی نرمافزار ممکن است بهرهوری تیم را بر رشد فردی ارج بگذارد، اما دانشمند افسانهای رایانه، رندال هاید، میخواهد برنامهنویسان امیدوارکننده را به استادان حرفهشان تبدیل کند. برای این منظور، نرمافزار مهندسی - جدیدترین جلد از مجموعههای بسیار معتبر Write Great Code از Hyde - پوشش عمیقی از همه چیز از روششناسی توسعه و بهرهوری استراتژیک گرفته تا الزامات طراحی شیگرا و مستندات سیستم را ارائه میدهد. یاد خواهید گرفت: • چرا پیروی از مدل کاردستی نرم افزار می تواند شما را به انجام بهترین کار سوق دهد • چگونه می توان از قابلیت ردیابی برای ایجاد ثبات در اسناد خود استفاده کرد • مراحل ایجاد الزامات UML خود با تجزیه و تحلیل موردی • چگونه از استانداردهای اسناد IEEE برای ایجاد نرم افزار بهتر استفاده کنیم این کارآموزی پیشرفته در مهارتها، نگرشها و اخلاقیات توسعه نرمافزار با کیفیت، راه درست اعمال اصول مهندسی در برنامهنویسی را نشان میدهد. هاید قوانین را به شما آموزش می دهد و به شما نشان می دهد که چه زمانی آنها را زیر پا بگذارید. در طول راه، او بینشهای روشنکنندهای را در مورد بهترین شیوهها ارائه میکند و در عین حال به شما قدرت میدهد تا موارد جدید اختراع کنید. نرم افزار مهندسی مملو از منابع و مملو از مثال ها، راهنمای شما برای نوشتن کد است که شما را از همتایان خود متمایز می کند.
Engineering Software, the third volume in the landmark Write Great Code series by Randall Hyde, helps you create readable and maintainable code that will generate awe from fellow programmers. The field of software engineering may value team productivity over individual growth, but legendary computer scientist Randall Hyde wants to make promising programmers into masters of their craft. To that end, Engineering Software--the latest volume in Hyde's highly regarded Write Great Code series--offers his signature in-depth coverage of everything from development methodologies and strategic productivity to object-oriented design requirements and system documentation. You'll learn: • Why following the software craftsmanship model can lead you to do your best work • How to utilize traceability to enforce consistency within your documentation • The steps for creating your own UML requirements with use-case analysis • How to leverage the IEEE documentation standards to create better software This advanced apprenticeship in the skills, attitudes, and ethics of quality software development reveals the right way to apply engineering principles to programming. Hyde will teach you the rules, and show you when to break them. Along the way, he offers illuminating insights into best practices while empowering you to invent new ones. Brimming with resources and packed with examples, Engineering Software is your go-to guide for writing code that will set you apart from your peers.
Brief Contents Contents in Detail Acknowledgments Introduction Assumptions and Prerequisites What Is Great Code? Programmer Classifications Amateurs Programmers Software Engineers Great Programmers So You Want to Be a Great Programmer A Final Note on Ethics and Character For More Information Part 1: Personal Software Engineering Chapter 1: Software Development Metaphors What Is Software? Software Is Not Manufactured Software Doesn’t Wear Out Most Software Is Custom Software Can Be Easily Upgraded Software Is Not an Independent Entity Parallels to Other Fields Programmer as Artist Programmer as Architect Programmer as Engineer Programmer as Craftsman Artist, Architect, Engineer, or Craftsman? Software Engineering A Formal Definition Project Size Where Software Engineering Fails Software Craftsmanship Education Apprenticeship The Software Journeyman The Master Craftsman Where Software Craftsmanship Fails The Path to Writing Great Code For More Information Chapter 2: Productivity What Is Productivity? Programmer Productivity vs. Team Productivity Man-Hours and Real Time Conceptual and Scope Complexity Predicting Productivity Metrics and Why We Need Them Executable Size Metric Machine Instructions Metric Lines of Code Metric Statement Count Metric Function Point Analysis McCabe’s Cyclomatic Complexity Metric Other Metrics The Problem with Metrics How Do We Beat 10 Lines per Day? Estimating Development Time Estimating Small Project Development Time Estimating Medium and Large Project Development Time Problems with Estimating Development Time Crisis Mode Project Management How to Be More Productive Choose Software Development Tools Wisely Manage Overhead Set Clear Goals and Milestones Practice Self-Motivation Focus and Eliminate Distractions If You’re Bored, Work on Something Else Be as Self-Sufficient as Possible Recognize When You Need Help Overcome Poor Morale For More Information Chapter 3: Software Development Models The Software Development Life Cycle The Software Development Model The Informal Model The Waterfall Model The V Model The Iterative Model The Spiral Model The Rapid Application Development Model The Incremental Model Software Development Methodologies Traditional (Predictive) Methodologies Adaptive Methodologies Agile Extreme Programming Scrum Feature-Driven Development Models and Methodologies for the Great Programmer For More Information Part 2: UML Chapter 4: An Introduction to UML and Use Cases The UML Standard The UML Use Case Model Use Case Diagram Elements Use Case Packages Use Case Inclusion Use Case Generalization Use Case Extension Use Case Narratives Use Case Scenarios The UML System Boundary Diagrams Beyond Use Cases For More Information Chapter 5: UML Activity Diagrams UML Activity State Symbols Start and Stop States Activities States Transitions Conditionals Merge Points Events and Triggers Forks and Joins (Synchronization) Call Symbols Partitions Comments and Annotations Connectors Additional Activity Diagram Symbols Extending UML Activity Diagrams For More Information Chapter 6: UML Class Diagrams Object-Oriented Analysis and Design in UML Visibility in a Class Diagram Public Class Visibility Private Class Visibility Protected Class Visibility Package Class Visibility Unsupported Visibility Types Class Attributes Attribute Visibility Attribute Derived Values Attribute Names Attribute Data Types Operation Data Types (Return Values) Attribute Multiplicity Default Attribute Values Property Strings Attribute Syntax Class Operations UML Class Relationships Class Dependency Relationships Class Association Relationships Class Aggregation Relationships Class Composition Relationships Relationship Features Class Inheritance Relationships Objects For More Information Chapter 7: UML Interaction Diagrams Sequence Diagrams Lifelines Message Types Message Labels Message Numbers Guard Conditions Iterations Long Delays and Time Constraints External Objects Activation Bars Branching Alternative Flows Object Creation and Destruction Sequence Fragments Collaboration Diagrams For More Information Chapter 8: Miscellaneous UML Diagrams Component Diagrams Package Diagrams Deployment Diagrams Composite Structure Diagrams Statechart Diagrams More UML For More Information Part 3: Documentation Chapter 9: System Documentation System Documentation Types Traceability Ways to Build Traceability into Your Documentation Tag Formats The Requirements/Reverse Traceability Matrix Validation, Verification, and Reviews Reducing Development Costs Using Documentation Reducing Costs via Validation Reducing Costs via Verification For More Information Chapter 10: Requirements Documentation Requirement Origins and Traceability A Suggested Requirements Format Characteristics of Good Requirements Design Goals The System Requirements Specification Document The Software Requirements Specification Document Introduction Overall Description Specific Requirements Supporting Information A Sample Software Requirements Specification Creating Requirements Use Cases Enable/Disable Debug Mode Enable/Disable Ethernet Enable/Disable RS-232 Enable/Disable Test Mode Enable/Disable USB Read DIP Switches Creating DAQ Software Requirements from the Use Cases (Selected) DAQ Software Requirements (from SRS) Updating the Traceability Matrix with Requirement Information Requirements to Be Verified by Review Requirements to Be Verified by Testing For More Information Chapter 11: Software Design Description Documentation IEEE Std 1016-1998 vs. IEEE Std 1016-2009 IEEE 1016-2009 Conceptual Model Design Concerns and Design Stakeholders Design Viewpoints and Design Elements Design Views, Overlays, and Rationales The IEEE Std 1016-2009 Conceptual Model SDD Required Contents SDD Identification Design Stakeholders and Their Design Concerns Design Views, Viewpoints, Overlays, and Rationales SDD Traceability and Tags A Suggested SDD Outline A Sample SDD Updating the Traceability Matrix with Design Information Creating a Software Design For More Information Chapter 12: Software Test Documentation The Software Test Documents in Std 829 Process Support Integrity Levels and Risk Assessment Software Development Testing Levels Test Plans Master Test Plan Level Test Plan Level Test Design Documentation Software Review List Documentation Sample SRL Outline Sample SRL Adding SRL Items to the Traceability Matrix Software Test Case Documentation Introduction in the STC Document Details General A Sample Software Test Case Document Updating the RTM with STC Information Software Test Procedure Documentation The IEEE Std 829-2009 Software Test Procedure Extended Outline for Software Test Procedure Introduction in the STP Document Test Procedures General Index A Sample STP Updating the RTM with STP Information Level Test Logs Introduction in the Level Test Logs Document Details Glossary A Few Comments on Test Logs Anomaly Reports Introduction in the Anomaly Reports Document Details A Few Comments on Anomaly Reports Test Reports Brief Mention of the Master Test Report Level Test Reports Do You Really Need All of This? For More Information Afterword: Designing Great Code Glossary Index