• Home
  • Utah Valley University
  • Software Engineering CS 2450
  • Software Engineering CS 2450 - Week 2 Lectures

Software Engineering CS 2450 - Week 2 Lectures

CS-2450 Week 2 Lectures and Notes Table of Contents WEEK 2 Lectures Lecture 3 Lecture 4 Chapter 3 The Software Life Cycle Revisited 3.1 The Waterfall Model 3.2 Agile Methods 3.2.1 Prototyping 3.2.2 Incremental Development 3.2.3 Rapid Application Development and Dynamic Systems Development Method 3.2.4 Extreme Programming 3.4 Model-Driven Architecture 3.5 Intermezzo: Maintenance or Evolution 3.7 Process Modeling 3.8 Summary Chapter 3 Slides UML Diagrams 2 2 2 3 4 5 6 7 9 10 12 14 15 16 17 17 29 WEEK 2 Lectures Lecture 3 Challenging chapters are Cost Estimation, Software Architecture, and Software Design. The weakness of agile development is that it does not use documentation well. We will be tested on life cycle models (from Chapter 3). Total quality management (TQM) is a form of agile development. Agile is not a method; it is a collection of methods. For the life cycle methods, none of them are really better than the others; the best model is just whatever works for you. Project: 0 Notes Students will be elementary kids up to 5th grade. Your program only needs to be able to run on one platform Our process model for the project plan is prototypical agile code For risks in the project plan, where are possible places we may fail? Staffing: Note who does what. You may decide to hand out work breakout packages that tell each person what to do. Resources: What resources do we have that are able to use? Schedule: We have 5-ish weeks. Suggestion: Have a tutorial that teaches the kids how to use the abacus. Change orders are used for changes. Make a form that explains what the change is, how many points we want for it, etc. Each person will submit the entire team project in Canvas. Money: We will use points for the project instead of money. (e.g., We estimate that this prototype will cost dollars because of these functions that we used.) Team manager should not be your best programmer; they should be your best organizer. Think of requirements for: Software maintenance Software backup How a user will expect the program to work. Will teachers be using the abacus for testing? Will the abacus remember user information, such as personal data? Learning levels of the abacus Accessibility - Can the kids access it from home? (Is it on the Internet?) Lecture 4 At the end of Milestone 1, your practice project should have the most essential parts that your project may have. What gets you your grade for Milestone 1 is if you make a sincere effort in trying out ADO. A work breakdown structure looks something like this: Abacus Project GUI Test Tutorial Confirm requirements Run code examples A work breakdown structure creates the Gantt chart; a Gantt chart creates the PERT chart. Look at the Extensions for Visual Studio for AzureDevOps. Project The real job of the team manager is that they assign each individual tasks and make sure that those tasks get done. o