Documentation, Requirements Analysis-Software Engineering-Lecture Slides, Slides of Software Engineering

Download Documentation, Requirements Analysis-Software Engineering-Lecture Slides and more Slides Software Engineering in PDF only on Docsity!

CS 501: Software Engineering

Fall 2000

Lecture 5

(a) Documentation (b) Requirements Analysis

Nomadic Computing Experiment

RECITATION SESSION, MONDAY SEPTEMBER 11

Dell laptops with wireless cards available for CS 501 projects

• 3 or 4 laptops per project
• 1 or 2 additional wireless cards per project
• surveys at beginning and end of project Each project as part of the Feasibility Study and Plan must identify which students will take responsibility for the equipment.

Assignment 1

Wednesday, September 13: Project plan due -- report. Title of project Client/customer Team members Outline description Current status (e.g., previous work) Plan (e.g., major stages, assignment to tasks, technical environment, schedule, etc.) Any other relevant information

Projects

Teams that are planning to carry out the Internet Butler project, please meet with me after the lecture.

Form of Documentation

External

• Printed
• Web site Internal
• Program documentation
• Program context (e.g., copyright notices)

Requirements Definition and Analysis

Requirements Definition

System and Software design

Programming and Unit Testing

Integration and System Testing

Operation and Maintenancedocsity.com

Requirements Analysis

1. Understand the requirements in depth:

• Domain understanding Examples: Tote Investors, Philips light bulbs
• Stakeholders

Example: Andrew project

Viewpoint Analysis

Example: University Admissions System

• Applicants
• University administration Admissions office Financial aid office Special offices (e.g., athletics, development)
• Computing staff Operations Software development and maintenance
• Academic departments

Requirements Analysis

2. Organize the requirements:

• Classification into coherent clusters (e.g., legal requirements)
• Recognize and resolve conflicts (e.g., functionality v. cost v. timeliness)

Example: Dartmouth general ledger system

Requirements Analysis

3. Model the requirements:

• Informal Prose
• Systematic Procedural models Data-centric models Object models
• Formal models

Flowchart: University Admissions

Form received New?

Database record

T

Notify student

F Update database

Complete?

Notify student

T

F

Evaluate

Procedural Models: Pseudo-code

Example: Check project project plan check_plan (report) if report (date_time) > due_date_time then error (too_late) if report (client) = none then error (no_client) if report (team) < min_team or > max_team then error (bad_team) if error() = none then comments = read_report (report) return (comments (text), comments (grade)) else return error()

Example: University Admissions

Applicant

Application form (^) Receive application

Completed application Evaluate

Rejection

Offer

Example: University Admissions

Assemble Application Stage

Applicant

Application form Receive

Completed application

Supporting information

Pending database

Acknowledgment

Initiate evaluation

Applicant database

Evaluation request

AND

AND

Acknowledgment