Special Offers see all
More at Powell'sRecently Viewed clear list
Original Essays | April 29, 2013
2 comments
|
$108.00
List price:
Used Trade Paper
Ships in 1 to 3 days
available for shipping or prepaid pickup only
Available for In-store Pickup
in 7 to 12 days
More copies of this ISBNProject-based Software Engineering : an Object-oriented Approach (02 Edition)by Evelyn Stiller
Synopses & ReviewsPlease note that used books may not include additional media (study guides, CDs, DVDs, solutions manuals, etc.) as described in the publisher comments.
Publisher Comments: Project-Based Software Engineering is the first textbook to provide hands-on process and practice in software engineering essentials for the beginner, enabling students without experience to gain real-world practice and see first-hand the benefits of utilizing software engineering techniques. The book presents steps through the software development life cycle, which are then realized via two running case studies that follow through the conceptualization, analysis, design, and implementation stages of the process. These case studies, which show the deliverables for each stage, can be worked through by a small software development team. A full software development project is also included so students can apply their understanding of and experience with the various phases of the process.
Project-Based Software Engineering focuses on object-oriented software development, and is structured for this paradigm. It takes a mostly language-independent approach (necessary code examples are in Java) and uses a subset of the Unified Modeling Language (UML) to model the software, explaining the notation as needed to support the students' work. This book is written for students and professionals alike whose goal is to gain hands-on experience in software project analysis, design, implementation, and testing. Book News Annotation:This textbook walks through the steps of the software development life cycle, illustrating the concepts through two running case studies. Separate chapters discuss requirements analysis, product design, class design, programming, testing, and maintenance. The authors (Plymouth State College) provide code examples in Java and use a subset of UML to model software.
Annotation c. Book News, Inc., Portland, OR (booknews.com) Synopsis: Project-Based Software Engineering is the first book to provide hands-on process and practice in software engineering essentials for the beginner. The book presents steps through the software development life cycle and two running case studies that develop as the steps are presented. Running parallel to the process presentation and case studies, the book supports a semester-long software development project. This book focuses on object-oriented software development, and supports the conceptualization, analysis, design and implementation of an object-oriented project. It is mostly language-independent, with necessary code examples in Java. A subset of UML is used, with the notation explained as needed to support the readers' work. Two running case studies a video game and a library check out system show the development of a software project. Both have sample deliverables and thus provide the reader with examples of the type of work readers are to create. This book is appropriate for readers looking to gain experience in project analysis, design implementation, and testing.
Table of Contents1. Introduction to Software Engineering.
Key Concepts.
Why Engineer Software?
Elements of a Software Development Paradigm.
A Brief History of Software Engineering Techniques.
The Costs of Not Engineering Software.
Why Software Engineering Is Not Universal.
The Role of the Project.
Working in Teams.
Creating the Project Team.
CLASS PROJECT: Functional Requirements.
Questions for Review.
2. Object-Oriented Paradigm Overview.
Key Concepts.
Getting Acquainted with the Class Project.
Object-Oriented Conceptualization.
The Software Life Cycle.
Object-Oriented Modeling.
Qualities of a Good Object-Oriented System.
Working in Teams.
Questions for Review.
3. Object-Oriented Analysis.
Key Concepts.
Introduction to Requirements Analysis.
The Importance of Requirements Analysis.
Requirements Specification.
CASE STUDY: Library Management System Specification.
Evaluating the Requirements Specification.
Refining the Requirements Specification.
Verifying the Requirements Specification.
Propagating Requirements throughout Development.
The Process of Requirements Analysis.
Analyzing the CLASS PROJECT.
Working in Teams.
Questions for Review.
4. Product Design.
Key Concepts.
Objectives of Design.
Class Design versus Product Design.
Product Design Overview and Objectives.
Object Persistence.
CASE STUDY: Object Persistence in LMS.
Process Architecture.
CASE STUDY: Interprocess Communication in LMS.
CLASS PROJECT: Interprocess Communication in Galaxy Sleuth.
User Interfaces.
User Interface Design.
User Interface Design Principles.
CASE STUDY: User Interface for LMS.
Working in Teams.
Class Project Product Design.
Questions for Review.
5. Class Design.
Key Concepts.
The Class Design Process.
More UML.
Objectives of the Class Design Phase.
Verification of the Class Design.
Designing the CLASS PROJECT.
Questions for Review.
6. CASE STUDY: Game2D with Method Design.
Key Concepts.
Overview.
Requirements Specification.
Refined Requirements Specification.
Requirements Analysis.
Product Design.
Class Design.
Method Design.
Questions for Review.
7. Implementation.
Key Concepts.
Introduction.
Implementation Approaches.
Implementation Plan.
CASE STUDY: Implementation Plan for the LMS.
Programming Style.
Comments and Internal Documentation.
Project Coding Standards.
Implementing the CLASS PROJECT.
Questions for Review.
8. Testing.
Key Concepts.
What Is Testing?
Principles of Object-Oriented Testing.
Definitions.
Testing Steps.
Special Issues for Testing Object-Oriented Systems.
CASE STUDY: Testing the LMS.
Testing the CLASS PROJECT.
Testing in the Face of Change: Configuration Management.
Questions for Review.
9. Project Management.
Key Concepts.
Introduction.
Project Manager Responsibilities.
Configuration Management.
Project Planning and Monitoring.
Project Teams.
Risk Management.
Reducing Risk.
Further Readings on Risk Management.
CASE STUDY: Risk Analysis in the LMS.
Questions for Review.
10. Design Patterns.
Key Concepts.
Motivation for Design Patterns.
What Are Design Patterns?
Exploring Design Patterns.
Questions for Review.
11. Software Development Horror Stories.
Key Concepts.
Introduction.
Therac-25.
CONFIRM.
Telephones and Communications.
12. Completing and Presenting the CLASS PROJECT.
Succeeding with the Class Project.
Reflecting on the Project.
Presenting the Project. What Our Readers Are SayingBe the first to add a comment for a chance to win!Product Details
Other books you might likeRelated Subjects
Computers and Internet » Internet » Information
|
|||||||||
|
|
||||||||||
|
Follow us on...
|
||||||||||
