7-SRS - team status team invite a TA or both invite on your...

Info iconThis preview shows page 1. Sign up to view the full content.

View Full Document Right Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: team status team invite a TA, or both invite on your web site: on Meeting highlights Roles – who is point of contact Phase 3 Phase The Software Requirements Specification Customer Points-of-Contention Customer Assumptions, Constraints, Limits Function Documentation – technical, user, and Documentation training manuals training Training Maintenance / Enhancements Requirements Changes Status and Reviews The Software Requirements Specification Specification After review of the customer’s System After Spec. Spec. After educated analysis Preliminary design A technical, software “approach” Results in permission to detail-design and Results code code From the customer’s perspective From How smart people are going to solve the How problem that was stated in the System Spec. Spec. A “contract”, more or less Is it doable? Technically On time Under budget Settles these issues: Settles Software Architecture Software Object Oriented? Structured? Database Oriented (Informational Flow)? Event Driven Major Modules to 2 or 3 levels of supervision llow level utilities if they touch hardware or the ow environment environment Risk Assessment Risk Technical Risks hardware software interfaces build vs. buy Schedule Risks budget calendar personnel – level of expertise required Phase 3 Phase Write PARTS OF an SRS Write PARTS Drawings Functional description Integration Thread (also a Drawing) Change of Scope Form Cross Reference Major Module Descriptions Major Supervisory / Executive Classes, Major Objects, and Libraries Build vs. Buy Interfaces Module to Module SW to HW Control to Data Low Level Utilities Drivers The Cross Reference Typically the last section of the SRS Typically List items from the System Spec. Tell which section of the SRS provides Tell coverage. coverage. Identify the items that contain risk. Identify the items that will be designed Identify with flexibility. with Identify the items that define the “Critical Identify Path” Path” NEXT SEMESTER (CSE453) Development Vehicle Development Development OS (may have been Development specified in System Spec) specified Language (may have been specified in Language System Spec) System Editors, Syntax Checkers, Libraries The Configuration Management and The Version Control Systems Version Specified for budgetary more than Specified technical reasons. technical NEXT SEMESTER (CSE453) Execution Vehicle Execution A llarge undertaking if not specified in the arge System Spec. System SHOULD be decided with the customer SHOULD before the SRS – force it into the System before Spec. Spec. NEXT SEMESTER (CSE453) After the SRS After Critical Design Module Level Details Structure Charts / Object Charts build the Integration Thread build Major Module Interfaces module-to-module hardware to software drivers to control (up levels of supervision) Can’t Go Back Can’t Once an SRS is approved, changes Once become very expensive: become A specification change, leading to design specification changes, lleading to coding changes, leading changes eading to schedule/budget changes, leading to testing changes and finally delivery changes testing Catch specification mistakes in the Catch specification phase. How? specification In the System Spec and SRS Use reviews ...
View Full Document

This document was uploaded on 11/03/2011 for the course CSE 442 at SUNY Buffalo.

Ask a homework question - tutors are online