Conclusion

Throughout the course of this book we use the Unified Process lifecycle model. This decision is based on the following reasoning.

Because the requirements for the project are more or less static, the Unified Process is a good choice. UP also enables us to explore the technological uncertainty at the beginning of the project by building a throw-away prototype. In addition, the traditional, well-structured approach with go/no-go decision points lets us track our progress and identify problems at the end of each iteration.

Within the iterations, we use the following icons to identify the core workflows:

graphics/requirements_icon.gif

Requirements

graphics/analysis_icon.gif

Analysis

graphics/design_icon.gif

Design

graphics/implementation_icon.gif

Implementation

graphics/test_icon.gif

Test

The following icons are used to differentiate programming and software engineering sections throughout the rest of the book:

graphics/programming_icon.gif

Programming Section

graphics/softeng_icon.gif

Software Engineering Section

Introducing .NET

Introducing Software Engineering

A .NET Prototype

Project Planning

The Photo Editor Application

GDI+ Graphics Extensions

Advanced GDI+ Operations

Dynamic Loading of Components

Accessing System Resources

Performance Optimization, Multithreading, and Profiling

Building the Web Application with ASP.NET

Security and Database Access

Product Release

show all menu





. NET-A Complete Development Cycle
.NET-A Complete Development Cycle
ISBN: 0321168828
EAN: 2147483647
Year: 2005
Pages: 123
Similar book on Amazon

Flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net