1 / 12

CSE 403, Software Engineering Lecture 2

CSE 403, Software Engineering Lecture 2. Software Life Cycle. Waterfall model (McConnell). System specification. Requirements Analysis. Architectural Design. Detailed Design. Coding and Debugging. Unit testing. System testing. Maintenance. Waterfall Model (01 au slides). Spiral model.

lcleveland
Download Presentation

CSE 403, Software Engineering Lecture 2

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. Waterfall model (McConnell) System specification Requirements Analysis Architectural Design Detailed Design Coding and Debugging Unit testing System testing Maintenance

  3. Waterfall Model (01 au slides)

  4. Spiral model

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

  6. 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

  7. 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, . . .

  8. 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

  9. Challenges of requirements gathering (Kulak, Guiney) • Finding out what users need • Documenting users' needs • Avoiding premature design assumptions • Resolving conflicting requirements • Eliminating redundant requirements • Reducing overwhelming volume • Traceability

  10. Use case • Overview of interactions • Text details • Example • Authenticate User • Actors: User, Unauthorized user • Summary: Users request entry to the system, valid credentials allow access

  11. Restaurant Reservation System • Support assignment of patrons to tables • Customer • Restaurant in a large chain • Willing to invest resources for a system that could be deployed widely

  12. Develop use cases for reservation system • What are the use cases?

More Related