Running head: DESIGN PHASE OF AN ENTERPRISE-LEVEL BUSINESS SYSTEM</t= itle> <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: DESIGN PHA= SE OF AN ENTERPRISE-LEVEL BUSINESS SYSTEM</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>Design Phase of an Enterpri= se-Level Business System</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 Analysis II</a>= <a name=3DbmTitleAdd2>BSA/400</a> <a name=3DbmTitleAdd4>Jul 08, 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>Design Phase of an Enterpri= se-Level Business System</a> The Design Phase of an Enterprise-Level Business System occu= rs after the Analysis Phase, and is where careful plans become actual details.= As author Martin Modell explains, “Systems analysis is the decomposition= of the current environment into its component pieces for examination and study. The design process is development of a plan for the building up of a larger harmonious unit from component parts” <a name=3DC385419019328704385419030208333>(Modell, 2003)</a>. In this paper, I= will examine a particular methodology and tool available to the developer in the Design Phase. “The objective of the Design Phase is to transform the detailed, defined requirements into complete, detailed specifications for t= he system to guide the work of the Development Phase” <a name=3DC385419069328704385419135995370>(Maryland Department of Budget & Management, 2002, chap. 5)</a>. Various methods exist to help the developer during this important phase that incorporate common characteristics. Howeve= r, these evolving methods require reconfiguring to meet the requirements of individual organizations. “As these methods become more widespread, m= ore widely adopted, and integrated into the software development life cycle, organizations inevitably will want to tailor them. Consequently, organizati= ons that wish to include quality-attribute-based requirements, explicit architecture design, and architecture analysis in their software development life cycles will be best served if they can do so organically” <a name=3DC385419164236111385419262962963>(K= azman, Nord, & Klein, 2003)</a>. Successful developers give careful considerat= ion as to which methodology to employ, and to which methodologies to reconfigur= e to suit the organization’s needs. The different components included in any system design are i= nput, output, processing, and files. Mapping these components and their relations= hip to each other is important before actual programming begins. “The exceptional or foolish programm= er might begin coding without a good design. Programmers who do so may find themselves going back to modify pieces of code they've already written as t= hey move through the project” <a name=3DC385435624652778385435673263889>(= Thompson Course Technology, n.d.)</a>. The input and output requirements are especia= lly important to the overall system design, as these constraints often determine which methodologies to use during the Design Phase. Over the past ten years, several architecture-centric analys= is and design methods became available. These methodologies evolved to meet the requirements of the organizations employing them in both Analysis and Design Phases. These methodologies, in no particular order, include Quality Attrib= ute Workshop, or QAW; Cost-Benefit Analysis Method, or CBAM; Active Reviews for Intermediate Design, or ARID and Attribute-Driven Design, or ADD= . While this list is not exhaustive, it includes predominate examples <a name=3DC385419164236111385435808680556>(Kazman et al., 2003)</a>. From this= list, I will examine the Cost-Benefit Analysis Method, or CBAM, as it is representative of all methods. The Cost-Benefit Analysis Method “helps the systemR= 17;s stakeholders to choose among architectural alternatives for enhancing the system in design or maintenance phases” <a name=3DC385419164236111385435842129630>(Kazman et al., 2003)</a>. This meth= od, more than the others, examines the overall benefits and risks associated wi= th the system in terms of cost. “The CBAM enables users to make informed software requirement and software investment decisions based upon an analys= is of the economic and architectural implications of those decisions” <a name=3DC385435879050926385435887847222>(</a><st1:place w:st=3D"on"><st1:Pla= ceName w:st=3D"on">C= arnegie</st1:PlaceName> <st1:PlaceName w:s= t=3D"on">Mellon</st1:PlaceName> <st1:PlaceType w:st=3D"on">University</st1:PlaceType></st1:place><s= pan style=3D'mso-bookmark:C385435879050926385435887847222'>, 2005). This methodology offers the programmer and organization a process for analyzing = the financial benefits of the system in question. Authors Rick Kazman, Robert Nord, and Mark Klein from the Ca= rnegie Mellon Software Engineering Institute break down this process from required inputs to outputs. The inputs to the CBAM include a) the system’s business/mission drivers, b) a list of scenarios, and c) the existing architectural documentation. Utilizing these inputs and following the prescribed steps, the CBAM offers outputs that include a) a set of architectural strategies, with associated costs, benefits, and schedule implications, b) prioritized architectural strategies based on Return On Investment, or ROI, and c) the = risk of each architectural strategy, quantified as variability in cost, benefit,= and ROI values <a name=3DC385419164236111385435966550926>(Kazman et al., 2003)<= /a>. Obviously, the accuracy of the inputs greatly affects the va= lidity of the outputs. For the CBAM to be effective, the previous steps of the SDLC must be correct. Assuming the inputs have merit, the CBAM offers nine steps= for achieving valid outputs. Within these nine steps, various architecture-cent= ered scenarios present themselves for analysis and voting. It is during these st= eps that examination of scenarios occurs for their ability to meet all of the n= eeds of the organization, including business goals, quality attributes, costs, a= nd ROI. These steps repeat themselves until one scenario becomes apparent <a name=3DC385419164236111385436100115741>(Kazman et al., 2003)</a>. The Cost-Benefit Analysis Method described above is an examp= le of several architecture-centric methodologies available in addition to the traditional SDLC. “While each of these steps involves additional over= head as compared with the traditional, non-architecture-aware SDLC, this additio= nal encumbrance is more than repaid by having an architecture that is designed, documented, analyzed, and evolved in a disciplined way” <a name=3DC385419164236111385436193171296>(Kazman et al., 2003)</a>. Many computer-aided tools are available to a programmer when designing an enterprise system following the SDLC. One such tool is Oracle’s Designer/2000. T= his software helps a programmer through the SDLC from start to finish, although Oracle re-designs the SDLC slightly to make the best possible use of their program. Oracle presents this method as CASE Application Development Method= , or CADM <a name=3DC385419273958333385436277199074>(Dorsey & Koletzke, 2000)</a>. M= any of the CADM phases are concurrent with the traditional SDLC however; Oracle of= fers Pre-Analysis and Pre-Design Phases to their method. The Pre-Design Phase= sits between the Analysis and Design Phases. Using Oracle’s CADM, the Pre-Design Phase includes steps for the design plan, process flows, design standards, screen concept prototype, and Pre-Design evaluation. It is during this phase that decisions concerning the screen layout, navigation tools, h= elp systems, documentation, functionality, coding standards, and naming convent= ions come under scrutiny <a name=3DC385419273958333385436342592593>(Dorsey & Koletzke, 2000)</a>. Oracle’s Designer/2000 program aids this process by of= fering templates for the developer to use. “The Pre-Design phase is complete when users are happy with the screen prototypes and process flows. Both use= rs and developers should approve the design standards and Design Plan” <a name=3DC385419273958333385436363078704>(Dorsey & Koletzke, 2000)</a>. O= nce complete, the Design Phase begins. Oracle’s CADM divides the Design Phase into two sub-ph= ases: Database Design and Application Design. Again, this coincides with their Design/2000 software product. “The Design phase is where the blueprints are drawn= for building the system. Every detail should be laid out before generation̶= 1; <a name=3DC385419273958333385436384490741>(Dorsey & Koletzke, 2000)</a>. As described in previous paragraphs, good preparation is paramount before actu= al programming begins. Oracle’s Designer/2000 product keeps this in mind= for the programmer and aids both database and application design. “Database Design involves the designing of the tables = and columns along with the detailed specification of domains and check constrai= nts on the columns” <a name=3DC385419273958333385436411226852>(Dorsey &am= p; Koletzke, 2000)</a>. This phase corresponds with the Detailed Design phase = of other methodologies. It is during this phase where the definition of databa= se objects takes place, as well as the tables and modules required of the database. Definition of a final Entity-Relationship Diagram takes place in = this phase, and documentation of the database is an essential deliverable. Again, Oracle’s Designer/2000 program offers templates and menus to aid the developer through this process. “In addition to the design of specific applications and reports, Application Design involves decision making about what product wil= l be used for those designs, i.e. Visual Basic, Forms, HTML, or C++” <a name=3DC385419273958333385436457638889>(Dorsey & Koletzke, 2000)</a>. W= hereas the Database Design determines the underlying database, the Application Des= ign determines how the database will appear before the users. “Another important activity in this part of the Design phase is the cross-checks of = the database design. You want to be sure that the data elements you defined in = the Database Design part of Design are fully utilized and included in the set of modules you produce” <a name=3DC385419164236111385436489930556>(Kazma= n et al., 2003)</a>. Once complete and approved, Designer/2000 takes the develop= er to the Build Phase of the CADM. In this paper, I have examined a methodology and tool availa= ble to developers during the Design Phase of the SDLC. As shown, the SDLC continue= s to evolve and develop as needs and requirements arise. The method and tool examined in this paper represent various methodologies and tools available,= and it becomes incumbent on system developers to prepare themselves with the be= st methodologies and tools for the system. <o:p> </o:p> <o:p> </o:p> <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=3DR385435879050926></a><st1:place w:st=3D"o= n"><st1:PlaceName w:st=3D"on">Carnegie<= /st1:PlaceName> <st1:PlaceName w:st=3D"on">Mellon= </st1:PlaceName> <st1:PlaceType w:st=3D"on">University</st1:PlaceType></st1:place><s= pan style=3D'mso-bookmark:R385435879050926'> (2005). Cost Benefit Analysis Method (CBAM). Retrieved July 8, 2005, fr= om <a href=3D"http://www.sei.cmu.edu/architecture/products_services/cbam.html"><s= pan style=3D'mso-bookmark:R385435879050926'>http://www.sei.cmu.edu/architecture= /products_services/cbam.html</a> <a name=3DR385419273958333>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=3DR385419164236111>Kazman, R., Nord, R. L.,= & Klein, M. (2003, September). A Life= -Cycle View of Architectural Analysis and Design Methods. Retrieved July 8, 20= 05, from </a><a href=3D"http://www.sei.cmu.edu/pub/documents/03.reports/pdf/03tn026.pdf"><s= pan style=3D'mso-bookmark:R385419164236111'>http://www.sei.cmu.edu/pub/document= s/03.reports/pdf/03tn026.pdf</a> <a name=3DR385419069328704>Maryland Department of B= udget & Management (2002, July). Systems Development Life Cycle (SDLC) Volume 2 - SDLC Phases. Retrieved July 8, 2005, from </a><a href=3D"http://docushare.msde.state.md.us/docushare/dsweb/Get/Document-5070= 1/sdlcvol2.pdf">http://docushare.msde.state.md.us/d= ocushare/dsweb/Get/Document-50701/sdlcvol2.pdf</a> <a name=3DR385419019328704>Modell, M. E. (2003). System Development Life Cycle - Design= . Retrieved July 8, 2005, from </a><a href=3D"http://www.dai-sho.com/ddsd/ddsd04.html">= http://www.dai-sho.com/ddsd/ddsd04.= html</a> <a name=3DR385435624652778>Thompson Course Technolo= gy (n.d.). The Systems Development Life Cycle.= Retrieved July 8, 2005, from </a><a href=3D"http://www.muskalipman.com/VBObjects/SDLC= .pdf">http://www.muskalipman.com/VBObject= s/SDLC.pdf</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.320A6890 Content-Location: file:///C:/8E8B314E/BSA400_ERPDesign_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_ERPDesign.htm"> <![if IE]> <base href=3D"file:///C:\8E8B314E\BSA400_ERPDesign_files\header.htm" id=3D"webarch_temp_base_tag"> <![endif]><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> Design Phase 1 </div> </body> </html> ------=_NextPart_01C59055.320A6890 Content-Location: file:///C:/8E8B314E/BSA400_ERPDesign_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_ERPDesign.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.320A6890" 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.320A6890 Content-Location: file:///C:/8E8B314E/BSA400_ERPDesign.htm Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="us-ascii" Running head: DESIGN PHASE OF AN ENTERPRISE-LEVEL BUSINESS SYSTEM</t= itle> <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: DESIGN PHA= SE OF AN ENTERPRISE-LEVEL BUSINESS SYSTEM</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>Design Phase of an Enterpri= se-Level Business System</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 Analysis II</a>= <a name=3DbmTitleAdd2>BSA/400</a> <a name=3DbmTitleAdd4>Jul 08, 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>Design Phase of an Enterpri= se-Level Business System</a> The Design Phase of an Enterprise-Level Business System occu= rs after the Analysis Phase, and is where careful plans become actual details.= As author Martin Modell explains, “Systems analysis is the decomposition= of the current environment into its component pieces for examination and study. The design process is development of a plan for the building up of a larger harmonious unit from component parts” <a name=3DC385419019328704385419030208333>(Modell, 2003)</a>. In this paper, I= will examine a particular methodology and tool available to the developer in the Design Phase. “The objective of the Design Phase is to transform the detailed, defined requirements into complete, detailed specifications for t= he system to guide the work of the Development Phase” <a name=3DC385419069328704385419135995370>(Maryland Department of Budget & Management, 2002, chap. 5)</a>. Various methods exist to help the developer during this important phase that incorporate common characteristics. Howeve= r, these evolving methods require reconfiguring to meet the requirements of individual organizations. “As these methods become more widespread, m= ore widely adopted, and integrated into the software development life cycle, organizations inevitably will want to tailor them. Consequently, organizati= ons that wish to include quality-attribute-based requirements, explicit architecture design, and architecture analysis in their software development life cycles will be best served if they can do so organically” <a name=3DC385419164236111385419262962963>(K= azman, Nord, & Klein, 2003)</a>. Successful developers give careful considerat= ion as to which methodology to employ, and to which methodologies to reconfigur= e to suit the organization’s needs. The different components included in any system design are i= nput, output, processing, and files. Mapping these components and their relations= hip to each other is important before actual programming begins. “The exceptional or foolish programm= er might begin coding without a good design. Programmers who do so may find themselves going back to modify pieces of code they've already written as t= hey move through the project” <a name=3DC385435624652778385435673263889>(= Thompson Course Technology, n.d.)</a>. The input and output requirements are especia= lly important to the overall system design, as these constraints often determine which methodologies to use during the Design Phase. Over the past ten years, several architecture-centric analys= is and design methods became available. These methodologies evolved to meet the requirements of the organizations employing them in both Analysis and Design Phases. These methodologies, in no particular order, include Quality Attrib= ute Workshop, or QAW; Cost-Benefit Analysis Method, or CBAM; Active Reviews for Intermediate Design, or ARID and Attribute-Driven Design, or ADD= . While this list is not exhaustive, it includes predominate examples <a name=3DC385419164236111385435808680556>(Kazman et al., 2003)</a>. From this= list, I will examine the Cost-Benefit Analysis Method, or CBAM, as it is representative of all methods. The Cost-Benefit Analysis Method “helps the systemR= 17;s stakeholders to choose among architectural alternatives for enhancing the system in design or maintenance phases” <a name=3DC385419164236111385435842129630>(Kazman et al., 2003)</a>. This meth= od, more than the others, examines the overall benefits and risks associated wi= th the system in terms of cost. “The CBAM enables users to make informed software requirement and software investment decisions based upon an analys= is of the economic and architectural implications of those decisions” <a name=3DC385435879050926385435887847222>(</a><st1:place w:st=3D"on"><st1:Pla= ceName w:st=3D"on">C= arnegie</st1:PlaceName> <st1:PlaceName w:s= t=3D"on">Mellon</st1:PlaceName> <st1:PlaceType w:st=3D"on">University</st1:PlaceType></st1:place><s= pan style=3D'mso-bookmark:C385435879050926385435887847222'>, 2005). This methodology offers the programmer and organization a process for analyzing = the financial benefits of the system in question. Authors Rick Kazman, Robert Nord, and Mark Klein from the Ca= rnegie Mellon Software Engineering Institute break down this process from required inputs to outputs. The inputs to the CBAM include a) the system’s business/mission drivers, b) a list of scenarios, and c) the existing architectural documentation. Utilizing these inputs and following the prescribed steps, the CBAM offers outputs that include a) a set of architectural strategies, with associated costs, benefits, and schedule implications, b) prioritized architectural strategies based on Return On Investment, or ROI, and c) the = risk of each architectural strategy, quantified as variability in cost, benefit,= and ROI values <a name=3DC385419164236111385435966550926>(Kazman et al., 2003)<= /a>. Obviously, the accuracy of the inputs greatly affects the va= lidity of the outputs. For the CBAM to be effective, the previous steps of the SDLC must be correct. Assuming the inputs have merit, the CBAM offers nine steps= for achieving valid outputs. Within these nine steps, various architecture-cent= ered scenarios present themselves for analysis and voting. It is during these st= eps that examination of scenarios occurs for their ability to meet all of the n= eeds of the organization, including business goals, quality attributes, costs, a= nd ROI. These steps repeat themselves until one scenario becomes apparent <a name=3DC385419164236111385436100115741>(Kazman et al., 2003)</a>. The Cost-Benefit Analysis Method described above is an examp= le of several architecture-centric methodologies available in addition to the traditional SDLC. “While each of these steps involves additional over= head as compared with the traditional, non-architecture-aware SDLC, this additio= nal encumbrance is more than repaid by having an architecture that is designed, documented, analyzed, and evolved in a disciplined way” <a name=3DC385419164236111385436193171296>(Kazman et al., 2003)</a>. Many computer-aided tools are available to a programmer when designing an enterprise system following the SDLC. One such tool is Oracle’s Designer/2000. T= his software helps a programmer through the SDLC from start to finish, although Oracle re-designs the SDLC slightly to make the best possible use of their program. Oracle presents this method as CASE Application Development Method= , or CADM <a name=3DC385419273958333385436277199074>(Dorsey & Koletzke, 2000)</a>. M= any of the CADM phases are concurrent with the traditional SDLC however; Oracle of= fers Pre-Analysis and Pre-Design Phases to their method. The Pre-Design Phase= sits between the Analysis and Design Phases. Using Oracle’s CADM, the Pre-Design Phase includes steps for the design plan, process flows, design standards, screen concept prototype, and Pre-Design evaluation. It is during this phase that decisions concerning the screen layout, navigation tools, h= elp systems, documentation, functionality, coding standards, and naming convent= ions come under scrutiny <a name=3DC385419273958333385436342592593>(Dorsey & Koletzke, 2000)</a>. Oracle’s Designer/2000 program aids this process by of= fering templates for the developer to use. “The Pre-Design phase is complete when users are happy with the screen prototypes and process flows. Both use= rs and developers should approve the design standards and Design Plan” <a name=3DC385419273958333385436363078704>(Dorsey & Koletzke, 2000)</a>. O= nce complete, the Design Phase begins. Oracle’s CADM divides the Design Phase into two sub-ph= ases: Database Design and Application Design. Again, this coincides with their Design/2000 software product. “The Design phase is where the blueprints are drawn= for building the system. Every detail should be laid out before generation̶= 1; <a name=3DC385419273958333385436384490741>(Dorsey & Koletzke, 2000)</a>. As described in previous paragraphs, good preparation is paramount before actu= al programming begins. Oracle’s Designer/2000 product keeps this in mind= for the programmer and aids both database and application design. “Database Design involves the designing of the tables = and columns along with the detailed specification of domains and check constrai= nts on the columns” <a name=3DC385419273958333385436411226852>(Dorsey &am= p; Koletzke, 2000)</a>. This phase corresponds with the Detailed Design phase = of other methodologies. It is during this phase where the definition of databa= se objects takes place, as well as the tables and modules required of the database. Definition of a final Entity-Relationship Diagram takes place in = this phase, and documentation of the database is an essential deliverable. Again, Oracle’s Designer/2000 program offers templates and menus to aid the developer through this process. “In addition to the design of specific applications and reports, Application Design involves decision making about what product wil= l be used for those designs, i.e. Visual Basic, Forms, HTML, or C++” <a name=3DC385419273958333385436457638889>(Dorsey & Koletzke, 2000)</a>. W= hereas the Database Design determines the underlying database, the Application Des= ign determines how the database will appear before the users. “Another important activity in this part of the Design phase is the cross-checks of = the database design. You want to be sure that the data elements you defined in = the Database Design part of Design are fully utilized and included in the set of modules you produce” <a name=3DC385419164236111385436489930556>(Kazma= n et al., 2003)</a>. Once complete and approved, Designer/2000 takes the develop= er to the Build Phase of the CADM. In this paper, I have examined a methodology and tool availa= ble to developers during the Design Phase of the SDLC. As shown, the SDLC continue= s to evolve and develop as needs and requirements arise. The method and tool examined in this paper represent various methodologies and tools available,= and it becomes incumbent on system developers to prepare themselves with the be= st methodologies and tools for the system. <o:p> </o:p> <o:p> </o:p> <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=3DR385435879050926></a><st1:place w:st=3D"o= n"><st1:PlaceName w:st=3D"on">Carnegie<= /st1:PlaceName> <st1:PlaceName w:st=3D"on">Mellon= </st1:PlaceName> <st1:PlaceType w:st=3D"on">University</st1:PlaceType></st1:place><s= pan style=3D'mso-bookmark:R385435879050926'> (2005). Cost Benefit Analysis Method (CBAM). Retrieved July 8, 2005, fr= om <a href=3D"http://www.sei.cmu.edu/architecture/products_services/cbam.html"><s= pan style=3D'mso-bookmark:R385435879050926'>http://www.sei.cmu.edu/architecture= /products_services/cbam.html</a> <a name=3DR385419273958333>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=3DR385419164236111>Kazman, R., Nord, R. L.,= & Klein, M. (2003, September). A Life= -Cycle View of Architectural Analysis and Design Methods. Retrieved July 8, 20= 05, from </a><a href=3D"http://www.sei.cmu.edu/pub/documents/03.reports/pdf/03tn026.pdf"><s= pan style=3D'mso-bookmark:R385419164236111'>http://www.sei.cmu.edu/pub/document= s/03.reports/pdf/03tn026.pdf</a> <a name=3DR385419069328704>Maryland Department of B= udget & Management (2002, July). Systems Development Life Cycle (SDLC) Volume 2 - SDLC Phases. Retrieved July 8, 2005, from </a><a href=3D"http://docushare.msde.state.md.us/docushare/dsweb/Get/Document-5070= 1/sdlcvol2.pdf">http://docushare.msde.state.md.us/d= ocushare/dsweb/Get/Document-50701/sdlcvol2.pdf</a> <a name=3DR385419019328704>Modell, M. E. (2003). System Development Life Cycle - Design= . Retrieved July 8, 2005, from </a><a href=3D"http://www.dai-sho.com/ddsd/ddsd04.html">= http://www.dai-sho.com/ddsd/ddsd04.= html</a> <a name=3DR385435624652778>Thompson Course Technolo= gy (n.d.). The Systems Development Life Cycle.= Retrieved July 8, 2005, from </a><a href=3D"http://www.muskalipman.com/VBObjects/SDLC= .pdf">http://www.muskalipman.com/VBObject= s/SDLC.pdf</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.320A6890 Content-Location: file:///C:/8E8B314E/BSA400_ERPDesign_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_ERPDesign.htm"> <![if IE]> <base href=3D"file:///C:\8E8B314E\BSA400_ERPDesign_files\header.htm" id=3D"webarch_temp_base_tag"> <![endif]><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> Design Phase 1 </div> </body> </html> ------=_NextPart_01C59055.320A6890 Content-Location: file:///C:/8E8B314E/BSA400_ERPDesign_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_ERPDesign.htm"/> <o:File HRef=3D"header.htm"/> <o:File HRef=3D"filelist.xml"/> </xml> ------=_NextPart_01C59055.320A6890--