csse 371/372 – software requirements and specification/software project management
DESCRIPTION
CSSE 371/372 – Software Requirements and Specification/Software Project Management. Steve Chenoweth/Sriram Mohan RHIT. Introductions. Name Major Hometown An interesting fact about you that others at Rose probably don’t know. Course Overview. Materials on Angel Syllabus Schedule. - PowerPoint PPT PresentationTRANSCRIPT
CSSE 371/372 – Software Requirements and Specification/Software Project Management
Steve Chenoweth/Sriram Mohan
RHIT
Introductions
Name Major Hometown An interesting fact about you that others at Rose probably
don’t know
Course Overview
Materials on Angel Syllabus Schedule
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? How do we plan, monitor and control a project?
Project versus Lecture
General Info
Books - 371 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
Books – 372 Effective Project Management: Traditional, Adaptive, Extreme,
Fourth Edition by Robert K. Wysocki, (paperback)
Case Studies Office Hours
Course Components
Project This is the most important part of the learning experience 5 Milestones (Typically due on Friday) 50% of the grade
Exams 20% of the grade Two mid-terms(No Finals)
Assignments 9 in 371, 8 in 372 (Typically Due on Tuesday and Friday) 9 Case Studies (Typically on Friday, Monday) 20% of the grade
Class Interaction/Quizzes/In-Class Activities 10%
Project
Project
Real clients with real needs Simulate the real world Teams
Each team will have 3 students. Management assigned
Project Managers Derek Baker Sam Green Tyler Gonnsen Andrew Houvener Jarrod Stormo
Project Deliverables
Deliverable Content Due Date
Milestone 1 Individual Engineering Journal
371-Current System Analysis371-Client Stakeholder Analysis371-Feature Listing372- POS372-Risk Assessment372- WBS
Sept 26
Milestone 2 Individual Engineering Journal 371-Use Cases371- Data Flow Diagram372-Risk Assessment372- WBS with Estimates and resource assignment
Oct 10
Milestone 3 Individual Engineering Journal 371-Supplementary Specification371- Initial Design/Paper Prototype372-Risk Assessment372- WBS with Estimates and resource assignment372- Project Plan
Oct 20
Project Deliverables
Deliverable Content Due Date
Milestone 4 Individual Engineering Journal 371-Psuedo code371- Coding Standards371- Test Cases372-Risk Assessment372- WBS with Estimates and resource assignment372 – Earned Value
Oct 30
Milestone 5 371-Initial Design371- Usability Report371- Final Design372-Risk Assessment372- WBS with Estimates and resource assignment372 – Earned Value
Nov 11
Final Individual Engineering Journal 371-Initial Design371 & 372 - Final Updated Versions of all milestones transitioned to new team (includes signoff)371 & 372 - Client Comments372 - Lessons Learnt372 – Report on use of Configuration Management
Oct 20
Presentations
Client Presentation Post partum presentation
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
Weekly Assessment Report
Due weekly to the PM and Primary Instructor PM – 12 hours before Meeting Instructor – Friday at Noon(Hard Copy)
It records Weekly Status Tasks to be completed next week
High Level Summary Who is responsible for them?
Tasks completed last week(same as above) Key issues and problems(include a mitigation strategy) Weekly Metrics(hours of work estimated, actual and variance from
previous weeks and total to date)
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
We 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
Anonymous Feedback
Questions???
Meetings Bloody Meetings
Discussion Question
What actionable things can you do as a project manager to have an effective meeting? (Due Monday – See Drop Box on Angel)