Running head: IMPLEMENTATION PHASE OF ENTERPRISE-LEVEL SYSTEMS</titl= e> <o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" name=3D"State"/> <o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" name=3D"place"/> <o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" name=3D"PlaceName"/> <o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" name=3D"PlaceType"/>  <style>  </style>  </head> <body lang=3DEN-US link=3Dblue vlink=3Dpurple style=3D'tab-interval:.5in'> <div class=3DSection1> <a name=3DbmTitlePageRun>Running head: IMPLEMENTA= TION PHASE OF ENTERPRISE-LEVEL SYSTEMS</a> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> <a name=3DbmTitlePageTitle>Implementation Phase of Enterprise-Level Systems</a> <a name=3DbmTitlePageName>Matthew R. King</a> <a name=3DbmTitlePageInst></a><st1:place w:st=3D"on"><= st1:PlaceType w:st=3D"on">University= </st1:PlaceType> of <st1:PlaceName w:st=3D"on">Phoe= nix</st1:PlaceName></st1:place> <a name=3DbmTitleAdd1>Business Systems Development II<= /a> <a name=3DbmTitleAdd2>BSA/400</a> <a name=3DbmTitleAdd4>Jul 16, 2005</a> </div> <span style=3D'font-size:12.0pt;mso-bidi-font-size:10.0pt;line-height:200%; font-family:"Times New Roman";mso-fareast-font-family:"Times New Roman"; mso-ansi-language:EN-US;mso-fareast-language:EN-US;mso-bidi-language:AR-SA'= > <div class=3DSection2></div> <span style=3D'font-size:12.0pt;mso-bidi-font-size:10.0pt;line-height:200%; font-family:"Times New Roman";mso-fareast-font-family:"Times New Roman"; mso-ansi-language:EN-US;mso-fareast-language:EN-US;mso-bidi-language:AR-SA'= > <div class=3DSection3> <a name=3DbmFirstPageTitle>Implementation Phase of Enterprise-Level Systems</a> The Implementation Phase of an Enterprise-level System desig= n is the phase in the SDLC where all planning and design comes to fruition. “This Phase will provide users with the documentation and training re= quired to use the system effectively” <a name=3DC385499243287037385499275462= 963>(Government of British Columbia Information Management Branch, 2001)</a>. In this paper= , I will examine the Build and Implementation Phases, while focus= ing on a specific CASE Tool used for system development. The CASE tool I will focus on is Oracle’s Designer/2000 software product as described by Dr. Paul Dorsey and Peter Koletzke. In developing a process that fits with Designer/2000, Dr. Dorsey and Mr. Kolet= zke re-designed the traditional SDLC. As they describe it, “We found the basic steps of the CASE design process too broad. Therefore, we have added = the transition steps of Pre-Analysis</i= > and Pre-Design to the basic methodolog= y as well as including Implementation</i= > in the overall process. We have named our expanded CASE method, CADM (CASE Application Development Method), pronounced cad-em” <a name=3DC385499295601852385499423263889>(Dorsey & Koletzke, 2000)</a>. Although Designer/2000 and CADM are relevant to the Enterprise-level System design as a whole, this paper will focus on the Build and Implementatio= n Phases. The Build Phase = of Enterprise-level System Development “deals with the development, unit testing and integration testing of the application modules, screens, and reports. In addition, this Phase addresses the preparation and establishmen= t of the technical environment for development, testing and training of user representatives” <a name=3DC385499243287037385499821875000>(Governmen= t of British Columbia Information Management Branch, 2001)</a>. This phase is the precursor to the Implementation Phase, and thus is very important to succes= sful implementation of the finished system. Using Designer/2000, this phase should flow smoothly, assumi= ng the previous phases are complete in a like fashion. With information provided f= rom previous phases, the developer begins the actual coding that will become the final system. In addition, documentation of the system and its operations develop. “This Phase is usually carried out in parallel with the development of user procedures and user documentation from the Implementati= on Phase. Both of these will be required for module testing, upon the completi= on of the Build Phase” <a name=3DC385499243287037385499878125000>(Govern= ment of British Columbia Information Management Branch, 2001)</a>. The final deliverables of the Build Phase are the database a= nd applications ready for testing. Oracle’s Designer/2000 helps the data= base building along by providing the developer with material from previous SDLC phase. “Database building involves direct generation using Designer/2= 000. All triggers and data structures can be kept within the physical model in Designer/2000, so the building of the database is a straightforward operation” <a name=3DC385499295601852385505209837963>(Dorsey & Koletzke, 2000)</a>. The database provides the backbone of the new system, = and must meet all system requirements as determined in the previous phases. Typically, the applications designed for user-access to the database develop in parallel with the database. The developer has several software options to choose from when designing the application. However, on= ce again, Designer/2000 offers its own solutions, should the developer choose = to go this route. “The exact activities you perform in Designer/2000 dep= end on your choice of products for the application modules. If you decide to use Oracle Developer/2000 Forms, Reports and Graphics for the product set, the Designer/2000 generators can give you a quite complete set of working modul= es which may or may not need modification after generation” <a name=3DC385499295601852385505317245370>(Dorsey & Koletzke, 2000)</a>. <= /p> In the traditional SDLC, the Build Phase ends with a test of= the applications and database. Sometimes, the Testing Phase occurs at the begin= ning of the Implementation Phase. “Individual system components that successfully completed unit and integration testing during the Build Phase = are now subjected to a more rigorous system and acceptance testing, as defined = by the testing plans” <a name=3DC385499243287037385505372106481>(Governm= ent of British Columbia Information Management Branch, 2001)</a>. In either case, a test of the applications and database completes before implementation begin= s. However, Dr. Dorsey and Mr. Koletzke feel this test is typic= ally inadequate, and so they have a separate Testing Phase in CADM. “Testi= ng is one of the most important but usually most poorly conducted phases in the system design process. The key to proper testing is to use multiple tests. = No single test, no matter how carefully conducted, will find all of the errors= in a system” <a name=3DC385499295601852385505349305556>(Dorsey & Kol= etzke, 2000)</a>. To this end, they cite several testing methods to elicit the most complete results. “To achieve this goal, you must perform unit-level tests application by application. The testing process should be meticulous,= using test data, automated testing scripts, code walkthroughs, and interviews with the system developer. You also must perform overall database-level checks” <a name=3DC385499295601852385505395601852>(Dorsey & Kolet= zke)</a>. By the end of the Testing Phase, the new database and applications are read= y for implementation. There are several methods for implementing a new system at t= he enterprise-level. One such method is a phased approach, whereby the implementation of the new system is module-by-mod= ule to ensure compatibility and reliability. This careful approach is time consuming. However, this seeming disadvantage is an advantage for those nee= ding to learn the new system. Another advantage to this approach is the focus of= the developer on one module at a time, ensuring it is working correctly before = proceeding to the next. Another method of implementing a new enterprise-level system= is the parallel method. In this method, the new system exists at the same time= as the old system. “In most cases, running the new system in parallel wi= th the legacy system requires double entry into both systems while the bugs are being worked out” <a name=3DC385499295601852385505575925926>(Dorsey &= amp; Koletzke, 2000)</a>. The largest advantage to this method involves the reliability of existing data until all of the bugs work themselves out of t= he new system. However, there are several large disadvantages to this method. = One being the labor required to maintain two systems at once, along with the confusion encountered by users when using two systems at once. Organizations requiring the safety net for sensitive information prefer this method. Nevertheless, it is a costly and time-consuming process. One more solution for implementing an enterprise-level syste= m is the Big-Bang approach. In this = risky endeavor, the old system is simply cut-off, and the new system brought on-l= ine to replace it. “In this approach, there is no turning back. If you use this approach, it is critical that the system is well tested” <a name=3DC385499295601852385505567592593>(Dorsey & Koletzke, 2000)</a>. T= he advantage of this approach is the potential time and cost savings in the instant implementation of the new system. The potentially devastating disadvantages involve the complete loss of data, and intense maintenance required as bugs appear. “While there are no special activities that occur in t= he Implementation phase from the Designer/2000 standpoint, you can produce huge volumes of documentation of all sorts using the Repository Reports tool as = well as reports you come up with based on the Designer/2000 API views” <a name=3DC385499295601852385505587268519>(Dorsey & Koletzke, 2000)</a>. T= he documentation automatically created using Designer/2000 is a large help to = the system developer, allowing for the creation of user manuals and code documentation. In this paper, I have examined the Build and Implementation = Phases of the SDLC by way of Oracle’s Designer/2000. A variance of the SDLC known as CADM, works well with Designer/2000 as it takes advantage of Designer/2000’s features. There are minor differences between the two methods in the Build and Implementation Phases, however CADM fits better wi= th application described. <span style=3D'font-size:12.0pt;mso-bidi-font-size:10.0pt;line-height:200%; font-family:"Times New Roman";mso-fareast-font-family:"Times New Roman"; mso-ansi-language:EN-US;mso-fareast-language:EN-US;mso-bidi-language:AR-SA'= > References <a name=3DR385499295601852>Dorsey, P., & Koletz= ke, P. (2000). CASE Application Development Method (CADM) Using Designer/2000. Retrieved July 8, 2005, from </a><a href=3D"http://ourworld.compuserve.com/homepages/Peter_Koletzke/white_paper= s/imeth132.pdf">http://ourworld.compuserve.com/home= pages/Peter_Koletzke/white_papers/imeth132.pdf</a> <a name=3DR385499243287037>Government of </a><st1:S= tate w:st=3D"on"><st1:place w:st=3D"on">British Columbia</st1:place></st1:State> Information Management Branch (2001). SDLC Standards. Retrieved July 16, 2005, from <a href=3D"http://srmwww.gov.bc.ca/imb/3star/sdlc/0overview/overview.htm#3-6">= http://srmwww.gov.bc.ca/imb/3star/s= dlc/0overview/overview.htm#3-6</a> <o:p> </o:p> <table class=3DMsoNormalTable border=3D0 cellpadding=3D0 width=3D"100%" style=3D'width:100.0%;mso-cellspacing:1.5pt;mso-padding-alt:0in 5.4pt 0in = 5.4pt'> <tr style=3D'mso-yfti-irow:0;mso-yfti-firstrow:yes;mso-yfti-lastrow:yes'> <td width=3D"50%" valign=3Dtop style=3D'width:50.0%;padding:.75pt .75pt .= 75pt .75pt'> <a href=3D"http://home.comcast.net/~mking56/papindex.htm">Return = to Index</a> </td> <td width=3D"50%" valign=3Dtop style=3D'width:50.0%;padding:.75pt .75pt .= 75pt .75pt'> <a href=3D"http://home.comcast.net/~mking56">Return to Home Page</a><o:p></o:p> </td> </tr> </table> <o:p> </o:p> </div> </body> </html> ------=_NextPart_01C59055.42C93670 Content-Location: file:///C:/6E4BB24E/BSA400_ERPImplementation_files/header.htm Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="us-ascii" <html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" xmlns=3D"http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii"> <meta name=3DProgId content=3DWord.Document> <meta name=3DGenerator content=3D"Microsoft Word 11"> <meta name=3DOriginator content=3D"Microsoft Word 11"> <link id=3DMain-File rel=3DMain-File href=3D"../BSA400_ERPImplementation.ht= m"> <![if IE]> <base href=3D"file:///C:\6E4BB24E\BSA400_ERPImplementation_files\header.htm" id=3D"webarch_temp_base_tag"> <![endif]><o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" name=3D"State"= /> <o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" name=3D"place"/> <o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" name=3D"PlaceName"/> <o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" name=3D"PlaceType"/>  </head> <body lang=3DEN-US link=3Dblue vlink=3Dpurple> <div style=3D'mso-element:footnote-separator' id=3Dfs> <![if !supportFootnotes]> <hr align=3Dleft size=3D1 width=3D"33%"> <![endif]> </div> <div style=3D'mso-element:footnote-continuation-separator' id=3Dfcs> <![if !supportFootnotes]> <hr align=3Dleft size=3D1> <![endif]> </div> <div style=3D'mso-element:endnote-separator' id=3Des> <![if !supportFootnotes]> <hr align=3Dleft size=3D1 width=3D"33%"> <![endif]> </div> <div style=3D'mso-element:endnote-continuation-separator' id=3Decs> <![if !supportFootnotes]> <hr align=3Dleft size=3D1> <![endif]> </div> <div style=3D'mso-element:header' id=3Dh1> Implementation Phase 1 </div> </body> </html> ------=_NextPart_01C59055.42C93670 Content-Location: file:///C:/6E4BB24E/BSA400_ERPImplementation_files/filelist.xml Content-Transfer-Encoding: quoted-printable Content-Type: text/xml; charset="utf-8" <xml xmlns:o=3D"urn:schemas-microsoft-com:office:office"> <o:MainFile HRef=3D"../BSA400_ERPImplementation.htm"/> <o:File HRef=3D"header.htm"/> <o:File HRef=3D"filelist.xml"/> </xml> ------=_NextPart

MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_NextPart_01C59055.42C93670" This document is a Single File Web Page, also known as a Web Archive file. If you are seeing this message, your browser or editor doesn't support Web Archive files. Please download a browser that supports Web Archive, such as Microsoft Internet Explorer. ------=_NextPart_01C59055.42C93670 Content-Location: file:///C:/6E4BB24E/BSA400_ERPImplementation.htm Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="us-ascii" Running head: IMPLEMENTATION PHASE OF ENTERPRISE-LEVEL SYSTEMS</titl= e> <o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" name=3D"State"/> <o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" name=3D"place"/> <o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" name=3D"PlaceName"/> <o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" name=3D"PlaceType"/>  <style>  </style>  </head> <body lang=3DEN-US link=3Dblue vlink=3Dpurple style=3D'tab-interval:.5in'> <div class=3DSection1> <a name=3DbmTitlePageRun>Running head: IMPLEMENTA= TION PHASE OF ENTERPRISE-LEVEL SYSTEMS</a> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> <a name=3DbmTitlePageTitle>Implementation Phase of Enterprise-Level Systems</a> <a name=3DbmTitlePageName>Matthew R. King</a> <a name=3DbmTitlePageInst></a><st1:place w:st=3D"on"><= st1:PlaceType w:st=3D"on">University= </st1:PlaceType> of <st1:PlaceName w:st=3D"on">Phoe= nix</st1:PlaceName></st1:place> <a name=3DbmTitleAdd1>Business Systems Development II<= /a> <a name=3DbmTitleAdd2>BSA/400</a> <a name=3DbmTitleAdd4>Jul 16, 2005</a> </div> <span style=3D'font-size:12.0pt;mso-bidi-font-size:10.0pt;line-height:200%; font-family:"Times New Roman";mso-fareast-font-family:"Times New Roman"; mso-ansi-language:EN-US;mso-fareast-language:EN-US;mso-bidi-language:AR-SA'= > <div class=3DSection2></div> <span style=3D'font-size:12.0pt;mso-bidi-font-size:10.0pt;line-height:200%; font-family:"Times New Roman";mso-fareast-font-family:"Times New Roman"; mso-ansi-language:EN-US;mso-fareast-language:EN-US;mso-bidi-language:AR-SA'= > <div class=3DSection3> <a name=3DbmFirstPageTitle>Implementation Phase of Enterprise-Level Systems</a> The Implementation Phase of an Enterprise-level System desig= n is the phase in the SDLC where all planning and design comes to fruition. “This Phase will provide users with the documentation and training re= quired to use the system effectively” <a name=3DC385499243287037385499275462= 963>(Government of British Columbia Information Management Branch, 2001)</a>. In this paper= , I will examine the Build and Implementation Phases, while focus= ing on a specific CASE Tool used for system development. The CASE tool I will focus on is Oracle’s Designer/2000 software product as described by Dr. Paul Dorsey and Peter Koletzke. In developing a process that fits with Designer/2000, Dr. Dorsey and Mr. Kolet= zke re-designed the traditional SDLC. As they describe it, “We found the basic steps of the CASE design process too broad. Therefore, we have added = the transition steps of Pre-Analysis</i= > and Pre-Design to the basic methodolog= y as well as including Implementation</i= > in the overall process. We have named our expanded CASE method, CADM (CASE Application Development Method), pronounced cad-em” <a name=3DC385499295601852385499423263889>(Dorsey & Koletzke, 2000)</a>. Although Designer/2000 and CADM are relevant to the Enterprise-level System design as a whole, this paper will focus on the Build and Implementatio= n Phases. The Build Phase = of Enterprise-level System Development “deals with the development, unit testing and integration testing of the application modules, screens, and reports. In addition, this Phase addresses the preparation and establishmen= t of the technical environment for development, testing and training of user representatives” <a name=3DC385499243287037385499821875000>(Governmen= t of British Columbia Information Management Branch, 2001)</a>. This phase is the precursor to the Implementation Phase, and thus is very important to succes= sful implementation of the finished system. Using Designer/2000, this phase should flow smoothly, assumi= ng the previous phases are complete in a like fashion. With information provided f= rom previous phases, the developer begins the actual coding that will become the final system. In addition, documentation of the system and its operations develop. “This Phase is usually carried out in parallel with the development of user procedures and user documentation from the Implementati= on Phase. Both of these will be required for module testing, upon the completi= on of the Build Phase” <a name=3DC385499243287037385499878125000>(Govern= ment of British Columbia Information Management Branch, 2001)</a>. The final deliverables of the Build Phase are the database a= nd applications ready for testing. Oracle’s Designer/2000 helps the data= base building along by providing the developer with material from previous SDLC phase. “Database building involves direct generation using Designer/2= 000. All triggers and data structures can be kept within the physical model in Designer/2000, so the building of the database is a straightforward operation” <a name=3DC385499295601852385505209837963>(Dorsey & Koletzke, 2000)</a>. The database provides the backbone of the new system, = and must meet all system requirements as determined in the previous phases. Typically, the applications designed for user-access to the database develop in parallel with the database. The developer has several software options to choose from when designing the application. However, on= ce again, Designer/2000 offers its own solutions, should the developer choose = to go this route. “The exact activities you perform in Designer/2000 dep= end on your choice of products for the application modules. If you decide to use Oracle Developer/2000 Forms, Reports and Graphics for the product set, the Designer/2000 generators can give you a quite complete set of working modul= es which may or may not need modification after generation” <a name=3DC385499295601852385505317245370>(Dorsey & Koletzke, 2000)</a>. <= /p> In the traditional SDLC, the Build Phase ends with a test of= the applications and database. Sometimes, the Testing Phase occurs at the begin= ning of the Implementation Phase. “Individual system components that successfully completed unit and integration testing during the Build Phase = are now subjected to a more rigorous system and acceptance testing, as defined = by the testing plans” <a name=3DC385499243287037385505372106481>(Governm= ent of British Columbia Information Management Branch, 2001)</a>. In either case, a test of the applications and database completes before implementation begin= s. However, Dr. Dorsey and Mr. Koletzke feel this test is typic= ally inadequate, and so they have a separate Testing Phase in CADM. “Testi= ng is one of the most important but usually most poorly conducted phases in the system design process. The key to proper testing is to use multiple tests. = No single test, no matter how carefully conducted, will find all of the errors= in a system” <a name=3DC385499295601852385505349305556>(Dorsey & Kol= etzke, 2000)</a>. To this end, they cite several testing methods to elicit the most complete results. “To achieve this goal, you must perform unit-level tests application by application. The testing process should be meticulous,= using test data, automated testing scripts, code walkthroughs, and interviews with the system developer. You also must perform overall database-level checks” <a name=3DC385499295601852385505395601852>(Dorsey & Kolet= zke)</a>. By the end of the Testing Phase, the new database and applications are read= y for implementation. There are several methods for implementing a new system at t= he enterprise-level. One such method is a phased approach, whereby the implementation of the new system is module-by-mod= ule to ensure compatibility and reliability. This careful approach is time consuming. However, this seeming disadvantage is an advantage for those nee= ding to learn the new system. Another advantage to this approach is the focus of= the developer on one module at a time, ensuring it is working correctly before = proceeding to the next. Another method of implementing a new enterprise-level system= is the parallel method. In this method, the new system exists at the same time= as the old system. “In most cases, running the new system in parallel wi= th the legacy system requires double entry into both systems while the bugs are being worked out” <a name=3DC385499295601852385505575925926>(Dorsey &= amp; Koletzke, 2000)</a>. The largest advantage to this method involves the reliability of existing data until all of the bugs work themselves out of t= he new system. However, there are several large disadvantages to this method. = One being the labor required to maintain two systems at once, along with the confusion encountered by users when using two systems at once. Organizations requiring the safety net for sensitive information prefer this method. Nevertheless, it is a costly and time-consuming process. One more solution for implementing an enterprise-level syste= m is the Big-Bang approach. In this = risky endeavor, the old system is simply cut-off, and the new system brought on-l= ine to replace it. “In this approach, there is no turning back. If you use this approach, it is critical that the system is well tested” <a name=3DC385499295601852385505567592593>(Dorsey & Koletzke, 2000)</a>. T= he advantage of this approach is the potential time and cost savings in the instant implementation of the new system. The potentially devastating disadvantages involve the complete loss of data, and intense maintenance required as bugs appear. “While there are no special activities that occur in t= he Implementation phase from the Designer/2000 standpoint, you can produce huge volumes of documentation of all sorts using the Repository Reports tool as = well as reports you come up with based on the Designer/2000 API views” <a name=3DC385499295601852385505587268519>(Dorsey & Koletzke, 2000)</a>. T= he documentation automatically created using Designer/2000 is a large help to = the system developer, allowing for the creation of user manuals and code documentation. In this paper, I have examined the Build and Implementation = Phases of the SDLC by way of Oracle’s Designer/2000. A variance of the SDLC known as CADM, works well with Designer/2000 as it takes advantage of Designer/2000’s features. There are minor differences between the two methods in the Build and Implementation Phases, however CADM fits better wi= th application described. <span style=3D'font-size:12.0pt;mso-bidi-font-size:10.0pt;line-height:200%; font-family:"Times New Roman";mso-fareast-font-family:"Times New Roman"; mso-ansi-language:EN-US;mso-fareast-language:EN-US;mso-bidi-language:AR-SA'= > References <a name=3DR385499295601852>Dorsey, P., & Koletz= ke, P. (2000). CASE Application Development Method (CADM) Using Designer/2000. Retrieved July 8, 2005, from </a><a href=3D"http://ourworld.compuserve.com/homepages/Peter_Koletzke/white_paper= s/imeth132.pdf">http://ourworld.compuserve.com/home= pages/Peter_Koletzke/white_papers/imeth132.pdf</a> <a name=3DR385499243287037>Government of </a><st1:S= tate w:st=3D"on"><st1:place w:st=3D"on">British Columbia</st1:place></st1:State> Information Management Branch (2001). SDLC Standards. Retrieved July 16, 2005, from <a href=3D"http://srmwww.gov.bc.ca/imb/3star/sdlc/0overview/overview.htm#3-6">= http://srmwww.gov.bc.ca/imb/3star/s= dlc/0overview/overview.htm#3-6</a> <o:p> </o:p> <table class=3DMsoNormalTable border=3D0 cellpadding=3D0 width=3D"100%" style=3D'width:100.0%;mso-cellspacing:1.5pt;mso-padding-alt:0in 5.4pt 0in = 5.4pt'> <tr style=3D'mso-yfti-irow:0;mso-yfti-firstrow:yes;mso-yfti-lastrow:yes'> <td width=3D"50%" valign=3Dtop style=3D'width:50.0%;padding:.75pt .75pt .= 75pt .75pt'> <a href=3D"http://home.comcast.net/~mking56/papindex.htm">Return = to Index</a> </td> <td width=3D"50%" valign=3Dtop style=3D'width:50.0%;padding:.75pt .75pt .= 75pt .75pt'> <a href=3D"http://home.comcast.net/~mking56">Return to Home Page</a><o:p></o:p> </td> </tr> </table> <o:p> </o:p> </div> </body> </html> ------=_NextPart_01C59055.42C93670 Content-Location: file:///C:/6E4BB24E/BSA400_ERPImplementation_files/header.htm Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="us-ascii" <html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" xmlns=3D"http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii"> <meta name=3DProgId content=3DWord.Document> <meta name=3DGenerator content=3D"Microsoft Word 11"> <meta name=3DOriginator content=3D"Microsoft Word 11"> <link id=3DMain-File rel=3DMain-File href=3D"../BSA400_ERPImplementation.ht= m"> <![if IE]> <base href=3D"file:///C:\6E4BB24E\BSA400_ERPImplementation_files\header.htm" id=3D"webarch_temp_base_tag"> <![endif]><o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" name=3D"State"= /> <o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" name=3D"place"/> <o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" name=3D"PlaceName"/> <o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" name=3D"PlaceType"/>  </head> <body lang=3DEN-US link=3Dblue vlink=3Dpurple> <div style=3D'mso-element:footnote-separator' id=3Dfs> <![if !supportFootnotes]> <hr align=3Dleft size=3D1 width=3D"33%"> <![endif]> </div> <div style=3D'mso-element:footnote-continuation-separator' id=3Dfcs> <![if !supportFootnotes]> <hr align=3Dleft size=3D1> <![endif]> </div> <div style=3D'mso-element:endnote-separator' id=3Des> <![if !supportFootnotes]> <hr align=3Dleft size=3D1 width=3D"33%"> <![endif]> </div> <div style=3D'mso-element:endnote-continuation-separator' id=3Decs> <![if !supportFootnotes]> <hr align=3Dleft size=3D1> <![endif]> </div> <div style=3D'mso-element:header' id=3Dh1> Implementation Phase 1 </div> </body> </html> ------=_NextPart_01C59055.42C93670 Content-Location: file:///C:/6E4BB24E/BSA400_ERPImplementation_files/filelist.xml Content-Transfer-Encoding: quoted-printable Content-Type: text/xml; charset="utf-8" <xml xmlns:o=3D"urn:schemas-microsoft-com:office:office"> <o:MainFile HRef=3D"../BSA400_ERPImplementation.htm"/> <o:File HRef=3D"header.htm"/> <o:File HRef=3D"filelist.xml"/> </xml> ------=_NextPart_01C59055.42C93670--