Chapter 2: Visualizing the Solution


Overview

Some software architects believe that software is constructed, not developed. The difference may not seem obvious at first, but by definition the word “construction” implies a completely different approach than the word “development.” The verb “develop” is defined as the process by which something grows or improves gradually over time. For instance, you can develop your muscles through weightlifting or develop impressive piano skills through regular practice. Building software is similar to building an office tower; you start with a vision, draw up a detailed plan, and strictly follow that plan until the project is complete.

I expect it will take quite some time to convince people to stop using the term “software development.” As much as I believe good software requires a lot more planning than the word “development” implies, too many people, including Microsoft, use that term to refer to this process. So who am I to try to change their minds?

In this chapter, we will start with an introductory look at the Microsoft Solutions Framework. The bulk of this chapter examines the first phase of that model, known as the envisioning phase. In order to understand the systems and business operating environment we will be deploying our application in, we must have some understanding of our organization’s enterprise architecture—we will discuss what that is (and why it’s important) later in the chapter. The final sections of the chapter deal with the process of the envisioning phase: creating a solution concept, assessing feasibility, defining scope, and identifying key project risks.




MCSD Analyzing Requirements and Defining. NET Solutions Architectures Study Guide (Exam 70-300)
MCSD Analyzing Requirements and Defining .NET Solutions Architectures Study Guide (Exam 70-300 (Certification Press)
ISBN: 0072125861
EAN: 2147483647
Year: 2003
Pages: 94

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