Software Engineering in the Agile World
暫譯: 敏捷世界中的軟體工程
Mr. Ashfaque Ahmed
- 出版商: CreateSpace Independent Publishing Platform
- 出版日期: 2018-01-12
- 語言: 英文
- 頁數: 314
- 裝訂: Paperback
- ISBN: 1983801577
- ISBN-13: 9781983801570
-
相關分類:
Agile Software、軟體工程
已絕版
買這商品的人也買了...
-
$1,420$1,349 -
$352DevOps 實踐 (Practical DevOps)
-
$199輕量級 Django
-
$400$340 -
$281修改軟件的藝術 : 構建易維護代碼的 9條最佳實踐 (Beyond Legacy Code: Nine Practices to Extend the Life (and Value) of Your Software)
-
$297Python 新手學 Django 2.0 架站的 16堂課, 2/e
-
$505Kotlin 編程權威指南
-
$520$411 -
$236Python Web 開發基礎教程 (Django版)(微課版)
-
$500$425 -
$556Jetpack Compose 從入門到實戰
-
$580$406
相關主題
商品描述
This book covers whole gamut of software engineering. The first chapter is on software engineering methodologies. Both Waterfall and Agile software engineering methodologies have been discussed in length. I have also provided information as to how each methodology stacks up against each other. Scrum is especially covered extensively as it has become very popular and learning Scrum is essential as it is being used more and more on software projects. The second chapter is on software requirement engineering. After you have gone through this chapter, you will be able to build user stories and other types of software requirement engineering documents. The third chapter is on software project management. Since we learned as to how to create good software requirements in Chapter 2; now we can do project planning activities for these software requirements. The fourth chapter is on software feasibility studies. For each software requirement; we can find out feasible solutions using prototyping techniques which are discussed in this chapter. The fifth chapter is on software high level design. A software product consists of many pieces and understanding it from a higher level is important. Also using pre defined templates in form of architecture and software patterns helps in building software products more productively. Chapter 6 is devoted to learn user interface design. We can learn how to build user interfaces using mock up screens. Chapter 7 is concerned about learning as to how to design and program so that business logic can be implemented. We will learn all object oriented design concepts including class diagrams, object diagrams, sequence diagrams, statechart diagrams etc. Programming concepts like variables, methods, classes and objects are also covered extensively. Chapter 8 is about database design. We will learn about Entity Relationship diagrams and other concepts to design databases for software products. Chapter 9 is about software testing. We will learn everything about unit, integration, system, and user acceptance testing in this chapter. Chapter 10 is about software maintenance. Apart from software maintenance; we will also learn about production instances of software products in this chapter. Chapter 11 is about project execution and conflict management. We will learn about project tracking techniques like Gantt charts for Waterfall projects and burn-down chart for Agile projects. Learning software engineering also involves project management. The main case study involves building a software product which is known as smart city. This software product can be used to provide information about a city (colleges, libraries, hotels, industries, parks, museums, zoos, restaurants, malls etc.). The case studies I have provided are all based on Scrum. Software engineering is completely aligned with Scrum in the case study. Software requirements are in form of user stories. Project management is provided in terms of Release and Sprint planning. Even daily planning is also discussed. As a software product must be developed incrementally; I have provided enough material to learn as to how to develop a software product incrementally. The Release and Sprint planning for the software products we will be building; are explained lucidly and you will learn these aspects while you build a software product. User interfaces are designed and implemented incrementally using mock up screens. Business logic is designed and implemented incrementally using classes. Even database is also designed incrementally. Unit, integration, system and user acceptance testing is also discussed in terms of incrementally building the software product. The smart city product is built over 3 Releases using 10 Sprints.
商品描述(中文翻譯)
這本書涵蓋了軟體工程的各個方面。第一章介紹了軟體工程方法論,詳細討論了瀑布式(Waterfall)和敏捷(Agile)軟體工程方法論。我也提供了每種方法論之間的比較資訊。Scrum 特別被廣泛討論,因為它已變得非常流行,學習 Scrum 是必須的,因為它在軟體專案中被越來越多地使用。第二章專注於軟體需求工程。在閱讀完這一章後,您將能夠建立用戶故事和其他類型的軟體需求工程文件。第三章是關於軟體專案管理。由於我們在第二章學會了如何創建良好的軟體需求,現在我們可以針對這些軟體需求進行專案規劃活動。第四章是關於軟體可行性研究。對於每個軟體需求,我們可以使用本章討論的原型技術來找出可行的解決方案。第五章是關於軟體高層設計。軟體產品由許多部分組成,從更高的層面理解它是很重要的。此外,使用預定義的架構和軟體模式模板有助於更高效地構建軟體產品。第六章專注於學習用戶介面設計。我們可以學習如何使用模擬畫面來構建用戶介面。第七章關注於學習如何設計和編程,以便實現業務邏輯。我們將學習所有面向對象設計的概念,包括類圖、物件圖、序列圖、狀態圖等。編程概念如變數、方法、類和物件也會被廣泛討論。第八章是關於資料庫設計。我們將學習實體關係圖(Entity Relationship diagrams)和其他概念,以設計軟體產品的資料庫。第九章是關於軟體測試。我們將在這一章中學習有關單元測試、整合測試、系統測試和用戶驗收測試的所有內容。第十章是關於軟體維護。除了軟體維護外,我們還將在這一章中學習有關軟體產品的生產實例。第十一章是關於專案執行和衝突管理。我們將學習專案追蹤技術,如瀑布專案的甘特圖(Gantt charts)和敏捷專案的燃盡圖(burn-down chart)。學習軟體工程也涉及專案管理。主要案例研究涉及構建一個名為智慧城市(smart city)的軟體產品。這個軟體產品可以用來提供有關城市的信息(如大學、圖書館、飯店、工業、公園、博物館、動物園、餐廳、購物中心等)。我提供的案例研究都是基於 Scrum。軟體工程在案例研究中與 Scrum 完全對齊。軟體需求以用戶故事的形式呈現。專案管理以版本(Release)和衝刺(Sprint)規劃的形式提供。甚至每日規劃也有討論。由於軟體產品必須逐步開發,我提供了足夠的材料來學習如何逐步開發軟體產品。我們將構建的軟體產品的版本和衝刺規劃被清晰地解釋,您將在構建軟體產品的過程中學習這些方面。用戶介面是使用模擬畫面逐步設計和實現的。業務邏輯是使用類逐步設計和實現的。資料庫也同樣是逐步設計的。單元測試、整合測試、系統測試和用戶驗收測試也以逐步構建軟體產品的方式進行討論。智慧城市產品是通過 3 次版本和 10 次衝刺來構建的。