We assume that before you begin using this kit, you are familiar with creating enterprise applications by using Microsoft Visual Studio 2005 and ASP.NET 2.0. You should also have a working knowledge of Microsoft Visual Basic or C#. You should have worked on a team throughout the software development life cycle, and you should be familiar with technical envisioning and planning, design and development, and stabilizing and releasing software.
By using this training kit, you’ll learn how to do the following:
- Envision and design an application
- Design and develop a component
- Design and develop an application framework
- Test and stabilize an application
- Deploy and support an application
- Envision and design an application
- Design and develop a component
- Design and develop an application framework
- Test and stabilize an application
- Deploy and support an application
Application development projects often have limited budgets and constrained timelines, set by the stakeholders and upper management. These same people typically provide the business vision and funding for the project. They make decisions about which projects to execute based on both the business value of the resulting project and a professional developer’s estimate of the effort associated with the project. It is their confidence you need to gain before you will be trusted with the budget to execute the project. This means demonstrating that you understand the business problems you will be trying to solve and that you will be successful in translating their vision into tangible software before budgets and timelines are exhausted. To professional developers, this means reviewing requirements and recommending, evaluating, and refining a design for the application.
This chapter looks at how you move from the vision, goals, and requirements of an application to a proposed solution. This process involves recommending technologies, defining a design, and then vetting your recommendations through the creation of a prototype. You then need to demonstrate the feasibility of the project (and your design) to the visionaries and stakeholders. Ultimately, it will be their confidence in your proposed solution that determines whether a project is funded and moves from idea to implementation.
This chapter looks at how you move from the vision, goals, and requirements of an application to a proposed solution. This process involves recommending technologies, defining a design, and then vetting your recommendations through the creation of a prototype. You then need to demonstrate the feasibility of the project (and your design) to the visionaries and stakeholders. Ultimately, it will be their confidence in your proposed solution that determines whether a project is funded and moves from idea to implementation.
Not every problem should be solved with code or technology. As technologists, our first instinct to any problem might be to write some code. However, this is often not the best choice. Some problems are too costly in terms of dollars, resources, or time to implement. You need to take a step back and look at a problem not just as a developer but from the perspective of what is best for your organization. You will find that looking at problems with this attitude might change the way you would approach a specific solution. The results of this thinking are beneficial to the organization. However, it also shows your management that you see a bigger picture beyond just the technology and can be relied on to add business value..
.
.
Cilck Here To Download 8898 KB