SlideShare a Scribd company logo
1 of 7
Project Id: 32
Implementation Planning
Chapter 6
IMPLEMENTATION PLANNING
________________________________________________
CCET (IT)
101
Project Id: 32
Implementation Planning
6.1 IMPLEMENTATION ENVIRONMENT
The implementation view of software requirement presents the real world
manifestation of processing functions and information structures. This computerized
system is specified in a manner that dictates accommodation of certain implementation
details.
The implementation environment of the developed system facilitates multiple users
to use this system simultaneously. The user interfaces are designed keeping in mind that
the users of this system are familiar to using GUI-based systems. Thus, we restricted
ourselves to developing a GUI-based system so that it becomes easier for the end user to
get acquainted to the developed system.
We have also followed the web based 4-tier architecture as the implementation
architecture which is as follows:
The presentation tier or user services layer:
• This layer gives a user access to the application. It contains all the web pages so it
is this interface through which user can access the application.
• This layer presents data to the user and optionally permits data manipulation and
data entry.
The control tier or control layer:
• This layer gives a well separation between code and its connectivity with database.
• This layer includes the code (VB.NET code) and JS. Mainly this layer includes the
replica of presentation layer pages and these pages are mainly control pages.
The business services layer:
• It consists of business and data rules. Also referred to as the business logic tier, the
middle tier is where we as developers can solve mission-critical business problems
and achieve major productivity advantages. The components that make up this
layer can exist on a server machine, to assist in resource sharing. These
CCET (IT)
102
Project Id: 32
Implementation Planning
components can be used to enforce business rules, such as business algorithms and
data rules, which are designed to keep the data structures consistent within either
specific or multiple databases. Because these middle-tier components are not tied
to a specific client, they can be used by all applications and can be moved to
different locations, as response time and other rules require.
• In our project we had created various classes appropriate to database and we
implemented business logic here. According to request from presentation layer the
appropriate rules called and it can access data through data tier.
The data tier or data services layer:
• This layer interacts with persistent data usually stored in a database or in
permanent storage.
• In this layer we have implemented the basic function through data can be
accessed like insert, update, delete, selection.
• Our Requirements are changing dynamically so we used four-tier architecture. The
four-tier approach provides benefits such as reusability, flexibility, manageability,
maintainability, and scalability.
Fig 6.1 Four tier architecture
CCET (IT)
103
Project Id: 32
Implementation Planning
6.2 CODING STANDARTS
• Objects
The below are the naming convention for the design element used in the form.
Table 6.1 Naming Convention Table
Field type Prefix Example
Check Box Chk chkReadOnly
Combo Box
Drop-Down List Box
Cmb cmbEnglish
Command Button cmd cmdExit
Common Dialog dlg dlgFileOpen
Data Grid dgr dgrOrderDetails
Date Time Picker dtp dtpDateOfBirth
Form frm frmEntry
Group Box grp grpPymntDtls
Horizontal Scroll Bar hsb hsbVolume
HTML/Frame fra fraLanguage
Image img imgIcon
Image List ils ilsAllIcons
Label lbl lblHelpMessage
Line lin linVertical
Link Label lnb lnbGotoWebSite
List Box lst lstPolicyCodes
List View lvw lvwFolderDtls
Main Menu mnu mnuFileOpen
Panel pnl pnlOrder
Picture Box pic pbxImage
Progress Bar prg pbrInstallProgress
Radio Button rad radSelect
Report rpt rptQtr1Earnings
Rich Text Box rtx rtxAddressDtls
Shape shp shpCircle
Status Bar sts staDateTime
Tab page tpg tpgPayerDtls
Text Box txt txtLastName
Timer tmr tmrAlarm
Tool Bar tlb tlbActions
Tool Tip tip tipTxtName
Vertical Scroll Bar vsb VsbRate
Regular Expression Validator rev revUserName
CCET (IT)
104
Project Id: 32
Implementation Planning
Required Field Validator rfv rfvUserName
Compare Validator cmv cmvStartDate
Validation Summary vas vasValidationSummary
Check Box List cbl cblDefectPattern
All Hidden Fields should be place one after the other to reserve the space in the form.
Description & purpose of each hidden field should be documented in the design spec of
the appropriate components.
• Variables
<prefix>_<meaningful name>
prefix : 2 character code.
First alphabet represents the scope of the variable
l - Local
g - Global
Second alphabet represents the type
b - Boolean
c - Currency
s - String
f - Float
i - Integer
l - Long
t - Time
a - Array
v - Variant
The body of the variable names and function names should use mixed case and
should be as long as needed to describe their purpose. To keep the name length reasonable,
abbreviations can be used for standard terms like Init for initialization, Tbl for table, Cnt
for count, Grp for Group etc. Wherever abbreviations are used, try to use them
consistently to improve readability. And in meaningful variable name variable name start
with lower case salphabet and second part of the name should be start with upper case
alphabet like for student name variable name should be studentName.
CCET (IT)
105
Project Id: 32
Implementation Planning
Recommended Maximum Length for variable names is 32 characters.
Example:
For declaring a global string variable for Group name: gs_grpName.
When passing values to a subroutine/function, use the same variable names in the
called routine as in the calling routine.
For Functions and Subroutines
<prefix>_<meaningful name>
For Functions: prefix is fn
CCET (IT)
106
Project Id: 32
Implementation Planning
Recommended Maximum Length for variable names is 32 characters.
Example:
For declaring a global string variable for Group name: gs_grpName.
When passing values to a subroutine/function, use the same variable names in the
called routine as in the calling routine.
For Functions and Subroutines
<prefix>_<meaningful name>
For Functions: prefix is fn
CCET (IT)
106

