1 / 20

Understanding the Software Life Cycle: Key Stages and Models

This lecture covers vital aspects of the software engineering life cycle, including various models like Waterfall and Spiral. We'll explore the organization of workflow, requirement analysis, and team dynamics, using the Surgical Team model as a basis for discussion. Key dates for project milestones and assignments will also be outlined, emphasizing the importance of understanding what goes beyond mere programming in software development. Students will critique the proposed team structure for the GizmoBall project, focusing on adaptation and evaluation.

nibaw
Download Presentation

Understanding the Software Life Cycle: Key Stages and Models

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CSE 403, Software EngineeringLecture 2 Software Life Cycle

  2. Announcements • Quiz section will be held in CSE 305

  3. Project Schedule • Preliminary Design, April 15 • Preliminary Release, May 6 • Test Plan, May 20 • Design Critique, June 1 • Final Release, June 1

  4. Writing assignment • Due Monday, 1:30 pm, April 4 • Individual Assignment • Target length: two pages Critique the Surgical Team model proposed by Brook's as an organization for your GizmoBall project.  You should first describe how you would adapt the model to a 6 or 7 person team, and then evaluate how appropriate it would be as a team organization.

  5. Lecture schedule • 1. Introduction • 2. Life Cycle • 3. Teams • 4. Risk analysis • 5. Requirements and Design • 6. Development and Deployment

  6. Course goal • To gain an understanding that developing a software product is not merely a matter of programming

  7. If it's not merely programming • What is it?

  8. Life Cycle

  9. Software life cycle

  10. Life Cycle (McConnell) System specification Requirements Analysis Architectural Design Detailed Design Coding and Debugging Unit testing System testing Maintenance

  11. Life Cycle (01 au slides)

  12. Model Goals • Understand what goes on • Organize workflow • Formal process

  13. Waterfall Model • Strong directionality in stages • Limited up stream interaction • Very large costs in fixing errors arising from early stages

  14. Critiques of the Waterfall Model

  15. Spiral model

  16. What is the value of a model • Understand process • Defining procedures • Decomposing workflow • Track, clarify, modify requirements through life cycle • Management tool

  17. Limitation of models • A model is just a model • Artificial constraints • Compromises with model necessary • (as with almost everything else in SE) • Risk of overemphasizing process • The process is not the end in itself • Product delivery is

  18. Requirements on requirements • Who are they for? • What are they for? • Pitch to management • Fodder for market study • Basis for legal contract • Easy to understand, concise, complete, unambiguous, . . .

  19. Requirements • "Gather and document the functions that the application should perform for the users in the users' language and from the users' perspective" • Requirements should neither constrain nor define methods of implementation

  20. Customers • (Almost) every large software project has a customer who is paying the bills • Project requirements driven by this customer

More Related