LiveZilla Live Chat Software
Download syllabus copy Download printable copy

MS.NET Live Project Training

Image

Software Project development requires a lot of other aspects apart from coding like understanding the specifications, requirements and preparing the documentation as per the needs. Result depends upon the way we come across all the important milestones like choosing technology, type of architecture and issues during the development of the project.

Most of the people in-spite of knowing MS.NET completely they are not ready to handle the project due to lack of confidence to develop the project independently and are failing to reach industry expectations.


MS.NET Live Project Training Objectives

  • To learn how to implement N-Tier Architecture in a Windows and Web based platforms
  • To learn how collect requirements and documented the same.
  • To build an abstract and complete requirement specification document.
  • To divide project into multiple modules and document the same.
  • To develop UML diagrams for all important modules.
  • To design E-R diagrams and create database scheme using SQL Server.
  • To setup project in VS.NET and design Master Page for the website.
  • To implement security in website for Admin related pages.
  • To write Data, DAO and BO classes using LINQ to SQL.
  • To design and program all ASP.NET Pages using the BO and utility classes.
  • To move the complete ASP.NET application into LIVE environment using FTP.

Prerequisites

Must have knowledge of

1.      C# specially OOPS and ADO.NET

2.      ASP.NET.


MS.NET Live Project Training Options

  • Regular classroom based training: 4 Weeks, 90 minutes of theory session per day.
  • Fast Track(1-1): 15 days.
  • Video based online training, please visit: http://www.bestdotnettraining.com/online-live-project-training
  • Online 1-1 training please send us your request to enquiry@deccansoft.com or call+91 4027841517 / 27815225 / 8008327000