More Related Content

Viewers also liked (8)

Pre eclampsia
Pre eclampsiaPre eclampsia
Pre eclampsia
 
Tafseer zafar3of5
Tafseer zafar3of5Tafseer zafar3of5
Tafseer zafar3of5
 
Tutoria hugo seccion 2 (1)
Tutoria hugo seccion 2 (1)Tutoria hugo seccion 2 (1)
Tutoria hugo seccion 2 (1)
 
Tafseer anwarenajaf8of15
Tafseer anwarenajaf8of15Tafseer anwarenajaf8of15
Tafseer anwarenajaf8of15
 
Decypher translating and interpretation service
Decypher translating and interpretation serviceDecypher translating and interpretation service
Decypher translating and interpretation service
 
PPT for grant roadmap
PPT for grant roadmapPPT for grant roadmap
PPT for grant roadmap
 
Simbolos diagrama de flujo
Simbolos diagrama de flujoSimbolos diagrama de flujo
Simbolos diagrama de flujo
 
FLUJOGRAMAS
FLUJOGRAMASFLUJOGRAMAS
FLUJOGRAMAS
 

Similar to Chapter 6

object oriented programming part inheritance.pptx
object oriented programming part inheritance.pptxobject oriented programming part inheritance.pptx
object oriented programming part inheritance.pptx
urvashipundir04
 
Cse viii-advanced-computer-architectures-06cs81-solution
Cse viii-advanced-computer-architectures-06cs81-solutionCse viii-advanced-computer-architectures-06cs81-solution
Cse viii-advanced-computer-architectures-06cs81-solution
Shobha Kumar
 
Matlab Based High Level Synthesis Engine for Area And Power Efficient Arithme...
Matlab Based High Level Synthesis Engine for Area And Power Efficient Arithme...Matlab Based High Level Synthesis Engine for Area And Power Efficient Arithme...
Matlab Based High Level Synthesis Engine for Area And Power Efficient Arithme...
ijceronline
 

Similar to Chapter 6 (20)

Unit 1
Unit  1Unit  1
Unit 1
 
Fundamentals of Data Structures Unit 1.pptx
Fundamentals of Data Structures Unit 1.pptxFundamentals of Data Structures Unit 1.pptx
Fundamentals of Data Structures Unit 1.pptx
 
Recipes 8 of Data Warehouse and Business Intelligence - Naming convention tec...
Recipes 8 of Data Warehouse and Business Intelligence - Naming convention tec...Recipes 8 of Data Warehouse and Business Intelligence - Naming convention tec...
Recipes 8 of Data Warehouse and Business Intelligence - Naming convention tec...
 
