'NET The Tip of the Iceberg

1
(No Transcript)
2
.NET The Tip of the Iceberg
3
Getting Started

• Getting Started with a Low Risk,
• High Value .NET Solution
• Marty Elvidge
• eBusiness Technology Manager
• OnSphere Corporation

4
Overview

• Advantages of .NET Technology for Application
  Development
• Getting Started

5
Advantages of .NET Technology

• Improved Time to Market - Excellent Dev Tools
• Many types of resources that make up a project
  are organized and edited in one place (VB.NET,
  C, HTML, ASP.NET, XML, Database Connections).
• Excellent debugging. Set break points in all
  languages including ASP.NET pages. Break points
  can even be set in SQL Server 2000 store
  procedures.
• Provides framework for Plug-Ins allowing third
  parties to develop Editors for their file types
  to be manipulated in the IDE (e.g., Crystal
  Decisions and Active Reports.NET).
• Software Development Magazine Jolt Awards
  Productivity Award.
• Web services Journal Editors Choice Award for Web
  Services IDE.

6
Advantages of .NET Technology

• Code Reuse Object-Oriented
• Takes a bit more up front planning.
• New Objects can be derived from existing and
  then add new functionality.
• We already have a library of OnSphere objects
  that we use as a starting point for projects.
• Complete-ness of .NET Framework
• Collections, Database Access, GDI, I/O,
  Directory Services, Email, XML Its all there.
• Availability of third-party tools
• Infragistics (Sheridan-Protoview) UI
  enhancements.
• Data Dynamics Active Reports.NET.
• Rational Development Tools.

7
Time-to-Market
8
Reliability and Security

• Exception model in .NET provides the framework to
  build robust applications
• You still have to provide action for handling the
  exception.
• More defined error handling framework than On
  Error handles or checking return codes.
• Focus on security when designing .NET
• Tighter security in IIS for ASP.NET.
• Code signing to help against viruses (Strong
  Naming).
• CLR execution domains (Sandboxes) to restrict
  access of bodies of executing code.

9
Getting Started

• Walk through the project solution process
  (Analysis, Planning, Implementation,
  Deployment) with emphasis on the impact of .NET.
• Relate multiple, first-hand experiences with
  projects we have successfully implemented.

10
Steps - Analysis

• Current Environment/Infrastructure
• What kind of systems are involved, servers,
  desktops, email/messaging, etc.
• Network environment/Internet Connections
• Security/User Account Management

11
Current Environment

• .NET Requirements
• For Deployment Windows 98, Me, NT 4.0
  (SP6),2000, XP with IE 5.01 or above and MDAC 2.6
  or higher
• Deployment PC
• Microsoft suggests 90MHz with 32MB RAM
• Real World ?
• For Development Windows NT4.0(SP6), 2000, XP
• Development PC
• Microsoft suggests 450MHz with between 96 to
  196MB RAM
• Real World 850MHz with at least 512MB RAM

12
Steps Analysis

• Current Resource Skill Set
• What skills do you have?
• What skills do you want to have?
• .NET Development Factors
• Paradigm change Object Oriented
• Learning .NET Framework
• Decision VB.NET or C
• OnSphere senior developers took approx. three
  weeks to ramp up

13
Steps Analysis (cont.)

• Big Picture View of Business Processes and
  Requirements
• Look for areas to begin implementing .NET
• Web Application
• Use with existing applications to access partner
  or third party Web Services
• Provide Web Services to your partners
• Use for Business Logic

14
Steps - Plan

• Plan
• Clearly define the scope.
• Prepare Business Requirements Document for the
  application (high-level definition of how the
  application is to perform, its interfaces, user
  population, etc.)
• Determine tasks for Environment/Infrastructure
  changes that may be required

15
Steps - Implement

• Detailed Design of the application
• Functional Specification
• What do the screens look like?
• How/When is this process going to run?
• How does the user navigate the application?
• Logical/Physical Data Design
• What needs to be stored?
• How will it be stored and retrieved?
• Object Design Important for .NET
• Defines the High Level classes and their methods
  for handling the applications data and business
  rules.
• How am I going to get the data to the screen?
• Where is Business Rule X enforced?

16
Steps Implement (cont.)

• Decide on naming conventions, coding conventions
• Microsoft provides guidelines for .NET but these
  may need to be more narrowly defined for a
  project or your organization to maintain
  consistency.
• Visual Studio.NET provides a way for new code
  templates to be defined so that some of the
  conventions can be automated.
• Format of comment blocks.
• Format of comments when checking resources in and
  out of Visual Source Safe.

17
Steps Implement (cont.)

• Project Structure/Organization
• Namespaces - .NET provides Namespaces as a way
  to logically organize modules of code. If its a
  sizeable project, more than one Namespace may be
  defined.
• Assemblies These are DLLs in .NET.
  They are another organization of code.
  Some consideration should be given to these when
  designed.
• Build the Application
• Quality Assurance

18
Steps - Deploy

• Deploy
• Install application in test environment
  equivalent to production environment.
• Perform acceptance testing.
• Train users, administrators, etc.
• Go into production.

19
Steps - Evaluate

• Conduct a Lessons Learned
• Did we stay in scope?
• Was there too much/not enough detail in the
  Specifications?
• Did the naming conventions and code organization
  work out?
• Are the end users happy? If not why not?