MS.NET Live Project Training Syllabus

  1. Here we will explain you everything you are going to learn in this course.
  2. This module contains an introduction video which explains this document file.
  1. A video of developing a N- tier architecture windows based application will be provided online, which will be giving you a clear picture of how to start with the project and what care should be taken during the implementation.
  2. We will then extend the same application and reuse most of the code to develop Web based N-Tier Application
  3. Complete Sample Code of both the projects will be provided here.
  1. For every project there are some Roles defined with the help of which it is known what a particular user’s responsibilitie are, according to a particular position or status in a group or organization he/she belongs to. Based on the roles the privileges to access a particular page is given to the user.
  2. Input:
    1. Participants will be explained all the types of users (Roles) and their individual task list.
    2. This information also will be given verbally.
  3. Task:
    1. Participant should prepare a document listing modules / tasks in each and every role.
    2. Role Overview Document must be submitted.
  4. Documents:
    1. Roles and their responsibilities Document.
  1. Input:
    1. A brief overview of the requirement will be given to the participant. 
    2. A template of Abstract Document also will be provided.  
  2. Task:
    1. Participant will have to draft an abstract document as per the requirements given verbally.
  3. Documents:
    1. Project Abstract Document
       
  1. Every project will be divided in to one or modules, each module will have its own functionality and importance. Project will be divided in to modules in order to ease the understanding of the project and development. Based on the project requirement and the roles identified the modules will be identified. In module document we are going to specify what the module is about, functionalities of a module and which role is going to use this module.
  2. Input:
    1. Detailed explanation about each and every module will be provided to the participants
  3. Task:
    1. Participant is supposed to provide detailed document explaining the operations to be performed in and every module.
  4. Document:
    1. Module Description Document
  1. For storage and retrieval we need a persistent storage in the form of Database, here we need to specify the following:
    1.  What are the different Entities
    2.  What are the fields and their types and size.
    3.  Defining the relationships between Entities
    4.  Validation rules for each field. Static values or sample data for each field must be provided
    5.  GUI element (Control) for each field of the entity.
  2. Input:
    1. A template of excel file will be provided to the participant
    2. Detailed explanation of any one entity including documenting in Excel file will be provided.
  3. Task:
    1. Participant will have to decide and finalize database entities for every module based on the inputs given.
    2. An excel file with all the details of the entities must be submitted.
  4. Document:
    1. Entity Description Document
  1. It’s very important that we plan proper Name, directory structure for the application.   Creating and setting up the application in visual studio means, creating different folders for different classes like BO, Data, DAO, utility etc. for ease of navigation and maintenance of the project.
  2. Input: 
    1. Demonstration of how to create a web application project 
    2. Create proper directory structure based on roles of different users.
  3. Task:
    1. Participant should do the same
  4. Document:
    1. Basic application setup with directory structure
  1. Data Class
    1. In the Data classes the developer is going to represent each table of database as a separate data class which holds every
    2. column of the table as a property with specific return type as the data type of the column in the table.
  2. Input
    1. Demonstration of writing any one data class
  3. Task:
    1. Participant should write data class for all the tables in the database
  4. Document:
    1. Application with Data Classes  
  5. Helper class  
    1. Helper class is a user defined class where the common functions are defined.  Common functions are the ones which arebeing used in more than one page so instead of writing them in each and every page we are going to put them in one classcalled “Helper”.
  6. Input: 
    1. Skeleton with declarations will be provided to the participant
  7. Task:
    1. Must provide implementation for all the members of this class
  8. Document:
    1. Application with Helper Classes 
  1. Exception handling is very crucial in every application.  
  2. Input: 
    1. Demonstration of how to write any one Custom Exception class
  3. Task:
    1. Participant should write other Exception classes.
  4. Document:
    1. Application with Custom Exception Classes 
  1. Documenting DAO Classes
    1. This will be a semi technical document created by a developer. In this document developer is going to specify the sequence of actions to be performed by the user. This document will help a developer to enter design phase to implementation.
  2. Input:
    1. Template along with demonstration of how to write the document for any one module will be provided
  3. Task:
    1. Participant will write the documentation for each and every module based on the guide lines provided.
  4. Document:
    1. Step by Step DAO Process document   
  5. Programming DAO classes.
    1. All the classes of DAO will be in the Data Access Layer (DAL).  This layer provides a simplified access to the persistent storage or Database.
    2. DAL will hide the complexity of underlying data source to the external world.
    3. For instance, instead of using the commands such as insert, delete, update to access a specific table in the database, we can write a class and few stored procedures in the database and we can call the stored procedure from a method inside the class which would return the object of specific type containing the requested values. Also we can fetch data from several tables of the application with a single call.  We can also make the DAL to support multiple database types.  

 

  1. Input: 
    1. Demonstration of how to write any one DAO class
  2. Task:
    1. Participant should write other DAO classes.
  3. Document:
    1. Application with DAO Classes 
  1. Documenting BO classes

This will be a semi technical document created by a developer. In this document developer is going to specify the sequence of actions to be performed by the user. This document will help a developer to enter design phase to implementation.

  1. Input:
    1. Template along with demonstration of how to write the document for any one module will be provided
  2. Task:
    1. Participant will write the documentation for each and every module based on the guide lines provided.

Document: Step by Step BO Process document   
Programming BO Class
Based on Detailed Process document for each module here we are going to program the BO classes.

  1. Input: 
    1. Demonstration of how to write any one BO class
  2. Task:
    1. Participant should write other BO classes.
  3. Document:
    1. Application with BO Classes 
  1. To get an idea about how the screens are going to look we are going to visit few websites and based on the above inputs and details we are going to develop the screens on paper and if everything looks fine  then we are going to start designing the screens. After preparing the screens we have to integrate the application with the respective BO’s.
  2. Input: 
    1. Demonstration of how to Design and code any one GUI form
  3. Task:
    1. Participant should do the same for other forms
  4. Document:
    1. Application with all GUI
  1. Input: 
    1. Demonstration of how to create a Setup an application on the web server of bestdotnettraining.com 
    2. How to use FTP client to upload and configure the application on server.
  2. Document:
    1. Completed Application.
No faculty for current course
Email Id
Contact No
Course
Subject
Details
Scroll to Top