Skip to main content
Disciplines
Automotive Business IT + Informatics Construction + Real Estate Electrical Engineering + Electronics Energy + Sustainability Insurance + Risk Finance + Banking Management + Leadership Marketing + Sales Mechanical Engineering + Materials
Events
DE
EN
Books
Journals
Topic Page
Marketing
Start single access now
Access for companies
EXTENDED SEARCH
Log in
Top

2004 | Book

Getting Started: A Modeling Primer Read chapter Read first chapter

Enterprise Development with Visual Studio .NET, UML, and MSF

Authors: John Erik Hansen, Carsten Thomsen

Publisher: Apress

Included in: Professional Book Archive

Login to get access
insite
SEARCH

About this book

Using Visual Studio .NET (VS .NET) for creating enterprise solutions, authors John Hansen and Carsten Thomsen have chosen to add the Unified Modeling Language (UML), for designing and documenting solutions, and the Microsoft Solutions Framework (MSF), for planning and managing projects.

Experienced developers, team leaders, and project managers who need a structured way of creating enterprise solutions will benefit from reading this book. Parts of this book can be used by developers (experienced or not) and managers who want to know about MSF and UML in connection with .NET development.

This guide provides an enterprise development overview, an in-depth introduction to UML, and coverage of various enterprise tools included with the VS .NET Enterprise Developer (VSED) and VS .NET Enterprise Architect (VSEA) editions, such as enterprise template projects, Visual SourceSafe (VSS), Visio for Enterprise Architects 2003 (VEA), Microsoft Application Center Test (ACT), and Visual Studio Analyzer.

Not only will you learn how to deploy your project, but also two hands-on chapters will show you how to analyze your project and model it using VEA, and guide you step-by-step through the process.

For most readers, this is a cover-to-cover book, but it can certainly be used as a reference guide whenever you need information about a particular tool or process. Throughout this book, youll find exercises that demonstrate the topic being discussed, making this book a must-have for programmers dealing with, or those with an interest in, developing enterprise .NET solutions.

Table of Contents

Frontmatter

The Basics

Frontmatter
Chapter 1. Getting Started: A Modeling Primer
Abstract
This chapter will introduce you to enterprise modeling, enterprise development, and enterprise applications. Because we believe in learning by doing, we’ll also use this chapter to let you get your feet wet. We’ll walk you through two short but useful example models: one that you’ll be able to use to create the skeleton for Visual Basic .NET (VB .NET) and/or C# classes and another that you can use to model the database.
John Erik Hansen, Carsten Thomsen
Chapter 2. Planning and Documenting Your Solution
Abstract
In this chapter, we introduce you to the concepts of solution design and planning. The majority of the chapter covers design. We explain what design really is, as seen from a rather wide perspective, and the implications of design to a software solution. We also introduce the Microsoft Solutions Framework (MSF) 3.0 design process and explain how Microsoft advises you to design your solutions. You’ll see why solution design is so important and what it means if you choose to skip solution design. You’ll also learn how design affects the cost and quality of your final software solution. You might even restrict yourself from selling your solution to certain customers if your design doesn’t fulfill some specific design requirements. For example US federal agencies must purchase software that is designed according to the “508”1 design standard, making it accessible to employees and the members of the public who are disabled. If you fail to meet these demands, you may lose the contract.
John Erik Hansen, Carsten Thomsen

UML