object oriented programming part inheritance.pptx
object oriented programming part inheritance.pptxobject oriented programming part inheritance.pptx
object oriented programming part inheritance.pptx
 
Patterns for distributed systems
Patterns for distributed systemsPatterns for distributed systems
Patterns for distributed systems
 
Cs 568 Spring 10 Lecture 5 Estimation
Cs 568 Spring 10  Lecture 5 EstimationCs 568 Spring 10  Lecture 5 Estimation
Cs 568 Spring 10 Lecture 5 Estimation
 
chapter 5 Objectdesign.ppt
chapter 5 Objectdesign.pptchapter 5 Objectdesign.ppt
chapter 5 Objectdesign.ppt
 
Technical Interview
Technical InterviewTechnical Interview
Technical Interview
 
C programming session7
C programming  session7C programming  session7
C programming session7
 
C programming session7
C programming  session7C programming  session7
C programming session7
 
Cse viii-advanced-computer-architectures-06cs81-solution
Cse viii-advanced-computer-architectures-06cs81-solutionCse viii-advanced-computer-architectures-06cs81-solution
Cse viii-advanced-computer-architectures-06cs81-solution
 
WSO2 Complex Event Processor - Product Overview
WSO2 Complex Event Processor - Product OverviewWSO2 Complex Event Processor - Product Overview
WSO2 Complex Event Processor - Product Overview
 
Unit-III(Design).pptx
Unit-III(Design).pptxUnit-III(Design).pptx
Unit-III(Design).pptx
 
06 chapter03 04_control_logix_tags_memory_structure_fa16
06 chapter03 04_control_logix_tags_memory_structure_fa1606 chapter03 04_control_logix_tags_memory_structure_fa16
06 chapter03 04_control_logix_tags_memory_structure_fa16
 
Software development effort reduction with Co-op
Software development effort reduction with Co-opSoftware development effort reduction with Co-op
Software development effort reduction with Co-op
 
Software engineering
Software engineeringSoftware engineering
Software engineering
 
05 Lecture - PARALLEL Programming in C ++.pdf
05 Lecture - PARALLEL Programming in C ++.pdf05 Lecture - PARALLEL Programming in C ++.pdf
05 Lecture - PARALLEL Programming in C ++.pdf
 
Matlab Based High Level Synthesis Engine for Area And Power Efficient Arithme...
Matlab Based High Level Synthesis Engine for Area And Power Efficient Arithme...Matlab Based High Level Synthesis Engine for Area And Power Efficient Arithme...
Matlab Based High Level Synthesis Engine for Area And Power Efficient Arithme...
 
Salesforce
SalesforceSalesforce
Salesforce
 
Oo Design And Patterns
Oo Design And PatternsOo Design And Patterns
Oo Design And Patterns
 

More from Amit Gandhi (20)

Job portal
Job portalJob portal
Job portal
 
Dimond recognition system
Dimond recognition systemDimond recognition system
Dimond recognition system
 
Project Report
Project ReportProject Report
Project Report
 
Uml examples
Uml examplesUml examples
Uml examples
 
Project Report
Project ReportProject Report
Project Report
 
Software requirement specification
Software requirement specificationSoftware requirement specification
Software requirement specification
 
Student management system
Student management systemStudent management system
Student management system
 
Student Management System
Student Management SystemStudent Management System
Student Management System
 
Student Management System
Student Management SystemStudent Management System
Student Management System
 
Student Management System
Student Management SystemStudent Management System
Student Management System
 
List of tables
List of tablesList of tables
List of tables
 
List of figures
List of figuresList of figures
List of figures
 
Company profile
Company profileCompany profile
Company profile
 
Chapter 10
Chapter 10Chapter 10
Chapter 10
 
Chapter 9
Chapter 9Chapter 9
Chapter 9
 
Chapter 8
Chapter 8Chapter 8
Chapter 8
 
Chapter 7
Chapter 7Chapter 7
Chapter 7
 
