Home

Class-Diagram-Final-Lab

1. System Class Diagram A Inventory Sub System Class Diagram B Inventory Sub System Class Diagram C etc Use as many slides as is necessary Purchase Order Sub System 11 The next major slide is a Title Slide that says Purchase Order amp Purchase Order Support Sub System Class 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 Class Diagrams and Support Class Diagrams Imagine yourself using it during a formal review session with your stakeholder s If the audience can clearly see the entire Class Diagram and Support Class Diagrams on a single slide label it Purchase Order Sub System Class Diagram A and continue if not label the other slides Purchase Order Sub System Class Diagram A Purchase Order Sub System Class Diagram B Purchase Order Sub System Class 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 amp Sales Order Support Sub System Class 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 Class Diagrams and Support Class Diagrams Imagine yourself using it during a formal review session with your stakeholder s If the audience can clearly see the entire Class Diagram and Support Class Diagrams on a single slide label it Sales Order Su
2. with the field attribute name the data type desirable would be the size and whether or not it would be a required field 3 You may use UML diagramming software name String primaryContactMethod String emailAddress String faxNumber String getNameQ String setName String void getEmailAddressd String setEmailAddress String void getF axNumben String setF axNumbenString void 4 You may use any database software design software 5 You may use the spread sheet data that we used for the design thoughts r Dheightscc MySQL Table File Edit Window Help PS New bed Save iH SaveAs fg Add Field Insert Field F Delete Field Fields Indexes Foreign Keys Triggers Options Comment SQL Preview Name Type Length gt UseriD int 11 UserName varchar 50 Password varchar 50 FullName varchar 35 Administrator char 1 Staff char 1 Leader char 1 Member char 1 Attend char 1 First varchar 20 Initial char 1 Last varchar 30 getPrimaryContactMethodgO String setPrimaryContactMethod String void Decimals eo o oocsoeoedqgceoe oc oc 8 O Allow Null HHH S K N S e g e o Primary Key MoveUp PP PRP NF oO Ww won nun Ff WN _id unique int _id user_password varchar 25 parent_id user_group int indexed supervisor_id first_name varchar 45 type last_name varchar 45 description picture BLOB date_added address varchar MAX added_by city varch
3. Final Class Diagrams 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 Class Diagram Software Select Anything You Want Final Class Diagrams Lab Class Diagrams Team Lab Assignment 60 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 you would necessarily want 2 Review the p
4. Final ppt etc Make all slides professional enough to view with stakeholder Class Diagrams 3 Team Prospera Team 2 On System CS 2 Evan Barnett Danny Saltus James Seales Kenny VVYong CLASS DIAGRAMS 3 THE SOFTWARE SCIENTISTS Class Diagrams Prometheus Kendall Bailey Matthew Fitzpatrick Matt Hawley Ryan Tanner Team 3 Class Diagrams Final Philip Jensen Douglas VVolf Will Thornton Orange Technologies Team 1 on CS 1 Team Bulletproof Mike Warner Tony Heehler Philip Repsher Team Behera 2 4 The first slide is a Title Slide that shall contain e Says Class 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 User Sub System 5 The next major slide is a Title Slide that says User amp User Support Class Class 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 Class Diagrams and Support Class Diagrams Imagine yourself using it during a formal review session with your stakeholder s If the audience can clearly see the entire Class Diagram and Support Class Diagrams on a single slide label it Users Sub System Class Diagram A and continue if not label the other slides Users Sub System Class D
5. ar MAX date_modified region varchar 100 modified_by 4 Whatever the implementation it should clearly identify the class of sub cass 5 It must include the data type for each attribute field varchar 45 var char MAX DATETIME DATETIME auto increment int default 0 null 6 Identifying size primary key and required are quite helpful when discussing this with the user and providing it to the developer 7 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 8 Make sure that you look at your prototype carefully Make sure that your class diagrams have every data item necessary to create every Filter 9 Make sure that you look at your prototype carefully Make sure that your class diagrams have every data item necessary to create every Order By 10 These diagrams should include sufficient information to enable the software engineer to create the all of the prototypes for this portion of the project 11 This system is to take advantage of all that technology has to offer possibly systems for user searching web interface etc 12 This must be professional in appearance Create A Power Point Presentation 1 Create a Power Point Presentation for your Class Diagram screen captures If you are on Team 1 call the presentation Team 1 Class Diagrams Final ppt If you are on Team 2 call the presentation Team 2 Class Diagrams
6. b System Class Diagram A and continue if not label the other slides Sales Order Sub System Class Diagram A Sales Order Sub System Class Diagram B Sales Order Sub System Class 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 Class 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 Class Diagrams and Support Class Diagrams Imagine yourself using it during a formal review session with your stakeholder s If the audience can clearly see the entire Class Diagram and Support Class Diagrams on a single slide label it Sub System Class Diagram A and continue if not label the other slides Sub System Class Diagram A Class Diagram B Sub System Class Diagram C etc Use as many slides as is necessary General Information 1 You will turn in Team x Class 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 15 POINTS
7. iagram A Users Sub System Class Diagram B Users Sub System Class Diagram C etc Use as many slides as is necessary Vendor Sub System 7 The next major slide is a Title Slide that says Vendor amp Vendor Support Sub System Class Diagram s 8 Immediately after this title slide shall be a collection one or more slides of professional quality screen captures of the User s Class Diagrams and Support Class Diagrams Imagine yourself using it during a formal review session with your stakeholder s If the audience can clearly see the entire Class Diagram and Support Class Diagrams on a single slide label it Vendors Sub System Class Diagram A and continue if not label the other slides Vendors Sub System Class Diagram A Vendors Sub System Class Diagram B Vendors Sub System Class 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 amp Inventory Support Sub System Class 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 Class Diagrams and Support Class Diagrams Imagine yourself using it during a formal review session with your stakeholder s If the audience can clearly see the entire Class Diagram and Support Class Diagrams on a single slide label it Inventory Sub System Class Diagram A and continue if not label the other slides Inventory Sub
8. roject 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 Class Diagram s Hint You Should Have At Least One Support Class 1 Create the Class Diagram for the Users Customers Class and all support classes You may use Spreadsheet Database OR UML You may combine all of your Users into one class 2 Whatever style you use should provide the developer

Class-Diagram-Final-Lab

Contents

Download Pdf Manuals

Related Search

Related Contents