Frontmatter
Chapter 3. Getting to Know the Unified Modeling Language
Abstract
In this chapter, we introduce you to the concepts of the Unified Modeling Language (UML). Our intention with this chapter is to give you a clear understanding of what UML really is, its historical background, and how it’s used. UML is a modeling language, meaning that it’s a language or concept for how to model and describe real-world objects and how they interact. The difference between UML and a normal programming language is that UML is a graphical language that uses graphics to describe objects. UML is also used to describe design patterns,1 which you can apply to your .NET environment.
John Erik Hansen, Carsten Thomsen
Chapter 4. Examining the UML Models: Behavioral Models
Abstract
In this chapter and the next, we’ll introduce you to the various UML models that you can create in VEA 2003. We’ll show you how to create the UML models in VEA and provide you with a description of each model, along with tips for when to use it.
John Erik Hansen, Carsten Thomsen
Chapter 5. Examining the UML Models: Static Models
Abstract
In this chapter, we’ll introduce you to the UML diagrams known as structural diagrams, which describe the structure (static structure) of your solution. The following UML diagrams are structural diagrams:
  • Class diagram
  • Statechart diagram
  • Component diagram
  • Deployment diagram
John Erik Hansen, Carsten Thomsen
Chapter 6. Planning a VB .NET or C# Project
Abstract
This chapter shows you how to plan a Visual Basic .NET or C# project. The information found in this chapter primarily consists of what you should do and in what order you should do it. You’ll find references to many of the other chapters in this book, which also means that this chapter is an overview chapter that binds the information in other chapters together. So, read this chapter as a TO-DO list, but remember that while this is how we most often start out planning our projects, we’re not methodology bigots. We don’t claim that this is an exhaustive list, nor do we mean to imply that you absolutely must follow all the instructions given for every project. You should go through this chapter with an open mind, taking notes, and then create your own project planning TO-DO list.
John Erik Hansen, Carsten Thomsen
Chapter 7. Maintaining the UML Documentation
Abstract
As you develop your solution, your UML model will be subject to refinements and changes. Then, after deploying the solution, you’ll want to maintain the UML model in order to reflect error corrections and the customer change requests you’ve chosen to apply. Maintaining your UML documentation to keep it up-to-date is not an easy task.
John Erik Hansen, Carsten Thomsen

VS. NET Enterprise Features

Frontmatter
Chapter 8. Using Enterprise Template Projects
Abstract
In this chapter, you’ll be introduced to enterprise template projects, which are solution templates for simplifying the task of creating distributed VS .NET appli­cations typically consisting of several projects. You can use enterprise template projects with both enterprise editions of VS .NET—VSED and VSEA—but you can create and edit enterprise template projects only with VSEA.
John Erik Hansen, Carsten Thomsen
Chapter 9. Using Policy Files
Abstract
In this chapter, you’ll be introduced to policy files. Policy files are used in conjunction with enterprise template projects, as described in Chapter 8. Enterprise template projects are application prototypes for various project types. Policy files allow you to constrain and guide the developers working on your enterprise solution. You can use policy files with both enterprise editions of VS.NET: VSED and VSEA. However, you can create and edit policy files only with VSEA.
John Erik Hansen, Carsten Thomsen
Chapter 10. Using Custom Help Topics
Abstract
In this chapter, you’ll be introduced to custom help topics and how they’re used in policy files associated with enterprise template projects. Policy files are covered in Chapter 9, and enterprise template projects are covered in Chapter 8.
John Erik Hansen, Carsten Thomsen
Chapter 11. Visual SourceSafe
Abstract
VS.NET can be used with any source control application that is Microsoft Source Code Control Interface (MSSCCI)-compliant. In this chapter, you’ll learn about using the source code locking and versioning facilities provided by Microsoft’s Visual SourceSafe (VSS) 6.0d, which is the source control application that comes with VSED and VSEA. VSS 6.0d integrates into the VS.NET IDE.
John Erik Hansen, Carsten Thomsen
Chapter 12. Visio for Enterprise Architects 2003
Abstract
This chapter describes the core functionality of Visio for Enterprise Architects 2003 (VEA 2003). In this chapter, we’ll focus on the VEN’s code generation, error checking, and reporting functions. You’ve learned about some of this functionality in previous chapters. You can consider this chapter as a summary or a brush-up on the core VEA functionality.
John Erik Hansen, Carsten Thomsen
Chapter 13. Application Center Test
Abstract
In this chapter, you’ll learn how you can use Microsoft Application Center Test (ACT) to analyze your Web applications’ performance and stress-test your Web servers. We’ll present an overview of ACT, and then move on to cover manipulating users and groups, creating projects and tests, running tests, and examining test results.
John Erik Hansen, Carsten Thomsen
Chapter 14. Visual Studio Analyzer
Abstract
Visual studio analyzer is a tool for collecting analysis information about distributed applications. Visual Studio Analyzer comes with both of the Enterprise editions of VS.NET 2003: VSEA and VSED. It is a high-level tool that works at the component level, effectively helping you isolate the components of your application that potentially need optimizing. Most profiling tools, such as code profilers, generally work at the method level, profiling the code in your methods. You’ll use those kinds of profiling tools once you’ve identified the components of your distributed application that need to be optimized by using Visual Studio Analyzer.
John Erik Hansen, Carsten Thomsen
Chapter 15. Deploying Your Applications
Abstract
In this chapter, you’ll learn how to use VS.NET for deploying your applications. Deployment is the process where you copy your solution to or install your solution on other machines. Generally, deployment is one of those often-overlooked areas of the software development process. In many organizations, it’s out there with testing—a task that will be performed after you finish the development, time permitting.1 But you now know that deployment (and testing) should be part of the overall project, and you should start planning it when you plan the development. We’re not saying that you should start building deployment projects as soon as you start developing, but you should have an idea of what to deploy and to where.
John Erik Hansen, Carsten Thomsen