Chapter 5
Chapter 5Chapter 5
Chapter 5
 
Chapter 4
Chapter 4Chapter 4
Chapter 4
 
Chapter 3
Chapter 3Chapter 3
Chapter 3
 

Recently uploaded

Salient Features of India constitution especially power and functions
Salient Features of India constitution especially power and functionsSalient Features of India constitution especially power and functions
Salient Features of India constitution especially power and functions
KarakKing
 
1029-Danh muc Sach Giao Khoa khoi 6.pdf
1029-Danh muc Sach Giao Khoa khoi  6.pdf1029-Danh muc Sach Giao Khoa khoi  6.pdf
1029-Danh muc Sach Giao Khoa khoi 6.pdf
QucHHunhnh
 
Vishram Singh - Textbook of Anatomy Upper Limb and Thorax.. Volume 1 (1).pdf
Vishram Singh - Textbook of Anatomy  Upper Limb and Thorax.. Volume 1 (1).pdfVishram Singh - Textbook of Anatomy  Upper Limb and Thorax.. Volume 1 (1).pdf
Vishram Singh - Textbook of Anatomy Upper Limb and Thorax.. Volume 1 (1).pdf
ssuserdda66b
 
Spellings Wk 3 English CAPS CARES Please Practise
Spellings Wk 3 English CAPS CARES Please PractiseSpellings Wk 3 English CAPS CARES Please Practise
Spellings Wk 3 English CAPS CARES Please Practise
AnaAcapella
 

Recently uploaded (20)

Salient Features of India constitution especially power and functions
Salient Features of India constitution especially power and functionsSalient Features of India constitution especially power and functions
Salient Features of India constitution especially power and functions
 
1029-Danh muc Sach Giao Khoa khoi 6.pdf
1029-Danh muc Sach Giao Khoa khoi  6.pdf1029-Danh muc Sach Giao Khoa khoi  6.pdf
1029-Danh muc Sach Giao Khoa khoi 6.pdf
 
This PowerPoint helps students to consider the concept of infinity.
This PowerPoint helps students to consider the concept of infinity.This PowerPoint helps students to consider the concept of infinity.
This PowerPoint helps students to consider the concept of infinity.
 
Spatium Project Simulation student brief
Spatium Project Simulation student briefSpatium Project Simulation student brief
Spatium Project Simulation student brief
 
How to Manage Global Discount in Odoo 17 POS
How to Manage Global Discount in Odoo 17 POSHow to Manage Global Discount in Odoo 17 POS
How to Manage Global Discount in Odoo 17 POS
 
Dyslexia AI Workshop for Slideshare.pptx
Dyslexia AI Workshop for Slideshare.pptxDyslexia AI Workshop for Slideshare.pptx
Dyslexia AI Workshop for Slideshare.pptx
 
Vishram Singh - Textbook of Anatomy Upper Limb and Thorax.. Volume 1 (1).pdf
Vishram Singh - Textbook of Anatomy  Upper Limb and Thorax.. Volume 1 (1).pdfVishram Singh - Textbook of Anatomy  Upper Limb and Thorax.. Volume 1 (1).pdf
Vishram Singh - Textbook of Anatomy Upper Limb and Thorax.. Volume 1 (1).pdf
 
Single or Multiple melodic lines structure
Single or Multiple melodic lines structureSingle or Multiple melodic lines structure
Single or Multiple melodic lines structure
 
Python Notes for mca i year students osmania university.docx
Python Notes for mca i year students osmania university.docxPython Notes for mca i year students osmania university.docx
Python Notes for mca i year students osmania university.docx
 
How to Give a Domain for a Field in Odoo 17
How to Give a Domain for a Field in Odoo 17How to Give a Domain for a Field in Odoo 17
How to Give a Domain for a Field in Odoo 17
 
Unit-IV; Professional Sales Representative (PSR).pptx
Unit-IV; Professional Sales Representative (PSR).pptxUnit-IV; Professional Sales Representative (PSR).pptx
Unit-IV; Professional Sales Representative (PSR).pptx
 
