Home

Architecture-Diagram-Final-Lab

1. 2 When all of the functionality of the entire system can be represented on a single page it is not necessary to refine the High Level Diagram into Sub Systems that is not the case for this application Refined AD Architecture Sub System Diagram 1 Create the Sub System Architecture Diagram s that refines the Users SubSystem The sub system name Users Sub System should be clearly visible You may use more than one slide if necessary Your slides need not follow the format below but they must clearly illustrate the functionality By Title Basic Functionality By Name Tag Delete A dd This Record Inventory Sub System Include Basic Functionality Ete Go Last Logical Record ear a Navigation Functionality Go First Logical Record Go Previous Logical Record Go Nex Logical Record Inventory Sub System CONT Include Navigational Functionality Can Food Seafood Fish amp Meat Filter Breads amp Bakery Functionality Fruits amp Vegetables Anarene AQMhrmMeaA Inventory Sub S stem CONT Include Filter Functionality you may include more than one Index Order Functionality Hopefully Won t Have To Sort To Change lt a momo Inventory Sub System CONT Include Order By Functionality Aschitecture Diagram Customer Management System Refinement 1 4 2007 Custom All Users Custom This User Late Notices All Users All Users
2. Late Notice This User This User Recent History View Check Out History Specials All User By Interest This User Total History View Payment History Print Reports Specials This User Contact List All Users Late Notice All Users Advanced Combo Search Late Notice This User By ID By Name 3 z 2 m JIE 2 g Customer Management System Include Report Functionality Architecture Diagram Customer Management System Refinement 1 4 2007 Every Body Interest Drama Interest Mystery Soler Fier ree inves Comedy ee Interest Sci Fi Interest Computer Games Interest etc Customer Management System 2 These diagrams should include sufficient information to enable the software engineer to understand all of the functionality required for this portion of the project Only include the functionality that directly relates to this sub system it is the case that you might have a button on the Customer Users Form to transport this User to a Check Out Form but that does not make this part of the Customer Users System 3 You must include Filters and Order By You must include great navigation buttons that include at least Next amp Previous 4 Once you have your prototype for this component completed you should make sure that all functionality described in the AD is clearly available on the proper forms 5 Once you have your class diagrams for this component completed you should make s
3. many slides as is necessary Purchase Order Sub System 11 The next major slide is a Title Slide that says Purchase Order Sub System Architecture Diagram s 12 Immediately after this title slide shall be a collection one or more slides of professional quality screen captures of the User s Sub System Architecture Diagrams Imagine yourself using it during a formal review session with your stakeholder s If the audience can clearly see the entire Subsystem AD on a single slide label it Purchase Order Sub System Architecture Diagram A and continue if not label the other slides Purchase Order Sub System Architecture Diagram A Purchase Order Sub System Architecture Diagram B Purchase Order Sub System Architecture Diagram C etc Use as many slides as is necessary Sales Order Sub System 13 The next major slide is a Title Slide that says Sales Order Sub System Architecture Diagram s 14 Immediately after this title slide shall be a collection one or more slides of professional quality screen captures of the User s Sub System Architecture Diagrams Imagine yourself using it during a formal review session with your stakeholder s If the audience can clearly see the entire Subsystem AD on a single slide label it Sales Order Sub System Architecture Diagram A and continue if not label the other slides Sales Order Sub System Architecture Diagram A Sales Order Sub System Architecture Diagram B Sales Order Sub System Ar
4. Final Architecture Diagrams 1 Lab Print Only Page 1 All of the work in this project is my own have not left copies of my code in public folders on university computers have not given any of this project to others will not give any portion of this project to others taking this class realize that the penalty for turning in work that is not my own can range from an F in the class to dismissal from Trinity University Team Name Team Print Name Time Spent i Hrs Signature pledged What Did this team member contribute to this application Print Name Time Spent Hrs Signature pledged What Did this team member contribute to this application Print Name Time Spent i Hrs Signature pledged What Did this team member contribute to this application Print Name Time Spent Hrs Signature pledged What Did this team member contribute to this application Architecture Diagram Software Select Anything You Want Final High Level AD amp Subsystem AD Lab Architectural Diagrams Team Lab Assignment 50 Points For SECURITY Reasons It Is Imperative That You Do Not Leave Any PowerPoint Or Prototype Components On Any University Computer In An UnSecure Folder Build The Right System 1 As your book points out more than a dozen times the job of the software engineer is to build the right system that is the system that the user wants It will often not be the system that
5. chitecture Diagram C etc Use as many slides as is necessary r Sub System Any Other Sub System You Have Deemed Necessary 13 The next major slide is a Title Slide that says Sub System Architecture Diagram s 14 Immediately after this title slide shall be a collection one or more slides of professional quality screen captures of the User s Sub System Architecture Diagrams Imagine yourself using it during a formal review session with your stakeholder s If the audience can clearly see the entire Subsystem AD on a single slide label it Sub System Architecture Diagram A and continue if not label the other slides Sub System Architecture Diagram A Architecture Diagram B Sub System Architecture Diagram C etc Use as many slides as is necessary General Information 1 You will turn in Team x Architecture Diagrams Final ppt What To Turn In 1 Page 1 of this assignment sheet Signed by all 2 Put a copy of your power point presentation in the Team Folder on Mars 3 Each team member should put a backup copy on his her own computer Put a backup copy on your Y drive Put a copy on your thumb drive 4 Printed Copy Of The Entire Power Point Presentation 1 slide to a page 10 POINTS
6. eam 3 Architecture Diagrams 3 Philip Jensen Douglas Wolf Will Thornton Orange Technologies Team 1 on CS 1 p MrR T EE CONAN T h N Team Bulletproof e Mike Warner l Tony Heehler Philip Repsher 2 The first slide is a Title Slide that shall contain e Says Architecture Diagrams 1 e Your company name revise it if you like e The names of all team members e Team replace with your number e Atleast one graphic image that you think is reflective of your group or team name 3 The next slide is a Title Slide that says High Level Architecture Diagram 4 Behind the title slide shall be a slide that contains a professional quality screen capture of your High Level Architecture Diagram Imagine yourself using it during a formal review session with your stakeholder s User Sub System 5 The next major slide is a Title Slide that says Users Sub System Architecture Diagram s 6 Immediately after this title slide shall be a collection one or more slides of professional quality screen captures of the User s Sub System Architecture Diagrams Imagine yourself using it during a formal review session with your stakeholder s If the audience can clearly see the entire Subsystem AD on a single slide label it Users Sub System Architecture Diagram A and continue if not label the other slides Users Sub System Architecture Diagram A Users Sub System Architecture Diagram B Users Sub System Architecture D
7. iagram C etc Use as many slides as is necessary Vendor Sub System 7 The next major slide is a Title Slide that says Vendors Sub System Architecture Diagram s 8 Immediately after this title slide shall be a collection one or more slides of professional quality screen captures of the Vendor s Sub System Architecture Diagrams Imagine yourself using it during a formal review session with your stakeholder s If the audience can clearly see the entire Subsystem AD on a single slide label it Vendors Sub System Architecture Diagram A and continue if not label the other slides Vendors Sub System Architecture Diagram A Vendors Sub System Architecture Diagram B Vendors Sub System Architecture Diagram C etc Use as many slides as is necessary Inventory Sub System 9 The next major slide is a Title Slide that says Inventory Sub System Architecture Diagram s 10 Immediately after this title slide shall be a collection one or more slides of professional quality screen captures of the User s Sub System Architecture Diagrams Imagine yourself using it during a formal review session with your stakeholder s If the audience can clearly see the entire Subsystem AD on a single slide label it Inventory Sub System Architecture Diagram A and continue if not label the other slides Inventory Sub System Architecture Diagram A Inventory Sub System Architecture Diagram B Inventory Sub System Architecture Diagram C etc Use as
8. ure that the fields necessary to implement all of the functionality described in the AD are available 6 Save all your original files so that you are able to modify them Each and every team modified the first of these diagrams last year 7 This is the time to carefully think through the implementation and design For example suppose there is a function called Delete on the AD diagram we have already discussed the problems that would occur if you physically removed users customers from the system check out transactions would be problematic because these transactions would point to records that don t exist BAD Thus we should have a field maybe called Deleted in the users customers class It should appear in the class diagram for users customers Create A Power Point Presentation 1 Create a Power Point Presentation for your Architecture Diagram screen captures If you are on Team 1 call the presentation Team 1 Architecture Diagrams Final ppt If you are on Team 2 call the presentation Team 2 Architecture Diagrams Final ppt etc Make all slides professional enough to view with stakeholder Create A Great First Slide Architecture Diagrams 3 Team Prospera Kerry Seitz Elise Thrasher Amara Keller Bonnie Brent Team 2 On System CS 2 NR a Evan Barnett Danny Saltus James Seales Kenny Wong Architecture Diagrams Prometheus Kendall Bailey Matthew Fitzpatrick Matt Hawley Ryan Tanner T
9. you would necessarily want 2 Review the project description 3 There will be times that wear the hat of the Stakeholder and tell you what want in our system Your book says that a stakeholder may well mention something once in passing and expect you to have that in the delivered product 4 You will often rely on witch craft to anticipate what the user might need want like before they tell you Your job is to create the ideal solution Build the Right System 5 Remember hope to franchise this application your software will be used by each and every site Project Thoughts 1 Your system is to be a multi user stand alone system that has absolutely no interface between any other computer system 2 You need not concern yourself with Payroll or Scheduling 3 You are to complete the design for a system that meets all of the communication and organization needs 4 You are to design a system whose functionality is so obvious that a user manual is not necessary 5 You are to concentrate on technology and take the application into the next 10 years Think outside the box 6 We have discussed a number of different scenarios gt Why was it necessary to look up a user Architecture Diagram AD 1 Create a High Level Architecture Diagram that shows all of the Sub Systems in the Application Save all your original files so that you are able to modify them Each and every team modified the first of these diagrams last year

Architecture-Diagram-Final-Lab

Contents

Download Pdf Manuals

Related Search

Related Contents