Hands-On Projects

Frontmatter
Chapter 16. Hands On: An Internal Project
Abstract
This chapter will guide you through the processes of enterprise modeling, using the knowledge you’ve gained so far. In addition, we’ll discuss some practical issues, such as which diagrams are best to create and to what degree they should be refined.
John Erik Hansen, Carsten Thomsen
Chapter 17. Hands On: An External Project
Abstract
The hands-on example in this chapter will be built from scratch, without using existing components from the customer’s enterprise. This is contrast to the example in Chapter 16, which did integrate existing components from the customer’s enterprise.
John Erik Hansen, Carsten Thomsen

Modeling Tools

Frontmatter
Chapter 18. IBM Rational XDE
Abstract
In this chapter we’ll introduce you to IBM Rational XDE (XDE). The version we cover is IBM Rational XDE Developer 2003 for.NET, because this edition is aimed toward.NET developers and contains code generation for.NET.
John Erik Hansen, Carsten Thomsen
Chapter 19. Comparing Microsoft and IBM Rational UML Tools and Development Frameworks
Abstract
Should you choose to use Microsoft VEA or IBM Rational XDE? That seems to be the big question for many developers, analysts, architects, and project managers, and the online newsgroups are filled with pros and cons for each product. It’s difficult—if not impossible—to give an objective, bulletproof answer to this question, because as with most IT decisions, it depends. It depends on your usage, knowledge, budget, development language, operating procedures, and so on. It seems as though the choice is also affected by personal preference and emotions.
John Erik Hansen, Carsten Thomsen

MSF

Frontmatter
Chapter 20. Microsoft Solutions Framework 3.0
Abstract
It’s possible to challenge and beat the well-known software paradox that states today’s software projects demand faster development with fewer resources and increased functionality requirements. To deal with this demand in a fast changing world, Microsoft has developed a framework for project and solution management called the Microsoft Solutions Framework (MSF), and you can find more information about it from Microsoft here:
  • http://wwwmicrosoft.com/technet/itsolutions/techguide/msf/ default.mspx
John Erik Hansen, Carsten Thomsen
Backmatter
Metadata
Title
Enterprise Development with Visual Studio .NET, UML, and MSF
Authors
John Erik Hansen
Carsten Thomsen
Copyright Year
2004
Publisher
Apress
Electronic ISBN
978-1-4302-0696-5
Print ISBN
978-1-59059-042-3
DOI
https://doi.org/10.1007/978-1-4302-0696-5