Holdier Curriculum Vitae (April 2024).pdf
Holdier Curriculum Vitae (April 2024).pdfHoldier Curriculum Vitae (April 2024).pdf
Holdier Curriculum Vitae (April 2024).pdf
 
Food safety_Challenges food safety laboratories_.pdf
Food safety_Challenges food safety laboratories_.pdfFood safety_Challenges food safety laboratories_.pdf
Food safety_Challenges food safety laboratories_.pdf
 
ComPTIA Overview | Comptia Security+ Book SY0-701
ComPTIA Overview | Comptia Security+ Book SY0-701ComPTIA Overview | Comptia Security+ Book SY0-701
ComPTIA Overview | Comptia Security+ Book SY0-701
 
Fostering Friendships - Enhancing Social Bonds in the Classroom
Fostering Friendships - Enhancing Social Bonds  in the ClassroomFostering Friendships - Enhancing Social Bonds  in the Classroom
Fostering Friendships - Enhancing Social Bonds in the Classroom
 
Sociology 101 Demonstration of Learning Exhibit
Sociology 101 Demonstration of Learning ExhibitSociology 101 Demonstration of Learning Exhibit
Sociology 101 Demonstration of Learning Exhibit
 
Unit-V; Pricing (Pharma Marketing Management).pptx
Unit-V; Pricing (Pharma Marketing Management).pptxUnit-V; Pricing (Pharma Marketing Management).pptx
Unit-V; Pricing (Pharma Marketing Management).pptx
 
On National Teacher Day, meet the 2024-25 Kenan Fellows
On National Teacher Day, meet the 2024-25 Kenan FellowsOn National Teacher Day, meet the 2024-25 Kenan Fellows
On National Teacher Day, meet the 2024-25 Kenan Fellows
 
