csse 371 – software requirements and specification sriram mohan
TRANSCRIPT
CSSE 371 – Software Requirements and Specification
Sriram Mohan
Outline
Introductions The Class Process
Possible life cycle
General Themes
How do we interact with clients to obtain requirements? How do we use the requirements to design the software? How do we use the requirements to verify client needs? How do we use the requirements to design the interaction?
Project versus Lecture
General Info
Books Managing Software Requirements: A Use Case Approach, Second
Edition, by Dean Leffingwell and Don Widrig Interaction Design: beyond human-computer interaction, Second
Edition, by Jennifer Preece, Yvonne Rogers and Helen Sharp
Office Hours
Course Components
Project This is the most important part of the learning experience 50% of the grade
Exams 20% of the grade Three mid-terms(No Finals)
Assignments Close to 16 20% of the grade
Class Interaction 10%
Outline
Introductions The Class Process
Project
Real clients with real needs Simulate the real world Teams
Each team will have 3 students. Management assigned
Management Project Managers(Brittany, Michelle & Zach) Quality Assurance Monitors(Brittany, Michelle & Zach) Instructor(me)
Project Deliverables
Fall Winter
Vision Document Detailed Design Document
Preliminary Design Document Detailed Test Plan
Preliminary Test Plan Finished Product
Supplementary Specification Usability Report
Interface Design Programmers Manual
Quality Assurance Plan User Manual
Usability Report Client Comments
Client Comments Presentations
Presentations Poster
Fall MilestonesDeliverable Contents Due DateMilestone 1 Current System Analysis
Client Stakeholder Analysis
Feature ListingProject Plan
September 20
Milestone 2 Use casesData Flow Diagram
October 7
Milestone 3 Supplementary Specification
Initial Design/Paper prototype
October 17
Milestone 4 Pseudo codeCoding Standards
Test Cases
October 26
Milestone 5 Usability ReportRevised Design
November 7
Final Deliverable Vision DocumentTest Plan
Design PlanInterface Design
Quality Assurance PlanUsability ReportClient Comments
November 12
Client Presentation Week of 5th NovemberPost Partum Presentation
Experiences ... Final Exam date
Team Activities
Meet with client once a week Meet with project manager once a week Meet regularly Plan Use your project manager and instructors expertise.
Plan ahead
Team Roles
Secretary Contacts
Manager Instructor Client
Tasks Assigner Monitor
Librarian Guru
Team Log
Due weekly to the project manager A day before the meeting
Log records Teams weekly activities Tasks to be completed
Start and end dates Who is responsible for them? Progress
Project Manager
Assist the team with process Supervisory role Review teams artifacts Evaluate teams performance
Can recommend that a team member be fired
Writing
Professionally written No slang, chat lingo … Free of grammatical and spelling errors Well organized Thorough and complete
Must be submitted to supervisor before final submission Each team member must approve the submission. Use the learning center
I will be happy to review any portion of the document before final submission
Milestone Document Content
Signed Title Page Table of Contents Executive Summary Introduction Main content References Appendix Index Glossary
Submissions will be on paper – Use a 3 ring binder
Presentations
Client Presentation Post partum presentation
Anonymous Feedback
Questions???