Software development with UML
โ Scribed by Lunn, Ken
- Publisher
- Palgrave Macmillan
- Year
- 2003
- Tongue
- English
- Leaves
- 430
- Category
- Library
No coin nor oath required. For personal study only.
โฆ Synopsis
SECTION ONE: INTRODUCTION AND CASE STUDIES -- Modelling and Notation The Unified Modelling Language -- Case Studies ICANDO Oil -- SECTION TWO: THE INTITIATION, ORGANISATION AND MANAGEMENT OF IT PROJECTS -- Project Conception and Initiation -- Software Development Lifecycle -- Managing the Process -- Business Modelling -- The Cost/Benefit Model -- SECTION THREE: ANALYSIS -- Business Modelling -- Requirements Analysis -- Buy, Build or Adapt -- Object Concepts -- Systems Analysis -- SECTION FOUR: ARCHITECTURE AND DESIGN -- Design -- Database Design -- Architecture -- SECTION FIVE: CONSTRUCTION, TESTING AND DEPLOYMENT -- Construction -- Testing -- Deployment, Support and Enhancement -- SECTION SIX: CONCLUSION -- Journey's End -- Answers to Review Questions -- UML Notation Summary -- Worked Example The Odd Shoe Company -- Glossary -- References -- Index.;This is an introductory book to information modelling with UML, for entry level university students. It assumes no previous knowledge of UML on the part of the reader, and uses a case-based approach to present the material clearly and accessibly. It harmonises the UML notation with a full software development approach, from project conception through to testing, deployment and enhancement. Ken Lunn is an experienced tutor, who also practices as a UML professional, and the cases are based upon his own experience.
โฆ Table of Contents
SECTION ONE: INTRODUCTION AND CASE STUDIES --
Modelling and Notation The Unified Modelling Language --
Case Studies ICANDO Oil --
SECTION TWO: THE INTITIATION, ORGANISATION AND MANAGEMENT OF IT PROJECTS --
Project Conception and Initiation --
Software Development Lifecycle --
Managing the Process --
Business Modelling --
The Cost/Benefit Model --
SECTION THREE: ANALYSIS --
Business Modelling --
Requirements Analysis --
Buy, Build or Adapt --
Object Concepts --
Systems Analysis --
SECTION FOUR: ARCHITECTURE AND DESIGN --
Design --
Database Design --
Architecture --
SECTION FIVE: CONSTRUCTION, TESTING AND DEPLOYMENT --
Construction --
Testing --
Deployment, Support and Enhancement --
SECTION SIX: CONCLUSION --
Journey's End --
Answers to Review Questions --
UML Notation Summary --
Worked Example The Odd Shoe Company --
Glossary --
References --
Index.
โฆ Subjects
Computer software--Development;COMPUTERS--Programming Languages--UML;COMPUTERS--Software Development & Engineering--General;UML (Computer science);Electronic books;Computer software -- Development;COMPUTERS -- Programming Languages -- UML;COMPUTERS -- Software Development & Engineering -- General
๐ SIMILAR VOLUMES
<P>This book presents the analysis, design, documentation, and quality of software solutions based on the OMG UML v2.5. Notably it covers 14 different modelling constructs including use case diagrams, activity diagrams, business-level class diagrams, corresponding interaction diagrams and state mach
<p>This book presents the analysis, design, documentation, and quality of software solutions based on the OMG UML v2.5. Notably it covers 14 different modelling constructs including use case diagrams, activity diagrams, business-level class diagrams, corresponding interaction diagrams and state mach
Software Evolution with UML and XML provides a forum where expert insights are presented on the subject of linking three current phenomena: software evolution, UML and XML. Software evolution and reengineering are a real problem in the software industry;
<p><P>Component-based software development regards software construction in terms of conventional engineering disciplines where the assembly of systems from readily-available prefabricated parts is the norm. Because both component-based systems themselves and the stakeholders in component-based deve
The main subject of the book is the description of built-in contract testing a test organization for component-based applications founded on building test artifacts directly into components. It makes individual components more controllable and observable, and thus more testable through built-in test