TỔNG ÔN TẬP THI VÀO LỚP 10 MÔN TIẾNG ANH NĂM HỌC 2023 - 2024 CÓ ĐÁP ÁN (NGỮ Â...
TỔNG ÔN TẬP THI VÀO LỚP 10 MÔN TIẾNG ANH NĂM HỌC 2023 - 2024 CÓ ĐÁP ÁN (NGỮ Â...TỔNG ÔN TẬP THI VÀO LỚP 10 MÔN TIẾNG ANH NĂM HỌC 2023 - 2024 CÓ ĐÁP ÁN (NGỮ Â...
TỔNG ÔN TẬP THI VÀO LỚP 10 MÔN TIẾNG ANH NĂM HỌC 2023 - 2024 CÓ ĐÁP ÁN (NGỮ Â...
 
Spellings Wk 3 English CAPS CARES Please Practise
Spellings Wk 3 English CAPS CARES Please PractiseSpellings Wk 3 English CAPS CARES Please Practise
Spellings Wk 3 English CAPS CARES Please Practise
 

Chapter 6

  • 1. Project Id: 32 Implementation Planning Chapter 6 IMPLEMENTATION PLANNING ________________________________________________ CCET (IT) 101
  • 2. Project Id: 32 Implementation Planning 6.1 IMPLEMENTATION ENVIRONMENT The implementation view of software requirement presents the real world manifestation of processing functions and information structures. This computerized system is specified in a manner that dictates accommodation of certain implementation details. The implementation environment of the developed system facilitates multiple users to use this system simultaneously. The user interfaces are designed keeping in mind that the users of this system are familiar to using GUI-based systems. Thus, we restricted ourselves to developing a GUI-based system so that it becomes easier for the end user to get acquainted to the developed system. We have also followed the web based 4-tier architecture as the implementation architecture which is as follows: The presentation tier or user services layer: • This layer gives a user access to the application. It contains all the web pages so it is this interface through which user can access the application. • This layer presents data to the user and optionally permits data manipulation and data entry. The control tier or control layer: • This layer gives a well separation between code and its connectivity with database. • This layer includes the code (VB.NET code) and JS. Mainly this layer includes the replica of presentation layer pages and these pages are mainly control pages. The business services layer: • It consists of business and data rules. Also referred to as the business logic tier, the middle tier is where we as developers can solve mission-critical business problems and achieve major productivity advantages. The components that make up this layer can exist on a server machine, to assist in resource sharing. These CCET (IT) 102
  • 3. Project Id: 32 Implementation Planning components can be used to enforce business rules, such as business algorithms and data rules, which are designed to keep the data structures consistent within either specific or multiple databases. Because these middle-tier components are not tied to a specific client, they can be used by all applications and can be moved to different locations, as response time and other rules require. • In our project we had created various classes appropriate to database and we implemented business logic here. According to request from presentation layer the appropriate rules called and it can access data through data tier. The data tier or data services layer: • This layer interacts with persistent data usually stored in a database or in permanent storage. • In this layer we have implemented the basic function through data can be accessed like insert, update, delete, selection. • Our Requirements are changing dynamically so we used four-tier architecture. The four-tier approach provides benefits such as reusability, flexibility, manageability, maintainability, and scalability. Fig 6.1 Four tier architecture CCET (IT) 103
  • 4. Project Id: 32 Implementation Planning 6.2 CODING STANDARTS • Objects The below are the naming convention for the design element used in the form. Table 6.1 Naming Convention Table Field type Prefix Example Check Box Chk chkReadOnly Combo Box Drop-Down List Box Cmb cmbEnglish Command Button cmd cmdExit Common Dialog dlg dlgFileOpen Data Grid dgr dgrOrderDetails Date Time Picker dtp dtpDateOfBirth Form frm frmEntry Group Box grp grpPymntDtls Horizontal Scroll Bar hsb hsbVolume HTML/Frame fra fraLanguage Image img imgIcon Image List ils ilsAllIcons Label lbl lblHelpMessage Line lin linVertical Link Label lnb lnbGotoWebSite List Box lst lstPolicyCodes List View lvw lvwFolderDtls Main Menu mnu mnuFileOpen Panel pnl pnlOrder Picture Box pic pbxImage Progress Bar prg pbrInstallProgress Radio Button rad radSelect Report rpt rptQtr1Earnings Rich Text Box rtx rtxAddressDtls Shape shp shpCircle Status Bar sts staDateTime Tab page tpg tpgPayerDtls Text Box txt txtLastName Timer tmr tmrAlarm Tool Bar tlb tlbActions Tool Tip tip tipTxtName Vertical Scroll Bar vsb VsbRate Regular Expression Validator rev revUserName CCET (IT) 104
  • 5. Project Id: 32 Implementation Planning Required Field Validator rfv rfvUserName Compare Validator cmv cmvStartDate Validation Summary vas vasValidationSummary Check Box List cbl cblDefectPattern All Hidden Fields should be place one after the other to reserve the space in the form. Description & purpose of each hidden field should be documented in the design spec of the appropriate components. • Variables <prefix>_<meaningful name> prefix : 2 character code. First alphabet represents the scope of the variable l - Local g - Global Second alphabet represents the type b - Boolean c - Currency s - String f - Float i - Integer l - Long t - Time a - Array v - Variant The body of the variable names and function names should use mixed case and should be as long as needed to describe their purpose. To keep the name length reasonable, abbreviations can be used for standard terms like Init for initialization, Tbl for table, Cnt for count, Grp for Group etc. Wherever abbreviations are used, try to use them consistently to improve readability. And in meaningful variable name variable name start with lower case salphabet and second part of the name should be start with upper case alphabet like for student name variable name should be studentName. CCET (IT) 105
  • 6. Project Id: 32 Implementation Planning Recommended Maximum Length for variable names is 32 characters. Example: For declaring a global string variable for Group name: gs_grpName. When passing values to a subroutine/function, use the same variable names in the called routine as in the calling routine. For Functions and Subroutines <prefix>_<meaningful name> For Functions: prefix is fn CCET (IT) 106
  • 7. Project Id: 32 Implementation Planning Recommended Maximum Length for variable names is 32 characters. Example: For declaring a global string variable for Group name: gs_grpName. When passing values to a subroutine/function, use the same variable names in the called routine as in the calling routine. For Functions and Subroutines <prefix>_<meaningful name> For Functions: prefix is fn CCET (IT) 106